Patent Description:
The UTRAN is the radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), a third generation (<NUM>) mobile phone technology supported by the <NUM>rd Generation Partnership Project (3GPP).

A UE may communicate with a base station via downlink (DL) and uplink (UL). The DL (or forward link) refers to the communication link from the base station to the UE, and the UL (or reverse link) refers to the communication link from the UE to the base station. A base station may transmit data and control information on the downlink to a UE or may receive data and control information on the uplink from the UE.

Research and development continue to advance the UMTS technologies not only to meet the growing demand for mobile broadband access, but also to advance and enhance the user experience with mobile communications.

<CIT> provides systems, methods, apparatuses, and computer program products providing a flexible reference signal pattern definition for shorter transmission time interval (TTI).

The <NPL>, makes the following observation: Observation <NUM>: The DM-RS procedure in <NUM> should be interpreted such that DM-RS location is shifted only due to the LTE-CRS configuration, because if the higher layer parameter mbsfn-SubframeConfigList is configured such that there would be at least one subframe for which LTE-CRS collision is happening, then all DM-RS are shifted to keep the timeline operation at the UE semi-statically controlled. Observation <NUM>: Current RAN1 specification explicitly states that DM-RS location shifts whenever any DM-RS symbol symbol coincides with any symbol containing LTE cell-specific reference signals as indicated by the higher-layer parameter lte-CRS-ToMatchAround, without considering any frequency-domain overlap in the determination. Said draft also makes the following proposal: Proposal <NUM>: Capture in the Chairman Notes that in the current RAN1 specification DMRS location does not shift based on higher layer parameter mbsfn-SubframeConfigList. Proposal <NUM>: Capture in the Chairman Notes that in the current RAN1 specification, for the scenario of DM-RS location shifting described in Section <NUM>. <NUM> of TS <NUM>, If the NR PDSCH DM-RS with l<NUM>=<NUM> appears on the same symbol with LTE cell-specific reference signals as indicated by the higher-layer parameter lte-CRS-ToMatchAround, independent of any PRB-level overlap or not with the scheduled PDSCH, the DM-RS of the PDSCH is expected to be shifted to symbol l<NUM>=<NUM>.

The <NPL>, provides further analysis and consideration for M-DCI and S-DCI based multiple TRP/panel transmission and reliability/robustness enhancement in Rel-<NUM>.

The <NPL>, gives detailed considerations on DL design for multiple PDCCH based NCJT.

<CIT> discloses a method for receiving a downlink signal through an Enhanced Physical Downlink Control Channel (EPDCCH) in a wireless communication system by a user equipment (UE). The UE receives a parameter indicating a quasi co-location behavior type is. The UE further receives a demodulation reference signal (DMRS) associated with the EPDCCH. The UE attempts to decode the EPDCCH based on the DMRS. If a transmission mode configured in the UE is a transmission mode <NUM>, the UE assumes that antenna ports of the DMRS are quasi co-located with antenna ports of a reference signal determined by the parameter.

The systems, methods and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

An innovative aspect of the subject matter described in this disclosure can be implemented in a method of wireless communication, as defined in claim <NUM>.

In some implementations, the first transmission is associated with the CORESET group, and the second transmission is associated with a second CORESET group.

In some implementations, determining that the at least one list is configured for DMRS shifting indicates that one or more CRS patterns overlap with the first DMRS or the second DMRS.

In some implementations, the method can include determining, by the UE, whether one or more CRS patterns of the at least one list overlaps with the first DMRS or the second DMRS, and where modifying the at least one DMRS symbol of the first DMRS or the at least one DMRS symbol of the second DMRS is further responsive to determining that at least one CRS pattern of the one or more CRS patterns overlaps with at least one DMRS symbol of the first DMRS or the second DMRS.

In some implementations, the at least one list of CRS patterns being configured for the component carrier enables DMRS shifting, rate matching, or both.

In some implementations, modifying the at least one DMRS symbol of the first DMRS or the at least one DMRS symbol of the second DMRS can include modifying the at least one DMRS symbol of the first DMRS and the at least one DMRS symbol of the second DMRS.

In some implementations, the method can include receiving, by the UE, the first transmission, the first transmission having modified DMRS symbols.

Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication, as defined in claim <NUM>.

In some implementations, the apparatus is operating in a multiple downlink control information (DCI), multiple transmission reception point (TRP) mode.

In some implementations, a second CORESET group is associated with a second list of CRS patterns of the at least one list of CRS patterns.

In some implementations, the first message is received on a Physical Downlink Control Channel (PDCCH), and the first transmission is received on a Physical Downlink Shared Channel (PDSCH).

In some implementations, modifying the at least one DMRS symbol of the first DMRS or the second DMRS can include adjusting a location of the at least one DMRS symbol of the first DMRS.

In some implementations, modifying the at least one DMRS symbol of the first DMRS or the second DMRS can include: incrementing a location value of each DMRS symbol of the first DMRS of the first transmission by one; and incrementing a location value of each DMRS symbol of the second DMRS of the second transmission by one.

In some implementations, the apparatus performs DMRS shifting for multiple downlink control information (DCI), multiple transmission reception point (TRP) modes independent of CRS and TRP associations.

In some implementations, the apparatus performs DMRS shifting across multiple transmission reception points (TRPs), and the apparatus performs rate matching per TRP.

Another innovative aspect of the subject matter described in this disclosure can be implemented in a method of wireless communication, as defined in claim <NUM>.

In some implementations, the method can include: transmitting, by the network entity, the first transmission with a modified DMRS symbol; transmitting, by the network entity, the second transmission with a modified DMRS symbol; or both.

In some implementations, the first message corresponds to downlink control information (DCI).

In some implementations, the first message is a periodic grant and corresponds to downlink control information (DCI) or a Radio Resource Control (RRC) message that is configured to schedule multiple transmissions including the first transmission.

In some implementations, first resources of the first transmission at least partially overlap with second resources of the second transmission in a time domain, a frequency domain, or both.

In some implementations, first resources of the first transmission are orthogonal to second resources of the second transmission in a time domain, a frequency domain, or both.

In some implementations, first resources of the first transmission do not overlap with second resources of the second transmission in a time domain, a frequency domain, or both.

In some implementations, the first message corresponds to the CORESET group, the second message corresponds to a second CORESET group, and the CORESET groups are indicated by higher level signaling.

The following description is directed to certain implementations for the purposes of describing the innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways.

Wireless communications systems operated by different network entities may share spectrum. In some instances, two network entities may be configured to send transmissions to multiple user equipments (UE). Thus, in order to enable network entities to use more of the shared spectrum, and in order to mitigate interfering communications between the different network entities, certain resources may be shifted to avoid collisions and interference with an effort to enable successful reception and decoding.

For example, when a network entity and UE are operating in a single transmission reception point (TRP) mode, there are some cases where a demodulation reference signal (DMRS) is shifted to avoid collisions with a cell-specific reference signal (CRS) pattern or with reserved resources of a control resource set (CORESET). In other words, a location of the DMRS symbols may be shifted due to collisions with other resources.

However, when operating in multiple TRP modes, conventional networks and devices are unable to perform DMRS shifting. For example, when the two transmissions are at least partially overlapping, if the DMRS location for one of the transmissions is shifted due to collision of a corresponding CRS pattern, the alignment of the transmissions may be altered. If DMRS symbols of overlapping transmissions are not aligned, interference may occur to the DMRS symbols, or the UE may not be able to receive and decode one or more of the transmissions due to poor channel estimation performance. On the other hand, if alignment of the DMRS symbols of overlapping transmissions is ensured, and the DMRS ports of the overlapping transmissions are separate and belong to different code division multiplexing (CDM) groups, the actual DMRS resource elements (REs) become orthogonal in the frequency domain, which enhances the channel estimation performance. Thus, the implementations described herein enable procedures for performing DMRS shifting in multiple TRP modes. Such shifting may enable the alignment of the DMRS locations for both transmissions to enable reception and decoding of the transmissions by the UE. For example, the DMRS symbols of both transmissions may be shifted responsive to determining an overlap for one of the transmissions. Thus, both of the transmissions may be DMRS shifted and remain aligned with each other.

Particular implementations of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. For example, by enabling DMRS shifting for multiple TRP modes, a network may send overlapping transmissions to increase bandwidth and reduce latency. Additionally, the network may be able to operate in multi-TRP modes for carrier aggregation or dual connectivity, such as by using multiple signaling, multiple TRP modes.

This disclosure relates generally to providing or participating in authorized shared access between two or more wireless communications systems, also referred to as wireless communications networks. In various implementations, the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, 5th Generation (<NUM>) or new radio (NR) networks (sometimes referred to as "<NUM> NR" networks/systems/devices), as well as other communications networks. As described herein, the terms "networks" and "systems" may be used interchangeably.

A CDMA network may implement a radio technology such as universal terrestrial radio access (UTRA), cdma2000, and the like.

3GPP defines standards for the GSM EDGE (enhanced data rates for GSM evolution) radio access network (RAN), also denoted as GERAN. GERAN is the radio component of GSM/EDGE, together with the network that joins the base stations (for example, the Ater and Abis interfaces) and the base station controllers (A interfaces, etc.). The radio access network represents a component of a GSM network, through which phone calls and packet data are routed from and to the public switched telephone network (PSTN) and Internet to and from subscriber handsets, also known as user terminals or user equipments (UEs). A mobile phone operator's network may include one or more GERANs, which may be coupled with UTRANs in the case of a UMTS/GSM network. Additionally, an operator network may include one or more LTE networks, or one or more other networks. The various different network types may use different radio access technologies (RATs) and radio access networks (RANs).

