Beam switching rules associated with switching between multiple transmit-receive points (mTRP) and single TRP (sTRP)

Abstract

In a Unified Transmission Configuration Indicator (TCI) framework, certain channels are pre-configured to use a fixed number of TCI states. However, when the number of TCI states dynamically changes during switching between a single transmit receive point (TRP) mode and a multi-TRP mode, the pre-configured channels are not currently updated. To mitigate this problem, a user equipment (UE) may receive downlink control information (DCI) indicating a first number of TCI states, and prior to the DCI, receive downlink information indicating a second number of TCI states, detect a switch between the multi-TRP (mTRP) mode and the single-TRP (sTRP) mode based on the first number of TCI states being different from the second number of TCI states, and transmit the detected switch between the multi-TRP (mTRP) mode and the single-TRP (sTRP) mode based on the first number of TCI states being different from the second number of TCI states. And communicating in a channel configured to use a selected TCI state associated with the first number of TCI states using a predefined rule based on the switching between the mTRP and the sTRP modes.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Non-Provisional Application No. 18 / 447,895, filed on August 10, 2023, and U.S. Provisional Application No. 63 / 377,875, filed on September 30, 2022, which are hereby incorporated by reference in their entirety. Technical Field

[0003] The present disclosure generally relates to communication systems, and more specifically to beam switching rules associated with switching between multiple transmit receive points (mTRP) and single TRP (sTRP). Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] Various aspects of the present disclosure relate to wireless communications, and in particular to efficient handling of transmit configuration indication (TCI) states in a user equipment (UE) when switching between a single transmit receive point (sTRP) mode and a multiple transmit receive point (mTRP) mode. In certain scenarios, channels such as a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) or a control resource set (CORESET) may be pre-configured assuming a fixed number of indicated TCIs. However, when the number of indicated TCI states changes dynamically due to UE switching between sTRP and mTRP modes, the pre-configuration of these channels may not be updated accordingly. To address this issue, the present disclosure defines rules or behaviors for pre-configuring channels when a change in the number of TRP or TCI states is detected. More specifically, if the UE receives downlink control information (DCI) indicating a number of TCI states (e.g., a first number of TCI states) that is different from the number of TCI states previously received (e.g., a second number of TCI states received in downlink information), the UE may detect a switch between mTRP and sTRP modes based on the difference between the first number and the second number of TCI states. The UE may communicate with a network entity in one or more channels configured to use a selected TCI state associated with the first number of TCI states following a predefined rule based on the detected switch. For example, when the first number of TCI states indicated in the DCI is greater than the second number of TCI states, the UE may detect a switch from sTRP mode to mTRP mode, and thus determine that the CORESET is configured to use a selected TCI state corresponding to the minimum TRP identifier among the TRP identifiers associated with the first number of TCI states. In another example, when a first number of TCI states indicated in the DCI is less than a second number of TCI states, the UE may detect a switch from mTRP mode to sTRP mode and thereby determine that the SPS PDSCH or CG PUSCH is configured to use a selected TCI state associated with the first number of TCI states that are active for the UE. Other rules may be similarly defined in other examples, but in any case, the method allows the UE to adapt to the dynamic changes in the number of TCI states due to sTRP / mTRP mode switching, thereby ensuring efficient communication with network entities in various channels such as the physical downlink control channel (PDCCH), semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH), and configuration grant (CG) physical uplink shared channel (PUSCH).In addition, the UE can determine the quasi co-location (QCL) assumption for the scheduled PDSCH based on the selected TCI state, and support channel state information (CSI) reporting based on the type II codebook for coherent joint transmission (CJT) in mTRP mode, thereby further enhancing the overall system performance and user experience in the wireless communication network.

[0008] Aspects of the present disclosure may result in several potential advantages. By detecting the switch between sTRP and mTRP modes and communicating in the configured channels accordingly using predefined rules, the UE can maintain optimal communication performance in various channels (such as PDCCH, SPS PDSCH, and CG PUSCH). For example, in response to determining that the CORESET is configured to use the selected TCI state corresponding to the minimum TRP identifier during the switch from sTRP mode to mTRP mode, the UE can ensure efficient communication with the network entity with minimal complexity when determining the appropriate TCI state for communication in mTRP mode. In another example, in response to determining that the SPS PDSCH or CG PUSCH is configured to use the selected TCI state associated with the first number of TCI states that are active for the UE during the switch from mTRP mode to sTRP mode, the UE can adapt to a reduced number of TCI states, thereby allowing more robust or reliable communication in sTRP mode. Based on these rules or other similar rules, the method enables the UE to adapt to dynamic changes in TCI states, thereby ensuring efficient communication with network entities. Furthermore, the ability to determine the QCL assumption for the scheduled PDSCH based on the selected TCI state allows the UE to optimize its reception performance, resulting in improved overall system performance and user experience in the wireless communication network. Additionally, supporting CSI reporting based on the type II codebook for CJT in mTRP mode enables the UE to provide more accurate and relevant feedback to the network entity, thereby facilitating better resource allocation and enhancing the overall performance of the wireless communication system.

[0009] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. According to one aspect of the present disclosure, an apparatus for wireless communication may include: one or more memories; and one or more processors, each of which is communicatively coupled to at least one of the one or more memories, and the one or more processors are capable of operating individually or in any combination to cause the apparatus to: receive a first number of downlink control information (DCI) indicating a transmission configuration indication (TCI) state from a network entity; detect a switch between a multiple transmit receive point (mTRP) mode and a single TRP (sTRP) mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; and communicate with the network entity in one or more channels configured to use a selected TCI state associated with the first number of TCI states using one or more predefined rules based on the switch between the mTRP mode and the sTRP mode.

[0010] According to one aspect of the present disclosure, an apparatus for wireless communication may include: a component for receiving a first number of DCIs indicating TCI states from a network entity; a component for detecting a switch between an mTRP mode and an sTRP mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; and a component for communicating with the network entity in one or more channels configured to use selected TCI states associated with the first number of TCI states using one or more predefined rules based on the switch between the mTRP mode and the sTRP mode.

[0011] A method for wireless communication according to one aspect of the present disclosure may include: receiving a first number of DCI indicating TCI states from a network entity; detecting a switch between an mTRP mode and an sTRP mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; and communicating with the network entity in one or more channels configured to use selected TCI states associated with the first number of TCI states using one or more predefined rules based on the switch between the mTRP mode and the sTRP mode.

[0012] A non-transitory computer-readable medium including computer executable code according to one aspect of the present disclosure may have code that, when executed by one or more processors of a UE, causes the one or more processors to perform the following operations, alone or in combination: receive a first number of DCIs indicating TCI states from a network entity; detect a switch between an mTRP mode and an sTRP mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; and communicate with the network entity in one or more channels configured to use a selected TCI state associated with the first number of TCI states using one or more predefined rules based on the switch between the mTRP mode and the sTRP mode.

[0013] To achieve the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0015] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0016] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0017] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0018] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0019] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0020] Figure 4 is a block diagram illustrating an example decomposed base station architecture in accordance with various aspects of the present disclosure.

[0021] Figure 5 It is a flowchart of beam selection rules during dynamic switching between multiple transmit receive point (mTRP) mode and single TRP (sTRP) mode according to one aspect of the present disclosure.

[0022] Figure 6 is a flow chart of a wireless communication method according to an aspect of the present disclosure.

[0023] Figure 7 is a block diagram illustrating an example configuration of a default beam for receiving information in accordance with various aspects of the present disclosure.

[0024] Figure 8 is a diagram illustrating an example of a hardware implementation for an example apparatus according to an aspect of the present disclosure. DETAILED DESCRIPTION

[0025] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid blurring such concepts.

[0026] Assuming a fixed number of indicated transmission configuration indications (TCIs) (e.g., semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH)), certain channels may be pre-configured, or the association of these channels with TCIs may be pre-configured (e.g., control resource sets (CORESETs)). However, when the number of indicated TCI states changes dynamically, the pre-configuration of such channels is currently not updated accordingly. To alleviate this problem during dynamic switching between multiple transmit receive points (mTRP) and single TRP (sTRP), it would be helpful to define rules or behaviors for pre-configuring channels after detecting a change in the number of TRPs.

[0027] The present disclosure provides a method for configuring one or more channels to use a selected TCI state associated with a first number of TCI states based on dynamic switching between an mTRP mode and an sTRP mode using one or more predefined rules, wherein a user equipment (UE) can detect switching between mTRP and sTRP modes in the UE based on a change in the first number of TCI states indicated in downlink control information (DCI).

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

[0029] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be widely interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc.

[0030] Accordingly, in one or more example aspects, the described functions may be implemented with hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0031] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a user equipment (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0032] The base station 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can also perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (eg, via the EPC 160 or the core network 190) via the third backhaul link 134 (eg, an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0033] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in the carrier aggregation for up to a total of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 can use a spectrum with a bandwidth of up to Y megahertz (MHz) (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​than for UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0034] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0035] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, a 5 gigahertz (GHz) unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0036] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0037] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is typically (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0038] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used in this document, it can broadly represent a frequency that can be less than 6 GHz, can be within FR1, or can 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 in this document, it can broadly represent a frequency that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

[0039] The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, may operate in the traditional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0040] Base station 180 may send beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also send beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or different. The transmit direction and receive direction of UE 104 may be the same or different.

[0041] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, an MBMS gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Generally speaking, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functions for MBMS user service configuration and delivery. BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. MBMS Gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area of ​​a broadcast specific service, and may be responsible for session management (start / stop) and for collecting eMBMS related billing information.

