Dynamic single TRP handover in multi-TRP operations

Abstract

A network entity may communicate at least one first transmission with a user equipment (UE) via a multiple transmit receive point (TRP) (mTRP) via a first TRP and a second TRP. The network entity may send an indication to the UE to switch to a single TRP (sTRP) mode, or a condition of the UE, such as a configuration specification, may provide the indication to switch to the sTRP mode. The UE may obtain the indication of switching to the sTRP mode from the network entity or from the condition. The UE may switch to communicate at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode based on the indication of switching to the sTRP mode.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to systems having multiple transmit receive points (mTRPs). Background Art

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

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, national, regional, and even global levels. 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. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary 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.

[0005] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may have a memory and at least one processor coupled to the memory UE. Based at least in part on the information stored in the memory, the at least one processor may be configured to communicate at least one first transmission with a network node via a first TRP and a second TRP in a multiple transmit receive point (TRP) (mTRP) mode. Based at least in part on the information stored in the memory, the at least one processor may be configured to obtain an indication of switching to a single TRP (sTRP) mode. Based at least in part on the information stored in the memory, the at least one processor may be configured to switch to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode based on the indication of switching to the sTRP mode.

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may have a memory and at least one processor coupled to the memory network node. Based at least in part on information stored in the memory, the at least one processor may be configured to communicate at least one first transmission with a user equipment (UE) via a first TRP and a second TRP in a multiple transmit receive point (TRP) (mTRP) mode. Based at least in part on information stored in the memory, the at least one processor may be configured to send an indication to the UE to switch to a single TRP (sTRP) mode. Based at least in part on information stored in the memory, the at least one processor may be configured to switch to communicating at least one second transmission with the UE via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode.

[0007] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0012] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to aspects of the present disclosure.

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

[0014] Figure 4 is a diagram showing a UE configured to communicate with multiple TRPs in a cell group.

[0015] Figure 5A is a diagram illustrating an example of mTRP resource configuration according to various aspects of the present disclosure.

[0016] Figure 5B is a diagram illustrating an example of mTRP resource configuration according to various aspects of the present disclosure.

[0017] Figure 5C is a diagram illustrating an example of mTRP resource configuration according to various aspects of the present disclosure.

[0018] Figure 5D is a diagram illustrating an example of mTRP resource configuration according to various aspects of the present disclosure.

[0019] Figure 5E is a diagram illustrating an example of mTRP resource configuration according to various aspects of the present disclosure.

[0020] Fig. 5F is a diagram illustrating an example of mTRP resource configuration according to various aspects of the present disclosure.

[0021] Figure 6 is a diagram illustrating an example of scheduling DCI according to various aspects of the present disclosure.

[0022] Figure 7 is a connection flow diagram illustrating a UE being configured to communicate with multiple TRPs in a cell group.

[0023] Figure 8 is a connection flow diagram illustrating a UE being configured to communicate with multiple TRPs in a cell group.

[0024] Fig. 9 is a connection flow diagram illustrating a UE being configured to communicate with multiple TRPs in a cell group.

[0025] Fig.10 A flow chart of a wireless communication method.

[0026] Fig.11A flow chart of a wireless communication method.

[0027] Fig.12 A flow chart of a wireless communication method.

[0028] Fig.13 A flow chart of a wireless communication method.

[0029] Fig.14 A flow chart of a wireless communication method.

[0030] Fig.15 A flow chart of a wireless communication method.

[0031] Fig.16 A flow chart of a wireless communication method.

[0032] Fig.17 A flow chart of a wireless communication method.

[0033] Fig.18 A flow chart of a wireless communication method.

[0034] Fig.19 are diagrams illustrating examples of hardware implementations of example devices and / or network entities.

[0035] Fig. 20 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0036] Fig.21 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0037] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not 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, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0038] Several aspects of the telecommunication system are also presented with reference to various apparatus and methods. These apparatus and methods are 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.

[0039] 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, gate 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 referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, functions, or any combination thereof.

[0040] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, 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, combinations of these types of computer-readable media, or any other media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0041] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user equipment, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may be specifically for use cases or applications, or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some practical environments, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0042] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP), or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0043] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0044] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0045] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0046] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces 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 configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0047] In some aspects, CU 110 may host one or more 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 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 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 110 may be implemented to communicate with DU 130 for network control and signaling.

[0048] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 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.) depending at least in part on a functional split such as that defined by 3GPP. In some aspects, DU 130 may also 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 130 or with control functions hosted by CU 110.

[0049] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 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 splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0050] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 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 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) 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 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

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

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

[0053] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Thus, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102, or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. 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). Small cells include femto cells, pico cells, and micro cells. 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). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmission diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The 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 ​​compared to 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).

[0054] 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 wireless wide area network (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). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

[0056] 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). Although a portion of FR1 is greater than 6 GHz, FR1 is often (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 often (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).

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

[0058] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used in this document, it can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used in this document, it can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2 and / or FR5, or may be within the EHF band.

[0059] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0060] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include disaggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0061] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the positioning determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement results and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the positioning of the UE 104. The NG-RAN may determine the positioning of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0062] Examples of UE 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, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, 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 stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.

[0063] Reference again Figure 1 In some aspects, the UE 104 may have a TRP communication component 198 configured to communicate at least one first transmission with a network node via a first TRP and a second TRP in mTRP mode. The TRP communication component 198 may be configured to obtain an indication of switching to sTRP mode. The TRP communication component 198 may be configured to switch to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in sTRP mode based on the indication of switching to sTRP mode. In some aspects, the base station 102 may have a TRP configuration component 199 configured to communicate at least one first transmission with the UE via the first TRP and the second TRP in mTRP mode. The TRP configuration component 199 may be configured to send an indication of switching to sTRP mode to the UE. The TRP configuration component 199 may be configured to switch to communicating at least one second transmission with the UE via one of the first TRP or the second TRP in sTRP mode based on the indication of switching to sTRP mode. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0064] 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 UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are 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 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0065] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of the same size (1ms). 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 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For a conventional CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a 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-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0066]

[0067] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 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 may have a specific parameter set and CP (normal or extended).

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

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

[0070] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the 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 system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0071] like Figure 2C As 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 one or 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 teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0072] Figure 2DExamples 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 indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0073] Figure 3 370 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements 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. The controller / processor 375 provides 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.

[0074] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (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 decoded and modulated symbols can then be divided into parallel streams. Subsequently, each stream can be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain 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 pre-coded to generate multiple 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 state 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 a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0075] 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 a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 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 merged into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). 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 the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0076] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0077] Similar to the functions described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides 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.

[0078] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via corresponding transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0079] 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 the RX processor 370.

[0080] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0081] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Various aspects related to the triggered TRP communication component 198.

[0082] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The TRP configuration component 199 combines various aspects.

[0083] The network node may be configured to communicate with the UE via one or more TRPs in a cell or zone. Figure 4 Diagram 400 shows a UE 402 configured to communicate with a network node 406. The network node 406 may be a single network entity, multiple network entities (multiple network entities controlling a set of TRPs), or multiple different network entities (each controlling a different TRP) in network communication with each other, such as via a backhaul connection. The network node 406 may be, for example Figure 1 406 may be in network communication with TRP 410 or TRP 412, such as via a backhaul connection. TRP 410 or TRP 412 may each include a transceiver configured to communicate with a public UE, such as UE 402. Each of TRP 410 or TRP 412 may be, for example, Figure 1 404. The RU 140 in the cell group 404 or the panel of the base station 102 can be a TRP 410 and a TRP 412. TRP 410 and TRP 412 can form a cell group 404. Each of TRP 410 and TRP 412 can be controlled and operated by a network node 406. Although the cell group 404 is shown as having two TRPs, in other aspects, the cell group can have more or fewer TRPs. TRP 410 and TRP 412 can each be designated as part of the same quasi-co-location (QCL) group. Each of TRP 410 and TRP 412 can be active at the same time, thereby providing maximum throughput when the load is high.

[0084] UE 402 may be configured to communicate with TRP 410 via communication link 420. UE 402 may be configured to communicate with TRP 412 via communication link 422. The communication link may be a frame structure such as Figures 2A to 2D The network node 406 may allocate TRP resources 430 to the communication link 420 between the TRP 410 and the UE 402. The TRP resources 430 may be defined as a set of RBs and a set of symbols. The network node may allocate TRP resources 432 to the communication link 422 between the TRP 412 and the UE 402. The TRP resources 432 may be defined as a set of RBs and a set of symbols.

[0085] UE 402 may be configured to communicate with network node 406 via TRP 410 and TRP 412 using any suitable channel. For example, UE 402 may be configured to communicate with network node 406 via TRP 410 and TRP 412 using PDCCH, PDSCH, PUSCH, and / or PUCCH. In the case where UE 402 communicates via both TRP 410 and TRP 412, communication between UE 402 and network node 406 may have increased throughput compared to the case where UE 402 communicates via one of TRP 410 or TRP 412. In some aspects, it may be advantageous for UE 402 to communicate with network node 406 via one of TRP 410 or TRP 412, for example, to increase signal-to-noise ratio (SNR) or reduce power consumption. In some aspects, the network node 406 may be configured to switch communications with the UE 402 from the mTRP mode to the sTRP mode. In some aspects, the network node 406 may be configured to switch communications with the UE 402 from the mTRP mode to the sTRP mode for one transmission, and may then switch communications with the UE 402 back to the mTRP mode after the one transmission.

[0086] The network node 406 may be configured to communicate at least one first transmission with the UE 402 via the TRP 410 and the TRP 412 in the mTRP mode. The UE 402 may be configured to communicate at least one first transmission with the network node 406 via the TRP 410 and the TRP 412 in the mTRP mode. The network node 406 may be configured to send an indication of switching to the sTRP mode to the UE 402. The UE 402 may be configured to obtain an indication of switching to the sTRP mode from the network node 406. The network node 406 may be configured to switch to communicating at least one second transmission with the UE 402 via one of the TRP 410 or the TRP 412 in the sTRP mode based on the indication of switching to the sTRP mode. The UE 402 may be configured to switch to communicating at least one second transmission with the network node 406 via one of the TRP 410 or the TRP 412 in the sTRP mode based on the indication of switching to the sTRP mode.

