Resource element overlap between synchronization signal block and demodulation reference signal

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may receive a synchronization signal block (SSB) including a physical layer cell identifier (PCI), where one or more resource elements carrying the SSB overlap with resource elements carrying a downlink shared channel associated with another PCI. The PCI may be for a serving cell or for another cell, such as a non-serving cell. The UE may also receive one or more demodulation reference signals (DMRS) in one or more resource elements in the downlink shared channel. The UE may determine whether overlap is allowed between resource elements by comparing the PCI of the SSB and the PCI of the downlink shared channel. In some examples, once the UE determines whether resource element overlap is allowed, the UE may process the DMRS.

Description

[Technical field]

[0001] cross reference This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 187,293, filed May 11, 2021, by KHOSHNEVISAN et al., entitled "RESOURCE ELEMENT OVERLAP BETWEEN A SYNCHRONIZATION SIGNAL BLOCK AND DEMODULATION REFERENCE SIGNAL," and U.S. Patent Application No. 17 / 740,881, filed May 10, 2022, by KHOSHNEVISAN et al., entitled "RESOURCE ELEMENT OVERLAP BETWEEN A SYNCHRONIZATION SIGNAL BLOCK AND DEMODULATION REFERENCE SIGNAL," each of which is assigned to the assignee of the present application.

[0002] The following relates to wireless communications that include resource element overlap between synchronization signal blocks (SSBs) and demodulation reference signals (DMRSs). [Background technology]

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasts, and the like. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems, such as Long Term Evolution (LTE), LTE Advanced (LTE-A), or LTE-A Pro systems, and fifth generation (5G) systems, sometimes referred to as New Radio (NR) systems. These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, which may in some cases be known as user equipment (UE). Summary of the Invention [Means for solving the problem]

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support resource element overlap between a synchronization signal block and a demodulation reference signal. In general, the described techniques provide a user equipment (UE) for determining whether overlap is allowed between a resource element carrying a synchronization signal block (SSB) and a resource element carrying a demodulation reference signal (DMRS) in a downlink shared channel. The UE may receive an SSB including a physical layer cell identifier (PCI), where one or more resource elements carrying the SSB overlap with resource elements carrying a downlink shared channel associated with another PCI. The PCI may be for a serving cell or for another cell, such as a non-serving cell. The UE may also receive one or more DMRSs in one or more resource elements in the downlink shared channel. The UE may determine whether overlap is allowed between resource elements by comparing the PCI of the SSB and the PCI of the downlink shared channel. In some examples, once the UE determines whether resource element overlap is allowed, the UE may process the DMRS.

[0005] A method for wireless communication in a UE is described. The method may include receiving an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI, determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between the one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel, and processing the DMRS based on the determination.

[0006] An apparatus for wireless communication in a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI, determine whether overlap is allowed between the one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel according to a comparison of the first PCI and the second PCI, and process the DMRS based on the determination.

[0007] Another apparatus for wireless communication in a UE is described. The apparatus may include means for receiving an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI, means for determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between the one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel, and means for processing the DMRS based on the determination.

[0008] A non-transitory computer-readable medium storing code for wireless communication in a UE is described, which may include instructions executable by a processor to receive an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI, determine whether overlap is allowed between the one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel according to a comparison of the first PCI and the second PCI, and process the DMRS based on the determination.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining whether overlap may be allowed may include operations, features, means, or instructions for determining that overlap is not allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI and the second PCI corresponding to a serving cell.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining whether overlap may be allowed may include operations, features, means, or instructions for determining that overlap is not allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI and the second PCI being the same PCI.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining whether overlap may be allowed may include operations, features, means, or instructions for determining that overlap is not allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI and the second PCI corresponding to the second cell.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining whether overlap may be allowed may include operations, features, means, or instructions for determining that overlap may be allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI corresponding to a serving cell and the second PCI corresponding to a second cell.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining whether overlap may be allowed may include operations, features, means, or instructions for determining that overlap may be allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI corresponding to the second cell and the second PCI corresponding to the serving cell.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a control message corresponding to a control resource set (CORESET) pool index value corresponding to a downlink shared channel, where the control message includes a scheduling downlink control information (DCI) message.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining that the downlink shared channel may be associated with the serving cell based on the CORESET pool index value having a value of 0.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining that the downlink shared channel may be associated with the second cell based on the CORESET pool index value having a value of one.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control message may be a semi-persistent scheduling (SPS) control message corresponding to an activation DCI message received in a CORESET associated with the CORESET pool index value.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control message may be an SPS control message corresponding to an SPS configuration in a radio resource control (RRC) message, where the SPS configuration indicates a CORESET pool index value.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining that a downlink shared channel may be associated with a serving cell based on a quasi-co-location (QCL) relationship corresponding to the SSB being associated with the serving cell.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining that a downlink shared channel may be associated with the second cell based on a QCL relationship corresponding to the SSB being associated with the second cell.

[0021] A method for wireless communication in a network entity is described, which may include transmitting an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI, determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between the one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel, and processing the DMRS based on the determination.

[0022] An apparatus for wireless communication in a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to transmit an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI, determine whether overlap is allowed between the one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel according to a comparison of the first PCI and the second PCI, and process the DMRS based on the determination.

[0023] Another apparatus for wireless communication in a network entity is described. The apparatus may include means for transmitting an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI, means for determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between the one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel, and means for processing the DMRS based on the determination.

[0024] A non-transitory computer-readable medium storing code for wireless communication in a network entity is described, the code may include instructions executable by a processor to: transmit an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI; determine, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between the one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel; and process the DMRS based on the determination.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining, based on the first PCI and the second PCI corresponding to a serving cell, that there may be no overlap between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining that there may be no overlap between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI and the second PCI being the same PCI.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining, based on the first PCI and the second PCI corresponding to the second cell, that there may be no overlap between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining that one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS overlap based on the first PCI corresponding to a serving cell and the second PCI corresponding to a second cell.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining that one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS overlap based on the first PCI corresponding to the second cell and the second PCI corresponding to the serving cell.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for transmitting a control message indicating a CORESET pool index value corresponding to the downlink shared channel.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining that the downlink shared channel may be associated with the serving cell based on the CORESET pool index value having a value of 0.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining that the downlink shared channel may be associated with the second cell based on the CORESET pool index value having a value of one.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control message may be an SPS control message corresponding to an activation DCI message received in a CORESET associated with the CORESET pool index value.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control message may be an SPS control message corresponding to an SPS configuration in the RRC message, where the SPS configuration indicates a CORESET pool index value.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining that a downlink shared channel may be associated with a serving cell based on a QCL relationship corresponding to the SSB being associated with the serving cell.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining that a downlink shared channel may be associated with the second cell based on a QCL relationship corresponding to the SSB being associated with the second cell. [Brief description of the drawings]

[0037] [Figure 1] FIG. 1 illustrates an example of a wireless communication system supporting resource element overlap between synchronization signal blocks (SSBs) and demodulation reference signals (DMRSs) in accordance with an aspect of the present disclosure. [Diagram 2] FIG. 2 illustrates an example of a wireless communication system supporting resource element overlap between SSB and DMRS, according to an aspect of the present disclosure. [Diagram 3] FIG. 2 illustrates an example of a resource diagram supporting resource element overlap between SSB and DMRS, according to an embodiment of the present disclosure. [Figure 4] FIG. 1 illustrates an example of a transmission diagram supporting resource element overlap between SSB and DMRS, according to an aspect of the present disclosure. [Diagram 5] FIG. 1 illustrates an example of a process flow for supporting resource element overlap between SSB and DMRS according to an embodiment of the present disclosure. [Figure 6] 1 is a block diagram of a device supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. [Figure 7] 1 is a block diagram of a device supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. [Figure 8] 1 is a block diagram of a communications manager supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. [Figure 9] FIG. 1 is a diagram of a system including a device that supports resource element overlap between SSB and DMRS, according to an aspect of the disclosure. [Figure 10] 1 is a block diagram of a device supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. [Figure 11] 1 is a block diagram of a device supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. [Figure 12]1 is a block diagram of a communications manager supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. [Figure 13] FIG. 1 is a diagram of a system including a device that supports resource element overlap between SSB and DMRS, according to an aspect of the disclosure. [Figure 14] 1 is a flowchart illustrating a method for supporting resource element overlap between SSB and DMRS according to an aspect of the present disclosure. [Figure 15] 1 is a flowchart illustrating a method for supporting resource element overlap between SSB and DMRS according to an aspect of the present disclosure. [Figure 16] 1 is a flowchart illustrating a method for supporting resource element overlap between SSB and DMRS according to an aspect of the present disclosure. [Figure 17] 1 is a flowchart illustrating a method for supporting resource element overlap between SSB and DMRS according to an aspect of the present disclosure. [Figure 18] 1 is a flowchart illustrating a method for supporting resource element overlap between SSB and DMRS according to an aspect of the present disclosure. [Figure 19] 1 is a flowchart illustrating a method for supporting resource element overlap between SSB and DMRS according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0038] In some communication systems, before exchanging data and additional messages, a user equipment (UE) may monitor and receive synchronization signals from a network entity, such as one or more components of a cell or base station, to determine configuration and timing information for transmitting and receiving subsequent messages to and from the cell or base station. For example, a cell or one or more components of a base station may transmit a synchronization signal block (SSB) including a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a physical broadcast channel (PBCH), a master information block (MIB), etc. In some examples, the SSB may also include a physical layer cell identifier (PCI) to indicate for which type of cell the SSB is configured. For example, the SSB may include or be associated with a serving cell PCI (e.g., in which case the PCI is determined from the PSS and SSS) or a non-serving cell PCI (e.g., one or more additional PCIs configured via radio resource control (RRC) signaling), and the UE uses the respective synchronization information to communicate with the corresponding serving cell or non-serving cell based on the PCI. In addition, in some cases, an SSB may overlap in time with one or more downlink channels transmitted by the same or a different cell than the cell transmitting the SSB. Techniques are desired for determining whether information about the SSB can be used to receive one or more downlink channels that overlap in time with the SSB, including one or more demodulation reference signals (DMRS).

