WO2025043435A1

WO2025043435A1 - Unified transmission configuration indicator selection

Info

Publication number: WO2025043435A1
Application number: PCT/CN2023/115216
Authority: WO
Inventors: Fang Yuan; Yan Zhou
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2023-08-28
Filing date: 2023-08-28
Publication date: 2025-03-06
Anticipated expiration: 2026-02-28

Abstract

Certain aspects of the present disclosure provide techniques for selecting Transmission Configuration Indicator (TCIs) for unified TCI based multiple transmission reception point (mTRP) operations. An example method, performed at a user equipment (UE), includes receiving first signaling that activates multiple TCI states for at least a first control resource set (CORESET) and a second CORESET, wherein the UE is operating in an mTRP mode that utilizes multiple downlink control information (DCI) scheduling, selecting a TCI state to apply to receive DCI in at least one of the first CORESET or the second CORESET before receiving a DCI with a field indicating a TCI state for that CORESET, and processing DCI in the at least one of the first CORESET or the second CORESET using the selected TCI state.

Description

UNIFIED TRANSMISSION CONFIGURATION INDICATOR SELECTION

BACKGROUND

Field of the Disclosure

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for selecting Transmission Configuration Indicator (TCIs) for unified TCI based multiple transmission reception point (mTRP) operations.

Description of Related Art

Wireless communications systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communications systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available wireless communications system resources with those users.

Although wireless communications systems have made great technological advancements over many years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Accordingly, there is a continuous desire to improve the technical performance of wireless communications systems, including, for example: improving speed and data carrying capacity of communications, improving efficiency of the use of shared communications mediums, reducing power used by transmitters and receivers while performing communications, improving reliability of wireless communications, avoiding redundant transmissions and/or receptions and related processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access wireless communications systems, increasing the ability for different types of devices to intercommunicate, increasing the number and type of wireless communications mediums available for use, and the like. Consequently, there exists a need for further improvements in wireless communications systems to overcome the aforementioned technical challenges and others.

SUMMARY

One aspect provides a method for wireless communications at a user equipment (UE) . The method includes receiving first signaling that activates multiple Transmission Configuration Indicator (TCI) states for at least a first control resource set (CORESET) and a second CORESET, wherein the UE is operating in a multiple transmitter receiver point (mTRP) mode that utilizes multiple downlink control information (DCI) scheduling; selecting a TCI state to apply to receive downlink control information (DCI) in at least one of the first CORESET or the second CORESET before receiving a DCI with a field indicating a TCI state for that CORESET; and processing DCI in the at least one of the first CORESET or the second CORESET using the selected TCI state.

Another aspect provides a method for wireless communications at a network entity. The method includes transmitting first signaling that activates, for a user equipment (UE) operating in a multiple transmitter receiver point (mTRP) mode that utilizes multiple downlink control information (DCI) scheduling, multiple Transmission Configuration Indicator (TCI) states for at least a first control resource set (CORESET) and a second CORESET; selecting a TCI state to apply to transmit downlink control information (DCI) in at least one of the first CORESET or the second CORESET before transmitting a DCI with a field indicating a TCI state for that CORESET; and transmitting DCI in the at least one of the first CORESET or the second CORESET using the selected TCI state.

Another aspect provides a method for wireless communications at a user equipment (UE) . The method includes receiving first signaling indicating a switch between a first transmission and reception point (TRP) mode and a second TRP mode; receiving second signaling indicating a Transmission Configuration Indicator (TCI) mode for an operating frequency; and processing a downlink transmission on the operating frequency in accordance with the TCI mode.

Another aspect provides a method for wireless communications at a network entity. The method includes transmitting first signaling indicating for a user equipment (UE) to switch between a first transmission and reception point (TRP) mode and a second TRP mode; transmitting second signaling indicating a Transmission Configuration Indicator (TCI) mode for an operating frequency; and transmitting a downlink transmission on the operating frequency in accordance with the TCI mode.

Other aspects provide: an apparatus operable, configured, or otherwise adapted to perform any one or more of the aforementioned methods and/or those described elsewhere herein; a non-transitory, computer-readable media comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform the aforementioned methods as well as those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the aforementioned methods as well as those described elsewhere herein; and/or an apparatus comprising means for performing the aforementioned methods as well as those described elsewhere herein. By way of example, an apparatus may comprise a processing system, a device with a processing system, or processing systems cooperating over one or more networks.

The following description and the appended figures set forth certain features for purposes of illustration.

BRIEF DESCRIPTION OF DRAWINGS

The appended figures depict certain features of the various aspects described herein and are not to be considered limiting of the scope of this disclosure.

FIG. 1 depicts an example wireless communications network.

FIG. 2 depicts an example disaggregated base station architecture.

FIG. 3 depicts aspects of an example base station and an example user equipment.

FIGS. 4A, 4B, 4C, and 4D depict various example aspects of data structures for a wireless communications network.

FIG. 5 illustrates example single downlink control information (single-DCI) multi transmission reception point (multi-TRP) scenario.

FIG. 6 illustrates an example multi-DCI multi-TRP (mTRP) scenario.

FIG. 7 depicts an example scenario involving mTRP operation.

FIG. 8 depicts example resource allocations for an example scenario involving mTRP operation.

FIGs. 9A and 9B depict an example scenario involving mTRP operation.

FIG. 10 depicts an example timing diagram illustrating a Transmission Configuration Indicator (TCI) selection field.

FIG. 11 depicts an example diagram illustrating TCI selection, in accordance with certain aspects of the present disclosure.

FIG. 12 depicts a call flow diagram, in accordance with certain aspects of the present disclosure.

FIG. 13 depicts another call flow diagram, in accordance with certain aspects of the present disclosure.

FIG. 14 depicts an example diagram illustrating TCI activation signaling with dynamic TRP switching, in accordance with certain aspects of the present disclosure.

FIG. 15 depicts a method for wireless communications.

FIG. 16 depicts a method for wireless communications.

FIG. 17 depicts a method for wireless communications.

FIG. 18 depicts a method for wireless communications.

FIG. 19 depicts aspects of an example communications device.

DETAILED DESCRIPTION

Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for selecting Transmission Configuration Indicator (TCI) states for unified TCI based multiple transmission reception point (mTRP) operations.

In some systems (e.g., according to NR Release 17) , a unified TCI state may indicate, to a user equipment (UE) , a common beam applicable to multiple DL/UL channels. In other words, once a unified TCI state is configured, it can be used for not just a single channel, but for multiple channels/signals simultaneously, which may reduce signalling overhead and latency. For example, a unified TCI state may be applied for a CSI-RS, a CORESET, and a PDSCH. A common beam may also be applied for uplink channels/signals, e.g., a PUSCH, a dedicated PUCCH, and an SRS, depending on how the UE is configured.

In some cases, a UE may communicate with multiple transmission reception points (TRPs) . In some cases, the unified TCI framework may be extended to multiple TRP (mTRP) operation. In such cases, different TCI states may be applied for transmissions to the different TRPs. For example, a UE may be configured with first and second unified TCI states. Unfortunately, there may be some ambiguity regarding which unified TCI state (e.g., or mode) the UE should apply for various scenarios.

For example, in some cases, the UE may be configured to monitor for a downlink control information (DCI) that includes a TCI selection field to indicate selection of at least one unified TCI state from a plurality of (e.g., activated) unified TCI states. The plurality of unified TCI states may be indicated, for example, by a MAC CE and the TCI selection field in a DCI may select one of the TCI states activated by the MAC CE. However, there may be ambiguity regarding which unified TCI state the UE is to use for processing an initial DCI (transmitted after the MAC CE that activates the TCI states) that includes the TCI selection field. This may be because, for example, none of the activated TCI states have been indicated yet.

Aspects of the present disclosure may provide various mechanisms that may help resolve such ambiguities. In some cases, for example, a UE may be configured to determine which unified TCI state to apply based on at least one rule. The mechanisms proposed herein may provide various advantages. For example, the mechanisms proposed herein may provide flexibility in expanding unified TCI framework to mTRP operation, providing enhanced performance with reduced signaling overhead. Enhanced performance may result from the techniques proposed herein allowing a UE and network to be in agreement on which TCI is being used to process a downlink transmission.

Introduction to Wireless Communications Networks

