Unified transmit configuration indicator (TCI) or prioritized TCI state in single frequency network operation

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a mobile station may receive a unified transmit configuration indicator (TCI) indication indicating a first TCI state associated with a physical downlink shared channel (PDSCH) communication, where a time resource associated with the PDSCH communication at least partially overlaps a time resource associated with a control resource set (CORESET), where the time resource associated with the PDSCH communication at least partially overlaps a time resource associated with the control resource set (CORESET). The control resource set (CORESET) is associated with a second TCI state that is different from the first TCI state. The mobile station may prioritize reception of physical downlink control channel (PDCCH) communications associated with the CORESET based at least in part on the second TCI state being different from the first TCI state. Numerous other aspects are described.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for unifying transmission configuration indicators (TCIs) or prioritizing TCI states in single frequency network operations. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to a method of wireless communication performed by a mobile station. The method may include receiving, by the mobile station, a unified transmission configuration indicator (TCI) indication indicating a first TCI state associated with a physical downlink shared channel (PDSCH) communication, wherein time resources associated with the PDSCH communication overlap at least partially with time resources associated with a control resource set (CORESET), the control resource set (CORESET) being associated with a second TCI state different from the first TCI state. The method may include prioritizing, by the mobile station, reception of a physical downlink control channel (PDCCH) communication associated with the CORESET based at least in part on the second TCI state being different from the first TCI state.

[0006] Some aspects described herein relate to a method of wireless communication performed by a mobile station. The method may include receiving, by the mobile station, a scheduled downlink control information (DCI) communication associated with a single frequency network (SFN) PDSCH communication, wherein the scheduled DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a CORESET, the CORESET being associated with a second TCI state different from the first TCI state. The method may include prioritizing, by the mobile station, reception of a PDCCH communication associated with the CORESET based at least in part on the second TCI state being different from the first TCI state.

[0007] Some aspects described herein relate to a mobile station for wireless communication. The mobile station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a unified TCI indication indicating a first TCI state associated with a PDSCH communication, wherein time resources associated with the PDSCH communication at least partially overlap with time resources associated with a CORESET, and the CORESET is associated with a second TCI state different from the first TCI state. The one or more processors may be configured to prioritize reception of a PDCCH communication associated with the CORESET based at least in part on the second TCI state being different from the first TCI state.

[0008] Some aspects described herein relate to a mobile station for wireless communication. The mobile station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a scheduling DCI communication associated with an SFN PDSCH communication, wherein the scheduling DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a CORESET, the CORESET being associated with a second TCI state different from the first TCI state. The one or more processors may be configured to prioritize reception of a PDCCH communication associated with a CORESET based at least in part on the second TCI state being different from the first TCI state.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a mobile station. The instruction set, when executed by one or more processors of the mobile station, may cause the mobile station to receive a unified TCI indication indicating a first TCI state associated with a PDSCH communication, wherein time resources associated with the PDSCH communication at least partially overlap with time resources associated with a CORESET, the CORESET being associated with a second TCI state different from the first TCI state. The instruction set, when executed by one or more processors of the mobile station, may cause the mobile station to prioritize reception of a PDCCH communication associated with a CORESET at least in part based on the second TCI state being different from the first TCI state.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a mobile station. The instruction set, when executed by one or more processors of the mobile station, may cause the mobile station to receive a scheduled DCI communication associated with an SFN PDSCH communication, wherein the scheduled DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a CORESET, the CORESET being associated with a second TCI state different from the first TCI state. The instruction set, when executed by one or more processors of the mobile station, may cause the mobile station to prioritize reception of a PDCCH communication associated with a CORESET at least in part based on the second TCI state being different from the first TCI state.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a unified TCI indication indicating a first TCI state associated with a PDSCH communication, wherein time resources associated with the PDSCH communication at least partially overlap with time resources associated with a CORESET associated with a second TCI state different from the first TCI state. The apparatus may include means for prioritizing reception of a PDCCH communication associated with the CORESET based at least in part on the second TCI state being different from the first TCI state.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a scheduled DCI communication associated with an SFN PDSCH communication, wherein the scheduled DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a CORESET associated with a second TCI state different from the first TCI state. The apparatus may include means for prioritizing reception of a PDCCH communication associated with the CORESET based at least in part on the second TCI state being different from the first TCI state.

[0013] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0014] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations of the claims.

[0015] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0018] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example resource structure for wireless communication according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of transmission reception point differentiation based at least in part on a control resource set pool index at a UE according to the present disclosure.

[0022] Figure 6is a diagram illustrating an example of access link communication between a network node and a UE using a beam according to the present disclosure.

[0023] Figure 7 is a diagram illustrating an example associated with prioritized TCI states in a unified Transmission Configuration Indication (TCI) operation according to the present disclosure.

[0024] FIG. 8A to FIG. 8B is a diagram illustrating another example associated with prioritized TCI states in unified TCI operation according to the present disclosure.

[0025] Fig. 9 is a diagram illustrating an example associated with prioritized TCI states in single frequency network operation according to the present disclosure.

[0026] Fig.10 is a diagram illustrating an example associated with a prioritized TCI state in a unified TCI or single frequency network operation according to the present disclosure.

[0027] Fig.11 is a diagram illustrating an example process performed, for example, by a mobile station according to the present disclosure.

[0028] Fig.12 is a diagram illustrating an example process performed, for example, by a mobile station according to the present disclosure.

[0029] Fig.13 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0030] Fig.14 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0031] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0032] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0034] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0035] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0036] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0037] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0038] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0039] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0040] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.

[0041] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0042] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0043] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0044] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0045] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0046] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0047] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0048] In some aspects, UE 120 may correspond to a mobile station described elsewhere herein. In addition, in some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: receive a unified transmission configuration indicator (TCI) indication indicating a first TCI state associated with a physical downlink shared channel (PDSCH) communication, wherein time resources associated with the PDSCH communication at least partially overlap with time resources associated with a control resource set (CORESET), the control resource set (CORESET) being associated with a second TCI state different from the first TCI state; and prioritize reception of a physical downlink control channel (PDCCH) communication associated with the CORESET based at least in part on the second TCI state being different from the first TCI state. Additionally or alternatively, the communication manager 140 may: receive a scheduled downlink control information (DCI) communication associated with a single frequency network (SFN) PDSCH communication, wherein the scheduled DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a CORESET, the CORESET being associated with a second TCI state different from the first TCI state; and prioritize reception of the PDCCH communication associated with the CORESET based at least in part on the second TCI state being different from the first TCI state. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0049] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

[0050] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0051] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0052] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0053] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0054] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0055] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 7 to 14 ) any aspects of any of the methods described herein.

[0056] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 7 to 14 ) any aspects of any of the methods described herein.

[0057] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the UE 120 may perform one or more techniques associated with the prioritized TCI state in unified TCI or single frequency network operation as described in more detail elsewhere herein. In some aspects, the mobile station described herein is a UE 120, is included in a UE 120, or includes Figure 2 One or more components of the UE 120 shown. The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.11 Process 1100, Fig.12 1200 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion and / or interpretation), may cause one or more processors, UE 120 and / or network node 110 to perform or direct, for example, Fig.11 Process 1100, Fig.12 The process 1200 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0058] In some aspects, the mobile station may include: means for receiving a unified TCI indication indicating a first TCI state associated with a PDSCH communication, wherein time resources associated with the PDSCH communication overlap at least partially with time resources associated with a CORESET associated with a second TCI state different from the first TCI state; and / or means for prioritizing reception of PDCCH communications associated with the CORESET based at least in part on the second TCI state being different from the first TCI state. In some aspects, means for the mobile station to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0059] In some aspects, the mobile station may include: means for receiving a scheduling DCI communication associated with a SFN PDSCH communication, wherein the scheduling DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication overlap at least partially with time resources associated with a CORESET associated with a second TCI state different from the first TCI state; and / or means for prioritizing reception of PDCCH communications associated with the CORESET based at least in part on the second TCI state being different from the first TCI state. In some aspects, means for the mobile station to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0060] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0061] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0062] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0063] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0064] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0065] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RTRIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0066] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0067] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 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, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0068] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0069] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0070] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 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 (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0071] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 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 through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0072] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to regulate RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0073] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.

[0074] Figure 4 4 is a diagram illustrating an example resource structure 400 for wireless communication according to the present disclosure. Resource structure 400 shows examples of various resource groups described herein. As shown, resource structure 400 may include subframe 405. Subframe 405 may include multiple time slots 410. Although resource structure 400 is shown as including 2 time slots per subframe, a different number of time slots (e.g., 4 time slots, 8 time slots, 16 time slots, 32 time slots, or another number of time slots) may be included in a subframe. In some aspects, in addition to subframes and / or time slots, different types of transmit time intervals (TTIs) may be used. Time slots 410 may include multiple symbols 415, such as 14 symbols per time slot.

[0075] The potential control region of the time slot 410 may be referred to as a CORESET 420, and may be configured to support efficient use of resources, such as by flexibly configuring or reconfiguring the resources of the CORESET 420 for one or more PDCCHs and / or one or more PDSCHs. In some aspects, the CORESET 420 may occupy the first symbol 415 of the time slot 410, the first two symbols 415 of the time slot 410, or the first three symbols 415 of the time slot 410. Thus, the CORESET 420 may include multiple resource blocks (RBs) in the frequency domain, and one, two, or three symbols 415 in the time domain. In 5G, the number of resources included in the CORESET 420 may be flexibly configured (such as by using RRC signaling to indicate the frequency domain region (e.g., the number of resource blocks) and / or the time domain region (e.g., the number of symbols) of the CORESET 420).