[0042] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Generally speaking, the AMF 192 provides quality of service (QoS) flow and session management. All user IP packets are delivered through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IMS, a packet switching (PS) streaming service, and / or other IP services.

[0043] Base stations may include and / or be referred to as gNBs, Node Bs, eNBs, access points, base transceivers, radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), transmit receive points (TRPs), or some other suitable terminology. Base stations 102 provide access points to EPC 160 or core network 190 for UEs 104. Examples of UEs 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0044] Although the present disclosure may focus on 5G NR, the concepts and various aspects described herein may be applicable to other similar areas such as LTE, Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), and / or other wireless / radio access technologies.

[0045] Reference again Figure 1 In certain aspects, the UE 104 may include a TRP mode dynamic switching configuration component 198. The UE 104, via the TRP mode dynamic switching configuration component 198, may be configured to: receive a first number of DCI indicating TCI states from a network entity; detect a switch between an mTRP mode and an sTRP mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; and communicate with the network entity in one or more channels configured to use a selected TCI state associated with the first number of TCI states using one or more predefined rules based on the switch between the mTRP mode and the sTRP mode.

[0046] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2CFIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of an UL channel within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), a subframe within the subcarrier set is dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), a subframe within the subcarrier set is dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 34 (most of which are UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0047] Other wireless communication technologies may have different frame structures and / or different channels. For example, a 10 millisecond (ms) frame may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbol on the DL may be a cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots in a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ *15 kilohertz (kHz), where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15 kHz, and the subcarrier spacing for parameter set μ=4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific set of parameters.

[0048] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0049] like Figure 2AAs illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration). x , where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). RS may also include beam measurement RS (BRS), beam refinement RS (BRRS) and phase tracking RS (PT-RS).

[0050] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. The PDCCH within a BWP may be referred to as a control resource set (CORESET). Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the position of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0051] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the combs in the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0052] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) / negative acknowledgement (NACK) feedback. The PUSCH carries data and may be used to carry, among other things, a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0053] Figure 33 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, IP packets from the EPC 160 may be provided to one or more controllers / processors 375. The one or more controllers / processors 375 implement layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. One or more controllers / processors 375 provide RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0054] One or more transmit (TX) processors 316 and one or more receive (RX) processors 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. One or more TX processors 316 handle mapping to signal constellations based on various modulation and coding schemes (MCS) (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce a plurality of spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0055] At the UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to one or more receive (RX) processors 356. One or more TX processors 368 and one or more RX processors 356 implement layer 1 functionality associated with various signal processing functions. One or more RX processors 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by one or more RX processors 356. Then, one or more RX processors 356 use a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to one or more controllers / processors 359 that implement layer 3 and layer 2 functionality.

[0056] The one or more controllers / processors 359 may each be associated with one or more memories 360 that store program codes and data. The one or more memories 360 may be referred to as computer readable media, alone or in any combination. In the UL, the one or more controllers / processors 359 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The one or more controllers / processors 359 are also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0057] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the one or more controllers / processors 359 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0058] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the one or more TX processors 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the one or more TX processors 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0059] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to one or more RX processors 370.

[0060] The one or more controllers / processors 375 may each be associated with one or more memories 376 that store program codes and data. The one or more memories 376 may be referred to as computer-readable media, either alone or in any combination. In the UL, the one or more controllers / processors 375 provide demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the one or more controllers / processors 375 may be provided to the EPC 160. The one or more controllers / processors 375 are also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0061] At least one of the one or more TX processors 368, the one or more RX processors 356, and the one or more controllers / processors 359 may be configured to perform operations related to Figure 1 The TRP mode dynamic switching configuration component 198 combines various aspects.

[0062] Figure 4 4 is a block diagram illustrating an example disaggregated base station 400 architecture. The disaggregated base station 400 architecture may include one or more CUs 410 that may communicate directly with a core network 420 via a backhaul link, or indirectly with a core network 420 through one or more disaggregated base station units, such as a near real-time (RT) RIC 425 via an E2 link, or a non-RT RIC 415 associated with a service management and orchestration (SMO) framework 405, or both. The CU 410 may communicate with one or more DUs 430 via respective midhaul links, such as an F1 interface. The DU 430 may communicate with one or more RUs 440 via respective fronthaul links. The RU 440 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 440.

[0063] Each of the units (i.e., CU 410, DU 430, RU 440, near-RT RIC 425, non-RT RIC 415, and SMO framework 405) may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive a signal or send a signal to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive a signal or send a signal to one or more of the other units via a wireless transmission medium, or both.

[0064] In some aspects, CU 410 may host higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 410. CU 410 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 410 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, CU 410 may be implemented to communicate with DU 430 for network control and signaling.

[0065] DU 430 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 440. In some aspects, DU 430 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional partitioning such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 430 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 430 or with control functions hosted by CU 410.

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

[0067] The SMO framework 405 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 405 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 405 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 490) 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 410, DU 430, RU 440, and near-RT RIC 425. In some specific implementations, the SMO framework 405 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 411 via the O1 interface. Additionally, in some specific implementations, the SMO framework 405 may communicate directly with one or more RUs 440 via the O1 interface. The SMO framework 405 may also include a non-RT RIC 415 configured to support the functionality of the SMO framework 405 .

[0068] The non-RT RIC 415 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 425. The non-RT RIC 415 may be coupled to or in communication with the near-RT RIC 425 (such as via an A1 interface). The near-RT RIC 425 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 410, one or more DUs 430, or both, and the O-eNB with the near-RT RIC 425.

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

[0070] In one aspect of the present disclosure, a unified transmit configuration indicator or indication (TCI) framework may be used to unify TCI for indicating multiple DL and UL TCI states, focusing on multi-TRP (mTRP) use cases. In some aspects, the unified TCI framework may facilitate simultaneous multi-panel UL transmissions to achieve higher UL throughput and / or reliability, focusing on FR2 (e.g., millimeter wave or higher frequencies) and multi-TRP modes, assuming up to 2 TRPs and up to 2 panels, for customer premises equipment (CPE) / fixed wireless access (FWA) / vehicles / industrial equipment. In one example of facilitating simultaneous multi-panel UL transmissions, in some aspects, the unified TCI framework may facilitate UL pre-coding indications for PUSCH, where no new codebook is introduced for multi-panel simultaneous transmissions. Considering multi-TRP operations based on single DCI and multi-DCI, the total number of data layers across all panels may be up to four and the total number of codewords across all panels may be up to two. In another example of facilitating simultaneous multi-panel UL transmission, in some aspects, UL beam indication for PUCCH / PUSCH (assuming unified TCI framework extension) may consider single-DCI and multi-DCI based multi-TRP operation. In this example, for the case of multi-DCI based multi-TRP operation, only PUSCH+PUSCH or PUCCH+PUCCH may be transmitted in the same component carrier across two panels.

[0071] There are three types of unified TCI. Type 1 is a joint TCI state, which indicates a common beam for at least one DL channel / RS plus at least one UL channel / RS (including at least UE-specific or dedicated PDCCH, PDSCH, PUCCH, PUSCH and CSI-RS). Type 2 is a separate DL TCI state, which is used to indicate a common beam for more than one DL channel / RS (including at least UE-specific or dedicated PDCCH, PDSCH and CSI-RS). Type 3 is a separate UL TCI state, which indicates a common beam for more than one UL channel / RS (including at least UE-specific or dedicated PUCCH, PUSCH).

[0072] In some aspects, a unified TCI may be configured in an RRC pool activated by a MAC-CE. DCI format 1_1 or 1_2 may indicate a unified TCI from an activated unified TCI. The indicated unified TCI may be applied to applicable channels (see Table 1). In some aspects, a DCI may indicate only 1 unified TCI at a time in an sTRP. In other aspects, when the unified TCI state framework is extended to an mTRP, a DCI may indicate more than 1 TCI (e.g., 1 indicated TCI per TRP).

[0073] As shown in Table 1, once activated, the TCI state can be applied to the following channels / RS.

[0074] Table 1: Application of TCI status to applicable channels

[0075]

[0076]

[0077] In one or more specific implementations, a DCI of format 1_1 or 1_2 may be used to indicate a TCI state of scheduling or not scheduling any DL assignment. When DCI is provided with a DL assignment, the TCI field in the DCI may explicitly indicate TCI. When DCI is provided without a DL assignment, TCI may be implicitly indicated as follows: 1) the cyclic redundancy check (CRC) of the DCI is scrambled by the configured scheduling radio network temporary identifier (CS-RNTI), and 2) the following fields are set as follows: Redundancy version (RV) = all '1'; Modulation and coding scheme (MCS) = all '1'; New data indicator (NDI) = 0; Frequency domain resource assignment (FDRA) = all '0' for FDRA type 0 or all '1' for FDRA type 1 or all '0' for dynamic switching; TCI field (if present) may be used to indicate TCI state ID; PDSCH to HARQ_Feedback Timing Indicator field (if present) may be used to indicate the time offset from the DCI to its ACK in PUCCH. For type-1 HARQ-ACK codebook, the TDRA field may be used to derive a virtual PDSCH position, which is further used to determine the position of the ACK information in the HARQ-ACK codebook.

[0078] Multiple TRPs may be deployed to improve spatial diversity of millimeter wave (mmW) signal reception. In some aspects, the maximum number of TRPs may be up to 2 TRPs. In other aspects, the maximum number of TRPs may be more than 2 TRPs.

[0079] In a configuration involving multiple TRPs using multiple DCIs (e.g., mTRP mDCI), each TRP may be associated with a CORESET pool. Each TRP may transmit its own PDCCH from the associated CORESET to schedule communications from the same TRP. In other words, DCI from a TRP may schedule communications from the same TRP. In some aspects, multiple TCI states may be associated with each CORESET pool TRP.