The techniques and methods described herein may be used for various wireless communications networks. While aspects may be described herein using terminology commonly associated with 3G, 4G, and/or 5G wireless technologies, aspects of the present disclosure may likewise be applicable to other communications systems and standards not explicitly mentioned herein.

FIG. 1 depicts an example of a wireless communications network 100, in which aspects described herein may be implemented.

Generally, wireless communications network 100 includes various network entities (alternatively, network elements or network nodes) . A network entity is generally a communications device and/or a communications function performed by a communications device (e.g., a user equipment (UE) , a base station (BS) , a component of a BS, a server, etc. ) . For example, various functions of a network as well as various devices associated with and interacting with a network may be considered network entities. Further, wireless communications network 100 includes terrestrial aspects, such as ground-based network entities (e.g., BSs 102) , and non-terrestrial aspects, such as satellite 140 and aircraft 145, which may include network entities on-board (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipments.

In the depicted example, wireless communications network 100 includes BSs 102, UEs 104, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190, which interoperate to provide communications services over various communications links, including wired and wireless links.

FIG. 1 depicts various example UEs 104, which may more generally include: a cellular phone, smart phone, session initiation protocol (SIP) phone, laptop, personal digital assistant (PDA) , satellite radio, global positioning system, multimedia device, video device, digital audio player, camera, game console, tablet, smart device, wearable device, vehicle, electric meter, gas pump, large or small kitchen appliance, healthcare device, implant, sensor/actuator, display, internet of things (IoT) devices, always on (AON) devices, edge processing devices, or other similar devices. UEs 104 may also be referred to more generally as a mobile device, a wireless device, a wireless communications device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.

BSs 102 wirelessly communicate with (e.g., transmit signals to or receive signals from) UEs 104 via communications links 120. The communications links 120 between BSs 102 and UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a BS 102 and/or downlink (DL) (also referred to as forward link) transmissions from a BS 102 to a UE 104. The communications links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity in various aspects.

BSs 102 may generally include: a NodeB, enhanced NodeB (eNB) , next generation enhanced NodeB (ng-eNB) , next generation NodeB (gNB or gNodeB) , access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission reception point, and/or others. Each of BSs 102 may provide communications coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell, and which may overlap in some cases (e.g., small cell 102’ may have a coverage area 110’ that overlaps the coverage area 110 of a macro cell) . A BS may, for example, provide communications coverage for a macro cell (covering relatively large geographic area) , a pico cell (covering relatively smaller geographic area, such as a sports stadium) , a femto cell (relatively smaller geographic area (e.g., a home) ) , and/or other types of cells.

While BSs 102 are depicted in various aspects as unitary communications devices, BSs 102 may be implemented in various configurations. For example, one or more components of a base station may be disaggregated, including a central unit (CU) , one or more distributed units (DUs) , one or more radio units (RUs) , a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) , or a Non-Real Time (Non-RT) RIC, to name a few examples. In another example, various aspects of a base station may be virtualized. More generally, a base station (e.g., BS 102) may include components that are located at a single physical location or components located at various physical locations. In examples in which a base station includes components that are located at various physical locations, the various components may each perform functions such that, collectively, the various components achieve functionality that is similar to a base station that is located at a single physical location. In some aspects, a base station including components that are located at various physical locations may be referred to as a disaggregated radio access network architecture, such as an Open RAN (O-RAN) or Virtualized RAN (VRAN) architecture. FIG. 2 depicts and describes an example disaggregated base station architecture.

Different BSs 102 within wireless communications network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and/or 5G. For example, BSs 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through first backhaul links 132 (e.g., an S1 interface) . BSs 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN) ) may interface with 5GC 190 through second backhaul links 184. BSs 102 may communicate directly or indirectly (e.g., through the EPC 160 or 5GC 190) with each other over third backhaul links 134 (e.g., X2 interface) , which may be wired or wireless.

Wireless communications network 100 may subdivide the electromagnetic spectrum into various classes, bands, channels, or other features. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, or a subband. For example, 3GPP currently defines Frequency Range 1 (FR1) as including 410 MHz –7125 MHz, which is often referred to (interchangeably) as “Sub-6 GHz” . Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 24, 250 MHz –52, 600 MHz, which is sometimes referred to (interchangeably) as a “millimeter wave” ( “mmW” or “mmWave” ) . A base station configured to communicate using mmWave/near mmWave radio frequency bands (e.g., a mmWave base station such as BS 180) may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

The communications links 120 between BSs 102 and, for example, UEs 104, may be through one or more carriers, which may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and/or other MHz) , and which may be aggregated in various aspects. Carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) .

Communications using higher frequency bands may have higher path loss and a shorter range compared to lower frequency communications. Accordingly, certain base stations (e.g., 180 in FIG. 1) may utilize beamforming 182 with a UE 104 to improve path loss and range. For example, BS 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming. In some cases, BS 180 may transmit a beamformed signal to UE 104 in one or more transmit directions 182’. UE 104 may receive the beamformed signal from the BS 180 in one or more receive directions 182” . UE 104 may also transmit a beamformed signal to the BS 180 in one or more transmit directions 182” . BS 180 may also receive the beamformed signal from UE 104 in one or more receive directions 182’. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. Notably, the transmit and receive directions for BS 180 may or may not be the same. Similarly, the transmit and receive directions for UE 104 may or may not be the same.

Wireless communications network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communications links 154 in, for example, a 2.4 GHz and/or 5 GHz unlicensed frequency spectrum.

Certain UEs 104 may communicate with each other using device-to-device (D2D) communications link 158. D2D communications 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) , a physical sidelink control channel (PSCCH) , and/or a physical sidelink feedback channel (PSFCH) .

EPC 160 may include various functional components, including: a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and/or a Packet Data Network (PDN) Gateway 172, such as in the depicted example. MME 162 may be in communication with a Home Subscriber Server (HSS) 174. MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, MME 162 provides bearer and connection management.

Generally, user Internet protocol (IP) packets are transferred through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation as well as other functions. PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a Packet Switched (PS) streaming service, and/or other IP services.

BM-SC 170 may provide functions for MBMS user service provisioning and delivery. BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and/or may be used to schedule MBMS transmissions. MBMS Gateway 168 may be used to distribute MBMS traffic to the BSs 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and/or may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

5GC 190 may include various functional components, including: an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. AMF 192 may be in communication with Unified Data Management (UDM) 196.

AMF 192 is a control node that processes signaling between UEs 104 and 5GC 190. AMF 192 provides, for example, quality of service (QoS) flow and session management.

Internet protocol (IP) packets are transferred through UPF 195, which is connected to the IP Services 197, and which provides UE IP address allocation as well as other functions for 5GC 190. IP Services 197 may include, for example, the Internet, an intranet, an IMS, a PS streaming service, and/or other IP services.

In various aspects, a network entity or network node can be implemented as an aggregated base station, as a disaggregated base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

FIG. 2 depicts an example disaggregated base station 200 architecture. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that can communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a Non-Real Time (Non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) Framework 205, or both) . A CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DUs 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RUs 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 240.

Each of the units, e.g., the CUs 210, the DUs 230, the RUs 240, as well as the Near-RT RICs 225, the Non-RT RICs 215 and the SMO Framework 205, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communications interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally or alternatively, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

In some aspects, the CU 210 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (e.g., Central Unit –User Plane (CU-UP) ) , control plane functionality (e.g., Central Unit –Control Plane (CU-CP) ) , or a combination thereof. In some implementations, the CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 210 can be implemented to communicate with the DU 230, as necessary, for network control and signaling.

The DU 230 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 240. In some aspects, the DU 230 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, or the like) depending, at least in part, on a functional split, such as those defined by the 3^rd Generation Partnership Project (3GPP) . In some aspects, the DU 230 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 230, or with the control functions hosted by the CU 210.

Lower-layer functionality can be implemented by one or more RUs 240. In some deployments, an RU 240, controlled by a DU 230, 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, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) 240 can 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 and user plane communications with the RU (s) 240 can be controlled by the corresponding DU 230. In some scenarios, this configuration can enable the DU (s) 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO Framework 205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 210, DUs 230, RUs 240 and Near-RT RICs 225. In some implementations, the SMO Framework 205 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 211, via an O1 interface. Additionally, in some implementations, the SMO Framework 205 can communicate directly with one or more RUs 240 via an O1 interface. The SMO Framework 205 also may include a Non-RT RIC 215 configured to support functionality of the SMO Framework 205.