[0076] As shown, a symbol 415 including a CORESET 420 may include one or more control channel elements (CCEs) 425 (shown as two CCEs 425 as an example) across a portion of the system bandwidth. The CCEs 425 may include DCI for providing control information for wireless communications. The network node 110 may transmit DCI during a plurality of CCEs 425 (as shown), wherein the number of CCEs 425 used for DCI transmission represents an aggregation level (AL) used by the network node 110 for DCI transmission. Figure 4 4, an aggregation level of two is shown as an example, which corresponds to two CCEs 425 in time slot 410. In some aspects, a different aggregation level may be used, such as 1, 2, 4, 8, 16, or another aggregation level.

[0077] Each CCE 425 may include a fixed number of resource element groups (REGs) 430 (shown as 6 REGs 430), or may include a variable number of REGs 430. In some aspects, the number of REGs 430 included in a CCE 425 may be specified by a REG cluster size. A REG 430 may include one resource block, which may include 12 resource elements (REs) 435 within a symbol 415. A resource element 435 may occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.

[0078] The search space may include all possible locations where a PDCCH may be located (e.g., in time and / or frequency). CORESET 420 may include one or more search spaces, such as a UE-specific search space, a group common search space, and / or a common search space. The search space may indicate a set of CCE positions in which a UE 120 may find a PDCCH that may potentially be used to send control information to the UE 120. The possible locations of a PDCCH may depend on whether the PDCCH is a UE-specific PDCCH (e.g., for a single UE 120) or a group common PDCCH (e.g., for multiple UEs 120), and / or the aggregation level being used. The possible locations of a PDCCH (e.g., in time and / or frequency) may be referred to as PDCCH candidates, and the set of all possible PDCCH locations at an aggregation level may be referred to as a search space. For example, a set of all possible PDCCH locations for a specific UE 120 may be referred to as a UE-specific search space. Similarly, a set of all possible PDCCH locations for all UEs 120 may be referred to as a common search space. The set of all possible PDCCH locations for a particular group of UEs 120 may be referred to as a group-common search space.One or more search spaces across aggregation levels may be referred to as a search space (SS) set.

[0079] The CORESET 420 may be interleaved or non-interleaved. An interleaved CORESET 420 may have a CCE to REG mapping such that adjacent CCEs are mapped to scattered REG bundles in the frequency domain (e.g., adjacent CCEs are not mapped to continuous REG bundles of the CORESET 420). A non-interleaved CORESET 420 may have a CCE to REG mapping such that all CCEs are mapped to continuous REG bundles of the CORESET 420 (e.g., in the frequency domain).

[0080] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Different than described.

[0081] Figure 5 is a diagram illustrating an example of TRP differentiation based at least in part on a CORESET pool index at a UE 120 in accordance with the present disclosure. In some aspects, a CORESET pool index (or CORESETPoolIndex) value may be used by a UE 120 to identify a TRP associated with an uplink grant received on a PDCCH.

[0082] like Figure 5 As illustrated, UE 120 may be configured to have multiple CORESETs in a given serving cell. Each CORESET configured for UE 120 may be associated with a CORESET identifier (CORESET ID). For example, a first CORESET configured for UE 120 may be associated with CORESET ID 1, a second CORESET configured for UE 120 may be associated with CORESET ID 2, a third CORESET configured for UE 120 may be associated with CORESET ID 3, and a fourth CORESET configured for UE 120 may be associated with CORESET ID 4.

[0083] like Figure 5 As further illustrated in , two or more (e.g., up to five) CORESETs may be grouped into CORESET pools. Each CORESET pool may be associated with a CORESET pool index. For example, CORESET ID 1 and CORESET ID 2 may be grouped into CORESET pool index 0, and CORESET ID 3 and CORESET ID 4 may be grouped into CORESET pool index 1. In a multi-TRP configuration, each CORESET pool index value may be associated with a particular TRP 505. As an example, and as Figure 5As illustrated, the first TRP 505 (TRP A) (or the first network node 110) may be associated with a CORESET pool index 0, and the second TRP 505 (TRP B) (or the second network node 110) may be associated with a CORESET pool index 1. The UE 120 may be configured with information identifying an association between a TRP and a CORESET pool index value assigned to the TRP via a higher layer parameter such as PDCCH-Config. Thus, the UE may identify the TRP that sent the DCI uplink grant by determining the CORESET ID of the CORESET in which the PDCCH carrying the DCI uplink grant was sent, determining the CORESET pool index value associated with the CORESET pool in which the CORESET ID is included, and identifying the TRP associated with the CORESET pool index value.

[0084] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Different than described.

[0085] Figure 6 6 is a diagram illustrating an example 600 of using beams for access link communications between a network node 110 and a UE 120 according to the present disclosure. Figure 6 As shown, network node 110 and UE 120 may communicate with each other in a wireless network (eg, wireless network 100).

[0086] The network node 110 may transmit to a UE 120 located within the coverage area of ​​the network node 110. The network node 110 and the UE 120 may be configured for beamformed communications, wherein the network node 110 may transmit in the direction of the UE 120 using a directional NN transmit beam, and the UE 120 may receive the transmission using a directional UE receive beam. Each NN transmit beam may have an associated beam ID, beam direction, or beam symbol, etc. The network node 110 may transmit downlink communications via one or more NN transmit beams 605.

[0087] UE 120 may attempt to receive a downlink transmission via one or more UE receive beams 610, which may be configured using different beamforming parameters at a receive circuit of UE 120. UE 120 may identify a particular NN transmit beam 605 (shown as NN transmit beam 605-A) and a particular UE receive beam 610 (shown as UE receive beam 610-A) that provide relatively good performance (e.g., having the best channel quality among different measured combinations of NN transmit beams 605 and UE receive beams 610). In some examples, UE 120 may send an indication of which NN transmit beam 605 UE 120 identifies as a preferred NN transmit beam, and network node 110 may select the preferred NN transmit beam to transmit to UE 120. Thus, UE 120 can obtain and maintain a beam pair link (BPL) for downlink communication with network node 110 (e.g., a combination of NN transmit beam 605-A and UE receive beam 610-A), which can be further refined and maintained based on one or more established beam refinement processes.

[0088] A downlink beam (such as a NN transmit beam 605 or a UE receive beam 610) may be associated with a TCI state. The TCI state may indicate the directionality or characteristics of the downlink beam, such as one or more quasi-co-location (QCL) characteristics of the downlink beam. The QCL characteristics may include, for example, Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters, etc. In some examples, the TCI state may be associated with one or more QCL types (sometimes referred to as qclType). For example, in some examples, the TCI state may be associated with one of four QCL types (referred to as QCL type A, QCL type B, QCL type C, and QCL type D), which indicate which large-scale channel characteristics are common across QCL channels. More specifically, QCL type A may be associated with channel characteristics of Doppler shift, Doppler spread, average delay, and delay spread, and may be used for the purpose of obtaining channel state information (CSI). QCL type B may be associated with channel characteristics of Doppler shift and Doppler spread, and may similarly be used for the purpose of obtaining CSI. QCL type C may be associated with channel characteristics of average delay and delay spread and may be used for the purpose of obtaining measurement information such as RSRP, etc. And QCL type D may be associated with spatial receiver parameters and may be used for the purpose of supporting beamforming, as described more fully below.

[0089] In some examples, each NN transmit beam 605 may be associated with a synchronization signal block (SSB), and the UE 120 may indicate a preferred NN transmit beam 605 by transmitting an uplink transmission in the resources of the SSB associated with the preferred NN transmit beam 605. A particular SSB may have an associated TCI state (e.g., for an antenna port or for beamforming). In some examples, the network node 110 may indicate a downlink NN transmit beam 605 based at least in part on an antenna port QCL characteristic that may be indicated by the TCI state. For different QCL types (e.g., QCL types for different combinations of Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters, etc.), the TCI state may be associated with a downlink reference signal set (e.g., SSB, and aperiodic, periodic, or semi-persistent CSI reference signal (CSI-RS)). In the case where the QCL type indicates spatial reception parameters (e.g., QCL type D), the QCL type may correspond to analog reception beamforming parameters of the UE reception beam 610 at the UE 120. Thus, the UE 120 may select the corresponding UE reception beam 610 from the BPL set based at least in part on the network node 110 indicating the NN transmit beam 605 via the TCI indication.

[0090] The network node 110 may maintain an activated TCI state set for downlink shared channel transmission and an activated TCI state set for downlink control channel transmission. The activated TCI state set for downlink shared channel transmission may correspond to a beam that the network node 110 uses for downlink transmission on PDSCH. The activated TCI state set for downlink control channel communication may correspond to a beam that the network entity 110 may use for downlink transmission on PDCCH or in CORESET. The UE 120 may also maintain the activated TCI state set for receiving downlink shared channel transmission and CORESET transmission. In the case where the TCI state is activated for the UE 120, the UE 120 may have one or more antenna configurations based at least in part on the TCI state, and the UE 120 may not need to reconfigure the antenna or antenna weighting configuration. In some examples, the set of activated TCI states (eg, activated PDSCH TCI states and activated CORESET TCI states) for UE 120 may be configured by a configuration message, such as an RRC message (eg, an RRCReconfiguration message).

[0091] Similarly, for uplink communications, UE 120 may transmit in the direction of network node 110 using a directional UE transmit beam, and network node 110 may receive the transmission using a directional NN receive beam. Each UE transmit beam may have an associated beam identifier (ID), beam direction or beam symbol, etc. UE 120 may transmit uplink communications via one or more UE transmit beams 615.

