Configuring transmit configuration indicator types for transmit-receive points in multiple transmit-receive point operations

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) can receive a multiple transmit-receive point (mTRP) configuration indicating a first transmit configuration indicator (TCI) state type corresponding to a first transmit-receive point (TRP) and a second TCI state type corresponding to a second TRP. The UE can communicate based at least in part on the mTRP configuration. 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 configuring a transmission configuration indicator type for a transmission reception point in a multiple transmission reception point operation. 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 one 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.

[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 user equipment (UE) for wireless communication. The user equipment may include: a memory; one or more processors coupled to the memory; and instructions, which are stored in the memory and can be executed by the one or more processors. These instructions can be executed by one or more processors to cause the user equipment to receive a multiple transmit-receive point (mTRP) configuration, which indicates a first transmit configuration indicator (TCI) state type corresponding to a first transmit-receive point (TRP) and a second TCI state type corresponding to a second TRP. These instructions can be executed by one or more processors to cause the user equipment to communicate at least in part based on the mTRP configuration.

[0006] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. These instructions may be executed by one or more processors so that the network node sends an mTRP configuration, and the mTRP configuration indicates a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP. These instructions may be executed by one or more processors so that the network node communicates at least partially based on the mTRP configuration.

[0007] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP. The method may include communicating based at least in part on the mTRP configuration.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP. The method may include communicating based at least in part on the mTRP configuration.

[0009] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for receiving an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP. The apparatus may include a component for communicating based at least in part on the mTRP configuration.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP. The apparatus may include a component for communicating based at least in part on the mTRP configuration.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication performed by a UE. The one or more instructions, when executed by one or more processors of the UE, may cause the UE to receive an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP. The one or more instructions, when executed by one or more processors of the UE, may cause the UE to communicate based at least in part on the mTRP configuration.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication performed by a network node. The one or more instructions, when executed by one or more processors of the network node, may cause the network node to send an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP. The one or more instructions, when executed by one or more processors of the network node, may cause the network node to communicate based at least in part on the mTRP configuration.

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

[0014] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively 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 to 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 only illustrate 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 of a decomposed base station architecture according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of a multiple transmit reception point (mTRP) operation based on a single downlink control information (DCI) according to the present disclosure.

[0021] Figures 5 to 9 is a diagram illustrating an example associated with configuring a transmission configuration indicator (TCI) type for a transmission reception point (TRP) in an mTRP operation according to the present disclosure.

[0022] Fig.10 and Fig.11 is a diagram illustrating an example process associated with configuring a TCI type for a TRP in an mTRP operation according to the present disclosure.

[0023] Fig.12 and Fig.13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0024] 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 interpreted 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 protection 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 implemented 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 devices or methods implemented using other structures, functionality, or structures 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 claims.

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

[0026] The present disclosure can be easily used as a basis for modifying or designing other structures for performing the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages are better understood from the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of the limitations of the claims.

[0027] Although various aspects are described in the present disclosure by illustrating some examples, 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 (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein can be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of different sizes, shapes and compositions.

[0028] 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.

[0029] 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 5G and beyond (e.g., 6G) RATs.

[0030] Figure 11 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 a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The network node 110 is an entity that communicates with the UE 120. The network node 110 (sometimes referred to as a NN) may include, for example, an NR network node, an LTE network node, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each network node 110 may provide communication coverage for a particular geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a network node 110 and / or a network node subsystem serving the coverage area, depending on the context in which the term is used.

[0031] 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. A network node 110 for a femto cell may be referred to as a femto network node or a home network node. In Figure 1 In the example shown, BS 110a may be a macro network node for macro cell 102a, BS 110b may be a pico network node for pico cell 102b, and BS 110c may be a femto network node for femto cell 102c. A network node may support one or more (eg, three) cells.

[0032] In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., the mobile network node). In some examples, the network nodes 110 may interconnect with each other and / or to one or more other network nodes 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0033] The wireless network 100 may include one or more relay stations. A relay station is an entity capable of receiving transmissions of data from an upstream station (e.g., a network node 110 or a UE 120) and transmitting transmissions of data to a downstream station (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 , BS 110d (eg, a relay network node) may communicate with BS 110a (eg, a macro network node) and UE 120d to facilitate communications between BS 110a and UE 120d. A network node 110 that relays communications may be referred to as a relay station, relay network node, relay, or the like.

[0034] 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).

[0035] 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. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul link or a wired backhaul link.

[0036] 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, and / or any other suitable device configured to communicate via a wireless medium.

[0037] 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, which 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, a processor component and a 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.

[0038] 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.

[0039] 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.

[0040] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to 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 portions of FR1 are 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).

[0041] 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, and therefore 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.

[0042] 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.

[0043] As described herein, a network node may also be referred to as a "node" or a "wireless node", and may be a base station (e.g., base station 110), a UE (e.g., UE 120), a relay device, a network controller, an apparatus, a device, a computing system, one or more components of any of these, and / or another processing entity configured to perform one or more aspects of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station. A network node may be one or more components of a converged base station and / or a decomposed base station. As an example, a first network node may be configured to communicate with a second network node or a third network node. The adjectives "first", "second", "third", etc. are used to contextually distinguish between two or more modified nouns in conjunction with a discussion, and are not meant to be absolute modifiers that apply only to a corresponding node in the entire document. For example, a network node may be referred to as a "first network node" in conjunction with one discussion, and may be referred to as a "second network node" in conjunction with another discussion, and vice versa. References to UEs, base stations, apparatuses, devices, computing systems, etc. may include disclosure of UEs, base stations, apparatuses, devices, computing systems, etc. as network nodes. For example, the disclosure that the UE is configured to receive information from the base station also discloses that the first network node is configured to receive information from the second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., the UE is configured to receive information from the base station also discloses that the first network node is configured to receive information from the second network node), the broader example of the narrower example can be interpreted in reverse, but in a broad, open-ended manner. In the above example that the UE is configured to receive information from the base station also discloses that the first network node is configured to receive information from the second network node, "first network node" may refer to a first UE configured to receive information from a second network, a first base station, a first device, a first equipment, a first computing system, a first one or more components, a first processing entity, etc.; and "second network node" may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second one or more components, a second processing entity, etc.

[0044] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a multiple transmit-receive point (mTRP) configuration indicating a first transmit configuration indicator (TCI) state type corresponding to a first transmit-receive point (TRP) and a second TCI state type corresponding to a second TRP; and communicate based at least in part on the mTRP configuration. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0045] In some aspects, the network node may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP; and communicate based at least in part on the mTRP configuration. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0046] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0047] Figure 2 1 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).

[0048] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a 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 (CQIs) 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 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., precoding) 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 upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0049] In some aspects, the term "base station" (e.g., base station 110), "network node" or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station", "network node" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (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", "network node" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station", "network node" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographical location or in different geographical 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", "network node" or "network entity" may refer to any one or more of these different devices. In some aspects, the terms "base station," "network node," or "network entity" may refer to one or more virtual base stations and / 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 terms "base station," "network node," or "network entity" 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.

[0050] 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.

[0051] 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.

[0052] 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.

[0053] Each of the antenna elements may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element that is cross-polarized with a second sub-element, which can be used to independently transmit a cross-polarized signal. The antenna elements may include patch antennas, dipole antennas, or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements may allow signals having a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam). For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half wavelength, or other fraction of a wavelength of the spacing between adjacent antenna elements to allow interaction or interference of signals transmitted by individual antenna elements within the desired range.

