Mode for control channel puncturing and shared channel rate matching

By configuring the UE in the LTE system to rate matching and punch the shared channels and control channels in the NR system in multiple modes, the problem of insufficient rate matching capabilities of communication devices in the LTE system in the frequency overlap mode is solved. Improve the communication reliability and spectrum efficiency of communication equipment and networks.

CN119032532APending Publication Date: 2024-11-26QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380030674.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-04
Filing Date
2023-03-28
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In LTE systems, communication devices in NR systems have difficulty in performing rate matching of shared channel signals in multiple modes where frequency overlap is overlapped on resources allocated for LTE reference signals, resulting in reduced communication reliability and low spectrum efficiency .

Method used

By configuring modes for controlling channel punching and shared channel rate matching in the UE, the CORESET indicator and mode list sent by the network enables the UE to share data signals in multiple modes that overlap or do not overlap in frequency and Control signals perform rate matching and hole punching to enhance communication capabilities with the network.

Benefits of technology

It improves wireless communication reliability and spectrum efficiency between communication devices in the NR system and the network, supports dynamic spectrum sharing, and enhances data rate and communication performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032532A_ABST
    Figure CN119032532A_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive an indication of a control resource set (CORESET) associated with a first radio access technology (RAT). The UE may receive an indication of a pattern for puncturing control signals associated with the first RAT around resources allocated for reference signals associated with a second RAT. The UE may communicate the control signal according to the mode. In some examples, the CORESET may be associated with a transmit configuration indicator (TCI) state, and the UE may receive a message that schedules a data signal based on the CORESET. The data signal may be associated with the first RAT. The UE may receive an indication of a pattern for rate matching of the data signal around the resource allocated for a reference signal associated with the second RAT. The UE may communicate the data signal according to the pattern.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 712,806, filed by Takeda et al. on April 4, 2022, entitled “PATTERNS FOR CONTROL CHANNEL PUNCTURING AND SHARED CHANNEL RATE-MATCHING,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including modes for controlling channel puncturing and shared channel rate matching. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses that support patterns for control channel puncturing and shared channel rate matching. For example, the described technology provides for configuring a communication device such as a user equipment (UE) using a pattern for control channel puncturing and shared channel rate matching. In some examples, the UE may receive an indication of a control resource set (CORESET) associated with a first radio access technology (RAT). The UE may receive an indication of a pattern for puncturing one or more control signals associated with the first RAT around resources allocated in the CORESET for reference signals associated with a second RAT. In response, the UE may communicate one or more control signals according to the pattern. In some examples, the CORESET may be associated with a transmission configuration indicator (TCI) state. The UE may receive a message scheduling a shared data signal based on the CORESET, and the shared data signal may also be associated with the first RAT. The UE may receive an indication of a pattern for rate matching a shared data signal around resources allocated for reference signals associated with the second RAT. In response, the UE may communicate a shared data signal according to the pattern. Therefore, such techniques can increase the reliability of wireless communications between a communication device and a wireless communication network.

[0006] A method for wireless communication at a UE is described. The method may include: receiving a first message scheduling at least one shared data signal associated with a first RAT based on a CORESET associated with a TCI state; receiving a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT; and communicating the at least one shared data signal according to the pattern.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include: a memory; and a processor coupled to the memory and configured to cause the apparatus to: receive a first message scheduling at least one shared data signal associated with a first RAT based on a CORESET associated with a TCI state; receive a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT; and communicate the at least one shared data signal according to the pattern.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT; means for receiving a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT; and means for communicating the at least one shared data signal according to the pattern.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive a first message scheduling at least one shared data signal associated with a first RAT based on a CORESET associated with a TCI state; receive a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT; and communicate the at least one shared data signal according to the pattern.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a third message indicating a first list including a first set of multiple modes for rate matching, wherein the mode may be based on two modes selected from the first set of multiple modes in the first list, and wherein the two modes may overlap in frequency.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending a report indicating at least one UE capability associated with rate matching, wherein receiving the third message may be based on the at least one UE capability.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a third message indicating a first list including a first set of multiple modes for rate matching and a second indication of a second list including a second set of multiple modes for rate matching, wherein the modes may be based on a first mode selected from the first list and a second mode selected from the second list, and wherein the first mode and the second mode may overlap in frequency or may not overlap in frequency.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first mode and the second mode may be associated with a mode index, and based on the mode index, the first mode may be selected from a first list and the second mode may be selected from a second list.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a third message indicating a first list including a first set of multiple modes for rate matching and a second indication of a second list including a second set of multiple modes for rate matching, wherein the mode may be based on two modes selected from the first list or the second list, and wherein the two modes may overlap in frequency.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying an indicator associated with the TCI state, wherein the two modes can be selected from a first list based on the indicator including a first value, and the two modes can be selected from a second list based on the indicator including a second value different from the first value.

[0016] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving a fourth message instructing the UE to select the two modes from one of the first list or the second list; and selecting the two modes from one of the first list or the second list based on the fourth message.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a third message indicating the CORESET associated with the TCI state, wherein receiving the first message may be based on the third message.

[0018] A method for wireless communication at a UE is described. The method may include: receiving a first message indicating a CORESET associated with a first RAT; receiving a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for reference signals associated with a second RAT; and communicating the at least one control signal according to the pattern.

[0019] An apparatus for wireless communication at a UE is described. The apparatus may include: a memory; and a processor coupled to the memory and configured to cause the apparatus to: receive a first message indicating a CORESET associated with a first RAT; receive a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for a reference signal associated with a second RAT; and communicate the at least one control signal according to the pattern.

[0020] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving a first message indicating a CORESET associated with a first RAT; means for receiving a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for a reference signal associated with a second RAT; and means for communicating the at least one control signal according to the pattern.

[0021] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive a first message indicating a CORESET associated with a first RAT; receive a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for reference signals associated with a second RAT; and communicate the at least one control signal according to the pattern.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a third message indicating at least one list, wherein each of the at least one list includes a set of multiple modes for punching, and wherein the mode may be based on at least one mode selected from the at least one list.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a fourth message indicating a mode position, wherein the mode is based on one of the at least one mode, and wherein the one mode is selected from a list of the at least one list based on the mode position.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the mode may be based on each of the at least one mode and each of the at least one mode may be selected from a list in the at least one list.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the mode can be based on each of the at least one mode.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying an indicator associated with the CORESET, wherein the at least one mode may be selected from a list in the at least one list, and wherein the list may be based on a value of the indicator.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second message includes a radio resource control (RRC) message and the second message indicates the mode via an information element (IE).

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a report indicating at least one UE capability associated with puncturing control signals associated with the first RAT around resources allocated in the CORESET for reference signals associated with the second RAT, wherein receiving the second message may be based on the at least one UE capability.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the at least one UE capability includes: the UE's ability to support puncturing according to multiple patterns associated with a serving cell, the UE's ability to support puncturing according to multiple patterns that overlap in frequency and can be associated with a serving cell, the UE's ability to support puncturing according to multiple patterns that do not overlap in frequency and can be associated with a serving cell, the UE's ability to support puncturing for multiple CORESETs associated with a bandwidth portion or a serving cell, or any combination thereof.

[0030] A method for wireless communication at a network entity is described. The method may include: sending a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT; sending a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT; and communicating the at least one shared data signal according to the pattern.

[0031] An apparatus for wireless communication at a network entity is described. The apparatus may include: a memory; and a processor coupled to the memory and configured to cause the apparatus to: send a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT; send a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT; and communicate the at least one shared data signal according to the pattern.

[0032] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT; means for sending a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT; and means for communicating the at least one shared data signal according to the pattern.

[0033] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: send a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT; send a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT; and communicate the at least one shared data signal according to the pattern.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a third message indicating a first list including a first set of multiple modes for rate matching, wherein the mode may be based on two modes selected from the first set of multiple modes in the first list, and wherein the two modes may overlap in frequency or may not overlap in frequency.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving a report indicating at least one UE capability associated with rate matching, wherein sending the third message may be based on the at least one UE capability.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a third message indicating a first list including a first set of multiple modes for rate matching and a second indication of a second list including a second set of multiple modes for rate matching, wherein the modes may be based on a first mode selected from the first list and a second mode selected from the second list, and wherein the first mode and the second mode may overlap in frequency.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first mode and the second mode may be associated with a mode index, and based on the mode index, the first mode may be selected from a first list and the second mode may be selected from a second list.