[0080] In a configuration involving multiple TRPs using a single DCI (e.g., mTRP sDCI), the DCI may schedule communications from multiple TRPs. When TCI is activated via MAC-CE, the MAC-CE may map a pair of TCIs (each of which originates from a corresponding TRP) to a TCI code point. The DCI may indicate the index of the TCI code point assigned for communication. In some aspects, a beam pair (each beam from a TRP) may be used for communication. In some aspects, a CORESET pool may not be configured, and the UE may or may not determine the association between a TRP and a TCI.

[0081] In the case of mTRP, the UE may have 1, 2, ... or M indicated TCIs, where M is the number of TRPs. The UE may have 0 or 1 indicated TCI per TRP. When the UE has more than 1 indicated TCI state, the association of the channel / resource with the indicated TCI state may be pre-configured or set by predefined rules. In some aspects, the indicated TCI state may be pre-configured by RRC signaling, where each CORESET is associated with 1 or 2 indicated TCI states. In other aspects, the indicated TCI state may be pre-configured by predefined rules. For example, if PUCCH / PUSCH is configured to have N-order repetitions, for each repetition, the UE may select an indicated TCI from multiple indicated TCIs by predefined rules. For example, the first repetition may use the first indicated TCI. In another example, the first repetition may use the TCI from CORESET pool ID0, etc.

[0082] Figure 5 500 is a flow chart of beam selection rules during dynamic switching of mTRP / sTRP modes according to an aspect of the present disclosure. Diagram 500 illustrates information received by UE 502 from BS 504. Initially, UE 502 receives downlink information, such as DL / TCI signal 506, from BS 504. UE 502 may also receive CORESET 508 from BS 504.

[0083] For example, the UE 502 may receive DCI 510 from the BS 504. At 512, the UE 502 then detects the sTRP / mTRP mode dynamic switch based on the received DCI 510. At 514, the UE 502 then configures the pre-configured one or more channels to use a fixed number of indicated TCIs or their pre-configured associations with TCIs based on the detected dynamic switch between the sTRP / mTRP modes. Finally, the UE 502 communicates data 516 with the BS 504 in the one or more channels configured at 514. For example, in a transmit beam associated with a TCI state selected for channel communication between UE 502 and base station 504 based on dynamic switching between detected sTRP / mTRP modes, UE 502 may receive downlink data in a PDCCH or PDSCH (e.g., a CORESET or SPS PDSCH) from base station 504, or UE 502 may send uplink data in a PUCCH or PUSCH (such as a CG PUSCH) to base station 504.

[0084] When only a single indicated TCI is indicated to the UE via DCI 510, the UE is effectively in sTRP mode. On the other hand, when multiple indicated TCIs are indicated to the UE via DCI, the UE is in mTRP mode. In some aspects, the indicated TCIs are dynamically updated by the DCI, which effectively changes the number of indicated TCIs. Therefore, the switch between sTRP and mTRP modes is effectively and dynamically signaled by the DCI.

[0085] Assuming a fixed number of indicated TCIs (e.g., SPS PDSCH), certain channels may be preconfigured, or their association with TCIs may be preconfigured (e.g., CORESET). However, the preconfiguration of those channels is not currently updated when the number of indicated TCI states changes dynamically. To alleviate this problem during dynamic switching of sTRP and mTRP, it would be helpful to define rules or behaviors for preconfigured channels after detecting a change in the number of TRPs.

[0086] In one or more specific implementations, the CORESET 508 may be configured to use N indicated TCIs (e.g., indicated to the UE 502 via the DL / TCI signal 506), where after the new TCI indication via the DCI 510, the UE has M indicated TCIs, where M>N. In this case, a switch is made from the sTRP mode to the mTRP mode. In some aspects, the CORESET 508 may still use the N indicated TCIs selected from the newly indicated M TCIs. The UE 502 may select which indicated TCI to use based on a predefined rule. For example, the UE 502 may be configured to use a single indicated TCI, and the CORESET 508 may be associated with the single TCI by pre-configuration. When the UE 502 receives the DCI 510, the UE 502 is indicated to have two indicated TCIs. In some specific implementations, the CORESET 508 may use the indicated TCI corresponding to the CORESET pool identifier (if the CORESET pool ID is configured). In other implementations, CORESET 508 may use the TCI corresponding to the indication of the smallest TRP identifier.

[0087] In one or more embodiments, CORESET 508 may be configured to use N indicated TCIs (e.g., indicated to UE 502 via DL / TCI signal 506), where after a new TCI indication via DCI 510, the UE has M indicated TCIs, where M < N. In this case, a switch is made from the mTRP mode to the sTRP mode. In some aspects, CORESET 508 may be deactivated until the next configuration. In other aspects, CORESET 508 may use the newly indicated M TCIs. For example, CORESET 508 may be preconfigured to be associated with two indicated TCIs (e.g., TCI1 and TCI2). The DCI 510 received by UE 502 may indicate that a single TCI corresponding to one of the preconfigured indicated TCIs (e.g., TCI2) is active for UE 502. Thus, CORESET 508 may use the newly indicated TCI2.

[0088] Thus, for CORESET sTRP / mTRP dynamic switching, the predefined rules for configuring the preconfigured channel may indicate that if two combined / DL TCI states are first indicated to the UE via the DL / TCI signal 506, and the DCI 510 later indicates to the UE 502 that a single combined / DL TCI state is indicated, the CORESET (e.g., CORESET 508) configured to share one or two indicated combined / DL TCI states may use the single indicated combined / DL TCI state.

[0089] In one or more embodiments, the preconfigured channel may be an SPS-PDSCH, which may be configured to use N indicated TCIs (e.g., indicated to UE 502 via DL / TCI signal 506), where after a new TCI indication via DCI 510, the UE has M indicated TCIs, where M > N. In this case, a switch is made from the sTRP mode to the mTRP mode. In some aspects, the SPS PDSCH may still use N indicated TCIs selected from the newly indicated M TCIs. UE 502 may select which indicated TCI to use based on predefined rules. For example, the SPS PDSCH may be configured to use a single indicated TCI. When UE 502 receives DCI 510, UE 502 is indicated to have two indicated TCIs. In some embodiments, the SPS PDSCH may use the indicated TCI corresponding to the smallest TRP identifier.

[0090] In one or more embodiments, the SPS PDSCH may be configured to use N indicated TCIs (e.g., indicated to the UE 502 via the DL / TCI signal 506), where after a new TCI indication via DCI 510, the UE has M indicated TCIs, where M < N. In this case, a switch is made from the mTRP mode to the sTRP mode. In some aspects, the SPS PDSCH may be deactivated until the next configuration. In other aspects, the SPS PDSCH may use the newly indicated M TCIs. In still other aspects, the SPS PDSCH may still use the originally configured TCIs. Which option to use may depend on the SPS PDSCH configuration. For example, if the SPS PDSCH is configured for time division multiplexing (TDM) or frequency division multiplexing (FDM), then an SPS PDSCH configured to use a smaller number of indicated TCIs compared to its original configuration may be acceptable. In another example, if the SPS PDSCH is configured for spatial division multiplexing (SDM), then the minimum number of TCI states may be based on the number of data layers of the UE. In some aspects, if the number of TCI states is less than the number of data layers, the UE 502 may disable the SPS PDSCH.

[0091] Thus, for SPS PDSCH sTRP / mTRP dynamic switching, the predefined rules for configuring the preconfigured channel may indicate that if two TCI states are first indicated to the UE via the DL / TCI signal 506 and DCI 510 later indicates to the UE 502 to instead indicate a single combined / DL TCI state, then the SPS PDSCH may use the later indicated combined / DL TCI state or the SPS PDSCH may be disabled. For example, for an FDM / TDM-based SPS PDSCH initially activated for two indicated combined / DL TCI states, all PDSCH occasions of the SPS PDSCH may use the later indicated single combined / DL TCI state. In another example, for an SDM-based SPS PDSCH initially activated for two indicated combined / DL TCI states, the corresponding SPS PDSCH may be implicitly disabled after the application time of the later indicated single combined / DL TCI state. In yet another example, for an sTRP-based SPS PDSCH initially activated for one of two indicated combined / DL TCI states, all PDSCH occasions of the SPS may use the later indicated single combined / DL TCI state.

[0092] Similarly, for PUSCH sTRP / mTRP dynamic switching, the predefined rules for configuring the pre-configured channels may indicate that if two TCI states are first indicated to the UE via the DL / TCI signal 506, and the DCI 510 may indicate to the UE 502 that a single TCI state is indicated instead, then the CG PUSCH may use a single indicated TCI state or the CG PUSCH may be disabled. For example, for PUSCH repetitions of type 1CG and type 2CG that are initially configured (or activated) for two indicated TCI states, all PUSCH repetitions may use a single TCI state that is indicated later. In another example, for SDM-based PUSCH repetitions of type 1CG and type 2CG that are initially configured (or activated) for two indicated TCI states, the corresponding CG may be implicitly disabled after the application time of the single TCI state that is indicated later.