The Non-RT RIC 215 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 225. The Non-RT RIC 215 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 225. The Near-RT RIC 225 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 210, one or more DUs 230, or both, as well as an O-eNB, with the Near-RT RIC 225.

In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 225, the Non-RT RIC 215 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 225 and may be received at the SMO Framework 205 or the Non-RT RIC 215 from non-network data sources or from network functions. In some examples, the Non-RT RIC 215 or the Near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 215 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 205 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .

FIG. 3 depicts aspects of an example BS 102 and a UE 104.

Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340) , antennas 334a-t (collectively 334) , transceivers 332a-t (collectively 332) , which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339) . For example, BS 102 may send and receive data between BS 102 and UE 104. BS 102 includes controller/processor 340, which may be configured to implement various functions described herein related to wireless communications.

Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380) , antennas 352a-r (collectively 352) , transceivers 354a-r (collectively 354) , which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., retrieved from data source 362) and wireless reception of data (e.g., provided to data sink 360) . UE 104 includes controller/processor 380, which may be configured to implement various functions described herein related to wireless communications.

In regards to an example downlink transmission, BS 102 includes a transmit processor 320 that may receive data from a data source 312 and control information from a controller/processor 340. The control information may be for the physical broadcast channel (PBCH) , physical control format indicator channel (PCFICH) , physical HARQ indicator channel (PHICH) , physical downlink control channel (PDCCH) , group common PDCCH (GC PDCCH) , and/or others. The data may be for the physical downlink shared channel (PDSCH) , in some examples.

Transmit processor 320 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor 320 may also generate reference symbols, such as for the primary synchronization signal (PSS) , secondary synchronization signal (SSS) , PBCH demodulation reference signal (DMRS) , and channel state information reference signal (CSI-RS) .

Transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a-332t may process a respective output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from the modulators in transceivers 332a-332t may be transmitted via the antennas 334a-334t, respectively.

In order to receive the downlink transmission, UE 104 includes antennas 352a-352r that may receive the downlink signals from the BS 102 and may provide received signals to the demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.

MIMO detector 356 may obtain received symbols from all the demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller/processor 380.

In regards to an example uplink transmission, UE 104 further includes a transmit processor 364 that may receive and process data (e.g., for the PUSCH) from a data source 362 and control information (e.g., for the physical uplink control channel (PUCCH) ) from the controller/processor 380. Transmit processor 364 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS) ) . The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366 if applicable, further processed by the modulators in transceivers 354a-354r (e.g., for SC-FDM) , and transmitted to BS 102.

At BS 102, the uplink signals from UE 104 may be received by antennas 334a-t, processed by the demodulators in transceivers 332a-332t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information sent by UE 104. Receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to the controller/processor 340.

Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

Scheduler 344 may schedule UEs for data transmission on the downlink and/or uplink.

In various aspects, BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 312, scheduler 344, memory 342, transmit processor 320, controller/processor 340, TX MIMO processor 330, transceivers 332a-t, antenna 334a-t, and/or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 334a-t, transceivers 332a-t, RX MIMO detector 336, controller/processor 340, receive processor 338, scheduler 344, memory 342, and/or other aspects described herein.

In various aspects, UE 104 may likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 362, memory 382, transmit processor 364, controller/processor 380, TX MIMO processor 366, transceivers 354a-t, antenna 352a-t, and/or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller/processor 380, receive processor 358, memory 382, and/or other aspects described herein.

In some aspects, a processor may be configured to perform various operations, such as those associated with the methods described herein, and transmit (output) to or receive (obtain) data from another interface that is configured to transmit or receive, respectively, the data.

FIGS. 4A, 4B, 4C, and 4D depict aspects of data structures for a wireless communications network, such as wireless communications network 100 of FIG. 1.

In particular, FIG. 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, FIG. 4B is a diagram 430 illustrating an example of DL channels within a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of UL channels within a 5G subframe.

Wireless communications systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such systems may also support half-duplex operation using time division duplexing (TDD) . OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth (e.g., as depicted in FIGS. 4B and 4D) into multiple orthogonal subcarriers. Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain with OFDM and/or in the time domain with SC-FDM.

A wireless communications frame structure may be frequency division duplex (FDD) , in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for either DL or UL. Wireless communications frame structures may also be time division duplex (TDD) , in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for both DL and UL.

In FIG. 4A and 4C, the wireless communications frame structure is TDD where D is DL, U is UL, and X is flexible for use between DL/UL. UEs may be configured with a slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI) , or semi-statically/statically through radio resource control (RRC) signaling) . In the depicted examples, a 10 ms frame is divided into 10 equally sized 1 ms subframes. Each subframe may include one or more time slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot format. Subframes may also include mini-slots, which generally have fewer symbols than an entire slot. Other wireless communications technologies may have a different frame structure and/or different channels.

In certain aspects, the number of slots within a subframe is based on a slot configuration and a numerology. For example, for slot configuration 0, different numerologies (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols/slot and 2μ slots/subframe. The subcarrier spacing and symbol length/duration are a function of the numerology. The subcarrier spacing may be equal to 2^μ×15 kHz, where μ is the numerology 0 to 5. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=5 has a subcarrier spacing of 480 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGS. 4A, 4B, 4C, and 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

As depicted in FIGS. 4A, 4B, 4C, and 4D, a resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.

As illustrated in FIG. 4A, some of the REs carry reference (pilot) signals (RS) for a UE (e.g., UE 104 of FIGS. 1 and 3) . The RS may include demodulation RS (DMRS) and/or channel state information reference signals (CSI-RS) for channel estimation at the UE.The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and/or phase tracking RS (PT-RS) .

FIG. 4B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) , each CCE including, for example, nine RE groups (REGs) , each REG including, for example, four consecutive REs in an OFDM symbol.

A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE (e.g., 104 of FIGS. 1 and 3) to determine subframe/symbol timing and a physical layer identity.

A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.

Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DMRS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block. The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and/or paging messages.