[0039] The UE may determine whether to expect resource element overlap between the SSB and the DMRS of the downlink shared channel (e.g., physical downlink shared channel (PDSCH)) based on the association of the SSB and the downlink shared channel with the PCI. For example, if the SSB and the PDSCH are both associated with a serving cell PCI, the UE may not expect overlap between resource elements. Similarly, if the SSB and the PDSCH are both associated with a non-serving cell PCI, the UE may not expect overlap between resource elements. However, if one of the SSB or the PDSCH is associated with the serving cell and the other is associated with a non-serving cell, the UE may expect overlap between resource elements. Thus, the UE may receive an SSB including a PCI from a cell or base station and may determine overlap between resource elements carrying the SSB and resource elements in the PDSCH carrying the DMRS based on whether the PCI of the SSB and the PCI of the PDSCH are associated with a serving cell or a non-serving cell. The UE may receive the DMRS based on a determination that the resource elements of the SSB and the resource elements of the DMRS overlap or do not overlap. In some examples, the UE may determine that the PDSCH is associated with a serving cell or a non-serving cell based on a control resource set (CORESET) pool index, an indication of which the UE may receive in control signaling from a cell or base station. Additionally or alternatively, the UE may determine that the PDSCH is associated with a serving cell or a non-serving cell based on a quasi-co-location (QCL) relationship with the SSB.

[0040] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further described in the context of resource diagrams, transmission diagrams and process flows. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams and flow charts relating to resource element overlap between SSB and DMRS.

[0041] 1 illustrates an example of a wireless communication system 100 supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, a LTE-Advanced (LTE-A) network, a LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

[0042] The base stations 105 may be distributed throughout a geographic area to form a wireless communication system 100 and may be devices in different forms or with different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base stations 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 may support communication of signals via one or more radio access technologies.

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

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

[0045] One or more of the base stations 105 described herein may include or be referred to by those skilled in the art as a base transceiver station, radio base station, access point, radio transceiver, Node B, eNode B (eNB), Next Generation Node B or Giga Node B (any of which may be referred to as a gNB), Home Node B, Home eNode B, or other suitable terminology.

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

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

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

[0049] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have collection or control signaling to coordinate operation with respect to other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be arranged according to a channel raster for discovery by the UE 115. A carrier may operate in a standalone mode, where initial collection and connection may be made by the UE 115 via the carrier, or the carrier may operate in a non-standalone mode, where a connection is anchored using a different carrier (e.g., of the same or different radio access technology).

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

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

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

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

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

[0055] Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into several slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on the subcarrier spacing. Each slot may include several symbol periods (e.g., depending on the length of a cyclic prefix prepended to each symbol period). In some wireless communications systems 100, a slot may be further divided into multiple minislots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the frequency band of operation.

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

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

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

[0059] A macro cell may generally cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 115 subscribing to the service of a network provider supporting the macro cell. A small cell may be associated with a lower power base station 105 compared to a macro cell, and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 subscribing to the service of a network provider, or may provide restricted access to UEs 115 that have an association with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with a user in a home or office). A base station 105 may support one or more cells and may also support communication on one or more cells using one or more component carriers.

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

[0061] In some examples, the base stations 105 may be mobile and thus provide communication coverage to moving geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include heterogeneous networks, for example, where different types of base stations 105 provide coverage to various geographic coverage areas 110 using the same or different radio access technologies.

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

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

[0064] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception, but not simultaneous transmission and reception). In some examples, the half-duplex communication may be performed at a reduced peak rate. Other power conservation techniques for the UE 115 include entering a power-saving deep sleep mode when not engaged in active communication, operating over a limited bandwidth (e.g., in accordance with narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of the carrier, or outside of the carrier.

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

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

[0067] In some systems, the D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UE 115). In some examples, the vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. The vehicles may signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, the vehicles in the V2X system may communicate with roadside infrastructure, such as roadside units, and / or with a network via one or more network nodes (e.g., base stations 105) using vehicle-to-network (V2N) communication.

[0068] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnects to external networks. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for the UEs 115 served by the base stations 105 associated with the core network 130. User IP packets may be forwarded through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to one or more network operators' IP services 150. The IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0069] Some of the network devices, such as the base station 105, may include subcomponents, such as an access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with the UE 115 through one or more other access network transmitting entities 145, which may be referred to as a radio head, a smart radio head, or a transmit receiving point (TRP). Each access network transmitting entity 145 may include one or more antenna panels. In some configurations, various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or integrated into a single network device (e.g., the base station 105).

[0070] As described herein, a base station 105 may include components located in a single physical location or components located in various physical locations. In examples where a base station 105 includes components located in various physical locations, the various components may each perform various functions, such that, collectively, the various components achieve similar functionality as a base station 105 located in a single physical location. Thus, a base station 105 as described herein may equivalently refer to a standalone base station 105 or a base station 105 including components located in various physical locations. In some implementations, such a base station 105 including components located in various physical locations may be referred to as or associated with a disaggregated radio access network (RAN) architecture, such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture.

[0071] As used herein, the term "network entity" may refer to a standalone base station, a component of a base station (such as one of the components that are physically or logically separated to collectively implement the functionality of a base station), or another network device that communicates with or supports communication with the UE 115.

[0072] The wireless communication system 100 may typically operate using one or more frequency bands within the range of 300 megahertz (MHz) to 300 gigahertz (GHz). The 300 MHz to 3 GHz region is commonly known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range in length from approximately 1 decimeter to 1 meter. Although UHF waves may be blocked or redirected by buildings and environmental features, these waves may penetrate structures sufficiently for a macrocell to serve UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmissions using lower frequencies and longer waves in the shortwave (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0073] The wireless communication system 100 may also operate in the super high frequency (SHF) region, also known as the centimeter band, using a frequency band from 3 GHz to 30 GHz, or in the extremely high frequency (EHF) region of the spectrum, also known as the millimeter band (e.g., from 30 GHz to 300 GHz). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the base station 105, and the EHF antennas of the respective devices may be smaller and more closely spaced than the UHF antennas. In some examples, this may facilitate the use of antenna arrays within the devices. However, propagation of EHF transmissions may experience more atmospheric attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of the bands across these frequency regions may vary by country or regulatory body.

[0074] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices such as the base station 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation in an unlicensed band may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA). Operation in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0075] The base station 105 or UE 115 may be equipped with multiple antennas that may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located in one or more antenna arrays or antenna panels that may support MIMO operations or transmit or receive beamforming. For example, the antennas or antenna arrays of one or more base stations may be co-located in an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with the base station 105 may be located in diverse geographic locations. The base station 105 may have an antenna array with several rows and columns of antenna ports that the base station 105 may use to support beamforming of communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support radio frequency beamforming for signals transmitted through the antenna ports.

[0076] A base station 105 or UE 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may be transmitted by a transmitting device via different antennas or different combinations of antennas, for example. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). The different spatial layers may be associated with different antenna ports used for channel measurements and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0077] Beamforming, sometimes referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used in a transmitting or receiving device (e.g., base station 105, UE 115) to shape or steer an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated through antenna elements of an antenna array such that some signals propagating in a particular orientation relative to the antenna array are subject to constructive interference and other signals are subject to destructive interference. Adjustment of signals communicated through antenna elements may include the transmitting or receiving device applying an amplitude offset, a phase offset, or both to signals conveyed through an antenna element associated with the device. The adjustment associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device, or to some other orientation).

[0078] The base station 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform a beamforming operation for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by the base station 105 multiple times in different directions. For example, the base station 105 may transmit signals according to different beamforming weight sets associated with different directions of transmission. The transmissions in different beam directions may be used to identify beam directions (e.g., by a transmitting device such as the base station 105 or by a receiving device such as the UE 115) for subsequent transmission or reception by the base station 105.

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

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

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

[0082] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. The Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. The Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may establish, configure, and maintain an RRC connection between the UE 115 and the base station 105 or core network 130, which supports radio bearers for user plane data. In the physical layer, the transport channels may be mapped to physical channels.

[0083] The UE 115 and the base station 105 may support retransmission of data to increase the likelihood of successful reception of the data. Hybrid Automatic Repeat Request (HARQ) feedback is one technique for increasing the likelihood that data is correctly received on the communication link 125. HARQ may include a combination of error detection (e.g., using a Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which the device may provide HARQ feedback in a particular slot for data received in a previous symbol in that slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0084] In some examples, the UE 115 may monitor and receive a synchronization signal from a cell or base station 105. The UE 115 may use the synchronization signal to determine configuration and timing information for transmitting and receiving subsequent messages to and from the cell or base station 105. In some examples, the base station 105 or cell may transmit an SSB including one or more synchronization signals to the UE 115, which the UE 115 may use to determine configuration and timing information for subsequent messages. In some cases, the serving cell (e.g., the cell serving the UE 115) may have a PCI determined from the synchronization signal in an initial access procedure. A non-serving cell, or an alternative cell (e.g., other than the serving cell), may have one or more additional PCIs configured by control signaling. In some cases, such as when downlink shared channel (e.g., PDSCH) resources overlap with SSB resources in time, frequency, or both, the downlink shared channel may be rate-matched with one or more PRBs including the SSB. The UE 115 may not expect the resource elements of the DMRS of the downlink shared channel to overlap with the resource elements for the SSBs. However, if the downlink shared channel associated with the serving cell PCI is not rate-matched with one or more non-serving cell SSBs, or if the downlink shared channel associated with the non-serving cell PCI is not rate-matched with one or more serving cell SSBs, there may be interference between the SSBs and the downlink shared channel.

