Resource element overlap between the synchronization signal block and the 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, and U.S. Patent Application No. 17 / 740,881, filed May 10, 2022, both entitled "RESOURCE ELEMENT OVERLAP BETWEEN A SYNCHRONIZATION SIGNAL BLOCK AND DEMODULATION REFERENCE SIGNAL," each of which was assigned to the assignee of this application.

[0002] The following relates to wireless communication that includes resource element overlap between a synchronization signal block (SSB) and a demodulation reference signal (DMRS).

Background Art

[0003] Wireless communication systems are widely deployed to provide various types of communication content, including voice, video, packet data, messaging, and broadcast. These systems may support 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) systems, LTE-A systems, 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 sometimes be known as user equipment (UEs). [Overview of the project] [Means for solving the problem]

[0004] The techniques described relate to improved methods, systems, devices, and apparatus for supporting resource element overlap between synchronous signal blocks and demodulated reference signals. Generally, the techniques described provide a user instrument (UE) for determining whether overlap is permitted between resource elements carrying synchronous signal blocks (SSBs) and resource elements carrying demodulated reference signals (DMRS) in a downlink shared channel. The UE may receive an SSB containing a physical layer cell identifier (PCI), and one or more resource elements carrying an SSB may overlap with resource elements carrying a downlink shared channel associated with another PCI. The PCI may be for a serving cell or another cell, such as a non-serving cell. The UE may also receive one or more DMRS in one or more resource elements in the downlink shared channel. The UE may determine whether overlap is permitted between resource elements by comparing the PCI of the SSB with the PCI of the downlink shared channel. In some examples, once the UE has determined whether resource element overlap is permitted, the UE may process the DMRS.

[0005] A method for wireless communication in a UE is described. The method may include the steps of: receiving an SSB associated with a first PCI, wherein 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 an overlap is permitted between the one or more resource elements carrying the SSB and the one or more resource elements carrying the DMRS corresponding to the downlink shared channel; and processing the DMRS based on the determination.

[0006] A device for wireless communication in a UE is described. The device may include a processor, memory coupled to the processor, and instructions stored in the memory. Instructions may be executable by the processor to cause the device to receive an SSB associated with a first PCI, wherein 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 an overlap is permitted 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.

[0007] Another apparatus for wireless communications in a UE is described. The apparatus may include means for receiving an SSB associated with a first PCI, wherein 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 an overlap is permitted between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to a downlink shared channel; and means for processing the DMRS based on the determination.

[0008] The present invention describes a non-temporary computer-readable medium for storing code for wireless communications in a UE. The code may include instructions executable by a processor to receive an SSB associated with a first PCI, wherein 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 an overlap is permitted between 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.

[0009] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, determining whether duplication may be permitted may include an operation, feature, means, or instruction for determining that duplication may not be permitted between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS, based on the fact that the first PCI and the second PCI correspond to serving cells.

[0010] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, determining whether duplication may be permitted may include an operation, feature, means, or instruction for determining that duplication may not be permitted between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS, based on the fact that the first PCI and the second PCI are the same PCI.

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

[0012] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, determining whether duplication may be permitted may include an operation, feature, means, or instruction for determining whether duplication may be permitted 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-temporary computer-readable media described herein, determining whether duplication may be permitted may include an operation, feature, means, or instruction for determining whether duplication may be permitted between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS, based on the fact that a first PCI corresponds to a second cell and a second PCI corresponds to a serving cell.

[0014] Some examples of methods, apparatus, and non-temporary computer-readable media described herein include receiving control messages corresponding to control resource set (CORESET) pool index values ​​corresponding to downlink shared channels, and further including operations, features, means, or instructions for receiving control messages, the control messages including scheduling downlink control information (DCI) messages.

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

[0016] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for determining that a downlink shared channel can be associated with a second cell based on the CORESET pool index value having a value of 1.

[0017] In some examples of the methods, apparatus, and non-temporary 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 CORESET associated with a CORESET pool index value.

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

[0019] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for determining that a downlink shared channel can be associated with a serving cell, based on the fact that a pseudo-collocation (QCL) relationship corresponding to an SSB is associated with a serving cell.

[0020] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for determining that a downlink shared channel can be associated with a second cell, based on the fact that a QCL relationship corresponding to an SSB is associated with a second cell.

[0021] A method for wireless communication in a network entity is described. The method may include the steps of: transmitting an SSB associated with a first PCI, wherein 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 an overlap is permitted between the one or more resource elements carrying the SSB and the one or more resource elements carrying a DMRS corresponding to the downlink shared channel; and processing the DMRS based on the determination.

[0022] A device for wireless communication in a network entity is described. The device may include a processor, memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to transmit an SSB associated with a first PCI, such that 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; to determine, according to a comparison of the first PCI and the second PCI, whether an overlap is permitted between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to the downlink shared channel; and to process the DMRS based on the determination.

[0023] Another apparatus for wireless communication in a network entity will be described. The apparatus may include means for transmitting an SSB associated with a first PCI, wherein 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, and means for determining whether overlap is permitted between 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 between the first PCI and the second PCI, and means for processing the DMRS based on the determination.

[0024] A non - transient computer - readable medium storing code for wireless communication in a network entity will be described. The code may include instructions executable by a processor to transmit an SSB associated with a first PCI, wherein 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, to determine whether overlap is permitted between 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 between the first PCI and the second PCI, and to process the DMRS based on the determination.

[0025] Some examples of the methods, apparatuses, and non - transient computer - readable media described herein may further include operations, features, means, or instructions for determining that there cannot be an 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.

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

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

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

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that one or more resource elements carrying the SSB and one or more resource elements carrying the 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, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting a control message indicating a CORESET pool index value corresponding to the downlink shared channel.

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

[0032] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for determining that a downlink shared channel can be associated with a second cell based on the CORESET pool index value having a value of 1.

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

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

[0035] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for determining that a downlink shared channel can be associated with a serving cell, based on the fact that a QCL relationship corresponding to an SSB is associated with a serving cell.

[0036] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for determining that a downlink shared channel can be associated with a second cell, based on the fact that a QCL relationship corresponding to an SSB is associated with a second cell. [Brief explanation of the drawing]

[0037] [Figure 1] This figure shows an example of a wireless communication system that supports resource element overlap between a synchronization signal block (SSB) and a demodulated reference signal (DMRS) according to an aspect of the present disclosure. [Figure 2] This figure shows an example of a wireless communication system that supports resource element overlap between SSB and DMRS according to an aspect of the present disclosure. [Figure 3] This figure shows an example of a resource diagram that supports resource element overlap between SSB and DMRS according to an aspect of this disclosure. [Figure 4] This figure shows an example of a transmission diagram that supports resource element overlap between SSB and DMRS according to an aspect of this disclosure. [Figure 5] This figure shows an example of a process flow that supports resource element overlap between SSB and DMRS according to an aspect of this disclosure. [Figure 6] This is a block diagram of a device that supports resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Figure 7] This is a block diagram of a device that supports resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Figure 8] This is a block diagram of a communications manager that supports resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Figure 9] This is a diagram of a system including a device that supports resource element overlap between an SSB and a DMRS, according to an aspect of the present disclosure. [Figure 10] This is a block diagram of a device that supports resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Figure 11] This is a block diagram of a device that supports resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Figure 12]This is a block diagram of a communications manager that supports resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Figure 13] This is a diagram of a system including a device that supports resource element overlap between an SSB and a DMRS, according to an aspect of the present disclosure. [Figure 14] This flowchart shows a method for supporting resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Figure 15] This flowchart shows a method for supporting resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Figure 16] This flowchart shows a method for supporting resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Figure 17] This flowchart shows a method for supporting resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Figure 18] This flowchart shows a method for supporting resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Figure 19] This flowchart shows a method for supporting resource element overlap between an SSB and a DMRS according to an aspect of the present disclosure. [Modes for carrying out the invention]