[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a third message indicating a first list including a first set of multiple modes for rate matching and a second indication of a second list including a second set of multiple modes for rate matching, wherein the mode may be based on two modes selected from one of the first list or the second list, and wherein the two modes may overlap in frequency.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the two modes may be selected from a first list based on an indicator associated with the TCI state including a first value, and the two modes may be selected from a second list based on the indicator associated with the TCI state including a second value different from the first value.

[0040] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending a fourth message instructing the UE to select the two modes from one of the first list or the second list.

[0041] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a third message indicating the CORESET associated with the TCI state, wherein receiving the first message may be based on the third message.

[0042] A method for wireless communication at a network entity is described. The method may include: sending a first message indicating a CORESET associated with a first RAT; sending a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for reference signals associated with a second RAT; and communicating the at least one control signal according to the pattern.

[0043] An apparatus for wireless communication at a network entity is described. The apparatus may include: a memory; and a processor coupled to the memory and configured to cause the apparatus to: send a first message indicating a CORESET associated with a first RAT; send a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for a reference signal associated with a second RAT; and communicate the at least one control signal according to the pattern.

[0044] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending a first message indicating a CORESET associated with a first RAT; means for sending a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for reference signals associated with a second RAT; and means for communicating the at least one control signal according to the pattern.

[0045] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: send a first message indicating a CORESET associated with a first RAT; send a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for reference signals associated with a second RAT; and communicate the at least one control signal according to the pattern.

[0046] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a third message indicating at least one list, wherein each of the at least one list includes a set of multiple modes for punching, and wherein the mode may be based on at least one mode selected from the at least one list.

[0047] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a fourth message indicating a mode position, wherein the mode is based on one of the at least one mode, and wherein the one mode is selected from a list of the at least one list based on the mode position.

[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the mode may be based on each of the at least one mode and each of the at least one mode may be selected from a list in the at least one list.

[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the mode can be based on each of the at least one mode.

[0050] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the at least one mode may be selected from a list in the at least one list, and wherein the list may be based on a value of an indicator associated with the CORESET.

[0051] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second message includes an RRC message and the second message indicates the mode via an IE.

[0052] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a report indicating at least one UE capability associated with puncturing control signals associated with the first RAT around resources allocated in the CORESET for reference signals associated with the second RAT, wherein sending the second message is based at least in part on the at least one UE capability.

[0053] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the at least one UE capability includes: the UE's ability to support puncturing according to multiple patterns associated with a serving cell, the UE's ability to support puncturing according to multiple patterns that overlap in frequency and can be associated with a serving cell, the UE's ability to support puncturing according to multiple patterns that do not overlap in frequency and can be associated with a serving cell, the UE's ability to support puncturing for multiple CORESETs associated with a bandwidth portion or a serving cell, or any combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Figure 1 An example of a wireless communication system supporting a mode for controlling channel puncturing and sharing channel rate matching according to one or more aspects of the present disclosure is illustrated.

[0055] Figure 2 An example of a network architecture supporting a mode for controlling channel puncturing and sharing channel rate matching according to one or more aspects of the present disclosure is illustrated.

[0056] Figure 3 An example of a wireless communication system supporting a mode for controlling channel puncturing and sharing channel rate matching according to one or more aspects of the present disclosure is illustrated.

[0057] Figure 4 and Figure 5 Each illustrates an example of a process flow supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure.

[0058] Figure 6 and Figure 7 A block diagram of a device supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown.

[0059] Figure 8 A block diagram of a communication manager supporting modes for controlling channel puncturing and shared channel rate matching is shown in accordance with one or more aspects of the present disclosure.

[0060] Fig. 9 A diagram of a system including a device supporting a mode for controlling channel puncturing and shared channel rate matching is shown in accordance with one or more aspects of the present disclosure.

[0061] Fig.10 and Fig.11 A block diagram of a device supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown.

[0062] Fig.12 A block diagram of a communication manager supporting modes for controlling channel puncturing and shared channel rate matching is shown in accordance with one or more aspects of the present disclosure.

[0063] Fig.13 A diagram of a system including a device supporting a mode for controlling channel puncturing and shared channel rate matching is shown in accordance with one or more aspects of the present disclosure.

[0064] Figures 14 to 21 A flow chart illustrating a method of supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0065] In some wireless communication systems, a cell (e.g., a network entity, a base station, an inter-access backhaul (IAB) node, a relay node, or any other service providing cell) may, for example, share a portion of a radio frequency spectrum with another cell (e.g., another network entity, another base station, another IAB node, another relay node, or any other service providing cell). For example, a wireless communication system may support dynamic spectrum sharing (DSS) so that multiple network entities (e.g., adjacent network entities) may use the same radio frequency spectrum band or overlapping portions of the same radio frequency spectrum band. In some examples, network entities (or cells) configured to share at least a portion of a radio frequency spectrum (e.g., a carrier) may communicate via different radio access technologies (RATs). That is, a carrier may be shared between multiple RATs (e.g., long term evolution (LTE) and fifth generation (5G) new radio (NR)) so that the multiple RATs may operate on a common time and frequency resource grid. However, in some examples of LTE systems, a communication device (e.g., user equipment (UE)) operating within the LTE system may be configured to continuously monitor a reference signal (e.g., an LTE reference signal). Thus, for DSS, resources for communication devices operating within the NR system may be assigned around the resources allocated for LTE reference signals.

[0066] For example, a communication device operating in an NR system may be configured to time and frequency multiplex (e.g., rate match) a shared channel signal around resources allocated for LTE reference signals according to one or more modes. However, in some examples, a communication device operating in an NR system may not be able to rate match a shared channel signal around resources allocated for LTE reference signals according to multiple modes overlapping in frequency. For example, if a communication device operating in an NR system is configured to operate in a single transmit and receive point (TRP) mode, the communication device may perform rate matching according to a single mode or multiple modes that may not overlap in frequency. Additionally or alternatively, a communication device operating in an NR system may not be able to rate match a control channel signal around resources allocated for LTE reference signals. For example, if a resource configured to monitor a symbol of a control channel (e.g., for a control channel signal) overlaps with one or more resources allocated for LTE reference signals, the communication device may not be able to monitor (or receive) a control channel signal during the symbol. Therefore, wireless communication between a communication device operating in an NR system and a network may be degraded.

[0067] Various aspects of the present disclosure generally relate to techniques for supporting patterns for control channel puncturing and shared channel rate matching, and more specifically, to techniques for configuring a communication device with patterns for puncturing control channel signals of a RAT or rate matching shared channel signals of a RAT around resources allocated for signals associated with another RAT. For example, a network may configure a communication device with one or more lists of patterns to be used by the communication device for shared channel rate matching, control channel puncturing, or both. The communication device may select one or more patterns from the one or more lists based on signaling from the network or based on rules configured for the communication device.

[0068] For example, the network (one or more network entities) may send an indication for (e.g., configuring) a communication device (e.g., UE) to operate in a single TRP mode. In some examples, the network may instruct the UE to operate in a single TRP mode by sending an indication of a control resource set (CORESET) configured with a single transmit configuration indicator (TCI) state (e.g., a TCI state corresponding to a single TRP). That is, the network may configure the UE to monitor signals on a CORESET associated with a single TRP. Additionally or alternatively, the network may send an indication of one or more mode lists for shared channel rate matching. In some examples, multiple modes in a list (or multiple modes across lists) may overlap in frequency (or not overlap in frequency). Therefore, the UE may perform shared channel rate matching according to two or more modes that overlap in frequency (e.g., from one or more lists in a list), regardless of whether the UE can be configured to operate in a single TRP mode.

[0069] In some examples, the UE may select one or more lists for shared channel rate matching based on signaling from the network. For example, the network may send an indication that causes the UE to select a list (or multiple lists) from a list configured at the UE (e.g., by the network). Additionally or alternatively, the network may send an indication that causes the UE to select a mode (or multiple modes) from a list configured at the UE. In other examples, the UE may select one or more lists for shared channel rate matching based on one or more rules indicated to the UE by the network (or configured at the UE). For example, the network may send an indication that causes the UE to select one or more modes based on the ordering of the modes within the one or more lists. Additionally or alternatively, the UE may be configured to select one or more modes based on an identifier of a CORESET (e.g., associated with a single TRP).

[0070] Additionally or alternatively, the network may send an indication that causes the UE to perform control channel puncturing according to one or more patterns. For example, the network may send an indication of one or more lists that may include patterns for control channel puncturing. These patterns may overlap in frequency or may not overlap in frequency. In some examples, one or more pattern lists configured at the UE may be used for both control channel puncturing and shared channel rate matching. That is, the network may send an indication that causes the UE to perform control channel puncturing according to one or more patterns in a list (or multiple lists) configured at the UE for shared channel rate matching. In some examples, the UE may select one or more lists (or one or more patterns from one or more lists) for control channel puncturing based on signaling from the network or one or more rules indicated by the network to the UE (or configured at the UE). In some examples, one or more lists (or one or more patterns) to be used by the UE for control channel puncturing may be based on one or more capabilities of the UE.

[0071] Certain aspects of the subject matter described herein may be implemented to achieve one or more of the following potential advantages. In some examples, the techniques employed by the described communication device may provide benefits and enhancements to the operation of the communication device (e.g., UE and network entity), including implementing modes for control channel puncturing and shared channel rate matching. For example, the operations performed by the described communication device may provide enhancements to shared channel rate matching by enabling a communication device operating in a single TRP mode to rate match a shared channel signal of a first RAT around resources allocated for a reference of a second RAT based on multiple modes overlapping in frequency. Additionally or alternatively, the operations performed by the described communication device may provide enhancements to communications between the communication device and a network by enabling the communication device to puncture a control channel signal of a first RAT around resources allocated for a reference signal of a second RAT. In some examples, the operations performed by the described communication device may support improvements to the reliability of DSS communications, improved spectral efficiency, and increased data rates, among other benefits.

[0072] Various aspects of the disclosure are first described in the context of a wireless communication system. Various aspects of the disclosure are also described in the context of a network architecture and process flow. Various aspects of the disclosure are further illustrated and described by apparatus diagrams, system diagrams, and flow diagrams related to modes for controlling channel puncturing and shared channel rate matching.

[0073] Figure 1An example of a wireless communication system 100 supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be an LTE network, an LTE-A network, an LTE-A Pro network, an NR network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0074] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In different examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). The network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0075] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be capable of communicating with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.

[0076] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0077] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other on the backhaul links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0078] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0079] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a TRP. One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0080] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0081] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such a case, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0082] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the modes for controlling channel puncturing and shared channel rate matching as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0083] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

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

[0085] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion (e.g., bandwidth portion) of an RF spectrum band that operates according to one or more physical layer channels for a given radio access technology (RAT) (such as LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN that communicates with another device (e.g., directly or via one or more other network entities 105).

[0086] The signal waveform sent on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system that employs MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The amount of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0087] The time interval of the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0088] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may also be divided into a plurality of mini-time slots including one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

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

[0091] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0092] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication can include private communication or group communication, and can be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions can include prioritization of services, and such services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency can be used interchangeably in this article.

[0093] In some examples, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 (e.g., coverage area 110-a) of a network entity 105 (e.g., a base station 140, a RU 170), and the one or more UEs may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

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

[0095] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region of 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0096] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can employ licensed assisted access (LAA), LTE-unlicensed (LTE-U) RAT, or NR technology in an unlicensed band (such as, the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band can be based on a carrier aggregation configuration (e.g., LAA) combined with component carriers operating in a licensed band. Operations in an unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0097] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having antenna ports of a set of rows and columns that the network entity 105 can use to support beamforming for communication with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0098] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0099] The wireless communication system 100 may support a technique for configuring a communication device (e.g., one or more UEs 115) with a pattern for control channel puncturing and shared channel rate matching. For example, the UE 115 may receive an indication of a CORESET associated with a first RAT from the network entity 105. In some cases, the UE 115 may receive an indication of a pattern for puncturing one or more control signals of the first RAT around resources in the CORESET allocated for reference signals associated with a second RAT from the network entity 105. In response, the UE 115 may communicate the one or more control signals according to the pattern. In some examples, the CORESET may be associated with a TCI state, and the UE 115 may receive a message including scheduling information for a shared data signal associated with the first RAT based on the CORESET. The UE 115 may receive an indication of a pattern for rate matching a shared data signal around resources allocated for a reference signal associated with a second RAT from the network entity 105. In response, the UE 115 may communicate the shared data signal according to the pattern. Such techniques may enable the UE 115 to increase the reliability of wireless communications between the UE 115 and nodes of the network (eg, the network entity 105).

[0100] Figure 2 An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with a core network 130-a through one or more disaggregated network entities 105 (e.g., a near RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. The RU 170-a may communicate with a corresponding UE 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be served by multiple RUs 170-a simultaneously.

[0101] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, the network entity 105 may include a wired interface that is configured to receive or send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive or send signals, or both, to one or more of the other network entities 105 over a wireless transmission medium.

[0102] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to process user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0103] DU 165-a may correspond to a logical unit including one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more aspects of the RLC layer, the MAC layer, and the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional splits, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU160-a.

[0104] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0105] SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) to perform network entity lifecycle management (e.g., instantiating virtualized network entities 105) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a can communicate directly with one or more RUs 170 via an O1 interface. The SMO 180-a can also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0106] The non-RT RIC 175-a may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b. The non-RT RIC 175-a may be coupled or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0107] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 175-b and can be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175-a. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via generating a RAN management policy (e.g., an A1 policy).

[0108] The network architecture 200 may support techniques for configuring a communication device (e.g., one or more UEs 115) with a pattern for control channel puncturing and shared channel rate matching. In some examples, a network entity (e.g., CU 160-a, DU 165-a, RU 170-a, etc.) may send an indication of a CORESET associated with a first RAT (e.g., 5G or NR). Additionally or alternatively, the network entity may send an indication of a pattern for puncturing one or more control signals associated with the first RAT around resources in the CORESET allocated for reference signals associated with a second RAT (e.g., 4G, 3G). In some examples, the network entity may communicate the one or more control signals according to the pattern. In some examples, a CORESET may be associated with a TCI state, and the network entity may send a message scheduling a shared data signal based on the CORESET. The shared data signal may also be associated with the first RAT. Additionally or alternatively, the network entity may send an indication of a pattern for rate matching the shared data signal around resources allocated for reference signals associated with the second RAT. In some examples, the network entity may communicate the shared data signal according to the pattern.

[0109] In some examples, the aforementioned operations of the network entities (e.g., CU 160-a, DU 165-a, RU 170-a) may be performed according to the network architecture 200. For example, a higher layer parameter (e.g., RRC parameter) indicating a mode for control channel puncturing or shared channel rate matching may be determined (e.g., selected, configured) by CU 160-a and communicated to DU 165-a (e.g., via midhaul communication link 162-a). In some examples, DU 165-a may perform control channel puncturing or shared channel rate matching according to the mode communicated to DU 165-a from CU 160-a (e.g., via higher layer parameters). For example, DU 165-a may generate a signal for rate matching or puncturing of a first RAT around resources allocated for one or more reference signals associated with a second RAT according to the mode. DU 165-a may communicate the signal to RU 170-a, for example, via fronthaul communication link 168-a. In some examples, and in response to obtaining the signal generated by DU 165-a, RU 170-a may transmit the signal (e.g., OTA) via communication link 125-a to one or more other communication devices (e.g., one or more UEs 115). Such techniques may result in increased reliability of wireless communications between UE 115 and the network.

[0110] Figure 3 An example of a wireless communication system 300 that supports a mode for controlling channel puncturing and sharing channel rate matching according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 can implement aspects of the wireless communication system 100 and the network architecture 200. For example, the wireless communication system 300 may include a network entity 305 and a UE 315, which may be reference Figure 1 and Figure 2 The network entity 305-a and the UE 315-a may communicate within the coverage area 310, which may be a reference area. Figure 1 or Figure 2 An example of a coverage area 110 is described. Figure 3 In the example of , coverage area 310 may correspond to a cell, and network entity 305 may be an example of a service providing cell (e.g., a serving cell). In some examples, network entity 305 and UE 315 may communicate over the cell via communication link 330. Figure 3 In the example of , communication link 330 can be an example of an uplink, a downlink, or one or more other communication links.