[0085] In some cases, the UE 115 may determine whether overlap is allowed between resource elements carrying an SSB and resource elements carrying a DMRS in a downlink shared channel (e.g., PDSCH). For example, the UE 115 may receive an SSB from the base station in one or more resource elements that includes a PCI for the serving cell or another cell. The UE 115 may also receive one or more DMRS from the base station 105 in one or more resource elements in the PDSCH. The PDSCH may be associated with a cell, such as the serving cell or another cell. For example, the PDSCH may have a PCI for the same cell as the PCI of the SSB (e.g., the same PCI) or a PCI for a cell that is different from the PCI of the SSB. The UE 115 may compare the PCI of the SSB and the PCI of the PDSCH to determine whether there is overlap in the resource elements. In some cases, the condition for whether the UE 115 may expect resource element overlap between the SSB and the DMRS of the PDSCH may be based on the association of the SSB and the PDSCH with the PCI, which will be described in more detail with respect to Figure 3. In some examples, once the UE 115 determines whether resource element overlap is allowed, the UE 115 may process the DMRS.

[0086] 2 illustrates an example of a wireless communication system 200 supporting resource element overlap between SSBs and DMRSs according to aspects of the disclosure. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100 and may include a UE 115-a and a base station 105-a with a coverage area 110-a, which may be an example of a UE 115 and a base station 105-a with a coverage area 110 as described with reference to FIG. 1. In some examples, the base station 105-a and the UE 115-a may communicate control information, data, or both using a downlink communication link 205 and an uplink communication link. For example, the base station 105-a may transmit an SSB 210 and a DMRS 215 to the UE 115-a using one or more resource elements 220, which may or may not overlap.

[0087] In some examples, the UE 115 may monitor and receive a synchronization signal from a cell or base station 105. The UE 115 may use the synchronization signal to determine configuration and timing information for transmitting and receiving subsequent messages to and from the cell or base station 105. In some examples, the base station 105 may transmit an SSB 210 (e.g., over four OFDM symbols) that includes a synchronization signal, such as a PSS, SSS, PBCH, MIB, or a combination thereof. In some cases, the base station 105 may transmit a synchronization signal in a synchronization signal burst set, which may be a set of SSBs 210 within a beam sweep (e.g., during a 5 millisecond (ms) time interval in the first or second half of a frame). The period of the synchronization signal burst set may vary (e.g., 5 ms, 10 ms, 20 ms, ... 160 ms, with a default period of 20 ms). In some examples, there may be a maximum number of SSBs 210 (e.g., 4 for sub-3 GHz, 8 for sub-7 GHz, 64 for frequency range 2 (FR2)) in a synchronization signal burst set.

[0088] In some cases, the base station 105 or cell may transmit the SSB 210 using different beams. The beams may be indexed with an SSB index (e.g., 0, 1 ... 63 for 64 SSBs). The time domain location of each SSB, such as a slot or one or more OFDM symbols, may come from a set of patterns (e.g., a set of defined or fixed patterns). The pattern may depend on the subcarrier spacing (e.g., 15 or 30 kilohertz (kHz) for Frequency Range 1 (FR1) and 120 or 240 kHz for FR2). The base station 105 may indicate the location of the SSB 210 to the UE 115. For example, the base station 105 may transmit one or more SSB indices that the base station 105 transmits as a parameter in control signaling (e.g., ssb-PositionsInBurst in a system information block (SIB) such as SIB Type 1 (SIB1) or in ServingCellConfigCommon).

[0089] In some cases, a UE 115, such as the UE 115-a, may communicate with one or more base stations 105, one or more cells, one or more transmit reception points (TRPs), or a combination thereof. In some examples, a transmission configuration indicator (TCI) state for a cell or a TRP may be defined according to QCL information configuring a reference signal. In some other examples, each cell may have a defined PCI and set of SSBs. For example, a serving cell (e.g., a cell serving the UE 115-a) may have a PCI determined from a PSS and an SSS in an initial access procedure. A non-serving cell, or an alternative cell (e.g., other than the serving cell), may have one or more additional PCIs configured by control signaling. In some cases, the base station 105-a may configure one or more cells with PCIs via RRC signaling. The base station 105 may configure an SSB set for the UE 115 associated with an RRC configured PCI (e.g., a PCI for a non-serving cell). If there are multiple PCIs for non-serving cells, the base station 105 may configure multiple SSB sets.

[0090] In some cases, a non-serving PCI or SSB 210 may define TCI state or QCL information based on an SSB index from a set of SSBs 210 associated with a neighboring PCI (e.g., a neighboring cell). A TCI state (e.g., PDSCH TCI state, PDCCH TCI state, or both) associated with a different PCI may be indirectly QCLed with an SSB 210 associated with that PCI. For example, in a multi-TRP transmission scenario, the secondary TRP may have a different PCI (e.g., inter-cell multi-TRP). In some other examples, such as in the case of a multi-TRP transmission scenario with multiple control messages (e.g., downlink control information (DCI) messages), the base station 105 may configure multiple CORESET pool index values ​​for different CORESETs.

[0091] In some cases, such as in the case of inter-cell multi-TRP operation, the UE 115 and base station 105 may support an additional PCI that may be different from the serving cell PCI for each component carrier. The additional PCI may be associated with one or more activated TCI states for a reference signal (e.g., CSI-RS of CSI), a downlink shared channel, a downlink control channel, or a combination thereof for each component carrier, such as in the case of a scenario with a non-cross-carrier QCL indication. In some examples, the base station 105 and UE 115 may determine non-serving cell SSB information. For example, the information may include (e.g., according to an implicit or explicit indication) SSB time domain position, SSB transmission periodicity, SSB transmit power, other non-serving cell information, etc.

[0092] In some cases, such as when downlink shared channel (e.g., PDSCH 225) resources overlap with SSB resources in time, frequency, or both, the downlink shared channel may be rate-matched with one or more PRBs including the SSB 210. That is, the PRB may not be available for the downlink shared channel. One or more SSBs 210 may be considered for rate-matching according to one or more parameters such as ssb-PositionsInBurst (e.g., one or more of the 64 SSBs 210). The UE 115 may not expect that resource elements of the DMRS 215 of the downlink shared channel overlap with resource elements for the SSB 210 (e.g., the rate-matching may be for data tones). In some examples, such as in the case of an inter-cell multi-TRP transmission scenario, one or more downlink shared channels associated with the serving cell PCI may not be rate-matched with the serving cell SSB 210. In some other examples, one or more downlink shared channels associated with other non-serving cell PCIs may be rate-matched with the non-serving cell SSB 210. However, if a downlink shared channel associated with a serving cell PCI is not rate-matched with one or more non-serving cell SSB210, or if a downlink shared channel associated with a non-serving cell PCI is not rate-matched with one or more serving cell SSB210, there may be interference between the SSB210 and the downlink shared channel.

[0093] In some examples, such as when the base station 105 performs rate matching, the resource elements may not overlap with the DMRS 215. For example, rate matching may be applicable to the data tones (e.g., data tones other than the DMRS tones may be rate matched, but there may be no overlap with the DMRS tones). In some other examples, such as when the base station 105 does not perform rate matching, there may be interference on the data tones (e.g., from the SSB 210 of another TRP). Thus, it may be acceptable for the DMRS tones to experience similar interference (e.g., overlap may be allowed because there may be interference on the data tones on the overlapping PRB). The base station 105 may benefit from taking into account conditions under which the resource elements do not overlap with the DMRS 215. For example, the base station 105 may consider whether the overlapping downlink shared channel is associated with the serving cell or another non-serving cell. Additionally or alternatively, the base station 105 may consider whether the overlapping SSB 210 is associated with the serving cell or another non-serving cell.

[0094] In some cases, the UE 115 may determine whether overlap is allowed between resource elements 220 carrying the SSB 210 and resource elements 220 carrying the DMRS 215 in a downlink shared channel (e.g., PDSCH 225). For example, the UE 115-a may receive the SSB 210 in one or more resource elements 220 from the base station 105-a via the downlink communication link 205. The SSB may include a PCI for a serving cell or for another cell, which may be a non-serving cell. The UE 115-a may also receive one or more DMRSs 215 from the base station 105-a in one or more resource elements 220 in the PDSCH 225. The PDSCH 225 may be associated with a cell, such as the serving cell or another cell. For example, the PDSCH 225 may have a PCI for the same cell as the PCI of the SSB 210 (e.g., the same PCI) or a PCI for a cell that is different from the PCI of the SSB. At 230, the UE 115-a may compare the PCI of the SSB 210 and the PCI of the PDSCH 225 to determine whether there is an overlap in the resource elements 220. In some cases, the condition for whether the UE 115-a may expect an overlap in the resource elements 220 between the SSB 210 and the DMRS 215 of the PDSCH 225 may be based on an association of the SSB 210 and the PDSCH 225 with the PCI, which will be described in more detail with respect to FIG.