[0038] In some communication systems, before exchanging data and additional messages, user equipment (UE) may monitor and receive synchronization signals from network entities, such as one or more components of a cell or base station, to determine configuration and timing information for sending and receiving subsequent messages to and from a cell or base station. For example, a cell, or one or more components of a base station, may transmit a synchronization signal block (SSB) which may include 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 which type of cell the SSB is configured for. For example, the SSB may include, or be associated with, a serving cell PCI (for example, in which case the PCI is determined from the PSS and SSS) or a non-serving cell PCI (for example, 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, SSB may temporally overlap with one or more downlink channels transmitted by the same cell or a different cell that transmits the SSB. A technique is desired to determine whether information about the SSB can be used to receive one or more downlink channels that contain demodulated reference signals (DMRS) among the one or more downlink channels that temporally overlap with the SSB.

[0039] Based on the association of the SSB and the downlink shared channel with the PCI, the UE may determine whether to anticipate resource element overlap between the SSB and the DMRS of the downlink shared channel (e.g., the physical downlink shared channel (PDSCH)). For example, if both the SSB and the PDSCH are associated with a serving cell PCI, the UE cannot anticipate overlap between resource elements. Similarly, if both the SSB and the PDSCH are associated with a non-serving cell PCI, the UE cannot anticipate overlap between resource elements. However, if one of the SSB or PDSCH is associated with a serving cell and the other with a non-serving cell, the UE can anticipate overlap between resource elements. Therefore, if the UE receives an SSB containing PCI from a cell or base station, it can determine whether there is overlap between the resource elements carrying the SSB and the 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. A UE may receive a DMRS based on its determination of whether the resource elements of the SSB and the DMRS overlap or not. In some examples, a UE may determine that a PDSCH is associated with a serving cell or a non-serving cell based on the control resource set (CORESET) pool index from which the UE can receive its instructions in control signaling from a cell or base station. Additionally or alternatively, a UE may determine that a PDSCH is associated with a serving cell or a non-serving cell based on a pseudo-collocation (QCL) relationship with an SSB.

[0040] The aspects of this disclosure will first be described in the context of wireless communication systems. Further descriptions of the aspects of this disclosure will be given in the context of resource diagrams, transmission diagrams, and process flows. The aspects of this disclosure will be further illustrated and described with reference to equipment diagrams, system diagrams, and flowcharts relating to resource element overlap between SSB and DMRS.

[0041] Figure 1 shows an example of a wireless communication system 100 that supports resource element overlap between SSB and DMRS according to an aspect of the present 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, an LTE Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support extended broadband communication, ultra-high reliability (e.g., mission-critical) communication, low-latency communication, communication with low-cost, low-complexity devices, or any combination thereof.

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

[0043] The UE115 may be distributed across the entire coverage area 110 of the wireless communication system 100, and each UE115 may be fixed, mobile, or both at different times. The UE115 may be devices in different forms or with different capabilities. Several exemplary UE115 are shown in Figure 1. The UE115 described herein may be capable of communicating with various types of devices, such as other UE115, 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 Figure 1.

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

[0045] One or more of the base stations 105 described herein may include, or be referred to as, a base transceiver station, a radio base station, an access point, a radio transceiver, a node B, an e-node B (eNB), a next-generation node B or giganode B (either of which may be called a gNB), a home node B, a home e-node B, or other preferred terms.

[0046] UE115 may include, or may be referred to as, a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other preferred term; “device” may also be referred to as a unit, station, terminal, or client, in the examples. UE115 may also include, or may be referred to as, personal electronic devices such as cellular phones, personal digital assistants (PDAs), tablet computers, laptop computers, or personal computers. In some examples, UE115 may include, or may be referred to as, a wireless local loop (WLL) station, an Internet of Things (IoT) device, any Internet of Things (IoE) device, or a machine-type communications (MTC) device, in the examples, or may be implemented in various items such as appliances, vehicles, meters, etc.

[0047] The UE115 described herein may be capable of communicating with other UE115s that may function as relays, as shown in Figure 1, and with various types of devices, including, among other examples, a macro eNB or gNB, a small cell eNB or gNB, or a base station 105 and network equipment including a relay base station.

[0048] UE115 and base station 105 may wirelessly communicate with each other via one or more communication links 125 over one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication links 125. For example, a carrier used for communication link 125 may include a portion of the radio frequency spectrum band (e.g., a bandwidth part (BWP)) operating 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 collected signaling (e.g., synchronization signals, system information), control signaling to coordinate operations with the carrier, user data, or other signaling. The wireless communication system 100 may support communication with UE115 using carrier aggregation or multi-carrier operation. UE115 may consist of multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation can be used with both frequency-division duplex (FDD) component carriers and time-division duplex (TDD) component carriers.

[0049] In some examples (for instance, in carrier aggregation configurations), a carrier may also have acquisition or control signaling to coordinate its operation with other carriers. A carrier may be associated with a frequency channel (e.g., an Advanced Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be positioned according to a channel raster for discovery by the UE115. A carrier may operate in a standalone mode where initial acquisition and connection are performed by the UE115 via the carrier, or in a non-standalone mode where connection is anchored using different carriers (e.g., the same or different radio access technologies).

[0050] A communication link 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. The carrier may carry downlink communications or uplink communications (for example, in FDD mode), or may be configured to carry downlink communications and uplink communications (for example, in TDD mode).

[0051] A carrier may be associated with a specific 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 the carrier of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have a hardware configuration that supports communication on a specific 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 over carriers associated with multiple carrier bandwidths. In some examples, each UE 115 being served may be configured to operate on a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0052] The signal waveform transmitted on a carrier can consist of multiple subcarriers (for example, using multicarrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM). In systems 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 subcarrier interval 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). Therefore, the more resource elements the UE115 receives, and the higher the order of the modulation scheme, the higher the data rate of the UE115 can be. Wireless communication resources may refer to a combination of radio frequency spectral resources, temporal 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 UE115.

[0053] One or more numerologies may be supported for a carrier, 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, UE115 may consist of multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communication for UE115 may be limited to one or more active BWPs.

[0054] The time interval for base station 105 or UE115 is, for example, T s = 1 / (Δf max ·N f It can refer to a sampling period of ) seconds, and may be expressed in multiples of the basic time unit, however, Δf max This can represent the maximum supported subcarrier interval, N fThis may represent the maximum supported Discrete Fourier Transform (DFT) size. The time interval of communication resources 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 contain multiple sequentially numbered subframes or slots, each subframe or slot having the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into several slots. Alternatively, each frame may contain a variable number of slots, the number of slots may depend on the subcarrier interval. Each slot may contain several symbol periods (e.g., depending on the length of the cyclic prefix prepared for each symbol period). In some wireless communication systems 100, a slot may be further divided into several minislots, each containing one or more symbols. Except for the cyclic prefix, each symbol period may contain one or more (e.g., N) symbols. f The sampling period may include (1) units. The duration of the symbol period may depend on the subcarrier interval 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 communication system 100 and may be called a transmit time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods within the TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0057] Physical channels can be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels can be multiplexed on a downlink carrier using, for example, one or more of the following techniques: time-division multiplexing (TDM), frequency-division multiplexing (FDM), or hybrid TDM-FDM. A control region (e.g., CORESET) for a physical control channel may be defined by the number of symbol periods and may extend to 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 UE115s. For example, one or more of the UE115s may monitor or search for control regions for control information according to one or more search space sets, each search space set may include one or more control channel candidates at one or more aggregation levels arranged in a cascaded manner. An aggregation level for control channel candidates may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. The search space set may include a common search space set configured to send control information to multiple UE115s, and a UE-specific search space set for sending control information to a specific UE115.

[0058] Each base station 105 may provide communication coverage through one or more cells, such as macrocells, small cells, hotspots, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with base station 105 (for example, on a carrier) and may be associated with an identifier for distinguishing neighboring cells (for example, a physical cell identifier (PCID), a virtual cell identifier (VCID), or other). In some examples, a cell may also refer to a geographical coverage area 110 or a portion of geographical coverage area 110 (for example, a sector) on which the logical communication entity operates. Such cells may range from smaller areas (for example, structures, subsets of structures) to larger areas, depending on various factors such as the capabilities of base station 105. For example, a cell may be, in the example, a building, a subset of a building, or external space between or overlapping with geographical coverage area 110.

[0059] Macrocells can typically cover relatively large geographical areas (e.g., a radius of several kilometers) and can enable unrestricted access by UE115s subscribed to the services of a network provider that supports macrocells. Small cells may be associated with lower-power base stations 105 compared to macrocells, and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macrocells. Small cells may provide unrestricted access to UE115s subscribed to the services of a network provider, or they may provide restricted access to UE115s associated with small cells (e.g., UE115s in a limited subscriber group (CSG), UE115s associated with users in a home or office). 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 cases, 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 can provide access to different types of devices.

[0061] In some examples, base station 105 may be mobile and therefore capable of providing communication coverage to a moving geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but 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, for example, heterogeneous networks in which 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 communication system 100 may support synchronous or asynchronous operation. In synchronous operation, base stations 105 may have similar frame timings, and transmissions from different base stations 105 may be approximately synchronized in time. In asynchronous operation, base stations 105 may have different frame timings, and transmissions from different base stations 105 may, in some cases, not be synchronized in time. The techniques described herein may be used for either synchronous or asynchronous operation.