[0111] In some examples, the wireless communication system 300 may support DSS so that the network entity 305 may share a portion of the radio frequency spectrum (e.g., carrier) with another (e.g., adjacent) network entity (not shown). For example, the network entity 305 may operate via a RAT such as an NR RAT and may be configured to use a carrier shared between an NR RAT (e.g., an NR system) and one or more other RATs such as an LTE RAT (e.g., an LTE system). In some examples, such operations between an LTE system and an NR system may be referred to as LTE-NR coexistence. In some examples of LTE-NR coexistence, the network entity 305 may support multiple carriers of multiple (e.g., different) RATs. That is, the network entity 305 may support LTE carriers and NR carriers. In some examples, a communication device operating within an LTE system (e.g., on an LTE cell) may be configured to continuously monitor a reference signal (e.g., an LTE reference signal). Therefore, resource elements (e.g., resources) for communication devices operating within an NR system (e.g., on an NR cell) may be assigned around resources allocated for LTE reference signals (e.g., LTE reference signal resources). That is, for LTE-NR coexistence, resources for a communication device (e.g., UE 315) operating within the NR system may be allocated around LTE reference signal resources (e.g., reference signal resources 325).

[0112] However, in some examples, UE 315 may not be able to handle control channel signals (e.g., NR control channel signals) that conflict with LTE reference signal resources. For example, UE 315 may not be able to rate match, puncture, or eliminate NR control channel signals that appear on resources overlapping with LTE reference signal resources. For example, if at least one resource of a control channel candidate (e.g., a physical downlink control channel (PDCCH) candidate) configured for monitoring a PDCCH signal (e.g., an NR PDCCH signal) by UE 315 (e.g., on a serving cell operating within an NR system, on an NR cell supported by network entity 305) overlaps with at least one resource allocated for an LTE reference signal (e.g., on an LTE cell supported by network entity 305 or another network entity (not shown)), UE 315 may not monitor the PDCCH candidate. In some examples, UE 315 may determine which resources are allocated for LTE reference signals (e.g., which PDCCH candidates may not be monitored) via an indication from network entity 305. For example, the network entity 305 may indicate which resources are allocated for LTE reference signals via an information element (IE) such as lte-CRSToMatchAround IE or LTE-CRS-PatternList IE. It should be understood that the names of the IEs and fields (e.g., parameters) described herein may vary based on the specific implementation of one or more devices (e.g., UE 315, base station 305, or both), and the examples described herein should not be considered to be limited to the scope covered by the claims or the present disclosure.

[0113] In some examples, a resource transmission structure (e.g., for downlink transmission or uplink transmission) may include a control region and a data region. The control region (e.g., a control channel, PDCCH) and the data region (e.g., a shared data channel, a physical downlink shared channel (PDSCH)) may span multiple modulation symbols in the time domain and multiple subcarriers in the frequency domain. For example, the control region may include PDCCH 320, and the data region may include PDSCH 321. The control region and the data region may overlap in the time domain. In some examples, a PDCCH candidate may span multiple (e.g., ranging from one to three) symbols (e.g., OFDM symbols) of a time slot. For example, a PDCCH candidate may span multiple symbols (or other durations) based on one or more parameters configured for UE 315 (e.g., via IEs such as SearchSpace IE and associated controlResourceSet IEs).

[0114] In some examples, an LTE reference signal may be transmitted on a cell having multiple (e.g., four) antenna ports (e.g., on a downlink cell). In such examples, the LTE reference signal may be transmitted during multiple symbols of the PDCCH 320 (e.g., may occur in the multiple symbols), such as during symbols with indices 0, 1, 4, 7, 8, and 11 (e.g., and subcarriers with indices 2, 5, 8, and 11). That is, reference signal resources 325 occurring on symbols with indices 0, 1, 4, 7, 8, and 11 and subcarriers with indices 2, 5, 8, and 11 may be allocated for LTE reference signal transmission. Therefore, if the UE 315 is configured with a PDCCH candidate that spans at least one of the symbols with indices 0 and 1 (e.g., for receiving an NR PDCCH signal), the UE 315 may not monitor the PDCCH candidate and may therefore not receive an NR PDCCH signal. In addition, although symbols with indices 0 and 1 may include available resources 326, reception of NR PDCCH signals may be disabled for such symbols (e.g., because these symbols include resources allocated for LTE reference signal transmission), which may result in the available resources 326 appearing in symbols with indices 0 and 1 not being utilized by the network. For example, the network (e.g., the network entity 305) may avoid scheduling transmissions on all subcarriers (e.g., subcarriers with indices 0-11) of a resource block during a symbol duration including at least one resource allocated for an LTE reference signal (e.g., symbols with indices 0, 1, 4, 7, 8, and 11). That is, during DSS operation on the cell, a PDCCH candidate (e.g., an NR PDCCH candidate) may not span all symbols of a slot (e.g., may span symbols with indices 2, 3, 5, 6, 9, 10, 12, and 13, and may not span symbols with indices 0, 1, 4, 7, 8, and 11), which may result in underutilization of communication resources, reduced throughput, and increased latency. Therefore, technology that enables NR PDCCH reception in symbols having resources allocated for LTE reference signals (e.g., LTE reference signal resources, reference signal resources 325) can improve communication reliability and flexibility of wireless devices.

[0115] In some examples, puncturing may be used to enable mapping of NR PDCCH candidates onto symbols where LTE reference signal resources are allocated (e.g., present or mapped). For example, a pattern for control channel puncturing as described herein may provide a performance gain in communications between UE 315 and a network by increasing utilization of communication resources (e.g., by increasing available PDCCH resources). For example, UE 315 may receive a CORESET indication message 335 indicating a CORESET associated with an NR RAT. UE 315 may receive a pattern indication message 336. In some examples, pattern indication message 336 may indicate a pattern for puncturing one or more control signals associated with an NR RAT (e.g., one or more NR PDCCH signals) around resources allocated for reference signals associated with an LTE RAT (e.g., LTE reference signal resources). In response, UE 315 may communicate the one or more NR PDCCH signals according to the pattern indicated via pattern indication message 336. For example, UE 315 may receive one or more NR PDCCH signals (e.g., on PDCCH 320) that are punctured around LTE reference signal resources (e.g., reference signal resources 325) according to the pattern, thereby increasing utilization of communication resources in the wireless communication system 300 (e.g., increasing utilization of available resources 326).

[0116] Additionally or alternatively, the UE 315 may be configured to rate match a shared channel signal associated with the NR RAT (e.g., an NR PDSCH signal sent on the PDSCH 321) around a reference signal resource 325 (e.g., an LTE reference signal resource) according to one or more patterns. In some examples, the LTE reference signal may be an LTE cell-specific reference signal (LTE-CRS). In some examples, the UE 315 may identify the reference signal resource 325 based on signaling from the network device 305. For example, the network entity 305 may send an indication of one or more patterns or one or more lists of patterns that may be considered (e.g., considered) for the LTE reference signal resource. That is, the network entity 305 may send an indication of one or more LTE reference signal patterns or one or more lists of LTE reference signal patterns for rate matching the NR PDSCH signal around the LTE reference signal resource (e.g., for NR PDSCH rate matching). Therefore, the UE 315 may not be able to determine (e.g., may not know) whether the reference signal is sent according to the one or more patterns (e.g., by a communication device operating on an LTE cell). In some examples, the network entity 305 may indicate the one or more modes via a higher layer parameter such as a RateMachPatternLTE-CRS IE configured via RRC. In some examples, the RateMachPatternLTE-CRS IE may be included in the lte-CRS-ToMatchAround field of the ServingCellConfig IE or ServingCellConfigCommon IE that configures an LTE reference signal (e.g., LTE-CRS). Additionally or alternatively, the RateMachPatternLTE-CRS IE may be included in the lte-CRS-PatternList1-r16 field of the ServingCellConfig IE. In some examples (e.g., for 15kHz subcarrier spacing), the one or more modes may indicate resources that are unavailable for PDSCH transmission via an LTE carrier in the serving cell (e.g., that may be allocated for LTE reference signals).

[0117] For example, the ServingCellConfig IE may include an lte-CRS-ToMatchAround field and a RateMatchPatternLTE-CRS IE, which provide (e.g., indicate) one or more parameters to determine a pattern of LTE reference signal resources around which the UE 315 can perform rate matching (e.g., an LTE reference signal pattern). In some examples, the ServingCellConfig IE may include a list of lte-CRS-PatterList1-r16 fields and RateMatchPatternLTE-CRS IEs. For example, the lte-CRS-PatterList1-r16 field may include a list of LTE reference signal patterns around which the UE 315 can perform NRPDSCH rate matching. In some examples, the LTE reference signal pattern indicated via the lte-CRS-PatterList1-r16 field may be non-overlapping in frequency. For example, the network entity 305 may not configure the UE 315 with multiple parameters indicating patterns that overlap in frequency. That is, the network entity 305 may not configure the lte-CRS-PatterList1-r16 field and the lte-CRS-ToMatchAround field at the same time. Additionally or alternatively, in some examples, rate matching may not be used for resources allocated for demodulation reference signal (DMRS) transmission (e.g., NR DMRS transmission performed by the network entity 305).

[0118] In some examples, the UE 315 may receive one or more patterns (e.g., LTE reference signal patterns) from the network entity 305 (e.g., a serving cell, a cell that may be transmitting an NR PDSCH signal). For example, the UE 315 may be configured with an LTE reference signal pattern corresponding to a specific network entity (e.g., the network entity 305) that supports both an LTE carrier and an NR carrier (e.g., a carrier shared between an LTE system and an NR system on which the UE 315 may operate). In some examples, the network entity 305 may configure the UE 315 with multiple LTE reference signal patterns (e.g., for the network entity 305 and one or more other network entities (not shown)). For example, the UE 315 may be operating on an NR cell supported by the network entity 305 and may experience interference from LTE reference signal transmissions from other network entities (not shown) (e.g., on an LTE cell). Therefore, the network entity 305 may configure the UE 315 with an LTE reference signal pattern for each of the other network entities (e.g., a network entity for transmitting LTE reference signals on an LTE cell).

[0119] In some instances, the LTE reference signal patterns for multiple LTE cells may not overlap in frequency. For example, if the bandwidth used by the NR cell (e.g., the NR carrier bandwidth) is greater than the bandwidth used by the LTE cell associated with the multiple LTE reference signal patterns (e.g., the LTE carrier bandwidth), the LTE reference signal patterns may not overlap in frequency. In such examples, the UE 315 may rate match the NR PDSCH signal (e.g., transmitted on the NR cell) from the network entity 305 according to one LTE reference signal pattern (e.g., associated with the first LTE cell) for a portion of the NR carrier bandwidth and according to another LTE reference signal pattern (e.g., associated with the second LTE cell) for another portion of the NR carrier bandwidth. In other instances, the LTE reference signal patterns for multiple LTE cells may overlap in frequency. In such instances, the UE 315 may rate match the PDSCH signal from the network entity 305 according to the two LTE reference signal patterns across multiple portions (e.g., a subset of the portions or all of the portions) of the NR carrier bandwidth. For example, UE 315 may rate match a PDSCH signal around reference signal resources 325 of PDSCH 321, such as reference signal resources 325 occurring during symbols having indices 0, 1, 4, 7, 8, and 11, and subcarriers having indices 1, 2, 4, 5, 7, 8, 10, and 11 (e.g., where subcarriers having indices 1, 4, 7, and 10 may be allocated for reference signals sent on a first LTE cell, and subcarriers having indices 2, 5, 8, and 11 may be allocated for reference signals sent on a second LTE cell).

[0120] However, in some examples, if the UE 315 is operating in a single TRP mode (e.g., during single TRP operation), the UE 315 may not be able to perform NR PDSCH rate matching based on multiple overlapping LTE reference signal patterns. For example, the network entity 305 may configure the UE 315 with a second list of LTE reference signal patterns based on the value of the indicator configured for the CORESET. For example, the ServingCellConfig IE may include a list of lte-CRS-PatterList2-r16 fields and a RateMatchPatternLTE-CRS IE, which may indicate another list of LTE reference signal patterns around which the UE 315 may perform rate matching for NR PDSCH signals that are scheduled using downlink control information (DCI) detected on a CORESET configured with an indicator set to 1 (e.g., the value of the CORESETPoolIndex field is set to 1). That is, if UE 315 is also configured to operate in a multi-TRP mode (e.g., to perform multi-TRP operations), the network entity 305 may configure UE 315 with such a list.