[0095] In some examples, the UE 115-a may determine whether the PDSCH 225 is associated with the serving cell PCI or another PCI, such as a non-serving cell PCI, based on the control message 235. For example, the UE 115-a may receive the control message 235 from the base station 105-a via the downlink communication link 205. The UE 115-a may identify a CORESET pool index value for the PDSCH 225 based on the control message 235. In some cases, the control message 235 may dynamically schedule the PDSCH 225 (e.g., via a DCI message). The UE 115-a may identify a CORESET pool index value based on a CORESET pool index value of a CORESET in which the UE 115-a receives a scheduling DCI. In some other cases, the control message 235 may semi-persistently schedule (SPS) the PDSCH 225. The UE 115-a may identify the CORESET pool index value based on a CORESET pool index value of a CORESET in which the UE 115-a receives an activation DCI. Additionally or alternatively, the UE 115-a may identify the CORESET pool index value based on a CORESET pool index value for an SPS configuration. The base station 105-a may RRC configure an SPS configuration with a CORESET pool index value of 0 or 1. In some cases, if the CORESET pool index value is 0, the PDSCH 225 may be associated with the serving cell. In some other cases, if the CORESET pool index value is 1, the PDSCH 225 may be associated with another cell, such as a non-serving cell.

[0096] In some other examples, the UE 115-a may determine whether the PDSCH 225 is associated with the serving cell PCI or another PCI, such as a non-serving cell PCI, based on an indirect QCL relationship, such as a top QCL chain, which will be described in more detail with respect to FIG. 4. In some examples, once the UE 115-a has determined whether resource element overlap is allowed, the UE 115-a may process the DMRS 215.

[0097] 3 illustrates an example of a resource diagram 300 supporting resource element overlap between an SSB and a DMRS according to an aspect of the disclosure. In some examples, the resource diagram 300 may implement aspects of the wireless communication system 100 and the wireless communication system 200. For example, the resource diagram 300 may be implemented by the UE 115 and the base station 105 as described with reference to FIGS. 1 and 2. In some cases, the base station may transmit an SSB 305 and a DMRS 310 in a downlink shared channel to the UE. Resource elements of the SSB 305 and the DMRS 310 may overlap according to whether resource element overlap is allowed at the UE.

[0098] In some examples, the UE may determine whether to expect resource element overlap between the SSB 305 and the DMRS 310 of a downlink shared channel (e.g., the PDSCH 315). For example, the SSB 305 may be associated with a PCI for the cell 320-a, which may be a serving cell PCI, or a PCI for another cell 320-b, such as a non-serving cell PCI. Similarly, the PDSCH 315, which includes the DMRS 310, may be associated with the PCI for the cell 320-a or the PCI for the cell 320-b. The UE may expect resource element overlap based on the association of the SSB 305 with the serving cell PCI or the non-serving cell PCI and the association of the PDSCH 315 with the serving cell PCI or the non-serving cell PCI.

[0099] In some examples, there may be resource element overlap between the SSB 305 associated with a PCI for the cell 320-a, such as a serving cell PCI, and the PDSCH 315 associated with the PCI for the cell 320-a, at 325. The UE may not anticipate overlap between the resource elements for the DMRS 310 of the PDSCH 315 and the resource elements of the SSB 305.

[0100] In some other examples, there may be resource element overlap between the SSB 305 associated with a PCI for the cell 320-b, such as a non-serving cell PCI, and the PDSCH 315 associated with the PCI for the cell 320-b, at 330. The UE may not expect overlap between the resource elements for the DMRS 310 of the PDSCH 315 and the resource elements of the SSB 305.

[0101] In some other examples, there may be resource element overlap between the SSB 305 associated with a PCI for the cell 320-a, such as a serving cell PCI, and the PDSCH 315 associated with a PCI for the cell 320-b, which may be a non-serving cell PCI, at 335. The UE may expect overlap between resource elements for the DMRS 310 of the PDSCH 315 and resource elements of the SSB 305.

[0102] In some other examples, there may be resource element overlap between the SSB 305 associated with a PCI for the cell 320-b, such as a non-serving cell PCI, and the PDSCH 315 associated with a PCI for the cell 320-a, such as the serving cell PCI, at 340. The UE may expect overlap between resource elements for the DMRS 310 of the PDSCH 315 and resource elements of the SSB 305.

[0103] 4 illustrates an example of a transmission diagram 400 supporting resource element overlap between SSB and DMRS according to aspects of the disclosure. In some examples, the transmission diagram 400 may implement aspects of the wireless communication system 100, the wireless communication system 200, and the resource diagram 300. For example, the transmission diagram 400 may be implemented by the UE 115 and the base station 105 as described with reference to FIG. 1 and FIG. 2. In some cases, the base station may transmit the SSB and the DMRS in the downlink shared channel to the UE. The resource elements of the SSB and the DMRS may overlap according to whether the downlink shared channel is associated with the serving cell PCI or another PCI, such as a non-serving cell PCI.

[0104] In some examples, the UE may determine whether a downlink shared channel (e.g., PDSCH) is associated with the serving cell PCI or another PCI for a different cell based on an indirect QCL relationship such as the top QCL chain 405. In some cases, the TCI state or QCL assumption for the PDSCH may be based on the CSI-RS or a tracking reference signal (TRS). The CSI-RS or TRS may be directly or indirectly QCLed with the SSB. For example, for QCL chain 405-a, at 410, the SSB may be QCLed with the CSI-RS associated with the TRS at 415, the CSI-RS at 420, and finally the PDSCH at 425. Similarly, for QCL chain 405-b, at 430, the SSB may be QCLed with the CSI-RS associated with the TRS at 435, and the PDSCH at 440. In some cases, if the SSB in the top QCL chain of the PDSCH is associated with the serving cell PCI, the PDSCH may also be associated with the serving cell PCI. In some other cases, if the SSB in the top QCL chain of the PDSCH is associated with another PCI, such as a non-serving cell PCI, the PDSCH may also be associated with another PCI.

[0105] FIG. 5 illustrates an example of a process flow 500 supporting resource element overlap between SSB and DMRS according to aspects of the disclosure. In some examples, the process flow 500 may implement aspects of the wireless communication system 100, the wireless communication system 200, the resource diagram 300, and the transmission diagram 400. The process flow 500 may illustrate an example in which the UE 115-b determines whether overlap is allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS on a downlink shared channel from the base station 105-b. The following alternative examples may be implemented, in which some processes are performed in a different order than described or are not performed. In some cases, the process may include additional features not mentioned below or additional processes may be added.

[0106] At 505, the base station 105-b may transmit a control message to the UE 115-b. For example, the base station 105-b may transmit a dynamic control message, such as a DCI message, or an SPS control message, such as an RRC configuration or MAC-CE with an activation DCI. In some examples, the UE 115-b may receive a control message according to a CORESET, which may have a CORESET pool index value. For example, the control message may be an SPS control message with an activation DCI message received in a CORESET with a CORESET pool index value. In some other examples, the control message may be an SPS control message with an SPS configuration in an RRC message, where the SPS configuration indicates a CORESET pool index value.

[0107] At 510, the UE 115-b may receive an SSB having a PCI, such as a PCI for the serving cell or another cell (e.g., a non-serving cell). In some cases, one or more resource elements carrying the SSB may overlap with one or more resource elements carrying a downlink shared channel, such as a PDSCH 515, having a different PCI.

[0108] The UE 115-b may receive one or more DMRSs from the base station 105-b, at 520. For example, the UE 115-b may receive the DMRS in a downlink shared channel, such as the PDSCH 515.

[0109] At 525, the UE 115-b may determine whether a PCI of a downlink shared channel, such as a PCI of the PDSCH 515, is for a serving cell or for another cell, such as a non-serving cell. In some cases, if the UE 115-b receives a scheduling DCI in a CORESET having a CORESET pool index value, the UE 115-b may use that CORESET pool index value to determine whether the downlink shared channel has a PCI associated with the serving cell or has a PCI associated with another cell. For example, the UE 115-b may determine that the downlink shared channel may be for the serving cell based on the CORESET pool index value being 0. In some other examples, the UE 115-b may determine that the downlink shared channel may be for another cell (e.g., a non-serving cell) based on the CORESET pool index value being 1.

[0110] In some cases, UE 115-b may determine that the downlink shared channel may be associated with the serving cell or another cell (e.g., a non-serving cell) based on the QCL relationship of the SSB being associated with the serving cell or another cell, respectively.

[0111] At 530, the UE 115-b may compare the PCI of the SSB and the PCI of the PDSCH with the DMRS to determine whether resource element overlap is allowed. For example, the UE 115-b may determine whether overlap is allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS in the downlink shared channel.

[0112] In some examples, the UE 115-b may determine that resource element overlap is not allowed at 535. For example, the UE 115-b may determine that overlap is not allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on both PCIs being for a serving cell or for another cell, such as a non-serving cell.

[0113] In some other examples, the UE 115-b may determine that resource element overlap is allowed at 540. For example, the UE 115-b may determine that overlap is allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on at least one of the PCIs being for the serving cell and the other PCI being for another cell.

[0114] At 545, the UE 115-b may process the DMRS based on determining at 530 whether resource element overlap is allowed.

[0115] 6 illustrates a block diagram 600 of a device 605 supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The device 605 may be an example of an aspect of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

[0116] The receiver 610 may provide a means for receiving information, such as packets, user data, control information, or any combination thereof, associated with various traffic channels (e.g., control channels, data channels, traffic channels related to resource element overlap between SSB and DMRS). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

[0117] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various traffic channels (e.g., control channels, data channels, traffic channels related to resource element overlap between SSB and DMRS). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0118] The communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be examples of means for performing various aspects of resource element overlap between SSB and DMRS as described herein. For example, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0119] In some examples, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing functions described in this disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0120] Additionally or alternatively, in some examples, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software or firmware). When implemented in code executed by a processor, the functions of the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in this disclosure).

[0121] In some examples, the communications manager 620 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to receive information, transmit information, or perform various other operations as described herein.

[0122] The communications manager 620 may support wireless communications in a UE according to examples as disclosed herein. For example, the communications manager 620 may be configured with or otherwise support a means for receiving an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The communications manager 620 may be configured with or otherwise support a means for determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel. The communications manager 620 may be configured with or otherwise support a means for processing the DMRS based on the determination.