[0063] Some UE115s, such as MTC devices or IoT devices, may be low-cost or low-complexity devices that can provide automated communication between machines (for example, via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that enables devices to communicate with each other or with base stations 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 it to a human interacting with the application program. Some UE115s 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 detection, physical access control, and transaction-based business billing.

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

[0065] The wireless communication system 100 may be configured to support ultra-high reliability communication, low latency communication, or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-high reliability low latency communication (URLLC) or mission-critical communication. The UE 115 may be designed to support ultra-high reliability, low latency, or critical functions (e.g., mission-critical functions). Ultra-high reliability communication may include private or group communication 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 mission-critical services may be used for public safety or general commercial purposes. The terms ultra-high reliability, low latency, mission-critical, and ultra-high reliability low latency may be used interchangeably herein.

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

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

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

[0069] Some of the network devices, such as the base station 105, may include sub-components 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 called radio heads, smart radio heads, or transmit / receive points (TRPs). Each access network transmitting entity 145 may include one or more antenna panels. In some configurations, the 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., base station 105).

[0070] As described herein, base station 105 may include components located in a single physical location or components located in various physical locations. In an example where base station 105 includes components located in various physical locations, each of the various components may perform a different function, and as a result, collectively, the various components achieve similar functionality to base station 105 located in a single physical location. Therefore, 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 physically or logically separated components that collectively implement the functionality of the base station), or another network device that communicates with or supports communication with the UE115.

[0072] The wireless communication system 100 may typically operate using one or more frequency bands in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band, as wavelengths range from approximately 1 decimeter to 1 meter. While UHF waves may be blocked or redirected by building and environmental characteristics, these waves can penetrate structures well enough to serve a UE 115 where a macrocell is located indoors. Transmitting UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmitting using lower frequencies and longer waves in the shortwave (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0073] The wireless communication system 100 may also operate in the super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz, also known as the centimeter band, or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communication system 100 may support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of each device may be smaller and more densely spaced than UHF antennas. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to greater atmospheric attenuation than SHF or UHF transmissions and may have shorter distances. The techniques disclosed herein may be employed across transmissions using one or more different frequency domains, and the specified use of bands across these frequency domains 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 unlicensed bands such as the 5 GHz Industrial Scientific Medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, devices such as base station 105 and UE 115 may employ carrier detection for collision detection and avoidance. In some examples, operation in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in licensed bands (e.g., LAA). Operation in unlicensed spectrums may include, among other examples, downlink transmission, uplink transmission, P2P transmission, or D2D transmission.

[0075] Base station 105 or UE115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE115 may be located in one or more antenna arrays or antenna panels that can support MIMO operation or transmit beamforming or receive beamforming. For example, one or more base station antennas or antenna arrays may be collated in an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with base station 105 may be located in diverse geographical locations. Base station 105 may have an antenna array with several rows and columns of antenna ports that base station 105 can use to support beamforming of communication with UE115. Similarly, UE115 may have one or more antenna arrays that can support various MIMO or beamforming operations. As an addition or alternative, antenna panels may support radio frequency beamforming for signals transmitted through antenna ports.

[0076] A base station 105 or UE115 may use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals through different spatial layers. Such techniques are sometimes called spatial multiplexing. Multiple signals may be transmitted by a transmitting device through different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device through different antennas or different combinations of antennas. Each of the multiple signals may be called 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). Different spatial layers may be associated with different antenna ports used for channel measurement 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 called spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used in a transmitting or receiving device (e.g., base station 105, UE115) to shape or steer an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals communicated through the antenna elements of an antenna array such that several signals propagating in a particular orientation relative to the antenna array undergo constructive interference and other signals undergo destructive interference. Coordination of signals communicated through antenna elements may include the transmitting or receiving device applying amplitude offset, phase offset, or both to the signals carried through the antenna elements associated with the device. Coordination associated with each antenna element 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 UE 115 may use beam sweeping techniques as part of its beamforming operation. For example, the base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Several signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the base station 105 in different directions. For example, the base station 105 may transmit signals according to different beamforming weight sets associated with different directions of transmission. Transmissions in different beam directions may be used to identify the beam direction for subsequent transmission or reception by the base station 105 (e.g., by a transmitting device such as the base station 105, or by a receiving device such as the UE 115).

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

[0080] In some examples, transmission by a device (e.g., by base station 105 or UE115) 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 base station 105 to UE115). UE115 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. Base station 105 may transmit reference signals that can be precoded or amplified (e.g., cell-specific reference signals (CRS), channel-state information reference signals (CSI-RS)). UE115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). These techniques will be described with reference to signals transmitted by base station 105 in one or more directions, but UE 115 may employ similar techniques for transmitting signals multiple times in different directions (for example, to identify beam directions for subsequent transmission or reception by UE 115) or for transmitting signals in a single direction (for example, to transmit data to a receiving device).

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

[0082] The wireless communication system 100 may be a packet-based network operating 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 for communication over logical channels. The Medium Access Control (MAC) layer may perform priority processing and multiplexing logical channels to transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to improve link efficiency by supporting retransmission at the MAC layer. In the control plane, the RRC protocol layer may establish, configure, and maintain RRC connections between the UE 115 and the base station 105 or core network 130, supporting radio bearers for user plane data. At the physical layer, transport channels may be mapped to physical channels.

[0083] UE115 and base station 105 may support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Retransmission Request (ARQ) feedback is one technique to increase the likelihood of data being correctly received on communication link 125. HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Retransmission Request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise conditions). In some examples, devices may support same-slot HARQ feedback, where the device may provide HARQ feedback in a slot for data received in a previous symbol within a particular slot. In other cases, the device may provide HARQ feedback in subsequent slots or according to some other time interval.

[0084] In some examples, UE115 may monitor and receive synchronization signals from the cell or base station 105. UE115 may use the synchronization signals to determine configuration and timing information for sending and receiving subsequent messages to and from the cell or base station 105. In some examples, base station 105 or the cell may transmit an SSB containing one or more synchronization signals to UE115, which UE115 may use to determine configuration and timing information for subsequent messages. In some cases, a serving cell (e.g., a cell serving UE115) may have PCI determined from the synchronization signals in the initial access procedure. A non-serving cell, or an alternative cell (e.g., a cell other than the serving cell), may have one or more additional PCI 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, a downlink shared channel may be rate-matched with one or more PRBs containing SSBs. UE115 may not expect the DMRS resource elements for a downlink shared channel to overlap with the resource elements for the SSB. However, interference may occur between the SSB and the downlink shared channel if a downlink shared channel associated with a serving cell PCI is not rate-matched with one or more non-serving cell SSBs, or if a downlink shared channel associated with a non-serving cell PCI is not rate-matched with one or more serving cell SSBs.

[0085] In some cases, UE115 may determine whether overlap is permitted between resource elements carrying SSBs and resource elements carrying DMRS in a downlink shared channel (e.g., PDSCH). For example, UE115 may receive an SSB from a base station in one or more resource elements, including PCIs for a serving cell or another cell. UE115 may also receive one or more DMRSs from base station 105 in one or more resource elements in a PDSCH. A PDSCH may be associated with a cell, such as a serving cell or another cell. For example, a PDSCH may have PCIs for the same cell as the SSB (e.g., the same PCI) or PCIs for a different cell than the SSB. UE115 may compare the PCIs of the SSB and the PCIs of the PDSCH to determine whether there is overlap in the resource elements. In some cases, the conditions under which UE115 can anticipate resource element overlap between the SSB and PDSCH DMRS may be based on the association between the SSB and PDSCH and PCI, which will be explained in more detail with respect to Figure 3. In some examples, once UE115 determines whether resource element overlap is permitted, UE115 may process the DMRS.

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

[0087] In some examples, UE115 may monitor and receive synchronization signals from the cell or base station 105. UE115 may use the synchronization signals to determine configuration and timing information for sending and receiving subsequent messages to and from the cell or base station 105. In some examples, base station 105 may transmit SSB210 containing the synchronization signals (e.g., via four OFDM symbols), such as PSS, SSS, PBCH, MIB, or a combination thereof. In some cases, base station 105 may transmit the synchronization signals in a set of synchronization signal bursts, which may be a set of SSB210s 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., 5ms, 10ms, 20ms, ... 160ms, with a default period of 20ms). In some examples, there may be a maximum number of SSB210s within a synchronization signal burst set (e.g., 4 for sub-3GHz, 8 for sub-7GHz, 64 for frequency range 2 (FR2)).

[0088] In some cases, base station 105 or a cell may transmit SSB210 using different beams. The beams may be indexed by 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 derive from a set of patterns (e.g., a defined or fixed set of patterns). The patterns may depend on the subcarrier interval (e.g., 15 or 30 kHz for frequency range 1 (FR1) and 120 or 240 kHz for FR2). Base station 105 may indicate the location of SSB210 to UE 115. For example, base station 105 may transmit one or more SSB indices that base station 105 transmits in control signaling as parameters (e.g., ssb-PositionsInBurst in a System Information Block (SIB), such as SIB Type 1 (SIB1), or in ServingCellConfigCommon).

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

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