[0092] The network node 110 may receive uplink transmissions via one or more NN receive beams 620. The network node 110 may identify specific UE transmit beams 615 (shown as UE transmit beams 615-A) and specific NN receive beams 620 (shown as NN receive beams 620-A) that provide relatively good performance (e.g., having the best channel quality of different measured combinations of UE transmit beams 615 and NN receive beams 620). In some examples, the network node 110 may send an indication of which UE transmit beam 615 the network node 110 identifies as a preferred UE transmit beam, which the network node 110 may select to transmit from the UE 120. Thus, the UE 120 and the network node 110 may obtain and maintain a BPL for uplink communications (e.g., a combination of the UE transmit beam 615-A and the NN receive beam 620-A), which may be further refined and maintained according to one or more established beam refinement procedures. An uplink beam, such as a UE transmit beam 615 or a NN receive beam 620, may be associated with a spatial relationship. The spatial relationship may indicate a directionality or characteristic (similar to one or more QCL characteristics) of the uplink beam, as described above.

[0093] Additionally or alternatively, such as Figure 6As shown, the network node 110 and the UE 120 may communicate using a unified TCI framework, in which case the network node 110 may indicate a TCI state that the UE 120 will use for beamformed uplink communications. For example, in the unified TCI framework, a joint TCI state (which may be referred to as a joint downlink and uplink TCI state) may be used to indicate a common beam that the UE 120 will use for downlink and uplink communications. In this case, the joint downlink and uplink TCI state may include at least one source reference signal to provide a reference (or UE assumption) for determining QCL characteristics for downlink communications or a spatial filter for uplink communications. For example, the joint downlink and uplink TCI state may be associated with providing one or more source reference signals for UE-specific PDSCH reception in a component carrier and common QCL information for one or more CORESETs, or providing a reference to determine one or more common uplink transmit spatial filters for a physical uplink shared channel (PUSCH) based on a dynamically granted or configured grant or one or more dedicated physical uplink control channel (PUCCH) resources in a component carrier.

[0094] Additionally or alternatively, the unified TCI framework may support separate downlink TCI states and separate uplink TCI states to accommodate separate downlink beam indications and uplink beam indications (e.g., in the case where the best uplink beam does not correspond to the best downlink beam, and vice versa). In such cases, each valid uplink TCI state configuration may include a source reference signal to indicate an uplink transmit beam (e.g., a target uplink reference signal or a target uplink channel) for a target uplink communication. For example, the source reference signal may be a sounding reference signal (SRS), an SSB, or a CSI-RS, etc., and the target uplink communication may be a PRACH, a PUCCH, a PUSCH, an SRS, and / or a DMRS (e.g., for a PUCCH or a PUSCH), etc. In this way, supporting a joint TCI state or separate downlink TCI states and uplink TCI states may enable a unified TCI framework for downlink and uplink communications, and / or may enable the network node 110 to indicate various uplink QCL relationships (e.g., Doppler shift, Doppler spread, average delay or delay spread, etc.) for uplink TCI communications.

[0095] In some cases, the UE 120 may receive an indication of a unified TCI state that indicates a TCI state that is different from the TCI state associated with the CORESET. In some other aspects, the UE 120 may receive an indication of a TCI state associated with SFN PDSCH communication that is different from the TCI state associated with the CORESET. In other words, in some cases, the CORESET may be associated with a TCI state that does not follow the indicated unified TCI state and / or the indicated TCI state associated with the SFN PDSCH communication. In such cases, if the CORESET is at least partially overlapped in the time domain with another communication associated with the indicated unified TCI state and / or the indicated TCI state associated with the SFN PDSCH communication, the UE 120 may not be able to receive the two communications using the corresponding TCI state (e.g., beam). Therefore, in such cases, UE 120 may not be able to receive control signaling (e.g., PDCCH communication in CORESET), data communication (e.g., PDSCH communication associated with the unified TCI state, or SFN PDSCH communication associated with the indicated TCI state, etc.), resulting in increased communication errors and therefore increased latency, reduced throughput, and increased power, computing and network resource consumption associated with correcting communication errors, etc.

[0096] Some techniques and apparatus described herein enable prioritization of a TCI state associated with a CORESET when the CORESET at least partially overlaps in the time domain with another communication, such as a PDSCH communication associated with a unified TCI state, a SFN PDSCH communication associated with an indicated TCI state, or the like. For example, in some aspects, a UE 120 may receive a unified TCI indication indicating a unified TCI state associated with a PDSCH communication that at least partially overlaps with a CORESET associated with a different TCI state. Based at least in part on the CORESET TCI state being different from the unified TCI state, the UE 120 may prioritize reception of communications associated with the CORESET (e.g., PDCCH communications associated with the CORESET) to ensure that control information is securely received. In some other aspects, the UE 120 may receive a scheduling DCI for a SFN PDSCH communication, the scheduling DCI indicating a TCI state associated with the SFN PDSCH communication, wherein the SFN PDSCH communication at least partially overlaps with a CORESET associated with a different TCI state. Based at least in part on the CORESET TCI state being different from the SFN PDSCH communication TCI state, the UE 120 may prioritize reception of communications associated with the CORESET (e.g., PDCCH communications associated with the CORESET) to ensure that control information is securely received. Thus, communication errors may be reduced, resulting in reduced latency, increased throughput, reduced power, computational, and network resource consumption associated with correcting communication errors, and an overall more efficient use of network resources.

[0097] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Different than described.

[0098] Figure 7 is a diagram illustrating an example 700 associated with prioritized TCI states in unified TCI operations according to the present disclosure.

[0099] Figure 7Various signals, communications, or messages that a mobile station (e.g., UE 120) or other wireless communication device may receive from another wireless communication device (e.g., network node 110) are illustrated. More specifically, as indicated by reference numeral 705, a mobile station may receive a TCI indication from a network node 110 or similar wireless communication device. The TCI indication may be received via a DCI communication (and therefore may sometimes be referred to as a TCI indication DCI), a MAC control element (MAC-CE) communication, or a similar communication. In some aspects, the TCI indication may be a unified TCI indication as part of a unified TCI framework. The TCI indication may indicate one or more TCI states to be used by the mobile station. For example, the TCI indication may indicate a unified TCI state associated with a downlink communication (such as a PDSCH communication). In some aspects, the TCI state indicated by the TCI indication may be used as a default TCI state by the mobile station. That is, the TCI state may be the TCI state for receiving downlink communications in the absence of an explicit indication (e.g., from the network node 110 or similar wireless communication device) for the mobile station to use a different TCI state for a particular communication, or in the absence of a prioritization rule that prioritizes another TCI state over the default TCI state (which prioritization rule will be described in more detail below in conjunction with reference numeral 730). In this regard, the one or more TCI states indicated by the TCI indication may sometimes be referred to as the default TCI state.

[0100] As shown by reference numeral 710, in some aspects, a mobile station may receive a scheduling DCI. The scheduling DCI may indicate one or more resources associated with an upcoming communication (such as a downlink communication). For example, the scheduling DCI may indicate resources associated with downlink data transmission. More specifically, in some aspects, the scheduling DCI may indicate resources associated with a PDSCH communication as shown by reference numeral 715. In some aspects, the scheduling DCI may be received in the same component carrier as the PDSCH communication (the PDSCH communication is sometimes referred to as a self-scheduled PDSCH communication). In some other aspects, the scheduling DCI may be received in a component carrier different from the component carrier used to receive the PDSCH communication (the PDSCH communication is sometimes referred to as a cross-carrier scheduled PDSCH communication). In addition, as described above in conjunction with reference numeral 705, in some aspects, the mobile station may be configured or otherwise indicated with a default TCI state, such as a unified TCI state indicated by the TCI indication described in conjunction with reference numeral 705. Thus, in the absence of an indication in the scheduling DCI or otherwise of another TCI state to be used for PDSCH communications, the mobile station may apply a default TCI state to reception of PDSCH communications, as indicated by the dashed arrow shown by reference numeral 720. For example, in some aspects, the TCI indication may indicate that the default TCI state and / or unified TCI state is a TCI state indexed as TCI 1. Thus, the mobile station may receive PDSCH communications using a beam associated with TCI 1.

[0101] In some aspects, time resources associated with PDSCH communications may at least partially overlap (e.g., overlap in at least one symbol) with a CORESET, such as the CORESET shown by reference numeral 725. Further, in some aspects, the CORESET may not be associated with a default TCI state and / or a unified TCI state (e.g., TCI1 in this example). More specifically, in aspects where a mobile station receives a TCI indication indicating a unified TCI state, the CORESET may have a TCI state that does not follow the indicated TCI state. For example, Figure 7 As shown, the CORESET may be associated with a TCI state indexed as TCI2. In this regard, if the mobile station applies a default TCI state and / or a unified TCI state (e.g., TCI1) during time resources associated with overlapping PDSCH communications and the CORESET, there is a risk that the mobile station may not be able to securely receive control information associated with the CORESET (e.g., PDCCH communications sent in the CORESET).

[0102] Thus, in some aspects, when PDSCH communications associated with a default TCI state and / or a unified TCI state (e.g., TCI1) at least partially overlap with a CORESET associated with another TCI state (e.g., TCI2), the mobile station may prioritize reception of the CORESET (e.g., the mobile station may prioritize reception of PDCCH communications associated with the CORESET) to ensure that control information, etc., is securely received by the mobile station. In other words, the mobile station may receive PDCCH communications using beams associated with the TCI state associated with the CORESET, and possibly PDSCH communications in some aspects (if the mobile station is capable of receiving PDSCH communications using the TCI state associated with the CORESET). More specifically, as indicated by reference numeral 730 and by using Figure 7 As shown by the solid arrow in (as opposed to the dashed arrow shown in conjunction with the default TCI state indicated by reference numeral 720), the CORESET TCI state (e.g., TCI2) may be used by the mobile station to receive CORESET (e.g., PDCCH communications associated with the CORESET) and / or PDSCH communications. In this regard, the mobile station may increase the likelihood that control information carried by the PDCCH communications associated with the CORESET is securely received even though the control information is associated with a TCI state that is different from the default TCI state and / or the unified TCI state.