[0121] In some examples, the first LTE reference signal pattern in the lte-CRS-PatterList2-r16 field may overlap in frequency with a first LTE reference signal pattern of another list, such as indicated via the lte-CRS-PatternList1 field. Additionally or alternatively, the second LTE reference signal pattern in the lte-CRS-PatterList2-r16 field may overlap in frequency with a second LTE reference signal pattern of a list indicated via the lte-CRS-PatternList1 field. That is, the pattern of the first list (e.g., the list indicated via the lte-CRS-PatterList2-r16 field) may overlap with the pattern of the second list (e.g., the list indicated via the lte-CRS-PatternList1 field). In some examples, if the lte-CRS-ToMatchAround field is not configured (e.g., and there is at least one CORESET in the downlink bandwidth of the serving cell, where the coresetPoolIndex field is set to 1), the network entity 305 may configure the lte-CRS-PatterList2-r16 field. That is, if the UE 315 is configured with multiple (e.g., two) values ​​of the coresetPoolIndex field via higher layer parameters such as via the PDCCH-Config IE (e.g., in the ControlResourceSet IE) and is also configured with both the lte-CRS-PatternList1 field and the lte-CRS-PatterList2-r16 field (e.g., in the ServingCellConfig IE), then the resources that are unavailable for NR PDSCH transmissions (e.g., resources around which the UE 315 may perform rate matching) may be based on the value of the coresetPoolIndex field.

[0122] For example, if the UE 315 is configured with the crs-RateMatch-PerCoresetPoolIndex IE and the value of the coresetPoolIndex field is set to 0, the UE 315 may perform NR PDSCH rate matching according to the LTE reference signal pattern of the first list (e.g., indicated via the lte-CRS-PatternList1 field). Additionally or alternatively, if the UE 315 is configured with the crs-RateMatch-PerCoresetPoolIndex IE and the value of the coresetPoolIndex field is set to 1, the UE 315 may perform NR PDSCH rate matching according to the LTE reference signal pattern of the second list (e.g., indicated via the lte-CRS-PatterList2-r16 field). Additionally or alternatively, if UE 315 is not configured with the crs-RateMatch-PerCoresetPoolIndex IE, UE 315 may perform NR PDSCH rate matching based on both the first list (e.g., indicated via the lte-CRS-PatternList1 field) and the second list (e.g., indicated via the lte-CRS-PatterList2-r16 field).

[0123] For example, if UE 315 is configured with a CORESET associated with multiple TCI states that can each correspond to a corresponding TRP (e.g., via a coresetPoolIndex field set to 1), UE 315 may rate match the PDSCH signal according to multiple overlapping LTE reference signal modes. That is, if UE 315 is configured to perform multi-TRP operation, UE 315 may rate match the PDSCH signal according to multiple overlapping LTE reference signal modes. In some examples of multi-TRP operation, each TRP may schedule PDSCH transmission (e.g., NR PDSCH transmission) via a corresponding DCI message (i.e., multi-TRP operation may be performed using multiple DCIs). Additionally or alternatively, if UE 315 is configured with a CORESET associated with a single TCI state corresponding to a corresponding TRP (e.g., via a coresetPoolIndex field set to 0), UE 315 may not be able to rate match NR PDSCH according to multiple overlapping LTE reference signal modes. That is, if UE 315 is configured to operate in a single TRP mode (e.g., perform single TRP operation), UE 315 may not rate match the PDSCH signal according to multiple overlapping LTE reference signal patterns. For example, UE 315 may be configured to (e.g., jointly) perform NR PDSCH rate matching according to one pattern or multiple overlapping patterns during multi-TRP operation and according to one pattern or multiple non-overlapping patterns during single TRP operation. However, such techniques may be inflexible and unsuitable for some communication scenarios.

[0124] In other examples, the UE 315 may be configured to support (e.g., and may be configured with) multiple overlapping LTE reference signal patterns, regardless of the UE 315's support for multi-TRP operation (or the UE 315's configuration for multi-TRP operation). For example, the UE 315 may receive an indication of a CORESET associated with an NR RAT and a TCI state corresponding to a particular TRP. The UE 315 may receive a scheduling message 337 that schedules a shared data signal (e.g., an NR PDSCH signal to be sent on the PDSCH 321) based on the CORESET. The UE 315 may receive a pattern indication message 336. In some examples, the pattern indication message 336 may indicate a pattern (e.g., an LTE reference signal pattern) for rate matching the NR PDSCH signal around resources (e.g., LTE reference signal resources) allocated for one or more reference signals associated with the second LTE RAT. In response, the UE 315 may communicate the NR PDSCH signal according to the pattern indicated via the pattern indication message 336. For example, UE 315 may receive an NR PDSCH signal on PDSCH 321 and may rate match the NR PDSCH signal around an LTE reference signal resource (e.g., reference signal resource 325) according to an LTE reference signal pattern. Such techniques may provide one or more improvements to spectral efficiency, such as during DSS (e.g., for LTE-NR coexistence).

[0125] Figure 4 An example of a process flow 400 for supporting a mode for controlling channel puncturing and sharing channel rate matching according to one or more aspects of the present disclosure is illustrated. The process flow 400 may implement or be implemented by one or more aspects of the wireless communication system 100, the network architecture 200, and the wireless communication system 300. For example, the process flow 400 may include a network entity 405 and a UE 415, which may be as described in reference Figures 1 to 3 Examples of corresponding devices described herein. Process flow 400 may be implemented by network entity 405, UE 415, or both. In the following description of process flow 400, operations between network entity 405 and UE 415 may occur in a different order or at a different time than shown. Some operations may also be omitted from process flow 400, and other operations may be added to process flow 400.

[0126] A wireless communication network may configure a communication device (e.g., UE 415) with multiple modes for rate matching a shared data channel signal (e.g., NR PDSCH signal) of a first RAT around resources (e.g., LTE reference signal resources) allocated for a reference signal of a second RAT. In some examples, the network (e.g., network entity 405) may configure UE 415 with multiple overlapping modes for rate matching NR PDSCH signals around LTE reference signal resources (e.g., NR PDSCH rate matching), regardless of whether UE 415 is configured for multi-TRP operation. For example, at 420, UE 415 may receive a first message (e.g., a shared data signal scheduling message) from network entity 405 that schedules a shared data signal (e.g., NR PDSCH signal) associated with a first RAT. In some examples, UE 415 may receive the shared data scheduling message based on a CORESET associated with a TCI state (e.g., corresponding to a TRP). For example, the network entity 405 may schedule an NR PDSCH signal for the UE 415 via a DCI message detected on a CORESET configured with an indicator set to 0 (e.g., the CORESETPoolIndex field is set to 0).

[0127] At 435, UE 415 may receive a second message (e.g., a rate matching mode indication message) indicating a pattern (e.g., an LTE reference signal pattern) for NR PDSCH rate matching. In some examples, the LTE reference signal pattern (e.g., indicated via the rate matching mode indication message received at 435) may be selected from (e.g., may be selected based on, may include) one or more LTE reference signal patterns from one or more lists configured for UE 415 (e.g., indicated to UE 415 via network entity 405). For example, at 430, UE 415 may receive another message (e.g., a rate matching mode list indication message) indicating one or more LTE reference signal pattern lists for NR PDSCH rate matching (e.g., via an lte-CRS-PatternList1 field, an lte-CRS-PatterList2-r16 field, or both).

[0128] In some examples, UE 415 may receive a rate matching pattern list indication message based on one or more capabilities of UE 415. For example, at 425, UE 415 may send a report (e.g., a UE capability report) indicating one or more UE capabilities associated with NR PDSCH rate matching. In such an example, UE 415 may receive a rate matching pattern list indication message (e.g., received at 430) based on one or more UE capabilities. In some examples, the rate matching pattern list indication message may indicate multiple (e.g., two) lists in which LTE reference signal patterns may overlap in frequency or may not overlap in frequency. For example, network entity 405 may enable multiple LTE reference signal patterns (e.g., multiple entries, two entries) in the list to overlap in frequency. Thus, the NR PDSCH signal (e.g., scheduled for UE 415 via the shared data signal scheduling message received at 420) may be rate matched around LTE resources according to the entries of a single list. For example, the NR-PDSCH signal may be rate matched around the LTE reference signal resources according to the LTE reference signal patterns in the list indicated via the lte-CRS-PatternList1 field, the lte-CRS-PatterList2-r16 field, or one or more other fields indicating other lists different from the list indicated via the lte-CRS-PatternList1 field and the lte-CRS-PatterList2-r16 field. In some examples, the network entity 405 may configure the UE 415 with a list in which the LTE reference signal patterns overlap in frequency (or do not overlap in frequency) based on one or more capabilities of the UE 415. For example, if the UE 415 indicates (e.g., announces) support for NR PDSCH rate matching via multiple overlapping patterns (e.g., via a UE capability report), the network entity 405 may enable the entries in the list to overlap in frequency. That is, the network entity 405 may configure the UE with one or more lists including LTE reference signal patterns that overlap in frequency based on the UE capability report.

[0129] Additionally or alternatively, the network entity 405 may configure (e.g., via RRC configuration) the UE 415 to rate match the NR PDSCH signal around the LTE reference signal resources according to the entries in the list based on the value of the indicator (e.g., the value of the CORESETPoolIndex field) configured for the CORESET (e.g., the CORESET associated with the search space on which the UE 415 receives the DCI that schedules the NR PDSCH signal). For example, the network entity 405 may configure the UE 415 so that if the NR PDSCH signal is scheduled by a DCI message (e.g., a format) detected on the search space associated with the CORESET configured with the indicator set to 0 (e.g., the coresetPoolIndex field is set to 0), the NR-PDSCH signal may be rate matched around the LTE reference signal resources according to the first list. Additionally or alternatively, the network entity 405 may configure the UE 415 such that if the NR PDSCH signal is scheduled via a DCI message detected on a search space associated with a CORESET configured with an indicator set to 1 (e.g., the coresetPoolIndex field is set to 1), the NR PDSCH signal may be rate matched around the LTE reference signal resources according to a second list (e.g., different from the first list).

[0130] Additionally or alternatively, the entries of the first list may overlap in frequency (or not overlap in frequency) with the entries of the second list. For example, the network entity 405 may enable one or more entries (e.g., the nth entry) of the first list (e.g., indicated via the lte-CRS-PatternList1 field) to overlap in frequency with one or more entries (e.g., the nth entry) of the second list (e.g., indicated via the lte-CRS-PatterList2-r16 field). That is, the network entity 405 may enable the LTE reference signal pattern associated with a specific pattern index in the first list (e.g., the nth pattern in the first list) and the LTE reference signal pattern associated with the same pattern index in the second list (e.g., the nth pattern in the first list) to overlap. Thus, the NR PDSCH signal (e.g., scheduled for the UE 415 via the shared data signal scheduling message received at 420) may be rate matched around the LTE resources according to entries of multiple lists (e.g., indicated via the lte-CRS-PatternList1 field, the lte-CRS-PatterList2-r16 field, or one or more other fields indicating other lists different from the lists indicated via the lte-CRS-PatternList1 field and the lte-CRS-PatterList2-r16 field). In some examples, the network entity 405 may configure the UE 415 with lists in which the entries overlap in frequency, regardless of whether the UE 415 is configured for multi-TRP operation. That is, the network entity 405 may configure the UE 415 (e.g., via RRC configuration) with a list in which LTE reference signal patterns overlap in frequency, regardless of the value of an indicator (e.g., the value of the CORESETPoolIndex field) configured for the CORESET (e.g., the CORESET on which the UE 415 receives the DCI scheduling the NR PDSCH signal).

[0131] At 440, UE 415 may communicate NR PDSCH signals according to the LTE reference signal pattern (e.g., indicated via the rate matching pattern indication message received at 435). For example, UE 315 may receive one or more PDSCH signals that are rate matched around LTE reference signal resources. In some examples, such techniques may provide one or more improvements in NR spectral efficiency for LTE and NR coexistence.

[0132] Figure 5An example of a process flow 500 for supporting a mode for controlling channel puncturing and sharing channel rate matching according to one or more aspects of the present disclosure is illustrated. The process flow 500 may implement or be implemented by one or more aspects of the wireless communication system 100, the network architecture 200, and the wireless communication system 300. For example, the process flow 500 may include a network entity 505 and a UE 515, which may be as described in reference Figures 1 to 3 Examples of corresponding devices described herein. Process flow 500 may be implemented by network entity 505, UE 515, or both. In the following description of process flow 500, operations between network entity 505 and UE 515 may occur in a different order or at a different time than shown. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500.