[0087] By enabling the network node 406 to support switching of the communication mode of the network node with the UE 402 between the mTRP mode and the sTRP mode, the network node 406 can take advantage of the mTRP mode in some aspects, such as increased throughput or reliability of communication with the UE 402, and can take advantage of the sTRP mode in other aspects, such as reduced power consumption or noise during communication with the UE 402.

[0088] The mTRP system may have one or more transmit configuration indicators (TCIs). TCI may be used to indicate the beam used for the TRP, for example, the first TCI may indicate the PDCCH beam used for TRP 410, the second TCI may indicate the PDSCH beam used for TRP 410, the third TCI may indicate the PUCCH beam used for TRP 410, the fourth TCI may indicate the PUSCH beam used for TRP 410, the fifth TCI may indicate the PDCCH beam used for TRP 412, the sixth TCI may indicate the PDSCH beam used for TRP 412, the seventh TCI may indicate the PUCCH beam used for TRP 412, and the eighth TCI may indicate the PUSCH beam used for TRP 412. Although an mTRP system may have a TCI for each beam of each TRP, it may be more efficient to use a unified TCI that can indicate a common beam between two or more beams of a TRP (such as the PDCCH and PUCCH of TRP 410) or a common beam between two or more beams of multiple TRPs (such as the PUCCH of TRP410 and the PUCCH of TRP 412).

[0089] In one aspect, the joint TCI state may indicate a common beam for at least one DL channel or reference signal (RS) plus at least one UL channel or RS. The joint TCI state may be specific to a UE such as Figure 4 402 in the UE), and may be common to two or more TRPs, such as TRP 410 and TRP 412. The joint TCI state may indicate a common beam for PDCCH and / or PDSCH plus PUCCH and / or PUSCH. In one aspect, a separate DL TCI state may indicate a common beam for at least two DL channels or RSs. A separate DL TCI state may indicate a common beam for a UE-specific PDCCH plus PDSCH. In one aspect, a separate UL TCI state may indicate a common beam for at least two UL channels or RSs. A separate UL TCI state may indicate a common beam for a UE-specific PUCCH plus PUSCH. A network node, such as Figure 4 The network node 406 in may configure joint or separate TCI states via RRC configuration.

[0090] FIG. 5A to FIG. 5F Various examples of mTRP resource allocation configurations in which a UE is configured to communicate with multiple TRPs in a cell group are illustrated. Figure 5A5 is a diagram illustrating an example of an mTRP resource allocation configuration. A network node may use frequency division multiplexing (FDM) to configure a UE to have a resource set 502 for a first TRP and a resource set 504 for a second TRP. Resource set 502 may have different RBs than resource set 504. Resource set 502 associated with the first TRP may have a frequency adjacent to a frequency of resource set 504 associated with the second TRP.

[0091] Figure 5B FIG. 5 is a diagram illustrating an example of mTRP resource allocation configuration. The network node may use time division multiplexing (TDM) to configure the UE for a first TRP such as Figure 4 TRP 410 in the example has resource set 512 and for a second TRP such as Figure 4 4. The TRP 412 in FIG. 4 has a resource set 514. The resource set 512 may have different symbols than the resource set 514. The resource set 512 associated with the first TRP may have resources immediately before or immediately after the resource set 514 associated with the second TRP.

[0092] Diagram 510 may represent a repetition of transmission using a first TRP and a second TRP. For example, diagram 510 may represent a first PUCCH associated with a first TRP associated with resource set 512 and a second PUCCH associated with a second TRP associated with resource set 514.

[0093] Figure 5C 520 is a diagram illustrating an example of mTRP resource allocation configuration. The network node may use space division multiplexing (SDM) to configure the UE for a first TRP (such as Figure 4 TRP 410 in has resource set 522 and for a second TRP (such as Figure 4 4. The resource set 522 may be transmitted over a different spatial region than the resource set 524. The resource set 522 associated with the first TRP may have resources that are spatially collocated with the resource set 524 associated with the second TRP.

[0094] Figure 5D FIG530 is a diagram illustrating an example of mTRP resource allocation configuration. The network node may use TDM cyclic mapping to configure the UE for a first TRP such as Figure 4 410) cyclically or periodically has a resource set including resource 532 and resource 536, and for a second TRP (such as Figure 4412) in TDM cyclically or periodically has a resource set including resource 534 and resource 538. Resources 532 and 536 can be associated with a first TRP, and resources 534 and 538 can be associated with a second TRP. Resources 532 and 536 can be cyclically mapped to the first TRP, and resources 534 and 538 can be cyclically mapped to the second TRP. The network node or UE can use RRC configuration in TDM to cyclically map the resource set to the first TRP and the second TRP.

[0095] Figure 5E FIG540 is a diagram illustrating an example of mTRP resource allocation configuration. The network node may use TDM sequence mapping to configure the UE for a first TRP (such as Figure 4 410) has a resource set including resource 542 and resource 544, which is configured for a second TRP such as Figure 4 44) has a resource set including resources 546 and 548. Resources 542 and 544 may be associated with a first TRP, and resources 546 and 548 may be associated with a second TRP. Resources 542 and 544 may be sequentially mapped to the first TRP, and resources 546 and 548 may be sequentially mapped to the second TRP. A network node or UE may use RRC configuration in TDM to map resource sets sequentially to the first TRP and the second TRP.