[0054] Antenna elements and / or sub-elements may be used to generate beams. A "beam" may specify a wireless signal that is transmitted in a direction, such as in the direction of a receiving device. A beam may include a directional signal, a direction associated with the signal, a set of directional resources associated with the signal (e.g., angle of arrival, horizontal direction, vertical direction), and / or a set of parameters indicating one or more aspects of a directional signal, a direction associated with the signal, and / or a set of directional resources associated with the signal.

[0055] As indicated above, antenna elements and / or sub-elements can be used to generate beams. For example, antenna elements can be individually selected or deselected for transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers. Beamforming includes generating beams using multiple signals on different antenna elements, wherein one or more or all of the multiple signals are shifted in phase relative to each other. The formed beams can carry physical or higher layer reference signals or information. When each of the multiple signals is radiated from the corresponding antenna element, the radiated signals interact, interfere (constructively and destructively) and amplify with each other to form the resulting beam. The shape (such as amplitude, width and / or the presence of side lobes) and direction (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shift or phase offset of the multiple signals relative to each other.

[0056] Beamforming may be used for communication between a UE and a network node, such as for millimeter wave communication, etc. In this case, the network node may provide the UE with configuration of TCI states, which respectively indicate beams that may be used by the UE, such as for receiving a physical downlink shared channel (PDSCH). The network node may indicate an activated TCI state to the UE, which the UE may use to select a beam for receiving the PDSCH.

[0057] The beam indication may be or include a TCI state information element, a beam ID, spatial relationship information, a TCI state ID, a closed loop index, a panel ID, a TRP ID, and / or a sounding reference signal (SRS) set ID, etc. The TCI state information element (referred to herein as TCI state) may indicate information associated with a beam, such as a downlink beam. For example, the TCI state information element may indicate a TCI state identifier (e.g., tci-StateID), a quasi co-location (QCL) type (e.g., qcl-Type1, qcl-Type2, qcl-TypeA, qcl-TypeB, qcl-TypeC, qcl-TypeD, etc.), a cell identifier (e.g., ServCellIndex), a bandwidth part identifier (bwp-Id), a reference signal identifier (such as a channel state information (CSI) reference signal (CSI-RS) (e.g., NZP-CSI-RS-ResourceId, SSB-Index, etc.)), etc. The spatial relationship information may similarly indicate information associated with an uplink beam.

[0058] The beam indication may be a joint or separate downlink (DL) / uplink (UL) beam indication in a unified TCI framework. In some cases, the network may use at least UE-specific (unicast) downlink control information (DCI) to indicate a joint or separate DL / UL beam indication from an active TCI state, thereby supporting beam indication based on layer 1 (L1). In some cases, existing DCI formats 1_0, 1_1, 1_2, 0_1, 0_2, 0_0 and / or 2_x may be reused for beam indication. For example, a DCI transmission may include a beam indication with one of six types of beam indications regarding a unified TCI. Type 1 may include a joint DL / UL common TCI state (joint TCI) for indicating a common beam for at least one DL channel and / or reference signal plus at least one UL channel and / or reference signal. Type 2 may include a separate DL common TCI state for indicating a common beam for more than one DL channel and / or reference signal. Type 3 may include a separate UL common TCI state for indicating a common beam for more than one UL channel and / or reference signal. Separate DL and UL TCI state types may be referred to as "directional" TCI types because each TCI type corresponds to a specific communication direction (UL or DL). The source reference signal in the unified TCI may provide QCL information for at least one of PDSCH and physical downlink control channel (PDCCH) reception in the serving cell, and the source reference signal in the unified TCI (if applicable) may provide a reference for determining a common spatial transmit filter for at least one of SRS, physical uplink shared channel (PUSCH), and physical uplink control channel (PUCCH) transmissions in the serving cell.

[0059] Beam indication may be provided for carrier aggregation (CA) scenarios. In a unified TCI framework, the network may support common TCI state ID updates and activations to provide common QCL information and / or one or more common UL transmit spatial filters across a set of configured component carriers (CCs). This type of beam indication may be applicable to intra-band CA as well as joint DL / UL beam indication and directional DL / UL beam indication. A common TCI state ID may mean that a reference signal (RS) determined according to a TCI state indicated by a common TCI state ID is used to provide a QCL type D indication and determine a UL transmit spatial filter across a set of configured CCs.

[0060] 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 operations described herein (eg, with reference to Figures 5 to 13 ) or any aspects of any of the methods described herein.

[0061] 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 of the modem 232 shown as DEMOD), 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 and / or uplink communications. 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 5 to 13 ) or any aspects of any of the methods described herein.

[0062] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the may perform one or more techniques associated with configuring TCI types for TRPs in mTRP operations, as described in more detail elsewhere herein. In some aspects, the network node described herein is the network node 110, included in the network node 110, or includes Figure 2 One or more components of the network node 110 shown in FIG. For example, 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 may perform or direct e.g. Fig.10 The process of 1000 Fig.11 The operations of process 1100 and / or 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.10 The process of 1000 Fig.11 The process 1100 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.

[0063] In some aspects, a UE includes: a component for receiving an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP; and / or a component for communicating based at least in part on the mTRP configuration. The components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0064] In some aspects, the network node includes a component for sending an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP; and / or a component for communicating based at least in part on the mTRP configuration. In some aspects, the components for the network node to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0065] 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.

[0066] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0067] 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 BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station.

[0068] A clustered base station 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 may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as a CU, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and 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.

[0069] 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.

[0070] 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, which 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-RT RIC 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 RF access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0071] 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 configured to receive or transmit 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 transmit signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0072] In some aspects, 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 can be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. 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, CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0073] 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 MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, 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 also 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.

[0074] 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, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc., based at least in part on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower layer functional splitting). 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.

[0075] 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.

[0076] 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 in communication 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.

[0077] 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 tune 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).

[0078] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0079] Figure 4 4 is a diagram illustrating an example 400 of single-DCI based mTRP operation according to the present disclosure. As shown, UE 405 can communicate with a first TRP 410 and a second TRP 415. UE 405 can be configured to have single-DCI based mTRP operation. In some aspects, TRP 410 and / or TRP 415 can be, include, one or more network nodes (e.g., as described above in conjunction with Figure 1 and Figure 2 The one or more base stations 110 described above may be included in the one or more network nodes. For example, different TRPs 410 and 415 may be included in different network nodes. In some cases, multiple TRPs 410 and 415 may be included in a single network node. In some cases, TRP 410 and / or TRP 415 may be referred to as a cell, a panel, an antenna array, or an array. UE 405 may be, include, or be included in the above combined Figure 1 and Figure 2 In the UE 120 described.

[0080] Multiple TRPs 410 and TRPs 415 may transmit communications (e.g., the same communication or different communications) in the same transmit time interval (TTI) (e.g., slot, mini-slot, subframe, or symbol) or in different TTIs using different QCL relationships (e.g., different spatial parameters, different TCI states, different pre-coding parameters, or different beamforming parameters). TCI states may be used to indicate one or more QCL relationships. TRPs 410 may be configured to serve traffic to UE 405 individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs 410).