[0123] By including or configuring the communications manager 620 according to examples as described herein, the device 605 (e.g., a processor controlling or possibly coupled to the receiver 610, the transmitter 615, the communications manager 620, or a combination thereof) can support techniques for the UE 115 to determine whether overlap is allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS on the downlink shared channel, which can result in reduced processing, reduced power consumption, more efficient utilization of communications resources, etc.

[0124] 7 illustrates a block diagram 700 of a device 705 supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The device 705 may be an example of an aspect of a device 605 or a UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. The device 705 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

[0125] The receiver 710 may provide a means for receiving information, such as packets, user data, control information, or any combination thereof, associated with various traffic channels (e.g., control channels, data channels, traffic channels related to resource element overlap between SSB and DMRS). The information may be passed to other components of the device 705. The receiver 710 may utilize a single antenna or a set of multiple antennas.

[0126] The transmitter 715 may provide a means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets, user data, control information, or any combination thereof associated with various traffic channels (e.g., control channels, data channels, traffic channels related to resource element overlap between SSB and DMRS). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.

[0127] The device 705, or various components thereof, may be an example of a means for performing various aspects of resource element overlap between SSB and DMRS as described herein. For example, the communications manager 720 may include an SSB component 725, a PCI component 730, a DMRS component 735, or any combination thereof. The communications manager 720 may be an example of an aspect of a communications manager 620 as described herein. In some examples, the communications manager 720 or various components thereof may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communications manager 720 may receive information from the receiver 710, send information to the transmitter 715, or be integrated in combination with the receiver 710, the transmitter 715, or both to receive information, transmit information, or perform various other operations as described herein.

[0128] The communications manager 720 may support wireless communications in a UE according to examples as disclosed herein. The SSB component 725 may be configured as, or otherwise support, a means for receiving an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The PCI component 730 may be configured as, or otherwise support, a means for determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel. The DMRS component 735 may be configured as, or otherwise support, a means for processing the DMRS based on the determination.

[0129] FIG. 8 illustrates a block diagram 800 of a communications manager 820 supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. Communications manager 820 may be an example of an aspect of communications manager 620, communications manager 720, or both, as described herein. Communications manager 820, or various components thereof, may be an example of a means for implementing various aspects of resource element overlap between SSB and DMRS as described herein. For example, communications manager 820 may include an SSB component 825, a PCI component 830, a DMRS component 835, a control message component 840, a QCL component 845, or any combination thereof. Each of these components may communicate with one another directly or indirectly (e.g., via one or more buses).

[0130] The communications manager 820 may support wireless communications in the UE according to examples as disclosed herein. The SSB component 825 may be configured as, or otherwise support, a means for receiving an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The PCI component 830 may be configured as, or otherwise support, a means for determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel. The DMRS component 835 may be configured as, or otherwise support, a means for processing the DMRS based on the determination.

[0131] In some examples, to support determining whether overlap is allowed, the PCI component 830 may be configured with or otherwise support a means for determining that overlap is not allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI and the second PCI corresponding to a serving cell.

[0132] In some examples, to support determining whether overlap is allowed, the PCI component 830 may be configured with or otherwise support a means for determining that overlap is not allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI and the second PCI being the same PCI.

[0133] In some examples, to support determining whether overlap is allowed, the PCI component 830 may be configured with or otherwise support a means for determining that overlap is not allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI and the second PCI corresponding to the second cell.

[0134] In some examples, to support determining whether overlap is allowed, the PCI component 830 may be configured with or otherwise support a means for determining that overlap is allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI corresponding to a serving cell and the second PCI corresponding to a second cell.

[0135] In some examples, to support determining whether overlap is allowed, the PCI component 830 may be configured as or otherwise support a means for determining that overlap is allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI corresponding to the second cell and the second PCI corresponding to the serving cell.

[0136] In some examples, the control message component 840 may be configured with or otherwise support a means for receiving a control message corresponding to a CORESET pool index value corresponding to a downlink shared channel, the control message including a scheduling DCI message.

[0137] In some examples, the control message component 840 may be configured as or otherwise support a means for determining that a downlink shared channel is associated with a serving cell based on the CORESET pool index value having a value of 0.

[0138] In some examples, the control message component 840 may be configured as or otherwise support a means for determining that the downlink shared channel is associated with the second cell based on the CORESET pool index value having a value of one.

[0139] In some examples, the control message is an SPS control message corresponding to an activation DCI message received in a CORESET associated with the CORESET pool index value.

[0140] In some examples, the control message is an SPS control message corresponding to an SPS configuration in the RRC message, the SPS configuration indicating a CORESET pool index value.

[0141] In some examples, the QCL component 845 may be configured as or otherwise support a means for determining that a downlink shared channel is associated with a serving cell based on a QCL relationship corresponding to the SSB being associated with the serving cell.

[0142] In some examples, the QCL component 845 may be configured as or otherwise support a means for determining that the downlink shared channel is associated with a second cell based on a QCL relationship corresponding to the SSB being associated with the second cell.

[0143] FIG. 9 illustrates a diagram of a system 900 including a device 905 supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The device 905 may be an example of or may include components of a device 605, a device 705, or a UE 115 as described herein. The device 905 may wirelessly communicate with one or more base stations 105, UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communication, including components for transmitting and receiving communications, such as a communications manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, code 935, and a processor 940. These components may be in electronic communication or may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) in some cases via one or more buses (e.g., a bus 945).

[0144] The I / O controller 910 may manage input and output signals for the device 905. The I / O controller 910 may also manage peripheral devices that are not integrated into the device 905. In some cases, the I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 910 may utilize an operating system, such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 910 may be implemented as part of a processor, such as the processor 940. In some cases, a user may interact with the device 905 through the I / O controller 910 or through hardware components controlled by the I / O controller 910.

[0145] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have two or more antennas 925 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, wired links, or wireless links as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets and providing the modulated packets to one or more antennas 925 for transmission and demodulating packets received from the one or more antennas 925. The transceiver 915, or the transceiver 915 and one or more antennas 925, may be an example of a transmitter 615, a transmitter 715, a receiver 610, a receiver 710, or any combination or components thereof as described herein.

[0146] The memory 930 may include random access memory (RAM) and read only memory (ROM). The memory 930 may store computer-readable computer-executable code 935 that includes instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some cases, the code 935 may not be directly executable by the processor 940, but may (e.g., when compiled and executed) cause a computer to perform functions described herein. In some cases, the memory 930 may include a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0147] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting resource element overlap between SSB and DMRS). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to the processor 940, where the processor 940 and the memory 930 are configured to perform various functions described herein.

[0148] The communications manager 920 may support wireless communications in a UE according to examples as disclosed herein. For example, the communications manager 920 may be configured with or otherwise support a means for receiving an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The communications manager 920 may be configured with or otherwise support a means for determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel. The communications manager 920 may be configured with or otherwise support a means for processing the DMRS based on the determination.

[0149] By including or configuring a communications manager 920 according to examples as described herein, the device 905 can support techniques for the UE 115 to determine whether overlap is allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS on the downlink shared channel, which can result in improved communications reliability, reduced latency, an improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communications resources, improved coordination between devices, longer battery life, improved utilization of processing power, and the like.

[0150] In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the transceiver 915, the one or more antennas 925, or any combination thereof. Although the communications manager 920 is shown as a separate component, in some examples, one or more functions described with reference to the communications manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions executable by the processor 940 to cause the device 905 to perform various aspects of resource element overlap between SSB and DMRS as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0151] 10 illustrates a block diagram 1000 of a device 1005 supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The device 1005 may be an example of a network entity implementing one or more aspects of a base station 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

[0152] The receiver 1010 may provide a means for receiving information, such as packets, user data, control information, or any combination thereof, associated with various traffic channels (e.g., control channels, data channels, traffic channels related to resource element overlap between SSB and DMRS). The information may be passed to other components of the device 1005. The receiver 1010 may utilize a single antenna or a set of multiple antennas.

[0153] The transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various traffic channels (e.g., control channels, data channels, traffic channels related to resource element overlap between SSB and DMRS). In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a set of multiple antennas.

[0154] The communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be examples of means for performing various aspects of resource element overlap between SSB and DMRS as described herein. For example, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0155] In some examples, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit). The hardware may include a processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing functions described in this disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0156] Additionally or alternatively, in some examples, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software or firmware). When implemented in code executed by a processor, the functions of the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in this disclosure).

[0157] In some examples, the communications manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to receive information, transmit information, or perform various other operations as described herein.

[0158] The communications manager 1020 may support wireless communications in a network entity implementing one or more aspects of a base station according to examples as disclosed herein. For example, the communications manager 1020 may be configured as or otherwise support a means for transmitting an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The communications manager 1020 may be configured as or otherwise support a means for determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel. The communications manager 1020 may be configured as or otherwise support a means for processing the DMRS based on the determination.

[0159] By including or configuring the communications manager 1020 according to examples as described herein, the device 1005 (e.g., a processor controlling or possibly coupled to the receiver 1010, the transmitter 1015, the communications manager 1020, or a combination thereof) can support techniques for the UE 115 to determine whether overlap is allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS on the downlink shared channel, which can result in reduced processing, reduced power consumption, more efficient utilization of communications resources, etc.

[0160] 11 illustrates a block diagram 1100 of a device 1105 supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The device 1105 may be an example of an aspect of the device 1005 or one or more aspects of a base station 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. The device 1105 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

[0161] The receiver 1110 may provide a means for receiving information, such as packets, user data, control information, or any combination thereof, associated with various traffic channels (e.g., control channels, data channels, traffic channels related to resource element overlap between SSB and DMRS). The information may be passed to other components of the device 1105. The receiver 1110 may utilize a single antenna or a set of multiple antennas.