[0091] In some cases, such as in inter-cell multi-TRP operation, the UE115 and base station 105 may support additional PCIs that may differ from the serving cell PCI for each component carrier. These additional PCIs may be associated with one or more activated TCI states for each component carrier, such as a reference signal (e.g., CSI-RS for CSI), downlink shared channel, downlink control channel, or a combination thereof, in scenarios with non-cross-carrier QCL instructions. In some examples, base station 105 and UE115 may determine non-serving cell SSB information. For example, this information may include (e.g., according to implicit or explicit instructions) the SSB time-domain position, SSB transmit period, SSB transmit power, and other non-serving cell information.

[0092] In some cases, such as when a downlink shared channel (e.g., PDSCH225) resource overlaps with an SSB resource in terms of time, frequency, or both, a downlink shared channel may be rate-matched with one or more PRBs, including an SSB210. That is, a PRB may not be available for the downlink shared channel. One or more SSB210s may be considered for rate matching according to one or more parameters such as ssb-PositionsInBurst (e.g., one or more of 64 SSB210s). UE115 may not expect the resource elements of DMRS215 for a downlink shared channel to overlap with the resource elements for an SSB210 (e.g., rate matching may be for a data tone). In some examples, such as in a multi-TRP transmission scenario between cells, one or more downlink shared channels associated with a serving cell PCI may not be rate-matched with a serving cell SSB210. In some other examples, one or more downlink shared channels associated with other non-serving cell PCIs may be rate-matched with a non-serving cell SSB210. However, if the downlink shared channel associated with a serving cell PCI is not rate-matched with one or more non-serving cell SSB210s, or if the downlink shared channel associated with a non-serving cell PCI is not rate-matched with one or more serving cell SSB210s, interference may occur between the SSB210 and the downlink shared channel.

[0093] In some cases, such as when base station 105 performs rate matching, resource elements may not overlap with DMRS215. For example, rate matching may be applicable to data tones (e.g., data tones other than DMRS tones may be rate-matched, but may not overlap with DMRS tones). In some other cases, such as when base station 105 does not perform rate matching, there may be interference to data tones (e.g., from SSB210 of another TRP). Therefore, it may be acceptable for DMRS tones to be subjected to similar interference (e.g., interference to data tones on overlapping PRBs may occur, so overlap may be permitted). Base station 105 can benefit from taking into account the condition that resource elements do not overlap with DMRS215. For example, base station 105 may consider whether overlapping downlink shared channels are associated with a serving cell or another non-serving cell. As an addition or alternative, base station 105 may consider whether overlapping SSB210s are associated with a serving cell or another non-serving cell.

[0094] In some cases, UE115 may determine whether overlap is permitted between resource elements 220 carrying SSB210 and resource elements 220 carrying DMRS215 in a downlink shared channel (e.g., PDSCH225). For example, UE115-a may receive SSB210 from base station 105-a via downlink communication link 205 in one or more resource elements 220. The SSB may include PCI for another cell, which may be a serving cell or a non-serving cell. UE115-a may also receive one or more DMRS215 from base station 105-a in one or more resource elements 220 in PDSCH225. PDSCH225 may be associated with a cell, such as a serving cell or another cell. For example, PDSCH225 may have PCI for the same cell as the PCI for SSB210 (e.g., the same PCI) or PCI for a different cell than the PCI for SSB. In 230, UE115-a may compare the PCI of SSB210 with the PCI of PDSCH225 to determine if there is any overlap in resource element 220. In some cases, the conditions under which UE115-a can predict an overlap of resource element 220 between SSB210 and PDSCH225's DMRS215 may be based on the association between SSB210 and PDSCH225 and PCI, which will be explained in more detail with reference to Figure 3.

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

[0096] In some other examples, UE115-a may determine whether PDSCH225 is associated with a serving cell PCI or another PCI, such as a non-serving cell PCI, based on indirect QCL relationships, such as a top QCL chain, as described in more detail with respect to Figure 4. In some examples, once UE115-a determines whether resource element duplication is permitted, UE115-a may process DMRS215.

[0097] Figure 3 shows an example of a resource diagram 300 that supports resource element overlap between SSB and DMRS according to an aspect of this disclosure. In some examples, resource diagram 300 may implement aspects of wireless communication systems 100 and 200. For example, resource diagram 300 may be implemented by a UE 115 and a base station 105, as described with reference to Figures 1 and 2. In some cases, the base station may transmit SSB 305 and DMRS 310 in a downlink shared channel to the UE. The resource elements of SSB 305 and DMRS 310 may overlap depending on whether resource element overlap is permitted in the UE.

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

[0099] In some cases, in 325, there may be resource element overlap between SSB305 associated with PCI for cell 320-a, such as the Serving Cell PCI, and PDSCH315 associated with PCI for cell 320-a. The UE cannot anticipate the overlap between the resource element for DMRS310 in PDSCH315 and the resource element in SSB305.

[0100] In some other examples, in 330, there may be resource element overlap between SSB305 associated with PCI for cell 320-b, such as a non-serving cell PCI, and PDSCH315 associated with PCI for cell 320-b. The UE cannot anticipate the overlap between the resource elements for DMRS310 in PDSCH315 and the resource elements in SSB305.

[0101] In some other examples, in 335, there may be resource element overlap between SSB305 associated with PCI for cell 320-a, such as a serving cell PCI, and PDSCH315 associated with PCI for cell 320-b, which may be a non-serving cell PCI. The UE may anticipate overlap between the resource element for DMRS310 in PDSCH315 and the resource element in SSB305.

[0102] In some other examples, in 340, there may be resource element overlap between SSB305 associated with PCI for cell 320-b, such as a non-serving cell PCI, and PDSCH315 associated with PCI for cell 320-a, such as a serving cell PCI. The UE may anticipate overlap between the resource elements for DMRS310 in PDSCH315 and the resource elements in SSB305.

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

[0104] In some cases, the UE may determine whether a downlink shared channel (e.g., PDSCH) is associated with a serving cell PCI or with another PCI for a different cell, based on indirect QCL relationships such as the top QCL chain 405. In some cases, the TCI state or QCL assumption for a PDSCH may be based on a CSI-RS or tracking reference signal (TRS). A CSI-RS or TRS can be QCL'd with an SSB directly or indirectly. For example, in QCL chain 405-a, at 410, the SSB can be QCL'd with a CSI-RS associated with a TRS at 415, a CSI-RS at 420, and ultimately with a PDSCH at 425. Similarly, in QCL chain 405-b, at 430, the SSB can be QCL'd with a CSI-RS associated with a TRS at 435, and with a PDSCH at 440. In some cases, if the SSB in the top QCL chain of a PDSCH is associated with a serving cell PCI, the PDSCH may also be associated with a 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, then the PDSCH may also be associated with another PCI.

[0105] Figure 5 shows an example of a process flow 500 supporting resource element overlap between SSB and DMRS according to aspects of the present disclosure. In some examples, the process flow 500 may implement aspects of wireless communication system 100, wireless communication system 200, resource diagram 300, and transmission diagram 400. The process flow 500 may show an example of determining whether overlap is permitted between one or more resource elements carrying SSB and one or more resource elements carrying DMRS on a downlink shared channel from 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 at all. In some cases, the process may include additional features not described below, or further processes may be added.

[0106] In 505, base station 105-b may transmit a control message to UE 115-b. For example, 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 activated DCI. In some examples, 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 activated DCI message received in a CORESET which has 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] In 510, UE115-b may receive an SSB having a PCI, such as a PCI for a serving cell or another cell (e.g., a non-serving cell). In some cases, one or more resource elements carrying an SSB may overlap with one or more resource elements carrying a downlink shared channel, such as a PDSCH515, which has another PCI.

[0108] In 520, UE115-b may receive one or more DMRS signals from base station 105-b. For example, UE115-b may receive DMRS signals on a downlink shared channel such as PDSCH515.

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

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

[0111] In 530, UE115-b may compare the PCI of the SSB with the PCI of the PDSCH having the DMRS to determine whether resource element overlap is permitted. For example, UE115-b may determine whether overlap is permitted between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS in the downlink shared channel.

[0112] In some cases, under 535, UE115-b may determine that resource element duplication is not permitted. For example, UE115-b may determine that duplication is not permitted between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS, based on the fact that both PCIs are for a serving cell or for another cell, such as a non-serving cell.

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

[0114] In 545, UE115-b may process the DMRS based on the decision made in 530 as to whether resource element duplication is permitted.

[0115] Figure 6 shows a block diagram 600 of a device 605 that supports resource element overlap between an SSB and a DMRS according to an aspect of this disclosure. Device 605 may be an example of an aspect of UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. Device 605 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

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

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