[0103] In some aspects, prioritizing reception of PDCCH communications associated with a CORESET (e.g., using a beam associated with the CORESET during a time period when the CORESET at least partially overlaps with PDSCH communications) can be based at least in part on whether an offset between the scheduled DCI and the PDSCH communications is less than a threshold duration (sometimes referred to as timeDurationForQCL). The threshold duration (e.g., timeDurationForQCL) can be associated with a time period during which a QCL parameter associated with a TCI state remains valid. In some aspects, a mobile station can prioritize reception of PDCCH communications associated with a CORESET (e.g., using a beam associated with the CORESET during a time period when the CORESET at least partially overlaps with PDSCH communications) based at least in part on whether an offset between the scheduled DCI communications and the PDSCH communications is less than a threshold duration (e.g., timeDurationForQCL). The threshold duration (e.g., timeDurationForQCL) can be associated with a time period during which a QCL parameter associated with a TCI state remains valid. Figure 7 As shown) to prioritize the reception of PDCCH communications associated with the CORESET.

[0104] Additionally or alternatively, prioritizing reception of PDCCH communications associated with the CORESET (e.g., using a beam associated with the CORESET during a time period when the CORESET at least partially overlaps with PDSCH communications) may be based at least in part on the QCL type associated with the scheduling DCI. More specifically, in some aspects, the mobile station may prioritize reception of PDCCH communications associated with the CORESET (e.g., using a beam associated with the CORESET during a time period when the CORESET at least partially overlaps with PDSCH communications). Figure 7 The depicted aspect is that a default TCI state or TCI1) is associated with QCL type D (eg, a QCL type associated with spatial receiver parameters for the purpose of supporting beamforming) to prioritize reception of PDCCH communications associated with a CORESET.

[0105] In some aspects, combined Figure 7 The operations shown and described can be summarized as follows: In RRC connected mode, regardless of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2, if the offset between the reception of the DL DCI and the reception of the corresponding self-scheduled or cross-carrier scheduled PDSCH is less than the threshold timeDurationForQCL and at least one configured TCI state of the serving cell for the scheduled PDSCH contains a qcl-type set to "Type D", if the default TCI of the scheduled PDSCH is the indicated unified TCI, and if the qcl-type of the PDSCH DMRS from the default TCI is set to "Type D" is different from the qcl-type of the PDCCH DMRS (where they overlap in at least one symbol), the UE is expected to prioritize the reception of the PDCCH associated with the CORESET. This also applies to intra-band carrier aggregation cases (when the PDSCH and CORESET are in different component carriers).

[0106] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 Different than described.

[0107] FIG. 8A to FIG. 8B is a diagram illustrating another example 800 associated with prioritized TCI states in unified TCI operation according to the present disclosure.

[0108] Similar to combining Figure 7 The signals, communications and / or messages described, FIG. 8A to FIG. 8B 1 illustrates various signals, communications, or messages that a mobile station (e.g., UE 120) or other wireless communication device may receive from another wireless communication device (e.g., network node 110). More specifically, as Fig. 8AAs shown, as indicated by reference numeral 805, the mobile station may receive a TCI indication from the network node 110. The TCI indication may be received via a DCI indication (e.g., a TCI indication DCI), a MAC-CE communication, or the like. The TCI indication may indicate one or more TCI states to be used by the mobile station. For example, the TCI indication may indicate a unified TCI state associated with downlink communications (such as PDSCH communications). In some aspects, the TCI state indicated by the TCI indication may be used by the mobile station as a default TCI state in a similar manner as described above in conjunction with reference numeral 705.

[0109] As shown by reference numeral 810, in some aspects, a mobile station may receive a scheduling DCI, which scheduling DCI (similar to the scheduling DCI described in conjunction with reference numeral 710) may indicate one or more resources associated with an upcoming communication, such as resources associated with a PDSCH communication, as shown by reference numeral 815. In some aspects, the scheduling DCI may be received in the same component carrier as the PDSCH communication (such as a self-scheduled PDSCH communication). In some other aspects, the scheduling DCI may be received in a different component carrier than the component carrier used to receive the PDSCH communication (such as a cross-carrier scheduled PDSCH communication).

[0110] In some aspects, a mobile station may be associated with more than one default TCI state. Further, in some aspects, a particular default TCI state to be used for receiving a given PDSCH communication may be based at least in part on an indicated TCI state (e.g., a unified TCI state indicated by a TCI indication, which is indicated in Fig. 8A In the example shown, the first default state or TCI1 may be referred to as the first default state or TCI1) is associated with a physical cell identifier (PCI) that is different from the serving cell PCI. For example, in some aspects, if the indicated TCI is associated with the serving cell PCI (sometimes referred to as intra-cell operation), the mobile station may use the indicated TCI for both mobile station-specific PDSCH communications and non-mobile station-specific PDSCH communications. In this regard, intra-cell operation may result in a state similar to that associated with Figure 7 The prioritization rules described (e.g., based at least in part on the CORESET TCI state being different from the unified TCI state associated with the PDSCH communication, the mobile station may prioritize reception of the PDCCH communication associated with the CORESET). That is, the mobile station may apply the first default TCI state (e.g., the unified TCI state, or TCI1 in this example) to the reception of the PDSCH communication, as indicated by the dashed arrow shown by reference numeral 820.

[0111] In some other aspects, if the indicated TCI is associated with a PCI that is different from the serving cell PCI (sometimes referred to as inter-cell operation), the mobile station may apply a different QCL assumption (e.g., a different TCI state may be applied to the reception of PDSCH communications). More specifically, as indicated by reference numeral 825, in some aspects, for inter-cell operation, the mobile station may apply the TCI state associated with the lowest CORESET ID in the most recent timeslot. That is, the mobile station may apply a second default TCI state (e.g., the TCI associated with the lowest CORESET ID, or TCI3 in this example) to the reception of PDSCH communications, as indicated by the dashed arrow shown by reference numeral 830. Additionally or alternatively, in some aspects, if the QCL type D characteristics associated with multiple default beams in timeslots of component carriers in a frequency band are different, the default beam of the component carrier with the lowest ID is prioritized (e.g., the default beam of the component carrier with the lowest ID is applied to all component carriers in the frequency band).

[0112] In any case, whether the mobile station applies the first default TCI state to PDSCH communications (as described above in conjunction with reference numeral 820) or the second default TCI state to PDSCH communications (as described above in conjunction with reference numeral 830), if the TCI state associated with the CORESET is different from the applied default TCI state (e.g., one of the first default TCI state (TCI1) or the second default TCI state (TCI3)), the mobile station may prioritize reception of communications associated with the CORESET. More specifically, in some aspects, time resources associated with PDSCH communications may at least partially overlap with a CORESET, such as the CORESET shown by reference numeral 835. Further, in some aspects, the CORESET may not be associated with a default TCI state (e.g., one of TCI1 or TCI3 in this example). More specifically, in aspects where the mobile station receives a TCI indication indicating a unified TCI state, or alternatively, when the mobile station applies the TCI state associated with the lowest CORESET ID in the most recent timeslot, the CORESET may not have a TCI state that does not follow the unified TCI state or the TCI state associated with the lowest CORESET ID in the most recent timeslot. Fig. 8AAs shown, the CORESET may be associated with a TCI state indexed as TCI2. In this regard, if the mobile station applies a default TCI state (e.g., TCI1 or TCI3) during time resources associated with overlapping PDSCH communications and the CORESET, there is a risk that the mobile station may not be able to securely receive control information associated with the CORESET (e.g., PDCCH communications sent in the CORESET).

[0113] Thus, in some aspects, when PDSCH communications associated with a default TCI state (e.g., TCI1 or TCI3) at least partially overlap with a CORESET associated with another TCI state (e.g., TCI2), the mobile station may prioritize reception of the CORESET (e.g., the mobile station may prioritize reception of PDCCH communications associated with the CORESET) to ensure that control information, etc., is safely received by the mobile station. In other words, the mobile station may receive PDCCH communications (and, in some aspects, PDSCH communications, as described above in conjunction with the TCI state associated with the CORESET) using beams associated with the TCI state associated with the CORESET. Figure 7 More specifically, as indicated by reference numeral 840 and by using Fig. 8A As shown by the solid arrows in FIG. 8 (as opposed to the dashed arrows shown in conjunction with the default TCI state indicated by reference numerals 820 and 830), the CORESET TCI (e.g., TCI2) may be used by the mobile station to receive the CORESET (e.g., PDCCH communications associated with the CORESET) and / or PDSCH communications. In this regard, the mobile station may increase the likelihood that control information carried by the PDCCH communications associated with the CORESET is securely received even though the CORESET is associated with a TCI state different from the default TCI state.

[0114] Combined with Figure 7 In a similar manner as described, in some aspects, prioritizing the reception of PDCCH communications associated with the CORESET (e.g., using a beam associated with the CORESET during a time period where the CORESET at least partially overlaps with PDSCH communications) may be based at least in part on whether an offset between the scheduling DCI and the PDSCH communications is below a threshold duration (e.g., timeDurationForQCL). Additionally or alternatively, prioritizing the reception of PDCCH communications associated with the CORESET may be based at least in part on an association of a TCI state associated with the scheduling DCI (which, in the aspect depicted in FIG. 8 , may be one of a first default TCI state TCI1 or a second default TCI state TCI3, as described) with a QCL type D (e.g., a QCL type associated with spatial receiver parameters for the purpose of supporting beamforming).