As illustrated in FIG. 4C, some of the REs carry DMRS (indicated as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE may transmit DMRS for the PUCCH and DMRS for the PUSCH. The PUSCH DMRS may be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. UE 104 may transmit sounding reference signals (SRS) . The SRS may be transmitted, for example, in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

FIG. 4D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and HARQ ACK/NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.

Introduction to Unified TCI Types

As noted above, a unified TCI state may indicate a common beam applicable to multiple DL/UL channels. In other words, once a unified TCI state is configured, it can be used for not just a single channel, but for multiple channels/signals simultaneously, which may reduce signalling overhead and latency. For example, a unified TCI state may be applied for a CSI-RS, a CORESET, and a PDSCH. A common beam may also be applied for uplink channels/signals, e.g., a PUSCH, a dedicated PUCCH, and an SRS, depending on how the UE is configured

Various types of unified TCI may be defined. For example, unified TCI types may include:

Type 1: Joint downlink (DL) /UL common TCI state to indicate a common beam; for at least one DL channel/reference signal (RS_plus at least one UL channel/RS

Type 2: Separate DL common TCI state to indicate a common beam for more than one DL channel/RS;

Type 3: Separate UL common TCI state to indicate a common beam for more than one UL channel/RS;

Type 4: Separate DL single channel/RS TCI state to indicate a beam for a single DL channel/RS; and

Type 5: Separate UL single channel/RS TCI state to indicate a beam for a single UL channel/RS.

Example Multi-TRP Scenarios

In certain wireless communication systems (e.g., Release 16 system) , a multi transmission reception point (multi-TRP) operation was introduced to increase system capacity as well as reliability. In some cases, as illustrated in the scenario 500 of FIG. 5, multi-TRP transmissions are configured based on a single downlink control information (single-DCI) . In some cases, as illustrated in the scenario 500 of FIG. 6, multi-TRP transmissions are configured based on multiple DCIs (multi-DCI) .

Referring back to FIG. 5, a single DCI (transmitted via a physical downlink control channel (PDCCH) from a first TRP (e.g., TRP 1) schedules a physical downlink shared channel (PDSCH) (e.g., PDSCH layer 1) from the first TRP and a PDSCH (e.g., PDSCH layer 2) from a second TRP (e.g., TRP 2) .

In some cases, the multi-TRP operation configured based on the single DCI communication is suited for deployments with an ideal backhaul or a backhaul with a small delay, and involves various transmission schemes. The transmissions schemes include a spatial division multiplexing (SDM) scheme, a frequency division multiplexing (FDM) scheme, and/or a time division multiplexing (TDM) scheme.

In some cases, per the SDM scheme (also known as a non-coherent joint transmission (NCJT) ) , a first set of layers are transmitted from the first TRP and a second set of layers are transmitted from the second TRP. These transmissions utilize a same frequency domain resource allocation (FDRA) and a time division resource allocation (TDRA) .

In some cases, per the FDM scheme, transmissions from the first TRP and the second TRP have a same rank and a same code word (CW) , but with different FDRAs across the first TRP and the second TRP.

In some cases, per the TDM scheme, transmissions from the first TRP and the second TRP have a same rank and a same CW, but with different TDRAs across the first TRP and the second TRP.

In some cases, the PDSCH to a user equipment (UE) is sent in multiple parts. For example, the first TRP sends a first part of the PDSCH (e.g., on the first set of layers with a first set of FDRA and a first set of TDRA) to the UE and the second TRP sends a second part of the PDSCH (e.g., on a second set of layers with a second set of FDRA and a second set of TDRA) to the UE.

Referring back to FIG. 6, each DCI schedules an individual PDSCH in a multi-TRP multi-DCI scenario. For example, a first DCI (e.g., DCI 1) from a first TRP (e.g., TRP 1) (e.g., transmitted in a first PDCCH) schedules a first PSDCH (e.g., PDSCH 1) from the first TRP, while a second DCI (e.g., DCI 2) from a second TRP (e.g., TRP 2) (e.g., transmitted in a second PDCCH) schedules a second PSDCH (e.g., PDSCH 2) from the second TRP. The two scheduled PDSCHs may be overlapped, non-overlapped, or partially overlapped in a frequency domain or a time domain.

Overview of Unified TCI for mTRP

In some cases, the unified TCI framework may be extended to multiple TRP (mTRP) operation. In such cases, different TCI states may be applied for transmissions to and from the different TRPs.

For example, scenario 700 of FIG. 7 depicts a multi-TRP scenario in which a UE communicates with a first TRP (TRP A) using a first TCI state and with a second TRP (TRP B) using a second TCI state. As shown in FIG. 7, time division multiplexing (TDM) may be used for such communications, for example, where the UE communicates with different TRPs at different times. For example, as illustrated, the TRPs may use TDM with cyclic mapping or sequential mapping.

Scenario 800 of FIG. 8 depicts example resource allocations for the multi-TRP scenario illustrated in FIG. 7. FIG. 8 illustrates an example of how a single DCI (S-DCI) for multi-TRP PDSCH may be used for different multiplexing modes. These mode may include spatial division multiplexing (SDM) where overlapping time/frequency resources may be used to communicate with different TRPs but with spatial filtering, frequency division multiplexing (FDM) in which different frequency resources are used to communicate with different TRPs, or TDM in which different time resources are used to communicate with different TRPs. FIG. 8 also illustrates that a multiple DCI (mDCI) for multi-TRP PDSCH may indicate different resources, which may include resources for demodulation reference signals (DMRS) .

Scenario 900A and 900B of FIGs. 9A and 9B depict multi-TRP scenarios. FIG. 9A illustrates how TDM may be used for physical uplink control channel (PUCCH) repetition. FIG. 9B further illustrates how a single frequency network (SFN) may use SDM for physical uplink shared channel (PUSCH) and/or PUCCH.

Aspects Related to Unified TCI Selection for mTRP

As described above, different TCI states may be applied for transmissions to and from different TRPs. Unfortunately, in some scenarios, there may be some ambiguity regarding which unified TCI state the UE should apply for which TRP. In such cases, a UE may not know what unified TCI state to apply when processing a downlink transmission from a TRP.

Aspects of the present disclosure provide mechanisms that help resolve such ambiguity and extend unified TCI framework for indication of multiple downlink and uplink TCI states in various scenarios. These mechanisms may be especially useful in multiple transmission reception point (TRP) scenarios.

In some cases, for unified TCI framework extension (e.g., for single DCI (S-DCI) based multi-TRP (mTRP) ) , certain DCI formats may include a TCI selection field TCI selection field to indicate which unified TCI state a UE is to apply to which TRP transmission. For example, a 2-bit TCI selection field may be configured by RRC to be present in a DCI format 1_1 and/or DCI format 1_2 that schedules/activates physical downlink shared channel (PDSCH) reception (e.g., including dynamic PDSCH and semi-persistent scheduling (SPS) PDSCH) according to certain criteria.

The selection field may include a 2-bit codepoint that indicates which unified TCI state a UE is to apply. For example, in some cases, if the TCI selection field indicates codepoint "00" , the UE may apply the first one of two indicated joint/DL TCI states to all PDSCH demodulation reference signal (DMRS) port (s) of corresponding PDSCH transmission occasions (s) scheduled/activated by the DCI.

In some cases, if TCI selection field indicates codepoint "01" , the UE may apply the second one of two indicated joint/DL TCI states to all PDSCH DMRS port (s) of corresponding PDSCH transmission occasions (s) scheduled/activated by the DCI. In some cases, if the TCI selection field indicates codepoint "10" , the UE may apply both indicated joint/DL TCI states to the PDSCH reception scheduled/activated by the DCI format. In some cases, the codepoint "11" of the TCI selection field may be unused, or may be reserved to indicate certain functionality or information.

FIG. 10 depicts an example timing diagram 1000, illustrating operations involving a TCI selection field.

As shown at 1002, a network entity (e.g., a gNB) may transmit, to a UE, DCI indicating 2 unified TCIs. The UE may transmit an acknowledgement (ACK) of the DCI, as shown at 1004. As shown at 1006, the gNB may then transmit a DCI of a certain format (e.g., DCI 1_1 or DCI 1_2) which may include a TCI selection field. If present, the TCI selection field may indicate to use one or two of the TCI states (indicated at 1002) for a scheduled PDSCH transmission.

As shown at 1008, the gNB may transmit the PDSCH using the one or two of the indicated TCI, in accordance with the TCI selection field. The UE may process the PDSCH transmission PDSCH using the one or two of the TCIs, as indicated in the TCI selection field. The UE may transmit ACK information in response to the PDSCH transmission, as illustrated at 1010.

In some cases, the presence of the TCI selection field in a DL DCI may be RRC-configured (e.g., in scenarios involving a unified TCI framework for mTRP operation) . This may help the UE know when it should monitor for a DCI format that contains a TCI selection field.

As noted above, however, there may be some ambiguity in processing an initial downlink transmission from a TRP after a MAC CE has activated multiple TCI states, but before one of the activated TCI states has been selected. For example, this initial downlink transmission may be a DCI containing the TCI selection field.

FIG. 11 depicts an example diagram illustrating TCI indication downlink control information (DCI) .

MAC CEs may be used to activate multiple TCI states for each control resource set (CORESET) associated with each TRP. As illustrated at 1102 and 1152, for a first TRP/CORESET pool index 1108 and a second TRP/CORESET pool index 1158, respectively, a network entity (e.g., a gNB) may use a medium access control (MAC) control element (CE) to activate multiple (e.g., X) TCIs for each TRP /CORESET pool index.

As illustrated at 1104 and 1154, respectively, the network entity may use DCI (e.g., a TCI Indication DCI) from a particular CORESET pool index to select a single TCI (e.g., from the X activated TCIs) for that CORESET pool index. The selected TCI state may be used for the associated CORESET and PDCCH/PDSCH transmissions, illustrated at 1106 and 1156.

However, there may be ambiguity regarding which TCI should be used for a CORESET for processing the TCI Indication DCI (e.g., especially when a previous TCI has not been used for that TRP) . For example, it may not be clear what TCI state to use for the initial DCI that includes the TCI selection field (e.g., the DCIs at 1104 and/or 1154) . Aspects of the present disclosure, however, may help resolve such ambiguity.

FIG. 12 depicts a call flow diagram 1200, in accordance with certain aspects of the present disclosure. In some aspects, the UE shown in FIG. 12 (and/or FIG. 13) may be an example of the UE 104 depicted and described with respect to FIG. 1 and 3. In some aspects, the network entity shown in FIG. 12 (and/or FIG. 13) may be an example of the BS 102 (e.g., a gNB) depicted and described with respect to FIG. 1 and 3 or a disaggregated base station depicted and described with respect to FIG. 2.

As illustrated at 1202, the UE may receive, from a network entity (e.g., a base station which may include multiple TRPs illustrated as TRP1 and TRP2) , signaling that activates multiple TCI states for at least a first CORESET and a second CORESET. For example, one or more MAC-CEs may activate multiple TCI states for a first CORESET associated with a first CORESET pool index and a second CORESET associated with a second CORESET pool index.

As illustrated at 1204, the UE may select a TCI state to apply to receive DCI in at least one of the first CORESET or the second CORESET, before receiving a DCI with a field indicating a TCI state for that CORESET.

For example, as illustrated at 1206, the UE may apply the selected TCI state to receive a DCI including a TCI selection field, in at least one of the first CORESET or the second CORESET.

As illustrated at 1208, after receiving the DCI at 1206, the UE may process a PDSCH using the TCI state indicated in the TCI selection field of the DCI.

The exact rule or rule used to determine what TCI state to use for an initial DCI transmission after TCI state activation (but before TCI selection) may vary.

In some aspects, an initial TCI indication (e.g., indicating a unified TCI framework for mTRP operations) may be provided for a new TRP, at the start of mDCI mTRP unified TCI mode operations. In some cases, such an initial TCI indication may be provided after initial access, and the initial TCI indication may indicate the TCI for a first TRP (e.g., before a second TRP is added) . In some cases, such an initial TCI indication may be provided after switching to an mDCI mTRP unified TCI mode from an sDCI sTRP unified TCI mode (e.g., before a second TRP is added) .

In some aspects, a TCI selection rule may be defined at least for a CORESET pool index before any TCI indication takes effects. For example, such a TCI selection rule may specify that the first activated TCI or the activated TCI having a lowest ID for the CORESET pool index is to be applied until any TCI indicated for the CORESET pool index takes effect.

In some aspects, a DCI from one CORESET pool index may indicate a TCI for the other CORESET pool index. In some aspects, the TRP of a first CORESET pool index may use the TCI of another (e.g., a second) CORESET pool index until any TCI indicated for the first CORESET pool index takes effect.

In some aspects, the first TCI activation MAC-CE may activate only one TCI for a CORESET pool index (X = 1 activated TCI) until any TCI indicated for the CORESET pool index takes effect. In such cases, for example, since there is only one activated TCI, the TCI selection by DCI may be ignored.

In some cases, there may be some ambiguity on what TCI mode to apply for an operation frequency (e.g., a component carrier (CC) or bandwidth part (BWP) ) on a switch between a first TRP mode and a second TRP mode. For example, it may not be clear what TCI mode to apply when dynamically switching between an sTRP mode and an sDCI-based mTRP unified TCI mode.

FIG. 13 depicts a call flow diagram 1300 with dynamic switching between TRP modes, in accordance with certain aspects of the present disclosure.

As illustrated at 1302, a network entity (e.g., a base station which may include multiple TRPs illustrated as TRP1 and TRP2) may transmit a TRP mode switch indication, indicating a switch between a first TRP mode and second TRP mode. As illustrated at 1304, a UE may switch between the first TRP mode and the second TRP mode based on the TRP mode switch indication.

As illustrated at 1306, the network entity may transmit a MAC-CE indicating a TCI mode for an operating frequency.

As illustrated at 1308, the UE may process a downlink transmission from the network entity on the operating frequency and in accordance with the TCI mode.

In some aspects, a UE may switch between an sTRP mode and an sDCI based mTRP unified TCI mode (e.g., an mTRP mode that that utilizes multiple downlink control information (DCI) scheduling) . Such a switch may be based on signaling from a network entity.

For example, in some aspects, a field in a TCI state activation command may be used. For example, a MAC-CE conveying such a command may (e.g., explicitly) indicate that an operating frequency (e.g., a component carrier (CC) and/or bandwidth part (BWP) is operating (e.g., or is to operate) in a unified TCI framework for an sTRP unified TCI mode or a unified TCI framework extension for an s-DCI based mTRP mode (e.g., an mTRP mode that utilizes single DCI scheduling) . Such modes may be defined in certain wireless communications standards.

This may be understood with reference to the example diagram 1400 of FIG. 14, illustrating TCI activation signaling that indicates dynamic TRP switching.

As illustrated at 1402, a TCI activation MAC-CE may include a field for dynamic TRP switching that indicates a switch to an mTRP mode. As illustrated at 1404, for example, a UE may switch (based on the MAC-CE) to an s-DCI based mTRP mode, and may process/receive a downlink transmission (e.g., a PDSCH) using that mode (e.g., on an associated operating frequency) .

As illustrated at 1452, a TCI activation MAC-CE may include a field for dynamic TRP switching that indicates a switch to an sTRP mode. As illustrated at 1454, for example, a UE may switch (based on the MAC-CE) to an sTRP mode, and may process/receive a downlink transmission (e.g., a PDSCH) using that sTRP mode (e.g., on an associated operating frequency) .

Other types of signaling may also be used to indicate what type of TCI mode should be used after a dynamic TRP mode switch. For example, a field in radio resource control (RRC) signaling may (e.g., explicitly) indicate that a CC and/or BWP is operating (e.g., or is to operate) in a unified TCI framework for an sTRP unified TCI mode or a unified TCI framework extension for an s-DCI based mTRP mode (e.g., an mTRP mode that utilizes single DCI scheduling) .

In some cases, a UE may be RRC configured with unified TCI states (e.g., via dl-OrJointTCI-StateList or TCI-UL-State) . In such cases, the UE may determine that an operating frequency (e.g., CC/BWP) is operated in a dynamic TRP mode switch for S-DCI based MTRP if a TCI state activation command (such as e Rel-18 TCI activation MAC-CE) in which at least one activated TCI codepoint is mapped with both first and second unified (joint/DL/UL) TCI states is received and applied to the CC/BWP. Similarly, a UE may determine that an operating frequency (e.g., a CC/BWP) is operated in single TRP only mode if an TCI state activation command (Rel-18 TCI activation MAC-CE MAC-CE) in which all activated TCI codepoint (s) is mapped with either only the first joint/DL/UL TCI state (s) or only the second joint/DL/UL TCI state (s) is received and applied to the CC/BWP.

Example Operations

FIG. 15 shows an example of a method 1500 of wireless communications at a user equipment (UE) , such as a UE 104 of FIGS. 1 and 3.

Method 1500 begins at step 1505 with receiving first signaling that activates multiple Transmission Configuration Indicator (TCI) states for at least a first control resource set (CORESET) and a second CORESET, wherein the UE is operating in a multiple transmitter receiver point (mTRP) mode that utilizes multiple downlink control information (DCI) scheduling. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference to FIG. 19.

Method 1500 then proceeds to step 1510 with selecting a TCI state to apply to receive downlink control information (DCI) in at least one of the first CORESET or the second CORESET before receiving a DCI with a field indicating a TCI state for that CORESET. In some cases, the operations of this step refer to, or may be performed by, circuitry for selecting and/or code for selecting as described with reference to FIG. 19.

Method 1500 then proceeds to step 1515 with processing DCI in the at least one of the first CORESET or the second CORESET using the selected TCI state. In some cases, the operations of this step refer to, or may be performed by, circuitry for processing and/or code for processing as described with reference to FIG. 19.

In some aspects, the selecting comprises selecting, for the second CORESET, a TCI state, from the multiple TCI states, indicated for the first CORESET.

In some aspects, the method 1500 further includes receiving second signaling indicating the UE to switch from a single TRP (sTRP) mode to the mTRP mode. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference to FIG. 19.

In some aspects, the method 1500 further includes switching from the sTRP mode to the mTRP mode, based on the second signaling. In some cases, the operations of this step refer to, or may be performed by, circuitry for switching and/or code for switching as described with reference to FIG. 19.

In some aspects, the selection is based on a selection rule.

In some aspects, the selection rule dictates use of a first activated TCI state or an activated TCI state of a lowest ID for a CORESET pool index.

In some aspects, the selecting comprises selecting, for the second CORESET, a TCI state, from the multiple TCI states, indicated in a DCI received in the first CORESET.

In some aspects, the TCI state indicated in a DCI received in the first CORESET is used for the second CORESET until a TCI state indicated for the second CORESET takes effect.

In some aspects, the first signaling comprises: a first medium access control (MAC) control element (CE) that activates a single TCI state for at least the first CORESET; and the selecting comprises selecting the single TCI state for at least the first CORESET.

In some aspects, the single TCI state is used for the first CORESET until a TCI state indicated for the first CORESET takes effect.

In one aspect, method 1500, or any aspect related to it, may be performed by an apparatus, such as communications device 1900 of FIG. 19, which includes various components operable, configured, or adapted to perform the method 1500. Communications device 1900 is described below in further detail.

Note that FIG. 15 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

FIG. 16 shows an example of a method 1600 of wireless communications at a network entity, such as a BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.

Method 1600 begins at step 1605 with transmitting first signaling that activates, for a user equipment (UE) operating in a multiple transmitter receiver point (mTRP) mode that utilizes multiple downlink control information (DCI) scheduling, multiple Transmission Configuration Indicator (TCI) states for at least a first control resource set (CORESET) and a second CORESET. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference to FIG. 19.

Method 1600 then proceeds to step 1610 with selecting a TCI state to apply to transmit downlink control information (DCI) in at least one of the first CORESET or the second CORESET before transmitting a DCI with a field indicating a TCI state for that CORESET. In some cases, the operations of this step refer to, or may be performed by, circuitry for selecting and/or code for selecting as described with reference to FIG. 19.

Method 1600 then proceeds to step 1615 with transmitting DCI in the at least one of the first CORESET or the second CORESET using the selected TCI state. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference to FIG. 19.

In some aspects, the method 1600 further includes transmitting second signaling indicating the UE to switch from a single TRP (sTRP) mode to the mTRP mode. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference to FIG. 19.

In some aspects, the selection is based on a selection rule.

In some aspects, the selecting comprises selecting, for the second CORESET, a TCI state, from the multiple TCI states, indicated in a DCI transmitted in the first CORESET.

In some aspects, the TCI state indicated in a DCI transmitted in the first CORESET is used for the second CORESET until a TCI state indicated for the second CORESET takes effect.

In one aspect, method 1600, or any aspect related to it, may be performed by an apparatus, such as communications device 1900 of FIG. 19, which includes various components operable, configured, or adapted to perform the method 1600. Communications device 1900 is described below in further detail.

Note that FIG. 16 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

FIG. 17 shows an example of a method 1700 of wireless communications at a user equipment (UE) , such as a UE 104 of FIGS. 1 and 3.

Method 1700 begins at step 1705 with receiving first signaling indicating a switch between a first transmission and reception point (TRP) mode and a second TRP mode. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference to FIG. 19.

Method 1700 then proceeds to step 1710 with receiving second signaling indicating a Transmission Configuration Indicator (TCI) mode for an operating frequency. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference to FIG. 19.

Method 1700 then proceeds to step 1715 with processing a downlink transmission on the operating frequency in accordance with the TCI mode. In some cases, the operations of this step refer to, or may be performed by, circuitry for processing and/or code for processing as described with reference to FIG. 19.

In some aspects, the operating frequency comprises at least one of a component carrier (CC) or a bandwidth part (BWP) .

In some aspects, the first TRP mode comprises a single TRP (sTRP) mode; and the second TRP mode comprises a multiple TRP (mTRP) mode that utilizes single downlink control information (DCI) scheduling.

In some aspects, the second signaling indicates whether the operating frequency is operating in a unified TCI framework for the sTRP mode or a unified TCI framework extension for the mTRP mode that utilizes single DCI scheduling.

In some aspects, the second signaling comprises a field in a TCI state activation command.

In some aspects, the second signaling comprises radio resource control (RRC) signaling.

In some aspects, the method 1700 further includes switching between the first TRP mode and the second TRP mode, based on the first signaling. In some cases, the operations of this step refer to, or may be performed by, circuitry for switching and/or code for switching as described with reference to FIG. 19.

In one aspect, method 1700, or any aspect related to it, may be performed by an apparatus, such as communications device 1900 of FIG. 19, which includes various components operable, configured, or adapted to perform the method 1700. Communications device 1900 is described below in further detail.

Note that FIG. 17 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

FIG. 18 shows an example of a method 1800 of wireless communications at a network entity, such as a BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.

Method 1800 begins at step 1805 with transmitting first signaling indicating for a user equipment (UE) to switch between a first transmission and reception point (TRP) mode and a second TRP mode. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference to FIG. 19.

Method 1800 then proceeds to step 1810 with transmitting second signaling indicating a Transmission Configuration Indicator (TCI) mode for an operating frequency. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference to FIG. 19.

Method 1800 then proceeds to step 1815 with transmitting a downlink transmission on the operating frequency in accordance with the TCI mode. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference to FIG. 19.

In one aspect, method 1800, or any aspect related to it, may be performed by an apparatus, such as communications device 1900 of FIG. 19, which includes various components operable, configured, or adapted to perform the method 1800. Communications device 1900 is described below in further detail.

Note that FIG. 18 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

Example Communications Device (s)

FIG. 19 depicts aspects of an example communications device 1900. In some aspects, communications device 1900 is a user equipment, such as UE 104 described above with respect to FIGS. 1 and 3. In some aspects, communications device 1900 is a network entity, such as BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.

The communications device 1900 includes a processing system 1905 coupled to the transceiver 1975 (e.g., a transmitter and/or a receiver) . In some aspects (e.g., when communications device 1900 is a network entity) , processing system 1905 may be coupled to a network interface 1985 that is configured to obtain and send signals for the communications device 1900 via communication link (s) , such as a backhaul link, midhaul link, and/or fronthaul link as described herein, such as with respect to FIG. 2. The transceiver 1975 is configured to transmit and receive signals for the communications device 1900 via the antenna 1980, such as the various signals as described herein. The processing system 1905 may be configured to perform processing functions for the communications device 1900, including processing signals received and/or to be transmitted by the communications device 1900.

The processing system 1905 includes one or more processors 1910. In various aspects, the one or more processors 1910 may be representative of one or more of receive processor 358, transmit processor 364, TX MIMO processor 366, and/or controller/processor 380, as described with respect to FIG. 3. In various aspects, one or more processors 1910 may be representative of one or more of receive processor 338, transmit processor 320, TX MIMO processor 330, and/or controller/processor 340, as described with respect to FIG. 3. The one or more processors 1910 are coupled to a computer-readable medium/memory 1940 via a bus 1970. In certain aspects, the computer-readable medium/memory 1940 is configured to store instructions (e.g., computer-executable code) that when executed by the one or more processors 1910, cause the one or more processors 1910 to perform the method 1500 described with respect to FIG. 15, or any aspect related to it; the method 1600 described with respect to FIG. 16, or any aspect related to it; the method 1700 described with respect to FIG. 17, or any aspect related to it; and the method 1800 described with respect to FIG. 18, or any aspect related to it. Note that reference to a processor performing a function of communications device 1900 may include one or more processors 1910 performing that function of communications device 1900.

In the depicted example, computer-readable medium/memory 1940 stores code (e.g., executable instructions) , such as code for receiving 1945, code for selecting 1950, code for processing 1955, code for switching 1960, and code for transmitting 1965. Processing of the code for receiving 1945, code for selecting 1950, code for processing 1955, code for switching 1960, and code for transmitting 1965 may cause the communications device 1900 to perform the method 1500 described with respect to FIG. 15, or any aspect related to it; the method 1600 described with respect to FIG. 16, or any aspect related to it; the method 1700 described with respect to FIG. 17, or any aspect related to it; and the method 1800 described with respect to FIG. 18, or any aspect related to it.

The one or more processors 1910 include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium/memory 1940, including circuitry for receiving 1915, circuitry for selecting 1920, circuitry for processing 1925, circuitry for switching 1930, and circuitry for transmitting 1935. Processing with circuitry for receiving 1915, circuitry for selecting 1920, circuitry for processing 1925, circuitry for switching 1930, and circuitry for transmitting 1935 may cause the communications device 1900 to perform the method 1500 described with respect to FIG. 15, or any aspect related to it; the method 1600 described with respect to FIG. 16, or any aspect related to it; the method 1700 described with respect to FIG. 17, or any aspect related to it; and the method 1800 described with respect to FIG. 18, or any aspect related to it.

Various components of the communications device 1900 may provide means for performing the method 1500 described with respect to FIG. 15, or any aspect related to it; the method 1600 described with respect to FIG. 16, or any aspect related to it; the method 1700 described with respect to FIG. 17, or any aspect related to it; and the method 1800 described with respect to FIG. 18, or any aspect related to it. For example, means for transmitting, sending or outputting for transmission may include transceivers 354 and/or antenna (s) 352 of the UE 104 illustrated in FIG. 3, transceivers 332 and/or antenna (s) 334 of the BS 102 illustrated in FIG. 3, and/or the transceiver 1975 and the antenna 1980 of the communications device 1900 in FIG. 19. Means for receiving or obtaining may include transceivers 354 and/or antenna (s) 352 of the UE 104 illustrated in FIG. 3, transceivers 332 and/or antenna (s) 334 of the BS 102 illustrated in FIG. 3, and/or the transceiver 1975 and the antenna 1980 of the communications device 1900 in FIG. 19.

Example Clauses

Implementation examples are described in the following numbered clauses:

Clause 1: A method for wireless communications at a user equipment (UE) , comprising: receiving first signaling that activates multiple Transmission Configuration Indicator (TCI) states for at least a first control resource set (CORESET) and a second CORESET, wherein the UE is operating in a multiple transmitter receiver point (mTRP) mode that utilizes multiple downlink control information (DCI) scheduling; selecting a TCI state to apply to receive downlink control information (DCI) in at least one of the first CORESET or the second CORESET before receiving a DCI with a field indicating a TCI state for that CORESET; and processing DCI in the at least one of the first CORESET or the second CORESET using the selected TCI state.

Clause 2: The method of Clause 1, wherein the selecting comprises selecting, for the second CORESET, a TCI state, from the multiple TCI states, indicated for the first CORESET.

Clause 3: The method of any one of Clauses 1-2, further comprising: receiving second signaling indicating the UE to switch from a single TRP (sTRP) mode to the mTRP mode; and switching from the sTRP mode to the mTRP mode, based on the second signaling.

Clause 4: The method of Clause 3, wherein the selection is based on a selection rule.

Clause 5: The method of Clause 4, wherein the selection rule dictates use of a first activated TCI state or an activated TCI state of a lowest ID for a CORESET pool index.

Clause 6: The method of Clause 3, wherein the selecting comprises selecting, for the second CORESET, a TCI state, from the multiple TCI states, indicated in a DCI received in the first CORESET.

Clause 7: The method of Clause 6, wherein the TCI state indicated in a DCI received in the first CORESET is used for the second CORESET until a TCI state indicated for the second CORESET takes effect.

Clause 8: The method of Clause 3, wherein the first signaling comprises: a first medium access control (MAC) control element (CE) that activates a single TCI state for at least the first CORESET; and the selecting comprises selecting the single TCI state for at least the first CORESET.

Clause 9: The method of Clause 8, wherein the single TCI state is used for the first CORESET until a TCI state indicated for the first CORESET takes effect.

Clause 10: A method for wireless communications at a network entity, comprising: transmitting first signaling that activates, for a user equipment (UE) operating in a multiple transmitter receiver point (mTRP) mode that utilizes multiple downlink control information (DCI) scheduling, multiple Transmission Configuration Indicator (TCI) states for at least a first control resource set (CORESET) and a second CORESET; selecting a TCI state to apply to transmit downlink control information (DCI) in at least one of the first CORESET or the second CORESET before transmitting a DCI with a field indicating a TCI state for that CORESET; and transmitting DCI in the at least one of the first CORESET or the second CORESET using the selected TCI state.

Clause 11: The method of Clause 10, wherein the selecting comprises selecting, for the second CORESET, a TCI state, from the multiple TCI states, indicated for the first CORESET.

Clause 12: The method of any one of Clauses 10-11, further comprising: transmitting second signaling indicating the UE to switch from a single TRP (sTRP) mode to the mTRP mode.

Clause 13: The method of Clause 12, wherein the selection is based on a selection rule.

Clause 14: The method of Clause 13, wherein the selection rule dictates use of a first activated TCI state or an activated TCI state of a lowest ID for a CORESET pool index.

Clause 15: The method of Clause 12, wherein the selecting comprises selecting, for the second CORESET, a TCI state, from the multiple TCI states, indicated in a DCI transmitted in the first CORESET.

Clause 16: The method of Clause 15, wherein the TCI state indicated in a DCI transmitted in the first CORESET is used for the second CORESET until a TCI state indicated for the second CORESET takes effect.

Clause 17: The method of Clause 12, wherein the first signaling comprises: a first medium access control (MAC) control element (CE) that activates a single TCI state for at least the first CORESET; and the selecting comprises selecting the single TCI state for at least the first CORESET.

Clause 18: The method of Clause 17, wherein the single TCI state is used for the first CORESET until a TCI state indicated for the first CORESET takes effect.

Clause 19: A method for wireless communications at a user equipment (UE) , comprising: receiving first signaling indicating a switch between a first transmission and reception point (TRP) mode and a second TRP mode; receiving second signaling indicating a Transmission Configuration Indicator (TCI) mode for an operating frequency; and processing a downlink transmission on the operating frequency in accordance with the TCI mode.

Clause 20: The method of Clause 19, wherein the operating frequency comprises at least one of a component carrier (CC) or a bandwidth part (BWP) .

Clause 21: The method of any one of Clauses 19-20, wherein: the first TRP mode comprises a single TRP (sTRP) mode; and the second TRP mode comprises a multiple TRP (mTRP) mode that utilizes single downlink control information (DCI) scheduling.

Clause 22: The method of Clause 21, wherein the second signaling indicates whether the operating frequency is operating in a unified TCI framework for the sTRP mode or a unified TCI framework extension for the mTRP mode that utilizes single DCI scheduling.

Clause 23: The method of any one of Clauses 19-22, wherein the second signaling comprises a field in a TCI state activation command.

Clause 24: The method of any one of Clauses 19-23, wherein the second signaling comprises radio resource control (RRC) signaling.

Clause 25: The method of any one of Clauses 19-24, further comprising switching between the first TRP mode and the second TRP mode, based on the first signaling.

Clause 26: A method for wireless communications at a network entity, comprising: transmitting first signaling indicating for a user equipment (UE) to switch between a first transmission and reception point (TRP) mode and a second TRP mode; transmitting second signaling indicating a Transmission Configuration Indicator (TCI) mode for an operating frequency; and transmitting a downlink transmission on the operating frequency in accordance with the TCI mode.

Clause 27: The method of Clause 26, wherein the operating frequency comprises at least one of a component carrier (CC) or a bandwidth part (BWP) .

Clause 28: The method of any one of Clauses 26-27, wherein: the first TRP mode comprises a single TRP (sTRP) mode; and the second TRP mode comprises a multiple TRP (mTRP) mode that utilizes single downlink control information (DCI) scheduling.

Clause 29: The method of Clause 28, wherein the second signaling indicates whether the operating frequency is operating in a unified TCI framework for the sTRP mode or a unified TCI framework extension for the mTRP mode that utilizes single DCI scheduling.

Clause 30: The method of any one of Clauses 26-29, wherein the second signaling comprises a field in a TCI state activation command.

Clause 31: The method of any one of Clauses 26-30, wherein the second signaling comprises radio resource control (RRC) signaling.

Clause 32: An apparatus, comprising: a memory comprising executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform a method in accordance with any one of Clauses 1-31.

Clause 33: An apparatus, comprising means for performing a method in accordance with any one of Clauses 1-31.

Clause 34: A non-transitory computer-readable medium comprising executable instructions that, when executed by a processor of an apparatus, cause the apparatus to perform a method in accordance with any one of Clauses 1-31.

Clause 35: A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any one of Clauses 1-31.

Additional Considerations

The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limiting of the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP) , an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD) , discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC) , or any other such configuration.

As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .

As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information) , accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.