[0133] A wireless communication network (e.g., network entity 505) may configure a communication device (e.g., UE 515) with one or more patterns for puncturing control channel signals (e.g., NR PDCCH signals) of a first RAT around resources (e.g., LTE reference signal resources) allocated for reference signals of a second RAT. For example, at 520, UE 515 may receive a first message (e.g., CORESET indication message) indicating a CORESET associated with an NR RAT. At 535, UE 515 may receive a second message (e.g., puncturing pattern indication message) indicating a pattern (e.g., LTE reference signal pattern) for puncturing one or more NR PDCCH signals around LTE reference signal resources (e.g., for NRPDCCH puncturing). In some examples, the LTE reference signal pattern indicated via the puncturing pattern indication message (e.g., received at 535) may be based on the LTE reference signal pattern indicated to UE 515 for NR PDSCH rate matching. For example, the network entity 505 may configure the UE 515 (e.g., via the puncturing pattern indication message received at 535) to perform NR PDCCH puncturing according to an LTE reference signal pattern for NR PDSCH rate matching, such as indicated via the lte-CRS-ToMatchAround IE. Additionally or alternatively, the UE 515 may configure the UE 515 to perform NR PDCCH puncturing according to the LTE reference signal pattern, regardless of whether (or how) NR PDSCH rate matching is configured. For example, the UE 515 may be configured to perform NR PDCCH puncturing based on an LTE reference signal pattern for NR PDCCH puncturing indicated via another IE, such as the lte-CRS-ToMatchAround IE (or another IE indicating resource elements allocated for LTE reference signals).

[0134] In some examples, the LTE reference signal pattern for NR PDCCH puncturing (e.g., indicated via the puncturing pattern indication message received at 535) can be selected from one or more LTE reference signal patterns from one or more lists configured for UE 515 (e.g., indicated to UE 515 via network entity 505) (e.g., can be selected based on these patterns, can include these patterns). For example, at 530, UE 515 can receive another message (e.g., a puncturing pattern list indication message) indicating one or more lists of LTE reference signal patterns for NR PDCCH puncturing. In some examples, network entity 405 can configure UE 515 to perform NR PDCCH puncturing according to one or more LTE reference signal pattern lists configured for NR PDSCH rate matching. In such an example (e.g., in the case where UE 515 is configured with one or more lists for NR PDSCH rate matching), NR PDCCH puncturing can be based on one or more entries in the one or more lists (e.g., one or more LTE reference signal patterns from one or more of the lists indicated via the puncturing pattern indication message received at 535). In some examples, the network entity 505 may indicate to the UE 515 one or more lists for NR PDSCH rate matching via the lte-CRS-PatternList1 field, the lte-CRS-PatterList2-r16 field, or one or more other fields indicating other lists different from the lists indicated via the lte-CRS-PatternList1 field and the lte-CRS-PatterList2-r16 field. Additionally or alternatively, the network entity 505 may configure the UE 515 to perform NR PDCCH puncturing according to one or more LTE reference signal patterns in the one or more lists, regardless of whether (or how) NR PDSCH rate matching is configured. That is, the network may configure the UE 515 to perform NR-PDCCH signal puncturing based on another IE that provides one or more lists of LTE reference signal patterns for NR PDCCH puncturing.

[0135] For example, the LTE reference signal pattern used for NR PDCCH puncturing may be based on an entry from a list, multiple entries from a list (e.g., all entries), one entry from each of a plurality of lists, or multiple entries from each of a plurality of lists (e.g., all entries). That is, the UE 515 may perform NR PDSCH signal puncturing based on an LTE reference signal pattern selected from an entry from a list, multiple entries from a list (e.g., all entries), one entry from each of a plurality of lists, or multiple entries from each of a plurality of lists (e.g., all entries). In some examples, the UE 515 may be configured to select an entry (e.g., an LTE reference signal pattern) based on signaling from the network entity 505 (e.g., via RRC configuration). Additionally or alternatively, the UE 515 may select an LTE reference signal pattern based on a position of the LTE reference signal pattern within the list (e.g., a pattern position), which may be fixed (e.g., defined, such as the first entry in the list) or configured by the network entity 505 (e.g., via RRC configuration).

[0136] In some examples, the UE 515 may determine to perform NR PDCCH puncturing according to one or more entries (e.g., all entries) of a list configured for NR PDSCH rate matching (e.g., indicated via the lte-CRS-PatternList1 field or the lte-CRS-PatternList2 field) depending on the value of an indicator (e.g., the value of the coresetPoolIndex field) configured for a CORESET associated with a search space in which the UE 515 monitors the NR PDCCH signal. For example, if the UE 515 monitors the NR PDCCH signal in a search space associated with a CORESET configured with an indicator set to 0 (e.g., the value of the coresetPoolIndex field is set to 0), the LTE reference signal pattern used for NR PDCCH puncturing may be based on the first list (e.g., indicated via the lte-CRS-PatternList1 IE). Additionally or alternatively, if UE515 monitors NR PDCCH signals in a search space associated with a CORESET configured with an indicator set to 1 (e.g., the value of coresetPoolIndex is set to 1), the LTE reference signal pattern used for NR PDCCH puncturing may be based on a second list (e.g., indicated via lte-CRS-PatternList2 IE). In some examples, a CORESET (e.g., for monitoring NR PDCCH signals) may be configured with two TCI states (e.g., corresponding to two TRPs). In such an example, UE 515 may be configured to support monitoring of NR PDCCH signals from these two TRPs (e.g., may be configured to perform multi-TRP operation) and may be further configured with a system frame number for the monitoring (e.g., via an sfnSchemePdcch field, an sfnSchemeA field, or an sfnSchemeB field). In such examples (e.g., for NR PDCCH signal reception from multiple TRPs), NR PDCCH puncturing may be based on multiple (e.g., two) lists of LTE reference signal patterns (e.g., one list for each of the two TRPs).

[0137] Additionally or alternatively, the UE 515 may determine to perform NR PDCCH puncturing according to one or more entries of a list (e.g., LTE reference signal patterns) depending on the value of an indicator configured for a CORESET associated with a search space in which the UE 515 monitors NR PDCCH signals (e.g., the value of a coresetPoolIndex field) and regardless of whether (or how) NRPDSCH rate matching is configured. For example, the UE 515 may perform NR PDCCH puncturing based on a list of NR PDCCH puncturing patterns depending on the value of an indicator configured for a CORESET associated with a search space monitored by the UE 515 for NR PDCCH signals (e.g., the value of a coresetPoolIndex field). In some examples, the UE 515 may perform NR PDCCH puncturing based on a list or multiple lists (e.g., all lists) that include LTE reference signal patterns for NRPDCCH puncturing. In some examples, one or more lists of LTE reference signal patterns for NR PDCCH puncturing may be configured via signaling from the network (e.g., based on RRC configuration) for UE 515. For example, one or more lists of LTE reference signal patterns for NR PDCCH puncturing may be configured via the crs-RateMatch-PerCoresetPoolIndex IE or another IE indicating one or more lists of LTE reference signal patterns for NR PDCCH puncturing.

[0138] In some examples, the LTE reference signal pattern for NR PDCCH puncturing (e.g., indicated via the puncturing pattern indication message received at 535) may be based on one or more UE capabilities. For example, at 525, the UE 515 may send a report indicating at least one UE capability associated with puncturing NR PDCCH signals around LTE reference signal resources (e.g., a UE capability report). In such an example, the puncturing pattern indication message (e.g., received by the UE 515 at 535) may be based on the UE capability report. In some examples, the UE 515 may report the number (e.g., a maximum number or an otherwise suitable number) of LTE reference signal patterns for NR PDCCH puncturing via the UE capability report (e.g., signaling) sent at 525. In some examples, the UE 515 may report the number (e.g., maximum number or otherwise acceptable number) of LTE reference signal patterns that may be configured for NRPDCCH puncturing in a serving cell (e.g., network entity 505), the number (e.g., maximum number or otherwise acceptable number) of LTE reference signal patterns that may overlap in frequency and may be configured for NR PDCCH puncturing in a serving cell, the number (e.g., maximum number or otherwise acceptable number) of LTE reference signal patterns that may not overlap in frequency and may be configured for NR PDCCH puncturing in a serving cell, or the number (e.g., maximum number or otherwise acceptable number) of CORESETs that may be enabled for NR PDCCH puncturing (e.g., per downlink bandwidth portion or per serving cell). At 540, and in response to receiving the puncturing pattern indication message received at 535, the UE 515 may communicate one or more NRPDCCH signals according to the LTE reference signal pattern. For example, the UE 515 may receive one or more NR PDCCH signals that are punctured around LTE reference signal resources according to the LTE reference signal pattern. In some examples, UE 515 can increase utilization of network communication resources by puncturing NR PDCCH signals around LTE reference signal resources according to a pattern (e.g., an LTE reference signal pattern).

[0139] Figure 6 A block diagram 600 of a device 605 supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0140] Receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to patterns for control channel puncturing and shared channel rate matching, data channels, information channels). The information may be communicated to other components of device 605. Receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0141] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to patterns for control channel puncturing and shared channel rate matching, data channels, information channels). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0142] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the modes for controlling channel puncturing and shared channel rate matching as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

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

[0144] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured to or otherwise support means for performing the functionality described in the present disclosure).

[0145] In some examples, communication manager 620 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in conjunction with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0146] The communication manager 620 may support wireless communications at a UE (e.g., device 605) according to examples as disclosed herein. For example, the communication manager 620 may be configured to or otherwise support a means for receiving a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The communication manager 620 may be configured to or otherwise support a means for receiving a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT. The communication manager 620 may be configured to or otherwise support a means for communicating the at least one shared data signal according to the pattern.

[0147] Additionally or alternatively, the communication manager 620 may support wireless communications at the UE according to examples as disclosed herein. For example, the communication manager 620 may be configured to or otherwise support a means for receiving a first message indicating a CORESET associated with a first RAT. The communication manager 620 may be configured to or otherwise support a means for receiving a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for a reference signal associated with the second RAT. The communication manager 620 may be configured to or otherwise support a means for communicating the at least one control signal according to the pattern.

[0148] By including or configuring the communication manager 620 according to examples as described herein, the device 605 (e.g., a processor controlling the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof or otherwise coupled thereto) may support techniques for more efficiently utilizing communication resources, etc.

[0149] Figure 7 A block diagram 700 of a device 705 supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0150] Receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to patterns for control channel puncturing and shared channel rate matching, data channels, information channels). The information may be communicated to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0151] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to patterns for control channel puncturing and shared channel rate matching, data channels, information channels). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0152] Device 705 or its various components may be examples of components for performing various aspects of a pattern for controlling channel puncturing and shared channel rate matching as described herein. For example, communication manager 720 may include CORESET component 725, rate matching pattern component 730, signal component 735, puncturing pattern component 740, or any combination thereof. Communication manager 720 may be an example of various aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 710, transmitter 715, or both. For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated with receiver 710, transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0153] The communication manager 720 may support wireless communications at the UE according to examples as disclosed herein. The CORESET component 725 may be configured to or otherwise support a means for receiving a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The rate matching mode component 730 may be configured to or otherwise support a means for receiving a second message indicating a mode for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT. The signal component 735 may be configured to or otherwise support a means for communicating the at least one shared data signal according to the mode.

[0154] Additionally or alternatively, the communication manager 720 may support wireless communications at a UE (e.g., device 705) according to examples as disclosed herein. The CORESET component 725 may be configured to or otherwise support means for receiving a first message indicating a CORESET associated with a first RAT. The puncturing pattern component 740 may be configured to or otherwise support means for receiving a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for a reference signal associated with the second RAT. The signal component 735 may be configured to or otherwise support means for communicating the at least one control signal according to the pattern.

[0155] Figure 8A block diagram 800 of a communication manager 820 supporting a mode for controlling channel puncturing and sharing channel rate matching according to one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of the mode for controlling channel puncturing and sharing channel rate matching as described herein. For example, the communication manager 820 may include a CORESET component 825, a rate matching mode component 830, a signal component 835, a puncturing mode component 840, a list component 845, a report component 850, a TCI state indicator component 855, a mode selection component 860, a mode position component 865, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0156] The communication manager 820 may support wireless communications at a UE (e.g., UE 115) according to examples as disclosed herein. The CORESET component 825 may be configured to or otherwise support means for receiving a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The rate matching pattern component 830 may be configured to or otherwise support means for receiving a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT. The signal component 835 may be configured to or otherwise support means for communicating the at least one shared data signal according to the pattern.

[0157] In some examples, the list component 845 can be configured to or otherwise support a means for receiving a third message indicating a first list including a first set of multiple modes for rate matching, wherein the mode is based on two modes selected from the first set of multiple modes in the first list, and wherein the two modes overlap in frequency. In some examples, the report component 850 can be configured to or otherwise support a means for sending a report indicating at least one UE capability associated with rate matching, wherein receiving the third message is based on the at least one UE capability.