[0096] Fig. 5F FIG. 550 is a diagram illustrating an example of mTRP resource allocation configuration. The network node may use CORESET repetition to configure the UE to have a resource allocation with respect to the first TRP (such as Figure 4 CORESET 552 associated with a TRP 410 in FIG. 1 and a second TRP such as Figure 4 4. The UE may include a CORESET 554 associated with a CORESET 552 (TRP 412 in FIG. 4). The CORESET 552 may be associated with a first TRP, and the CORESET 554 may be associated with a second TRP. The PDCCH 556 associated with the CORESET 552 and the PDCCH 558 associated with the CORESET 554 may be linked to enable PDCCH repetition. In other words, the PDCCH 556 of the CORESET 552 sent to the UE may be repeated via the PDCCH 558 of the CORESET 554.

[0097] Figure 6An example of a scheduling DCI 600 is shown, which has a TCI field 602, an SRS resource set indicator field 604, a TCI selection indicator field 606, a time domain resource allocation (TDRA) field 608, a PUUCH resource indicator 610, and other fields 612 not explicitly shown in the diagram 600. The scheduling DCI 600 can be used to indicate the use of sTRP mode for scheduled transmissions. The scheduling DCI 600 can be used to indicate the use of mTRP mode for scheduled transmissions. One or more of the fields of the scheduling DCI 600 can be dedicated to providing a receiving UE (such as, Figure 4 402 in the scheduling DCI 600) indicates that the sTRP mode is used for the scheduled transmission. One or more of the fields in the scheduling DCI 600 may have a field that indicates to the receiving UE (such as Figure 4 The UE 402 in the scheduling DCI 600 may indicate a portion (e.g., one or more bits) of the sTRP mode used for the scheduled transmission. One or more of the fields of the scheduling DCI 600 may be dedicated to providing a signal to the receiving UE (e.g., Figure 4 The UE 402 in the scheduling DCI 600 indicates that the mTRP mode is used for the scheduled transmission. One or more of the fields in the scheduling DCI 600 may have a field that indicates to the receiving UE (such as, Figure 4 UE 402 in ) indicates a portion (e.g., one or more bits) of the mTRP pattern used for scheduled transmission.

[0098] Figure 7 700 illustrates a connection flow diagram of an example UE 702 configured to communicate with a TRP 704 and a TRP 706 in a cell group 705. The cell group 705 may be defined by a network node such as Figure 1 Base station 102 or Figure 4 The network node 406 in is controlled and operated.

[0099] The TRP 704 or TRP 706 may send a beam indication DCI or a beam indication MAC-CE 708 to the UE 702. The UE 702 may receive the beam indication DCI or the beam indication MAC-CE 708 from the TRP 704 or the TRP 706. The beam indication DCI or the beam indication MAC-CE 708 may indicate the mTRP operation using a pair of unified TCIs. The pair of unified TCIs may identify two DL applicable TCIs or two UL applicable TCIs for each of the TRP 704 and the TRP 706. For example, the first TCI may be associated with the PDSCH and PDCCH of the TRP 704, and the second TCI may be associated with the PDSCH and PDCCH of the TRP 706. On the other hand, the first TCI may be associated with the PDSCH and PUSCH of the TRP 704, and the second TCI may be associated with the PDSCH and PUSCH of the TRP 706.

[0100] The TRP 704 or the TRP 706 may send an mTRP scheduling DCI 710 to the UE 702. The UE 702 may receive the mTRP scheduling DCI 710 from the TRP 704 or the TRP 706. The mTRP scheduling DCI 710 may indicate mTRP communication using a pair of unified TCIs indicated by the beam indication DCI or the beam indication MAC-CE 708. The mTRP communication may be, for example, a PDSCH communication with both the TRP 704 and the TRP 706 or a PUSCH communication with both the TRP 704 and the TRP 706. The TRP 704 may communicate with the UE 702 via an mTRP communication 712 (which may be a PDSCH or a PUSCH) in response to the mTRP scheduling DCI 710. The TRP 706 may communicate with the UE 702 via an mTRP communication 714 (which may be a PDSCH or a PUSCH) in response to the mTRP scheduling DCI 710.

[0101] The TRP 704 or the TRP 706 may send a sTRP scheduling DCI 716 to the UE 702. The UE 702 may receive the sTRP scheduling DCI 716 from the TRP 704 or the TRP 706. The sTRP scheduling DCI 716 may use a field of the scheduling DCI 716 to indicate a sTRP communication 722. The sTRP scheduling DCI 716 may select a TCI state corresponding to the TRP 704 or the TRP 706. Although the connection flow diagram 700 shows that the sTRP scheduling DCI 716 indicates the selection of the TCI state associated with the TRP 704, in other aspects, the sTRP scheduling DCI 716 may indicate the selection of the TCI state associated with the TRP 706.

[0102] In one aspect, a dedicated field of the sTRP scheduling DCI 716 may indicate to the UE 702 which indicated TCI state applies to the PDSCH or PUSCH of the sTRP communication 722. In one aspect, if the sTRP communication 722 is a PUSCH transmission, the dedicated field may be Figure 6 In one aspect, if the sTRP communication 722 is a PDSCH transmission, the dedicated field may be Figure 6704. In response to the dedicated field including the selected TCI state associated with TRP 704, at 718, UE 702 may switch to communicate with TRP 704 via sTRP communication 722 in sTRP mode. At 720, TRP 704 may switch to communicate with UE 702 via sTRP communication 722 in sTRP mode. At 720, TRP 706 may switch to not communicate with UE 702.

[0103] In one aspect, the TDRA field of the sTRP scheduling DCI 716 may indicate to the UE 702 which indicated TCI state applies to the PDSCH or PUSCH of the sTRP communication 722. The TDRA field may be, for example, Figure 6 704 or TRP 706. In one aspect, the TDRA field may indicate at least one of a slot offset value (e.g., K0), a start and length indicator value (SLIV), or a TCI selection indicator to the scheduled PDSCH or PUSCH. The TCI selection indicator may select a TCI state associated with the TRP 704 or TRP 706 for the scheduled PDSCH or PUSCH. If the TCI selection indicator does not select a TRP (e.g., has a zero or null value), the UE 702 may apply two TCIs to the scheduled PDSCH or PUSCH (i.e., perform mTRP communication with both the TRP 704 and the TRP 706). For example, the mTRP scheduling DCI 710 may include a TDRA field having a TCI selection indicator that does not select a TRP. In response to the TCI selection indicator including the selected TCI state associated with the TRP 704, at 718, the UE 702 may switch to communicate with the TRP 704 in the sTRP mode via the sTRP communication 722. At 720, the TRP 704 may switch to communicate with the UE 702 in the sTRP mode via the sTRP communication 722. At 720, the TRP 706 may switch to not communicate with the UE 702.

[0104] In one aspect, the TCI field of the sTRP scheduling DCI 716 may indicate to the UE 702 which indicated TCI state is applied to the PDSCH or PUSCH of the sTRP communication 722. The TCI field may include a dedicated bit for selecting the TCI. For example, the TCI field may have three bits to indicate the index of the TCI state (e.g., selected from a table provided by the RRC configuration), and may have a dedicated bit for selecting the TCI from the first TCI associated with the TRP 704 and the second TCI associated with the TRP 706. In one aspect, one or more TCI code points in the sTRP scheduling DCI 716 may indicate to the UE 702 which indicated TCI state of the selected TCI is applied to the PDSCH or PUSCH of the sTRP communication 722. In response to the TCI field of the sTRP scheduling DCI 716 including the selected TCI state associated with the TRP 704, at 718, the UE 702 may switch to communicate with the TRP 704 via the sTRP communication 722 in the sTRP mode. At 720, TRP 704 may switch to communicate with UE 702 in sTRP mode via sTRP communication 722. At 720, TRP 706 may switch to not communicate with UE 702.

[0105] At 724, UE 702 may switch back to mTRP mode. UE 702 may switch back to mTRP mode in response to completing sTRP communication 722 (e.g., after completing PUSCH transmission or after sending ACK from TRP 704 for PDSCH transmission). At 726, TRP 704 may switch to communicate with UE 702 in mTRP mode. At 726, TRP 706 may switch to communicate with UE 702 in mTRP mode.

[0106] Figure 8 800 illustrates a connection flow diagram of an example UE 802 configured to communicate with a TRP 804 and a TRP 806 in a cell group 805. The cell group 805 may be configured by a network node such as Figure 1 Base station 102 or Figure 4 The network node 406 in is controlled and operated.

[0107] The TRP 804 or the TRP 806 may send a CORESET configuration 807 to the UE 802. The UE 802 may receive the CORESET configuration 807 from the TRP 804 or the TRP 806. The CORESET configuration 807 may be, for example, an RRC configuration that configures one or more CORESETs associated with the UE 802. In one aspect, the CORESET configuration 807 may configure two CORESETs to enable PDCCH repetition, such as by Fig. 5FFIG. 550 illustrates PDCCH repetition.

[0108] The TRP 804 or TRP 806 may send a beam indication DCI or a beam indication MAC-CE 808 to the UE 802. The UE 802 may receive the beam indication DCI or the beam indication MAC-CE 808 from the TRP 804 or the TRP 806. The beam indication DCI or the beam indication MAC-CE 808 may indicate the mTRP operation using a pair of unified TCIs. The pair of unified TCIs may identify two DL applicable TCIs or two UL applicable TCIs for each of the TRP 804 and the TRP 806. For example, the first TCI may be associated with the PDSCH and PDCCH of the TRP 804, and the second TCI may be associated with the PDSCH and PDCCH of the TRP 806. On the other hand, the first TCI may be associated with the PDCCH and PUCCH of the TRP 804, and the second TCI may be associated with the PDCCH and PUCCH of the TRP 806.

[0109] The TRP 804 or the TRP 806 may send an mTRP scheduling DCI 810 to the UE 802. The UE 802 may receive the mTRP scheduling DCI 810 from the TRP 804 or the TRP 806. The mTRP scheduling DCI 810 may indicate mTRP communication using a pair of unified TCIs indicated by the beam indication DCI or the beam indication MAC-CE 808. The mTRP communication may be, for example, repeated PDCCH communication with both the TRP 804 and the TRP 806 using CORESET repetition. The TRP 804 may communicate with the UE 802 via mTRP communication 812 (which may be a PDCCH repeated using CORESET repetition) in response to the mTRP scheduling DCI 810. The TRP 806 may communicate with the UE 802 via mTRP communication 814 (which may be a PDCCH repeated using CORESET repetition) in response to the mTRP scheduling DCI 810.

[0110] The TRP 804 or TRP 806 may send a sTRP scheduling DCI 816 to the UE 802. The UE 802 may receive the sTRP scheduling DCI 816 from the TRP 804 or TRP 806. The sTRP scheduling DCI 816 may indicate a sTRP communication 822 using a field of the scheduling DCI 816. The sTRP scheduling DCI 816 may select an inappropriate TCI state for the sTRP communication 822. At 818, in response to the sTRP scheduling DCI 816 selecting an inappropriate TCI state associated with the TRP 806 for the sTRP communication 822, the UE 802 may suppress monitoring of the PDCCH candidates associated with the TRP 806 (i.e., associated with the inappropriate TCI state). The UE 802 may be configured to suppress or skip monitoring the PDCCH candidates after a certain number of symbols to avoid transmitting an ACK to the sTRP scheduling DCI 816. Although connection flow diagram 800 illustrates that sTRP scheduling DCI 816 indicates selection of an inappropriate TCI state associated with TRP 806, in other aspects, sTRP scheduling DCI 816 may indicate selection of an inappropriate TCI state associated with TRP 804.

[0111] In one aspect, a dedicated field of the sTRP scheduling DCI 816 may indicate to the UE 802 which inappropriate TCI state should be used to skip the PDCCH repetition of the sTRP communication 822. In one aspect, the dedicated field may be Figure 6 In one aspect, the dedicated field may be Figure 6 806. In response to the dedicated field including an inappropriate TCI state associated with TRP 806, at 818, UE 802 may switch to communicating with TRP 804 via sTRP communication 822 in sTRP mode by suppressing monitoring of PDCCH candidates associated with the inappropriate TCI state (i.e., associated with TRP 806).

[0112] In one aspect, the TDRA field of the sTRP scheduling DCI 816 may indicate to the UE 802 which inappropriate TCI state applies to the PDCCH of the sTRP communication 822. The TDRA field may be, for example, Figure 6806. In one aspect, the TDRA field 608 in the scheduled PDCCH may indicate at least one of a slot offset value (e.g., K0), a start and length indicator value (SLIV), or a TCI selection indicator for the scheduled PDCCH. The TCI selection indicator may select an inappropriate TCI state associated with TRP 804 or TRP 806 for the scheduled PDCCH. If the TCI selection indicator does not select a TRP (e.g., has a zero or null value), the UE 802 may monitor two PDCCH candidates associated with the CORESET repetition for the scheduled PDCCH (i.e., perform mTRP communication with both TRP 804 and TRP 806). For example, the mTRP scheduling DCI 810 may include a TDRA field having a TCI selection indicator that does not select a TRP. In response to the TCI selection indicator including an inappropriate TCI state associated with TRP 806, at 818, UE 802 may suppress monitoring of PDCCH candidates associated with the inappropriate TCI state (i.e., associated with TRP 806) for sTRP communication 822.

[0113] At 824, UE 802 may switch back to mTRP mode. UE 802 may switch back to mTRP mode in response to completing sTRP communication 822 (e.g., after sending an ACK for the PDCCH transmission). Switching back to mTRP mode may include monitoring two PDCCH candidates associated with CORESET repetition.

[0114] In one aspect, the beam indication DCI or beam indication MAC-CE 808 may indicate mTRP operation using a single unified TCI associated with both TRP 804 and TRP 806. For example, the beam indication DCI or beam indication MAC-CE 808 may define a first single unified TCI associated with the PDCCH for both TRP 804 and TRP 806, and define a second single unified TCI associated with the PDCCH for TRP 804 but not for TRP 806. In other words, the first single unified TCI may be used to receive the mTRP operation. Fig. 5F two links in the CORESET, and a second single unified TCI can be used to receive Fig. 5F In one aspect, the second single unified TCI may be pre-determined by a TCI to CORESET association. In one aspect, the second single unified TCI may be pre-configured or pre-determined by a condition such as a definition in a specification. For example, the condition may be to select a lower CORESET ID for a TCI state, or to select a higher CORESET ID for a TCI state.

[0115] The TRP 804 or the TRP 806 may send an mTRP scheduling DCI 810 to the UE 802. The UE 802 may receive the mTRP scheduling DCI 810 from the TRP 804 or the TRP 806. The mTRP scheduling DCI 810 may indicate mTRP communication using a single unified TCI associated with the TRP 804 and the TRP 806 indicated by the beam indication DCI or the beam indication MAC-CE 808. The mTRP communication may be, for example, repeated PDCCH communication with both the TRP 804 and the TRP 806 using CORESET repetition. The TRP 804 may communicate with the UE 802 via an mTRP communication 812 (which may be a PDCCH repeated using CORESET repetition) in response to the mTRP scheduling DCI 810. The TRP 806 may communicate with the UE 802 in response to the mTRP scheduling DCI 810 via an mTRP communication 814 (which may be a PDCCH repeated using CORESET repetition).

[0116] The TRP 804 or TRP 806 may send a sTRP scheduling DCI 816 to the UE 802. The UE 802 may receive the sTRP scheduling DCI 816 from the TRP 804 or TRP 806. The sTRP scheduling DCI 816 may indicate a single unified TCI for receiving one of the two linked CORESETs. In other words, the sTRP scheduling DCI 816 may indicate a TCI state associated with the TRP 804 but not associated with the TRP 806. The UE 802 may be configured to suppress or skip monitoring PDCCH candidates after a certain number of symbols to avoid transmitting an ACK to the sTRP scheduling DCI 816. While the connection flow diagram 800 illustrates that the sTRP scheduling DCI 816 indicates a single unified TCI associated with the TRP 804 but not associated with the TRP 806, in other aspects, the sTRP scheduling DCI 816 may indicate a selection of a single unified TCI associated with the TRP 806 but not associated with the TRP 804. In response to the sTRP scheduling DCI 816 indicating a single unified TCI associated with the TRP 804 for receiving the CORESET, at 818, the UE 802 may refrain from monitoring the PDCCH candidates associated with the TRP 806 for sTRP communications 822.

[0117] At 824, UE 802 may switch back to mTRP mode. UE 802 may switch back to mTRP mode in response to completing sTRP communication 822 (e.g., after sending an ACK for the PDCCH transmission). Switching back to mTRP mode may include monitoring two PDCCH candidates associated with CORESET repetition.

[0118] Fig. 9 900 illustrates a connection flow diagram of an example UE 902 configured to communicate with a TRP 904 and a TRP 906 in a cell group 905. The cell group 905 may be defined by a network node such as Figure 1 Base station 102 or Figure 4 The network node 406 in is controlled and operated.

[0119] The TRP 904 or TRP 906 may output an RRC configuration 907 to the UE 902. The UE 902 may receive the RRC configuration 907 from the TRP 904 or TRP 906. The RRC configuration 907 provides, for example, a table that associates a PUCCH resource indicator (PRI) code point in the DCI with the number of repetitions used for PUCCH transmission. For example, the table may associate a PRI of zero with one PUCCH repetition, and may associate a PRI of one with two PUCCH repetitions.

[0120] The TRP 904 or TRP 906 may output a beam indication DCI or a beam indication MAC-CE 908 to the UE 902. The UE 902 may receive the beam indication DCI or the beam indication MAC-CE 908 from the TRP 904 or TRP 906. The beam indication DCI or the beam indication MAC-CE 908 may indicate the mTRP operation using a pair of unified TCIs. The pair of unified TCIs may identify two DL applicable TCIs or two UL applicable TCIs for each of the TRP 904 and the TRP 906. For example, the first TCI may be associated with the PUSCH and PUCCH of the TRP 904, and the second TCI may be associated with the PUSCH and PUCCH of the TRP 906. On the other hand, the first TCI may be associated with the PDCCH and PUCCH of the TRP 904, and the second TCI may be associated with the PDCCH and PUCCH of the TRP 906.

[0121] The TRP 904 or the TRP 906 may output the mTRP scheduling DCI 910 to the UE 902. The UE 902 may receive the mTRP scheduling DCI 910 from the TRP 904 or the TRP 906. The mTRP scheduling DCI 910 may indicate the mTRP communication using a pair of unified TCIs indicated by the beam indication DCI or the beam indication MAC-CE 908. The mTRP scheduling DCI 910 may indicate one or more PUCCH repetitions through a PUCCH resource indicator.

[0122] In one aspect, the mTRP scheduling DCI 910 may indicate Figure 5B510 in which UE 902 may use resource set 512 to send PUCCH to TRP 904 and use resource set 514 to send PUCCH to TRP 906 (i.e., one PUCCH repetition). On the other hand, mTRP scheduling DCI 910 may indicate the same Figure 5D 530 in FIG. 5, where UE 902 may use resources 532 and 536 to send PUCCH to TRP 904 and may use resources 534 and 538 to send PUCCH to TRP 906. On the other hand, mTRP scheduling DCI 910 may indicate the same as Figure 5E 540 in which UE 902 may use resources 542 and 544 to send PUCCH as mTRP communication 912 to TRP 904 and may use resources 546 and 548 to send PUCCH as mTRP communication 914 to TRP 906.

[0123] The TRP 904 or TRP 906 may output a sTRP scheduling DCI 916 to the UE 902. The UE 902 may receive the sTRP scheduling DCI 916 from the TRP 904 or TRP 906. The sTRP scheduling DCI 916 may indicate one or more PUCCH repetitions by a PUCCH resource indicator. The sTRP scheduling DCI 916 may indicate a selection of a TCI state. In one aspect, a PUCCH resource indicator (such as Figure 6 The PUUCH resource indicator 610 in the PUUCH resource indicator 610 may indicate the selection of the TCI state. In one aspect, the TCI selection indicator (such as Figure 6 The TCI selection indicator field 606 in the sTRP scheduling DCI 916 may indicate the selection of the TCI state. In one aspect, the dedicated field of the sTRP scheduling DCI 916 may indicate to the UE 902 which indicated TCI state applies to the PUUCH of the sTRP communication 922. In one aspect, the dedicated field may be Figure 6 In one aspect, the dedicated field may be Figure 6 The TCI selection indicator field 606 in .

[0124] In response to the sTRP scheduling DCI 916 indicating a TCI state associated with the TRP 904, at 918, the UE 902 may switch to communicating with the TRP 904 via the sTRP communication 922 in the sTRP mode by sending a PUCCH transmission to the TRP 904 as a sTRP communication 922 and abandoning the PUCCH transmission repeated to the TRP 906. At 920, the TRP 906 may switch to the sTRP mode by not monitoring the PUCCH transmission from the UE 902.

[0125] At 924, UE 902 may switch back to mTRP mode. UE 902 may switch back to mTRP mode in response to completing sTRP communication 922 (e.g., after completing PUCCH transmission). At 926, TRP 906 may switch to communicating with UE 902 in mTRP mode by monitoring repeated PUCCH transmissions from UE 902.

[0126] In one aspect, the beam indication DCI or beam indication MAC-CE 908 may indicate mTRP operation using a single unified TCI associated with both TRP 904 and TRP 906. For example, the beam indication DCI or beam indication MAC-CE 908 may define a first single unified TCI associated with the PUCCH for both TRP 904 and TRP 906, and define a second single unified TCI associated with the PUCCH for TRP 904 but not for TRP 906. In other words, the first single unified TCI may be used to indicate mTRP operation using Figure 5B The PUCCH is transmitted in both resource set 512 and resource set 514 in the example, and a second single unified TCI may be used to transmit the PUCCH using Figure 5B The PUCCH may be sent using one of resource set 512 or resource set 514 in the UEFI_SRC. In one aspect, the second single unified TCI may be preconfigured or predetermined by a condition such as a definition in a specification.

[0127] The TRP 904 or the TRP 906 may output an mTRP scheduling DCI 910 to the UE 902. The UE 902 may receive the mTRP scheduling DCI 910 from the TRP 904 or the TRP 906. The mTRP scheduling DCI 910 may indicate mTRP communication using a single unified TCI associated with the TRP 904 and the TRP 906 indicated by the beam indication DCI or the beam indication MAC-CE 908. The mTRP communication may be, for example, repeated PUCCH communication with both the TRP 904 and the TRP 906. The TRP 904 may communicate with the UE 902 via an mTRP communication 912 (which may be a PUCCH repeated using TDM) in response to the mTRP scheduling DCI 910. The TRP 906 may communicate with the UE 902 in response to the mTRP-scheduled DCI 910 via an mTRP communication 914 (which may be a PUCCH repeated using TDM).

[0128] The TRP 904 or TRP 906 may output a sTRP scheduling DCI 916 to the UE 902. The UE 902 may receive the sTRP scheduling DCI 916 from the TRP 904 or TRP 906. The sTRP scheduling DCI 916 may indicate a single unified TCI for sending one of the two PUCCHs. In other words, the sTRP scheduling DCI 916 may indicate a TCI state associated with the TRP 904 but not associated with the TRP 906. The UE 902 may be configured to suppress or skip sending PUCCH transmissions to the TRP 906. Although the connection flow chart 900 shows that the sTRP scheduling DCI 916 indicates a single unified TCI associated with the TRP 904 but not associated with the TRP 906, in other aspects, the sTRP scheduling DCI 916 may indicate a selection of a single unified TCI associated with the TRP 906 but not associated with the TRP 904. In response to the sTRP scheduling DCI 916 indicating a single unified TCI associated with TRP 904 for receiving CORESET, at 918, UE 902 may suppress sending PUCCH transmissions to TRP 906.

[0129] At 924, the UE 902 may switch back to the mTRP mode. The UE 902 may switch back to the mTRP mode in response to completing the sTRP communication 922 (e.g., after sending the PUCCH transmission). Switching back to the mTRP mode may include sending each PUCCH transmission indicated by the PUCCH source indicator. At 926, the TRP 906 may switch to communicating with the UE 902 in the mTRP mode by monitoring repeated PUCCH transmissions from the UE 902.

[0130] Fig.101000 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 402, UE 702, UE 802, UE 902; device 1904). At 1002, the UE may communicate at least one first transmission with a network node via a first TRP and a second TRP in an mTRP mode. For example, 1002 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0131] At 1004, the UE may obtain an indication to switch to sTRP mode. For example, 1004 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0132] At 1006, the UE may switch to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode. For example, 1006 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0133] Fig.11 1100 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 402, UE 702, UE 802, UE 902; device 1904). At 1102, the UE may communicate at least one first transmission with a network node via a first TRP and a second TRP in an mTRP mode. For example, 1102 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0134] At 1104, the UE may obtain an indication to switch to sTRP mode. For example, 1104 may be indicated by Fig.19 Component 198 of device 1904 is executed.