[0115] like Figure 8B As shown, in some aspects, the scheduling DCI may be transmitted on a first component carrier (CC) (in Figure 8B The PDSCH communication scheduled by the scheduling DCI may be received in a second component carrier (shown as "CC1" in FIG. 1 ) different from the first component carrier. Figure 8B In such aspects, the default TCI state may be based at least in part on whether the indicated TCI state (e.g., the TCI state indicated by the TCI indication described in conjunction with reference numeral 805) is associated with the PCI of the scheduled component carrier (e.g., CC2). More specifically, if the indicated TCI state in the active bandwidth part (BWP) of the scheduled component carrier (e.g., CC2) is associated with the serving cell PCI of the scheduled component carrier, the mobile station may select the indicated TCI state (e.g., the TCI state indicated by the TCI indication described in conjunction with reference numeral 805) from the active BWP of the scheduled CC. Figure 8B The first default TCI state (TCI1) in the example shown obtains its QCL assumption for scheduled PDSCH communications.

[0116] However, if the indicated TCI state in the active BWP of the scheduled component carrier (e.g., CC2) is associated with a PCI that is different from the serving cell PCI of the scheduled component carrier, the mobile station may apply a default TCI state associated with the activated TCI state with the lowest ID applicable to PDSCH communication. More specifically, as indicated by reference numeral 845, in some aspects, for cross-carrier scheduling, the mobile station may apply a TCI state associated with the activated TCI state with the lowest ID. That is, the mobile station may apply a third default TCI state (e.g., the activated TCI state with the lowest ID, or TCI4 in this example) for reception of PDSCH communication, as indicated by the dashed arrow shown by reference numeral 850. In any case (e.g., for cross-carrier scheduled PDSCH communications, whether the mobile station applies the indicated TCI state (e.g., TCI1) or the activated TCI state with the lowest ID (e.g., TCI4)), when PDSCH communications associated with a default TCI state (e.g., TCI1 or TCI4) at least partially overlap with a CORESET associated with another TCI state (e.g., TCI2), the mobile station may prioritize reception of the CORESET (e.g., the mobile station may prioritize reception of PDCCH communications associated with the CORESET) to ensure that control information, etc., is securely received by the mobile station, as indicated by reference numeral 840 and by using Figure 8B, as shown by the solid arrow in (as opposed to the dashed arrow shown in conjunction with the default TCI state indicated by reference numerals 820 and 850).

[0117] In some aspects, combined Figure 8B The operations shown and described can be summarized as follows: If a PDCCH carrying a scheduling DCI is received on one component carrier and a PDSCH scheduled by the DCI is on another component carrier: (1) If the indicated TCI in the active BWP of the scheduled component carrier is associated with a PCI that is different from the serving cell PCI of the scheduled component carrier, and when the UE is configured with enableDefaultBeamForCCS, if the offset between the reception of the DL DCI and the reception of the corresponding PDSCH is less than the threshold timeDurationForQCL, or if the DL DCI does not have a TCI field present, the UE derives its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID of the PDSCH in the active BWP applicable to the scheduled CC. In this case, if the qcl-type of the PDSCH DMRS-RS is set to "Type D" which is different from the qcl-type of the PDCCH DMRS-RS (where they overlap in at least one symbol), the UE is expected to prioritize reception of the PDCCH associated with the CORESET. This also applies to the intra-band carrier aggregation case (when the PDSCH and CORESET are in different component carriers). (2) If the indicated TCI in the active BWP of the scheduled component carrier is associated with the serving cell PCI of the scheduled component carrier, the UE derives its QCL assumption for the scheduled PDSCH from the indicated TCI in the active BWP of the scheduled component carrier. In this case, if the qcl-type of the PDSCH DMRS-RS is set to "Type D" which is different from the qcl-type of the PDCCH DMRS-RS (where they overlap in at least one symbol), the UE is expected to prioritize reception of the PDCCH associated with the CORESET. This also applies to the intra-band carrier aggregation case (when the PDSCH and CORESET are in different component carriers).

[0118] As indicated above, FIG. 8A to FIG. 8B are provided as examples. Other examples can be found in the FIG. 8A to FIG. 8B Different than described.

[0119] Fig. 9 is a diagram illustrating an example 900 associated with prioritized TCI states in single frequency network operation according to the present disclosure.

[0120] With Figures 7 to 8B In a similar way, Fig. 9Various signals, communications, or messages that a mobile station (e.g., UE 120) or other wireless communication device may receive from another wireless communication device (e.g., network node 110) are illustrated. More specifically, as indicated by reference numeral 905, in some aspects, a mobile station may receive a scheduling DCI that may indicate resources associated with downlink data transmission. For example, in some aspects, the scheduling DCI may indicate resources associated with SFN PDSCH communications as indicated by reference numeral 910. SFN PDSCH communications may be downlink communications associated with a transmission scheme in which multiple transmitters (e.g., multiple network nodes 110) transmit the same signal simultaneously on the same frequency channel. In some aspects, the scheduling DCI may be received in the same component carrier as the PDSCH communication (the PDSCH communication, for example, a self-scheduled SFN PDSCH communication), and in some other aspects, the scheduling DCI may be received in a component carrier different from the component carrier used to receive the PDSCH communication (the PDSCH communication, for example, a cross-carrier scheduled SFN PDSCH communication). Furthermore, in this aspect, the scheduling DCI may indicate a default TCI state associated with SFN PDSCH communications. Thus, without applying a prioritization rule (as described in more detail below in conjunction with reference numeral 925), the mobile station may apply the default TCI state to reception of SFN PDSCH communications, as indicated by the dashed arrow shown by reference numeral 915. For example, in some aspects, the TCI indication may indicate that the default TCI state is the TCI state indexed as TCI1. Thus, the mobile station may generally receive SFN PDSCH communications using a beam associated with TCI1.

[0121] In combination with the above Figures 7 to 8B In a similar manner as described above, in some aspects, resources associated with SFN PDSCH communications may at least partially overlap with a CORESET, such as the CORESET shown by reference numeral 920. Further, in some aspects, the CORESET may not be associated with a default TCI state (e.g., TCI1 in this example). More specifically, in aspects where the mobile station receives a TCI indication via a scheduling DCI, the CORESET may not have a TCI state that does not follow the indicated TCI state. For example, Figure 7 As shown, the CORESET may be associated with a TCI state indexed as TCI2. In this regard, if the mobile station applies a default TCI state (e.g., TCI1) during time resources associated with overlapping SFN PDSCH communications and the CORESET, there is a risk that the mobile station may not be able to securely receive control information associated with the CORESET (e.g., PDCCH communications sent in the CORESET).

[0122] Thus, in some aspects, when SFNPDSCH communications associated with an indicated or default TCI state (e.g., TCI1) at least partially overlap with a CORESET associated with another TCI state (e.g., TCI2), the mobile station may prioritize reception of the CORESET (e.g., the mobile station may prioritize reception of PDCCH communications associated with the CORESET) to ensure that control information, etc., is safely received by the mobile station. In other words, the mobile station may receive PDCCH communications (and in some aspects SFN PDSCH communications, in conjunction with the above) using beams associated with the TCI state associated with the CORESET. Figures 7 to 8B More specifically, as indicated by reference numeral 925 and by using Fig. 9 As shown by the solid arrow in (as opposed to the dashed arrow shown in conjunction with the default TCI state indicated by reference numeral 915), the CORESET TCI state (e.g., TCI2) may be used by the mobile station to receive the CORESET (e.g., PDCCH communications associated with the CORESET) and / or SFNPDSCH communications. In this regard, the mobile station may increase the likelihood that control information carried by the PDCCH communications associated with the CORESET is securely received even though the CORESET is associated with a TCI state different from the indicated and / or default TCI state.

[0123] In combination with the above Figures 7 to 8B In a similar manner as described, in some aspects, prioritizing the reception of PDCCH communications associated with the CORESET (e.g., using a beam associated with the CORESET during a time period where the CORESET at least partially overlaps with PDSCH communications) may be based at least in part on whether an offset between the scheduling DCI and the SFN PDSCH communications is below a threshold duration (e.g., timeDurationForQCL). Additionally or alternatively, prioritizing the reception of PDCCH communications associated with the CORESET may be based at least in part on a TCI state associated with the scheduling DCI (which is Fig. 9 The depicted aspect is that a default TCI state, or TCI1), is associated with a QCL type D (eg, a QCL type associated with spatial receiver parameters for the purpose of supporting beamforming).

[0124] In some aspects, combined Fig. 9The operations shown and described may be summarized as follows: If the UE is not configured with sfnSchemePdsch, and the UE is configured with sfnSchemePdcch set to "sfnSchemeA", and there is no TCI code point with two TCI states in the activation command, and the CORESET with the lowest ID in the most recent slot is indicated with two TCI states, then the UE may assume that the DMRS ports of the PDSCH of the serving cell are quasi-co-located with the reference signal with respect to the QCL parameters associated with the first of the two TCI states indicated for the CORESET. In this case, if the qcl-type of the PDSCH DMRS-RS is set to "Type D" which is different from the qcl-type of the PDCCH DMRS-RS (where they overlap in at least one symbol), then the UE is expected to prioritize the reception of the PDCCH associated with the CORESET. This also applies to intra-band carrier aggregation cases (when the PDSCH and the CORESET are in different component carriers).

[0125] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 Different than described.

[0126] Fig.10 1 is a diagram illustrating an example 1000 associated with a prioritized TCI state in a unified TCI or single frequency network operation according to the present disclosure. Fig.10 As shown, a mobile station 1005 (e.g., UE 120) can communicate with a network node 1010 (e.g., network node 110). In some aspects, the network node 1010 and the mobile station 1005 can be part of a wireless network (e.g., wireless network 100). The mobile station 1005 and the network node 1010 can be in communication with each other. Fig.10 The operations shown have previously established a wireless connection. For example, the mobile station 1005 and the network node 1010 may have established a wireless connection via one or more BPLs, as described above in conjunction with Figure 6 as described.

[0127] As indicated by reference numeral 1015, the network node 1010 may send, and the mobile station 1005 may receive, a unified TCI indication (e.g., an indication associated with a unified TCI framework). In some aspects, the mobile station 1005 may receive the unified TCI indication via one or more MAC-CEs and / or DCIs, etc. In some aspects, the unified TCI indication may include an indication of one or more configuration parameters for selection by the mobile station 1005 (e.g., already known to the mobile station 1005 and / or previously indicated by the network node 1010 or other network device), explicit information for use by the mobile station 1005 to configure the mobile station 1005, etc.

[0128] In some aspects, the unified TCI indication may indicate a first TCI state associated with a PDSCH communication (e.g., the PDSCH communication described in conjunction with 715, the PDSCH communication described in conjunction with reference numeral 815, the SFN PDSCH communication described in conjunction with reference numeral 910, or a similar PDSCH communication). The mobile station 1005 may configure itself (e.g., configure a default UE receive beam) based at least in part on the unified TCI indication. In some aspects, the mobile station 1005 may be configured to perform one or more operations described herein based at least in part on the unified TCI indication. In some aspects, the mobile station 1005 may enable one or more default UE receive beams based at least in part on the unified TCI indication. For example, the mobile station 1005 may enable a default UE receive beam associated with a TCI state indicated by the unified TCI indication.

[0129] As indicated by reference numeral 1020, the network node 1010 may send and the mobile station 1005 may receive a scheduled DCI communication associated with the PDSCH communication (e.g., the scheduled DCI described in conjunction with 710, the scheduled DCI described in conjunction with reference numeral 810, the scheduled DCI described in conjunction with reference numeral 905, or similar scheduled DCI). In some aspects, the scheduled DCI communication may be associated with the PDSCH communication described above. Fig. 9 The SFN is associated with PDSCH communication.

[0130] As above combined Figures 7 to 9As described, in some aspects, time resources associated with PDSCH communications associated with a first TCI state (e.g., a TCI state indicated by a unified TCI indication and / or a TCI state indicated by a scheduling DCI) may overlap at least partially (e.g., overlap at least one symbol) with time resources associated with a CORESET that is associated with a second TCI state that is different from the first TCI state. In such aspects, the mobile station 1005 may prioritize the reception of PDCCH communications associated with the CORESET based at least in part on the second TCI state being different from the first TCI state. More specifically, as indicated by reference numeral 1025, in order to prioritize the reception of PDCCH communications associated with the CORESET, when receiving PDCCH communications associated with the CORESET (as indicated by reference numeral 1030), the mobile station may use the TCI state associated with the CORESET. In some aspects, the mobile station 1005 is also capable of receiving PDSCH communications using the TCI state associated with the CORESET, as indicated by reference numeral 1035. In such aspects, because the mobile station 1005 prioritizes PDCCH communications (e.g., because the mobile station uses a receive beam associated with a TCI state associated with the CORESET), the PDCCH communications can be more easily received (e.g., received with less interference, communication errors, etc.) than PDSCH communications, as illustrated by the use of solid arrows for PDCCH communications described in conjunction with reference numeral 1030 and the use of dashed arrows for PDSCH communications described in conjunction with reference numeral 1035.

[0131] In some aspects, the PDSCH communication and the CORESET may be associated with the same component carrier, while in some other aspects, the PDSCH communication may be associated with a first component carrier and the CORESET may be associated with a second component carrier different from the first component carrier. Fig. 8A and Figure 8B As described above, in some aspects, a mobile station may be associated with multiple default TCI states, and a TCI state associated with a CORESET may take precedence over one or more of the multiple default TCI states. For example, in some aspects, a mobile station may be associated with a first default TCI state (such as a unified TCI state) and a second default TCI state (such as a TCI state associated with a lowest CORESET identifier), as described above in conjunction with Fig. 8AFurthermore, in some aspects, the PCI associated with the first default TCI state (e.g., the unified TCI state) may be different from the PCI associated with the serving cell associated with the PDSCH communication, and the second default state associated with the lowest CORESET identifier may be different from the TCI state associated with the CORESET, as described above in conjunction with Fig. 8A as described. In such aspects, prioritizing reception of PDCCH communications associated with the CORESET may also be based at least in part on the second default TCI state being different from the CORESET TCI state. Additionally or alternatively, in some aspects, scheduled DCI communications may be associated with a first component carrier, and PDSCH communications may be associated with a second component carrier that is different from the first component carrier (e.g., the PDSCH communications may be cross-carrier scheduled PDSCH communications). In such aspects, the second default TCI state may correspond to a TCI state associated with the lowest activated TCI identifier associated with the active bandwidth portion. Furthermore, the second default TCI state (e.g., a TCI state associated with the lowest activated TCI identifier associated with the active bandwidth portion) may be different from the TCI state associated with the CORESET, as described above in conjunction with Figure 8B In such aspects, prioritizing reception of PDCCH communications associated with the CORESET may also be based at least in part on the second default TCI state being different from the CORESET TCI state.

[0132] In some aspects, prioritizing the reception of PDCCH communications associated with the CORESET may be based at least in part on an offset between scheduled DCI and PDSCH communications being below a threshold and / or based at least in part on a QCL type of a default TCI state. More specifically, as shown by reference numerals 1040 and 1045, in some aspects, prioritizing the reception of PDCCH communications associated with the CORESET may also be based at least in part on an offset between scheduled DCI communications and time resources associated with the PDSCH being less than a threshold duration (e.g., timeDurationForQCL). Additionally or alternatively, in some aspects, prioritizing the reception of PDCCH communications associated with the CORESET may also be based at least in part on associating a first TCI state (e.g., a unified TCI state and / or a default TCI state) with a type D quasi-co-location type (e.g., QCL type D).

[0133] Based at least in part on the mobile station 1005 prioritizing reception of PDCCH communications associated with the CORESET when the CORESET TCI state is different from the PDSCH communication TCI state of the overlapping PDSCH communications, the mobile station 1005 and / or the network node 1010 can save computational, power, network, and / or communication resources that might otherwise be consumed when receiving PDCCH communications and / or PDSCH communications using the default and / or unified TCI state. For example, based at least in part on the mobile station 1005 prioritizing reception of PDCCH communications associated with the CORESET when the CORESET TCI state is different from the PDSCH communication TCI state of the overlapping PDSCH communications, the mobile station 1005 can receive control information with a reduced error rate, which can save computational, power, network, and / or communication resources that might otherwise be consumed to detect and / or correct communication errors.

[0134] As indicated above, Fig.10 are provided as examples. Other examples can be found in the Fig.10 Different than described.

[0135] Fig.11 is a diagram illustrating an example process 1100 performed, for example, by a mobile station in accordance with the present disclosure. The example process 1100 is an example in which a mobile station (eg, mobile station 1005) performs operations associated with prioritized TCI states in unified TCI operations.

[0136] like Fig.11 As shown, in some aspects, process 1100 may include receiving a unified TCI indication indicating a first TCI state associated with a PDSCH communication, wherein time resources associated with the PDSCH communication overlap at least partially with time resources associated with a CORESET that is associated with a second TCI state different from the first TCI state (block 1110). Fig.13 The communication manager 1308 and / or receiving component 1302 depicted in the figure may receive a unified TCI indication indicating a first TCI state associated with a PDSCH communication, wherein time resources associated with the PDSCH communication at least partially overlap with time resources associated with a CORESET, which is associated with a second TCI state different from the first TCI state, as described above.

[0137] like Fig.11 As further shown, in some aspects, process 1100 may include prioritizing reception of PDCCH communications associated with the CORESET based at least in part on the second TCI state being different from the first TCI state (block 1120). Fig.13The communication manager 1308, unified TCI component 1310, and / or prioritization component 1312 depicted in FIG. 1 may prioritize reception of PDCCH communications associated with a CORESET based at least in part on the second TCI state being different from the first TCI state, as described above.

[0138] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0139] In a first aspect, a unified TCI indication is received in at least one of a downlink control information communication or a MAC-CE communication.