[0162] The transmitter 1115 may provide a means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information such as packets, user data, control information, or any combination thereof associated with various traffic channels (e.g., control channels, data channels, traffic channels related to resource element overlap between SSB and DMRS). In some examples, the transmitter 1115 may be co-located with the receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a set of multiple antennas.

[0163] The device 1105, or various components thereof, may be an example of a means for performing various aspects of resource element overlap between SSB and DMRS as described herein. For example, the communications manager 1120 may include an SSB manager 1125, a PCI manager 1130, a DMRS manager 1135, or any combination thereof. The communications manager 1120 may be an example of an aspect of the communications manager 1020 as described herein. In some examples, the communications manager 1120, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the receiver 1110, the transmitter 1115, or both. For example, the communications manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or be integrated in combination with the receiver 1110, the transmitter 1115, or both to receive information, transmit information, or perform various other operations as described herein.

[0164] The communications manager 1120 may support wireless communications in a network entity implementing one or more aspects of a base station according to examples as disclosed herein. The SSB manager 1125 may be configured as, or otherwise support, a means for transmitting an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The PCI manager 1130 may be configured as, or otherwise support, a means for determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel. The DMRS manager 1135 may be configured as, or otherwise support, a means for processing the DMRS based on the determination.

[0165] FIG. 12 illustrates a block diagram 1200 of a communications manager 1220 supporting resource element overlap between an SSB and a DMRS according to an aspect of the disclosure. The communications manager 1220 may be an example of an aspect of the communications manager 1020, the communications manager 1120, or both, as described herein. The communications manager 1220, or various components thereof, may be an example of a means for implementing various aspects of resource element overlap between an SSB and a DMRS, as described herein. For example, the communications manager 1220 may include an SSB manager 1225, a PCI manager 1230, a DMRS manager 1235, a control message manager 1240, a QCL manager 1245, or any combination thereof. Each of these components may communicate with one another directly or indirectly (e.g., via one or more buses).

[0166] The communications manager 1220 may support wireless communications in a network entity implementing one or more aspects of a base station according to examples as disclosed herein. The SSB manager 1225 may be configured as, or otherwise support, a means for transmitting an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The PCI manager 1230 may be configured as, or otherwise support, a means for determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel. The DMRS manager 1235 may be configured as, or otherwise support, a means for processing the DMRS based on the determination.

[0167] In some examples, the PCI manager 1230 may be configured with or otherwise support a means for determining that there is no overlap between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI and the second PCI corresponding to a serving cell.

[0168] In some examples, the PCI manager 1230 may be configured with or otherwise support a means for determining that there is no overlap between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI and the second PCI being the same PCI.

[0169] In some examples, the PCI manager 1230 may be configured with or otherwise support a means for determining that there is no overlap between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI and the second PCI corresponding to the second cell.

[0170] In some examples, the PCI manager 1230 may be configured with or otherwise support a means for determining that one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS overlap based on the first PCI corresponding to a serving cell and the second PCI corresponding to a second cell.

[0171] In some examples, the PCI manager 1230 may be configured with or otherwise support a means for determining that one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS overlap based on the first PCI corresponding to the second cell and the second PCI corresponding to the serving cell.

[0172] In some examples, the control message manager 1240 may be configured with or otherwise support a means for transmitting a control message indicating a CORESET pool index value corresponding to a downlink shared channel.

[0173] In some examples, the control message manager 1240 may be configured with or otherwise support a means for determining that a downlink shared channel is associated with a serving cell based on the CORESET pool index value having a value of 0.

[0174] In some examples, the control message manager 1240 may be configured with or otherwise support a means for determining that the downlink shared channel is associated with the second cell based on the CORESET pool index value having a value of one.

[0175] In some examples, the control message is an SPS control message corresponding to an activation DCI message received in a CORESET associated with the CORESET pool index value.

[0176] In some examples, the control message is an SPS control message corresponding to an SPS configuration in the RRC message, the SPS configuration indicating a CORESET pool index value.

[0177] In some examples, the QCL manager 1245 may be configured as or otherwise support a means for determining that a downlink shared channel is associated with a serving cell based on a QCL relationship corresponding to the SSB being associated with the serving cell.

[0178] In some examples, the QCL manager 1245 may be configured as or otherwise support a means for determining that a downlink shared channel is associated with a second cell based on a QCL relationship corresponding to the SSB being associated with the second cell.

[0179] FIG. 13 illustrates a diagram of a system 1300 including a device 1305 supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The device 1305 may be an example of or may include a device 1005, device 1105, or a component of a network entity implementing one or more aspects of a base station 105 as described herein. The device 1305 may wirelessly communicate with one or more base stations 105, UEs 115, or any combination thereof. The device 1305 may include components for two-way voice and data communication, including components for transmitting and receiving communications, such as a communications manager 1320, a network communications manager 1310, a transceiver 1315, an antenna 1325, a memory 1330, code 1335, a processor 1340, and an inter-station communications manager 1345. These components may be in electronic communication or may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) possibly via one or more buses (e.g., a bus 1350).

[0180] The network communications manager 1310 may manage communications with the core network 130 (e.g., via one or more wired backhaul links). For example, the network communications manager 1310 may manage the transfer of data communications for client devices, such as one or more UEs 115.

[0181] In some cases, the device 1305 may include a single antenna 1325. However, in some other cases, the device 1305 may have two or more antennas 1325 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 1315 may communicate bidirectionally via one or more antennas 1325, wired links, or wireless links as described herein. For example, the transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1315 may also include a modem for modulating packets and providing the modulated packets to one or more antennas 1325 for transmission and demodulating packets received from the one or more antennas 1325. The transceiver 1315, or the transceiver 1315 and one or more antennas 1325, may be an example of the transmitter 1015, the transmitter 1115, the receiver 1010, the receiver 1110, or any combination or components thereof as described herein.

[0182] The memory 1330 may include RAM and ROM. The memory 1330 may store computer-readable computer-executable code 1335 including instructions that, when executed by the processor 1340, cause the device 1305 to perform various functions described herein. The code 1335 may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some cases, the code 1335 may not be directly executable by the processor 1340, but may (e.g., when compiled and executed) cause the computer to perform functions described herein. In some cases, the memory 1330 may include a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0183] The processor 1340 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1340 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1340. The processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause the device 1305 to perform various functions (e.g., functions or tasks supporting resource element overlap between SSB and DMRS). For example, the device 1305 or a component of the device 1305 may include a processor 1340 and a memory 1330 coupled to the processor 1340, where the processor 1340 and the memory 1330 are configured to perform various functions described herein.

[0184] The inter-station communications manager 1345 may manage communications with other base stations 105 and may include a controller or scheduler for controlling communications with the UE 115 in cooperation with the other base stations 105. For example, the inter-station communications manager 1345 may coordinate scheduling for transmissions to the UE 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, the inter-station communications manager 1345 may provide an X2 interface in LTE / LTE-A wireless communications network technology to communicate between the base stations 105.

[0185] The communications manager 1320 may support wireless communications in a network entity implementing one or more aspects of a base station according to examples as disclosed herein. For example, the communications manager 1320 may be configured as or otherwise support a means for transmitting an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The communications manager 1320 may be configured as or otherwise support a means for determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel. The communications manager 1320 may be configured as or otherwise support a means for processing the DMRS based on the determination.

[0186] By including or configuring the communications manager 1320 according to examples as described herein, the device 1305 can support techniques for the UE 115 to determine whether overlap is allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS on the downlink shared channel, which can result in improved communications reliability, reduced latency, an improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communications resources, improved coordination between devices, longer battery life, improved utilization of processing power, and the like.

[0187] In some examples, the communications manager 1320 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the transceiver 1315, the one or more antennas 1325, or any combination thereof. Although the communications manager 1320 is shown as a separate component, in some examples, one or more functions described with reference to the communications manager 1320 may be supported or performed by the processor 1340, the memory 1330, the code 1335, or any combination thereof. For example, the code 1335 may include instructions executable by the processor 1340 to cause the device 1305 to perform various aspects of resource element overlap between SSB and DMRS as described herein, or the processor 1340 and the memory 1330 may be otherwise configured to perform or support such operations.

[0188] FIG. 14 illustrates a flow chart illustrating a method 1400 for supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The operations of the method 1400 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1400 may be performed by the UE 115 as described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using dedicated hardware.

[0189] At 1405, the method may include receiving an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by an SSB component 825 as described with reference to FIG.

[0190] At 1410, the method may include determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS corresponding to the downlink shared channel. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a PCI component 830 as described with reference to FIG.

[0191] At 1415, the method may include processing the DMRS based on the determination. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by the DMRS component 835 as described with reference to FIG.

[0192] FIG. 15 illustrates a flow chart illustrating a method 1500 for supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The operations of method 1500 may be implemented by a UE or components thereof as described herein. For example, the operations of method 1500 may be performed by a UE 115 as described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using dedicated hardware.

[0193] At 1505, the method may include receiving an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by an SSB component 825 as described with reference to FIG.

[0194] At 1510, the method may include determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS corresponding to the downlink shared channel. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a PCI component 830 as described with reference to FIG.

[0195] At 1515, the method may include determining that no overlap is allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS based on the first PCI and the second PCI corresponding to or being the same as the serving cell. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by a PCI component 830 as described with reference to FIG.

[0196] At 1520, the method may include processing the DMRS based on the determination. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed by the DMRS component 835 as described with reference to FIG.

[0197] FIG. 16 illustrates a flow chart illustrating a method 1600 for supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The operations of the method 1600 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1600 may be performed by a UE 115 as described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using dedicated hardware.