[0158] In some examples, the list component 845 may be configured or otherwise support a means for receiving a third message indicating a first list including a first set of multiple modes for rate matching and a second indication of a second list including a second set of multiple modes for rate matching, wherein the modes are based on a first mode selected from the first list and a second mode selected from the second list, and wherein the first mode and the second mode overlap in frequency or do not overlap in frequency. In some examples, the first mode and the second mode are associated with a mode index. In some examples, based on the mode index, the first mode is selected from the first list and the second mode is selected from the second list.

[0159] In some examples, list component 845 may be configured to or otherwise support a component for receiving a third message indicating a first list including a first set of multiple modes for rate matching and a second indication of a second list including a second set of multiple modes for rate matching, wherein the modes are based on two modes selected from the first list or the second list, and wherein the two modes overlap in frequency.

[0160] In some examples, the TCI state indicator component 855 may be configured as or otherwise support components for identifying an indicator associated with the TCI state, wherein the two modes are selected from a first list based on the indicator including a first value, and the two modes are selected from a second list based on the indicator including a second value different from the first value.

[0161] In some examples, mode selection component 860 may be configured or otherwise support means for receiving a fourth message indicating that the UE selects two modes from one of the first list or the second list. In some examples, mode selection component 860 may be configured or otherwise support means for selecting two modes from one of the first list or the second list based on the fourth message. In some examples, CORESET component 825 may be configured or otherwise support means for receiving a third message indicating a CORESET associated with the TCI state, wherein receiving the first message is based on the third message.

[0162] Additionally or alternatively, the communication manager 820 may support wireless communications at the UE according to examples as disclosed herein. In some examples, the CORESET component 825 may be configured to or otherwise support a means for receiving a first message indicating a CORESET associated with a first RAT. The puncturing pattern component 840 may be configured to or otherwise support a means for receiving a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for a reference signal associated with the second RAT. In some examples, the signal component 835 may be configured to or otherwise support a means for communicating the at least one control signal according to the pattern.

[0163] In some examples, the list component 845 may be configured or otherwise support means for receiving a third message indicating at least one list, wherein each list in the at least one list includes a set of multiple modes for punching, and wherein the mode is based on at least one mode selected from the at least one list. In some examples, the mode position component 865 may be configured or otherwise support means for receiving a fourth message indicating a mode position, wherein the mode is based on one of the at least one modes, and wherein the one mode is selected from a list in the at least one list according to the mode position.

[0164] In some examples, the mode is based on each of the at least one mode. In some examples, each of the at least one mode is selected from a list in the at least one list. In some examples, the mode is based on each of the at least one mode.

[0165] In some examples, CORESET component 825 can be configured to or otherwise support means for identifying an indicator associated with the CORESET, wherein the at least one mode is selected from a list in the at least one list, and wherein the list is based on a value of the indicator. In some examples, the second message includes an RRC message. In some examples, the second message indicates the mode via an IE.

[0166] In some examples, reporting component 850 may be configured to or otherwise support means for sending a report indicating at least one UE capability associated with puncturing control signals associated with the first RAT around resources allocated in the CORESET for reference signals associated with the second RAT, wherein receiving the second message is based on the at least one UE capability.

[0167] In some examples, the at least one UE capability includes: the UE's ability to support puncturing according to multiple patterns associated with a serving cell, the UE's ability to support puncturing according to multiple patterns that overlap in frequency and are associated with a serving cell, the UE's ability to support puncturing according to multiple patterns that do not overlap in frequency and are associated with a serving cell, the UE's ability to support puncturing for multiple CORESETs associated with a bandwidth portion or a serving cell, or any combination thereof.

[0168] Fig. 9 A diagram of a system 900 including a device 905 supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein, or include components of these devices. The device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0169] I / O controller 910 can manage input and output signals of device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor such as processor 940. In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

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

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

[0172] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) so that the device 905 performs various functions (e.g., functions or tasks supporting modes for controlling channel puncturing and shared channel rate matching). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0173] The communication manager 920 may support wireless communications at a UE (e.g., device 905) according to examples as disclosed herein. For example, the communication manager 920 may be configured to or otherwise support a means for receiving a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The communication manager 920 may be configured to or otherwise support a means for receiving a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT. The communication manager 920 may be configured to or otherwise support a means for communicating the at least one shared data signal according to the pattern.

[0174] Additionally or alternatively, the communication manager 920 may support wireless communications at a UE (e.g., device 905) according to examples as disclosed herein. For example, the communication manager 920 may be configured to or otherwise support a means for receiving a first message indicating a CORESET associated with a first RAT. The communication manager 920 may be configured to or otherwise support a means for receiving a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for a reference signal associated with the second RAT. The communication manager 920 may be configured to or otherwise support a means for communicating the at least one control signal according to the pattern.

[0175] By including or configuring a UE communication manager 920 according to examples as described herein, the device 905 may support techniques for improving communication reliability, reducing latency, and more efficiently utilizing communication resources, among other things.

[0176] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that are executable by the processor 940 to cause the device 905 to perform various aspects of the mode for controlling channel puncturing and shared channel rate matching as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0177] Fig.10A block diagram 1000 of a device 1005 supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0178] The receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0179] The transmitter 1015 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0180] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the modes for controlling channel puncturing and shared channel rate matching as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

[0183] In some examples, communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in conjunction with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0184] The communication manager 1020 may support wireless communication at a network entity (e.g., device 1005) according to examples as disclosed herein. For example, the communication manager 1020 may be configured to or otherwise support a means for sending a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The communication manager 1020 may be configured to or otherwise support a means for sending a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT. The communication manager 1020 may be configured to or otherwise support a means for communicating the at least one shared data signal according to the pattern.

[0185] Additionally or alternatively, the communication manager 1020 may support wireless communication at a network entity (e.g., device 1005) according to examples as disclosed herein. For example, the communication manager 1020 may be configured to or otherwise support means for sending a first message indicating a CORESET associated with a first RAT. The communication manager 1020 may be configured to or otherwise support means for sending a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for a reference signal associated with the second RAT. The communication manager 1020 may be configured to or otherwise support means for communicating the at least one control signal according to the pattern.

[0186] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof or otherwise coupled thereto) can support techniques for more efficiently utilizing communication resources, etc.

[0187] Fig.11 A block diagram 1100 of a device 1105 supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0188] The receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units), etc. The information may be communicated to other components of the device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0189] The transmitter 1115 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0190] The device 1105 or its various components may be examples of components for performing various aspects of the mode for controlling channel puncturing and shared channel rate matching as described herein. For example, the communication manager 1120 may include a scheduling component 1125, a mode indication component 1130, a data signal component 1135, a CORESET indication component 1140, a control signal component 1145, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to use or otherwise cooperate with the receiver 1110, the transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0191] The communication manager 1120 may support wireless communications at a network entity (e.g., device 1105) according to examples as disclosed herein. The scheduling component 1125 may be configured to or otherwise support means for sending a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The mode indication component 1130 may be configured to or otherwise support means for sending a second message indicating a mode for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT. The data signal component 1135 may be configured to or otherwise support means for communicating the at least one shared data signal according to the mode.

[0192] Additionally or alternatively, the communication manager 1120 may support wireless communications at a network entity (e.g., device 1105) according to examples as disclosed herein. The CORESET indication component 1140 may be configured to or otherwise support means for sending a first message indicating a CORESET associated with a first RAT. The mode indication component 1130 may be configured to or otherwise support means for sending a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for reference signals associated with the second RAT. The control signal component 1145 may be configured to or otherwise support means for communicating the at least one control signal according to the pattern.

[0193] Fig.12 A block diagram 1200 of a communication manager 1220 supporting a mode for controlling channel puncturing and sharing channel rate matching according to one or more aspects of the present disclosure is shown. The communication manager 1220 can be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components can be examples of means for performing various aspects of the mode for controlling channel puncturing and sharing channel rate matching as described herein. For example, the communication manager 1220 may include a scheduling component 1225, a mode indication component 1230, a data signal component 1235, a CORESET indication component 1240, a control signal component 1245, a list indication component 1250, a UE capability component 1255, a mode position indication component 1260, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0194] The communication manager 1220 may support wireless communications at a network entity (e.g., the network entity 105) according to examples as disclosed herein. The scheduling component 1225 may be configured to or otherwise support means for sending a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The mode indication component 1230 may be configured to or otherwise support means for sending a second message indicating a mode for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT. The data signal component 1235 may be configured to or otherwise support means for communicating the at least one shared data signal according to the mode.

[0195] In some examples, list indication component 1250 may be configured to or otherwise support means for sending a third message indicating a first list including a first set of multiple modes for rate matching, wherein the mode is based on two modes selected from the first set of multiple modes in the first list, and wherein the two modes overlap in frequency or do not overlap in frequency. In some examples, UE capability component 1255 may be configured to or otherwise support means for receiving a report indicating at least one UE capability associated with rate matching, wherein sending the third message is based on the at least one UE capability.

[0196] In some examples, the list indication component 1250 may be configured to or otherwise support a means for sending a third message indicating a first list including a first set of multiple modes for rate matching and a second indication of a second list including a second set of multiple modes for rate matching, wherein the modes are based on a first mode selected from the first list and a second mode selected from the second list, and wherein the first mode and the second mode overlap in frequency. In some examples, the first mode and the second mode are associated with a mode index. In some examples, based on the mode index, the first mode is selected from the first list and the second mode is selected from the second list.

[0197] In some examples, list indication component 1250 may be configured to or otherwise support components for sending a third message indicating a first list including a first set of multiple modes for rate matching and a second indication of a second list including a second set of multiple modes for rate matching, wherein the modes are based on two modes selected from one of the first list or the second list, and wherein the two modes overlap in frequency.

[0198] In some examples, the two modes are selected from the first list based on the indicator associated with the TCI state including a first value, and the two modes are selected from the second list based on the indicator associated with the TCI state including a second value different from the first value. In some examples, the mode indication component 1230 can be configured as or otherwise supports means for sending a fourth message indicating that the UE selects the two modes from one of the first list or the second list. In some examples, the CORESET indication component 1240 can be configured as or otherwise supports means for sending a third message indicating the CORESET associated with the TCI state, wherein receiving the first message is based on the third message.

[0199] Additionally or alternatively, the communication manager 1220 may support wireless communications at a network entity according to examples disclosed herein. The CORESET indication component 1240 may be configured to or otherwise support means for sending a first message indicating a CORESET associated with a first RAT. In some examples, the mode indication component 1230 may be configured to or otherwise support means for sending a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for reference signals associated with the second RAT. The control signal component 1245 may be configured to or otherwise support means for communicating the at least one control signal according to the pattern.

[0200] In some examples, list indication component 1250 may be configured or otherwise support means for sending a third message indicating at least one list, wherein each list in the at least one list includes a set of multiple modes for punching, and wherein the mode is based on at least one mode selected from the at least one list. In some examples, mode position component 1260 may be configured or otherwise support means for sending a fourth message indicating a mode position, wherein the mode is based on one of the at least one modes, and wherein the one mode is selected from a list in the at least one list according to the mode position.

[0201] In some examples, the mode is based on each of the at least one mode. In some examples, each of the at least one mode is selected from a list in the at least one list. In some examples, the mode is based on each of the at least one mode. In some examples, the at least one mode is selected from a list in the at least one list. In some examples, the list is based on a value of an indicator associated with a CORESET. In some examples, the second message includes an RRC message. In some examples, the second message indicates the mode via an IE.

[0202] In some examples, the UE capabilities component 1255 may be configured to or otherwise support a component for receiving a report indicating at least one UE capability associated with puncturing control signals associated with the first RAT around resources allocated in the CORESET for reference signals associated with the second RAT, wherein sending the second message is based on the at least one UE capability.

[0203] In some examples, the at least one UE capability includes: the UE's ability to support puncturing according to multiple patterns associated with a serving cell, the UE's ability to support puncturing according to multiple patterns that overlap in frequency and are associated with a serving cell, the UE's ability to support puncturing according to multiple patterns that do not overlap in frequency and are associated with a serving cell, the UE's ability to support puncturing for multiple CORESETs associated with a bandwidth portion or a serving cell, or any combination thereof.