[0081] UE 405 may be configured to have mTRP operation based on a single DCI. As shown, when configured to have multi-TRP operation based on a single DCI, UE 405 may receive a DCI transmission 420 from TRP 410 in a first PDCCH transmission (shown as "PDCCH1"), wherein the DCI transmission 420 may schedule a first PUSCH transmission 425 for transmission to the first TRP 410. The DCI transmission 420 may also schedule a second PUSCH transmission 430 for transmission to a second TRP 415. In some cases, the DCI transmission 420 may schedule one or more PDSCH transmissions in addition to or in lieu of the PUSCH transmission. In association with monitoring the DCI transmitted from the first TRP 410, the UE 405 may monitor PDCCH candidates in PDCCH monitoring opportunities configured by the network in a certain number of different core resource sets (CORESETs).

[0082] In some cases, the first TRP 410 may be associated with a serving cell of the UE 405. For example, the first TRP 410 may be a base station providing a serving cell or a relay device providing access to the serving cell. In some cases, a certain number of additional TRPs may be associated with a certain number of additional serving cells. In some cases, the second TRP 415 may be associated with a non-serving cell. In order to communicate with the cell and receive DCI transmissions, the UE 405 may obtain a beam indication about beam selection based on the TCI state. In some cases, synchronization signal block (SSB) information may be used to perform channel measurements, obtain TCI states, or select beams for communication. The UE 405 may obtain SSB transmission positioning, SSB transmission periodicity, and SSB transmission power associated with the cell, and use this information to facilitate reception and decoding of DCI transmissions.

[0083] For a single DCI mTRP, the activated TCI code point may be mapped to a plurality of unified TCI states having different types. For example, TRP 410 may send an activation MAC CE 440 to UE 405. As shown, the activation MAC CE may indicate TCI code point mapping. For example, as shown, the TCI state may be mapped to a code point (shown as "C_0", "C_1", "C_2", and "C_3"), where C_x represents the last TCI state mapped to the code point. For each code point, the mapped TCI state may have the following combinations (note that the order listed in the MAC CE is ignored): {DL only, UL only, joint}, {DL only, joint}, {UL only, joint}, {joint, joint}, {DL only, DL only, UL only}, {DL only, UL only, UL only}, and {DL only, DL only, UL only, UL only}. The code point may be mapped to up to two DL applicable TCIs and up to two UL applicable TCIs, where the DL applicable TCI may include a DL TCI (DL only) and a joint TCI (joint), and the UL applicable TCI may include a UL TCI (UL only) and a joint TCI (joint). In some cases, the code point mapped to a single TCI may be a code point mapped to a TCI of a single TRP, which may be a code point mapped to a single DL TCI, a code point mapped to a single UL TCI, or a code point mapped to a single DL TCI and a single UL TCI. In some cases, the code point mapped to two TCIs may be a code point mapped to a TCI of two TRPs, where, for example, the code point may be mapped to a single DL TCI and a single joint TCI, or the code point may be mapped to two DL TCIs.

[0084] Unified TCI includes directional TCI and joint TCI. The UE can be configured to have directional TCI or joint TCI or both. For example, the UE can be configured for one TRP with directional TCI and another TRP with joint TCI. However, support for other combinations of TCI configurations can facilitate the expansion of options for mTRP communications, thereby adding flexibility to the network.

[0085] Some aspects of the techniques and apparatus described herein provide per-TRP TCI type configuration and indication. For example, a UE may receive an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP. The UE may communicate based at least in part on the mTRP configuration. In this way, some aspects may facilitate expansion of options for mTRP TCI mapping and communication and thus add flexibility to the network. Therefore, some aspects may have a positive impact on network performance.

[0086] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0087] Figure 5 5 is a call flow diagram illustrating an example 500 associated with configuring a TCI type for a TRP in an mTRP operation according to the present disclosure. As shown, a UE 502 and a network node 504 may communicate with each other. In some aspects, the UE 502 and the network node 504 may communicate with each other based on the mTRP configuration. In some aspects, the network node 504 may include a first TRP 506 and a second TRP 508, as shown. In some other aspects, one or both of the TRP 506 and the TRP 508 may be independent of the network node 504. The UE 502 may be, similar to, including, or included in: Figure 5 UE 502 depicted in Figure 4 UE 405 and / or Figures 1 to 3 UE 120 depicted in FIG. The network node 504 may be, be similar to, include, or be included in: Figure 4 TRP 410 and / or TRP 415 and / or Figure 1 and Figure 2 A network node 110 is depicted in FIG.

[0088] As shown by reference numeral 510, the network node 504 may send and the UE 502 may receive an mTRP configuration. The mTRP configuration may include an RRC configuration and may indicate any number of configurations. In some aspects, for example, the mTRP configuration may indicate a first TRP ID corresponding to TRP 506 and a second TRP ID corresponding to TRP 508. In some aspects, the mTRP configuration may indicate at least one of a channel or a reference signal associated with at least one TCI state in a plurality of TCI states. In some aspects, the mTRP configuration may configure a component carrier list indicating a plurality of frequency partitions. The plurality of frequency partitions may be associated with a unified TCI indication. In some aspects, TRP 506 may be associated with a first CORESET pool index, and TRP508 may be associated with a second CORESET pool index.

[0089] In some aspects, the mTRP configuration may indicate a first TCI state type corresponding to TRP 506 and a second TCI state type corresponding to TRP 508. In some aspects, for example, the first TCI state type may match the second TCI state type. When the two TCI state types are the same, the TCI state type matches the other TCI state type. In some aspects, the first TCI state type may be a joint TCI state type or a directional TCI state type. In some aspects, the first TCI state type may be a directional TCI state type, and the second TCI state type may be a joint TCI state type. For example, in some aspects, the wireless network may support a per-TRP TCI type (directional or joint TCI) configuration for a UE (e.g., UE 502) in mTRP operation. In the first case, two TRPs may be configured to have a joint TCI type. In the second case, two TRPs may be configured to have a directional TCI type. In the third case, one TRP may be configured to have a directional TCI type, and another TRP may be configured to have a joint TCI type.

[0090] As shown by reference numeral 512, the network node 504 may send and the UE 502 may receive a TCI activation MAC CE. The TCI activation MAC CE may include an activation indicator corresponding to at least one code point mapped to multiple TCI states. In some aspects, the at least one code point includes a single code point. In some aspects, the mTRP configuration may include a TCI activation MAC CE. In some aspects, to support code points mapped to multiple TCI states, the UE 502 may be configured with a CSI report to report one or more pairs of beams that may be received or transmitted simultaneously. For example, when UE 502 is configured with parameter “groupBasedBeamReporting-r17” in group-based CSI reporting configuration “CSI-ReportConfig”, when the corresponding CSI resource set is not configured with a repetition parameter set to “on”, UE 502 may report CSI resource indexes (CRIs) for CSI reporting in pairs, and when UE 502 is configured with parameter “groupBasedBeamReporting-r17” in group-based CSI reporting configuration “CSI-ReportConfig”, where the repetition parameter is set to “on”, UE 502 may not report CRIs for CSI reporting.

[0091] As shown in reference numeral 514, network node 504 may send and UE 502 may receive one or more DCI transmissions. In some aspects, the mTRP configuration may correspond to a single downlink control information (sDCI) operation. In some aspects, for example, the mTRP configuration may include a TCI mapping including a TCI state activation field that maps a corresponding TCI state to a reference TCI code point in a DCI transmission. In some aspects, the mapping between the TCI state and the TCI code point may be indicated by a higher layer signaling such as a TCI activation MAC-CE. For example, the TCI activation MAC-CE may activate multiple TCI code points, and the DCI may indicate to the UE 502 a TCI code point selected from multiple TCI code points.