[0135] At 1106, the UE may switch to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode. For example, 1106 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0136] At 1108, the UE may receive at least one of a beam indication DCI or a beam indication MAC-CE indicating an mTRP mode using a first unified TCI associated with the first TRP and a second unified TCI associated with the second TRP. For example, 1108 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0137] At 1110, the UE may receive a scheduling DCI for scheduling at least one second transmission, wherein the scheduling DCI includes a field including an indication of switching to sTRP mode, wherein the indication of switching to sTRP mode may select a suitable TCI state of the first TCI and the second TCI for the at least one second transmission. For example, 1110 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0138] At 1112, the UE may receive a scheduling DCI scheduling at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating one PUCCH repetition, wherein the scheduling DCI may include an indication of switching to sTRP mode, wherein the indication may include at least one of a PUCCH resource indicator, a TCI selection indicator, or a dedicated field of the scheduling DCI selecting a suitable TCI state in the first TCI and the second TCI for the at least one second transmission. For example, 1112 may be Fig.19 Component 198 of device 1904 is executed.

[0139] Fig.12 1200 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 402, UE 702, UE 802, UE 902; device 1904). At 1202, the UE may communicate at least one first transmission with a network node via a first TRP and a second TRP in an mTRP mode. For example, 1202 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0140] At 1204, the UE may obtain an indication to switch to sTRP mode. For example, 1204 may be indicated by Fig.19 Component 198 of device 1904 is executed.