UTRA, E-UTRA, and GSM are part of universal mobile telecommunication system (UMTS). 3GPP long term evolution (LTE) is a 3GPP project aimed at improving the universal mobile telecommunications system (UMTS) mobile phone standard. The present disclosure may describe certain aspects with reference to LTE, <NUM>, <NUM>, or NR technologies; however, the description is not intended to be limited to a specific technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Indeed, one or more aspects the present disclosure are related to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.

<NUM> networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using an OFDM-based unified, air interface. To achieve these goals, further enhancements to LTE and LTE-A are considered in addition to development of the new radio technology for <NUM> NR networks. The <NUM> NR will be capable of scaling to provide coverage (<NUM>) to a massive Internet of things (IoTs) with an ultra-high density (such as ~<NUM> nodes/km2), ultra-low complexity (such as ~<NUM> of bits/sec), ultra-low energy (such as ~<NUM>+ years of battery life), and deep coverage with the capability to reach challenging locations; (<NUM>) including mission-critical control with strong security to safeguard sensitive personal, financial, or classified information, ultra-high reliability (such as ~<NUM>% reliability), ultra-low latency (such as ∼<NUM> millisecond (ms)), and users with wide ranges of mobility or lack thereof; and (<NUM>) with enhanced mobile broadband including extreme high capacity (such as ∼ <NUM> Tbps/km2), extreme data rates (such as multi-Gbps rate, <NUM>+ Mbps user experienced rates), and deep awareness with advanced discovery and optimizations.

<NUM> NR devices, networks, and systems may be implemented to use optimized OFDM-based waveform features. These features may include scalable numerology and transmission time intervals (TTIs); a common, flexible framework to efficiently multiplex services and features with a dynamic, low-latency time division duplex (TDD)/frequency division duplex (FDD) design; and advanced wireless technologies, such as massive multiple input, multiple output (MIMO), robust millimeter wave (mmWave) transmissions, advanced channel coding, and device-centric mobility. Scalability of the numerology in <NUM> NR, with scaling of subcarrier spacing, may efficiently address operating diverse services across diverse spectrum and diverse deployments. For example, in various outdoor and macro coverage deployments of less than <NUM> FDD/TDD implementations, subcarrier spacing may occur with <NUM>, for example over <NUM>, <NUM>, <NUM>, <NUM>, and the like bandwidth. For other various outdoor and small cell coverage deployments of TDD greater than <NUM>, subcarrier spacing may occur with <NUM> over <NUM>/<NUM> bandwidth. For other various indoor wideband implementations, using a TDD over the unlicensed portion of the <NUM> band, the subcarrier spacing may occur with <NUM> over a <NUM> bandwidth. Finally, for various deployments transmitting with mmWave components at a TDD of <NUM>, subcarrier spacing may occur with <NUM> over a <NUM> bandwidth.

The scalable numerology of <NUM> NR facilitates scalable TTI for diverse latency and quality of service (QoS) requirements.

For clarity, certain aspects of the apparatus and techniques may be described below with reference to example <NUM> NR implementations or in a <NUM>-centric way, and <NUM> terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to <NUM> applications.

Moreover, it should be understood that, in operation, wireless communication networks adapted according to the concepts herein may operate with any combination of licensed or unlicensed spectrum depending on loading and availability. Accordingly, it will be apparent to one of ordinary skill in the art that the systems, apparatus and methods described herein may be applied to other communications systems and applications than the particular examples provided.

<FIG> is a block diagram illustrating details of an example wireless communication system. The wireless communication system may include wireless network <NUM>. The wireless network <NUM> may, for example, include a <NUM> wireless network. As appreciated by those skilled in the art, components appearing in <FIG> are likely to have related counterparts in other network arrangements including, for example, cellular-style network arrangements and non-cellular-style-network arrangements, such as device to device or peer to peer or ad hoc network arrangements, etc..

The wireless network <NUM> illustrated in <FIG> includes a number of base stations <NUM> and other network entities. A base station may be a station that communicates with the UEs and may be referred to as an evolved node B (eNB), a next generation eNB (gNB), an access point, and the like. Each base station <NUM> may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to this particular geographic coverage area of a base station or a base station subsystem serving the coverage area, depending on the context in which the term is used. In implementations of the wireless network <NUM> herein, base stations <NUM> may be associated with a same operator or different operators, such as the wireless network <NUM> may include a plurality of operator wireless networks. Additionally, in implementations of the wireless network <NUM> herein, the base stations <NUM> may provide wireless communications using one or more of the same frequencies, such as one or more frequency bands in licensed spectrum, unlicensed spectrum, or a combination thereof, as a neighboring cell. In some examples, an individual base station <NUM> or UE <NUM> may be operated by more than one network operating entity. In some other examples, each base station <NUM> and UE <NUM> may be operated by a single network operating entity.

A base station may provide communication coverage for a macro cell or a small cell, such as a pico cell or a femto cell, or other types of cell. A macro cell generally covers a relatively large geographic area, such as several kilometers in radius, and may allow unrestricted access by UEs with service subscriptions with the network provider. A small cell, such as a femto cell, would also generally cover a relatively small geographic area, such as a home, and, in addition to unrestricted access, may provide restricted access by UEs having an association with the femto cell, such as UEs in a closed subscriber group (CSG), UEs for users in the home, and the like. A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station or a home base station. In the example shown in <FIG>, base stations 105d and 105e are regular macro base stations, while base stations 105a-105c are macro base stations enabled with one of <NUM> dimension (3D), full dimension (FD), or massive MIMO. Base stations <NUM>-<NUM> take advantage of their higher dimension MIMO capabilities to exploit 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station which may be a home node or portable access point. A base station may support one or multiple cells, such as two cells, three cells, four cells, and the like.

In some scenarios, networks may be enabled or configured to handle dynamic switching between synchronous or asynchronous operations.

The UEs <NUM> are dispersed throughout the wireless network <NUM>, and each UE may be stationary or mobile. It should be appreciated that, although a mobile apparatus is commonly referred to as user equipment (UE) in standards and specifications promulgated by the 3rd Generation Partnership Project (3GPP), such apparatus may additionally or otherwise be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. Within the present document, a "mobile" apparatus or UE need not necessarily have a capability to move, and may be stationary. Some non-limiting examples of a mobile apparatus, such as may include implementations of one or more of the UEs <NUM>, include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a laptop, a personal computer (PC), a notebook, a netbook, a smart book, a tablet, and a personal digital assistant (PDA). A mobile apparatus may additionally be an "Internet of things" (IoT) or "Internet of everything" (IoE) device such as an automotive or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a logistics controller, a drone, a multi-copter, a quad-copter, a smart energy or security device, a solar panel or solar array, municipal lighting, water, or other infrastructure; industrial automation and enterprise devices; consumer and wearable devices, such as eyewear, a wearable camera, a smart watch, a health or fitness tracker, a mammal implantable device, gesture tracking device, medical device, a digital audio player (such as MP3 player), a camera, a game console, etc.; and digital home or smart home devices such as a home audio, video, and multimedia device, an appliance, a sensor, a vending machine, intelligent lighting, a home security system, a smart meter, etc. In one aspect, a UE may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, UEs that do not include UICCs may be referred to as IoE devices. The UEs 115a-115d of the implementation illustrated in <FIG> are examples of mobile smart phone-type devices accessing the wireless network <NUM> A UE may be a machine specifically configured for connected communication, including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like. The UEs 115e-<NUM> illustrated in <FIG> are examples of various machines configured for communication that access <NUM> network <NUM>.

A mobile apparatus, such as UEs <NUM>, may be able to communicate with any type of the base stations, whether macro base stations, pico base stations, femto base stations, relays, and the like. In <FIG>, a communication link (represented as a lightning bolt) indicates wireless transmissions between a UE and a serving base station, which is a base station designated to serve the UE on the downlink or uplink, or desired transmission between base stations, and backhaul transmissions between base stations. Backhaul communication between base stations of the wireless network <NUM> may occur using wired or wireless communication links.

In operation at the <NUM> network <NUM>, the base stations 105a-105c serve the UEs 115a and 115b using 3D beamforming and coordinated spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity. Macro base station 105d performs backhaul communications with the base stations 105a-105c, as well as small cell, the base station 105f. Macro base station 105d also transmits multicast services which are subscribed to and received by the UEs 115c and 115d.

The wireless network <NUM> of implementations supports mission critical communications with ultra-reliable and redundant links for mission critical devices, such the UE 115e, which is a drone. Redundant communication links with the UE 115e include from the macro base stations 105d and 105e, as well as small cell base station 105f. Other machine type devices, such as UE 115f (thermometer), the UE <NUM> (smart meter), and the UE <NUM> (wearable device) may communicate through the wireless network <NUM> either directly with base stations, such as the small cell base station 105f, and the macro base station 105e, or in multi-hop configurations by communicating with another user device which relays its information to the network, such as the UE 115f communicating temperature measurement information to the smart meter, the UE <NUM>, which is reported to the network through the small cell base station 105f. The <NUM> network <NUM> may provide additional network efficiency through dynamic, low-latency TDD/FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between the UEs 115i-<NUM> communicating with the macro base station 105e.