[0092] The TCI state activation field may map the next TCI state indicated in the next octet of the TCI map based at least in part on the value of the TCI state activation field, where the value is the first value or the second value. For example, for sDCI mTRP operation, the UE 502 may be activated for one or more TCIs for TCI code points in the DCI. The TCI activation field C_x may indicate that the corresponding TCI is activated for the xth TCI code point.

[0093] In some aspects, the next TCI state may be mapped to a reference TCI code point based at least in part on the value being a first value (e.g., where C_x=1). In some aspects, the next TCI state may be mapped to the next TCI code point based at least in part on the value being a second value (e.g., where C_x=0). A TCI code point set of one or more TCI code points may be associated with one of the first TRP and the second TRP, and each TCI state associated with a TCI code point of the TCI code point set in one or more TCI states may be associated with a directional TCI state type. In some aspects, a TCI code point set of one or more TCI code points may be associated with one of the first TRP and the second TRP. Each TCI state associated with a TCI code point of the TCI code point set in one or more TCI states may be associated with a joint TCI state type. In some aspects, for example, the TCI states indicated in different TCI code points belonging to the same TRP may all be configured as directional TCI state types or joint TCI state types. Figures 6 to 9 Several different implementations of TCI mapping for sDCI mTRP operation are depicted.

[0094] In some aspects, the mTRP configuration may correspond to a multi-downlink control information (mDCI) operation. One or more DCI transmissions may include multiple DCI transmissions. The first DCI transmission may indicate a first TCI state set corresponding to a first TRP associated with a first TCI code point set, and a second TCI state set corresponding to a second TRP associated with a second TCI code point set. Each TCI state in the first TCI state set may correspond to a first TCI state type, and each TCI state in the second TCI state set may correspond to a second TCI state type. For example, for mDCI mTRP operation, for TCIs of different TCI code points activated for each TRP, a TCI type may be configured for each TRP.

[0095] In some aspects, the first TCI state type may be a directional TCI state type, and the second TCI state type may be a joint TCI state type. Each TCI code point of the first TCI code point set may be associated with at least one of an uplink TCI state or a downlink TCI state, and each TCI code point of the second TCI code point set may be associated with a joint TCI state. In some aspects, for example, for mDCI mTRP, one TRP may be configured to have a directional TCI state, and another TRP may be configured to have a joint TCI state. A TRP (e.g., TRP 506) may be activated using a TCI code point having a DL TCI state, a UL TCI state, or a pair including a DL TCI state and a UL TCI state. Another TRP (e.g., TRP508) may be activated using a TCI code point having a joint TCI state.

[0096] As indicated by reference numeral 516, UE 502 and network node 504 may communicate based at least in part on the mTRP configuration.

[0097] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0098] Figure 6is a diagram illustrating an example 600 associated with configuring TCI types for a TRP in an mTRP operation in accordance with the present disclosure. For example, example 600 may include a TCI state map 602 that may be indicated, for example, using a bitmap in a MAC CE. As shown, the state map 602 may indicate a mapping of an uplink TCI state type (shown as "U"), a downlink TCI state type (shown as "D"), and a joint TCI state type (shown as "J") to code points. In example 600, the first TCI state type may be a joint TCI state type, and the second TCI state type may be a joint TCI state type. One or more TCI code points may include TCI code points indicating a first TCI state and a second TCI state, and the first TCI state may be associated with a first TRP and the second TCI state may be associated with a second TRP.

[0099] For example, as shown, the first TCI code point may include a TCI activation indication field indicating a mapping of the first TCI code point to joint TCI state #35 via a first value (C_x=0). The second TCI code point may indicate two TCI states, one TCI state associated with the first TRP and the other TCI state associated with the second TRP. For example, as shown, the second TCI code point may include a first TCI activation indication field indicating a mapping of the second TCI code point to joint TCI state #7 via a second value (C_x=1). The second TCI code point may include a second TCI activation indication field indicating a mapping of the second TCI code point to joint TCI state #29 via a first value (e.g., C_x=0).

[0100] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The example described is different. In this example, both TRPs are configured to have a TCI state with a joint TCI type, and the TCI state in all activated TCI codepoints is a joint TCI state.

[0101] Figure 7 7 is a diagram illustrating an example 700 associated with configuring TCI types for a TRP in mTRP operation according to the present disclosure. For example, the example 700 may include a TCI state map 702 that may be indicated, for example, using a bitmap in a MAC CE. In the example 700, two TCI state types (each of which is associated with a TRP) may be directional TCI state types.

[0102] For example, as shown, the TCI code point associated with row 12 may include: a first TCI activation indication field indicating a mapping of the TCI code point to DL TCI state #7 via a second value (C_x=1); a second TCI activation indication field indicating a mapping of the TCI code point to UL TCI state #29 via a second value (C_x=1); a third TCI activation indication field indicating a mapping of the TCI code point to DL TCI state #6 via a second value (C_x=1); and a fourth TCI activation indication field indicating a mapping of the TCI code point to UL TCI state #21 via a first value (C_x=0). In some cases, rows 3 and 5 of TCI state mapping 702 may both not be supported due to ambiguity.

[0103] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The example described is different. In this example, both TRPs are configured to have a TCI state with a directional TCI type, and the TCI state in all activated TCI code points is either a DL TCI state or a UL TCI state.

[0104] Figure 8 is a diagram illustrating an example 800 associated with configuring TCI types for a TRP in an mTRP operation in accordance with the present disclosure. For example, example 800 may include a TCI state map 802 that may be indicated, for example, using a bitmap in a MAC CE. In example 800, a first TCI state type may be a directional TCI state type, and a second TCI state type may be a joint TCI state type. For example, TRP A may be configured only for a directional TCI state, and TRP B may be configured only for a joint TCI state. In example 800, a TCI state scan operation may be allowed in only one of the activated TCI code points.

[0105] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The example described is different. In this example, the first TRP (e.g., TRP A) is configured with a directional TCI with a TCI type, and the second TRP (e.g., TRPB) is configured with a TCI state with a joint TCI type. A TCI code point can be activated with two DL applicable TCI states (e.g., joint TCI or DL ​​TCI) or two UL applicable TCI states (e.g., joint TCI or DL ​​TCI), and for the TCI code point, the first DL or UL applicable TCI (which is a separate DL or UL TCI) can be intended for TRP A, and the second DL or UL applicable TCI (which is a joint TCI) can be intended for TRP B.

[0106] Fig. 9 9 is a diagram illustrating an example 900 associated with configuring TCI types for a TRP in an mTRP operation in accordance with the present disclosure. For example, example 900 may include a TCI state map 902 that may be indicated, for example, using a bitmap in a MAC CE. In example 900, a first TCI state type may be a directional TCI state type, and a second TCI state type may be a joint TCI state type. For example, TRP A may be configured only for a directional TCI state, and TRP B may be configured only for a joint TCI state. In example 900, TCI state scan operations may be allowed in more than one TCI code point, as shown in association with rows having D, U, and J TCI states.

[0107] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 The examples described are different. In this example, a first TRP (e.g., TRP A) is configured to have a TCI state with a directional TCI type, and a second TRP (e.g., TRP B) is configured to have a TCI state with a joint TCI type. The TCI code point can be activated with two DL applicable TCI states (e.g., joint TCI or DL ​​TCI) or two UL applicable TCIs (e.g., joint TCI or DL ​​TCI), and the TRP order can be further indicated by the TCI code point. In some TCI code points, the first DL or UL applicable TCI as a separate DL or UL TCI may be intended for TRP A, and the second DL or UL applicable TCI as a joint TCI may be intended for TRP B. In some TCI code points, the first DL or UL applicable TCI as a joint TCI may be intended for TRP B, and the second DL or UL applicable TCI as a separate DL or UL TCI may be intended for TRP A.