[0141] At 1206, the UE may switch to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode. Fig.19 Component 198 of device 1904 is executed.

[0142] At 1208, the UE may receive at least one CORESET configuration indicating a first CORESET associated with a first TRP and a first PDCCH, a second CORESET associated with a second TRP and a second PDCCH, and a link between the first PDCCH and the second PDCCH for enabling PDCCH repetition. For example, 1208 may be Fig.19 Component 198 of device 1904 is executed.

[0143] At 1210, the UE may receive a scheduling DCI that schedules at least one second transmission, wherein the scheduling DCI may include a field including an indication of switching to sTRP mode, wherein the indication of switching to sTRP mode may indicate an inappropriate TCI state in the first TCI and the second TCI. For example, 1210 may be Fig.19 Component 198 of device 1904 is executed.

[0144] At 1212, the UE may monitor an inappropriate TCI state for at least one second transmission suppression. Fig.19 Component 198 of device 1904 is executed.

[0145] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 402, UE 702, UE 802, UE 902; device 1904). At 1302, the UE may communicate at least one first transmission with a network node via a first TRP and a second TRP in an mTRP mode. For example, 1302 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0146] At 1304, the UE may obtain an indication to switch to sTRP mode. For example, 1304 may be indicated by Fig.19 Component 198 of device 1904 is executed.

[0147] At 1306, the UE may switch to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode. For example, 1306 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0148] At 1308, the UE may receive a scheduling DCI scheduling at least one second transmission, wherein the scheduling DCI includes a PUCCH resource indicator indicating a PUCCH repetition. For example, 1308 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0149] At 1310, the UE may obtain a condition for selecting a suitable TCI state in the first TCI and the second TCI for at least one second transmission in response to the PUCCH resource indicator indicating one PUCCH repetition. For example, 1310 may be Fig.19 Component 198 of device 1904 is executed.

[0150] Fig.141400 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 402, UE 702, UE 802, UE 902; device 1904). At 1402, the UE may communicate at least one first transmission with a network node via a first TRP and a second TRP in an mTRP mode. For example, 1402 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0151] At 1404, the UE may obtain an indication to switch to sTRP mode. For example, 1404 may be indicated by Fig.19 Component 198 of device 1904 is executed.

[0152] At 1406, the UE may switch to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode. For example, 1406 may be performed by Fig.19 Component 198 of device 1904 is executed.

[0153] At 1408, the UE may receive at least one of a beam indication DCI or a beam indication MAC-CE indicating an mTRP mode using a first unified TCI associated with the first TRP and the second TRP. Fig.19 Component 198 of device 1904 is executed.

[0154] At 1410, the UE may receive at least one CORESET configuration indicating a first CORESET associated with a first TRP and a first PDCCH, a second CORESET associated with a second TRP and a second PDCCH, and a link between the first PDCCH and the second PDCCH for enabling PDCCH repetition. Fig.19 Component 198 of device 1904 is executed.

[0155] At 1412, the UE may receive a scheduling DCI scheduling at least one second transmission, wherein the scheduling DCI may include a PUCCH resource indicator indicating a number of PUCCH repetitions. Fig.19 Component 198 of device 1904 is executed.

[0156] At 1414, the UE may obtain a condition indicating an inappropriate TRP in the first TRP and the second TRP for at least one second transmission in response to at least one of the beam indication DCI or the beam indication MAC-CE indicating the mTRP mode using the first TCI indicator associated with the first TRP and the second TRP. For example, 1404 may be Fig.19 Component 198 of device 1904 is executed.

[0157] At 1416, the UE may monitor for an inappropriate TRP for at least one second transmission suppression. Fig.19 Component 198 of device 1904 is executed.

[0158] At 1418, the UE may send the PUCCH without repeating using an inappropriate TRP. Fig.19 Component 198 of device 1904 is executed.

[0159] Fig.15 1500 is a flow chart of a method of wireless communication. The method may be performed by a network node (e.g., base station 102, base station 310; network node 406; network entity 1902, network entity 2002, network entity 2160). At 1502, the network node may communicate at least one first transmission with a UE via a first TRP and a second TRP in an mTRP mode. For example, 1502 may be performed by Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0160] At 1504, the network node may send an indication to the UE to switch to the sTRP mode. For example, 1504 may be performed by Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0161] At 1506, the network node may switch to communicating at least one second transmission with the UE via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode. Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0162] Fig.161600 is a flow chart of a method of wireless communication. The method may be performed by a network node (e.g., base station 102, base station 310; network node 406; network entity 1902, network entity 2002, network entity 2160). At 1602, the network node may communicate at least one first transmission with a UE via a first TRP and a second TRP in an mTRP mode. For example, 1602 may be performed by Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0163] At 1604, the network node may send an indication to the UE to switch to the sTRP mode. For example, 1604 may be Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0164] At 1606, the network node may switch to communicating at least one second transmission with the UE via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode. For example, 1606 may be performed by Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0165] At 1608, the network node may send at least one of a beam indication DCI or a beam indication MAC-CE indicating the mTRP mode using a first unified TCI associated with the first TRP and a second unified TCI associated with the second TRP. Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0166] At 1610, the network node may send a scheduling DCI for scheduling at least one second transmission, wherein the scheduling DCI may include a field including an indication of switching to sTRP mode, wherein the indication of switching to sTRP mode may select a suitable TCI state of the first TCI and the second TCI for the at least one second transmission. For example, 1610 may be performed by Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0167] At 1612, the network node may send a scheduling DCI for scheduling at least one second transmission, the scheduling DCI may include a PUCCH resource indicator indicating one PUCCH repetition, wherein the scheduling DCI may include an indication of switching to sTRP mode, wherein the indication may include at least one of a PUCCH resource indicator, a TCI selection indicator, or a dedicated field of the scheduling DCI for selecting a suitable TCI state in the first TCI and the second TCI for the at least one second transmission. For example, 1612 may be performed by Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0168] Fig.17 1700 is a flow chart of a method of wireless communication. The method may be performed by a network node (e.g., base station 102, base station 310; network node 406; network entity 1902, network entity 2002, network entity 2160). At 1702, the network node may communicate at least one first transmission with a UE via a first TRP and a second TRP in an mTRP mode. For example, 1702 may be performed by Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0169] At 1704, the network node may send an indication to the UE to switch to the sTRP mode. For example, 1704 may be performed by Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0170] At 1706, the network node may switch to communicating at least one second transmission with the UE via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode. Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0171] At 1708, the network node may send at least one CORESET configuration indicating a first CORESET associated with a first TRP and a first PDCCH, a second CORESET associated with a second TRP and a second PDCCH, and a link between the first PDCCH and the second PDCCH for enabling PDCCH repetition. Fig. 20 Component 199 of network entity 2002 or Fig.21Executed by component 199 of network entity 2160.

[0172] At 1710, the network node may send a scheduling DCI for scheduling at least one second transmission, wherein the scheduling DCI may include a field including an indication of switching to sTRP mode, wherein the indication of switching to sTRP mode may indicate an inappropriate TCI state in the first TCI and the second TCI. For example, 1710 may be performed by Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0173] At 1712, the network node may monitor the inappropriate TCI state for at least one second transmission inhibition. Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0174] Fig.18 1800 is a flow chart of a method of wireless communication. The method may be performed by a network node (e.g., base station 102, base station 310; network node 406; network entity 1902, network entity 2002, network entity 2160). At 1802, the network node may communicate at least one first transmission with a UE via a first TRP and a second TRP in an mTRP mode. For example, 1802 may be performed by Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0175] At 1804, the network node may send an indication to the UE to switch to the sTRP mode. For example, 1804 may be Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0176] At 1806, the network node may switch to communicating at least one second transmission with the UE via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode. Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0177] At 1808, the network node may send at least one CORESET configuration indicating a first CORESET associated with a first TRP and a first PDCCH, a second CORESET associated with a second TRP and a second PDCCH, and a link between the first PDCCH and the second PDCCH for enabling PDCCH repetition. For example, 1808 may be Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0178] At 1810, the network node may send a scheduling DCI scheduling at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating a number of PUCCH repetitions. For example, 1810 may be performed by Fig. 20 Component 199 of network entity 2002 or Fig.21 Executed by component 199 of network entity 2160.