[0140] In a second aspect, alone or in combination with the first aspect, process 1100 includes receiving a scheduled DCI communication associated with a PDSCH communication, wherein prioritizing reception of a PDCCH communication associated with a CORESET is further based at least in part on an offset between the scheduled DCI communication and a time resource associated with the PDSCH being less than a threshold duration.

[0141] In a third aspect, alone or in combination with one or more of the first and second aspects, prioritizing reception of PDCCH communications associated with a CORESET is further based at least in part on associating the first TCI state with a Type D quasi co-location type.

[0142] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the PDSCH communication and the CORESET are associated with the same component carrier.

[0143] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the PDSCH communication is associated with a first component carrier, and wherein the CORESET is associated with a second component carrier different from the first component carrier.

[0144] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, a PCI associated with a first TCI state is different from a PCI associated with a serving cell associated with PDSCH communications, a third TCI state associated with a lowest CORESET identifier is different from a second TCI state, and prioritizing reception of PDCCH communications associated with a CORESET is also at least partially based on the third TCI state being different from the second TCI state.

[0145] In a seventh aspect, alone or in combination with one or more of aspects 1 to 6, process 1100 includes receiving a scheduled DCI communication associated with a PDSCH communication, wherein the scheduled DCI communication is associated with a first component carrier and the PDSCH communication is associated with a second component carrier different from the first component carrier, wherein a third TCI state associated with a lowest activated TCI identifier associated with an active bandwidth portion is different from the second TCI state, and wherein prioritizing reception of PDCCH communications associated with a CORESET is also based at least in part on the third TCI state being different from the second TCI state.