[0108] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a UE according to the present disclosure. Example process 1000 is an example in which a UE (eg, UE 502) performs operations associated with configuring a TCI type for a TRP in an mTRP operation.

[0109] like Fig.10 As shown in FIG. 1 , in some aspects, process 1000 may include configuring an mTRP, the mTRP configuration indicating a first TCI state type corresponding to a TRP and a second TCI state type corresponding to a second TRP (block 1010). For example, a UE (e.g., using Fig.12The communication manager 1208 and / or receiving component 1202 depicted in the figure can receive an mTRP configuration that indicates a TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP, as described above.

[0110] like Fig.10 As further shown in FIG. 1 , in some aspects, process 1000 may include communicating based at least in part on the mTRP configuration (block 1020). For example, a UE (e.g., using Fig.12 The communication manager 1208, receiving component 1202 and / or sending component 1204 depicted in the figure can communicate based at least in part on the mTRP configuration, as described above.

[0111] Process 1000 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.

[0112] In a first aspect, a first TCI state type matches a second TCI state type, and wherein the first TCI state type comprises a joint TCI state type. In a second aspect, either alone or in combination with the first aspect, the first TCI state type matches the second TCI state type, and wherein the first TCI state type comprises a directional TCI state type. In a third aspect, either alone or in combination with one or more of the first and second aspects, the first TCI state type comprises a directional TCI state type, and the second TCI state type comprises a joint TCI state type.

[0113] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the mTRP configuration corresponds to an sDCI operation, the method further comprising receiving a DCI transmission indicating one or more TCI states associated with one or more TCI code points. In a fifth aspect, either alone or in combination with the fourth aspect, the mTRP configuration comprises a TCI map, the TCI map comprising a TCI state activation field, the TCI state activation field mapping the corresponding TCI state to a reference TCI code point in the DCI transmission, wherein the TCI state activation field maps a next TCI state indicated in a next octet of the TCI map based at least in part on a value of the TCI state activation field, wherein the value is a first value or a second value.

[0114] In a sixth aspect, either alone or in combination with the fifth aspect, the next TCI state is mapped to a reference TCI code point based at least in part on the value being a first value. In a seventh aspect, either alone or in combination with the sixth aspect, the next TCI state is mapped to the next TCI code point based at least in part on the value being a second value. In an eighth aspect, either alone or in combination with one or more of the fourth to seventh aspects, a TCI code point set of one or more TCI code points is associated with one TRP in the first TRP and the second TRP, and wherein each TCI state associated with a TCI code point of the TCI code point set in the one or more TCI states is associated with a directional TCI state type. In a ninth aspect, either alone or in combination with one or more of the fourth to eighth aspects, a TCI code point set of one or more TCI code points is associated with one TRP in the first TRP and the second TRP, and wherein each TCI state associated with a TCI code point of the TCI code point set in the one or more TCI states is associated with a joint TCI state type.

[0115] In the tenth aspect, alone or in combination with the fourth aspect, the first TCI state type is a joint TCI state type, and wherein the second TCI state type is a joint TCI state type. In the eleventh aspect, alone or in combination with one or more of the fourth to tenth aspects, one or more TCI code points include a TCI code point indicating a first TCI state and a second TCI state, and wherein the first TCI state is associated with a first TRP and the second TCI state is associated with a second TRP. In the twelfth aspect, alone or in combination with the fourth aspect, the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a directional TCI state type. In the thirteenth aspect, alone or in combination with the fourth aspect, the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a joint TCI state type.

[0116] In a fourteenth aspect, alone or in combination with one or more of the fourth aspect or the thirteenth aspect, a TCI state scan operation is allowed in only one TCI code point among the one or more TCI code points. In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, a TCI state scan operation is allowed in more than one TCI code point among the one or more TCI code points.

[0117] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the mTRP configuration corresponds to an mDCI operation, and the method also includes receiving multiple DCI transmissions, wherein a first DCI transmission indicates a first TCI state set corresponding to a first TRP associated with a first TCI code point set and a second TCI state set corresponding to a second TRP associated with a second TCI code point set.

[0118] In the seventeenth aspect, either alone or in combination with the sixteenth aspect, each TCI state of the first TCI state set corresponds to a first TCI state type, and wherein each TCI state of the second TCI state set corresponds to a second TCI state type. In the eighteenth aspect, either alone or in combination with the seventeenth aspect, the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a joint TCI state type. In the nineteenth aspect, either alone or in combination with the eighteenth aspect, each TCI code point of the first TCI code point set is associated with at least one of an uplink TCI state or a downlink TCI state, and wherein each TCI code point of the second TCI code point set is associated with a joint TCI state. In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the first TRP is associated with a first CORESET pool index, and the second TRP is associated with a second CORESET pool index.

[0119] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 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 1000 may be performed in parallel.

[0120] Fig.11 is a diagram illustrating an example process 1100 performed, for example, by a network node in accordance with the present disclosure. The example process 1100 is an example in which a network node (eg, network node 504) performs operations associated with configuring a TCI type for a TRP in an mTRP operation.

[0121] like Fig.11 As shown in FIG. 1 , in some aspects, process 1100 may include sending an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP (block 1110). For example, a network node (e.g., using Fig.13The communication manager 1308 and / or the sending component 1304 depicted in the figure can send an mTRP configuration that indicates a first TCI state type corresponding to the first TRP and a second TCI state type corresponding to the second TRP, as described above.

[0122] like Fig.11 As further shown in FIG. 1 , in some aspects, process 1100 may include communicating based at least in part on the mTRP configuration (block 1120). For example, a network node (e.g., using Fig.13 The communication manager 1308, receiving component 1302 and / or sending component 1304 depicted in the figure can communicate based at least in part on the mTRP configuration, as described above.

[0123] Process 1100 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.

[0124] In a first aspect, a first TCI state type matches a second TCI state type, and wherein the first TCI state type includes a joint TCI state type. In a second aspect, either alone or in combination with the first aspect, the first TCI state type matches the second TCI state type, and wherein the first TCI state type includes a directional TCI state type. In a third aspect, either alone or in combination with one or more of the first and second aspects, the first TCI state type includes a directional TCI state type, and the second TCI state type includes a joint TCI state type. In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the mTRP configuration corresponds to an sDCI operation, and the method further includes sending a DCI transmission indicating one or more TCI states associated with one or more TCI code points.

[0125] In a fifth aspect, either alone or in combination with the fourth aspect, the mTRP configuration includes a TCI mapping, the TCI mapping including a TCI state activation field, the TCI state activation field mapping the corresponding TCI state to a reference TCI code point in the DCI transmission, wherein the TCI state activation field maps the next TCI state indicated in the next octet of the TCI mapping based at least in part on the value of the TCI state activation field, wherein the value is a first value or a second value. In a sixth aspect, either alone or in combination with the fifth aspect, the next TCI state is mapped to the reference TCI code point based at least in part on the value being a first value. In a seventh aspect, either alone or in combination with the fifth aspect, the next TCI state is mapped to the next TCI code point based at least in part on the value being a second value.

[0126] In an eighth aspect, either alone or in combination with one or more of the fourth to seventh aspects, a TCI code point set of one or more TCI code points is associated with one of the first TRP and the second TRP, and wherein each TCI state in the one or more TCI states associated with a TCI code point of the TCI code point set is associated with a directional TCI state type. In a ninth aspect, either alone or in combination with one or more of the fourth to eighth aspects, a TCI code point set of one or more TCI code points is associated with one of the first TRP and the second TRP, and wherein each TCI state in the one or more TCI states associated with a TCI code point of the TCI code point set is associated with a joint TCI state type.

[0127] In a tenth aspect, either alone or in combination with the fourth aspect, the first TCI state type is a joint TCI state type, and wherein the second TCI state type is a joint TCI state type. In an eleventh aspect, either alone or in combination with one or more of the fourth to tenth aspects, the one or more TCI code points include a TCI code point indicating a first TCI state and a second TCI state, and wherein the first TCI state is associated with a first TRP and the second TCI state is associated with a second TRP.

[0128] In the twelfth aspect, either alone or in combination with the fourth aspect, the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a directional TCI state type. In the thirteenth aspect, either alone or in combination with the fourth aspect, the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a joint TCI state type. In the fourteenth aspect, either alone or in combination with one or more of the fourth aspect or the thirteenth aspect, a TCI state scanning operation is allowed in only one TCI code point in one or more TCI code points. In the fifteenth aspect, either alone or in combination with one or more of the fourth aspect or the thirteenth aspect, a TCI state scanning operation is allowed in more than one TCI code point in one or more TCI code points.

[0129] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, the mTRP configuration corresponds to an mDCI operation, the method further comprising sending a plurality of DCI transmissions, wherein the first DCI transmission indicates a first TCI state set corresponding to a first TRP associated with a first TCI code point set and a second TCI state set corresponding to a second TRP associated with a second TCI code point set. In the seventeenth aspect, either alone or in combination with the sixteenth aspect, each TCI state of the first TCI state set corresponds to a first TCI state type, and wherein each TCI state of the second TCI state set corresponds to a second TCI state type. In the eighteenth aspect, either alone or in combination with the seventeenth aspect, the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a joint TCI state type. In the nineteenth aspect, either alone or in combination with the eighteenth aspect, each TCI code point of the first TCI code point set is associated with at least one of an uplink TCI state or a downlink TCI state, and wherein each TCI code point of the second TCI code point set is associated with a joint TCI state. In a twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the first TRP is associated with a first control resource set (CORESET) pool index, and the second TRP is associated with a second CORESET pool index.

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

[0131] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication. Apparatus 1200 may be a UE, or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a network node, or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 1208.

[0132] In some aspects, the apparatus 1200 may be configured to perform the Figures 4 to 9 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Fig.10The process of 1000 Fig.11 In some aspects, Fig.12 The apparatus 1200 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown in the figure 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 codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0133] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 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 one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0134] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 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 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0135] The communication manager 1208 and / or the receiving component 1202 can receive an mTRP configuration indicating a first TCI state type corresponding to a first TRP and a second TCI state type corresponding to a second TRP. In some aspects, the communication manager 1208 can include combining Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the UE described herein. In some aspects, the communication manager 1208 may include a receiving component 1202 and / or a sending component 1204. In some aspects, the communication manager 1208 may be Figure 1 and Figure 2 The communication manager 140 depicted in, similar to, including, or included in the communication manager. The communication manager 1208, the receiving component 1202, and / or the sending component 1204 can communicate based at least in part on the mTRP configuration.

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

[0137] Fig.13 1 is a diagram of an example apparatus 1300 for wireless communication. Apparatus 1300 may be a network node, or a network node may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a sending component 1304 that 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 a UE, a network node, or another wireless communication device) using receiving component 1302 and sending component 1304. As further shown, apparatus 1300 may include a communication manager 1308.