[0179] Fig.191900 is an example of a hardware implementation of an example device 1904. The device 1904 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 1904 may include a cellular baseband processor 1924 (also referred to as a modem) coupled to one or more transceivers 1922 (e.g., a cellular RF transceiver). The cellular baseband processor 1924 may include on-chip memory 1924'. In some aspects, the device 1904 may also include one or more subscriber identity module (SIM) cards 1920 and an application processor 1906 coupled to a secure digital (SD) card 1908 and a screen 1910. The application processor 1906 may include on-chip memory 1906'. In some aspects, the device 1904 may also include a Bluetooth module 1912, a WLAN module 1914, an SPS module 1916 (e.g., a GNSS module), one or more sensor modules 1918 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1926, a power source 1930, and / or a camera 1932. The Bluetooth module 1912, the WLAN module 1914, and the SPS module 1916 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1912, the WLAN module 1914, and the SPS module 1916 may include their own dedicated antennas and / or communicate using an antenna 1980. The cellular baseband processor 1924 communicates with the UE 104 and / or with the RU associated with the network entity 1902 through the transceiver 1922 via one or more antennas 1980. The cellular baseband processor 1924 and the application processor 1906 may each include a computer-readable medium / memory 1924', 1906', respectively. The additional memory module 1926 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1924', 1906', 1926 may be non-transitory. The cellular baseband processor 1924 and the application processor 1906 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1924 / application processor 1906, enables the cellular baseband processor 1924 / application processor 1906 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1924 / application processor 1906 when executing the software.The cellular baseband processor 1924 / application processor 1906 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1904 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1924 and / or the application processor 1906, while in another configuration, the device 1904 may be the entire UE (e.g., see. Figure 3 UE 350) and includes additional modules of device 1904.

[0180] As discussed above, component 198 may be configured to communicate at least one first transmission with a network node via a first TRP and a second TRP in mTRP mode. Component 198 may be configured to obtain an indication of switching to sTRP mode. Component 198 may be configured to switch to communicating at least one second transmission with a network node via one of the first TRP or the second TRP in sTRP mode based on an indication of switching to sTRP mode. Component 198 may be within a cellular baseband processor 1924, an application processor 1906, or within both a cellular baseband processor 1924 and an application processor 1906. Component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. As shown, device 1904 may include a variety of components configured for various functions. In one configuration, the device 1904, and specifically the cellular baseband processor 1924 and / or the application processor 1906, includes a component for communicating at least one first transmission with a network node via a first TRP and a second TRP in mTRP mode. The device 1904 may include a component for obtaining an indication of switching to sTRP mode. The device 1904 may include a component for switching to communicate at least one second transmission with a network node via one of the first TRP or the second TRP in sTRP mode based on the indication of switching to sTRP mode. The device 1904 may include a component for receiving at least one of a beam indication DCI or a beam indication MAC-CE indicating an mTRP mode using a first unified transmission configuration indicator TCI associated with the first TRP and a second unified TCI associated with the second TRP. The device 1904 may include a component for obtaining an indication of switching to sTRP mode by receiving a scheduling DCI that schedules at least one second transmission. The device 1904 may include a component for obtaining an indication of switching to sTRP mode by receiving a scheduling DCI that schedules at least one second transmission. The apparatus 1904 may include means for switching to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in sTRP mode by suppressing monitoring of an inappropriate TCI state for at least one second transmission. The apparatus 1904 may include means for obtaining an indication of switching to sTRP mode by receiving a scheduling DCI for scheduling at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating one PUCCH repetition. The apparatus 1904 may include means for receiving a scheduling DCI for scheduling at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating one PUCCH repetition.Device 1904 may include a component for obtaining an indication of switching to sTRP mode by obtaining a condition for selecting a suitable TCI state of the first TCI and the second TCI for at least one second transmission in response to a PUCCH resource indicator indicating a PUCCH repetition. Device 1904 may include a component for receiving at least one of a beam indication DCI or a beam indication MAC-CE that indicates an mTRP mode using a first unified TCI associated with the first TRP and the second TRP. Device 1904 may include a component for obtaining an indication of switching to sTRP mode by obtaining a condition for indicating an inappropriate TRP of the first TRP and the second TRP for at least one second transmission in response to at least one of a beam indication DCI or a beam indication MAC-CE that indicates an mTRP mode using a first TCI indicator associated with the first TRP and the second TRP. The apparatus 1904 may include a component for receiving at least one CORESET configuration indicating a first CORESET associated with a first TRP and a first PDCCH, a second CORESET associated with a second TRP and a second PDCCH, and a link between the first PDCCH and the second PDCCH for enabling PDCCH repetition. The apparatus 1904 may include a component for switching to communicating at least one second transmission by suppressing monitoring an inappropriate TRP for at least one second transmission. The apparatus 1904 may include a component for receiving a scheduling DCI for scheduling at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating the number of PUCCH repetitions. The apparatus 1904 may include a component for switching to communicating at least one second transmission by transmitting a PUCCH without repeating using an inappropriate TRP. The component may be a component 198 of the apparatus 1904 configured to perform the functions recited by the component. As described above, the apparatus 1904 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, this component may be the TX Processor 368, the RX Processor 356, and / or the controller / processor 359 configured to perform the functions recited by this component.

[0181] Fig. 202000 is a diagram illustrating an example of a hardware implementation for a network entity 2002. The network entity 2002 may be a BS, a component of a BS, or may implement BS functionality. The network entity 2002 may include at least one of a CU 2010, a DU 2030, or a RU 2040. For example, depending on the layer functionality handled by the component 199, the network entity 2002 may include a CU 2010; both a CU 2010 and a DU 2030; each of the CU 2010, the DU 2030, and the RU 2040; the DU 2030; both a DU 2030 and a RU 2040; or a RU 2040. The CU 2010 may include a CU processor 2012. The CU processor 2012 may include an on-chip memory 2012'. In some aspects, the CU 2010 may also include an additional memory module 2014 and a communication interface 2018. CU 2010 communicates with DU 2030 via a midhaul link, such as an F1 interface. DU 2030 may include a DU processor 2032. DU processor 2032 may include on-chip memory 2032'. In some aspects, DU 2030 may also include additional memory modules 2034 and a communication interface 2038. DU 2030 communicates with RU 2040 via a fronthaul link. RU 2040 may include a RU processor 2042. RU processor 2042 may include on-chip memory 2042'. In some aspects, RU 2040 may also include additional memory modules 2044, one or more transceivers 2046, antenna 2080, and communication interface 2048. RU 2040 communicates with UE 104. On-chip memory 2012', 2032', 2042' and additional memory modules 2014, 2034, 2044 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of the processors 2012, 2032, 2042 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0182] As discussed above, component 199 is configured to communicate at least one first transmission with the UE via the first TRP and the second TRP in the mTRP mode. Component 199 may be configured to send an indication of switching to the UE in the sTRP mode. Component 199 may be configured to switch to communicating at least one second transmission with the UE via one of the first TRP or the second TRP in the sTRP mode based on the indication of switching to the sTRP mode. Component 199 may be within one or more processors of one or more of CU 2010, DU 2030, and RU 2040. Component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. Network entity 2002 may include a variety of components configured for various functions. In one configuration, network entity 2002 may include a component for communicating at least one first transmission with the UE via the first TRP and the second TRP in the mTRP mode. The network entity 2002 may include a component for sending an indication of switching to sTRP mode to the UE. The network entity 2002 may include a component for switching to communicate at least one second transmission with the UE via one of the first TRP or the second TRP in the sTRP mode based on the indication of switching to the sTRP mode. The network entity 2002 may include a component for sending at least one of a beam indication DCI or a beam indication MAC-CE indicating the mTRP mode using a first unified TCI associated with the first TRP and a second unified TCI associated with the second TRP. The network entity 2002 may include a component for sending an indication of switching to sTRP mode by sending a scheduling DCI that schedules at least one second transmission. The network entity 2002 may include a component for sending at least one CORESET configuration, the at least one CORESET configuration indicating a first CORESET associated with the first TRP and the first PDCCH, a second CORESET associated with the second TRP and the second PDCCH, and a link between the first PDCCH and the second PDCCH for enabling PDCCH repetition. The network entity 2002 may include a component for sending an indication of switching to sTRP mode, which may include sending a scheduling DCI for scheduling at least one second transmission. The network entity 2002 may include a component for switching to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in sTRP mode by suppressing monitoring of an inappropriate TCI state for at least one second transmission. The network entity 2002 may include a component for sending an indication of switching to sTRP mode by sending a scheduling DCI for scheduling at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating one PUCCH repetition.The network entity 2002 may include a component for sending at least one CORESET configuration, the at least one CORESET configuration indicating a first CORESET associated with a first TRP and a first PDCCH for enabling PDCCH repetition, a second CORESET associated with a second TRP and a second PDCCH, and a link between the first PDCCH and the second PDCCH. The network entity 2002 may include a component for sending a scheduling DCI for scheduling at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating the number of PUCCH repetitions. The component may be a component 199 of the network entity 2002 configured to perform the functions recited by the component. As described above, the network entity 2002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the component.

[0183] Fig.21 2100 is an example of a hardware implementation for a network entity 2160. In one example, the network entity 2160 may be within the core network 120. The network entity 2160 may include a network processor 2112. The network processor 2112 may include an on-chip memory 2112'. In some aspects, the network entity 2160 may also include an additional memory module 2114. The network entity 2160 communicates with the CU 2102 directly (e.g., backhaul link) or indirectly (e.g., through the RIC) via the network interface 2180. The on-chip memory 2112' and the additional memory module 2114 may each be considered as a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 2112 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software causes the processor to perform the various functions described above when executed by the corresponding processor. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0184] As discussed above, component 199 may be configured to communicate at least one first transmission with the UE via the first TRP and the second TRP in the mTRP mode. Component 199 may be configured to send an indication of switching to the sTRP mode to the UE. Component 199 may be configured to switch to communicating at least one second transmission with the UE via one of the first TRP or the second TRP in the sTRP mode based on the indication of switching to the sTRP mode. Component 199 may be within processor 2112. Component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. Network entity 2160 may include a variety of components configured for various functions. In one configuration, network entity 2160 includes a component for communicating at least one first transmission with the UE via the first TRP and the second TRP in the mTRP mode. Network entity 2160 may include a component for sending an indication of switching to the sTRP mode to the UE. The network entity 2160 may include a component for switching to communicate at least one second transmission with the UE via one of the first TRP or the second TRP in the sTRP mode based on an indication of switching to the sTRP mode. The network entity 2160 may include a component for sending at least one of a beam indication DCI or a beam indication MAC-CE indicating the mTRP mode using a first unified TCI associated with the first TRP and a second unified TCI associated with the second TRP. The network entity 2160 may include a component for sending an indication of switching to the sTRP mode by sending a scheduling DCI that schedules at least one second transmission. The network entity 2160 may include a component for sending at least one CORESET configuration, the at least one CORESET configuration indicating a first CORESET associated with the first TRP and the first PDCCH for enabling PDCCH repetition, a second CORESET associated with the second TRP and the second PDCCH, and a link between the first PDCCH and the second PDCCH. The network entity 2160 may include a component for sending an indication of switching to the sTRP mode that may include sending a scheduling DCI that schedules at least one second transmission. The network entity 2160 may include a component for switching to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode by suppressing monitoring an inappropriate TCI state for at least one second transmission. The network entity 2160 may include a component for sending an indication of switching to the sTRP mode by sending a scheduling DCI scheduling at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating one PUCCH repetition.The network entity 2160 may include means for sending at least one CORESET configuration indicating a first CORESET associated with a first TRP and a first PDCCH for enabling PDCCH repetition, a second CORESET associated with a second TRP and a second PDCCH, and a link between the first PDCCH and the second PDCCH. The network entity 2160 may include means for sending a scheduling DCI scheduling at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating a number of PUCCH repetitions. The means may be a component 199 of the network entity 2160 configured to perform the functions recited by the means.

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