[0093] In mTRP mode for PUSCH repetition with type 1 CG, the existing sounding reference signal (SRS) resource indicator and other parameters configured in the configured grant configuration parameter (referred to as "configuredGrantConfig" parameter) may be used to inform the UE 502 which indicated TCI state(s) are applied to the PUSCH. Specifically, if two SRIs and transmit precoder matrix indicators (TPMIs) are provided, and if two joint / UL TCI states are indicated in the DCI 510, then the PUSCH repetition associated with one SRS resource set may use one of the two indicated TCI states (e.g., the PUSCH repetition associated with the 1st SRS resource set may use the 1st indicated TCI state, and the PUSCH repetition associated with the 2nd SRS resource set may use the 2nd indicated TCI state). If there is only one set of SRI, TPMI and power control (PC) parameters in the configuredGrantConfig parameter, and if two joint / UL TCI states are indicated in DCI510, all PUSCH repetitions may use or be associated with one of the two indicated TCI states (e.g., the 1st indicated TCI state for all PUSCH repetitions). The PC parameters may include, for example, a path loss reference index (pathlossReferenceIndex), an alpha value for PUSCH (p0-PUSCH-Alpha), and a power control loop parameter (powerControlLoopToUse).

[0094] Thus, for PUSCH repetitions with type 1 CG, the predefined rules for configuring the preconfigured channel may indicate that an existing SRI configured in the configuredGrantConfig parameter may be reused to notify which TCI state(s) are applied to the PUSCH. In one or more specific implementations, if two SRIs and two precoding information are provided, if two joint / UL TCI states are indicated (e.g., the first indicated TCI state is for the PUSCH repetition associated with the first SRS resource set), then the PUSCH repetition associated with one SRS resource set may use one of the two indicated TCI states. In one or more specific implementations, if the configuredGrantConfig parameter contains only one value for each of pathlossReferenceIndex, p0-PUSCH-Alpha, powerControlLoopToUse, srs-ResourceIndicator, and precodingAndNumberOfLayers (for CB), if two joint / UL TCI states are indicated, all PUSCH repetitions may be associated with only one of the two indicated TCI states (e.g., the first indicated TCI state is used for all repetitions).

[0095] Figure 6 600 is a flow chart of a wireless communication method. The method may be performed by a UE (e.g., UE 104, 502; UE 350; device 802). As shown, flow chart 600 includes multiple enumerated operations, but aspects of flow chart 600 may include additional operations before, after, and between these enumerated operations. In some aspects, one or more of the enumerated operations may be omitted or performed in a different order. According to different aspects, one or more of the illustrated operations may be swapped and / or performed concurrently.

[0096] At 602, the UE may receive downlink control information indicating a first number of transmit configuration indication states, such as DCI 510, from a network entity. In some aspects, the UE may receive a CORESET preconfigured to use a second number of TCI states.

[0097] At 603 , the UE may receive a second amount of downlink information indicating a TCI state, such as the DL / TCI signal 506 , prior to receiving the downlink control information at 602 .

[0098] At 604, the UE may detect a switch between an mTRP mode and an sTRP mode in the UE based on a first number of TCI states indicated in the DCI being different from a second number of TCI states (such as in response to an identification DCI 510 indicating one TCI state and a previously indicated DL / TCI signal 506 indicating multiple TCI states, or vice versa). In some aspects, the first number of TCI states includes a single TCI state in the sTRP mode of the UE. In other aspects, the first number of TCI states includes multiple TCI states in the mTRP mode of the UE.

[0099] Finally, at 606, the UE may communicate with the network entity in one or more channels configured to use the selected TCI state associated with the first number of TCI states using one or more predefined rules based on the switch between the mTRP mode and the sTRP mode. In some aspects, the one or more channels are preconfigured to use a fixed number of TCI states prior to switching between the mTRP mode and the sTRP mode.

[0100] In some aspects, one or more channels may include a PDCCH associated with a CORESET that is preconfigured to use a second number of TCI states, and the first number of TCI states indicated in the DCI is greater than the second number of TCI states. Therefore, the UE may detect a switch from sTRP mode to mTRP mode for CORESET sTRP / mTRP dynamic switching based on the second number of TCI states being less than the first number of TCI states. In some aspects, one or more predefined rules indicate that the CORESET is configured to switch the associated TCI state from a TCI state associated with the second number of TCI states to a selected TCI state associated with the first number of TCI states based on the switch between mTRP mode and sTRP mode. In some aspects, one or more predefined rules further indicate that the CORESET is configured to use a selected TCI state corresponding to the minimum TRP identifier among the TRP identifiers associated with the first number of TCI states. In other aspects, one or more predefined rules further indicate that the CORESET is configured to use a selected TCI state corresponding to a CORESET pool identifier in response to a CORESET pool identifier being configured for the CORESET.

[0101] In other aspects, the first number of TCI states indicated in the DCI is less than the second number of TCI states. Thus, the UE may detect a switch from mTRP mode to sTRP mode for CORESET sTRP / mTRP dynamic switching based on the second number of TCI states being greater than the first number of TCI states. In some aspects, one or more predefined rules further indicate that the CORESET is configured to become disabled after the application time of the selected TCI state until the next downlink control signaling indicates another switch between mTRP mode and sTRP mode in the UE. In other aspects, one or more predefined rules further indicate that the CORESET is configured to use a selected TCI state that is active for the UE from the first number of TCI states.

[0102] In some aspects, one or more channels include a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) preconfigured to use a second number of TCI states, wherein one or more predefined rules indicate that the SPSPDSCH is configured to switch the associated TCI state from a TCI state associated with the second number of TCI states to a selected TCI state associated with the first number of TCI states based on switching between an mTRP mode and an sTRP mode.

[0103] In some aspects, a first number of TCI states indicated in a DCI is greater than a second number of TCI states, wherein the UE may detect a switch from sTRP mode to mTRP mode for PDSCH sTRP / mTRP dynamic switching based on the second number of TCI states being less than the first number of TCI states. In some aspects, one or more predefined rules further indicate that the SPS PDSCH is configured to use a selected TCI state corresponding to a CORESET pool identifier associated with a DCI activating the SPS PDSCH in response to a CORESET pool identifier being configured. In other aspects, one or more predefined rules further indicate that the SPS PDSCH is configured to use a selected TCI state corresponding to the minimum TRP identifier among the TRP identifiers associated with the first number of TCI states. In yet other aspects, one or more predefined rules further indicate that the SPS PDSCH is configured to use a selected TCI state corresponding to the minimum TCI identifier of the TCI associated with the first number of TCI states in response to a DCI indicating a TCI from the same CORESET pool associated with the first number of TCI states.

[0104] In some aspects, a first number of TCI states indicated in the DCI is less than a second number of TCI states, wherein the UE may detect a switch from mTRP mode to sTRP mode for PDSCH sTRP / mTRP dynamic switching based on the second number of TCI states being greater than the first number of TCI states. In some aspects, one or more predefined rules further indicate that the SPS PDSCH is configured to be implicitly disabled after the application time of the selected TCI state in response to the SPS PDSCH being configured for space division multiplexing (SDM) and the first number of TCI states indicated in the DCI being less than the number of data layers of the UE until the next downlink control signaling indicates another switch between mTRP mode and sTRP mode in the UE. In some aspects, one or more predefined rules further indicate that the SPS PDSCH is configured to use a selected TCI state associated with a first number of TCI states that are active for the UE in response to the SPS PDSCH being configured for time division multiplexing (TDM) or frequency division multiplexing (FDM). In some aspects, the one or more predefined rules further indicate that the SPS PDSCH is configured to use a TCI state associated with a second number of TCI states preconfigured to the UE.

[0105] In one or more specific implementations, one or more channels include a configuration grant (CG) physical uplink shared channel (PUSCH) preconfigured to use a second number of TCI states, wherein one or more predefined rules indicate that the CG PUSCH is configured to switch the associated TCI state from a TCI state associated with the second number of TCI states to a selected TCI state associated with a first number of TCI states based on a switch between the mTRP mode and the sTRP mode. In some aspects, the first number of TCI states indicated in the DCI is less than the second number of TCI states, wherein the UE may detect a switch from the mTRP mode to the sTRP mode for PUSCH sTRP / mTRP dynamic switching based on the second number of TCI states being greater than the first number of TCI states. In some aspects, the one or more predefined rules further indicate that the CG PUSCH is configured to become implicitly disabled after the application time of the selected TCI state in response to a PUSCH with a type 1CG or a type 2CG being configured for spatial division multiplexing (SDM) until the next downlink control signaling indicates another switch between the mTRP mode and the sTRP mode in the UE. In other aspects, one or more predefined rules further indicate that each PUSCH repetition of multiple PUSCH repetitions having type 1CG or type 2CG is configured to use a selected TCI state associated with a first number of TCI states that are active for the UE in response to the CG PUSCH being configured for time division multiplexing (TDM) or frequency division multiplexing (FDM).

[0106] In one or more specific implementations, the UE may be further configured to receive a configuration indicating one or more sounding reference signal (SRS) resource indicators (SRIs) from a network entity, wherein the one or more SRIs inform the UE that a selected TCI state is applied to a type 1 CG PUSCH repetition in a CG PUSCH. In some aspects, the selected TCI state associated with the first number of TCI states is applied to a type 1 CG PUSCH repetition associated with an SRS resource set in response to the configuration indicating multiple SRIs and the first number of TCI states indicating multiple TCI states. In other aspects, the selected TCI state associated with the first number of TCI states is applied to a type 1 CG PUSCH repetition in response to the configuration indicating a single SRI and the first number of TCI states indicating multiple TCI states.

[0107] In one or more specific implementations, in response to DCI being received on a first component carrier, the DCI indicating a scheduled physical downlink shared channel (PDSCH) on a second component carrier different from the first component carrier, the selected TCI state being associated with a non-serving cell, and a scheduling time offset between reception of the DCI and reception of the scheduled PDSCH being less than a time offset threshold, the UE may receive a medium access control (MAC) control element (MAC-CE) in a scheduled time slot of the scheduled PDSCH, the medium access control (MAC) control element (MAC-CE) indicating a plurality of TCI identifiers in a PDSCH TCI list activated by the MAC-CE, wherein the selected TCI state corresponds to a lowest TCI identifier of an active bandwidth part (BWP) for a second component carrier having the scheduled PDSCH among the plurality of TCI identifiers, and determine a quasi co-location (QCL) assumption for the scheduled PDSCH based on the selected TCI state.