[0138] In some aspects, the apparatus 1300 may be configured to perform the Figures 4 to 9 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.10 The process of 1000 Fig.11In some aspects, Fig.13 The apparatus 1300 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown in the figure 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 codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0139] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1306. The receiving component 1302 may provide the received communications to one or more other components of the apparatus 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) on ​​the received communications and may provide the processed signals to one or more other components of the apparatus 1300. In some aspects, the receiving component 1302 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a UE or network node described.

[0140] The transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1306. In some aspects, one or more other components of the device 1300 may generate communications and may provide the generated communications to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting 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 the device 1306. In some aspects, the transmitting component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE or network node. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0141] The sending component 1304 can send an mTRP configuration that indicates a first TCI state type corresponding to the first TRP and a second TCI state type corresponding to the second TRP. In some aspects, the communication manager 1308 can include combining Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of a UE or network node as described herein. In some aspects, the communication manager 1308 may include a receiving component 1302 and / or a sending component 1304. In some aspects, the communication manager 1308 may be Figure 1 and Figure 2 The communication manager 150 depicted in, similar to, including, or included in the communication manager. The communication manager 1308, the receiving component 1302, and / or the sending component 1304 can communicate based at least in part on the mTRP configuration.

[0142] Fig.13 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.13 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.13 Two or more components shown in the figure may be implemented in a single component, or Fig.13 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.13 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.13 One or more functions performed by another group of components shown in the figure.

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

[0144] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving a multiple transmit-receive point (mTRP) configuration, wherein the multiple transmit-receive point (mTRP) configuration indicates a first transmit configuration indicator (TCI) state type corresponding to a first transmit-receive point (TRP) and a second TCI state type corresponding to a second TRP; and communicating at least in part based on the mTRP configuration.

[0145] Aspect 2: The method according to aspect 1, wherein the first TCI state type matches the second TCI state type, and wherein the first TCI state type includes a joint TCI state type.

[0146] Aspect 3: The method according to aspect 1, wherein the first TCI state type matches the second TCI state type, and wherein the first TCI state type includes a directional TCI state type.

[0147] Aspect 4: The method according to aspect 1, wherein the first TCI state type includes a directional TCI state type, and the second TCI state type includes a joint TCI state type.

[0148] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the mTRP configuration corresponds to a single downlink control information (sDCI) operation, and the method further includes receiving a downlink control information (DCI) transmission indicating one or more TCI states associated with one or more TCI code points.

[0149] Aspect 6: A method according to Aspect 5, wherein the mTRP configuration includes a TCI mapping, the TCI mapping includes a TCI state activation field, the TCI state activation field maps the corresponding TCI state to a reference TCI code point in the DCI transmission, wherein the TCI state activation field maps the next TCI state indicated in the next octet of the TCI mapping at least in part based on the value of the TCI state activation field, wherein the value is a first value or a second value.

[0150] Aspect 7: The method according to aspect 6, wherein the next TCI state is mapped to the reference TCI code point based at least in part on the value being the first value.

[0151] Aspect 8: The method of aspect 6, wherein the next TCI state is mapped to a next TCI code point based at least in part on the value being the second value.

[0152] Aspect 9: A method according to any one of Aspects 5 to 8, wherein a TCI code point set of the one or more TCI code points is associated with one TRP of the first TRP and the second TRP, and wherein each TCI state of the one or more TCI states associated with a TCI code point of the TCI code point set is associated with a directional TCI state type.

[0153] Aspect 10: A method according to any one of Aspects 5 to 8, wherein a TCI code point set of the one or more TCI code points is associated with one TRP of the first TRP and the second TRP, and wherein each TCI state of the one or more TCI states associated with a TCI code point of the TCI code point set is associated with a joint TCI state type.