[0186] The foregoing 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 apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "at ..." do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an instant action in response to the occurrence of an action or during the occurrence of an action, but only mean that if the condition is met, the action will occur without a specific or instantaneous time constraint to make the action occur. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having an advantage 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, and 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 contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0187] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0188] A device configured to "output" data (such as sending, signaling, or messages) may, for example, send the data using a transceiver, or may transmit the data to a device that sends the data. A device configured to "obtain" data (such as sending, signaling, or messages) may, for example, receive the data using a transceiver, or may obtain the data from a device that receives the data.

[0189] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0190] Aspect 1 is a method for wireless communication at a UE, wherein the method may include: communicating at least one first transmission with a network node via a first TRP and a second TRP in an mTRP mode. The method may include: obtaining an indication to switch to an sTRP mode. The method may include: switching to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode.

[0191] Aspect 2 is a method according to Aspect 1, wherein the method may include: receiving at least one of a beam indication DCI or a beam indication MAC-CE indicating the mTRP mode using a first unified transmission configuration indicator TCI associated with the first TRP and a second unified TCI associated with the second TRP.

[0192] Aspect 3 is a method according to aspect 2, wherein the first TCI is associated with a first PDSCH and the second TCI is associated with a second PDSCH, or wherein the first TCI is associated with a first PUSCH and the second TCI is associated with a second PUSCH.

[0193] Aspect 4 is a method according to any one of aspects 2 to 3, wherein obtaining the indication of switching to the sTRP mode may include: receiving a scheduling DCI that schedules the at least one second transmission. The scheduling DCI may include a field including the indication of switching to the sTRP mode. The indication of switching to the sTRP mode may select a suitable TCI state in the first TCI and the second TCI for the at least one second transmission.

[0194] Aspect 5 is a method according to aspect 4, wherein the field may include at least one of an SRS resource set indicator field or a TCI selection indicator field used for the indication.

[0195] Aspect 6 is a method according to any one of Aspects 4 to 5, wherein the field may include a TDRA field, and the TDRA field includes the indication of switching to the sTRP mode.

[0196] Aspect 7 is a method according to aspect 6, wherein the TDRA field may include at least one of a time slot offset value, a SLIV, or a TCI selection indicator including the indication associated with the at least one second transmission.

[0197] Aspect 8 is a method according to any one of aspects 4 to 7, wherein the field comprises a TCI field, and the TCI field comprises a dedicated bit including the indication.

[0198] Aspect 9 is a method according to Aspect 2, wherein the method may include: receiving at least one CORESET configuration, the at least one CORESET configuration indicating a first CORESET associated with the first TRP and the first PDCCH for enabling PDCCH repetition, a second CORESET associated with the second TRP and the second PDCCH, and a link between the first PDCCH and the second PDCCH.

[0199] Aspect 10 is a method according to aspect 9, wherein obtaining the indication of switching to the sTRP mode may include: receiving a scheduling DCI that schedules the at least one second transmission. The scheduling DCI may include a field including the indication of switching to the sTRP mode. The indication of switching to the sTRP mode may indicate an inappropriate TCI state in the first TCI and the second TCI.

[0200] Aspect 11 is a method according to any one of Aspects 9 to 10, wherein switching to communicate the at least one second transmission with the network node via one of the first TRP or the second TRP in the s TRP mode may include: suppressing monitoring of the inappropriate TCI state for the at least one second transmission.

[0201] Aspect 12 is a method according to aspect 2, wherein obtaining the indication of switching to the sTRP mode may include: receiving a scheduling DCI that schedules the at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating a PUCCH repetition. The scheduling DCI may include the indication of switching to the sTRP mode. The indication may include at least one of a PUCCH resource indicator, a TCI selection indicator, or a dedicated field of the scheduling DCI that selects a suitable TCI state in the first TCI and the second TCI for the at least one second transmission.

[0202] Aspect 13 is a method according to aspect 2, wherein the method may include: receiving a scheduling DCI that schedules the at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating a PUCCH repetition. Obtaining the indication to switch to the sTRP mode may include: obtaining a condition for selecting a suitable TCI state in the first TCI and the second TCI for the at least one second transmission in response to the PUCCH resource indicator indicating the one PUCCH repetition.

[0203] Aspect 14 is a method according to aspect 1, wherein the method may include: receiving at least one of a beam indication DCI or a beam indication MAC-CE that uses a first unified TCI associated with the first TRP and the second TRP to indicate the mTRP mode. Obtaining the indication to switch to the sTRP mode may include: obtaining a condition indicating an inappropriate TRP in the first TRP and the second TRP for the at least one second transmission in response to at least one of the beam indication DCI or the beam indication MAC-CE using the first TCI indicator associated with the first TRP and the second TRP to indicate the mTRP mode.

[0204] Aspect 15 is a method according to aspect 14, wherein the method may include: receiving at least one CORESET configuration, the at least one CORESET configuration indicating a first CORESET associated with the first TRP and the first PDCCH for enabling PDCCH repetition, a second CORESET associated with the second TRP and the second PDCCH, and a link between the first PDCCH and the second PDCCH. Switching to communicate the at least one second transmission may include: suppressing monitoring the inappropriate TRP for the at least one second transmission.

[0205] Aspect 16 is a method according to aspect 14, wherein the method may include: scheduling a scheduling DCI for the at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating the number of PUCCH repetitions. Switching to communicate the at least one second transmission may include sending the PUCCH without repeating using the inappropriate TRP.

[0206] Aspect 17 is a method for wireless communication at a network node, wherein the method may include: communicating at least one first transmission with a UE via a first TRP and a second TRP in mTRP mode. The method may include: sending an indication to the UE to switch to sTRP mode. The method may include: switching to communicating at least one second transmission with the UE via one of the first TRP or the second TRP in the sTRP mode based on the indication to switch to the sTRP mode.

[0207] Aspect 18 is a method according to Aspect 17, wherein the method may include: sending at least one of a beam indication DCI or a beam indication MAC-CE that indicates the mTRP mode using a first unified TCI associated with the first TRP and a second unified TCI associated with the second TRP.

[0208] Aspect 19 is a method according to aspect 18, wherein the first TCI is associated with a first PDSCH and the second TCI is associated with a second PDSCH, or wherein the first TCI is associated with a first PUSCH and the second TCI is associated with a second PUSCH.

[0209] Aspect 20 is a method according to any one of aspects 18 to 19, wherein sending the indication of switching to the sTRP mode may include sending a scheduling DCI that schedules the at least one second transmission. The scheduling DCI may include a field including the indication of switching to the sTRP mode. The indication of switching to the sTRP mode may select a suitable TCI state in the first TCI and the second TCI for the at least one second transmission.

[0210] Aspect 21 is a method according to aspect 20, wherein the field may include at least one of an SRS resource set indicator field or a TCI selection indicator field for the indication.

[0211] Aspect 22 is a method according to any one of Aspects 20 to 21, wherein the field may include a TDRA field, and the TDRA field includes the indication of switching to the sTRP mode.

[0212] Aspect 23 is a method according to aspect 22, wherein the TDRA field may include at least one of a time slot offset value, a SLIV, or a TCI selection indicator including the indication associated with the at least one second transmission.

[0213] Aspect 24 is a method according to aspect 20, wherein the field may include a TCI field, the TCI field including a dedicated bit including the indication.

[0214] Aspect 25 is a method according to Aspect 18, wherein the method may include: sending at least one CORESET configuration, the at least one CORESET configuration indicating a first CORESET associated with the first TRP and the first PDCCH for enabling PDCCH repetition, a second CORESET associated with the second TRP and the second PDCCH, and a link between the first PDCCH and the second PDCCH.

[0215] Aspect 26 is a method according to aspect 25, wherein sending the indication of switching to the sTRP mode may include: sending a scheduling DCI that schedules the at least one second transmission. The scheduling DCI may include a field including the indication of switching to the sTRP mode. The indication of switching to the sTRP mode may indicate an inappropriate TCI state in the first TCI and the second TCI.

[0216] Aspect 27 is a method according to Aspect 26, wherein switching to communicate the at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode may include: suppressing monitoring of the inappropriate TCI state for the at least one second transmission.

[0217] Aspect 28 is a method according to aspect 18, wherein sending the indication of switching to the sTRP mode may include: sending a scheduling DCI that schedules the at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating a PUCCH repetition. The scheduling DCI may include the indication of switching to the sTRP mode. The indication may include at least one of a PUCCH resource indicator, a TCI selection indicator, or a dedicated field of the scheduling DCI that selects a suitable TCI state in the first TCI and the second TCI for the at least one second transmission.

[0218] Aspect 29 is a method according to Aspect 17, wherein the method may include: sending at least one CORESET configuration, the at least one CORESET configuration indicating a first CORESET associated with the first TRP and the first PDCCH for enabling PDCCH repetition, a second CORESET associated with the second TRP and the second PDCCH, and a link between the first PDCCH and the second PDCCH.