<FIG> is a block diagram conceptually illustrating an example design of a base station <NUM> and a UE <NUM>. The base station <NUM> and the UE <NUM> may be one of the base stations and one of the UEs in <FIG>. For a restricted association scenario (as mentioned above), the base station <NUM> may be the small cell base station 105f in <FIG>, and the UE <NUM> may be the UE 115c or 115b operating in a service area of the base station 105f, which in order to access the small cell base station 105f, would be included in a list of accessible UEs for the small cell base station 105f. Additionally, the base station <NUM> may be a base station of some other type. As shown in <FIG>, the base station <NUM> may be equipped with antennas 234a through 234t, and the UE <NUM> may be equipped with antennas 252a through 252r for facilitating wireless communications.

At the base station <NUM>, a transmit processor <NUM> may receive data from a data source <NUM> and control information from a controller/processor <NUM>. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid-ARQ (automatic repeat request) indicator channel (PHICH), physical downlink control channel (PDCCH), enhanced physical downlink control channel (EPDCCH), MTC physical downlink control channel (MPDCCH), etc. The data may be for the PDSCH, etc. The transmit processor <NUM> may process, such as encode and symbol map, the data and control information to obtain data symbols and control symbols, respectively. Additionally, the transmit processor <NUM> may generate reference symbols, such as for the primary synchronization signal (PSS) and secondary synchronization signal (SSS), and cell-specific reference signal. Transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing on the data symbols, the control symbols, or the reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) 232a through 232t. For example, spatial processing performed on the data symbols, the control symbols, or the reference symbols may include precoding. Each modulator <NUM> may process a respective output symbol stream, such as for OFDM, etc., to obtain an output sample stream. Each modulator <NUM> may additionally or alternatively process the output sample stream to obtain a downlink signal. For example, to process the output sample stream, each modulator <NUM> may convert to analog, amplify, filter, and upconvert the output sample stream to obtain the downlink signal. Downlink signals from modulators 232a through 232t may be transmitted via the antennas 234a through 234t, respectively.

At the UE <NUM>, the antennas 252a through 252r may receive the downlink signals from the base station <NUM> and may provide received signals to the demodulators (DEMODs) 254a through 254r, respectively. Each demodulator <NUM> may condition a respective received signal to obtain input samples. For example, to condition the respective received signal, each demodulator <NUM> may filter, amplify, downconvert, and digitize the respective received signal to obtain the input samples. Each demodulator <NUM> may further process the input samples, such as for OFDM, etc., to obtain received symbols. MIMO detector <NUM> may obtain received symbols from demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor <NUM> may process the detected symbols, provide decoded data for the UE <NUM> to a data sink <NUM>, and provide decoded control information to a controller/processor <NUM>. For example, to process the detected symbols, receive processor <NUM> may demodulate, deinterleave, and decode the detected symbols.

On the uplink, at the UE <NUM>, a transmit processor <NUM> may receive and process data (such as for the physical uplink shared channel (PUSCH)) from a data source <NUM> and control information (such as for the physical uplink control channel (PUCCH)) from the controller/processor <NUM>. Additionally, transmit processor <NUM> may generate reference symbols for a reference signal. The symbols from the transmit processor <NUM> may be precoded by TX MIMO processor <NUM> if applicable, further processed by the modulators 254a through 254r (such as for SC-FDM, etc.), and transmitted to the base station <NUM>. At base station <NUM>, the uplink signals from UE <NUM> may be received by antennas <NUM>, processed by demodulators <NUM>, detected by MIMO detector <NUM> if applicable, and further processed by receive processor <NUM> to obtain decoded data and control information sent by UE <NUM>. Receive processor <NUM> may provide the decoded data to data sink <NUM> and the decoded control information to controller/processor <NUM>.

Controllers/processors <NUM> and <NUM> may direct the operation at base station <NUM> and UE <NUM>, respectively. Controller/processor <NUM> or other processors and modules at base station <NUM> or controller/processor <NUM> or other processors and modules at UE <NUM> may perform or direct the execution of various processes for the techniques described herein, such as to perform or direct the execution illustrated in <FIG>, or other processes for the techniques described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. Scheduler <NUM> may schedule UEs for data transmission on the downlink or uplink.

In some cases, the UE <NUM> and the base station <NUM> may operate in a shared radio frequency spectrum band, which may include licensed or unlicensed, such as contention-based, frequency spectrum. In an unlicensed frequency portion of the shared radio frequency spectrum band, the UEs <NUM> or the base stations <NUM> may traditionally perform a medium-sensing procedure to contend for access to the frequency spectrum. For example, the UE <NUM> or base station <NUM> may perform a listen-before-talk or listen-before-transmitting (LBT) procedure such as a clear channel assessment (CCA) prior to communicating in order to determine whether the shared channel is available. A CCA may include an energy detection procedure to determine whether there are any other active transmissions. For example, a device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that a channel is occupied. Specifically, signal power that is concentrated in a certain bandwidth and exceeds a predetermined noise floor may indicate another wireless transmitter. In some implementations, a CCA may include detection of specific sequences that indicate use of the channel. For example, another device may transmit a specific preamble prior to transmitting a data sequence. In some cases, an LBT procedure may include a wireless node adjusting its own backoff window based on the amount of energy detected on a channel or the acknowledge/negative-acknowledge (ACK/NACK) feedback for its own transmitted packets as a proxy for collisions.

Use of a medium-sensing procedure to contend for access to an unlicensed shared spectrum may result in communication inefficiencies. This may be particularly evident when multiple network operating entities, such as network operators, are attempting to access a shared resource. In the <NUM> network <NUM>, the base stations <NUM> and the UEs <NUM> may be operated by the same or different network operating entities. In some examples, an individual base station <NUM> or UE <NUM> may be operated by more than one network operating entity. In other examples, each base station <NUM> and UE <NUM> may be operated by a single network operating entity. Requiring each base station <NUM> and UE <NUM> of different network operating entities to contend for shared resources may result in increased signaling overhead and communication latency.

<FIG> illustrates an example of a wireless communications system <NUM> that supports different multi-TRP schemes. In some examples, wireless communications system <NUM> may implement aspects of wireless communication system <NUM>. For example, wireless communications system <NUM> may include multiple UEs <NUM> and base stations <NUM>. The base stations <NUM> may communicate with the UEs <NUM> using TRPs <NUM>. Each base station <NUM> may have one or more TRPs <NUM>. For example, base station <NUM>-a may include TRP <NUM>-a and TRP <NUM>-b, while base station <NUM>-b may include TRP <NUM>-c. UE <NUM>-a may communicate with the network using a single TRP <NUM>, using multiple TRPs <NUM> corresponding to a single base station <NUM> (such as TRPs <NUM>-a and <NUM>-b at base station <NUM>-a), or using multiple TRPs <NUM> corresponding to multiple different base stations <NUM> (such as TRP <NUM>-a at base station <NUM>-a and TRP <NUM>-c at base station <NUM>-b, where base stations <NUM>-a and <NUM>-b may be connected via a backhaul connection).

In a communication scheme that includes multiple TRPs <NUM>, a single DCI message may configure the communications for the multiple TRPs <NUM>. In an example, base station <NUM>-a may communicate using a first TRP <NUM>-a and a second TRP <NUM>-b. Base station <NUM>-a may transmit DCI using TRP <NUM>-a on a PDCCH <NUM>-a to UE <NUM>-a. The DCI may include communication configuration information for the TCI state(s). The TCI state(s) may determine whether the communications correspond to single TRP communication or multiple TRP communication. The TCI state(s) also may indicate the type of communication scheme (such as TDM, FDM, SDM, etc.) configured for the communication. If the TCI configuration is one TCI state, the one TCI state may correspond to single TRP communication. If the TCI configuration is multiple TCI states, the multiple TCI states may correspond to communication with multiple TRPs. In some cases, the wireless communications system <NUM> may support up to M candidate TCI states for the purpose of quasi-co-location (QCL) indication. Of these M candidates (such as <NUM> candidate TCI states), a subset of TCI states may be determined based on a medium access control (MAC) control element (CE). The MAC-CE may correspond to a certain number (such as <NUM>N, such as <NUM> TCI states) of candidate TCI states for PDSCH QCL indication. One of these <NUM>N TCI states can be dynamically indicated in a message (such as DCI) using N bits.

The DCI on the PDCCH <NUM>-a may schedule PDSCH <NUM>-a transmissions from TRP <NUM>-a for single TRP communication configurations. Alternatively, the DCI on the PDCCH <NUM>-a may schedule multiple PDSCH <NUM> transmissions from multiple TRPs <NUM>. For example, the DCI may schedule PDSCH <NUM>-a transmissions from TRP <NUM>-a and PDSCH <NUM>-b transmissions from TRP <NUM>-b or PDSCH <NUM>-a transmissions from TRP <NUM>-a and PDSCH <NUM>-c transmission from TRP <NUM>-c for multiple TRP communication configurations. A UE <NUM> may be configured with a list of different candidate TCI states for the purpose of QCL indication. Each TCI code point in a DCI may correspond to one or more TCI states (such as corresponding to one or more reference signal (RS) sets for indicating the QCL relationships).