[0204] Fig.13 A diagram of a system 1300 including a device 1305 supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein, or include components thereof. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support output and acquisition of communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0205] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 may also include a modem for modulating a signal, providing the modulated signal for transmission (e.g., by one or more antennas 1315, by a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and demodulating the signal. The transceiver 1310, or the transceiver 1310 and one or more antennas 1315 or wired interfaces (if applicable) may be examples of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

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

[0207] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1325) so that the device 1305 performs various functions (e.g., functions or tasks supporting modes for controlling channel puncturing and shared channel rate matching). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, the processor 1335 and the memory 1325 being configured to perform the various functions described herein. Processor 1335 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing functions of device 1305 (e.g., by executing code 1330).

[0208] In some examples, bus 1340 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1305, or communications performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

[0209] In some examples, communication manager 1320 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1320 may manage delivery of data communications for client devices such as one or more UEs 115. In some examples, communication manager 1320 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in coordination with other network entities 105. In some examples, communication manager 1320 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0210] The communication manager 1320 may support wireless communication at a network entity (e.g., device 1305) according to examples as disclosed herein. For example, the communication manager 1320 may be configured to or otherwise support means for sending a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The communication manager 1320 may be configured to or otherwise support means for sending a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT. The communication manager 1320 may be configured to or otherwise support means for communicating the at least one shared data signal according to the pattern.

[0211] Additionally or alternatively, the communication manager 1320 may support wireless communications at a network entity according to examples disclosed herein. For example, the communication manager 1320 may be configured to or otherwise support a means for sending a first message indicating a CORESET associated with a first RAT. The communication manager 1320 may be configured to or otherwise support a means for sending a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for a reference signal associated with the second RAT. The communication manager 1320 may be configured to or otherwise support a means for communicating the at least one control signal according to the pattern.

[0212] By including or configuring a communications manager 1320 according to examples as described herein, the device 1305 can support techniques for improving communications reliability, reducing latency, and more efficiently utilizing communications resources, among other things.

[0213] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (e.g., if applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1335, the memory 1325, the code 1330, the transceiver 1310, or any combination thereof. For example, the code 1330 may include instructions that are executable by the processor 1335 to cause the device 1305 to perform various aspects of the mode for controlling channel puncturing and shared channel rate matching as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0214] Fig.14 A flow chart illustrating a method 1400 for supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0215] At 1405, the method may include receiving a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The CORESET component 825 described above is used to perform the above operations.

[0216] At 1410, the method may include receiving a second message indicating a mode for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by Figure 8 The described rate matching mode component 830 is performed.

[0217] At 1415, the method may include communicating the at least one shared data signal according to the mode. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 8 The signal component 835 described is executed.

[0218] Fig.15 A flow chart illustrating a method 1500 for supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described functions may be performed by the UE 115. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0219] At 1505, the method may include receiving a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The CORESET component 825 described above is used to perform the above operations.

[0220] At 1510, the method may include receiving a third message indicating a first list including a set of multiple modes for rate matching. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The described list component 845 is executed.

[0221] At 1515, the method may include receiving a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with the second RAT, wherein the pattern is based on two patterns selected from the first plurality of patterns in the first list, and wherein the two patterns overlap in frequency. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by Figure 8 The described rate matching mode component 830 is performed.

[0222] At 1520, the method may include communicating the at least one shared data signal according to the mode. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 8 The signal component 835 described is executed.

[0223] Fig.16 A flow chart illustrating a method 1600 for supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described functions may be performed by the UE 115. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0224] At 1605, the method may include receiving a first message indicating a CORESET associated with a first RAT. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 8The CORESET component 825 described above is used to perform the above operations.

[0225] At 1610, the method may include receiving, based on the CORESET, a second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for reference signals associated with the second RAT. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by Figure 8 The described punching mode component 840 is executed.

[0226] At 1615, the method may include communicating the at least one control signal according to the mode. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference Figure 8 The signal component 835 described is executed.

[0227] Fig.17 A flow chart illustrating a method 1700 for supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described functions may be performed by the UE 115. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0228] At 1705, the method may include receiving a first message indicating a CORESET associated with a first RAT. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figure 8 The CORESET component 825 described above is used to perform the above operations.

[0229] At 1710, the method may include receiving a third message indicating at least one list, wherein each list in the at least one list includes a set of multiple modes for puncturing. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Figure 8 The described list component 845 is executed.

[0230] At 1715, the method may include receiving, based on the CORESET, a second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for reference signals associated with the second RAT, wherein the pattern is based on at least one pattern selected from the at least one list. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by Figure 8 The described punching mode component 840 is executed.

[0231] At 1720, the method may include communicating the at least one control signal according to the mode. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Figure 8 The signal component 835 described is executed.

[0232] Fig.18 A flow chart illustrating a method 1800 for supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0233] At 1805, the method may include sending a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.12 The described scheduling component 1225 is executed.

[0234] At 1810, the method may include sending a second message indicating a mode for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with the second RAT. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by Fig.12 The described mode instructs component 1230 to execute.

[0235] At 1815, the method may include communicating the at least one shared data signal according to the mode. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.12 The data signal component 1235 described is executed.

[0236] Fig.19 A flow chart illustrating a method 1900 for supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0237] At 1905, the method may include sending a first message based on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.12 The described scheduling component 1225 is executed.

[0238] At 1910, the method may include sending a third message indicating a first list including a set of multiple modes for rate matching. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.12 The described listing instructs component 1250 to execute.

[0239] At 1915, the method may include sending a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with the second RAT, wherein the pattern is based on two patterns selected from the first plurality of patterns in the first list, and wherein the two patterns overlap in frequency or do not overlap in frequency. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed by reference to Fig.12 The described mode instructs component 1230 to execute.

[0240] At 1920, the method may include communicating the at least one shared data signal according to the mode. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Fig.12 The data signal component 1235 described is executed.

[0241] Fig. 20 A flow chart illustrating a method 2000 for supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0242] At 2005, the method may include sending a first message indicating a CORESET associated with a first RAT. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.12 The described CORESET instructs component 1240 to execute.

[0243] At 2010, the method may include sending, based on the CORESET, a second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for reference signals associated with the second RAT. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed by as described in reference Fig.12 The described mode instructs component 1230 to execute.

[0244] At 2015, the method may include communicating the at least one control signal according to the mode. The operations of 2015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed as described in reference to Fig.12 The control signal component 1245 described is executed.

[0245] Fig.21 A flow chart illustrating a method 2100 for supporting a mode for controlling channel puncturing and shared channel rate matching according to one or more aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2100 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0246] At 2105, the method may include sending a first message indicating a CORESET associated with the first RAT. The operations of 2105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed as described in reference to Fig.12 The described CORESET instructs component 1240 to execute.

[0247] At 2110, the method may include sending a third message indicating at least one list, wherein each list in the at least one list includes a set of multiple modes for puncturing. The operations of 2110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed as described in reference to Fig.12 The described listing instructs component 1250 to execute.

[0248] At 2115, the method may include sending a second message based on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for reference signals associated with the second RAT, wherein the pattern is based on at least one pattern selected from the at least one list. The operations of 2115 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed by as described in reference Fig.12 The described mode instructs component 1230 to execute.

[0249] At 2120, the method may include communicating the at least one control signal according to the mode. The operations of 2120 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2120 may be performed as described in reference to Fig.12 The control signal component 1245 described is executed.

[0250] The following provides an overview of various aspects of the disclosure:

[0251] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a first message based at least in part on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT; receiving a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT; and communicating the at least one shared data signal according to the pattern.

[0252] Aspect 2: According to the method described in Aspect 1, the method also includes: receiving a third message, the third message indicating a first list including a first plurality of modes for rate matching, wherein the mode is at least partially based on two modes selected from the first plurality of modes in the first list, and wherein the two modes overlap in frequency.

[0253] Aspect 3: According to the method of aspect 2, the method also includes: sending a report indicating at least one UE capability associated with the rate matching, wherein receiving the third message is at least partially based on the at least one UE capability.

[0254] Aspect 4: According to the method according to Aspect 1, the method also includes: receiving a third message indicating a first list including a first plurality of modes for rate matching and a second indication of a second list including a second plurality of modes for rate matching, wherein the modes are at least partially based on a first mode selected from the first list and a second mode selected from the second list, and wherein the first mode and the second mode overlap in frequency or do not overlap in frequency.

[0255] Aspect 5: A method according to aspect 4, wherein the first mode and the second mode are associated with a mode index, and based at least in part on the mode index, the first mode is selected from the first list and the second mode is selected from the second list.

[0256] Aspect 6: According to the method according to Aspect 1, the method also includes: receiving a third message indicating a first list including a first plurality of modes for rate matching and a second indication of a second list including a second plurality of modes for rate matching, wherein the modes are at least partially based on two modes selected from the first list or the second list, and wherein the two modes overlap in frequency.

[0257] Aspect 7: According to the method described in Aspect 6, the method also includes: identifying an indicator associated with the TCI state, wherein the two modes are selected from the first list at least in part based on the indicator including a first value, and the two modes are selected from the second list at least in part based on the indicator including a second value different from the first value.

[0258] Aspect 8: According to the method described in Aspect 6, the method also includes: receiving a fourth message instructing the UE to select the two modes from one of the first list or the second list; and selecting the two modes from one of the first list or the second list based at least in part on the fourth message.

[0259] Aspect 9: According to any one of aspects 1 to 8, the method further includes: receiving a third message indicating the CORESET associated with the TCI state, wherein receiving the first message is at least partially based on the third message.

[0260] Aspect 10: A method for wireless communication at a UE, the method comprising: receiving a first message indicating a CORESET associated with a first RAT; receiving a second message based at least in part on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for a reference signal associated with a second RAT; and communicating the at least one control signal according to the pattern.

[0261] Aspect 11: According to the method according to Aspect 10, the method also includes: receiving a third message indicating at least one list, wherein each list in the at least one list includes multiple modes for punching, and wherein the mode is at least partially based on at least one mode selected from the at least one list.

[0262] Aspect 12: According to the method of Aspect 11, the method also includes: receiving a fourth message indicating a mode position, wherein the mode is at least partially based on one of the at least one modes, and wherein the one mode is selected from a list in the at least one list according to the mode position.

[0263] Aspect 13: The method according to aspect 11, wherein the mode is based at least in part on each of the at least one mode, and each of the at least one mode is selected from a list in the at least one list.

[0264] Aspect 14: The method according to aspect 11, wherein the mode is based at least in part on each mode of the at least one mode.

[0265] Aspect 15: The method according to aspect 11, the method further comprising: identifying an indicator associated with the CORESET, wherein the at least one mode is selected from a list in the at least one list, and wherein the list is based at least in part on the value of the indicator.

[0266] Aspect 16: The method according to any one of aspects 10 to 15, wherein the second message comprises an RRC message, and the second message indicates the mode via an information element.

[0267] Aspect 17: According to any one of Aspects 10 to 16, the method also includes: sending a report indicating at least one UE capability associated with puncturing a control signal associated with the first RAT around the resources allocated in the CORESET for the reference signal associated with the second RAT, wherein receiving the second message is at least partially based on the at least one UE capability.

[0268] Aspect 18: A method according to Aspect 17, wherein the at least one UE capability includes: the UE's ability to support puncturing according to multiple modes associated with a serving cell, the UE's ability to support puncturing according to multiple modes that overlap in frequency and are associated with a serving cell, the UE's ability to support puncturing according to multiple modes that do not overlap in frequency and are associated with a serving cell, the UE's ability to support puncturing for multiple CORESETs associated with a bandwidth part or a serving cell, or any combination thereof.

[0269] Aspect 19: A method for wireless communication at a network entity, the method comprising: sending a first message based at least in part on a CORESET associated with a TCI state, the first message scheduling at least one shared data signal associated with a first RAT; sending a second message indicating a pattern for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second RAT; and communicating the at least one shared data signal according to the pattern.

[0270] Aspect 20: According to the method described in Aspect 19, the method also includes: sending a third message, wherein the third message indicates a first list including a first plurality of modes for rate matching, wherein the mode is at least partially based on two modes selected from the first plurality of modes in the first list, and wherein the two modes overlap in frequency or do not overlap in frequency.

[0271] Aspect 21: The method according to aspect 20, the method also includes: receiving a report indicating at least one UE capability associated with the rate matching, wherein sending the third message is at least partially based on the at least one UE capability.

[0272] Aspect 22: According to the method according to Aspect 19, the method also includes: sending a third message indicating a first list including a first plurality of modes for rate matching and a second indication of a second list including a second plurality of modes for rate matching, wherein the modes are at least partially based on a first mode selected from the first list and a second mode selected from the second list, and wherein the first mode and the second mode overlap in frequency.