[0198] At 1605, the method may include receiving an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by an SSB component 825 as described with reference to FIG.

[0199] At 1610, the method may include determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS corresponding to the downlink shared channel. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a PCI component 830 as described with reference to FIG.

[0200] At 1615, the method may include determining, based on the first PCI and the second PCI corresponding to the second cell, that overlap is not allowed between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed by a PCI component 830 as described with reference to FIG.

[0201] At 1620, the method may include processing the DMRS based on the determination. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed by the DMRS component 835 as described with reference to FIG.

[0202] FIG. 17 illustrates a flow chart illustrating a method 1700 for supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The operations of the method 1700 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1700 may be performed by the UE 115 as described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using dedicated hardware.

[0203] At 1705, the method may include receiving an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by an SSB component 825 as described with reference to FIG.

[0204] At 1710, the method may include determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS corresponding to the downlink shared channel. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a PCI component 830 as described with reference to FIG.

[0205] At 1715, the method may include determining that overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS based on the first PCI corresponding to the serving cell and the second PCI corresponding to the second cell. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by a PCI component 830 as described with reference to FIG.

[0206] At 1720, the method may include processing the DMRS based on the determination. The operations of 1720 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed by the DMRS component 835 as described with reference to FIG.

[0207] FIG. 18 illustrates a flow chart illustrating a method 1800 for supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The operations of the method 1800 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1800 may be performed by the UE 115 as described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using dedicated hardware.

[0208] At 1805, the method may include receiving an SSB associated with a first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with a second PCI. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by an SSB component 825 as described with reference to FIG.

[0209] At 1810, the method may include determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by a PCI component 830 as described with reference to FIG.

[0210] At 1815, the method may include determining that overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS based on the first PCI corresponding to the second cell and the second PCI corresponding to the serving cell. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by a PCI component 830 as described with reference to FIG.

[0211] At 1820, the method may include processing the DMRS based on the determination. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed by the DMRS component 835 as described with reference to FIG.

[0212] FIG. 19 illustrates a flow chart illustrating a method 1900 for supporting resource element overlap between SSB and DMRS according to an aspect of the disclosure. The operations of the method 1900 may be implemented by a network entity implementing one or more aspects of a base station or components thereof as described herein. For example, the operations of the method 1900 may be performed by a base station 105 as described with reference to FIGS. 1-5 and 10-13. In some examples, the base station may execute a set of instructions to control functional elements of the base station to perform the described functions. Additionally or alternatively, the base station may perform aspects of the described functions using dedicated hardware.

[0213] At 1905, the method may include transmitting an SSB associated with the first PCI, where one or more resource elements carrying the SSB overlap with one or more resource elements carrying a downlink shared channel associated with the second PCI. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed by an SSB manager 1225 as described with reference to FIG.

[0214] At 1910, the method may include determining, according to a comparison of the first PCI and the second PCI, whether overlap is allowed between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS corresponding to the downlink shared channel. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by a PCI manager 1230 as described with reference to FIG.

[0215] At 1915, the method may include processing the DMRS based on the determination. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed by the DMRS manager 1235 as described with reference to FIG.

[0216] The following provides a summary of aspects of the disclosure.

[0217] Aspect 1: A method for wireless communications in a UE, comprising: receiving a synchronization signal block associated with a first physical layer cell identifier, wherein one or more resource elements carrying the synchronization signal block overlap with one or more resource elements carrying a downlink shared channel associated with a second physical layer cell identifier; determining, according to a comparison of the first physical layer cell identifier and the second physical layer cell identifier, whether overlap is allowed between the one or more resource elements carrying the synchronization signal block and one or more resource elements carrying a demodulation reference signal corresponding to the downlink shared channel; and processing the demodulation reference signal based at least in part on the determination.

[0218] Aspect 2: The method of aspect 1, wherein the step of determining whether overlap is allowed includes determining that overlap is not allowed between one or more resource elements carrying a synchronization signal block and one or more resource elements carrying a demodulation reference signal based at least in part on the first physical layer cell identifier and the second physical layer cell identifier being the same physical layer cell identifier.

[0219] Aspect 3: The method of aspect 1, wherein the step of determining whether overlap is allowed includes determining that overlap is not allowed between one or more resource elements carrying the synchronization signal block and one or more resource elements carrying the demodulation reference signal based at least in part on the first physical layer cell identifier and the second physical layer cell identifier corresponding to the second cell.

[0220] Aspect 4: The method of aspect 1, wherein the step of determining whether overlap is allowed includes determining that overlap is allowed between one or more resource elements carrying the synchronization signal block and one or more resource elements carrying the demodulation reference signal based at least in part on the first physical layer cell identifier corresponding to the serving cell and the second physical layer cell identifier corresponding to the second cell.

[0221] Aspect 5: The method of aspect 1, wherein the step of determining whether overlap is allowed includes determining that overlap is allowed between one or more resource elements carrying the synchronization signal block and one or more resource elements carrying the demodulation reference signal based at least in part on the first physical layer cell identifier corresponding to the second cell and the second physical layer cell identifier corresponding to the serving cell.

[0222] Aspect 6: The method of any of aspects 1 to 5, further comprising the step of receiving a control message corresponding to a control resource set pool index value corresponding to a downlink shared channel, the control message including a scheduling downlink control information message.

[0223] Aspect 7: The method of aspect 6, further comprising determining that the downlink shared channel is associated with the serving cell based at least in part on the control resource set pool index value having a value of 0.

[0224] Aspect 8: The method of aspect 6, further comprising determining that the downlink shared channel is associated with the second cell based at least in part on the control resource set pool index value having a value of one.

[0225] Aspect 9: The method of any of aspects 6-8, wherein the control message is a semi-persistent scheduling control message corresponding to an activation downlink control information message received on a control resource set associated with a control resource set pool index value.

[0226] Aspect 10: The method of any of aspects 6 to 8, wherein the control message is a semi-persistent scheduling control message corresponding to a semi-persistent scheduling configuration in the radio resource control message, and the semi-persistent scheduling configuration indicates a control resource set pool index value.

[0227] Aspect 11: The method of any of aspects 1 to 10, further comprising determining that the downlink shared channel is associated with the serving cell based at least in part on the quasi-co-location relationship corresponding to the synchronization signal block being associated with the serving cell.

[0228] Aspect 12: The method of any of aspects 1-11, further comprising determining that the downlink shared channel is associated with the second cell based at least in part on the quasi-co-location relationship corresponding to the synchronization signal block being associated with the second cell.

[0229] Aspect 13: A method for wireless communication in a network entity, comprising: transmitting a synchronization signal block associated with a first physical layer cell identifier, wherein one or more resource elements carrying the synchronization signal block overlap with one or more resource elements carrying a downlink shared channel associated with a second physical layer cell identifier; determining, according to a comparison of the first physical layer cell identifier and the second physical layer cell identifier, whether overlap is allowed between the one or more resource elements carrying the synchronization signal block and one or more resource elements carrying a demodulation reference signal corresponding to the downlink shared channel; and processing the demodulation reference signal based at least in part on the determination.

[0230] Aspect 14: The method of aspect 13, further comprising: determining, based at least in part on the first physical layer cell identifier and the second physical layer cell identifier being the same physical layer cell identifier, that there is no overlap between one or more resource elements carrying the synchronization signal block and one or more resource elements carrying the demodulation reference signal.

[0231] Aspect 15: The method of aspect 13, further comprising: determining, based at least in part on the first physical layer cell identifier and the second physical layer cell identifier corresponding to the second cell, that there is no overlap between one or more resource elements carrying the synchronization signal block and one or more resource elements carrying the demodulation reference signal.

[0232] Aspect 16: The method of aspect 13, further comprising: determining, based at least in part on the first physical layer cell identifier corresponding to the serving cell and the second physical layer cell identifier corresponding to the second cell, that one or more resource elements carrying the synchronization signal block and one or more resource elements carrying the demodulation reference signal overlap.

[0233] Aspect 17: The method of aspect 13, further comprising: determining, based at least in part on the first physical layer cell identifier corresponding to the second cell and the second physical layer cell identifier corresponding to the serving cell, that one or more resource elements carrying the synchronization signal block and one or more resource elements carrying the demodulation reference signal overlap.

[0234] Aspect 18: The method of any of aspects 13-17, further comprising transmitting a control message indicating a control resource set pool index value corresponding to a downlink shared channel.

[0235] Aspect 19: The method of aspect 18, further comprising determining that the downlink shared channel is associated with the serving cell based at least in part on the control resource set pool index value having a value of 0.

[0236] Aspect 20: The method of any of aspects 18-19, further comprising determining that the downlink shared channel is associated with the second cell based at least in part on the control resource set pool index value having a value of one.

[0237] Aspect 21: The method of any of aspects 18-20, wherein the control message is a semi-persistent scheduling control message corresponding to an activation downlink control information message received on a control resource set associated with a control resource set pool index value.

[0238] Aspect 22: The method of any of aspects 18-20, wherein the control message is a semi-persistent scheduling control message corresponding to a semi-persistent scheduling configuration in the radio resource control message, and the semi-persistent scheduling configuration indicates a control resource set pool index value.

[0239] Aspect 23: The method of any of aspects 13 to 22, further comprising determining that the downlink shared channel is associated with the serving cell based at least in part on the quasi-co-location relationship corresponding to the synchronization signal block being associated with the serving cell.

[0240] Aspect 24: The method of any of aspects 13-22, further comprising determining that the downlink shared channel is associated with the second cell based at least in part on the quasi-co-location relationship corresponding to the synchronization signal block being associated with the second cell.

[0241] Aspect 25: An apparatus for wireless communication in a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform any of the methods of aspects 1-12.