In cases where the network communicates with a UE <NUM> with TRPs <NUM>, whether in a single TRP configuration or a multiple TRP configuration, there may be multiple different schemes with which to communicate with the TRP(s) <NUM>. The TRP communication scheme may be determined by the TCI states. The TCI state(s) for communication on the PDSCH <NUM> may be indicated in the DCI by one or more bits, where the one or more bits indicate a TCI code point. The TCI code point in the DCI can correspond to one or more TCI states (such as either one or two TCI states). If the TCI code point in the DCI indicates one TCI state, the UE <NUM> is configured for single TRP operation. If the TCI code point in the DCI indicates two TCI states (and, correspondingly, two QCL relationships), the UE <NUM> is configured for multiple TRP operation. For example, if two TCI states are indicated within a TCI code point, each TCI state may correspond to one DMRS code division multiplexing (CDM) group.

In a first example multi-TRP scheme, TRPs <NUM> may communicate by utilizing SDM. In this case, different spatial layers may be transmitted from different TRPs <NUM> on the same RBs and symbols. Each TCI state also may correspond to different DMRS port groups. The DMRS ports in a DMRS CDM port group may be quasi-collocated (QCLed). This may allow a UE <NUM> to estimate each channel separately. In SDM, each antenna port used on the downlink may belong to a different CDM group. Base station <NUM>-a may indicate the antenna port groups using an antenna port(s) field in DCI.

The SDM scheme may include different TCI states within a single slot, where the TCI states overlap in time, frequency, or both. Different groups of spatial layers (which may correspond to different TCI states) may use the same modulation order. Cases where multiple groups use the same modulation order may be signaled through the modulation and coding scheme (MCS). In some cases, base station <NUM>-a may indicate the MCS in the DCI. In cases where the different groups of spatial layers use different modulation orders, each of the different modulation orders may be signaled to UE <NUM>-a. Different DMRS port groups may correspond to different TRPs, QCL relationships, TCI states, or a combination thereof.

In other examples of multi-TRP schemes, TRPs <NUM> may communicate with UE <NUM>-a by utilizing FDM or TDM communication schemes. In an FDM scheme, one set of RBs or a set of PRGs may correspond to a first TRP <NUM>-a and a first TCI state, and a second set of RBs or PRGs may correspond to a second TRP <NUM>-b and a second TCI state. The RBs allocated for each TRP may be distinct from each other, so that each TRP communicates on a designated set of RBs that are distinct form the other set of RBs (but may overlap in the same OFDM symbol). The frequency domain resource assignment field in the DCI may indicate both the first set and the second set or RBs or PRGs. In some cases, base station <NUM>-a may use additional signaling in the DCI to indicate which RBs belong to the first set and which belong to the second set. In some cases, the system may support a limited number of possibilities for allocating the frequency resources to the different TRPs (such as to reduce the overhead).

In a TDM scheme, a similar table of possibilities may be used to signal the resource allocation for different TRPs. In this case, each TRP is allocated to different sets of OFDM symbols rather than to different sets of RBs. Such a TDM scheme may support TDMed transmissions within a single slot (such as transmission time interval (TTI)). In some cases, a TDM scheme may implement slot aggregation, where transmissions using different TCI states may be spread across different slots (such as TTIs). In slot aggregation, the transmissions over the different TRPs may use separate rate matching, but may have the same or different modulation orders.

The network may communicate with UE <NUM>-a using multiple TRPs and any of the communication schemes described herein. Further, some communication schemes may include a combination of TDM and FDM, or cases where TDM may or may not be in a slot aggregation configuration. The schemes also may include some cases where rate matching is joint and some cases where rate matching is separate for different TRPs, and the schemes also may include cases where the different TRPs have the same or different modulation orders. Each scheme also may utilize different parameters that are included in signaling, such as which DMRS ports are used (such as for an SDM scheme) or how RBs are split up (such as for an FDM scheme).

To efficiently configure UE <NUM>-a with the TCI state information-and the corresponding TRP scheme-base station <NUM>-a may generate bits for a DCI message and may transmit the DCI on PDCCH <NUM>-a. The DCI message may be transmitted to UE <NUM>-a using TRP <NUM>-a. UE <NUM>-a may determine which scheme is configured for communication with TRPs <NUM> based on one or more fields of the received DCI. The DCI may be the same size across all communication schemes, and the formatting (such as a number of bits) of DCI fields may remain the same across the communication schemes.

<FIG> is a block diagram illustrating an example of a process flow for different multi-TRP schemes. <FIG> illustrates an example of a process flow <NUM> that supports different multi-TRP schemes. In some examples, process flow <NUM> may implement aspects of a wireless communications system <NUM> or <NUM>. For example, a base station <NUM> and UE <NUM>, such as base station <NUM>-c and UE <NUM>-b, may perform one or more of the processes described with reference to process flow <NUM>. Base station <NUM>-c may communicate with UE <NUM>-b by transmitting and receiving signals through TRPs <NUM>-a and <NUM>-b. In other cases, TRPs <NUM>-a and <NUM>-b may correspond to different base stations <NUM>. Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.

At <NUM>, base station <NUM>-c may generate DCI. The generation may include generating a first set of bits (such as a TCI field) that may indicate a set of TCI states for communication with UE <NUM>-b. The generation also may include generating a second set of bits (such as an antenna port(s) field) that may indicate a set of antenna ports and, in some cases, a multi-TRP communication scheme for multiple TRP communication operation. In some cases, the second set of bits may additionally indicate a modulation order for at least one TCI state (such as a second TCI state for TRP <NUM>-b), an RV for a TB for at least one TCI state (such as the second TCI state for TRP <NUM>-b), or a combination thereof.

At <NUM>, base station <NUM>-c may transmit the generated DCI to UE <NUM>-b. UE <NUM>-b may receive the DCI from base station <NUM>-c. The DCI may be transmitted on a PDCCH from TRP <NUM>-a. The DCI may schedule upcoming PDSCH transmissions and may include other control information. The DCI may include an indication of the first set of bits and the second set of bits. For example, the DCI may include coded bits based on the first set of bits and the second set of bits.

At <NUM>, UE <NUM>-b may read the TCI field (such as the first set of bits) received in the DCI message. UE <NUM>-b may identify, using the first set of bits, one or more TCI states for communication with base station <NUM>-c using one or more TRPs <NUM>.

At <NUM>, UE <NUM>-b may determine the TCI state configuration based on reading the TCI field of the DCI. For example, a value (such as tci-PresentInDCI) in the TCI field may not be configured for the CORESET scheduling the PDSCH, or the value may correspond to one TCI state. In these cases, the communication scheme may be configured for one TRP. In other cases, the TCI field value may correspond to more than one TCI state. In these other cases, the communication may be configured for communication with multiple TRPs.

UE <NUM>-b may read the antenna port(s) field of the DCI and may interpret the value of the field based on the determined TCI state configuration. For example, if UE <NUM>-b determines that the TCI field indicates a single TCI state, UE <NUM>-b may identify, using the second set of bits, a set of antenna ports for the PDSCH transmission. At <NUM>, UE <NUM>-b may access a table (such as pre-configured in memory or configured by the network) to determine one or more antenna ports corresponding to the antenna port(s) field value.

Alternatively, if UE <NUM>-b determines that the TCI field indicates multiple TCI states, UE <NUM>-b may identify, using the second set of bits, a set of antenna ports and a multi-TRP communication scheme based on identifying the set of TCI states. The second set of bits may include the same number of bits whether the field indicates just the set of antenna ports for single TRP operation or the set of antenna ports and the multi-TRP scheme for multi-TRP operation. At <NUM>, UE <NUM>-b may access a lookup table to determine the set of antenna ports and multi-TRP scheme based on the antenna port(s) field value. In some cases, UE <NUM>-b may select the lookup table from a set of lookup tables, where the set may include one lookup table to use for single TRP operation and one lookup table to use for multiple TRP operation.

The lookup table may include information mapping both the set of antenna ports and the multiple TRP scheme to the second set of bits. In some cases, the lookup table mapping both the set of antenna ports and the multiple TRP communication scheme to the second set of bits may be preconfigured in memory, and in some cases it may be dynamically configured by base station <NUM>-c. UE <NUM>-b may identify the second set of antenna ports and multiple TRP schemes based on the selected lookup table. In the lookup table for multi-TRP operation, along with indications of the DMRS ports, the table may include indications of the multiple TRP scheme (such as SDM, FDM, TDM, or some combination thereof). The antenna port(s) field lookup table may indicate that a value in the antenna port(s) field of the DCI corresponds to a set of DMRS ports, where the set of DMRS ports further corresponds to a communication scheme, such as SDM or FDM. The antenna port(s) field value also may indicate if rate matching is joint or separate. If the antenna port(s) field value indicates the use of an FDM communication scheme, the table may additionally indicate an RB configuration for the FDMed TCI states, as shown in the "Possibility" column of the table below. If the lookup tables are configurable by the network, the network may define the sets of possible DMRS ports and the type of schemes using radio resource control (RRC) signaling.