[0118] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various forms of resource element overlap between SSB and DMRS as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof 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 (for example, in communications management circuits). 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, which are configured as means for performing the functions described herein or otherwise supporting such means. In some examples, a processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (for example, by the processor executing instructions stored in memory).

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

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

[0122] The communication manager 620 may support wireless communications in the UE in accordance with examples such as those disclosed herein. For example, the communication manager 620 may be configured as a means for receiving an SSB associated with a first PCI, wherein 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, or the means may be otherwise supported. The communication manager 620 may be configured as a means for determining, in accordance with a comparison of the first PCI and the second PCI, whether an overlap is permitted between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS corresponding to the downlink shared channel, or the means may be otherwise supported. The communication manager 620 may be configured as a means for processing the DMRS based on the determination, or the means may be otherwise supported.

[0123] By including or configuring the communications manager 620 in accordance with examples such as those described herein, the device 605 (e.g., a processor controlling the receiver 610, transmitter 615, communications manager 620, or a combination thereof, or optionally coupled thereto) can support a technique for the UE 115 to determine whether overlap is permitted between one or more resource elements carrying SSB and one or more resource elements carrying DMRS over the downlink shared channel, which can result in reduced processing, reduced power consumption, more efficient use of communications resources, and so on.

[0124] Figure 7 shows a block diagram 700 of a device 705 that supports resource element overlap between an SSB and a DMRS according to an aspect of this disclosure. Device 705 may be an example of an aspect of device 605 or UE115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. Device 705 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

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

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

[0127] Device 705, or its various components, may be examples of means for performing various forms of resource element overlap between SSB and DMRS as described herein. For example, the communications manager 720 may include the SSB component 725, the PCI component 730, the DMRS component 735, or any combination thereof. The communications manager 720 may be an example of a form of communications manager 620 as described herein. In some examples, the communications manager 720 or its various components may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in other ways in cooperation 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 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 the UE in accordance with examples such as those disclosed herein. The SSB component 725 is a means for receiving an SSB associated with a first PCI, wherein 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, or the means may be otherwise supported. The PCI component 730 is a means for determining, according to a comparison of the first PCI and the second PCI, whether an overlap is permitted between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS corresponding to the downlink shared channel, or the means may be otherwise supported. The DMRS component 735 is a means for processing the DMRS based on the determination, or the means may be otherwise supported.

[0129] Figure 8 shows a block diagram 800 of a communications manager 820 supporting resource element overlap between an SSB and a DMRS according to an aspect of this 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 means for implementing various aspects of resource element overlap between an SSB and a 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 (for example, via one or more buses).

[0130] The communications manager 820 may support wireless communications in the UE in accordance with examples such as those disclosed herein. The SSB component 825 is a means for receiving an SSB associated with a first PCI, wherein 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, or the means may be otherwise supported. The PCI component 830 is a means for determining, according to a comparison of the first PCI and the second PCI, whether an overlap is permitted between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS corresponding to the downlink shared channel, or the means may be otherwise supported. The DMRS component 835 is a means for processing the DMRS based on the determination, or the means may be otherwise supported.

[0131] In some examples, to support determining whether duplication is permitted, the PCI component 830 may be configured as a means for determining, or otherwise supporting, that duplication is not permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRSs, based on the fact that the first PCI and the second PCI correspond to serving cells.

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

[0133] In some examples, to support determining whether duplication is permitted, the PCI component 830 may be configured as a means for determining, or otherwise supporting, that duplication is not permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRSs, based on the fact that the first PCI and the second PCI correspond to a second cell.

[0134] In some examples, to support determining whether duplication is permitted, the PCI component 830 may be configured as a means for determining whether duplication is permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRSs, based on the fact that the first PCI corresponds to a serving cell and the second PCI corresponds to a second cell, or the means may be supported in other ways.

[0135] In some examples, to support determining whether duplication is permitted, the PCI component 830 may be configured as a means for determining whether duplication is permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRS, based on the fact that the first PCI corresponds to a second cell and the second PCI corresponds to a serving cell, or the means may be supported in other ways.

[0136] In some examples, the control message component 840 is a means for receiving a control message corresponding to a CORESET pool index value corresponding to a downlink shared channel, wherein the control message is configured to include a scheduling DCI message, or the means may be supported in other ways.

[0137] In some examples, the control message component 840 may be configured as 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, or it may support such a means in other ways.

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

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

[0140] In some examples, the control message is an SPS control message corresponding to the SPS configuration within the RRC message, and the SPS configuration indicates the CORESET pool index value.

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

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

[0143] Figure 9 shows a diagram of a system 900 including a device 905 that supports resource element overlap between an SSB and a DMRS, according to an aspect of this disclosure. Device 905 may be an example of, or include, a component of, device 605, device 705, or UE 115 as described herein. Device 905 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 905 may include components for bidirectional 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, a code 935, and a processor 940. These components may communicate electronically or, in some cases, be coupled via one or more buses (e.g., bus 945) (e.g., operably, communicatively, functionally, electronically, electrically).

[0144] The I / O controller 910 may manage input and output signals for device 905. The I / O controller 910 may also manage peripheral devices not integrated into 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, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of a processor, such as processor 940. In some cases, a user may interact with device 905 via the I / O controller 910 or through hardware components controlled by the I / O controller 910.

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

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

[0147] The processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, 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 memory (e.g., memory 930) to cause device 905 to perform various functions (e.g., functions or tasks supporting resource element overlap between SSB and DMRS). For example, device 905 or components of device 905 may include the processor 940 and memory 930 coupled to the processor 940, and the processor 940 and memory 930 may be configured to perform various functions described herein.

[0148] The communication manager 920 may support wireless communications in the UE in accordance with examples such as those disclosed herein. For example, the communication manager 920 may be configured as a means for receiving an SSB associated with a first PCI, wherein 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, or the means may be otherwise supported. The communication manager 920 may be configured as a means for determining, in accordance with a comparison of the first PCI and the second PCI, whether an overlap is permitted between one or more resource elements carrying the SSB and one or more resource elements carrying the DMRS corresponding to the downlink shared channel, or the means may be otherwise supported. The communication manager 920 may be configured as a means for processing the DMRS based on the determination, or the means may be otherwise supported.

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

[0150] In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the transceiver 915, 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, memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by the processor 940 to cause the device 905 to perform various aspects of resource element overlap between the SSB and DMRS as described herein, or the processor 940 and memory 930 may be otherwise configured to perform or support such operations.

[0151] Figure 10 shows a block diagram 1000 of a device 1005 that supports resource element overlap between an SSB and a DMRS according to an aspect of this disclosure. Device 1005 may be an example of a network entity that implements one or more aspects of a base station 105 as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. Device 1005 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

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

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

[0154] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof or various components thereof may be examples of means for performing various forms of resource element overlap between SSB and DMRS as described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof 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 (for example, in communications management circuits). The hardware may include a processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which are configured as means for performing the functions described herein or otherwise support such means. In some examples, a processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (for example, by the processor executing instructions stored in memory).

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

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

[0158] The communication manager 1020 may support wireless communications in a network entity implementing one or more embodiments of a base station in accordance with examples such as those disclosed herein. For example, the communication manager 1020 may be configured as a means for transmitting an SSB associated with a first PCI, wherein 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, or the means may be otherwise supported. The communication manager 1020 may be configured as a means for determining, in accordance with a comparison of the first PCI and the second PCI, whether an overlap is permitted between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to a downlink shared channel, or the means may be otherwise supported. The communication manager 1020 may be configured as a means for processing the DMRS based on the determination, or the means may be otherwise supported.

[0159] By including or configuring the communications manager 1020 in accordance with examples such as those described herein, the device 1005 (for example, a processor controlling the receiver 1010, transmitter 1015, communications manager 1020, or a combination thereof, or optionally coupled thereto) can support a technique for the UE 115 to determine whether overlap is permitted between one or more resource elements carrying SSB and one or more resource elements carrying DMRS over the downlink shared channel, which can result in reduced processing, reduced power consumption, more efficient use of communications resources, and so on.

[0160] Figure 11 shows a block diagram 1100 of a device 1105 that supports resource element overlap between an SSB and a DMRS according to an aspect of this disclosure. Device 1105 may be an example of an aspect of device 1005 or one or more aspects of base station 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. Device 1105 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

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

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

[0163] Device 1105, or its various components, may be examples of means for performing various forms of resource element overlap between SSB and DMRS as described herein. For example, communication manager 1120 may include SSB manager 1125, PCI manager 1130, DMRS manager 1135, or any combination thereof. Communication manager 1120 may be an example of a form of communication manager 1020 as described herein. In some examples, communication manager 1120, or its various components, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in other ways in cooperation with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, send information to transmitter 1115, or be integrated with receiver 1110, 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 embodiments of a base station in accordance with examples such as those disclosed herein. The SSB manager 1125 is configured, or otherwise supports, means for transmitting an SSB associated with a first PCI, wherein 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 is configured, or otherwise supports, means for determining, in accordance with a comparison of the first PCI and the second PCI, whether an overlap is permitted 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 DMRS manager 1135 is configured, or otherwise supports, means for processing the DMRS based on the determination.