[0273] Aspect 23: A method according to Aspect 22, wherein the first mode and the second mode are associated with a mode index, and based at least in part on the mode index, the first mode is selected from the first list and the second mode is selected from the second list.

[0274] Aspect 24: According to the method according to Aspect 19, the method also includes: sending a third message indicating a first list including a first plurality of modes for rate matching and a second indication of a second list including a second plurality of modes for rate matching, wherein the modes are at least partially based on two modes selected from one of the first list or the second list, and wherein the two modes overlap in frequency.

[0275] Aspect 25: A method according to Aspect 24, wherein the two modes are selected from the first list at least in part based on the indicator associated with the TCI state including a first value, and the two modes are selected from the second list at least in part based on the indicator associated with the TCI state including a second value different from the first value.

[0276] Aspect 26: The method according to aspect 24, the method further comprising: sending a fourth message instructing the UE to select the two modes from one of the first list or the second list.

[0277] Aspect 27: The method according to any one of Aspects 19 to 26, the method further comprising: sending a third message indicating the CORESET associated with the TCI state, wherein receiving the first message is at least partially based on the third message.

[0278] Aspect 28: A method for wireless communication at a network entity, the method comprising: sending a first message indicating a CORESET associated with a first RAT; sending a second message based at least in part on the CORESET, the second message indicating a pattern for puncturing at least one control signal associated with the first RAT around resources allocated in the CORESET for a reference signal associated with a second RAT; and communicating the at least one control signal according to the pattern.

[0279] Aspect 29: According to the method according to Aspect 28, the method also includes: sending a third message indicating at least one list, wherein each list in the at least one list includes multiple modes for punching, and wherein the mode is at least partially based on at least one mode selected from the at least one list.

[0280] Aspect 30: According to the method of Aspect 29, the method also includes: sending a fourth message indicating a mode position, wherein the mode is at least partially based on one of the at least one modes, and wherein the one mode is selected from a list in the at least one list according to the mode position.

[0281] Aspect 31: The method according to aspect 29, wherein the mode is based at least in part on each of the at least one mode, and each of the at least one mode is selected from a list in the at least one list.

[0282] Aspect 32: The method according to aspect 29, wherein the mode is based at least in part on each mode of the at least one mode.

[0283] Aspect 33: The method according to aspect 29, wherein the at least one mode is selected from a list in the at least one list, and the list is based at least in part on a value of an indicator associated with the CORESET.

[0284] Aspect 34: A method according to any one of Aspects 28 to 33, wherein the second message comprises an RRC message, and the second message indicates the mode via an information element.

[0285] Aspect 35: According to any one of Aspects 28 to 34, the method also includes: receiving a report indicating at least one UE capability associated with puncturing a control signal associated with the first RAT around the resources allocated in the CORESET for the reference signal associated with the second RAT, wherein sending the second message is at least partially based on the at least one UE capability.

[0286] Aspect 36: A method according to Aspect 35, wherein the at least one UE capability includes: the UE's ability to support puncturing according to multiple modes associated with a serving cell, the UE's ability to support puncturing according to multiple modes that overlap in frequency and are associated with a serving cell, the UE's ability to support puncturing according to multiple modes that do not overlap in frequency and are associated with a serving cell, the UE's ability to support puncturing for multiple CORESETs associated with a bandwidth portion or a serving cell, or any combination thereof.

[0287] Aspect 37: An apparatus for performing wireless communication at a UE, the apparatus comprising: a memory; and a processor, the processor being coupled to the memory and configured to cause the apparatus to perform a method according to any one of aspects 1 to 9.

[0288] Aspect 38: An apparatus for wireless communication at a UE, the apparatus comprising at least one means for performing a method according to any one of aspects 1 to 9.

[0289] Aspect 39: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 9.

[0290] Aspect 40: An apparatus for wireless communication at a UE, the apparatus comprising: a memory; and a processor, the processor being coupled to the memory and configured to cause the apparatus to perform a method according to any one of aspects 10 to 18.

[0291] Aspect 41: An apparatus for wireless communication at a UE, the apparatus comprising at least one means for performing a method according to any one of aspects 10 to 18.

[0292] Aspect 42: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 10 to 18.

[0293] Aspect 43: An apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and a processor, the processor being coupled to the memory and configured to cause the apparatus to perform a method according to any one of aspects 19 to 27.

[0294] Aspect 44: An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing the method according to any one of aspects 19 to 27.

[0295] Aspect 45: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 19 to 27.

[0296] Aspect 46: An apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and a processor, the processor being coupled to the memory and configured to cause the apparatus to perform a method according to any one of aspects 28 to 36.

[0297] Aspect 47: An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing a method according to any one of aspects 28 to 36.

[0298] Aspect 48: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 28 to 36.

[0299] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

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

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

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

[0303] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent on a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0304] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0305] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0306] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0307] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.

[0308] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." Specific embodiments include specific details to provide an understanding of the technology. However, the technologies may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

[0309] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and a processor coupled to the memory and configured to: receiving a first message scheduling at least one shared data signal associated with a first radio access technology based at least in part on a control resource set associated with a transmit configuration indicator state; receiving a second message indicating a mode for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second radio access technology; as well as The at least one shared data signal is communicated according to the mode.

2. The apparatus of claim 1, wherein the processor is further configured to: A third message is received, the third message indicating a first list including a first plurality of modes for rate matching, wherein the modes are based at least in part on two modes selected from the first plurality of modes in the first list, and wherein the two modes overlap in frequency.

3. The apparatus of claim 2, wherein the processor is further configured to: A report is sent indicating at least one UE capability associated with the rate matching, wherein receiving the third message is based at least in part on the at least one UE capability.

4. The apparatus of claim 1, wherein the processor is further configured to: A third message is received indicating a first list including a first plurality of modes for rate matching and a second indication of a second list including a second plurality of modes for rate matching, wherein the modes are based at least in part on a first mode selected from the first list and a second mode selected from the second list, and wherein the first mode and the second mode overlap in frequency or do not overlap in frequency.

5. The device according to claim 4, wherein: The first mode and the second mode are associated with a mode index, and Based at least in part on the mode index, the first mode is selected from the first list and the second mode is selected from the second list.

6. The apparatus of claim 1, wherein the processor is further configured to: A third message is received indicating a first list of a first plurality of modes for rate matching and a second indication of a second list of a second plurality of modes for rate matching, wherein the modes are based at least in part on two modes selected from the first list or the second list, and wherein the two modes overlap in frequency.

7. The apparatus of claim 6, wherein the processor is further configured to: Identify an indicator associated with the transmit configuration indicator state, wherein the two modes are selected from the first list based at least in part on the indicator including a first value, and the two modes are selected from the second list based at least in part on the indicator including a second value different from the first value.

8. The apparatus of claim 6, wherein the processor is further configured to: receiving a fourth message instructing the UE to select the two modes from one of the first list or the second list; and The two modes are selected from one of the first list or the second list based at least in part on the fourth message.

9. The apparatus of claim 1, wherein the processor is further configured to: A third message is received indicating the set of control resources associated with the transmit configuration indicator state, wherein receiving the first message is based at least in part on the third message.

10. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and a processor coupled to the memory and configured to: receiving a first message indicating a set of control resources associated with a first radio access technology; receiving a second message based at least in part on the set of control resources, the second message indicating a pattern for puncturing at least one control signal associated with the first radio access technology around resources in the set of control resources allocated for reference signals associated with a second radio access technology; as well as The at least one control signal is communicated according to the mode.

11. The apparatus of claim 10, wherein the processor is further configured to: A third message is received indicating at least one list, wherein each list of the at least one list includes a plurality of patterns for puncturing, and wherein the patterns are based at least in part on at least one pattern selected from the at least one list.

12. The apparatus of claim 11, wherein the processor is further configured to: A fourth message is received indicating a mode position, wherein the mode is based at least in part on one of the at least one mode, and wherein the one of the modes is selected from a list of the at least one list based on the mode position.

13. The device according to claim 11, wherein: The mode is based at least in part on each of the at least one mode, and Each mode of the at least one mode is selected from a list of the at least one list.

14. The apparatus of claim 11, wherein the mode is based at least in part on each of the at least one mode.

15. The apparatus of claim 11, wherein the processor is further configured to: An indicator associated with the set of control resources is identified, wherein the at least one mode is selected from a list in the at least one list, and wherein the list is based at least in part on a value of the indicator.

16. The device according to claim 10, wherein: The second message comprises a radio resource control message, and The second message indicates the mode via an information element.

17. The apparatus of claim 10, wherein the processor is further configured to: sending a report indicating at least one UE capability associated with puncturing control signals associated with the first radio access technology around the resources in the control resource set allocated for the reference signals associated with the second radio access technology, wherein receiving the second message is based at least in part on the at least one UE capability.

18. The apparatus of claim 17, wherein the at least one UE capability comprises: The UE supports the ability to perform puncturing according to multiple patterns associated with a serving cell, the UE supports the ability to perform puncturing according to multiple patterns that overlap in frequency and are associated with a serving cell, the UE supports the ability to perform puncturing according to multiple patterns that do not overlap in frequency and are associated with a serving cell, the UE supports the ability to perform puncturing for multiple control resource sets associated with a bandwidth portion or a serving cell, or any combination thereof.

19. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and a processor coupled to the memory and configured to: transmitting a first message scheduling at least one shared data signal associated with a first radio access technology based at least in part on a set of control resources associated with a transmit configuration indicator state; sending a second message indicating a mode for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second radio access technology; as well as The at least one shared data signal is communicated according to the mode.

20. The apparatus of claim 19, wherein the processor is further configured to: A third message is sent, the third message indicating a first list including a first plurality of modes for rate matching, wherein the modes are based at least in part on two modes selected from the first plurality of modes in the first list, and wherein the two modes overlap in frequency or do not overlap in frequency.

21. The apparatus of claim 20, wherein the processor is further configured to: A report is received indicating at least one user equipment (UE) capability associated with the rate matching, wherein sending the third message is based at least in part on the at least one UE capability.

22. The apparatus of claim 19, wherein the processor is further configured to: Sending a third message indicating a first list of first multiple modes for rate matching and a second indication of a second list of second multiple modes for rate matching, wherein the modes are at least partially based on a first mode selected from the first list and a second mode selected from the second list, and wherein the first mode and the second mode overlap in frequency.

23. The apparatus of claim 19, wherein the processor is further configured to: Sending a third message indicating a first list of a first plurality of modes for rate matching and a second indication of a second list of a second plurality of modes for rate matching, wherein the modes are based at least in part on two modes selected from one of the first list or the second list, and wherein the two modes overlap in frequency.

24. The apparatus of claim 23, wherein the processor is further configured to: A fourth message is sent to instruct the UE to select the two modes from one of the first list or the second list.

25. The apparatus of claim 19, wherein the processor is further configured to: A third message is transmitted indicating the set of control resources associated with the transmit configuration indicator state, wherein receiving the first message is based at least in part on the third message.

26. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and a processor coupled to the memory and configured to: sending a first message indicating a set of control resources associated with a first radio access technology; sending a second message based at least in part on the set of control resources, the second message indicating a pattern for puncturing at least one control signal associated with the first radio access technology around resources in the set of control resources allocated for reference signals associated with a second radio access technology; as well as The at least one control signal is communicated according to the mode.

27. The apparatus of claim 26, wherein the processor is further configured to: A third message is sent indicating at least one list, wherein each list of the at least one list includes a plurality of patterns for puncturing, and wherein the patterns are based at least in part on at least one pattern selected from the at least one list.

28. The apparatus of claim 27, wherein the processor is further configured to: A fourth message is sent indicating a mode position, wherein the mode is based at least in part on one of the at least one mode, and wherein the one of the modes is selected from a list of the at least one list based on the mode position.

29. The apparatus of claim 26, wherein: The second message comprises a radio resource control message, and The second message indicates the mode via an information element.

30. The apparatus of claim 26, wherein the processor is further configured to: receiving a report indicating at least one user equipment (UE) capability associated with puncturing control signals associated with the first radio access technology around the resources allocated in the control resource set for the reference signals associated with the second radio access technology, wherein sending the second message is based at least in part on the at least one UE capability.

31. A method for wireless communication at a user equipment (UE), the method comprising: receiving a first message scheduling at least one shared data signal associated with a first radio access technology based at least in part on a control resource set associated with a transmit configuration indicator state; receiving a second message indicating a mode for rate matching the at least one shared data signal around resources allocated for one or more reference signals associated with a second radio access technology; as well as The at least one shared data signal is communicated according to the mode.