In some cases, UE <NUM>-b may identify, using the second set of bits, a modulation order for at least one TCI state of the set of possible TCI states. Different modulation orders also may be used across different TCI states. A first modulation order may be indicated in a modulation order field. The first modulation order may correspond to a first TCI state in a multi-TRP operation. A second modulation order may be indicated in one of the tables above based on the received value for the antenna port(s) field. For example, a column in the antenna port(s) field lookup table may indicates if the modulation order corresponding to the second TCI state is the same as the modulation order indicated in the MCS (i.e., the modulation order for the first TCI state). If the modulation order is not the same as the modulation order indicated in the MCS, the value of the modulation order for the second TCI state may be indicated in the antenna port(s) field. The value of the modulation order may be an absolute value or may be a relative value with respect to the first modulation order.

If the TCI state configuration is determined to indicate communication with a single TRP, UE <NUM>-b may receive a transmission from one TRP <NUM>-a at <NUM>. UE <NUM>-b may communicate with the single TRP <NUM>-a based on the determined communication scheme.

If the TCI state configuration is determined to indicate communication with multiple TRPs <NUM>, UE <NUM>-b may receive a transmission from one TRP <NUM>-a at <NUM> and also may receive a transmission from another TRP <NUM>-b at <NUM> (where, in some cases, <NUM> and <NUM> may correspond to a same time or OFDM symbol). UE <NUM>-b may communicate with the network via the multiple configured TRPs <NUM> based on the determined communication scheme.

Systems and methods described herein are directed to DMRS modifications for multiple messaging and multiple TRP modes. The DMRS modifications may enable enhanced or improved operation in multi-TRP modes. In some implementations, the systems and methods described herein enable DMRS shifting in multiple DCI based multi-TRP modes. Accordingly, such systems and methods can be utilized for multiple TRP modes.

<FIG> are diagrams illustrating different example multi-TRP schemes. Referring to <FIG>, examples of diagrams for different multiple TRP modes are illustrated. In <FIG>, a diagram illustrating carrier aggregation is illustrated. <FIG> depicts one base station 105a which communicates with UE 115a. Base station 105a may transmit data and control information; base station <NUM> may transmit (and receive) information using different equipment or settings (such as different frequencies). In <FIG>, a diagram illustrating dual connectivity is illustrated. <FIG> depicts two base stations, 105a and 105f, which communicate with UE 115a. UE 115a communicates data with both base stations and control information with one base station, main base station 105a.

<FIG> depict DCI based operations for multiple TRP modes. <FIG> depicts a single DCI operation mode, and <FIG> depicts a multiple DCI operation mode. In <FIG>, a system includes a first TRP 505a, a second TRP 505b, and a UE <NUM>. The second TRP 505b may be included with the first TRP 505a (such as two TRPs of first base station 105a of <FIG>) or may be separate from the first TRP 505a (such as a TRP from each of first and second base stations 105a and 105f, of <FIG>). In <FIG>, the first TRP 505a transmits downlink control information or DCIs, as illustrated by first PDCCH <NUM>. In <FIG>, the first PDCCH <NUM> schedules two PDSCHs, first PDSCH <NUM> and second PDSCH <NUM>.

Conversely, in <FIG>, both the first TRP 505a and the second TRP 505b transmit a DCI, as illustrated by PDCCHs <NUM> and <NUM>. Each PDCCH <NUM> and <NUM> schedules a corresponding PDSCH, PDSCHs <NUM>, <NUM>. The PDSCH resources can be overlapping, partially overlapping, or non-overlapping. For the PDCCHs <NUM> and <NUM>, different CORESETs or CORESET groups may be used for the two TRPs 505a and 505b (i.e., a first CORESET group for first transmissions for the first TRP 505a and a second CORESET group for second transmissions for the second TRP 505b). Each CORESET or CORESET group may have a different TCI state.

The CORESET groups may or may not be indicated to the UE. For example, when signaled to the UE, the CORESET groups may be indicated by higher layer signaling. The CORESET group information may be used for DMRS modifications, CRS rate matching, or both. As another example, when not signaled, the UE may be unaware of the CORESET groups and may not utilize the CORESET group data for DMRS modifications, CRS rate matching, or both.

<FIG> is a block diagram illustrating an example of a wireless communications system that enables DMRS modifications. <FIG> illustrates an example of a wireless communications system <NUM> that supports DMRS modifications. In some examples, wireless communications system <NUM> may implement aspects of wireless communication system <NUM>. For example, wireless communications system <NUM> may include network entity <NUM> (such as base station <NUM>), UE <NUM>, and optionally second network entity <NUM> (such as second base station <NUM> or a second TRP of base station <NUM>). DMRS modification operations may enable multi-DCI based multi-TRP operations and operation with other types of networks, such as LTE. Operating on multiple networks and bandwidth may enable increased throughput and reliability and reduced latency.

Network entity <NUM> and UE <NUM> may be configured to communicate via frequency bands, such as FR1 having a frequency of <NUM> to <NUM> or FR2 having a frequency of <NUM> to <NUM> for mm-Wave. It is noted that sub-carrier spacing (SCS) may be equal to <NUM>, <NUM>, <NUM>, or <NUM> for some data channels. Network entity <NUM> and UE <NUM> may be configured to communicate via one or more component carriers (CCs), such as representative first CC <NUM>, second CC <NUM>, third CC <NUM>, and fourth CC <NUM>. Although four CCs are shown, this is for illustration only, as more or fewer than four CCs may be used. One or more CCs may be used to communicate a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), a Physical Uplink Control Channel (PUCCH), or a Physical Uplink Shared Channel (PUSCH). In some implementations, such transmissions may be scheduled by dynamic grants. In some other implementations, such transmissions may be scheduled by one or more periodic grants and may correspond to semi-persistent scheduling (SPS) grants or configured grants of the one or more periodic grants.

Each periodic grant may have a corresponding configuration, such as configuration parameters/settings. The periodic grant configuration may include SPS configurations and settings. Additionally, or alternatively, one or more periodic grants (such as SPS grants thereof) may have or be assigned to a CC ID, such as intended CC ID.

Each CC may have a corresponding configuration, such as configuration parameters/settings. The configuration may include bandwidth, bandwidth part, hybrid automatic repeat request (HARQ) process, TCI state, RS, control channel resources, data channel resources, or a combination thereof. Additionally, or alternatively, one or more CCs may have or be assigned to a Cell ID, a Bandwidth Part (BWP) ID, or both. The Cell ID may include a unique cell ID for the CC, a virtual Cell ID, or a particular Cell ID of a particular CC of the plurality of CCs. Additionally, or alternatively, one or more CCs may have or be assigned to a HARQ ID. Each CC also may have corresponding management functionalities, such as, beam management, BWP switching functionality, or both. In some implementations, two or more CCs are quasi co-located, such that the CCs have the same beam or same symbol.

In some implementations, control information may be communicated via network entity <NUM> and UE <NUM>. For example, the control information may be communicated suing MAC-CE transmissions, RRC transmissions, DCI, transmissions, another transmission, or a combination thereof.

UE <NUM> includes processor <NUM>, memory <NUM>, transmitter <NUM>, receiver <NUM>, encoder, <NUM>, decoder <NUM>, DMRS modifier <NUM>, CRS rate matcher <NUM>, and antennas 252a-r. Processor <NUM> may be configured to execute instructions stored at memory <NUM> to perform the operations described herein. In some implementations, processor <NUM> includes or corresponds to controller/processor <NUM>, and memory <NUM> includes or corresponds to memory <NUM>. Memory <NUM> also may be configured to store DMRS data <NUM>, CRS data <NUM>, CORESET groups data <NUM>, modification parameter data <NUM>, or a combination thereof, as further described herein.

The DMRS data <NUM> corresponds to DMRS data of or associated with the network entity <NUM>, the second network entity <NUM>, or both. To illustrate, DMRS data <NUM> may include DMRS symbols for transmissions, such as PDSCH transmissions, and locations of the DMRS symbols in the transmissions. The CRS data <NUM> includes or corresponds to CRS data of or associated with the network entity <NUM>, the second network entity <NUM>, or both. To illustrate, CRS data <NUM> may include timing and location data for CRS data, often referred to as a CRS pattern. The CRS data <NUM> may include or indicate one or more CRS patterns, and may include or correspond to a CRS pattern parameter, such as lte-CRS-ToMatchAround. Some CRS pattern parameters, may include or be associated with multiple CRS patterns, (thus such CRS pattern parameters are known and referred to in the art as a list of CRS patterns). Such CRS pattern parameters (including lists) are known in the art as being associated with a particular component carrier as they are configured per component carrier.

The CORESET groups data <NUM> includes or corresponds to data which associates or links a network entity, such as a base station, cell, or TRP thereof, and optionally transmissions thereof, to a particular DMRS, a particular CRS pattern, or both. The CORESET groups data <NUM> may be indicated by higher layer signaling, such as RRC signaling (such as a configuration message). Alternatively, only the network entities include such association data, and the UE is unaware of such associations. In such implementations, the UE may perform DMRS modifications (such as shifting), CRS rate matching, or both independent of network entity associations.

The modification parameter data <NUM> includes or corresponds to data which is used by UE <NUM> to modify DMRS data <NUM>, such as configured to modify DMRS data <NUM> to generate modified DMRS data, such as <NUM>, <NUM>. The DMRS data <NUM> may further include modified DMRS data (<NUM>, <NUM>) of or associated with the network entity <NUM>, the second network entity <NUM>, or both. To illustrate, DMRS data <NUM> may include modified locations of the DMRS symbols in the transmissions.