[0165] Figure 12 shows a block diagram 1200 of a communications manager 1220 supporting resource element overlap between an SSB and a DMRS according to an aspect of this disclosure. The communications manager 1220 may be an example of an aspect of communications manager 1020, communications manager 1120, or both, as described herein. The communications manager 1220, or various components thereof, may be an example of means for performing various aspects of resource element overlap between an SSB and a DMRS as described herein. For example, 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 each other directly or indirectly (for example, via one or more buses).

[0166] The communications manager 1220 may support wireless communications in a network entity implementing one or more embodiments of a base station in accordance with examples such as those disclosed herein. The SSB manager 1225 is configured, or may otherwise support, means for transmitting an SSB associated with a first PCI, wherein 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 is configured, or may otherwise support, means for determining, based on a comparison of the first PCI and the second PCI, whether an overlap is permitted 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 DMRS manager 1235 is configured, or may otherwise support, means for processing the DMRS based on the determination.

[0167] In some examples, the PCI manager 1230 may be configured as a means for determining, or otherwise supporting, that there is no overlap between one or more resource elements carrying SSBs and one or more resource elements carrying DMRSs, based on the fact that the first PCI and the second PCI correspond to serving cells.

[0168] In some examples, the PCI manager 1230 may be configured as a means for determining, or otherwise supporting, that there is no overlap between one or more resource elements carrying SSBs and one or more resource elements carrying DMRSs, based on the fact that the first PCI and the second PCI are the same PCI.

[0169] In some examples, the PCI manager 1230 may be configured as a means for determining, or otherwise supporting, that there is no overlap between one or more resource elements carrying SSBs and one or more resource elements carrying DMRSs, based on the fact that the first PCI and the second PCI correspond to the second cell.

[0170] In some examples, the PCI manager 1230 may be configured, or otherwise support, a means for determining whether one or more resource elements carrying SSBs and one or more resource elements carrying DMRSs overlap, based on the fact that a first PCI corresponds to a serving cell and a second PCI corresponds to a second cell.

[0171] In some examples, the PCI manager 1230 may be configured, or otherwise support, a means for determining whether one or more resource elements carrying SSBs and one or more resource elements carrying DMRSs overlap, based on the fact that a first PCI corresponds to a second cell and the second PCI corresponds to a serving cell.

[0172] In some examples, the control message manager 1240 may be configured as a means for sending control messages indicating the CORESET pool index value corresponding to the downlink shared channel, or it may support such means in other ways.

[0173] In some examples, the control message manager 1240 may be configured as 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, or it may support such a means in other ways.

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

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

[0176] In some examples, the control message is an SPS control message corresponding to the SPS configuration within the RRC message, and the SPS configuration indicates the CORESET pool index value.

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

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

[0179] Figure 13 shows a diagram of a system 1300 including a device 1305 that supports resource element overlap between an SSB and a DMRS, according to an aspect of this disclosure. Device 1305 may be an example of, or include, a device 1005, device 1105, or a component of a network entity that implements one or more aspects of a base station 105 as described herein. Device 1305 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 1305 may include components for bidirectional 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, a code 1335, a processor 1340, and an inter-station communications manager 1345. These components may communicate electronically or, in some cases, be coupled via one or more buses (e.g., bus 1350) (e.g., operably, communicatively, functionally, electronically, electrically).

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

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

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

[0183] The processor 1340 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, 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 memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks supporting resource element overlap between SSB and DMRS). For example, device 1305 or components of device 1305 may include the processor 1340 and memory 1330 coupled to the processor 1340, and the processor 1340 and memory 1330 may be configured to perform various functions described herein.

[0184] The inter-station communication manager 1345 can manage communication with other base stations 105 and may include a controller or scheduler to coordinate communication with the UE 115 in cooperation with other base stations 105. For example, the inter-station communication 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 communication manager 1345 may provide an X2 interface within the LTE / LTE-A wireless communication network technology for communication between base stations 105.

[0185] The communication manager 1320 may support wireless communications in a network entity implementing one or more embodiments of a base station in accordance with examples such as those disclosed herein. For example, the communication manager 1320 may be configured, or otherwise support, means for transmitting an SSB associated with a first PCI, wherein 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 communication manager 1320 may be configured, or otherwise support, means for determining, based on a comparison of the first PCI and the second PCI, whether an overlap is permitted between one or more resource elements carrying the SSB and one or more resource elements carrying a DMRS corresponding to a downlink shared channel. The communication manager 1320 may be configured, or otherwise support, means for processing the DMRS based on the determination.

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

[0187] In some examples, the communications manager 1320 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the transceiver 1315, 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, memory 1330, code 1335, or any combination thereof. For example, code 1335 may include instructions that can be executed by the processor 1340 to cause device 1305 to perform various forms of resource element overlap between SSB and DMRS as described herein, or the processor 1340 and memory 1330 may be otherwise configured to perform or support such operations.

[0188] Figure 14 shows a flowchart illustrating method 1400 for supporting resource element overlap between an SSB and a DMRS, according to aspects of this disclosure. The operation of method 1400 may be implemented by a UE or its components as described herein. For example, the operation of method 1400 may be performed by UE 115, as described with reference to Figures 1 to 9. In some examples, the UE may execute a set of instructions for controlling functional elements of the UE to perform the functions described. Additional or alternative, the UE may perform aspects of the functions described using dedicated hardware.

[0189] In 1405, the method may include receiving an SSB associated with a first PCI, wherein 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 operation of 1405 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1405 may be performed by an SSB component 825 as described with reference to Figure 8.

[0190] In 1410, the method may include determining whether overlap is permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRS corresponding to downlink shared channels, according to a comparison of a first PCI and a second PCI. The operation of 1410 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1410 may be performed by a PCI component 830 as described with reference to Figure 8.

[0191] In 1415, the method may include processing the DMRS based on the decision. The operation of 1415 may be carried out according to examples such as those disclosed herein. In some examples, the operation of 1415 may be carried out by a DMRS component 835, as described with reference to Figure 8.

[0192] Figure 15 shows a flowchart illustrating method 1500 for supporting resource element overlap between an SSB and a DMRS, according to aspects of this disclosure. The operation of method 1500 may be implemented by a UE or its components as described herein. For example, the operation of method 1500 may be performed by UE 115, as described with reference to Figures 1 to 9. In some examples, the UE may execute a set of instructions for controlling functional elements of the UE to perform the functions described. Additionally or alternatively, the UE may perform aspects of the functions described using dedicated hardware.

[0193] In 1505, the method may include receiving an SSB associated with a first PCI, wherein 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 operation of 1505 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1505 may be performed by an SSB component 825 as described with reference to Figure 8.

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

[0195] In 1515, the method may include determining that no overlap is permitted between one or more resource elements carrying an SSB and one or more resource elements carrying a DMRS, based on the fact that the first PCI and the second PCI correspond to or are the same serving cell. The operation of 1515 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1515 may be performed by a PCI component 830 as described with reference to Figure 8.

[0196] In 1520, the method may include processing the DMRS based on the decision. The operation of 1520 may be carried out according to examples such as those disclosed herein. In some examples, the operation of 1520 may be carried out by a DMRS component 835, as described with reference to Figure 8.

[0197] Figure 16 shows a flowchart illustrating method 1600 for supporting resource element overlap between an SSB and a DMRS, according to aspects of this disclosure. The operation of method 1600 may be implemented by a UE or its components as described herein. For example, the operation of method 1600 may be performed by a UE 115 as described with reference to Figures 1 to 9. In some examples, the UE may execute a set of instructions for controlling a functional element of the UE to perform the functions described. Additionally or alternatively, the UE may perform aspects of the functions described using dedicated hardware.

[0198] In 1605, the method may include receiving an SSB associated with a first PCI, wherein 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 operation of 1605 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1605 may be performed by an SSB component 825 as described with reference to Figure 8.

[0199] In 1610, the method may include determining whether overlap is permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRS corresponding to downlink shared channels, according to a comparison of a first PCI and a second PCI. The operation of 1610 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1610 may be performed by a PCI component 830 as described with reference to Figure 8.

[0200] In 1615, the method may include determining that no overlap is permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRSs, based on the fact that the first PCI and the second PCI correspond to the second cell. The operation of 1615 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1615 may be performed by a PCI component 830 as described with reference to Figure 8.

[0201] In 1620, the method may include processing the DMRS based on the decision. The operation of 1620 may be carried out according to examples such as those disclosed herein. In some examples, the operation of 1620 may be carried out by a DMRS component 835, as described with reference to Figure 8.