The methods disclosed herein comprise one or more actions for achieving the methods. The method actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and/or use of specific actions may be modified without departing from the scope of the claims. Further, the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software component (s) and/or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor.

The following claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims. Within a claim, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” Unless specifically stated otherwise, the term “some” refers to one or more. No claim element is to be construed under the provisions of 35 U.S.C. §112 (f) unless the element is expressly recited using the phrase “means for” . All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

An apparatus for wireless communication at a user equipment (UE) , comprising: at least one memory comprising computer-executable instructions; and one or more processors configured to execute the computer-executable instructions and cause the apparatus to:

receive first signaling that activates multiple Transmission Configuration Indicator (TCI) states for at least a first control resource set (CORESET) and a second CORESET, wherein the UE is operating in a multiple transmitter receiver point (mTRP) mode that utilizes multiple downlink control information (DCI) scheduling;

select a TCI state to apply to receive DCI in at least one of the first CORESET or the second CORESET before receiving a DCI with a field indicating a TCI state for that CORESET; and

process DCI in the at least one of the first CORESET or the second CORESET using the selected TCI state.
The apparatus of claim 1, wherein the selecting comprises selecting, for the second CORESET, a TCI state, from the multiple TCI states, indicated for the first CORESET.
The apparatus of claim 1, wherein the one or more processors are further configured to execute the computer-executable instructions and cause the apparatus to:

receive second signaling indicating the UE to switch from a single TRP (sTRP) mode to the mTRP mode; and

switch from the sTRP mode to the mTRP mode, based on the second signaling.
The apparatus of claim 3, wherein the selection is based on a selection rule.
The apparatus of claim 4, wherein the selection rule dictates use of a first activated TCI state or an activated TCI state of a lowest ID for a CORESET pool index.
The apparatus of claim 3, wherein the selecting comprises selecting, for the second CORESET, a TCI state, from the multiple TCI states, indicated in a DCI received in the first CORESET.
The apparatus of claim 6, wherein the TCI state indicated in a DCI received in the first CORESET is used for the second CORESET until a TCI state indicated for the second CORESET takes effect.
The apparatus of claim 3, wherein:

the first signaling comprises a first medium access control (MAC) control element (CE) that activates a single TCI state for at least the first CORESET, and

the selecting comprises selecting the single TCI state for at least the first CORESET.
The apparatus of claim 8, wherein the single TCI state is used for the first CORESET until a TCI state indicated for the first CORESET takes effect.
An apparatus for wireless communication at a network entity, comprising: at least one memory comprising computer-executable instructions; and one or more processors configured to execute the computer-executable instructions and cause the apparatus to:

transmitting first signaling that activates, for a user equipment (UE) operating in a multiple transmitter receiver point (mTRP) mode that utilizes multiple downlink control information (DCI) scheduling, multiple Transmission Configuration Indicator (TCI) states for at least a first control resource set (CORESET) and a second CORESET;