Transmitter <NUM> is configured to transmit data to one or more other devices, and receiver <NUM> is configured to receive data from one or more other devices. For example, transmitter <NUM> may transmit data, and receiver <NUM> may receive data, via a network, such as a wired network, a wireless network, or a combination thereof. For example, UE <NUM> may be configured to transmit or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communications network now known or later developed within which permits two or more electronic devices to communicate. In some implementations, transmitter <NUM> and receiver <NUM> may be replaced with a transceiver. Additionally, or alternatively, transmitter <NUM>, receiver, <NUM>, or both may include or correspond to one or more components of UE <NUM> described with reference to <FIG>.

Encoder <NUM> and decoder <NUM> may be configured to encode and decode, such as encode or decode transmissions with modified DMRS locations, respectively. DMRS modifier <NUM> may be configured to perform DMRS modification. For example, DMRS modifier <NUM> is configured to modify a location of one or more DMRS symbols for a encoding or decoding transmission. To illustrate, responsive to determining collision or overlap with a CRS resource, a partial or full overlap with a second transmission, or both, the DMRS modifier <NUM> adjusts a location of the overlapping DMRS symbol. In some implementations, the DMRS modifier <NUM> adjusts, such as increments or decrements, the location of each DMRS symbol of each transmission, that is the DMRS symbols of the first and second transmissions.

CRS rate matcher <NUM> may be configured to perform CRS rate matching of a transmission (such as the first PDSCH transmitted from the first TRP associated with the first value of higher index or the first PDSCH transmitted from the first TRP associated with the first value of higher index) around a particular LTE CRS or LTE CRS pattern. Such rate matching procedures enable coexistence of NR and LTE as the data transmission of NR (such as the first PDSCH or the second PDSCH) is rate matched around one or more LTE CRS pattern(s).

Network entity <NUM> includes processor <NUM>, memory <NUM>, transmitter <NUM>, receiver <NUM>, encoder <NUM>, decoder <NUM>, DMRS modifier <NUM>, CRS rate matcher <NUM>, and antennas 234a-t. Processor <NUM> may be configured to execute instructions stores at memory <NUM> to perform the operations described herein. In some implementations, processor <NUM> includes or corresponds to controller/processor <NUM>, and memory <NUM> includes or corresponds to memory <NUM>. Memory <NUM> may be configured to store DMRS data <NUM>, CRS data <NUM>, CORESET group data <NUM>, modifying parameters <NUM>, or a combination thereof, similar to the UE <NUM> and as further described herein.

Transmitter <NUM> is configured to transmit data to one or more other devices, and receiver <NUM> is configured to receive data from one or more other devices. For example, transmitter <NUM> may transmit data, and receiver <NUM> may receive data, via a network, such as a wired network, a wireless network, or a combination thereof. For example, network entity <NUM> may be configured to transmit or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communications network now known or later developed within which permits two or more electronic devices to communicate. In some implementations, transmitter <NUM> and receiver <NUM> may be replaced with a transceiver. Additionally, or alternatively, transmitter <NUM>, receiver, <NUM>, or both may include or correspond to one or more components of network entity <NUM> described with reference to <FIG>. Encoder <NUM>, and decoder <NUM> may include the same functionality as described with reference to encoder <NUM> and decoder <NUM>, respectively. DMRS modifier <NUM> and CRS rate matcher <NUM> may include the same functionality as described with reference to DMRS modifier <NUM> and CRS rate matcher <NUM>, respectively.

During operation of wireless communications system <NUM>, network entity <NUM> may determine that UE <NUM> has DMRS shifting capability for multiple TRP operating modes, such as multi-DCI, multi-TRP operating modes. For example, UE <NUM> may transmit a message <NUM>, such as a capabilities message, that includes DMRS shifting indicator <NUM>. Indicator <NUM> may indicate enhanced DMRS shifting capability or a particular type of DMRS shifting, such as by incrementing location values. In some implementations, network entity <NUM> sends control information to indicate to UE <NUM> that DMRS shifting capability for multiple TRP operating modes is to be used. For example, in some implementations, message <NUM> (or another message, such as response or trigger message) is transmitted by the network entity <NUM>.

In the example of <FIG>, network entity <NUM> transmits an optional a configuration transmission <NUM>. The configuration transmission <NUM> may include or indicate a DMRS modification configuration, such as modifying parameters data <NUM>. The configuration transmission <NUM> (such as <NUM> thereof) may indicate how to adjust a location of DMRS symbols or what type of DMRS shifting mode to operate in, such as per TRP, across all TRPs, independent of CRS rate matching, etc..

After transmission of the message <NUM> (such as a DMRS shifting configuration message, such as a RRC message or a DCI), transmissions may be scheduled by the network entity <NUM>, the network entity <NUM>, the UE <NUM>, or both. Such scheduled transmissions may include shared channel transmissions, such as PDSCH or PUSCH. Such transmissions may be scheduled by dynamic grant or by periodic grant. The periodic grants are configured to schedule one or more SPS grants (such as PDSCHs).

In the example of <FIG>, the network entity <NUM> transmits a first message <NUM> and optionally transmits a second message <NUM>. For example, the network entity <NUM> is a base station that include multiple TRPs, and different TRPs transmit the messages <NUM>, <NUM>. In some other implementations, the second network entity <NUM> transmits the second message <NUM>. For example, in such implementations, each of the network entities <NUM>, <NUM> may include or correspond to a TRP of different panels or of different base stations.

First and second message <NUM>, <NUM> may include or correspond to DCIs or RRC messages and may be sent via corresponding PDCCHs. The first message <NUM> and the second message <NUM> each schedule one or more corresponding downlink transmissions. In the example of <FIG>, the first message <NUM> schedules first transmission <NUM> and the second message <NUM> schedules second transmission <NUM>.

Each of the first message <NUM> and the second message <NUM> has or is associated with a corresponding DMRS for the corresponding downlink transmission or transmissions. In <FIG>, these corresponding DMRSs include a first DMRS <NUM> of or associated with the first transmission <NUM> and a second DMRS <NUM> of or associated with the second transmission <NUM>. In some implementations, the first DMRS <NUM> and the second DMRS <NUM> are similar. For example, they have the same number of DMRS symbols and the DMRS symbols are located in the symbol position or slot, referred to as symbol location.

Additionally, each of the first message <NUM> and the second message <NUM> has or is associated with a corresponding CRS. The CRS may be associated with the particular network entity that transmits the message, or may be associated with a particular value of the higher layer index configured per CORESET (i.e., associated with a CORESET group representing a TRP). To illustrate, each TRP may have an associated CRS pattern. Alternatively, a single CRS pattern may be used for multiple TRPs, such as multiple TRPs of a single base station or serving cell. When multiple CRS patterns are used, the UE <NUM>, the network entity <NUM>, the network entity <NUM>, or a combination thereof, may generate a combined CRS pattern, such as a union of CRS patterns which includes each of the resources of the multiple CRS patterns.

After transmission of the first message <NUM>, the second message <NUM>, or both, the UE <NUM>, the network entity <NUM>, the network entity <NUM>, or a combination thereof, may determine whether the one or more associated CRS patterns overlap the associated DMRS of the first message <NUM> or the second message <NUM>. Although not illustrated in <FIG>, the CRS patterns may be sent in messages <NUM>, <NUM> or other messages, such as by RRC message or configuration.

To illustrate, the UE <NUM> may determine whether any resources of the one or more associated CRS patterns overlap any resources, such as DMRS symbols, of the first and second DMRS <NUM>, <NUM> for the first and second transmissions <NUM>, <NUM> indicated by messages <NUM>, <NUM>. Responsive to determining no overlap, the UE <NUM> may refrain from performing DMRS shifting. For example, the UE <NUM> may refrain from determining whether one or more CRS resource and DMRS symbols overlap. As another example, the UE <NUM> may refrain from modifying or not modify, such as shift, DMRS symbols even though the UE <NUM> determines that one or more CRS resource and DMRS symbols overlap.

Responsive to determining an overlap, the UE <NUM> may performing DMRS shifting. In some implementations, the above determination is only performed when the first transmission <NUM> and the second transmission <NUM> at least partially overlap in time, frequency, or both. In such implementations, the above determination is not performed when the first transmission <NUM> and the second transmission <NUM> do not overlap, such as when the resources thereof (such as resource blocks (RBs)) are orthogonal and the CRS pattern does not have an association with the first transmission, or optionally any transmission. Examples of overlapping include partial overlap of the first transmission <NUM> with the second transmission <NUM> in time, frequency, or both, or full overlap of the first transmission <NUM> with the second transmission <NUM> in time, frequency, or both. As an illustrative example, if the transmissions <NUM>, <NUM> are frequency division multiplexed, they may be partially or fully overlapping in the time domain, such as by occupying at least one common ODFM symbol in orthogonal resource blocks.

The UE <NUM> and the network entity <NUM> or network entities <NUM> and <NUM> modify DMRS <NUM>, <NUM> to generate modified DMRS <NUM>, <NUM>. The transmissions <NUM>, <NUM> include the modified DMRS, that is DMRS <NUM> and <NUM>, respectively.

Network entity <NUM> or network entities <NUM> and <NUM> may encode the transmissions <NUM>, <NUM> to be transmitted, such as via the same serving cell (such as a same CC) or multiple serving cell (such as multiple CCs). For example, network entity <NUM> may transmit first transmission <NUM> via first CC <NUM> and may transmit second transmission <NUM> via second CC <NUM>.