[0154] Aspect 11: The method according to aspect 5, wherein the first TCI status type is a joint TCI status type, and wherein the second TCI status type is the joint TCI status type.

[0155] Aspect 12: A method according to any one of Aspects 5 to 11, wherein the one or more TCI code points include a TCI code point indicating a first TCI state and a second TCI state, and wherein the first TCI state is associated with the first TRP and the second TCI state is associated with the second TRP.

[0156] Aspect 13: The method according to aspect 5, wherein the first TCI state type is a directional TCI state type, and wherein the second TCI state type is the directional TCI state type.

[0157] Aspect 14: The method according to aspect 5, wherein the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a joint TCI state type.

[0158] Aspect 15: The method according to any one of aspects 5 or 14, wherein a TCI state scanning operation is allowed in only one TCI code point among the one or more TCI code points.

[0159] Aspect 16: The method according to any one of aspects 5 or 14, wherein a TCI state scanning operation is allowed in more than one TCI code point among the one or more TCI code points.

[0160] Aspect 17: A method according to any one of Aspects 1 to 16, wherein the mTRP configuration corresponds to a multi-downlink control information (mDCI) operation, and the method further includes receiving multiple downlink control information (DCI) transmissions, wherein a first DCI transmission indicates a first TCI state set corresponding to the first TRP and associated with a first TCI code point set, and a second TCI state set corresponding to the second TRP and associated with a second TCI code point set.

[0161] Aspect 18: The method according to aspect 17, wherein each TCI state of the first TCI state set corresponds to the first TCI state type, and wherein each TCI state of the second TCI state set corresponds to the second TCI state type.

[0162] Aspect 19: The method according to Aspect 18, wherein the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a joint TCI state type.

[0163] Aspect 20: A method according to Aspect 19, wherein each TCI code point of the first TCI code point set is associated with at least one of an uplink TCI state or a downlink TCI state, and wherein each TCI code point of the second TCI code point set is associated with a joint TCI state.

[0164] Aspect 21: A method according to any one of Aspects 1 to 20, wherein the first TRP is associated with a first control resource set (CORESET) pool index, and the second TRP is associated with a second CORESET pool index.

[0165] Aspect 22: A method of wireless communication performed by a network node, comprising: sending a multiple transmit-receive point (mTRP) configuration, wherein the multiple transmit-receive point (mTRP) configuration indicates a first transmit configuration indicator (TCI) state type corresponding to a first transmit-receive point (TRP) and a second TCI state type corresponding to a second TRP; and communicating based at least in part on the mTRP configuration.

[0166] Aspect 23: The method according to Aspect 22, wherein the first TCI status type matches the second TCI status type, and wherein the first TCI status type comprises a joint TCI status type.

[0167] Aspect 24: The method according to aspect 22, wherein the first TCI state type matches the second TCI state type, and wherein the first TCI state type comprises a directional TCI state type.

[0168] Aspect 25: The method according to Aspect 22, wherein the first TCI state type comprises a directional TCI state type, and the second TCI state type comprises a joint TCI state type.

[0169] Aspect 26: A method according to any one of Aspects 22 to 25, wherein the mTRP configuration corresponds to a single downlink control information (sDCI) operation, and the method further includes sending a downlink control information (DCI) indicating one or more TCI states associated with one or more TCI code points.

[0170] Aspect 27: A method according to Aspect 26, wherein the mTRP configuration includes a TCI mapping, the TCI mapping includes a TCI state activation field, the TCI state activation field maps the corresponding TCI state to a reference TCI code point in the DCI transmission, wherein the TCI state activation field maps the next TCI state indicated in the next octet of the TCI mapping at least in part based on the value of the TCI state activation field, wherein the value is a first value or a second value.

[0171] Aspect 28: The method of aspect 27, wherein the next TCI state is mapped to the reference TCI code point based at least in part on the value being the first value.

[0172] Aspect 29: The method of aspect 27, wherein the next TCI state is mapped to a next TCI code point based at least in part on the value being the second value.

[0173] Aspect 30: A method according to any one of Aspects 26 to 29, wherein a TCI code point set of the one or more TCI code points is associated with one TRP of the first TRP and the second TRP, and wherein each TCI state of the one or more TCI states associated with a TCI code point of the TCI code point set is associated with a directional TCI state type.

[0174] Aspect 31: A method according to any one of Aspects 26 to 29, wherein a TCI code point set of the one or more TCI code points is associated with one TRP of the first TRP and the second TRP, and wherein each TCI state of the one or more TCI states associated with a TCI code point of the TCI code point set is associated with a joint TCI state type.

[0175] Aspect 32: The method according to Aspect 26, wherein the first TCI status type is a joint TCI status type, and wherein the second TCI status type is the joint TCI status type.

[0176] Aspect 33: A method according to any one of Aspects 26 to 32, wherein the one or more TCI code points include a TCI code point indicating a first TCI state and a second TCI state, and wherein the first TCI state is associated with the first TRP and the second TCI state is associated with the second TRP.

[0177] Aspect 34: The method according to aspect 26, wherein the first TCI state type is a directional TCI state type, and wherein the second TCI state type is the directional TCI state type.

[0178] Aspect 35: The method according to Aspect 26, wherein the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a joint TCI state type.

[0179] Aspect 36: A method according to any one of Aspects 26 or 35, wherein a TCI state scan operation is allowed in only one TCI code point among the one or more TCI code points.

[0180] Aspect 37: A method according to any one of Aspects 26 or 35, wherein a TCI state scanning operation is allowed in more than one TCI code point among the one or more TCI code points.

[0181] Aspect 38: A method according to any one of Aspects 22 to 37, wherein the mTRP configuration corresponds to a multi-downlink control information (mDCI) operation, and the method further includes sending multiple downlink control information (DCI) transmissions, wherein a first DCI transmission indicates a first TCI state set corresponding to the first TRP and associated with a first TCI code point set, and a second TCI state set corresponding to the second TRP and associated with a second TCI code point set.

[0182] Aspect 39: The method according to aspect 38, wherein each TCI state of the first TCI state set corresponds to the first TCI state type, and wherein each TCI state of the second TCI state set corresponds to the second TCI state type.

[0183] Aspect 40: The method according to Aspect 39, wherein the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a joint TCI state type.

[0184] Aspect 41: A method according to Aspect 40, wherein each TCI code point of the first TCI code point set is associated with at least one of an uplink TCI state or a downlink TCI state, and wherein each TCI code point of the second TCI code point set is associated with a joint TCI state.

[0185] Aspect 42: A method according to any one of Aspects 22 to 41, wherein the first TRP is associated with a first control resource set (CORESET) pool index and the second TRP is associated with a second CORESET pool index.

[0186] Aspect 43: 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 one or more of the methods described in Aspects 1 to 21.

[0187] Aspect 44: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the memory comprising instructions, the instructions being executable by the one or more processors to cause the device to perform one or more of the methods described in Aspects 1 to 21.

[0188] Aspect 45: An apparatus for wireless communication, comprising: a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 21.

[0189] Aspect 46: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 21.

[0190] Aspect 47: 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 21.

[0191] Aspect 48: 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 device, cause the device to perform one or more of the methods described in aspects 1 to 21.

[0192] Aspect 49: An apparatus for 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 one or more of the methods described in Aspects 22 to 42.

[0193] Aspect 50: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the memory comprising instructions, the instructions being executable by the one or more processors to cause the device to perform the method according to one or more of aspects 22 to 42.