selecting a TCI state to apply to transmit DCI in at least one of the first CORESET or the second CORESET before transmitting a DCI with a field indicating a TCI state for that CORESET; and

transmitting DCI in the at least one of the first CORESET or the second CORESET using the selected TCI state.
The apparatus of claim 10, wherein the selecting comprises selecting, for the second CORESET, a TCI state, from the multiple TCI states, indicated for the first CORESET.
The apparatus of claim 10, wherein the one or more processors are further configured to execute the computer-executable instructions and cause the apparatus to:

transmit second signaling indicating the UE to switch from a single TRP (sTRP) mode to the mTRP mode.
The apparatus of claim 12, wherein the selection is based on a selection rule.
The apparatus of claim 13, wherein the selection rule dictates use of a first activated TCI state or an activated TCI state of a lowest ID for a CORESET pool index.
The apparatus of claim 12, wherein the selecting comprises selecting, for the second CORESET, a TCI state, from the multiple TCI states, indicated in a DCI transmitted in the first CORESET.
The apparatus of claim 15, wherein the TCI state indicated in a DCI transmitted in the first CORESET is used for the second CORESET until a TCI state indicated for the second CORESET takes effect.
The apparatus of claim 12, wherein:

the first signaling comprises a first medium access control (MAC) control element (CE) that activates a single TCI state for at least the first CORESET, and