UE <NUM> receives the transmissions <NUM>, <NUM> including the modified DMRS <NUM> and <NUM>. For example, UE <NUM> decodes or processes the transmissions <NUM>, <NUM> based on the modified DMRS <NUM> and <NUM>. Based on the decoding of messages <NUM>, <NUM>, transmissions <NUM>, <NUM>, or both, UE <NUM> may send one or more acknowledgment messages (such as PUCCHs) to network entities <NUM>, <NUM>. It is noted that the acknowledgment message may include or correspond to a positive or negative acknowledgment, such as an ACK/NACK. UE <NUM> may send an ACK or a NACK based on a determination of whether the first transmission <NUM>, the second transmission <NUM>, or both, were successfully decoded. To illustrate, an ACK is communicated if decoding is successful and a NACK is communicated if decoding is unsuccessful.

Referring to <FIG> and <FIG>, diagrams illustrating DMRS modifications are depicted. <FIG> are block diagrams illustrating an example of DMRS modifications for a single PDSCH. <FIG> corresponds to DMRS modifications for a single PDSCH, and <FIG> correspond to DMRS modifications for multiple PDSCHs. In <FIG> and <FIG>, symbols of PDSCHs are illustrated with pattern filling.

Referring to <FIG> a block diagram illustrating an example DMRS pattern/scheme is illustrated. <FIG> depicts an example of a DMRS pattern for a PDSCH, such as a portion thereof. The PDSCH, such as the portion of the PDSCH, includes <NUM> symbols in the example of <FIG>. The <NUM> symbols may be used for DMRS and data, such as DMRS symbols and data symbols. As illustrated in <FIG>, the DMRS of the PDSCH includes four DMRS symbols and six data symbols. The four DMRS symbols are located at symbols <NUM>, <NUM>, and <NUM> of the PDSCH, when the numbering starts from <NUM>.

Referring to <FIG>, a block diagram illustrating an example CRS pattern/scheme is illustrated. <FIG> depicts an example of a CRS pattern. Similar to <FIG>, the PDSCH includes <NUM> symbols in the example of <FIG>. All or a portion of the symbols of the PDSCH may be used for CRS, such as for CRS rate matching, and may correspond to CRS blocks. As illustrated in <FIG>, the CRS includes or occupies four symbols. The four symbols are located at symbols <NUM>, <NUM>, <NUM>, and <NUM> of the PDSCH, when the numbering starts from <NUM>.

Referring to <FIG>, a block diagram illustrating an example DMRS modification is illustrated. <FIG> illustrates DMRS shifting by modifying of a location of one or more DMRS symbols of a transmission, such as PDSCH.

In <FIG>, a single PDSCH is illustrated. The PDSCH has the DMRS pattern or scheme as illustrated in <FIG>. Additionally, the PDSCH has or is associated with the CRS pattern or scheme illustrated in <FIG>. As illustrated in <FIG>, multiple DMRS symbols, locations thereof, may overlap with the CRS blocks of the CRS pattern illustrated in <FIG>. Specifically, each of the DMRS symbols (<NUM>, <NUM>, and <NUM>) overlap with the CRS resources/symbols of the CRS pattern. Accordingly, each DMRS symbol of each PDSCH is modified based on the overlap of one or more DMRS symbols and CRS blocks/locations.

For example, a location of each DMRS symbol of the PDSCH is modified based on modification parameters. In the example illustrated in <FIG>, each DMRS symbol location is incremented by a first value, that is one.

<FIG> are block diagrams illustrating an example of DMRS modifications for multiple PDSCHs. Referring to <FIG> a block diagram illustrating an example DMRS pattern/scheme is illustrated. <FIG> depicts an example of a DMRS pattern for a PDSCH. The PDSCH includes <NUM> symbols in the example of <FIG>. A first four symbols are unused by the DMRS and for data (that is not assigned to PDSCH), and may correspond to gaps or control data. The remaining <NUM> symbols may be used for DMRS and data. As illustrated in <FIG>, the DMRS of the PDSCH includes <NUM> DMRS symbols. The four DMRS symbols are located at symbols <NUM>, <NUM>, and <NUM> of the PDSCH, when the numbering starts from <NUM>.

Referring to <FIG>, a block diagram illustrating an example CRS pattern/scheme is illustrated. <FIG> depicts an example of a CRS pattern (such as one CRS pattern of possibly many CRS patterns configured for a component carrier). Similar to <FIG>, the PDSCH includes <NUM> symbols in the example of <FIG>. All or a portion of the symbols of the PDSCH may be used for CRS, such as for CRS rate matching, and may correspond to CRS blocks. As illustrated in <FIG>, the CRS includes or occupies <NUM> symbols. The six symbols are located at symbols <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> of the PDSCH, when the numbering starts from <NUM>.

Referring to <FIG>, a block diagram illustrating an example DMRS modification is illustrated. <FIG> illustrates DMRS shifting by incrementing of a location of each DMRS symbol of overlapping transmissions, such as PDSCHs.

In <FIG>, two partially overlapping PDSCHs are illustrated. The PDSCHs (which correspond to two TRPs, two higher layer indices, or two CORESET groups) have the DMRS pattern or scheme as illustrated in <FIG>. Additionally, the PDSCHs have or are associated with the CRS pattern or scheme illustrated in <FIG>. Alternatively, the CRS pattern may be associated with only one of the PDSCHs. As illustrated in <FIG>, multiple DMRS symbols, locations thereof, overlap with the CRS blocks of the CRS pattern illustrated in <FIG>. Specifically, each of the DMRS symbols (<NUM>, <NUM>, and <NUM>) of each PDSCH overlap with the CRS resources/symbols of the CRS pattern. Accordingly, each DMRS symbol of each PDSCH is modified based on the overlap of one or more DMRS symbols and CRS blocks/locations. This may be done irrespective of the association of the CRS pattern with the two PDSCH (i.e., is done for both PDSCHs).

For example, a location of each DMRS symbol of each PDSCH is modified based on modification parameters. In the example illustrated in <FIG>, each DMRS symbol location is incremented by a first value, that is one. Although incrementing is shown, in some other implementations, the DMRS symbol locations may be decremented, divided, multiplied, adjusted using a table or formula, or a combination thereof. Additionally, although a value of one is applied to the incrementing of DMRS symbol locations, in some other implementations, other values may be used, such as two, three, four, etc..

Although each DMRS symbol overlaps with a CRS resource and each DMRS symbol is moved, in some other implementations, each DMRS symbol is moved based on only a single DMRS symbol and CRS resource overlap in one PDSCH. Additionally, or alternatively, although the PDSCHs partially overlap in both time and frequency, the PDSCHs may fully overlap in time, frequency, or both, or may partially overlap in time or frequency in some other implementations.

When there are one or more CRS patterns (such as lte-CRS-ToMatchAround or its extension for multiple CRS patterns) to rate match around for deciding whether any DMRS symbols of the two PDSCHs (corresponding to the two TRPs, two higher layer indices, or two CORESET groups) are shifted, the one or more CRS patterns may be considered for both PDSCHs irrespective of the association of the PDSCHs to the CRS patterns (i.e., the association with the TRPs, higher layer indices, or CORESET groups).

For example, when only one CRS pattern or set of CRS patterns (such as lte-CRS-ToMatchAround) is configured and is associated with the first TRP (such as a first higher layer index value, i.e., a first CORESET group), and the two PDSCHs are partially/fully overlapping, DMRS of both PDSCHs shift even though the CRS pattern(s) is/are associated only with one PDSCH (such as the second PDSCH).

In some implementations, for shifting the DMRS pattern (i.e., if the DMRS is in the same symbol as the CRS), both PDSCHs follow the same behavior irrespective of association of the CRS pattern. Additionally, or alternatively, for rate matching, only the first PDSCH may be rate matched around the resources of the CRS pattern and the second PDSCH may not be rate matched around the resources of the CRS pattern (which is configured for the CORESET and component carrier). That is, even though PDSCH rate matching may take into account the association of a CRS pattern (or a list of CRS patterns) with a TRP (or with a CORESET group), DMRS shifting is performed irrespective of the association of PDSCHs with a TRP (or with a CORESET group) or the association of a CRS pattern (or a list of CRS patterns) with a TRP (or with a CORESET group).

A CRS pattern or list of CRS patterns can be configured for a multi-TRP UE in general, configured in a serving cell, and configured for a higher layer index value (i.e., CORESET group). Accordingly, the one or more CRS patterns are intended as design options for a component carrier and a TRP (CORESET group) within the component carrier, and thus the one or more CRS patterns are configured for a component carrier and a TRP.

Though the PDSCHs have the same DMRS pattern in the example provided herein, in some other implementations the PDSCHs may have different DMRS patterns from each other. In such implementations, the DMRS pattern of one or both may be adjusted based on a collision of either of the DMRS patterns.

<FIG> is a block diagram illustrating example blocks executed by a UE. The example blocks will also be described with respect to the UE <NUM> as illustrated in <FIG> is a block diagram conceptually illustrating an example design of a UE. <FIG> illustrates a UE <NUM> configured according to one aspect of the present disclosure. The UE <NUM> includes the structure, hardware, and components as illustrated for the UE <NUM> of <FIG> or <FIG>. For example, the UE <NUM> includes the controller/processor <NUM>, which operates to execute logic or computer instructions stored in the memory <NUM>, as well as controlling the components of the UE <NUM> that provide the features and functionality of the UE <NUM>. The UE <NUM>, under control of the controller/processor <NUM>, transmits and receives signals via the wireless radios noia-r and the antennas 252a-r. The wireless radios noia-r includes various components and hardware, as illustrated in <FIG> for the UE <NUM>, including the modulator/demodulators 254a-r, the MIMO detector <NUM>, the receive processor <NUM>, the transmit processor <NUM>, and the TX MIMO processor <NUM>.