[0219] Aspect 30 is a method according to aspect 17, wherein the method may include: sending a scheduling DCI that schedules the at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating a number of PUCCH repetitions.

[0220] Aspect 31 is an apparatus for wireless communication, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and being configured to implement any one of Aspects 1 to 30 based at least in part on information stored in the memory.

[0221] Aspect 32 is the apparatus of aspect 31, further comprising at least one of an antenna or a transceiver coupled to the at least one processor.

[0222] Aspect 33 is an apparatus for wireless communication, comprising means for implementing any one of aspects 1 to 30.

[0223] Aspect 34 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 30.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: communicating at least one first transmission with a network node via a first TRP and a second TRP in a multiple transmit receive point (TRP) (mTRP) mode; Get an indication to switch to single TRP (sTRP) mode; as well as Based on the indication to switch to the sTRP mode, switch to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: Receive at least one of beam indication downlink control information (DCI) or beam indication medium access control (MAC) control element (MAC-CE) indicating the mTRP mode using a first unified transmission configuration indicator (TCI) associated with the first TRP and a second unified TCI associated with the second TRP.

3. An apparatus according to claim 2, wherein the first TCI is associated with a first physical downlink shared channel (PDSCH) and the second TCI is associated with a second PDSCH, or wherein the first TCI is associated with a first physical uplink shared channel (PUSCH) and the second TCI is associated with a second PUSCH.

4. The apparatus of claim 2, wherein to obtain the indication to switch to the sTRP mode, the at least one processor is further configured to: Receive a scheduling DCI that schedules the at least one second transmission, wherein the scheduling DCI includes a field including the indication of switching to the sTRP mode, wherein the indication of switching to the sTRP mode selects a suitable TCI state among the first TCI and the second TCI for the at least one second transmission.

5. The apparatus of claim 4, wherein the field comprises at least one of a sounding reference signal (SRS) resource set indicator field or a TCI selection indicator field for the indication.

6. The apparatus of claim 4, wherein the field comprises a time domain resource allocation (TDRA) field, the time domain resource allocation (TDRA) field comprising the indication of switching to the sTRP mode.

7. The apparatus of claim 6, wherein the TDRA field comprises at least one of a slot offset value, a start and length indicator value (SLIV), or a TCI selection indicator comprising the indication associated with the at least one second transmission.

8. The apparatus of claim 4, wherein the field comprises a TCI field including a dedicated bit that includes the indication.

9. The apparatus of claim 2, wherein the at least one processor is further configured to: Receive at least one control resource set (CORESET) configuration, wherein the at least one control resource set (CORESET) configuration indicates a first CORESET associated with the first TRP and a first physical downlink control channel (PDCCH) for enabling PDCCH repetition, a second CORESET associated with the second TRP and a second PDCCH, and a link between the first PDCCH and the second PDCCH.

10. The apparatus of claim 9, wherein to obtain the indication to switch to the sTRP mode, the at least one processor is further configured to: Receive a scheduling DCI that schedules the at least one second transmission, wherein the scheduling DCI includes a field including the indication of switching to the sTRP mode, wherein the indication of switching to the sTRP mode indicates an inappropriate TCI state in the first TCI and the second TCI.

11. The apparatus of claim 10, wherein to switch to communicating the at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode, the at least one processor is further configured to: The inappropriate TCI state is monitored for the at least one second transmission inhibition.

12. The apparatus of claim 2, wherein to obtain the indication to switch to the sTRP mode, the at least one processor is further configured to: Receive a scheduling DCI that schedules the at least one second transmission, the scheduling DCI including a physical uplink control channel (PUCCH) resource indicator indicating a PUCCH repetition, wherein the scheduling DCI includes the indication to switch to the sTRP mode, wherein the indication includes at least one of the PUCCH resource indicator, the TCI selection indicator, or a dedicated field of the scheduling DCI for selecting a suitable TCI state among the first TCI and the second TCI for the at least one second transmission.

13. The apparatus of claim 2, wherein the at least one processor is further configured to: Receiving a scheduling DCI that schedules the at least one second transmission, the scheduling DCI comprising a PUCCH resource indicator indicating a PUCCH repetition, wherein obtaining the indication to switch to the sTRP mode comprises: A condition is obtained for selecting a suitable TCI state of the first TCI and the second TCI for the at least one second transmission in response to the PUCCH resource indicator indicating the one PUCCH repetition.

14. The apparatus of claim 1, wherein the at least one processor is further configured to: Receiving at least one of a beam indication DCI or a beam indication MAC-CE indicating the mTRP mode using a first unified TCI associated with the first TRP and the second TRP, wherein obtaining the indication to switch to the sTRP mode comprises: Obtaining a condition indicating an inappropriate TRP in the first TRP and the second TRP for the at least one second transmission in response to at least one of the beam indication DCI or the beam indication MAC-CE using the first TCI indicator associated with the first TRP and the second TRP to indicate the mTRP mode.

15. The apparatus of claim 14, wherein the at least one processor is further configured to: Receive at least one CORESET configuration, the at least one CORESET configuration indicating a first CORESET associated with the first TRP and the first PDCCH for enabling PDCCH repetition, a second CORESET associated with the second TRP and the second PDCCH, and a link between the first PDCCH and the second PDCCH, wherein switching to communicate the at least one second transmission includes suppressing monitoring of the inappropriate TRP for the at least one second transmission.

16. The apparatus of claim 14, wherein the at least one processor is further configured to: Receive a scheduling DCI that schedules the at least one second transmission, the scheduling DCI including a PUCCH resource indicator indicating the number of PUCCH repetitions, wherein switching to communicate the at least one second transmission includes sending the PUCCH without repeating using the inappropriate TRP.

17. The apparatus according to claim 1, further comprising: A transceiver is coupled to the at least one processor, wherein communicating the at least one first transmission with the network node comprises communicating the at least one first transmission with the network node using the transceiver.

18. An apparatus for wireless communication at a network node, comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: communicating at least one first transmission with a user equipment (UE) via a first TRP and a second TRP in a multiple transmit reception point (TRP) (mTRP) mode; Sending an indication to the UE to switch to a single TRP (sTRP) mode; as well as Based on the indication to switch to the sTRP mode, switch to communicating with the UE via one of the first TRP or the second TRP in the sTRP mode for at least one second transmission.

19. The apparatus of claim 18, wherein the at least one processor is further configured to: Sending at least one of beam indication downlink control information (DCI) or beam indication medium access control (MAC) control element (MAC-CE) indicating the mTRP mode using a first unified transmission configuration indicator (TCI) associated with the first TRP and a second unified TCI associated with the second TRP.

20. An apparatus according to claim 19, wherein the first TCI is associated with a first physical downlink shared channel (PDSCH) and the second TCI is associated with a second PDSCH, or wherein the first TCI is associated with a first physical uplink shared channel (PUSCH) and the second TCI is associated with a second PUSCH.

21. The apparatus of claim 19, wherein to send the indication to switch to the sTRP mode, the at least one processor is further configured to: Send a scheduling DCI that schedules the at least one second transmission, wherein the scheduling DCI includes a field including the indication of switching to the sTRP mode, wherein the indication of switching to the sTRP mode selects a suitable TCI state among the first TCI and the second TCI for the at least one second transmission.

22. The apparatus of claim 21, wherein the field comprises at least one of a sounding reference signal (SRS) resource set indicator field or a TCI selection indicator field for the indication.

23. The apparatus of claim 21, wherein the field comprises a time domain resource allocation (TDRA) field, the time domain resource allocation (TDRA) field comprising the indication of switching to the sTRP mode.

24. The apparatus of claim 23, wherein the TDRA field comprises at least one of a slot offset value, a start and length indicator value (SLIV), or a TCI selection indicator comprising the indication associated with the at least one second transmission.

25. The apparatus of claim 19, wherein the at least one processor is further configured to: At least one control resource set (CORESET) configuration is sent, and the at least one control resource set (CORESET) configuration indicates a first CORESET associated with the first TRP and a first physical downlink control channel (PDCCH) for enabling PDCCH repetition, a second CORESET associated with the second TRP and a second PDCCH, and a link between the first PDCCH and the second PDCCH.

26. The apparatus of claim 25, wherein to send the indication to switch to the sTRP mode, the at least one processor is further configured to: Send a scheduling DCI that schedules the at least one second transmission, wherein the scheduling DCI includes a field including the indication of switching to the sTRP mode, wherein the indication of switching to the sTRP mode indicates an inappropriate TCI state in the first TCI and the second TCI.

27. The apparatus of claim 26, wherein to switch to communicating the at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode, the at least one processor is further configured to: The inappropriate TCI state is monitored for the at least one second transmission inhibition.

28. The apparatus of claim 19, wherein to send the indication to switch to the sTRP mode, the at least one processor is further configured to: Send a scheduling DCI that schedules the at least one second transmission, the scheduling DCI including a physical uplink control channel (PUCCH) resource indicator indicating a PUCCH repetition, wherein the scheduling DCI includes the indication of switching to the sTRP mode, wherein the indication includes at least one of the PUCCH resource indicator, the TCI selection indicator, or a dedicated field of the scheduling DCI for selecting a suitable TCI state among the first TCI and the second TCI for the at least one second transmission.

29. A method of wireless communication at a user equipment (UE), comprising: communicating at least one first transmission with a network node via a first TRP and a second TRP in a multiple transmit receive point (TRP) (mTRP) mode; Get an indication to switch to single TRP (sTRP) mode; as well as Based on the indication to switch to the sTRP mode, switch to communicating at least one second transmission with the network node via one of the first TRP or the second TRP in the sTRP mode.

30. A method for wireless communication at a network node, comprising: communicating at least one first transmission with a user equipment (UE) via a first TRP and a second TRP in a multiple transmit reception point (TRP) (mTRP) mode; Sending an indication to the UE to switch to a single TRP (sTRP) mode; as well as Based on the indication to switch to the sTRP mode, switch to communicating with the UE via one of the first TRP or the second TRP in the sTRP mode for at least one second transmission.

Images