the selecting comprises selecting the single TCI state for at least the first CORESET.
The apparatus of claim 17, wherein the single TCI state is used for the first CORESET until a TCI state indicated for the first CORESET takes effect.
An apparatus for wireless communication at a user equipment (UE) , comprising: at least one memory comprising computer-executable instructions; and one or more processors configured to execute the computer-executable instructions and cause the apparatus to:

receiving first signaling indicating a switch between a first transmission and reception point (TRP) mode and a second TRP mode;

receiving second signaling indicating a Transmission Configuration Indicator (TCI) mode for an operating frequency; and

processing a downlink transmission on the operating frequency in accordance with the TCI mode.
The apparatus of claim 19, wherein the operating frequency comprises at least one of a component carrier (CC) or a bandwidth part (BWP) .
The apparatus of claim 19, wherein:

the first TRP mode comprises a single TRP (sTRP) mode, and

the second TRP mode comprises a multiple TRP (mTRP) mode that utilizes single downlink control information (DCI) scheduling.
The apparatus of claim 21, wherein the second signaling indicates whether the operating frequency is operating in a unified TCI framework for the sTRP mode or a unified TCI framework extension for the mTRP mode that utilizes single DCI scheduling.
The apparatus of claim 19, wherein the second signaling comprises a field in a TCI state activation command.
The apparatus of claim 19, wherein the second signaling comprises radio resource control (RRC) signaling.
The apparatus of claim 19, wherein the one or more processors are further configured to execute the computer-executable instructions and cause the apparatus to switch between the first TRP mode and the second TRP mode, based on the first signaling.
An apparatus for wireless communication at a network entity, comprising: at least one memory comprising computer-executable instructions; and one or more processors configured to execute the computer-executable instructions and cause the apparatus to:

transmitting first signaling indicating for a user equipment (UE) to switch between a first transmission and reception point (TRP) mode and a second TRP mode;

transmitting second signaling indicating a Transmission Configuration Indicator (TCI) mode for an operating frequency; and

transmitting a downlink transmission on the operating frequency in accordance with the TCI mode.
The apparatus of claim 26, wherein the operating frequency comprises at least one of a component carrier (CC) or a bandwidth part (BWP) .
The apparatus of claim 26, wherein:

the first TRP mode comprises a single TRP (sTRP) mode, and

the second TRP mode comprises a multiple TRP (mTRP) mode that utilizes single downlink control information (DCI) scheduling.
The apparatus of claim 28, wherein the second signaling indicates whether the operating frequency is operating in a unified TCI framework for the sTRP mode or a unified TCI framework extension for the mTRP mode that utilizes single DCI scheduling.
The apparatus of claim 26, wherein the second signaling comprises a field in a TCI state activation command.
The apparatus of claim 26, wherein the second signaling comprises radio resource control (RRC) signaling.
A method for wireless communications at a user equipment (UE) , comprising:

receiving first signaling that activates multiple Transmission Configuration Indicator (TCI) states for at least a first control resource set (CORESET) and a second CORESET, wherein the UE is operating in a multiple transmitter receiver point (mTRP) mode that utilizes multiple downlink control information (DCI) scheduling;

selecting a TCI state to apply to receive DCI in at least one of the first CORESET or the second CORESET before receiving a DCI with a field indicating a TCI state for that CORESET; and

processing DCI in the at least one of the first CORESET or the second CORESET using the selected TCI state.
A method for wireless communications at a network entity, comprising:

transmitting first signaling that activates, for a user equipment (UE) operating in a multiple transmitter receiver point (mTRP) mode that utilizes multiple downlink control information (DCI) scheduling, multiple Transmission Configuration Indicator (TCI) states for at least a first control resource set (CORESET) and a second CORESET;

selecting a TCI state to apply to transmit DCI in at least one of the first CORESET or the second CORESET before transmitting a DCI with a field indicating a TCI state for that CORESET; and

transmitting DCI in the at least one of the first CORESET or the second CORESET using the selected TCI state.
A method for wireless communications at a user equipment (UE) , comprising:

receiving first signaling indicating a switch between a first transmission and reception point (TRP) mode and a second TRP mode;

receiving second signaling indicating a Transmission Configuration Indicator (TCI) mode for an operating frequency; and

processing a downlink transmission on the operating frequency in accordance with the TCI mode.
A method for wireless communications at a network entity, comprising:

transmitting first signaling indicating for a user equipment (UE) to switch between a first transmission and reception point (TRP) mode and a second TRP mode;

transmitting second signaling indicating a Transmission Configuration Indicator (TCI) mode for an operating frequency; and

transmitting a downlink transmission on the operating frequency in accordance with the TCI mode.