As shown, the memory <NUM> may include DMRS Modification Logic <NUM>, CRS Rate Matching Logic <NUM>, CORESET Group Logic <NUM>, DMRS data <NUM>, modified DMRS data <NUM>, DMRS Modification data <NUM>, CRS data <NUM>, and CORESET Group data <NUM>. The DMRS data <NUM>, the modified DMRS data <NUM>, the DMRS modification data <NUM>, CRS data <NUM>, and the CORESET Group data <NUM> may include or correspond to DMRS data <NUM>, CRS data <NUM>, CORESET data <NUM>, and modifying parameters <NUM>. The DMRS Modification Logic <NUM> may include or correspond to the DMRS modifier <NUM>. The CRS Rate Matching Logic <NUM> may include or correspond to the CRS rate matcher <NUM>. The CORESET Group Logic <NUM> may include or correspond to the DMRS modifier <NUM>, the CRS rate matcher <NUM>, or both. In some aspects, the logic <NUM>-<NUM>, may include or correspond to processor(s) <NUM>. The UE <NUM> may receive signals from or transmit signals to a base station or base stations, such as the base station <NUM> or the network entity or entities <NUM>, <NUM>. When communicating with a single base station or serving cell, the UE <NUM> may receive signals from or transmit signals to multiple TRPs of the single base station or serving cell.

Referring to <FIG>, at block <NUM>, the UE receives a configuration message including at least one list of CRS patterns for a component carrier. A list of the at least one list is associated with a control resource set (CORESET) group.

At block <NUM>, the UE receives a first message scheduling a first transmission associated with a first demodulation reference signal (DMRS) and for the component carrier.

At block <NUM>, the UE receives a second message scheduling a second transmission associated with a second DMRS and for the component carrier. In some implementations, the first and second messages are DCIs or RRC messages. Additionally, or alternatively, the first and second transmissions are PDSCH transmissions. The first and second DMRS may be aligned, such as have the same symbol locations in some implementations.

At block <NUM>, the UE optionally determines whether one or more CRS patterns overlap with the first DMRS or the second DMRS. The determination may be based on whether the one or more CRS patterns are configured for the UE (for example, as described in Technical Specification (TS) <NUM> v16. <NUM>, section <NUM>. In some implementations, a single CRS pattern associated with multiple TRPs is used. In some other implementations, each TRP has an associated CRS pattern, and each CRS pattern is checked for overlap with each DMRS.

At block <NUM>, the UE modifies at least one DMRS symbol of the first DMRS or at least one DMRS symbol of the second DMRS based on the list being configured for the component carrier.

In some implementations, the method may further include determining whether the first transmission at least partially overlaps with the second transmission (such as same component carrier and different CORESET groups). For example, first resources of the first transmission are checked for overlap with second resources of the second transmission, in a time domain, frequency domain, or both. In some such implementations, one or more of the previous described blocks are performed responsive to or based on such as determination. To illustrate, DMRS modification or determinations for overlap may not be performed based on the UE determining that the first transmission does not overlap with the second transmissions, such as in the case of orthogonal resource blocks.

In some implementations, the method may further include receiving the first and second transmission with modified DMRS symbols. To illustrate, the UE <NUM> may receive the first and second transmission which have locations of DMRS symbols shifted as compared to the DMRS patterns indicated by or associated with the correspond first and second messages.

<FIG> is a block diagram illustrating example blocks executed by a network entity. The network entity may include or correspond to as base station or TRP thereof, configured according to an aspect of the present disclosure. The example blocks will also be described with respect to gNB <NUM> (or eNB) as illustrated in <FIG> is a block diagram conceptually illustrating an example design of a network entity. <FIG> illustrates a gNB <NUM> configured according to one aspect of the present disclosure. The gNB <NUM> includes the structure, hardware, and components as illustrated for gNB <NUM> of <FIG>. For example, gNB <NUM> includes controller/processor <NUM>, which operates to execute logic or computer instructions stored in memory <NUM>, as well as controlling the components of gNB <NUM> that provide the features and functionality of gNB <NUM>. The gNB <NUM>, under control of controller/processor <NUM>, transmits and receives signals via wireless radios 1201a-t and antennas 234a-r. Wireless radios 1201a-t includes various components and hardware, as illustrated in <FIG> for gNB <NUM>, including modulator/demodulators 232a-t, MIMO detector <NUM>, receive processor <NUM>, transmit processor <NUM>, and TX MIMO processor <NUM>. The data <NUM>-<NUM> in memory <NUM> may include or correspond to the corresponding data <NUM>-<NUM> in memory <NUM>, respectively.

Referring to <FIG>, at block <NUM>, the network entity transmits a configuration message including at least one list of CRS patterns for a component carrier. A list of the at least one list is associated with a control resource set (CORESET) group.

At block <NUM>, a network entity transmits a first message scheduling a first transmission associated with a first demodulation reference signal (DMRS) and for the component carrier.

At block <NUM>, the network entity transmits a second message scheduling a second transmission associated with a second DMRS and for the component carrier. In some implementations, the first and second message are DCIs or RRC messages. Additionally, or alternatively, the first and second transmissions are PDSCH transmissions. The first and second DMRS may be the same, such as have the same symbol locations in some implementations.

At block <NUM>, the network entity optionally determines whether one or more CRS patterns overlap with the first DMRS or the second DMRS. The determination may be based on whether the one or more CRS patterns are configured for the UE (for example, as described in <NUM> NR Technical Specification (TS) <NUM> v16. <NUM>, section <NUM>. In some implementations, a single CRS pattern associated with multiple TRPs is used. In some other implementations, each TRP has an associated CRS pattern, and each CRS pattern is checked for overlap with each DMRS.

At block <NUM>, the network entity modifies at least one DMRS symbol of the first DMRS or at least one DMRS symbol of the second DMRS responsive to determining that the list is configured for the component carrier.

In some implementations, the method may further include determining whether the first transmission at least partially overlaps with the second transmission (such as same component carrier and different CORESET groups). For example, first resources of the first transmission are checked for overlap with second resources of the second transmission, in a time domain, frequency domain, or both. In some such implementations, one or more of the previous described blocks are performed responsive to or based on such as determination. To illustrate, DMRS modification or determinations for overlap may not be performed based on the network entity determining that the first transmission does not overlap with the second transmissions, such as in the case of orthogonal resource blocks.

In some implementations, the method may further include transmitting the first transmission, the second transmission, or both. When transmitted, the first and second transmissions may have modified DMRS symbols. To illustrate, the network entity may transmit the first and second transmission which have locations of DMRS symbols shifted as compared to the DMRS patterns indicated by or associated with the correspond first and second messages.

It is noted that one or more blocks (or operations) described with reference to <FIG> may be combined with one or more blocks (or operations) of another of figure. For example, one or more blocks of <FIG> may be combined with one or more blocks (or operations) of another of <FIG>, <FIG>, <FIG>, <FIG>, or <FIG>. Additionally, or alternatively, one or more operations described above with reference to <FIG> may be combined with one or more operations described with reference to <FIG>.

Components, the functional blocks, and the modules described herein (such as components of <FIG>, functional blocks of <FIG>, and modules in <FIG>) may include processors, electronics devices, hardware devices, electronics components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof. In addition, features discussed herein relating to components, the functional blocks, and the modules described herein (such as components of <FIG>, functional blocks of <FIG>, and modules in <FIG>) may be implemented via specialized processor circuitry, via executable instructions, or combinations thereof.

The hardware and data processing apparatus used to implement the various illustrative logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single- or multi-chip 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 designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. In some implementations, a processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some implementations, particular processes and methods may be performed by circuitry that is specific to a given function.

Various modifications to the implementations described in this disclosure may be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other implementations without departing from the scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shown herein, but are to be accorded the widest scope consistent with the appended claims.

Certain features that are described in this specification in the context of separate implementations also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple implementations separately or in any suitable subcombination.

Claim 1:
A method of wireless communication, comprising:
receiving, by a user equipment (<NUM>), UE, a configuration message (<NUM>) including at least one list of cell specific reference signal, CRS, patterns for a component carrier, wherein a list of the at least one list is associated with a control resource set, CORESET, group;
receiving, by the UE (<NUM>), a first message (<NUM>) scheduling a first transmission (<NUM>) associated with a first demodulation reference signal, DMRS, and for the component carrier;
receiving, by the UE (<NUM>), a second message (<NUM>) scheduling a second transmission (<NUM>) associated with a second DMRS and for the component carrier; and
modifying, by the UE (<NUM>), at least one DMRS symbol of the first DMRS or at least one DMRS symbol of the second DMRS based on the list being configured for the component carrier;
wherein the first DMRS includes multiple DMRS symbols and wherein modifying the at least one DMRS symbol of the first DMRS or the second DMRS includes:
incrementing a location value of each DMRS symbol of the multiple DMRS symbols of the first DMRS of the first transmission by one.