[0242] Example 26: An apparatus for wireless communication in a UE, comprising at least one means for performing the method of any of Examples 1-12.

[0243] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication in a UE, the code including instructions executable by a processor to perform the method of any of aspects 1-12.

[0244] Aspect 28: An apparatus for wireless communication in a network entity, 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 any of the methods of aspects 13-24.

[0245] Example 29: An apparatus for wireless communication in a network entity, comprising at least one means for performing the method of any of Examples 13-24.

[0246] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication in a network entity, the code including instructions executable by a processor to perform any of the methods of aspects 13-24.

[0247] It should be noted that the methods described herein represent possible implementations, that the acts and steps may be rearranged or otherwise modified, and that other implementations are possible. Additionally, aspects from two or more of the methods may be combined.

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

[0249] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

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

[0251] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed such that parts of the functions are implemented in various physical locations.

[0252] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, Electrically Erasable Programmable ROM (EEPROM), Flash memory, Compact Disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or a general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer readable media. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer readable media.

[0253] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such as, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, the phrase "based on" as used herein should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, the phrase "based on" as used herein should be construed similarly to the phrase "based at least in part on."

[0254] The term "determine" or "determining" encompasses a wide variety of actions, and thus "determining" can include calculating, computing, processing, deriving, investigating, looking up (such as by looking up in a table, database, or another data structure), ascertaining, etc. "Determining" can also include receiving (such as receiving information), accessing (such as accessing data in a memory), etc. "Determining" can also include resolving, selecting, choosing, establishing, and other such similar actions.

[0255] In the accompanying figures, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes the similar components. If only a first reference label is used herein, the description is applicable to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0256] The description set forth herein with respect to the accompanying drawings describes exemplary configurations and does not represent every example that may be implemented or fall within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purposes of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0257] The description herein is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications of the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. [Explanation of symbols]

[0258] 100 Wireless communication system 105 Base Station, Standalone Base Station 105-a base station 105-b base station 110 Coverage Area, Geographical Coverage Area 110-a Coverage Area 115 UE 115-a UE 115-b UE 120 backhaul links 125 Communication Links 130 Core Network 135 Device-to-device (D2D) communication links, D2D communication links 140 Access Network Entity 145 Access Network Transmission Entity 150 IP Services 200 Wireless Communication System 205 Downlink Communication Link 210 SSB, Serving Cell SSB, Non-Serving Cell SSB 215 DMRS 220 Resource Element 225 PDSCH 235 Control Messages 300 Resources Diagram 305 SSB 310 DMRS 315 PDSCH 320-a Cell 320-b cell 400 Transmission diagram 405 Top QCL Chain 405-a QCL Chain 405-b QCL chain 500 Process Flow 600 Block Diagram 605 Devices 610 Receiver 615 Transmitter 620 Communications Manager 700 Block Diagram 705 Devices 710 Receiver 715 Transmitter 720 Communications Manager 725 SSB Components 730 PCI components 735 DMRS Components 800 Block Diagram 820 Communications Manager 825 SSB Components 830 PCI components 835 DMRS Components 840 Control Message Components 845 QCL Components 900 System 905 Devices 910 I / O Controller 915 Transceiver 920 Communications Manager 925 Antenna 930 Memory 935 Code 940 Processor 945 Bus 1000 Block Diagram 1005 Devices 1010 Receiver 1015 Transmitter 1020 Communications Manager 1100 Block Diagram 1105 Devices 1110 Receiver 1115 Transmitter 1120 Communications Manager 1125 SSB Manager 1130 PCI Manager 1135 DMRS Manager 1200 Block Diagram 1220 Communications Manager 1225 SSB Manager 1230 PCI Manager 1235 DMRS Manager 1240 Control Message Manager 1245 QCL Manager 1300 System 1305 Devices 1310 Network Communications Manager 1315 Transceiver 1320 Communications Manager 1325 Antenna 1330 Memory 1335 Code 1340 Processor 1345 Inter-Station Communications Manager 1350 Bus 1400 methods 1500 ways 1600 methods 1700 methods 1800 methods 1900 method

Claims

1. 1. A method for wireless communication in a user equipment (UE), comprising: receiving a synchronization signal block associated with a first physical layer cell identifier, wherein one or more resource elements carrying the synchronization signal block overlap with one or more resource elements carrying a downlink shared channel associated with a second physical layer cell identifier; determining whether an overlap is allowed between the one or more resource elements carrying the synchronization signal block and one or more resource elements carrying a demodulation reference signal corresponding to the downlink shared channel according to a comparison of the first physical layer cell identifier and the second physical layer cell identifier; processing the demodulation reference signal based at least in part on the determination; The method includes:

2. determining whether the overlap is permitted, determining, based at least in part on the first physical layer cell identifier and the second physical layer cell identifier being the same physical layer cell identifier, that no overlap is allowed between the one or more resource elements carrying the synchronization signal block and the one or more resource elements carrying the demodulation reference signal; or determining, based at least in part on the first physical layer cell identifier and the second physical layer cell identifier corresponding to a second cell, that no overlap is allowed between the one or more resource elements carrying the synchronization signal block and the one or more resource elements carrying the demodulation reference signal; or determining, based at least in part on the first physical layer cell identifier corresponding to a serving cell and the second physical layer cell identifier corresponding to a second cell, that overlap is allowed between the one or more resource elements carrying the synchronization signal block and the one or more resource elements carrying the demodulation reference signal; or determining, based at least in part on the first physical layer cell identifier corresponding to a second cell and the second physical layer cell identifier corresponding to a serving cell, that overlap is allowed between the one or more resource elements carrying the synchronization signal block and the one or more resource elements carrying the demodulation reference signal.

2. The method of claim 1, comprising:

3. The method of claim 1, further comprising a step of receiving a control message corresponding to a control resource set pool index value corresponding to the downlink shared channel, the control message including a scheduling downlink control information message. determining, based at least in part on the control resource set pool index value having a value of 0, that the downlink shared channel is associated with a serving cell; or determining that the downlink shared channel is associated with a second cell based at least in part on the control resource set pool index value having a value of one.

4. The method of claim 3, further comprising:

5. The control message is a semi-persistent scheduling control message corresponding to an activation downlink control information message received on a control resource set associated with the control resource set pool index value, or The method of claim 3, wherein the control message is a semi-persistent scheduling control message corresponding to a semi-persistent scheduling configuration in a radio resource control message, the semi-persistent scheduling configuration indicating the control resource set pool index value. determining that the downlink shared channel is associated with the serving cell based at least in part on a quasi-co-location relationship corresponding to the synchronization signal block being associated with the serving cell; or determining that the downlink shared channel is associated with a second cell based at least in part on a quasi-co-location relationship corresponding to the synchronization signal block being associated with the second cell; The method of claim 1, further comprising:

7. 1. A method for wireless communication in a network entity, comprising: transmitting a synchronization signal block associated with a first physical layer cell identifier, wherein one or more resource elements carrying the synchronization signal block overlap with one or more resource elements carrying a downlink shared channel associated with a second physical layer cell identifier; determining whether an overlap is allowed between the one or more resource elements carrying the synchronization signal block and one or more resource elements carrying a demodulation reference signal corresponding to the downlink shared channel according to a comparison of the first physical layer cell identifier and the second physical layer cell identifier; processing the demodulation reference signal based at least in part on the determination; The method includes: determining that there is no overlap between the one or more resource elements carrying the synchronization signal block and the one or more resource elements carrying the demodulation reference signal based at least in part on the first physical layer cell identifier and the second physical layer cell identifier being the same physical layer cell identifier; or determining, based at least in part on the first physical layer cell identifier and the second physical layer cell identifier corresponding to a second cell, that there is no overlap between the one or more resource elements carrying the synchronization signal block and the one or more resource elements carrying the demodulation reference signal; or determining that the one or more resource elements carrying the synchronization signal block and the one or more resource elements carrying the demodulation reference signal overlap based at least in part on the first physical layer cell identifier corresponding to a serving cell and the second physical layer cell identifier corresponding to a second cell; or determining that the one or more resource elements carrying the synchronization signal block and the one or more resource elements carrying the demodulation reference signal overlap based at least in part on the first physical layer cell identifier corresponding to a second cell and the second physical layer cell identifier corresponding to a serving cell.

8. The method of claim 7, further comprising:

9. The method of claim 7, further comprising the step of transmitting a control message indicating a control resource set pool index value corresponding to the downlink shared channel.

10. The method of claim 1, further comprising: determining, based at least in part on the control resource set pool index value having a value of 0, that the downlink shared channel is associated with a serving cell; or determining that the downlink shared channel is associated with a second cell based at least in part on the control resource set pool index value having a value of one; 10. The method of claim 9, further comprising:

11. The control message is a semi-persistent scheduling control message corresponding to an activation downlink control information message received on a control resource set associated with the control resource set pool index value, or 10. The method of claim 9, wherein the control message is a semi-persistent scheduling control message corresponding to a semi-persistent scheduling configuration in a radio resource control message, the semi-persistent scheduling configuration indicating the control resource set pool index value. determining that the downlink shared channel is associated with the serving cell based at least in part on a quasi-co-location relationship corresponding to the synchronization signal block being associated with a serving cell; or determining that the downlink shared channel is associated with a second cell based at least in part on a quasi-co-location relationship corresponding to the synchronization signal block being associated with the second cell; 8. The method of claim 7, further comprising:

13. An apparatus for wireless communication in a user equipment (UE) comprising at least one means for performing a method according to any one of claims 1 to 6.

14. An apparatus for wireless communication in a network entity comprising at least one means for performing a method according to any one of claims 7 to 12.

15. A computer program comprising instructions which, when executed by a computer, cause the computer to carry out a method according to any one of claims 1 to 12.

Images