[0146] although Fig.11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Fig.11 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0147] Fig.12 is a diagram illustrating an example process 1200 performed, for example, by a mobile station in accordance with the present disclosure. The example process 1200 is an example in which a mobile station (eg, mobile station 1005) performs operations associated with a prioritized TCI state in a single frequency network operation.

[0148] like Fig.12 As shown, in some aspects, process 1200 may include receiving a scheduling DCI communication associated with a SFN PDSCH communication, wherein the scheduling DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a CORESET associated with a second TCI state different from the first TCI state (block 1210). For example, a mobile station (e.g., using Fig.14 The communication manager 1408 and / or receiving component 1402 depicted in the figure may receive a scheduled DCI communication associated with an SFN PDSCH communication, wherein the scheduled DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a CORESET that is associated with a second TCI state different from the first TCI state, as described above.

[0149] like Fig.12As further shown, in some aspects, process 1200 may include prioritizing reception of PDCCH communications associated with a CORESET based at least in part on the second TCI state being different from the first TCI state (block 1220). Fig.14 The communication manager 1408, SFN component 1410, and / or prioritization component 1412 depicted in FIG. 1404 may prioritize reception of PDCCH communications associated with a CORESET based at least in part on the second TCI state being different from the first TCI state, as described above.

[0150] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0151] In the first aspect, prioritizing reception of PDCCH communications associated with the CORESET is further based at least in part on an offset between a scheduled DCI communication and a time resource associated with the PDSCH being less than a threshold duration.

[0152] In a second aspect, alone or in combination with the first aspect, prioritizing reception of PDCCH communications associated with a CORESET is further based at least in part on associating the first TCI state with a Type D quasi co-location type.

[0153] In a third aspect, alone or in combination with one or more of the first and second aspects, the PDSCH communication and the CORESET are associated with the same component carrier.

[0154] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the PDSCH communication is associated with a first component carrier, and wherein the CORESET is associated with a second component carrier different from the first component carrier.

[0155] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0156] Fig.131 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a mobile station (e.g., mobile station 1005), or a mobile station may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a sending component 1304, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as UE 120, network node 110, or another wireless communication device) using receiving component 1302 and sending component 1304. As further shown, apparatus 1300 may include a communication manager 1308 (e.g., communication manager 140). Communication manager 1308 may include one or more of a unified TCI component 1310 or a prioritization component 1312, etc.

[0157] In some aspects, the apparatus 1300 may be configured to perform the Figures 7 to 10 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.11 The process 1100. In some aspects, Fig.13 The apparatus 1300 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 One or more components of the described UE 120. Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0158] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2 The UE 120 is described as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0159] Transmit component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and may provide the generated communications to transmit component 1304 for transmission to device 1306. In some aspects, transmit component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1306. In some aspects, transmit component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof of the depicted UE 120. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0160] Receiving component 1302 can receive a unified TCI indication indicating a first TCI state associated with a PDSCH communication, wherein time resources associated with the PDSCH communication at least partially overlap with time resources associated with a CORESET associated with a second TCI state different from the first TCI state. Unifying TCI component 1310 and / or prioritizing component 1312 can prioritize reception of the PDCCH communication associated with the CORESET based at least in part on the second TCI state being different from the first TCI state.

[0161] Receiving component 1302 can receive a scheduled DCI communication associated with a PDSCH communication, wherein prioritizing reception of a PDCCH communication associated with a CORESET is further based at least in part on an offset between the scheduled DCI communication and a time resource associated with the PDSCH being less than a threshold duration.

[0162] The receiving component 1302 may receive a DCI communication associated with a PDSCH communication, wherein the scheduled DCI communication is associated with a first component carrier and the PDSCH communication is associated with a second component carrier different from the first component carrier, wherein a third TCI state associated with a lowest activated TCI identifier associated with an active bandwidth portion is different from the second TCI state, and wherein prioritizing reception of the PDCCH communication associated with the CORESET is also based at least in part on the third TCI state being different from the second TCI state.

[0163] Fig.13 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The illustrated set of component(s) may be described as being executable by Fig.13 Another collection of components shown performs one or more functions.

[0164] Fig.14 1 is a diagram of an example apparatus 1400 for wireless communication according to the present disclosure. Apparatus 1400 may be a mobile station (e.g., mobile station 1005), or a mobile station may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402 and a transmitting component 1404, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 may communicate with another apparatus 1406 (such as UE 120, network node 110, or another wireless communication device) using receiving component 1402 and transmitting component 1404. As further shown, apparatus 1400 may include a communication manager 1408 (e.g., communication manager 140). Communication manager 1408 may include one or more of SFN component 1410 or prioritization component 1412, etc.

[0165] In some aspects, the apparatus 1400 may be configured to perform the Figures 7 to 10 Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Fig.12 The process 1200. In some aspects, Fig.14 The apparatus 1400 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 One or more components of the described UE 120. Additionally or alternatively, Fig.14 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0166] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1406. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 1400. In some aspects, the receiving component 1402 may include combining Figure 2 The UE 120 is described as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0167] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some aspects, one or more other components of the device 1400 may generate communications and may provide the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof of the depicted UE 120. In some aspects, the transmit component 1404 can be co-located with the receive component 1402 in a transceiver.

[0168] The receiving component 1402 can receive a scheduling DCI communication associated with a SFN PDSCH communication, wherein the scheduling DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a CORESET associated with a second TCI state different from the first TCI state. The SFN component 1410 and / or the prioritizing component 1412 can prioritize reception of the PDCCH communication associated with the CORESET based at least in part on the second TCI state being different from the first TCI state.

[0169] Fig.14 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.14 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.14Two or more components shown may be implemented in a single component, or Fig.14 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.14 The illustrated set of component(s) may be described as being executable by Fig.14 Another collection of components shown performs one or more functions.

[0170] The following provides an overview of some aspects of the disclosure:

[0171] Aspect 1: A method of wireless communication performed by a mobile station, comprising: receiving, by the mobile station, a unified TCI indication indicating a first TCI state associated with a PDSCH communication, wherein time resources associated with the PDSCH communication at least partially overlap with time resources associated with a CORESET, and the CORESET is associated with a second TCI state different from the first TCI state; and prioritizing, by the mobile station, reception of a PDCCH communication associated with the CORESET at least partially based on the second TCI state being different from the first TCI state.

[0172] Aspect 2: The method according to aspect 1, wherein the unified TCI indication is received in at least one of downlink control information communication or MAC-CE communication.

[0173] Aspect 3: The method according to any one of Aspects 1 to 2 also includes: receiving, by the mobile station, a scheduled DCI communication associated with the PDSCH communication, wherein the priority of receiving the PDCCH communication associated with the CORESET is also at least partially based on the offset between the scheduled DCI communication and the time resources associated with the PDSCH being less than a threshold duration.

[0174] Aspect 4: The method according to any one of aspects 1 to 3, wherein prioritizing reception of the PDCCH communication associated with the CORESET is further based at least in part on associating the first TCI state with a Type D quasi co-location type.

[0175] Aspect 5: The method according to any one of aspects 1 to 4, wherein the PDSCH communication and the CORESET are associated with the same component carrier.

[0176] Aspect 6: The method according to any one of aspects 1 to 4, wherein the PDSCH communication is associated with a first component carrier, and wherein the CORESET is associated with a second component carrier different from the first component carrier.

[0177] Aspect 7: A method according to any one of Aspects 1 to 6, wherein the PCI associated with the first TCI state is different from the PCI associated with the serving cell associated with the PDSCH communication, wherein the third TCI state associated with the lowest CORESET identifier is different from the second TCI state, and wherein the reception of the PDCCH communication associated with the CORESET is prioritized also at least in part based on the third TCI state being different from the second TCI state.

[0178] Aspect 8: The method according to any one of Aspects 1 to 7 further includes receiving, by the mobile station, a scheduled DCI communication associated with the PDSCH communication, wherein the scheduled DCI communication is associated with a first component carrier and the PDSCH communication is associated with a second component carrier different from the first component carrier, wherein a third TCI state associated with the lowest activated TCI identifier associated with the active bandwidth portion is different from the second TCI state, and wherein prioritizing the reception of the PDCCH communication associated with the CORESET is also at least partially based on the third TCI state being different from the second TCI state.

[0179] Aspect 9: A method of wireless communication performed by a mobile station, comprising: receiving, by the mobile station, a scheduled DCI communication associated with an SFNPDSCH communication, wherein the scheduled DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a CORESET, and the CORESET is associated with a second TCI state different from the first TCI state; and prioritizing, by the mobile station, reception of a PDCCH communication associated with the CORESET at least partially based on the second TCI state being different from the first TCI state.

[0180] Aspect 10: The method of aspect 9, wherein prioritizing reception of the PDCCH communication associated with the CORESET is further based at least in part on an offset between the scheduled DCI communication and the time resources associated with the PDSCH being less than a threshold duration.

[0181] Aspect 11: The method according to any one of aspects 9 to 10, wherein prioritizing reception of the PDCCH communication associated with the CORESET is further based at least in part on the first TCI state being associated with a Type D quasi co-location type.

[0182] Aspect 12: The method according to any one of aspects 9 to 11, wherein the PDSCH communication and the CORESET are associated with the same component carrier.

[0183] Aspect 13: The method according to any one of aspects 9 to 11, wherein the PDSCH communication is associated with a first component carrier, and wherein the CORESET is associated with a second component carrier different from the first component carrier.

[0184] Aspect 14: An apparatus for performing wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1 to 8.

[0185] Aspect 15: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors being coupled to the memory and configured to execute the method according to one or more of aspects 1 to 8.

[0186] Aspect 16: An apparatus for wireless communication, the apparatus comprising at least one component, the at least one component being configured to perform the method according to one or more of aspects 1 to 8.