[0108] Figure 7 700 is a flow chart illustrating an example configuration of a default beam for receiving information in accordance with various aspects of the present disclosure. At 702, the UE 104 determines whether a default beam selection for a cross-carrier scheduling parameter (e.g., a parameter named “enableDefaultBeamForCCS”) is received and / or configured to the UE 104. If the parameter is not received and / or configured, the UE may determine a scheduling offset between a DCI received on one CC and a PDSCH received on another CC, as shown in block 704.

[0109] If enableDefaultBeamForCCS is received and / or configured to the UE 104, then at block 708, the UE 104 determines whether there is an indicated DL TCI or an indicated joint TCI (for DL ​​and UL). If there is an indicated DL TCI or an indicated joint TCI for receiving the PDSCH, a quasi co-location (QCL) of the indicated DL TCI or the indicated joint TCI for the active BWP is applied by the UE 104 for reception of the PDSCH, as shown in block 710.

[0110] If there is no indicated DL TCI or indicated joint TCI as determined in block 708, at 712, the UE determines whether the scheduled time offset between the reception of the DCI and the reception of the scheduled PDSCH is less than a threshold. In one aspect of the present disclosure, the UE 104 may receive the DCI on the first CC and the scheduled PDSCH on the second CC. The determined scheduling time offset may be the minimum amount of time that the UE must wait between the reception of the DCI on the first CC and the reception of the PDSCH on the second CC. When the UE 104 is configured with enableDefaultBeamForCCS, the scheduling time offset between the last symbol of the PDCCH carrying the triggering DCI on one CC and the first symbol of the scheduled PDSCH on another CC may be less than a predetermined time offset (or threshold). If the scheduling time offset between the reception of the DCI and the reception of the scheduled PDSCH is less than a threshold, the UE 104 may apply the QCL assumption for the PDSCH from the activated TCI state with the lowest ID for the reception of the scheduled PDSCH, as shown in block 716.

[0111] If there is no indicated DL TCI or indicated joint TCI as determined in box 708, and the scheduled time offset between the reception of the DCI and the reception of the scheduled PDSCH as determined by box 712 is not less than the threshold, the UE 104 may apply the QCL assumption of the lowest CORESET identifier in the latest timeslot for reception of the PDSCH as applied at box 714; however, other TCI states may be used without departing from the scope of the present disclosure.

[0112] In one or more implementations, a scheduling offset less than a threshold corresponding to a QCL duration parameter (e.g., a "timeDurationForQCL" parameter) may trigger a configuration rule regardless of any configuration of a follow unified TCI state parameter (e.g., a "followUnifiedTCIstate" parameter). In some implementations of the configuration rule, if the indicated TCI is associated with a physical cell identity (PCI) that is different from the serving cell PCI (e.g., inter-cell), the UE may be configured to apply a default QCL assumption (e.g., the QCL assumption of the lowest CORESET ID in the latest timeslot) to both non-UE-specific PDSCH and UE-specific PDSCH. In some implementations of the configuration rule, if the QCL-TypeD characteristics of one or more default beams in timeslots of component carriers in a frequency band are different, the default beam of the component carrier with the lowest identifier (ID) is prioritized (e.g., the default beam of the component carrier with the lowest ID is applied to all component carriers in the frequency band). In one or more other specific implementations of the configuration rule, if the indicated TCI is associated with the serving cell PCI (e.g., intra-cell), the UE may use the indicated TCI for both UE-specific / non-UE-specific PDSCH (e.g., the UE does not consider the default QCL). In some aspects, the same approach may be applied to the default beam for aperiodic CSI-RS.

[0113] Therefore, the aforementioned configuration rule indicates that when the scheduling time offset between the DCI and its scheduled PDSCH is less than a threshold, and if the indicated TCI is associated with a non-serving cell, the UE may use the default beam as the beam of the lowest ID CORESET in the most recently monitored timeslot. Alternatively, if the indicated TCI is associated with a serving cell, the UE may use the default beam as the currently indicated TCI.

[0114] However, for cross-carrier scheduling, a DCI in a first component carrier denoted as CC1 may schedule a PDSCH in a second component carrier denoted as CC2, where CC2 does not have a configured CORESET. If the indicated TCI in CC2 is associated with a non-serving cell, the aforementioned configuration rules may not apply because CC2 is not configured with a CORESET.

[0115] In this example of a cross-carrier scheduling situation, the base station (or network entity) may generally schedule the PDSCH later than a threshold value. That is, the UE may not expect the network to schedule a PDSCH whose scheduling time offset is less than a threshold value.

[0116] In another example of such a cross-carrier scheduling case, if the indicated TCI is not associated with a serving cell, the default TCI may be the TCI state corresponding to the lowest TCI ID in the PDSCH TCI list activated by the MAC-CE in the scheduled PDSCH slot. In yet another example of such a cross-carrier scheduling case, the default beam may typically be the indicated TCI in the scheduled PDSCH slot.

[0117] When the UE is configured with enableDefaultBeamForCCS (see the Y port or branch of box 702) and is not indicated with a DLorJointTCIState for an active BWP for a component carrier with a scheduled PDSCH (see the N port or No branch of box 708), and if the scheduling time offset between the reception of the DL DCI and the reception of the corresponding PDSCH is less than a threshold as defined by the "timeDurationForQCL" parameter (see the Y port or branch of box 712), or if the DL DCI does not have a TCI field present (not shown), the UE may obtain its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID, which QCL assumption is applicable to the PDSCH in the active BWP of the scheduled cell (see box 716).

[0118] In some specific implementations, when the UE is configured with enableDefaultBeamForCCS and is indicated with a DLorJointTCIState of an active BWP for a component carrier with scheduled PDSCH, the UE does not expect the offset between the reception of the DL DCI and the reception of the corresponding PDSCH to be less than a threshold "timeDurationForQCL", nor does the DL DCI include a TCI field.

[0119] In some specific implementations, when the UE is configured with enableDefaultBeamForCCS and is indicated with a DLorJointTCIState of an active BWP for a component carrier with scheduled PDSCH, if the offset between the reception of the DL DCI and the reception of the corresponding PDSCH is less than a threshold timeDurationForQCL, or if the DL DCI does not have a TCI field present, the UE may derive its QCL assumption for the scheduled PDSCH based on the activated TCI of the lowest ID of the active BWP for the component carrier with the scheduled PDSCH.

[0120] When the UE is configured with enableDefaultBeamForCCS and is indicated with a DLorJointTCIState of an active BWP for a component carrier with scheduled PDSCH, if the scheduling time offset between the reception of the DL DCI and the reception of the corresponding PDSCH is less than the threshold "timeDurationForQCL", or if the DL DCI does not have the TCI field present, the UE may derive its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID, which QCL assumption is applicable to the PDSCH in the active BWP of the scheduled cell.

[0121] In some specific implementations, when the UE is configured with enableDefaultBeamForCCS and is indicated with a DLorJointTCIState of an active BWP for a component carrier with scheduled PDSCH, if the offset between the reception of the DL DCI and the reception of the corresponding PDSCH is less than a threshold timeDurationForQCL, or if the DL DCI does not have a TCI field present, the UE may obtain its QCL assumption for the scheduled PDSCH based on the indicated DLorJointTCIState of the active BWP for the component carrier with scheduled PDSCH.

[0122] In some embodiments, the UE may be configured to receive downlink data from one or more TRPs using multiple TCI states. The downlink data may include multiple MIMO layers that may be jointly pre-coded across multiple TCIs in a coherent joint transmission (CJT) manner. In some examples, the TCI state used for CJT operation may be a TCI state configured for a single frequency network (SFN) mode. In one example, the maximum number of TCI states for CJT may be up to a value defined by the UE capabilities or configured by the network at the UE (e.g., as an RRC parameter). In some aspects, in order to determine a pre-decoder for CJT, the base station may configure the UE to receive CSI-RS, derive a CSI report based on a predefined codebook, and transmit the CSI report based on the CSI-RS measurement. The predefined codebook may be based on an existing codebook defined in a legacy standard for non-CJT operation. In some aspects, the predefined codebook may be a type II codebook for CJT mTRP, which may be an extension of a codebook based on an enhanced type II conventional codebook, a further enhanced type II port selection (PS) codebook, or a codebook dedicated to CJT operation. The number of TRPs in the mTRP mode may include at least a number (NTRP) = [1, 2, 3, 4]. In some aspects, the UE may report its UE capabilities to the network based on which codebook(s) the UE supports to derive a CSI report for CJT operation.