[0202] Figure 17 shows a flowchart illustrating method 1700 for supporting resource element overlap between an SSB and a DMRS, according to aspects of this disclosure. The operation of method 1700 may be implemented by a UE or its components as described herein. For example, the operation of method 1700 may be performed by UE 115, as described with reference to Figures 1 to 9. In some examples, the UE may execute a set of instructions for controlling functional elements of the UE to perform the functions described. Additionally or alternatively, the UE may perform aspects of the functions described using dedicated hardware.

[0203] In 1705, the method may include receiving an SSB associated with a first PCI, wherein 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 operation of 1705 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1705 may be performed by an SSB component 825 as described with reference to Figure 8.

[0204] In 1710, the method may include determining whether overlap is permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRS corresponding to downlink shared channels, according to a comparison of a first PCI and a second PCI. The operation of 1710 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1710 may be performed by a PCI component 830 as described with reference to Figure 8.

[0205] In 1715, the method may include determining that overlap is permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRSs, based on the fact that the first PCI corresponds to a serving cell and the second PCI corresponds to a second cell. The operation of 1715 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1715 may be performed by a PCI component 830 as described with reference to Figure 8.

[0206] In 1720, the method may include processing the DMRS based on the decision. The operation of 1720 may be carried out according to examples such as those disclosed herein. In some examples, the operation of 1720 may be carried out by a DMRS component 835, as described with reference to Figure 8.

[0207] Figure 18 shows a flowchart illustrating method 1800 for supporting resource element overlap between an SSB and a DMRS, according to aspects of this disclosure. The operation of method 1800 may be implemented by a UE or its components as described herein. For example, the operation of method 1800 may be performed by UE 115, as described with reference to Figures 1 to 9. In some examples, the UE may execute a set of instructions for controlling functional elements of the UE to perform the functions described. Additionally or alternatively, the UE may perform aspects of the functions described using dedicated hardware.

[0208] In 1805, the method may include receiving an SSB associated with a first PCI, wherein 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 operation of 1805 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1805 may be performed by an SSB component 825 as described with reference to Figure 8.

[0209] In 1810, the method may include determining whether overlap is permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRS corresponding to downlink shared channels, according to a comparison of a first PCI and a second PCI. The operation of 1810 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1810 may be performed by a PCI component 830 as described with reference to Figure 8.

[0210] In 1815, the method may include determining that overlap is permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRSs, based on the fact that the first PCI corresponds to a second cell and the second PCI corresponds to a serving cell. The operation of 1815 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1815 may be performed by a PCI component 830 as described with reference to Figure 8.

[0211] In 1820, the method may include processing the DMRS based on the decision. The operation of 1820 may be carried out according to examples such as those disclosed herein. In some examples, the operation of 1820 may be carried out by a DMRS component 835, as described with reference to Figure 8.

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

[0213] In 1905, the method may include transmitting an SSB associated with a first PCI, wherein 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 operation of 1905 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1905 may be performed by an SSB manager 1225 as described with reference to Figure 12.

[0214] In 1910, the method may include determining whether overlap is permitted between one or more resource elements carrying SSBs and one or more resource elements carrying DMRS corresponding to downlink shared channels, according to a comparison of a first PCI and a second PCI. The operation of 1910 may be performed according to examples such as those disclosed herein. In some examples, the operation of 1910 may be performed by a PCI manager 1230, as described with reference to Figure 12.

[0215] In 1915, the method may include processing the DMRS based on the decision. The operation of 1915 may be carried out according to examples such as those disclosed herein. In some examples, the operation of 1915 may be carried out by a DMRS manager 1235, as described with reference to Figure 12.

[0216] The following provides an overview of the aspects of this disclosure.

[0217] Embodiment 1: A method for wireless communication in a UE, comprising the steps of: 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 an overlap is permitted between the one or more resource elements carrying the synchronization signal block and the one or more resource elements carrying a demodulated reference signal corresponding to the downlink shared channel; and processing the demodulated reference signal at least in part based on the determination.

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

[0219] Embodiment 3: The method of Embodiment 1, wherein the step of determining whether duplication is permitted includes determining that duplication is not permitted between one or more resource elements carrying a synchronization signal block and one or more resource elements carrying a demodulation reference signal, at least on the basis that a first physical layer cell identifier and a second physical layer cell identifier correspond to a second cell.

[0220] Embodiment 4: The method of Embodiment 1, wherein the step of determining whether duplication is permitted includes determining that duplication is permitted between one or more resource elements carrying a synchronization signal block and one or more resource elements carrying a demodulation reference signal, at least on the basis that a first physical layer cell identifier corresponds to a serving cell and a second physical layer cell identifier corresponds to a second cell.

[0221] Embodiment 5: The method of Embodiment 1, wherein the step of determining whether duplication is permitted includes determining that duplication is permitted between one or more resource elements carrying a synchronization signal block and one or more resource elements carrying a demodulation reference signal, at least on the basis that a first physical layer cell identifier corresponds to a second cell and the second physical layer cell identifier corresponds to a serving cell.

[0222] Embodiment 6: A method according to any one of Embodiments 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, wherein the control message includes a scheduling downlink control information message.

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

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

[0225] Embodiment 9: Any method of Embodiments 6 to 8, wherein the control message is a semi-persistent scheduling control message corresponding to an activation downlink control information message received in a control resource set associated with a control resource set pool index value.

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

[0227] Embodiment 11: Any method of Embodiments 1 to 10, further comprising the step of determining that a downlink shared channel is associated with a serving cell, at least in part on the fact that a pseudo-collocation relationship corresponding to a synchronization signal block is associated with a serving cell.

[0228] Embodiment 12: Any method of Embodiments 1 to 11, further comprising the step of determining that a downlink shared channel is associated with a second cell, at least in part on the fact that a pseudo-collocation relationship corresponding to a synchronization signal block is associated with a second cell.

[0229] Embodiment 13: A method for wireless communication in a network entity, comprising the steps of: 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 an overlap is permitted between one or more resource elements carrying the synchronization signal block and one or more resource elements carrying a demodulated reference signal corresponding to a downlink shared channel; and processing the demodulated reference signal at least in part based on the determination.

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

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

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

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

[0234] Embodiment 18: Any method of Embodiments 13 to 17, further comprising the step of sending a control message indicating a control resource set pool index value corresponding to a downlink shared channel.

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

[0236] Embodiment 20: Any method of Embodiments 18 to 19, further comprising the step of determining that a downlink shared channel is associated with a second cell, at least in part on the fact that the control resource set pool index value is 1.

[0237] Embodiment 21: Any method of Embodiments 18 to 20, wherein the control message is a semi-persistent scheduling control message corresponding to an activation downlink control information message received in a control resource set associated with a control resource set pool index value.

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

[0239] Embodiment 23: Any method of Embodiments 13 to 22, further comprising the step of determining that a downlink shared channel is associated with a serving cell, at least in part on the fact that a pseudo-collocation relationship corresponding to a synchronization signal block is associated with a serving cell.

[0240] Embodiment 24: Any method of Embodiments 13 to 22, further comprising the step of determining that a downlink shared channel is associated with a second cell, at least in part on the fact that a pseudo-collocation relationship corresponding to a synchronization signal block is associated with a second cell.

[0241] Embodiment 25: A device for wireless communication in a UE, comprising a processor, a memory coupled to the processor, and instructions stored in the memory that can be executed by the processor to cause the device to perform any of the methods of Embodiments 1 to 12.

[0242] Embodiment 26: Apparatus for wireless communication in a UE, comprising at least one means for performing any of the methods of Embodiments 1 to 12.

[0243] Embodiment 27: A non-temporary computer-readable medium for storing code for wireless communication in a UE, wherein the code includes instructions that can be executed by a processor to perform any of Embodiments 1 to 12.

[0244] Embodiment 28: A device for wireless communication in a network entity, comprising a processor, a memory coupled to the processor, and instructions stored in the memory that can be executed by the processor to cause the device to perform any of the methods of Embodiments 13 to 24.

[0245] Embodiment 29: An apparatus for wireless communication in a network entity, comprising at least one means for performing any of the methods of Embodiments 13 to 24.

[0246] Embodiment 30: A non-temporary computer-readable medium for storing code for wireless communication in a network entity, wherein the code includes instructions that can be executed by a processor to perform any of the methods of Embodiments 13 to 24.

[0247] It should be noted that the methods described herein represent possible implementations, that the operations and steps may be reconfigured or otherwise modified, and that other implementations are possible. Furthermore, two or more embodiments of the methods may be combined.