[0187] Aspect 17: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 8.

[0188] Aspect 18: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of aspects 1 to 8.

[0189] Aspect 19: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 9 to 13.

[0190] Aspect 20: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory and configured to execute the method according to one or more of aspects 9 to 13.

[0191] Aspect 21: An apparatus for wireless communication, the apparatus comprising at least one component, the at least one component being configured to perform the method according to one or more of aspects 9 to 13.

[0192] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 9 to 13.

[0193] Aspect 23: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of aspects 9 to 13.

[0194] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0195] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0196] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0197] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0198] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A method of wireless communication performed by a mobile station, the method comprising: receiving, by the mobile station, a unified transmission configuration indicator (TCI) indication indicating a first TCI state associated with a physical downlink shared channel (PDSCH) communication, wherein time resources associated with the PDSCH communication at least partially overlap with time resources associated with a control resource set (CORESET), the control resource set (CORESET) being associated with a second TCI state different from the first TCI state; as well as Reception of a physical downlink control channel (PDCCH) communication associated with the CORESET is prioritized by the mobile station based at least in part on the second TCI state being different than the first TCI state.

2. The method of claim 1, wherein the unified TCI indication is received in at least one of a downlink control information communication or a medium access control (MAC)-control element (MAC-CE) communication.

3. The method of claim 1 , further comprising receiving, by the mobile station, a scheduled downlink control information (DCI) communication associated with the PDSCH communication, wherein prioritizing reception of the PDCCH communication associated with the CORESET is further based at least in part on an offset between the scheduled DCI communication and the time resources associated with the PDSCH being less than a threshold duration.

4. The method of claim 1 , wherein prioritizing reception of the PDCCH communications associated with the CORESET is further based at least in part on associating the first TCI state with a Type D quasi co-location type.

5. The method of claim 1, wherein the PDSCH communication and the CORESET are associated with the same component carrier.

6. The method of claim 1, wherein the PDSCH communication is associated with a first component carrier, and wherein the CORESET is associated with a second component carrier different from the first component carrier.

7. The method of claim 1 , wherein a physical cell identifier (PCI) associated with the first TCI state is different from a PCI associated with a serving cell associated with the PDSCH communication, wherein a third TCI state associated with a lowest CORESET identifier is different from the second TCI state, and wherein prioritizing reception of the PDCCH communication associated with the CORESET is further based at least in part on the third TCI state being different from the second TCI state.

8. The method of claim 1 , further comprising receiving, by the mobile station, a scheduled downlink control information (DCI) communication associated with the PDSCH communication, wherein the scheduled DCI communication is associated with a first component carrier and the PDSCH communication is associated with a second component carrier different from the first component carrier, wherein a third TCI state associated with a lowest activated TCI identifier associated with an active bandwidth portion is different from the second TCI state, and wherein prioritizing reception of the PDCCH communication associated with the CORESET is also based at least in part on the third TCI state being different from the second TCI state.

9. A method of wireless communication performed by a mobile station, the method comprising: receiving, by the mobile station, a scheduled downlink control information (DCI) communication associated with a single frequency network (SFN) physical downlink shared channel (PDSCH) communication, wherein the scheduled DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a control resource set (CORESET), the control resource set (CORESET) being associated with a second TCI state different from the first TCI state; as well as Reception of a physical downlink control channel (PDCCH) communication associated with the CORESET is prioritized by the mobile station based at least in part on the second TCI state being different than the first TCI state.

10. The method of claim 9, wherein prioritizing reception of the PDCCH communication associated with the CORESET is further based at least in part on an offset between the scheduled DCI communication and the time resources associated with the PDSCH being less than a threshold duration.

11. The method of claim 9, wherein prioritizing reception of the PDCCH communications associated with the CORESET is further based at least in part on the first TCI state being associated with a Type D quasi co-location type.

12. The method of claim 9, wherein the PDSCH communication and the CORESET are associated with the same component carrier.

13. The method of claim 9, wherein the PDSCH communication is associated with a first component carrier, and wherein the CORESET is associated with a second component carrier different from the first component carrier.

14. A mobile station for wireless communication, the mobile station comprising: Memory; and and one or more processors coupled to the memory and, based at least in part on the information stored in the memory, configured to: receiving a unified transmission configuration indicator (TCI) indication indicating a first TCI state associated with a physical downlink shared channel (PDSCH) communication, wherein time resources associated with the PDSCH communication at least partially overlap with time resources associated with a control resource set (CORESET), the control resource set (CORESET) being associated with a second TCI state different from the first TCI state; as well as Reception of a physical downlink control channel (PDCCH) communication associated with the CORESET is prioritized based at least in part on the second TCI state being different than the first TCI state.

15. The mobile station of claim 14, wherein the unified TCI indication is received in at least one of a downlink control information communication or a medium access control (MAC)-control element (MAC-CE) communication.

16. The mobile station of claim 14, wherein the one or more processors are further configured to: receive a scheduled downlink control information (DCI) communication associated with the PDSCH communication, wherein prioritizing reception of the PDCCH communication associated with the CORESET is further based at least in part on an offset between the scheduled DCI communication and the time resources associated with the PDSCH being less than a threshold duration.

17. The mobile station of claim 14, wherein prioritizing reception of the PDCCH communications associated with the CORESET is further based at least in part on the first TCI state being associated with a Type D quasi co-location type.

18. The mobile station of claim 14, wherein the PDSCH communication and the CORESET are associated with the same component carrier.

19. The mobile station of claim 14, wherein the PDSCH communication is associated with a first component carrier, and wherein the CORESET is associated with a second component carrier different from the first component carrier.

20. The mobile station of claim 14, wherein a physical cell identifier (PCI) associated with the first TCI state is different from a PCI associated with a serving cell associated with the PDSCH communication, wherein a third TCI state associated with a lowest CORESET identifier is different from the second TCI state, and wherein prioritizing reception of the PDCCH communication associated with the CORESET is further based at least in part on the third TCI state being different from the second TCI state.

21. The mobile station of claim 14, wherein the one or more processors are further configured to receive a scheduled downlink control information (DCI) communication associated with the PDSCH communication, wherein the scheduled DCI communication is associated with a first component carrier and the PDSCH communication is associated with a second component carrier different from the first component carrier, wherein a third TCI state associated with a lowest activated TCI identifier associated with an active bandwidth portion is different from the second TCI state, and wherein prioritizing reception of the PDCCH communication associated with the CORESET is also based at least in part on the third TCI state being different from the second TCI state.

22. A mobile station for wireless communication, the mobile station comprising: Memory; and and one or more processors coupled to the memory and, based at least in part on the information stored in the memory, configured to: receiving a scheduled downlink control information (DCI) communication associated with a single frequency network (SFN) physical downlink shared channel (PDSCH) communication, wherein the scheduled DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a control resource set (CORESET) associated with a second TCI state different from the first TCI state; as well as Reception of a physical downlink control channel (PDCCH) communication associated with the CORESET is prioritized based at least in part on the second TCI state being different than the first TCI state.

23. The mobile station of claim 22, wherein prioritizing reception of the PDCCH communication associated with the CORESET is further based at least in part on an offset between the scheduled DCI communication and the time resources associated with the PDSCH being less than a threshold duration.

24. The mobile station of claim 22, wherein prioritizing reception of the PDCCH communications associated with the CORESET is further based at least in part on the first TCI state being associated with a Type D quasi co-location type.

25. The mobile station of claim 22, wherein the PDSCH communication and the CORESET are associated with the same component carrier.

26. The mobile station of claim 22, wherein the PDSCH communication is associated with a first component carrier, and wherein the CORESET is associated with a second component carrier different than the first component carrier.

27. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a mobile station, cause the mobile station to: receiving a unified transmission configuration indicator (TCI) indication indicating a first TCI state associated with a physical downlink shared channel (PDSCH) communication, wherein time resources associated with the PDSCH communication at least partially overlap with time resources associated with a control resource set (CORESET), the control resource set (CORESET) being associated with a second TCI state different from the first TCI state; as well as Reception of a physical downlink control channel (PDCCH) communication associated with the CORESET is prioritized based at least in part on the second TCI state being different than the first TCI state.

28. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a mobile station, cause the mobile station to: receiving a scheduled downlink control information (DCI) communication associated with a single frequency network (SFN) physical downlink shared channel (PDSCH) communication, wherein the scheduled DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a control resource set (CORESET) associated with a second TCI state different from the first TCI state; as well as Reception of a physical downlink control channel (PDCCH) communication associated with the CORESET is prioritized based at least in part on the second TCI state being different than the first TCI state.

29. An apparatus for wireless communication, the apparatus comprising: means for receiving a unified transmission configuration indicator (TCI) indication indicating a first TCI state associated with a physical downlink shared channel (PDSCH) communication, wherein time resources associated with the PDSCH communication at least partially overlap with time resources associated with a control resource set (CORESET), the control resource set (CORESET) being associated with a second TCI state different from the first TCI state; and Means for prioritizing reception of a physical downlink control channel (PDCCH) communication associated with the CORESET based at least in part on the second TCI state being different than the first TCI state.

30. An apparatus for wireless communication, the apparatus comprising: means for receiving a scheduled downlink control information (DCI) communication associated with a single frequency network (SFN) physical downlink shared channel (PDSCH) communication, wherein the scheduled DCI communication indicates a first TCI state associated with the SFN PDSCH communication, and wherein time resources associated with the SFN PDSCH communication at least partially overlap with time resources associated with a control resource set (CORESET) associated with a second TCI state different from the first TCI state; and Means for prioritizing reception of a physical downlink control channel (PDCCH) communication associated with the CORESET based at least in part on the second TCI state being different than the first TCI state.

Images