[0123] Figure 8 800 is a diagram illustrating an example of a hardware implementation for an apparatus 802. The apparatus 802 is a UE and includes one or more cellular baseband processors 804 (also referred to as a modem) coupled to a cellular RF transceiver 822 and one or more subscriber identity modules (SIM) cards 820, an application processor 806 coupled to a secure digital (SD) card 808 and a screen 810, a Bluetooth module 812, a wireless local area network (WLAN) module 814, a global positioning system (GPS) module 816, and a power source 818. The one or more cellular baseband processors 804 communicate with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 822. The one or more cellular baseband processors 804 may each include a computer-readable medium / one or more memories. The computer-readable medium / one or more memories may be non-transitory. The one or more cellular baseband processors 804 are responsible for general processing, including executing software stored on the computer-readable medium / one or more memories, either alone or in combination. The software, when executed by one or more cellular baseband processors 804, causes the one or more cellular baseband processors 804 to perform the various functions described above, either alone or in combination. The computer-readable medium / one or more memories may also be used, either alone or in combination, to store data manipulated by the one or more cellular baseband processors 804 when executing the software. The one or more cellular baseband processors 804 also include, either alone or in combination, a receiving component 830, a communication manager 832, and a sending component 834. The communication manager 832 includes one or more illustrated components. The components within the communication manager 832 may be stored in a computer-readable medium / one or more memories and / or configured as hardware within the one or more cellular baseband processors 804. The one or more cellular baseband processors 804 may be a component of the UE 350 and may include, either alone or in combination, one or more memories 360 and / or at least one TX processor of the one or more TX processors 368, at least one RX processor of the one or more RX processors 356, and at least one controller / processor of the one or more controllers / processors 359. In one configuration, the apparatus 802 may be a modem chip and include only one or more baseband processors 804, and in another configuration, the apparatus 802 may be an entire UE (e.g., see Figure 3 350) and includes the above-mentioned additional modules of device 802.

[0124] The communication manager 832 includes a DL / TCI receiving component 840 that receives input in the form of DL / TCI information and is configured to receive downlink control information (DCI) including a first number of DL / TCI information indicating TCI states from a network entity via the receiving component 830 (e.g., as described in conjunction with 602), and receive a second number of downlink information indicating TCI states before receiving the DCI (e.g., as described in conjunction with 603). The communication manager 832 includes a TRP mode dynamic switching detection component 842 that is configured to detect dynamic switching between a multiple transmit receive point (mTRP) mode and a single TRP (sTRP) mode in the UE based on the first number of TCI states being different from the second number of TCI states (e.g., as described in conjunction with 604). The communication manager 832 also includes a communication component 844 that is configured to communicate with a network entity in one or more channels configured to use selected TCI states associated with a first number of TCI states using one or more predefined rules based on switching between the mTRP mode and the sTRP mode (e.g., as described in conjunction with 606).

[0125] The device may include executing Figure 6 and Figure 7 Each of the boxes in the algorithm in the preceding flowchart is an additional component. Therefore, Figure 6 and Figure 7 Each block in the foregoing flow chart of can be performed by a component, and the apparatus may include one or more of those components. These components may be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors that are configured to perform the stated process / algorithm alone or in combination, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above.

[0126] In one configuration, the device 802 (and in particular one or more cellular baseband processors 804) includes a component for receiving a first number of downlink control information (DCI) indicating a transmission configuration indication (TCI) state from a network entity. The device 802 also includes a component for detecting a switch between a multi-transmission reception point (mTRP) mode and a single TRP (sTRP) mode in a UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE. The device 802 also includes a component for using one or more predefined rules based on the switch between the mTRP mode and the sTRP mode to communicate with the network entity in one or more channels configured to use a selected TCI state associated with the first number of TCI states. The aforementioned components may be one or more of the aforementioned components of the device 802 configured to perform the functions recorded by the aforementioned components. As described above, the device 802 may include one or more TX processors 368, one or more RX processors 356, and one or more controllers / processors 359. Thus, in one configuration, the aforementioned components may be at least one of the one or more TX processors 368, at least one of the one or more RX processors 356, or at least one of the one or more controllers / processors 359, which are configured alone or in any combination to perform the functions recited by the aforementioned components.

[0127] The following embodiments are merely illustrative and may be combined with other aspects or aspects of the teachings described herein, but are not limited thereto.

[0128] Clause 1. A device for wireless communication at a user equipment (UE), the device comprising: one or more memories; and one or more processors, each of the one or more processors being communicatively coupled to at least one of the one or more memories, the one or more processors being capable of operating individually or in any combination to cause the device to: receive a first number of downlink control information (DCI) indicating a transmit configuration indication (TCI) state from a network entity; detect a switch between a multiple transmit receive point (mTRP) mode and a single TRP (sTRP) mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; and communicate with the network entity in one or more channels configured to use a selected TCI state associated with the first number of TCI states using one or more predefined rules based on the switch between the mTRP mode and the sTRP mode.

[0129] Clause 2. An apparatus according to Clause 1, wherein the first number of TCI states includes a single TCI state in the sTRP mode of the UE and multiple TCI states in the mTRP mode of the UE.

[0130] Clause 3. An apparatus according to clause 1 or 2, wherein the one or more channels include a physical downlink control channel (PDCCH) associated with a control resource set (CORESET) preconfigured to use the second number of TCI states, and the one or more predefined rules indicate that the CORESET is configured to switch the associated TCI state from a TCI state associated with the second number of TCI states to the selected TCI state associated with the first number of TCI states based on the switching between the mTRP mode and the sTRP mode.

[0131] Clause 4. An apparatus according to Clause 3, wherein the first number of TCI states indicated in the DCI is greater than the second number of TCI states, and the one or more processors are capable of further operating, individually or in combination, to enable the apparatus to detect the switch from the sTRP mode to the mTRP mode based on the second number of TCI states being less than the first number of TCI states.

[0132] Clause 5. An apparatus according to Clause 4, wherein the one or more predefined rules further indicate that the CORESET is configured to use the selected TCI state corresponding to the smallest TRP identifier among the TRP identifiers associated with the first number of TCI states.

[0133] Clause 6. An apparatus as described in clause 4 or clause 5, wherein the one or more predefined rules further indicate that the CORESET is configured to use the selected TCI state corresponding to the CORESET pool identifier in response to a CORESET pool identifier being configured for the CORESET.

[0134] Clause 7. An apparatus according to Clause 3, wherein the first number of TCI states indicated in the DCI is less than the second number of TCI states, and the one or more processors are capable of further operating, individually or in combination, to enable the apparatus to detect the switch from the mTRP mode to the sTRP mode based on the second number of TCI states being greater than the first number of TCI states.

[0135] Clause 8. An apparatus according to clause 7, wherein the one or more predefined rules further indicate that the CORESET is configured to become disabled after the application time of the selected TCI state until the next downlink control signaling indicates another switch between the mTRP mode and the sTRP mode in the UE.

[0136] Clause 9. An apparatus as described in clause 7 or clause 8, wherein the one or more predefined rules further indicate that the CORESET is configured to use the selected TCI state that is active for the UE from the first number of TCI states.

[0137] Clause 10. An apparatus according to any one of clauses 1 to 9, wherein the one or more channels include a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) or a configuration grant (CG) physical uplink shared channel (PUSCH) pre-configured to use the second number of TCI states, and the one or more predefined rules indicate that the SPS PDSCH or the CG PUSCH is configured to switch the associated TCI state from the TCI state associated with the second number of TCI states to the selected TCI state associated with the first number of TCI states based on the switching between the mTRP mode and the sTRP mode.

[0138] Clause 11. An apparatus according to clause 10, wherein the first number of TCI states indicated in the DCI is greater than the second number of TCI states, and the one or more processors are capable of further operating, individually or in combination, to enable the apparatus to detect the switch from the sTRP mode to the mTRP mode based on the second number of TCI states being less than the first number of TCI states.

[0139] Clause 12. An apparatus according to clause 11, wherein the one or more predefined rules further indicate that the SPS PDSCH is configured to use the selected TCI state corresponding to the control resource set (CORESET) pool identifier in response to configuring the CORESET pool identifier associated with the DCI that activates the SPS PDSCH.

[0140] Clause 13. An apparatus according to clause 11 or clause 12, wherein the one or more predefined rules further indicate that the SPS PDSCH is configured to use the selected TCI state corresponding to the minimum TRP identifier among the TRP identifiers associated with the first number of TCI states.

[0141] Clause 14. An apparatus according to any one of clauses 11 to 13, wherein the one or more predefined rules further indicate that the SPS PDSCH is configured to use the selected TCI state corresponding to the minimum TCI identifier of the TCI associated with the first number of TCI states in response to the DCI indicating TCI from the same control resource set (CORESET) pool associated with the first number of TCI states.

[0142] Clause 15. An apparatus according to clause 10, wherein the first number of TCI states indicated in the DCI is less than the second number of TCI states, and the one or more processors are capable of further operating, individually or in combination, to enable the apparatus to detect the switch from the mTRP mode to the sTRP mode based on the second number of TCI states being greater than the first number of TCI states.

[0143] Clause 16. An apparatus according to clause 15, wherein the one or more predefined rules further indicate that the SPS PDSCH or the CG PUSCH is configured to become disabled after the application time of the selected TCI state in response to the SPS PDSCH or the CG PUSCH being configured for spatial division multiplexing (SDM) and the first number of TCI states indicated in the DCI being less than the number of data layers of the UE, until the next downlink control signaling indicates another switch between the mTRP mode and the sTRP mode in the UE.

[0144] Clause 17. An apparatus according to clause 15 or 16, wherein the one or more predefined rules further indicate that the SPS PDSCH or the CG PUSCH is configured to use the selected TCI state associated with the first number of TCI states in response to the SPS PDSCH or the CG PUSCH being configured for time division multiplexing (TDM) or frequency division multiplexing (FDM).

[0145] Clause 18. An apparatus as described in any of clauses 15 to 17, wherein the one or more predefined rules further indicate that the SPS PDSCH is configured to use a TCI state associated with the second number of TCI states.

[0146] Clause 19. An apparatus according to any one of clauses 10 to 18, wherein the one or more processors are capable of further operating, individually or in combination, to cause the apparatus to receive a configuration indicating one or more sounding reference signal (SRS) resource indicators (SRIs) from the network entity, the one or more SRIs notifying the UE that the selected TCI state is applied to the type 1 CG PUSCH repetition in the CG PUSCH.