[0248] While embodiments of LTE, LTE-A, LTE-A Pro, or NR systems may be described as examples, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used extensively in the description, the techniques described herein are applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR. For example, the techniques described may be applicable to various other wireless communication systems such as Ultra-Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and wireless technologies not expressly mentioned herein.

[0249] The information and signals described herein may be represented using any of the following different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips which may be mentioned throughout this description may be represented by voltage, electric current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0250] The various exemplary blocks and components described in this disclosure may be implemented or run using general-purpose processors, DSPs, ASICs, CPUs, FPGAs or other programmable logic devices, 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, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working 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 accompanying claims. For example, due to the nature of the 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 the distribution of parts of the functions so that they are implemented in various physical locations.

[0252] Computer-readable media include both non-temporary computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location to another. Non-temporary storage media can be any available media that can be accessed by a general-purpose computer or a dedicated computer. Examples, but not limited to, non-temporary 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-temporary media 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 computer or a dedicated computer or a general-purpose processor or a dedicated processor. Any connection is also appropriately referred to as computer-readable media. For example, if 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, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable media. As used herein, disk and disc include CD, laserdisc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray® disc, where disk typically reproduces data magnetically and disc optically using a laser. Any combination of the above is also included in the scope of computer-readable media.

[0253] When used herein, including within the claims, “or” in a list of items (for example, 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 when 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 interpreted as a reference to a closed set of conditions. For example, an exemplary step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, the phrase “based on” as used herein should be interpreted similarly to the phrase “at least partially based on.”

[0254] The term "decide" or "make a decision" encompasses a wide variety of actions, and therefore "making a decision" can include calculating, calculating, processing, deriving, investigating, looking up (such as by looking up in a table, database, or another data structure), confirming, etc. It can also include receiving (such as receiving information), accessing (such as accessing data in memory), etc. Furthermore, "making a decision" can include resolving, selecting, choosing, establishing, and other such similar actions.

[0255] In the attached diagrams, 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 similar components. When only the 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 or other subsequent reference labels.

[0256] The descriptions provided herein with respect to the accompanying drawings describe exemplary configurations and do not represent all examples that may be implemented or that fall within the scope of the claims. The term “example” as used herein means “acting as an example, case, or illustration,” and does not mean “preferred” or “advantageous over other examples.” Detailed descriptions include specific details to facilitate understanding of the techniques described. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples described.

[0257] The descriptions herein are provided to enable those skilled in the art to create or use this disclosure. Various modifications of this disclosure will become 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 this disclosure. Accordingly, this disclosure should be given the broadest scope that corresponds to the principles and novel features disclosed herein, and is not limited to the examples and designs described herein. [Explanation of Symbols]

[0258] 100 Wireless Communication Systems 105 base stations, standalone base stations 105-a base station 105-b base station 110 coverage areas, geographical coverage areas 110-a Coverage Area 115 UE 115-a UE 115-b UE 120 backhaul links 125 Communication Link 130 Core Network 135 Device-to-device (D2D) communication links, D2D communication links 140 Access Network Entities 145 Access Network Transmitting Entities 150 IP services 200 Wireless Communication Systems 205 Downlink communication link 210 SSB, Serving Cell SSB, Non-Serving Cell SSB 215 DMRS 220 resource elements 225 PDSCH 235 Control Message 300 Resource 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 Flows 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 Device 910 I / O Controller 915 Transceiver 920 Communication Manager 925 Antenna 930 Memory 935 Code 940 Processor 945 Bus 1000 Block Diagram 1005 Device 1010 Receiver 1015 Transmitter 1020 Communication Manager 1100 Block Diagram 1105 Device 1110 Receiver 1115 Transmitter 1120 Communication Manager 1125 SSB Manager 1130 PCI Manager 1135 DMRS Manager 1200 Block Diagram 1220 Communication Manager 1225 SSB Manager 1230 PCI Manager 1235 DMRS Manager 1240 Control Message Manager I245 QCL Manager 1300 System ​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​

Claims

1. A method for wireless communication in user equipment (UE), A step of 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. The steps include determining whether duplication is permitted between the one or more resource elements that carry the synchronization signal block and the one or more resource elements that carry the demodulation reference signal corresponding to the downlink shared channel, based on a comparison of the first physical layer cell identifier and the second physical layer cell identifier, In response to the decision that the aforementioned duplication is permitted, the steps include processing the demodulated reference signal using information about the synchronization signal block, and A method that includes this.

2. The step of determining whether the aforementioned duplication is permitted is: A step of determining, at least in part, that no overlap is permitted between the one or more resource elements that carry the synchronization signal block and the one or more resource elements that carry the demodulation reference signal, based at least in part on the fact that the first physical layer cell identifier and the second physical layer cell identifier are the same physical layer cell identifier, or A step of determining that no overlap is permitted between the one or more resource elements that carry the synchronization signal block and the one or more resource elements that carry the demodulation reference signal, based at least in part on the fact that the first physical layer cell identifier and the second physical layer cell identifier correspond to the second cell, or A step of determining that overlap is permitted between the one or more resource elements that carry the synchronization signal block and the one or more resource elements that carry the demodulation reference signal, at least in part on the fact that the first physical layer cell identifier corresponds to a serving cell and the second physical layer cell identifier corresponds to a second cell, or Steps to determine that overlap is permitted between the one or more resource elements that carry the synchronization signal block and the one or more resource elements that carry the demodulation reference signal, at least in part on the fact that the first physical layer cell identifier corresponds to a second cell and the second physical layer cell identifier corresponds to a serving cell. The method according to claim 1, including the method described in claim 1.

3. The method according to claim 1, further comprising the step of receiving a control message corresponding to a control resource set pool index value corresponding to the downlink shared channel, wherein the control message includes a scheduling downlink control information message.

4. The step of determining that the downlink shared channel is associated with a serving cell, at least in part on the fact that the control resource set pool index value has a value of 0, or The step of determining that the downlink shared channel is associated with the second cell, at least in part on the fact that the control resource set pool index value is 1. The method according to claim 3, further comprising:

5. The control message is a semi-persistent scheduling control message corresponding to an activation downlink control information message received in the control resource set associated with the control resource set pool index value, or The method according to claim 3, wherein the control message is a semi-persistent scheduling control message corresponding to a semi-persistent scheduling configuration in a wireless resource control message, and the semi-persistent scheduling configuration indicates the control resource set pool index value.

6. The step of determining that the downlink shared channel is associated with the serving cell, at least in part on the fact that the pseudo-collocation relationship corresponding to the synchronization signal block is associated with the serving cell, or The step of determining that the downlink shared channel is associated with the second cell, at least in part on the fact that the pseudo-collocation relationship corresponding to the synchronization signal block is associated with the second cell. The method according to claim 1, further comprising:

7. A method for wireless communication in a network entity, A step of 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. The steps include determining whether duplication is permitted between the one or more resource elements that carry the synchronization signal block and the one or more resource elements that carry the demodulation reference signal corresponding to the downlink shared channel, based on a comparison of the first physical layer cell identifier and the second physical layer cell identifier, In response to the decision that the aforementioned duplication is permitted, the steps include processing the demodulated reference signal using information about the synchronization signal block, and A method that includes this.

8. A step of determining, at least partially based on the fact that the first physical layer cell identifier and the second physical layer cell identifier are the same physical layer cell identifier, that there is no overlap between the one or more resource elements that carry the synchronization signal block and the one or more resource elements that carry the demodulation reference signal, or The step of determining that there is no overlap between the one or more resource elements that carry the synchronization signal block and the one or more resource elements that carry the demodulation reference signal, based at least in part on the fact that the first physical layer cell identifier and the second physical layer cell identifier correspond to the second cell, or The step of 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, at least in part on the fact that the first physical layer cell identifier corresponds to a serving cell and the second physical layer cell identifier corresponds to a second cell, or The step of 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, at least in part on the fact that the first physical layer cell identifier corresponds to a second cell and the second physical layer cell identifier corresponds to a serving cell. The method according to claim 7, further comprising:

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

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

11. The control message is a semi-persistent scheduling control message corresponding to an activation downlink control information message received in the control resource set associated with the control resource set pool index value, or The method according to claim 9, wherein the control message is a semi-persistent scheduling control message corresponding to a semi-persistent scheduling configuration in a wireless resource control message, and the semi-persistent scheduling configuration indicates the control resource set pool index value.

12. The step of determining that the downlink shared channel is associated with the serving cell, at least in part on the fact that the pseudo-collocation relationship corresponding to the synchronization signal block is associated with the serving cell, or The step of determining that the downlink shared channel is associated with the second cell, at least in part on the fact that the pseudo-collocation relationship corresponding to the synchronization signal block is associated with the second cell. The method according to claim 7, further comprising:

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

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

15. A computer program comprising instructions, wherein, when executed by a computer, the instructions cause the computer to perform the method described in any one of claims 1 to 12.

Images