[0194] Aspect 51: An apparatus for wireless communication, comprising: a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 22 to 42.

[0195] Aspect 52: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 22 to 42.

[0196] Aspect 53: 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 22 to 42.

[0197] Aspect 54: 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 device, cause the device to perform one or more of the methods described in aspects 22 to 42.

[0198] 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.

[0199] As used herein, the term "component" is intended to be broadly interpreted as hardware and / or a combination of hardware and software. 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, executables, threads of execution, processes, and / or functions and other examples, whether it is described in software, firmware, middleware, microcode, hardware description language or other terms. As used herein, a processor is implemented in hardware and / or in a combination of 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, the operation and performance of these systems and / or methods are described herein without reference to specific software codes, and it should be understood that the software and hardware used to implement these systems and / or methods can be designed at least in part based on the description herein.

[0200] 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.

[0201] 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 (for example, 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 sorting of a, b and c).

[0202] 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 one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless explicitly stated otherwise. 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 (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; as well as one or more processors, the one or more processors being coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the UE to: receiving a multiple transmit-receive point (mTRP) configuration indicating a first transmit configuration indicator (TCI) state type corresponding to a first transmit-receive point (TRP) and a second TCI state type corresponding to a second TRP; and Communicate based at least in part on the mTRP configuration.

2. The UE of claim 1, wherein the first TCI state type matches the second TCI state type, and wherein the first TCI state type comprises a joint TCI state type.

3. The UE of claim 1, wherein the first TCI state type matches the second TCI state type, and wherein the first TCI state type comprises a directional TCI state type.

4. The UE of claim 1, wherein the first TCI state type comprises a directional TCI state type, and the second TCI state type comprises a joint TCI state type.

5. A UE according to claim 1, wherein the mTRP configuration corresponds to a single downlink control information (sDCI) operation, and wherein executable instructions are executable by the one or more processors to further enable the UE to receive a downlink control information (DCI) transmission indicating one or more TCI states associated with one or more TCI code points.

6. A UE according to claim 5, wherein the mTRP configuration includes a TCI mapping, the TCI mapping includes a TCI state activation field, the TCI state activation field maps the corresponding TCI state to a reference TCI code point in the DCI transmission, wherein the TCI state activation field maps the next TCI state indicated in the next octet of the TCI mapping at least partially based on the value of the TCI state activation field, wherein the value is a first value or a second value.

7. The UE of claim 6, wherein the next TCI state is mapped to the reference TCI code point based at least in part on the value being the first value.

8. The UE of claim 6, wherein the next TCI state is mapped to a next TCI code point based at least in part on the value being the second value.

9. The UE of claim 5, wherein the TCI code point set of the one or more TCI code points is associated with one TRP of the first TRP and the second TRP, and wherein each TCI state of the one or more TCI states associated with a TCI code point of the TCI code point set is associated with a directional TCI state type.

10. The UE of claim 5, wherein a TCI code point set of the one or more TCI code points is associated with one TRP of the first TRP and the second TRP, and wherein each TCI state of the one or more TCI states associated with a TCI code point of the TCI code point set is associated with a joint TCI state type.

11. The UE of claim 5, wherein the first TCI state type is a joint TCI state type, and wherein the second TCI state type is the joint TCI state type.

12. The UE of claim 5, wherein the one or more TCI code points include a TCI code point indicating a first TCI state and a second TCI state, and wherein the first TCI state is associated with the first TRP and the second TCI state is associated with the second TRP.

13. The UE of claim 5, wherein the first TCI state type is a directional TCI state type, and wherein the second TCI state type is the directional TCI state type.

14. The UE of claim 5, wherein the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a joint TCI state type.

15. The UE of claim 5, wherein a TCI state scanning operation is allowed in only one TCI code point among the one or more TCI code points.

16. The UE of claim 5, wherein a TCI state scanning operation is allowed in more than one TCI code point among the one or more TCI code points.

17. A UE according to claim 1, wherein the mTRP configuration corresponds to a multiple downlink control information (mDCI) operation, and wherein the executable instructions are executable by the one or more processors to further cause the UE to receive multiple downlink control information (DCI) transmissions, wherein a first DCI transmission indicates a first TCI state set corresponding to the first TRP associated with a first TCI code point set and a second TCI state set corresponding to the second TRP associated with a second TCI code point set.

18. The UE of claim 17, wherein each TCI state of the first TCI state set corresponds to the first TCI state type, and wherein each TCI state of the second TCI state set corresponds to the second TCI state type.

19. The UE of claim 18, wherein the first TCI state type is a directional TCI state type, and wherein the second TCI state type is a joint TCI state type.

20. The UE of claim 19, wherein each TCI code point of the first TCI code point set is associated with at least one of an uplink TCI state or a downlink TCI state, and wherein each TCI code point of the second TCI code point set is associated with a joint TCI state.

21. The UE of claim 1, wherein the first TRP is associated with a first control resource set (CORESET) pool index, and the second TRP is associated with a second CORESET pool index.

22. A network node for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the network node to: transmitting a multiple transmit-receive point (mTRP) configuration indicating a first transmit configuration indicator (TCI) state type corresponding to a first transmit-receive point (TRP) and a second TCI state type corresponding to a second TRP; and Communicate based at least in part on the mTRP configuration.

23. The network node of claim 22, wherein the first TCI state type matches the second TCI state type, and wherein the first TCI state type comprises a joint TCI state type or a directional TCI state type.

24. The network node of claim 22, wherein the first TCI state type comprises a directional TCI state type, and the second TCI state type comprises a joint TCI state type.

25. A network node according to claim 22, wherein the mTRP configuration corresponds to a single downlink control information (sDCI) operation, and wherein executable instructions are executable by the one or more processors to further cause the network node to send a downlink control information (DCI) transmission indicating one or more TCI states associated with one or more TCI code points.

26. The network node of claim 25, wherein the one or more TCI code points include a TCI code point indicating a first TCI state and a second TCI state, and wherein the first TCI state is associated with the first TRP and the second TCI state is associated with the second TRP.

27. A method of wireless communication performed by a user equipment (UE), comprising: receiving a multiple transmit-receive point (mTRP) configuration indicating a first transmit configuration indicator (TCI) state type corresponding to a first transmit-receive point (TRP) and a second TCI state type corresponding to a second TRP; and Communicate based at least in part on the mTRP configuration.

28. A method according to claim 27, wherein the mTRP configuration corresponds to a downlink control information (sDCI) operation, and the method also includes receiving a downlink control information (DCI) transmission indicating one or more TCI states associated with one or more TCI code points, wherein the one or more TCI code points include a TCI code point indicating a first TCI state and a second TCI state, and wherein the first TCI state is associated with the first TRP and the second TCI state is associated with the second TRP.

29. A method of wireless communication performed by a network node, comprising: transmitting a multiple transmit-receive point (mTRP) configuration indicating a first transmit configuration indicator (TCI) state type corresponding to a first transmit-receive point (TRP) and a second TCI state type corresponding to a second TRP; and Communicate based at least in part on the mTRP configuration.

30. A method according to claim 29, wherein the mTRP configuration corresponds to a downlink control information (sDCI) operation, and the method further includes sending a downlink control information (DCI) transmission indicating one or more TCI states associated with one or more TCI code points, wherein the one or more TCI code points include a TCI code point indicating a first TCI state and a second TCI state, and wherein the first TCI state is associated with the first TRP and the second TCI state is associated with the second TRP.

Images