[0147] Clause 20. An apparatus according to clause 19, wherein the selected TCI state associated with the first number of TCI states is applied to the type 1CG PUSCH repetition associated with an SRS resource set in response to the configuration indicating multiple SRIs and the first number of TCI states indicating multiple TCI states.

[0148] Clause 21. An apparatus according to clause 19 or 20, wherein the selected TCI state associated with the first number of TCI states is applied to the type 1 CG PUSCH repetition in response to the configuration indicating a single SRI and the first number of TCI states indicating multiple TCI states.

[0149] Clause 22. An apparatus according to any one of clauses 1 to 21, wherein the one or more processors are capable of further operating, individually or in combination, to cause the apparatus to: receive a medium access control (MAC) control element (MAC-CE) in a scheduled time slot of the scheduled PDSCH, the medium access control (MAC-CE) indicating a plurality of TCI identifiers in a PDSCH TCI list activated by the MAC-CE, in response to the DCI being received on a first component carrier, the DCI indicating a scheduled physical downlink shared channel (PDSCH) on a second component carrier different from the first component carrier, the selected TCI state being associated with a non-serving cell, and a scheduling time offset between reception of the DCI and reception of the scheduled PDSCH being less than a time offset threshold, wherein the selected TCI state corresponds to a lowest TCI identifier among the plurality of TCI identifiers for an active bandwidth part (BWP) of the second component carrier having the scheduled PDSCH, and determine a quasi co-location (QCL) assumption for the scheduled PDSCH based on the selected TCI state.

[0150] Clause 23. An apparatus according to any one of clauses 1 to 22, wherein the one or more processors are capable of further operating, individually or in combination, to cause the apparatus to receive a configuration from the network entity to configure the UE to report channel state information (CSI) based on a type II codebook for coherent joint transmission (CJT) in the mTRP mode.

[0151] Clause 24. An apparatus according to clause 23, wherein the one or more processors are capable of further operating, individually or in combination, to cause the apparatus to send UE capability information to the network entity indicating CSI reporting supporting CJT operation based on the type II codebook used for CJT in the mTRP mode.

[0152] Clause 25. An apparatus according to clause 23 or 24, wherein the type II codebook used for CJT in the mTRP mode is an extension based on one or more of an enhanced type II conventional codebook, a further enhanced type II port selection codebook, or a codebook dedicated to CJT operation.

[0153] Clause 26. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: a component for receiving a first number of downlink control information (DCI) indicating a transmit configuration indication (TCI) state from a network entity; a component for detecting a switch between a multiple transmit receive point (mTRP) mode and a single TRP (sTRP) mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; and a component for communicating with the network entity in one or more channels configured to use the selected TCI state associated with the first number of TCI states using one or more predefined rules based on the switch between the mTRP mode and the sTRP mode.

[0154] Clause 27. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a first number of downlink control information (DCI) indicating a transmit configuration indication (TCI) state from a network entity; detecting a switch between a multiple transmit receive point (mTRP) mode and a single TRP (sTRP) mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; and communicating with the network entity in one or more channels configured to use a selected TCI state associated with the first number of TCI states using one or more predefined rules based on the switch between the mTRP mode and the sTRP mode.

[0155] Clause 28. A method according to clause 27, wherein the one or more channels include a physical downlink control channel (PDCCH) associated with a control resource set (CORESET) pre-configured to use the second number of TCI states, and the one or more predefined rules indicate that the CORESET is configured to switch the associated TCI state from a TCI state associated with the second number of TCI states to the selected TCI state associated with the first number of TCI states based on the switching between the mTRP mode and the sTRP mode.

[0156] Clause 29. A method according to clause 27 or 28, wherein the one or more channels include a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) or a configuration grant (CG) physical uplink shared channel (PUSCH) pre-configured to use the second number of TCI states, and the one or more predefined rules indicate that the SPS PDSCH or the CG PUSCH is configured to switch the associated TCI state from the TCI state associated with the second number of TCI states to the selected TCI state associated with the first number of TCI states based on the switching between the mTRP mode and the sTRP mode.

[0157] Clause 30. A non-transitory computer-readable medium comprising computer executable code that, when executed by one or more processors of a user equipment (UE), causes the one or more processors to, individually or in combination: receive downlink control information (DCI) indicating a first number of transmit configuration indication (TCI) states from a network entity; detect a switch between a multiple transmit receive point (mTRP) mode and a single TRP (sTRP) mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; and communicate with the network entity in one or more channels configured to use a selected TCI state associated with the first number of TCI states using one or more predefined rules based on the switch between the mTRP mode and the sTRP mode.

[0158] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily understood by those of ordinary skill in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language. Therefore, the language used herein is not intended to limit the scope of the claims to only those aspects shown herein, but should be given the full scope consistent with the language of the claims.

[0159] As an example, the language "determine" may encompass a wide variety of actions, and thus may not be limited to the concepts and aspects explicitly described or illustrated by the present disclosure. In some contexts, "determine" may include calculating, computing, processing, measuring, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, resolving, selecting, choosing, establishing, and the like. In some other contexts, "determining" may include some communication and / or memory operations / procedures by which some information or value is obtained, such as "receiving" (e.g., receiving information), "accessing" (e.g., accessing data in a memory), "detecting," and the like.

[0160] As another example, reference to a singular element is not intended to mean "there is and only one" (unless specifically so stated), but "one or more". Specifically, reference to a singular element is not intended to mean "there is and only one" (unless specifically so stated), but "one or more". Terms such as "if", "when..." and "while..." should be interpreted as "under the condition of...", rather than meaning an immediate time relationship or reaction. That is, these phrases, such as "when...", do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the condition is met, the action will occur, but no specific or immediate time limit is required for the action to occur. The word "exemplary" is used in this article to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," "device," etc. cannot replace the word "component." Thus, no claim element will be construed as part-plus-function unless the element is explicitly recited using the phrase "component for..."

[0161] As used herein, a processor, at least one processor, and / or one or more processors that are configured to perform or are operable to perform multiple actions (such as the functions described above), either individually or in combination, is intended to include at least two different processors capable of performing different subsets, overlapping subsets, or non-overlapping subsets of the multiple actions, or a single processor capable of performing all of the multiple actions. In a non-limiting example of multiple processors capable of performing different actions combined in the multiple actions, a description of a processor, at least one processor, and / or one or more processors that are configured or are operable to perform actions X, Y, and Z may include at least a first processor that is configured or is operable to perform a first subset of X, Y, and Z (e.g., perform X) and at least a second processor that is configured or is operable to perform a second subset of X, Y, and Z (e.g., perform Y and Z). Alternatively, the first processor, the second processor, and the third processor may be configured or operable to perform corresponding actions in actions X, Y, and Z, respectively. It should be understood that any combination of one or more processors may each be configured or operable to perform any one of the multiple actions or any combination of the multiple actions.

[0162] Similarly, as used herein, a memory, at least one memory, a computer-readable medium, and / or one or more memories configured, alone or in combination, to store or have stored thereon instructions for performing multiple actions (such as the functions described above) that are executable by one or more processors are intended to include at least two different memories capable of storing different subsets, overlapping subsets, or non-overlapping subsets of instructions for performing different subsets, overlapping subsets, or non-overlapping subsets of the multiple actions, or a single memory capable of storing instructions for performing all of the multiple actions. In one non-limiting example of one or more memories (alone or in combination) capable of storing different subsets of instructions for performing different ones of the plurality of actions, a description of a memory, at least one memory, a computer-readable medium, and / or one or more memories configured or operable to store or have stored thereon instructions for performing actions X, Y, and Z may include at least a first memory configured or operable to store or have stored thereon a first subset of instructions for performing a first subset of X, Y, and Z (e.g., instructions to perform X), and at least a second memory configured or operable to store or have stored thereon a second subset of instructions for performing a second subset of X, Y, and Z (e.g., instructions to perform Y and Z). Alternatively, the first memory, the second memory, and the third memory may be configured or operable to store or have stored thereon a respective one of the first subset of instructions for performing X, the second subset of instructions for performing Y, and the third subset of instructions for performing Z, respectively. It should be understood that any combination of one or more memories may each be configured or operable to store or have stored thereon any instruction or any combination of instructions that can be executed by one or more processors to perform any of a plurality of actions or any combination of the plurality of actions. In addition, one or more processors may each be coupled to at least one of the one or more memories and configured or operable to execute instructions to perform the plurality of actions. For example, in the above non-limiting example of different instruction subsets for performing actions X, Y, and Z, a first processor may be coupled to a first memory storing instructions for performing action X, at least a second processor may be coupled to at least a second memory storing instructions for performing actions Y and Z, and the first processor and the second processor may execute the corresponding instruction subsets in combination to complete the execution of actions X, Y, and Z. Alternatively, three processors may access one of three different memories, each of which stores instructions for performing actions X, Y, or Z, and the three processors may execute the corresponding instruction subsets in combination to complete the execution of actions X, Y, and Z. Alternatively, a single processor may execute instructions stored on a single memory or distributed on multiple memories to complete the execution of actions X, Y, and Z.

[0163] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not meant to be limited to the specific order or hierarchy provided.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories; and one or more processors, each of the one or more processors being communicatively coupled to at least one of the one or more memories, the one or more processors being operable, alone or in any combination, to cause the apparatus to: receiving a first amount of downlink control information (DCI) indicating a transmit configuration indication (TCI) status from a network entity; detecting a switch between a multiple transmit receive point (mTRP) mode and a single TRP (sTRP) mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; as well as Based on the switching between the mTRP mode and the sTRP mode, one or more predefined rules are used to communicate with the network entity in one or more channels configured to use selected TCI states associated with the first number of TCI states.

2. The apparatus of claim 1, wherein the first number of TCI states includes a single TCI state in the sTRP mode of the UE and multiple TCI states in the mTRP mode of the UE.

3. An apparatus according to claim 1, wherein the one or more channels include a physical downlink control channel (PDCCH) associated with a control resource set (CORESET) pre-configured to use the second number of TCI states, and the one or more predefined rules indicate that the CORESET is configured to switch the associated TCI state from the TCI state associated with the second number of TCI states to the selected TCI state associated with the first number of TCI states based on the switching between the mTRP mode and the sTRP mode.

4. An apparatus according to claim 3, wherein the first number of TCI states indicated in the DCI is greater than the second number of TCI states, and the one or more processors are capable of further operating individually or in combination to enable the apparatus to detect the switch from the sTRP mode to the mTRP mode based on the second number of TCI states being less than the first number of TCI states.

5. The apparatus of claim 4, wherein the one or more predefined rules further indicate that the CORESET is configured to use the selected TCI state corresponding to a minimum TRP identifier among the TRP identifiers associated with the first number of TCI states.

6. The apparatus of claim 4, wherein the one or more predefined rules further indicate that the CORESET is configured to use the selected TCI state corresponding to the CORESET pool identifier in response to a CORESET pool identifier being configured for the CORESET.

7. An apparatus according to claim 3, wherein the first number of TCI states indicated in the DCI is less than the second number of TCI states, and the one or more processors are capable of further operating individually or in combination to enable the apparatus to detect the switch from the mTRP mode to the sTRP mode based on the second number of TCI states being greater than the first number of TCI states.

8. The apparatus of claim 7, wherein the one or more predefined rules further indicate that the CORESET is configured to become disabled after the application time of the selected TCI state until a next downlink control signaling indicates another switch between the mTRP mode and the sTRP mode in the UE.

9. The apparatus of claim 7, wherein the one or more predefined rules further indicate that the CORESET is configured to use the selected TCI state that is active for the UE from the first number of TCI states.

10. An apparatus according to claim 1, wherein the one or more channels include a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) or a configuration grant (CG) physical uplink shared channel (PUSCH) pre-configured to use the second number of TCI states, and the one or more predefined rules indicate that the SPS PDSCH or the CG PUSCH is configured to switch the associated TCI state from the TCI state associated with the second number of TCI states to the selected TCI state associated with the first number of TCI states based on the switching between the mTRP mode and the sTRP mode.

11. An apparatus according to claim 10, wherein the first number of TCI states indicated in the DCI is greater than the second number of TCI states, and the one or more processors are capable of further operating individually or in combination to enable the apparatus to detect the switch from the sTRP mode to the mTRP mode based on the second number of TCI states being less than the first number of TCI states.

12. The apparatus of claim 11, wherein the one or more predefined rules further indicate that the SPS PDSCH is configured to use the selected TCI state corresponding to a control resource set (CORESET) pool identifier in response to configuring a CORESET pool identifier associated with the DCI that activates the SPS PDSCH.

13. The apparatus of claim 11, wherein the one or more predefined rules further indicate that the SPS PDSCH is configured to use the selected TCI state corresponding to a minimum TRP identifier among the TRP identifiers associated with the first number of TCI states.

14. An apparatus according to claim 11, wherein the one or more predefined rules further indicate that the SPS PDSCH is configured to use the selected TCI state corresponding to the minimum TCI identifier of the TCI associated with the first number of TCI states in response to the DCI indicating TCI from the same control resource set (CORESET) pool associated with the first number of TCI states.

15. An apparatus according to claim 10, wherein the first number of TCI states indicated in the DCI is less than the second number of TCI states, and the one or more processors are capable of further operating individually or in combination to enable the apparatus to detect the switch from the mTRP mode to the sTRP mode based on the second number of TCI states being greater than the first number of TCI states.

16. An apparatus according to claim 15, wherein the one or more predefined rules further indicate that the SPS PDSCH or the CG PUSCH is configured to become disabled after the application time of the selected TCI state in response to the SPS PDSCH or the CG PUSCH being configured for spatial division multiplexing (SDM) and the first number of TCI states indicated in the DCI being less than the number of data layers of the UE, until the next downlink control signaling indicates another switch between the mTRP mode and the sTRP mode in the UE.

17. An apparatus according to claim 15, wherein the one or more predefined rules further indicate that the SPS PDSCH or the CG PUSCH is configured to use the selected TCI state associated with the first number of TCI states that are active for the UE in response to the SPS PDSCH or the CG PUSCH being configured for time division multiplexing (TDM) or frequency division multiplexing (FDM).

18. The apparatus of claim 15, wherein the one or more predefined rules further indicate that the SPS PDSCH is configured to use a TCI state associated with the second number of TCI states preconfigured for the UE.

19. An apparatus according to claim 10, wherein the one or more processors are capable of further operating individually or in combination to cause the apparatus to receive a configuration indicating one or more sounding reference signal (SRS) resource indicators (SRIs) from the network entity, and the one or more SRIs notify the UE that the selected TCI state is applied to the type 1CG PUSCH repetition in the CGPUSCH.

20. The apparatus of claim 19, wherein the selected TCI state associated with the first number of TCI states is responsive to the configuration indicating multiple SRIs and the first number of TCI states indicating multiple TCI states to be applied to the type 1CG PUSCH repetition associated with an SRS resource set.

21. The apparatus of claim 19, wherein the selected TCI state associated with the first number of TCI states is applied to the Type 1 CG PUSCH repetition in response to the configuration indicating a single SRI and the first number of TCI states indicating multiple TCI states.

22. The apparatus of claim 1, wherein the one or more processors, individually or in combination, are further operable to cause the apparatus to: in response to the DCI being received on a first component carrier, the DCI indicating a scheduled physical downlink shared channel (PDSCH) on a second component carrier different from the first component carrier, the selected TCI state being associated with a non-serving cell, and a scheduled time offset between reception of the DCI and reception of the scheduled PDSCH being less than a time offset threshold: receiving a medium access control (MAC) control element (MAC-CE) in a scheduled time slot of the scheduled PDSCH, the medium access control (MAC) control element (MAC-CE) indicating a plurality of TCI identifiers in a PDSCH TCI list activated by the MAC-CE, wherein the selected TCI state corresponds to a lowest TCI identifier of the plurality of TCI identifiers for an active bandwidth part (BWP) of the second component carrier having the scheduled PDSCH, and A quasi co-location (QCL) assumption for the scheduled PDSCH is determined based on the selected TCI state.

23. An apparatus according to claim 1, wherein the one or more processors are capable of further operating individually or in combination to cause the apparatus to receive a configuration from the network entity to configure the UE to report channel state information (CSI) based on a type II codebook for coherent joint transmission (CJT) in the mTRP mode.

24. An apparatus according to claim 23, wherein the one or more processors are capable of further operating individually or in combination to cause the apparatus to send UE capability information to the network entity indicating CSI reporting supporting CJT operation based on the type II codebook used for CJT in the mTRP mode.

25. The apparatus of claim 23, wherein the type II codebook for CJT in the mTRP mode is an extension based on one or more of an enhanced type II conventional codebook, a further enhanced type II port selection codebook, or a codebook dedicated to CJT operation.

26. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: means for receiving, from a network entity, a first amount of downlink control information (DCI) indicating a transmit configuration indication (TCI) status; means for detecting a switch between a multiple transmit receive point (mTRP) mode and a single TRP (sTRP) mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; and A component for communicating with the network entity in one or more channels configured to use the selected TCI states associated with the first number of TCI states using one or more predefined rules based on the switching between the mTRP mode and the sTRP mode.

27. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a first amount of downlink control information (DCI) indicating a transmit configuration indication (TCI) status from a network entity; detecting a switch between a multiple transmit receive point (mTRP) mode and a single TRP (sTRP) mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; as well as Based on the switching between the mTRP mode and the sTRP mode, one or more predefined rules are used to communicate with the network entity in one or more channels configured to use selected TCI states associated with the first number of TCI states.

28. A method according to claim 27, wherein the one or more channels include a physical downlink control channel (PDCCH) associated with a control resource set (CORESET) pre-configured to use the second number of TCI states, and the one or more predefined rules indicate that the CORESET is configured to switch the associated TCI state from the TCI state associated with the second number of TCI states to the selected TCI state associated with the first number of TCI states based on the switching between the mTRP mode and the sTRP mode.

29. A method according to claim 27, wherein the one or more channels include a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) or a configuration grant (CG) physical uplink shared channel (PUSCH) pre-configured to use the second number of TCI states, and the one or more predefined rules indicate that the SPS PDSCH or the CG PUSCH is configured to switch the associated TCI state from the TCI state associated with the second number of TCI states to the selected TCI state associated with the first number of TCI states based on the switching between the mTRP mode and the sTRP mode.

30. A non-transitory computer readable medium comprising computer executable code that, when executed by one or more processors of a user equipment (UE), causes the one or more processors to, individually or in combination: receiving a first amount of downlink control information (DCI) indicating a transmit configuration indication (TCI) status from a network entity; detecting a switch between a multiple transmit reception point (mTRP) mode and a single TRP (sTRP) mode in the UE based on the first number of TCI states being different from a second number of TCI states previously received by the UE; and Based on the switching between the mTRP mode and the sTRP mode, one or more predefined rules are used to communicate with the network entity in one or more channels configured to use selected TCI states associated with the first number of TCI states.

Images