[go: up one dir, main page]

WO2025081402A1 - Techniques de groupage de quasi-colocalisation (qcl) pour des informations de commande de liaison descendante unique (s-dci) pour de multiples points d'émission/réception (mtrp) avec des états d'indication de configuration de transmission (tci) unifiés - Google Patents

Techniques de groupage de quasi-colocalisation (qcl) pour des informations de commande de liaison descendante unique (s-dci) pour de multiples points d'émission/réception (mtrp) avec des états d'indication de configuration de transmission (tci) unifiés Download PDF

Info

Publication number
WO2025081402A1
WO2025081402A1 PCT/CN2023/125352 CN2023125352W WO2025081402A1 WO 2025081402 A1 WO2025081402 A1 WO 2025081402A1 CN 2023125352 W CN2023125352 W CN 2023125352W WO 2025081402 A1 WO2025081402 A1 WO 2025081402A1
Authority
WO
WIPO (PCT)
Prior art keywords
tci
tci state
qcl
states
pdsch reception
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/125352
Other languages
English (en)
Inventor
Shaozhen GUO
Mostafa KHOSHNEVISAN
Xiaoxia Zhang
Peter Gaal
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2023/125352 priority Critical patent/WO2025081402A1/fr
Publication of WO2025081402A1 publication Critical patent/WO2025081402A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H04B7/06968—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping using quasi-colocation [QCL] between signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0026—Division using four or more dimensions, e.g. beam steering or quasi-co-location [QCL]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver

Definitions

  • aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to configuring and using transmission configuration indication (TCI) states with multiple transmit reception points (TRPs) .
  • TCI transmission configuration indication
  • TRPs transmit reception points
  • Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) . Examples of such multiple-access systems include code-division multiple access (CDMA) systems, time-division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, and orthogonal frequency-division multiple access (OFDMA) systems, and single-carrier frequency division multiple access (SC-FDMA) systems.
  • CDMA code-division multiple access
  • TDMA time-division multiple access
  • FDMA frequency-division multiple access
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • 5G communications technology can include: enhanced mobile broadband addressing human-centric use cases for access to multimedia content, services and data; ultra-reliable-low latency communications (URLLC) with certain specifications for latency and reliability; and massive machine type communications, which can allow a very large number of connected devices and transmission of a relatively low volume of non-delay-sensitive information.
  • URLLC ultra-reliable-low latency communications
  • an apparatus for wireless communication includes a transceiver, one or more memories configured to, individually or in combination, store instructions, one or more processors communicatively coupled with the one or more memories.
  • the one or more processors are, individually or in combination, configured to execute the instructions to cause the apparatus to receive, from a network node, a transmission configuration indicator (TCI) state configuration indicating a plurality of TCI states, receive, from the network node, an indication to activate or select a first TCI state and a second TCI state from the plurality of TCI states, and receive, from the network node, a scheduling physical downlink control channel (PDCCH) that schedules one or more physical downlink shared channel (PDSCH) reception occasions, wherein a first quasi-colocation (QCL) assumption for at least one of the one or more PDSCH reception occasions is that the at least one of the one or more PDSCH reception occasions is not quasi-colocated (QCLed) with a downlink reference signal (DL RS) .
  • TCI transmission configuration indicator
  • an apparatus for wireless communication includes a transceiver, one or more memories configured to, individually or in combination, store instructions, and one or more processors communicatively coupled with the one or more memories.
  • the one or more processors are, individually or in combination, configured to execute the instructions to cause the apparatus to transmit, for a user equipment (UE) , a TCI state configuration indicating a plurality of TCI states, transmit, for the UE, an indication to activate or select a first TCI state and a second TCI state from the plurality of TCI states, and transmit, for the UE, a scheduling PDCCH that schedules one or more PDSCH reception occasions, wherein a first QCL assumption for at least one of the one or more PDSCH reception occasions is that the at least one of the one or more PDSCH reception occasions is not QCLed with a DL RS.
  • UE user equipment
  • a method for wireless communication at a UE includes receiving, from a network node, a TCI state configuration indicating a plurality of TCI states, receiving, from the network node, an indication to activate or select a first TCI state and a second TCI state from the plurality of TCI states, and receiving, from the network node, a scheduling PDCCH that schedules one or more PDSCH reception occasions, wherein a first QCL assumption for at least one of the one or more PDSCH reception occasions is that the at least one of the one or more PDSCH reception occasions is not QCLed with a DL RS.
  • a method for wireless communication at a network node includes transmitting, for a UE, a transmission configuration indicator (TCI) state configuration indicating a plurality of TCI states, transmitting, for the UE, an indication to activate or select a first TCI state and a second TCI state from the plurality of TCI states, and transmitting, for the UE, a scheduling PDCCH that schedules one or more PDSCH reception occasions, wherein a first QCL assumption for at least one of the one or more PDSCH reception occasions is that the at least one of the one or more PDSCH reception occasions is not QCLed with a DL RS.
  • TCI transmission configuration indicator
  • an apparatus for wireless communication includes a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled with the transceiver and the memory. The one or more processors are configured to execute the instructions to perform the operations of methods described herein.
  • an apparatus for wireless communication is provided that includes means for performing the operations of methods described herein.
  • a computer-readable medium is provided including code executable by one or more processors to perform the operations of methods described herein.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
  • FIG. 1 illustrates an example of a wireless communication system, in accordance with various aspects of the present disclosure
  • FIG. 2 is a diagram illustrating an example of disaggregated base station architecture, in accordance with various aspects of the present disclosure
  • FIG. 3 is a block diagram illustrating an example of a user equipment (UE) , in accordance with various aspects of the present disclosure
  • FIG. 4 is a block diagram illustrating an example of a base station, in accordance with various aspects of the present disclosure
  • FIG. 5 is a flow chart illustrating an example of a method for configuring transmission configuration indication (TCI) state information for transmitting wireless communications, in accordance with aspects described herein;
  • TCI transmission configuration indication
  • FIG. 6 is a flow chart illustrating an example of a method for receiving and processing TCI state information for receiving wireless communications, in accordance with aspects described herein;
  • FIG. 7 illustrates a timeline of resources allocated for wireless communications over which TCI states can be activated, selected, and/or utilized, in accordance with aspects described herein;
  • FIG. 8 illustrates a timeline of resources allocated for wireless communications over which TCI states can be activated, selected, and/or utilized including a new TCI state selection field for floating TCI states, in accordance with aspects described herein;
  • FIG. 9 illustrates a timeline of resources allocated for wireless communications over which TCI states associated with different quasi-colocation (QCL) groups can be activated, selected, and/or utilized, in accordance with aspects described herein;
  • QCL quasi-colocation
  • FIG. 10 illustrates a timeline of resources allocated for wireless communications over which TCI states associated with different QCL groups can be activated, selected, and/or utilized including a new TCI state selection field, in accordance with aspects described herein;
  • FIG. 11 illustrates timelines of resources allocated for wireless communications over which QCL profiles can be reset, in accordance with aspects described herein;
  • FIG. 12 illustrates a timeline of resources allocated for wireless communications over which QCL profiles can be reset using a scheduling PDCCH, in accordance with aspects described herein;
  • FIG. 13 is a block diagram illustrating an example of a multiple-input multiple-output (MIMO) communication system including a base station and a UE, in accordance with various aspects of the present disclosure.
  • MIMO multiple-input multiple-output
  • the described features generally relate to obtaining or using quasi-colocation (QCL) for transmissions in single downlink control information (DCI) for multiple transmit reception points (mTRPs) with unified transmission configuration indication (TCI) states.
  • some wireless communication technologies such as fifth generation (5G) new radio (NR) , define a unified TCI framework for single DCI-based mTRP operation where for a serving cell configured for a device (e.g., a user equipment (UE) ) with joint downlink (DL) /uplink (UL) TCI mode, a full set or a subset of ⁇ first joint TCI state, second joint TCI state ⁇ can be mapped to a TCI codepoint of the TCI field in DCI format 1_1/1_2 by a TCI state activation command in a media access control (MAC) -control element (CE) .
  • MAC media access control
  • CE media access control element
  • the joint UL/DL TCI state can apply to both UL and DL communications.
  • a full set or a subset of ⁇ first DL TCI state, first UL TCI state, second DL TCI state, second UL TCI state ⁇ can be mapped to a TCI codepoint of the TCI field in DCI format 1_1/1_2 by TCI state activation command in a MAC-CE.
  • the TCI state activation command in a MAC-CE can indicate that each TCI state (e.g., joint TCI state, DL TCI state, or UL TCI state) mapped to a TCI codepoint is the first or second TCI state.
  • the first/second indicated TCI state (s) e.g., joint TCI state, DL TCI state, or UL TCI state
  • the UE can update the first/second indicated TCI state (s) according to the first/second TCI state (s) in the subset and keep other indicated first/second TCI state (s) that is/are not updated by the received TCI codepoint.
  • the existing TCI field in DCI format 1_1/1_2 can indicate TCI state (s) (e.g., joint TCI state, DL TCI state, or UL TCI state) for one or both of two TRPs in a component carrier (CC) /bandwidth part (BWP) or a set of CCs/BWPs in a CC list.
  • TCI state e.g., joint TCI state, DL TCI state, or UL TCI state
  • CC component carrier
  • BWP bandwidth part
  • an indicator field e.g., TCI state selection field
  • DCI format 1_1/1_2 that schedules/activates physical downlink shared channel (PDSCH) reception to determine which one or both of the indicated TCI states (e.g., joint TCI state or DL TCI state) can be applied to the scheduled/activated PDSCH reception.
  • the presence of the TCI state selection field can be radio resource control (RRC) configured per DL BWP.
  • RRC radio resource control
  • the UE can apply the default indicated TCI state (s) (e.g., joint TCI state or DL TCI state) to PDSCH reception.
  • the UE can apply both indicated TCI states to the scheduled/activated PDSCH reception. If the UE is in frequency range 1 (FR1) , as defined in 5G NR, or the UE supports the capability of two default beams for single DCI-based mTRP in frequency range 2 (FR2) , defined in 5G NR, the UE can apply both indicated TCI states to the scheduled/activated PDSCH reception regardless of the offset between the reception of the scheduling DCI format 1_1/1_2 and the scheduled/activated PDSCH reception.
  • FR1 frequency range 1
  • FR2 frequency range 2
  • the UE can apply both indicated TCI states to the scheduled/activated PDSCH reception when the offset between the reception of the scheduling DCI format 1_1/1_2 and the scheduled/activated PDSCH reception is equal to or larger than a threshold.
  • the UE can alternatively apply the first indicated TCI state to the scheduled/activated PDSCH reception.
  • the UE can alternatively apply the first indicated TCI state to the scheduled/activated PDSCH reception when the offset between the reception of the scheduling/activation DCI format 1_0/1_1/1_2 and the scheduled/activated PDSCH reception is less than a threshold in FR2.
  • the TCI state selection field can be two bits. If the DCI format 1_1/1_2 indicates codepoint ‘10’ for the two bits of the TCI state selection field, the UE can apply both indicated TCI states (e.g., both joint TCI states or both DL TCI states) to PDSCH reception scheduled/activated by the DCI format 1_1/1_2.
  • both indicated TCI states e.g., both joint TCI states or both DL TCI states
  • Applying both TCI states in this regard may be based on rules defined in 5G NR for mapping legacy TCI states to PDSCH transmission occasions, code division multiplexing (CDM) groups, or non-overlapping frequency domain resource allocations by respectively replacing the first and the second indicated legacy TCI states with the first and the second indicated TCI states indicated by the activation command in a MAC-CE and/or the codepoint.
  • the DCI format 1_1/1_2 indicates codepoint ‘00’ or '01’ for the two bits of the TCI state selection field
  • the UE can respectively apply the first or second indicated TCI state to PDSCH reception scheduled/activated by the DCI format 1_1/1_2.
  • the codepoint ‘11’ of the TCI state selection field is reserved.
  • the existing TCI framework in 5G NR can require a demodulation reference signal (DMRS) of PDSCH to be quasi-colocated (QCLed) with a tracking reference signal (TRS) with respect to TypeA QCL (i.e. QCL with respect to Doppler shift, Doppler spread, average delay and delay spread) .
  • DMRS demodulation reference signal
  • TRS tracking reference signal
  • TypeA QCL i.e. QCL with respect to Doppler shift, Doppler spread, average delay and delay spread
  • RB resource block
  • SNR signal-to-noise ratio
  • the DMRS channel estimation performance degradation due to not having the QCL properties from TRS may not be significant.
  • the UE can start to build a QCL profile for those PDSCHs and/or may further refine it as it receives more such PDSCHs over time without the need for TRS.
  • the performance degradation of DMRS channel estimation due to no QCL with TRS
  • Other PDSCHs e.g., PDSCH from serving TRP
  • the UE may benefit from knowing the type of PDSCH (e.g., whether QCLed with TRS or not) .
  • TCI state configuration, activation, and/or selection can be modified to support QCL bundling, or an indication of QCL bundling, for space division multiplexing (SDM) , frequency division multiplexing (FDM) , or time division multiplexing (TDM) schemes in single DCI mTRP with TCI framework.
  • SDM space division multiplexing
  • FDM frequency division multiplexing
  • TDM time division multiplexing
  • unified TCI framework can be enhanced for single DCI mTRP, to support QCL bundling for single DCI mTRP with unified TCI state.
  • the activation command (e.g., in MAC-CE) can be modified, or the interpretation of the command can be modified, to allow for activating TCI states that support QCL bundling among DL transmissions without requiring QCL to a TRS or other DL reference signal (RS) .
  • the TCI selection command (e.g., in DCI) can be modified, or the interpretation of the command can be modified, to allow for selecting TCI states that support QCL bundling among DL transmissions without requiring QCL to a TRS.
  • floating TCI states may be configured (e.g., by the TCI configuration in RRC) .
  • a floating TCI state can be defined to include a TCI state without an associated downlink reference signal.
  • the floating TCI state can be configured with a group index, and/or an indication of whether the floating TCI state corresponds to a dedicated group specific to orphan PDSCHs.
  • the orphan PDSCHs can include PDSCHs that are not QCLed with a TRS and are not QCLed with any other PDSCHs, but are standalone PDSCHs for which a QCL assumption can be derived based on the DMRS associated with the PDSCH.
  • PDSCH (s) associated with floating TCI state in a same group may be QCLed with each other and also QCLed with prior PDSCHs associated with the same group until the QCL profile is reset. If reset, as described further herein, PDSCH associated with floating TCI state in the same group can be QCLed with each other and not QCLed with any prior PDSCHs associated with the same group. In addition, PDSCH (s) associated with floating TCI state in different group may not be QCLed with each other.
  • the activation command (e.g., in MAC-CE) and/or TCI selection command (e.g., in DCI) can be modified to allow for activating or selecting one or more floating TCI states.
  • aspects described herein allow for configuring, activating, and/or selecting TCI states for which corresponding PDSCH transmissions can be bundled for QCL purposes, which can allow for relaxing a requirement that TCI states QCLed with a TRS.
  • This can allow a network node to transmit, and a UE to receive, PDSCH transmissions without having to transmit or receive a TRS for determining QCL relationship.
  • This can save signaling by not requiring the TRS, and/or can save processing required to receive, process, and associate the QCL assumption with the TCI state.
  • the bundled QCL can be aggregated with each received PDSCH transmission, and applied without having to first process a separate reference signal.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and the computing device can be a component.
  • One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • the components can communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal.
  • a processor, at least one processor, and/or one or more processors, individually or in combination, configured to perform or operable for performing a plurality of actions is meant to include at least two different processors able to perform different, overlapping or non-overlapping subsets of the plurality actions, or a single processor able to perform all of the plurality of actions.
  • a description of a processor, at least one processor, and/or one or more processors configured or operable to perform actions X, Y, and Z may include at least a first processor configured or operable to perform a first subset of X, Y, and Z (e.g., to perform X) and at least a second processor configured or operable to perform a second subset of X, Y, and Z (e.g., to perform Y and Z) .
  • a first processor, a second processor, and a third processor may be respectively configured or operable to perform a respective one of actions X, Y, and Z. It should be understood that any combination of one or more processors each may be configured or operable to perform any one or any combination of a plurality of actions.
  • a memory at least one memory, and/or one or more memories, individually or in combination, configured to store or having stored thereon instructions executable by one or more processors for performing a plurality of actions is meant to include at least two different memories able to store different, overlapping or non-overlapping subsets of the instructions for performing different, overlapping or non-overlapping subsets of the plurality actions, or a single memory able to store the instructions for performing all of the plurality of actions.
  • a description of a memory, at least one memory, and/or one or more memories configured or operable to store or having stored thereon instructions for performing actions X, Y, and Z may include at least a first memory configured or operable to store or having stored thereon a first subset of instructions for performing a first subset of X, Y, and Z (e.g., instructions to perform X) and at least a second memory configured or operable to store or having stored thereon a second subset of instructions for performing a second subset of X, Y, and Z (e.g., instructions to perform Y and Z) .
  • a first memory, and second memory, and a third memory may be respectively configured to store or have stored thereon a respective one of a first subset of instructions for performing X, a second subset of instruction for performing Y, and a third subset of instructions for performing Z.
  • any combination of one or more memories each may be configured or operable to store or have stored thereon any one or any combination of instructions executable by one or more processors to perform any one or any combination of a plurality of actions.
  • one or more processors may each be coupled to at least one of the one or more memories and configured or operable to execute the instructions to perform the plurality of actions.
  • a first processor may be coupled to a first memory storing instructions for performing action X
  • at least a second processor may be coupled to at least a second memory storing instructions for performing actions Y and Z
  • the first processor and the second processor may, in combination, execute the respective subset of instructions to accomplish performing actions X, Y, and Z.
  • three processors may access one of three different memories each storing one of instructions for performing X, Y, or Z, and the three processor may in combination execute the respective subset of instruction to accomplish performing actions X, Y, and Z.
  • a single processor may execute the instructions stored on a single memory, or distributed across multiple memories, to accomplish performing actions X, Y, and Z.
  • a CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA) , etc.
  • CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
  • IS-2000 Releases 0 and A are commonly referred to as CDMA2000 1X, 1X, etc.
  • IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD) , etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • a TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • GSM Global System for Mobile Communications
  • An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB) , Evolved UTRA (E-UTRA) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM TM , etc.
  • UMB Ultra Mobile Broadband
  • E-UTRA Evolved UTRA
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM TM
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS) .
  • 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP) .
  • CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • the techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies, including cellular (e.g., LTE) communications over a shared radio frequency spectrum band.
  • LTE/LTE-A system for purposes of example, and LTE terminology is used in much of the description below, although the techniques are applicable beyond LTE/LTE-A applications (e.g., to fifth generation (5G) new radio (NR) networks or other next generation communication systems) .
  • 5G fifth generation
  • NR new radio
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100.
  • the wireless communications system (also referred to as a wireless wide area network (WWAN) ) can include base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and/or a 5G Core (5GC) 190.
  • the base stations 102 may include macro cells (high power cellular base station) and/or small cells (low power cellular base station) .
  • the macro cells can include base stations.
  • the small cells can include femtocells, picocells, and microcells.
  • the base stations 102 may also include gNBs 180, as described further herein.
  • some nodes of the wireless communication system may have a modem 340 and UE communicating component 342 for processing TCI state configuration information and applying a TCI state for communicating with a network node, in accordance with aspects described herein.
  • some nodes may have a modem 440 and BS communicating component 442 for configuring and applying TCI states in communicating with a UE, in accordance with aspects described herein.
  • a UE 104 is shown as having the modem 340 and UE communicating component 342 and a base station 102/gNB 180 is shown as having the modem 440 and BS communicating component 442, this is one illustrative example, and substantially any node or type of node may include a modem 340 and UE communicating component 342 and/or a modem 440 and BS communicating component 442 for providing corresponding functionalities described herein.
  • the base stations 102 configured for 4G LTE (which can collectively be referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through backhaul links 132 (e.g., using an S1 interface) .
  • the base stations 102 configured for 5G NR (which can collectively be referred to as Next Generation RAN (NG-RAN) ) may interface with 5GC 190 through backhaul links 184.
  • NG-RAN Next Generation RAN
  • the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, head compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages.
  • NAS non-access stratum
  • RAN radio access network
  • MBMS multimedia broadcast multicast service
  • RIM RAN information management
  • the base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or 5GC 190) with each other over backhaul links 134 (e.g., using an X2 interface) .
  • the backhaul links 134 may be wired or wireless.
  • the base stations 102 may wirelessly communicate with one or more UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102.
  • a network that includes both small cell and macro cells may be referred to as a heterogeneous network.
  • a heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group, which can be referred to as a closed subscriber group (CSG) .
  • eNBs Home Evolved Node Bs
  • HeNBs Home Evolved Node Bs
  • CSG closed subscriber group
  • the communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104.
  • the communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity.
  • the communication links may be through one or more carriers.
  • the base stations 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc.
  • the component carriers may include a primary component carrier and one or more secondary component carriers.
  • a primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
  • D2D communication link 158 may use the DL/UL WWAN spectrum.
  • the D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia,
  • the wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum.
  • AP Wi-Fi access point
  • STAs Wi-Fi stations
  • communication links 154 in a 5 GHz unlicensed frequency spectrum.
  • the STAs 152 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
  • CCA clear channel assessment
  • a base station 102 may include an eNB, gNodeB (gNB) , or other type of base station.
  • Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and/or near mmW frequencies in communication with the UE 104.
  • mmW millimeter wave
  • mmW millimeter wave
  • mmW base station Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters.
  • Radio waves in the band may be referred to as a millimeter wave.
  • Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters.
  • the super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW /near mmW radio frequency band has extremely high path loss and a short range.
  • the mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.
  • a base station 102 referred to herein can include a gNB 180.
  • the EPC 160 may include 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 a Packet Data Network (PDN) Gateway 172.
  • MME Mobility Management Entity
  • MBMS Multimedia Broadcast Multicast Service
  • BM-SC Broadcast Multicast Service Center
  • PDN Packet Data Network
  • the MME 162 may be in communication with a Home Subscriber Server (HSS) 174.
  • HSS Home Subscriber Server
  • the MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160.
  • the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172.
  • IP Internet protocol
  • the PDN Gateway 172 provides UE IP address allocation as well as other functions.
  • the PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176.
  • the IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services.
  • the BM-SC 170 may provide functions for MBMS user service provisioning and delivery.
  • the 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 may be used to schedule MBMS transmissions.
  • PLMN public land mobile network
  • the 5GC 190 may include a Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195.
  • the AMF 192 may be in communication with a Unified Data Management (UDM) 196.
  • the AMF 192 can be a control node that processes the signaling between the UEs 104 and the 5GC 190.
  • the AMF 192 can provide QoS flow and session management.
  • User Internet protocol (IP) packets (e.g., from one or more UEs 104) can be transferred through the UPF 195.
  • the UPF 195 can provide UE IP address allocation for one or more UEs, as well as other functions.
  • the UPF 195 is connected to the IP Services 197.
  • the IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services.
  • the base station may also be referred to as a gNB, Node B, evolved Node B (eNB) , an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology.
  • the base station 102 provides an access point to the EPC 160 or 5GC 190 for a UE 104.
  • Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • IoT devices e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.
  • IoT UEs may include machine type communication (MTC) /enhanced MTC (eMTC, also referred to as category (CAT) -M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs.
  • MTC machine type communication
  • eMTC also referred to as category (CAT) -M, Cat M1
  • NB-IoT also referred to as CAT NB1 UEs
  • eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies.
  • eMTC may include FeMTC (further eMTC) , eFeMTC (enhanced further eMTC) , mMTC (massive MTC) , etc.
  • NB-IoT may include eNB-IoT (enhanced NB-IoT) , FeNB-IoT (further enhanced NB-IoT) , etc.
  • the UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • a network node a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS, e.g., BS 102) , or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture.
  • BS base station
  • BS 102 base station
  • a BS such as a Node B (NB) , evolved NB (eNB) , NR BS, 5G NB, access point (AP) , a transmit receive point (TRP) , or a cell, etc.
  • NB Node B
  • eNB evolved NB
  • NR BS 5G NB
  • AP access point
  • TRP transmit receive point
  • a cell etc.
  • a BS may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.
  • An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node.
  • a disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) .
  • a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes.
  • the DUs may be implemented to communicate with one or more RUs.
  • Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) .
  • VCU virtual central unit
  • VDU virtual distributed
  • Base station-type operation or network design may consider aggregation characteristics of base station functionality.
  • disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) .
  • Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design.
  • the various units of the disaggregated base station, or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.
  • UE communicating component 342 can receive TCI state configuration information for configuring, activating, and/or selecting one or more TCI states for communicating with multiple TRPs, where at least one of the TCI states can be associated with a QCL assumption that associated communications are not QCL with a DL RS.
  • UE communicating component 342 can accordingly receive communications that are transmitted based on the at least one TCI state having the QCL assumption and can apply QCL based on QCL bundling with previous communications that are transmitted based on the at least one TCI state.
  • BS communicating component 442 can generate and transmit the TCI state configuration information, and can transmit the wireless communications based on the associated QCL assumption.
  • FIG. 2 shows a diagram illustrating an example of 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.
  • DUs distributed units
  • 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.
  • RF radio frequency
  • the UE 104 may be simultaneously served by multiple RUs 240.
  • Each of the units 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 communication interfaces of the units can be configured to communicate with one or more of the other units via the transmission medium.
  • 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.
  • 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.
  • 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.
  • RF radio frequency
  • the CU 210 may host one or more higher layer control functions.
  • control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • 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 (i.e., Central Unit –User Plane (CU-UP) ) , control plane functionality (i.e., Central Unit –Control Plane (CU-CP) ) , or a combination thereof.
  • 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.
  • 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 third Generation Partnership Project (3GPP) .
  • 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.
  • 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.
  • the RU (s) 240 can be implemented to handle over the air (OTA) communication with one or more UEs 104.
  • OTA over the air
  • real-time and non-real-time aspects of control and user plane communication with the RU (s) 240 can be controlled by the corresponding DU 230.
  • 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.
  • 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) .
  • 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) .
  • a cloud computing platform such as an open cloud (O-Cloud) 290
  • network element life cycle management such as to instantiate virtualized network elements
  • 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.
  • 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.
  • 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) .
  • SMO Framework 205 such as reconfiguration via O1
  • A1 policies such as A1 policies
  • FIGS. 3-13 aspects are depicted with reference to one or more components and one or more methods that may perform the actions or operations described herein, where aspects in dashed line may be optional.
  • FIGS. 5 and 6 are presented in a particular order and/or as being performed by an example component, it should be understood that the ordering of the actions and the components performing the actions may be varied, depending on the implementation.
  • the following actions, functions, and/or described components may be performed by a specially programmed processor, a processor executing specially programmed software or computer-readable media, or by any other combination of a hardware component and/or a software component capable of performing the described actions or functions.
  • one example of an implementation of UE 104 may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors 312 and one or more memories 316 and one or more transceivers 302 in communication via one or more buses 344.
  • the one or more processors 312 can include a single processor or multiple processors configured to perform one or more functions described herein.
  • the multiple processors can be configured to perform a certain subset of a set of functions described herein, such that the multiple processors together can perform the set of functions.
  • the one or more memories 316 can include a single memory device or multiple memory devices configured to store instructions or parameters for performing one or more functions described herein.
  • the multiple memory devices can be configured to store the instructions or parameters for performing a certain subset of a set of functions described herein, such that the multiple memory devices together can store the instructions or parameters for the set of functions.
  • the one or more processors 312, one or more memories 316, and one or more transceivers 302 may operate in conjunction with modem 340 and/or UE communicating component 342 for processing TCI state configuration information and applying a TCI state for communicating with a network node, in accordance with aspects described herein.
  • the one or more processors 312 can include a modem 340 and/or can be part of the modem 340 that uses one or more modem processors.
  • the various functions related to UE communicating component 342 may be included in modem 340 and/or processors 312 and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors.
  • the one or more processors 312 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver 302. In other aspects, some of the features of the one or more processors 312 and/or modem 340 associated with UE communicating component 342 may be performed by transceiver 302.
  • memory/memories 316 may be configured to store data used herein and/or local versions of applications 375 or UE communicating component 342 and/or one or more of its subcomponents being executed by at least one processor 312.
  • Memory/memories 316 can include any type of computer-readable medium usable by a computer or at least one processor 312, such as random access memory (RAM) , read only memory (ROM) , tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof.
  • memory/memories 316 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining UE communicating component 342 and/or one or more of its subcomponents, and/or data associated therewith, when UE 104 is operating at least one processor 312 to execute UE communicating component 342 and/or one or more of its subcomponents.
  • Receiver 306 may include hardware, firmware, and/or software code executable by a processor for receiving data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium) .
  • Receiver 306 may be, for example, a radio frequency (RF) receiver.
  • RF radio frequency
  • receiver 306 may receive signals transmitted by at least one base station 102. Additionally, receiver 306 may process such received signals, and also may obtain measurements of the signals, such as, but not limited to, Ec/Io, signal-to-noise ratio (SNR) , reference signal received power (RSRP) , received signal strength indicator (RSSI) , etc.
  • SNR signal-to-noise ratio
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • Transmitter 308 may include hardware, firmware, and/or software code executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium) .
  • a suitable example of transmitter 308 may including, but is not limited to, an RF transmitter.
  • UE 104 may include RF front end 388, which may operate in communication with one or more antennas 365 and transceiver 302 for receiving and transmitting radio transmissions, for example, wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by UE 104.
  • RF front end 388 may be connected to one or more antennas 365 and can include one or more low-noise amplifiers (LNAs) 390, one or more switches 392, one or more power amplifiers (PAs) 398, and one or more filters 396 for transmitting and receiving RF signals.
  • LNAs low-noise amplifiers
  • PAs power amplifiers
  • LNA 390 can amplify a received signal at a desired output level.
  • each LNA 390 may have a specified minimum and maximum gain values.
  • RF front end 388 may use one or more switches 392 to select a particular LNA 390 and its specified gain value based on a desired gain value for a particular application.
  • one or more PA (s) 398 may be used by RF front end 388 to amplify a signal for an RF output at a desired output power level.
  • each PA 398 may have specified minimum and maximum gain values.
  • RF front end 388 may use one or more switches 392 to select a particular PA 398 and its specified gain value based on a desired gain value for a particular application.
  • one or more filters 396 can be used by RF front end 388 to filter a received signal to obtain an input RF signal.
  • a respective filter 396 can be used to filter an output from a respective PA 398 to produce an output signal for transmission.
  • each filter 396 can be connected to a specific LNA 390 and/or PA 398.
  • RF front end 388 can use one or more switches 392 to select a transmit or receive path using a specified filter 396, LNA 390, and/or PA 398, based on a configuration as specified by transceiver 302 and/or processor 312.
  • transceiver 302 may be configured to transmit and receive wireless signals through one or more antennas 365 via RF front end 388.
  • transceiver may be tuned to operate at specified frequencies such that UE 104 can communicate with, for example, one or more base stations 102 or one or more cells associated with one or more base stations 102.
  • modem 340 can configure transceiver 302 to operate at a specified frequency and power level based on the UE configuration of the UE 104 and the communication protocol used by modem 340.
  • modem 340 can be a multiband-multimode modem, which can process digital data and communicate with transceiver 302 such that the digital data is sent and received using transceiver 302.
  • modem 340 can be multiband and be configured to support multiple frequency bands for a specific communications protocol.
  • modem 340 can be multimode and be configured to support multiple operating networks and communications protocols.
  • modem 340 can control one or more components of UE 104 (e.g., RF front end 388, transceiver 302) to enable transmission and/or reception of signals from the network based on a specified modem configuration.
  • the modem configuration can be based on the mode of the modem and the frequency band in use.
  • the modem configuration can be based on UE configuration information associated with UE 104 as provided by the network during cell selection and/or cell reselection.
  • the UE 104 can communicate (e.g., concurrently or otherwise) with multiple TRPs 320 and 322 associated with a base station 102 /gNB 180 in multi-TRP operation.
  • the multiple TRPs 320 and 322 can have different physical locations, and can transmit signals for, and/or receive signals for, the base station 102 /gNB 180.
  • the UE 104 can communicate with the multiple TRPs 320 and 322 using separate TCI state information configured for each TRP.
  • the TCI state configured for one or more of the TRPs 320 and/or 322 can be associated with QCL bundling, as described herein, or otherwise associated with a QCL assumption that is not QCL with a DL RS.
  • the UE 104 can receive a single DCI that selects the TCI state for multi-TRP operation with the TRPs 320 and 322.
  • UE communicating component 342 can optionally include a TCI state processing component 352 for receiving and/or processing TCI state information received from a network node to configure a TCI state for certain wireless communications, and/or a QCL component 354 for applying a QCL with a DL RS or without a DL RS (e.g., using bundling with other wireless communications) , depending on the TCI state configuration, for receiving the certain wireless communications.
  • TCI state processing component 352 for receiving and/or processing TCI state information received from a network node to configure a TCI state for certain wireless communications
  • QCL component 354 for applying a QCL with a DL RS or without a DL RS (e.g., using bundling with other wireless communications) , depending on the TCI state configuration, for receiving the certain wireless communications.
  • the processor (s) 312 may correspond to one or more of the processors described in connection with the UE in FIG. 13.
  • the memory/memories 316 may correspond to the one or more memories described in connection with the UE in FIG. 13.
  • one example of an implementation of base station 102 may include a variety of components, some of which have already been described above, but including components such as one or more processors 412 and one or more memories 416 and one or more transceivers 402 in communication via one or more buses 444.
  • the one or more processors 412 can include a single processor or multiple processors configured to perform one or more functions described herein.
  • the multiple processors can be configured to perform a certain subset of a set of functions described herein, such that the multiple processors together can perform the set of functions.
  • the one or more memories 416 can include a single memory device or multiple memory devices configured to store instructions or parameters for performing one or more functions described herein.
  • the multiple memory devices can be configured to store the instructions or parameters for performing a certain subset of a set of functions described herein, such that the multiple memory devices together can store the instructions or parameters for the set of functions.
  • the one or more processors 412, one or more memories 416, and one or more transceivers 402 may operate in conjunction with modem 440 and/or BS communicating component 442 for configuring and applying TCI states in communicating with a UE, in accordance with aspects described herein.
  • the transceiver 402, receiver 406, transmitter 408, one or more processors 412, memory/memories 416, applications 475, buses 444, RF front end 488, LNAs 490, switches 492, filters 496, PAs 498, and one or more antennas 465 may be the same as or similar to the corresponding components of UE 104, as described above, but configured or otherwise programmed for base station operations as opposed to UE operations.
  • BS communicating component 442 can optionally include a TCI state configuring component 452 for generating and/or transmitting TCI state information to a UE to configure a TCI state for certain wireless communications, and/or a QCL component 354 for applying a QCL with a DL RS or without a DL RS (e.g., using bundling with other wireless communications) , depending on the TCI state configuration, for transmitting the certain wireless communications.
  • TCI state configuring component 452 for generating and/or transmitting TCI state information to a UE to configure a TCI state for certain wireless communications
  • QCL component 354 for applying a QCL with a DL RS or without a DL RS (e.g., using bundling with other wireless communications) , depending on the TCI state configuration, for transmitting the certain wireless communications.
  • FIG. 5 illustrates a flow chart of an example of a method 500 for configuring TCI state information for transmitting wireless communications, in accordance with aspects described herein.
  • FIG. 6 illustrates a flow chart of an example of a method 600 for receiving and processing TCI state information for receiving wireless communications, in accordance with aspects described herein.
  • a node scheduling the UE 104 with communication resources such as a base station 102 or gNB 180, a monolithic base station or gNB, a portion of a disaggregated base station or gNB, a UE in sidelink communication, etc., can perform the functions described in method 500 shown in FIG. 5 using one or more of the components described in FIGS. 1 and/or 4.
  • a UE 104 can perform the functions described in method 600 shown in FIG. 6 using one or more of the components described in FIGS. 1 and/or 3.
  • Methods 500 and 600 are described in conjunction with one another for ease of explanation; however, the methods 500 and 600 are not required to be performed together and indeed can be performed independently using separate devices.
  • a TCI state configuration indicating a plurality of TCI states can be transmitted for a UE.
  • TCI state configuring component 452 e.g., in conjunction with processor (s) 412, memory/memories 416, transceiver 402, BS communicating component 442, etc., can transmit, for the UE (e.g., UE 104) , the TCI state configuration indicating the plurality of TCI states.
  • TCI state configuring component 452 can transmit the TCI state configuration to the UE 104 in RRC signaling.
  • TCI state configuring component 452 can generate the TCI state configuration indicating parameters regarding multiple TCI states that can be activated and/or selected for certain wireless communications.
  • the TCI states can be activated and/or selected for applying an associated QCL assumption to wireless communications, such as a PDSCH scheduled for the UE 104 by a scheduling PDCCH, which can be transmitted by the network node.
  • the TCI state configuration can indicate TCI states that are QCL with a DL RS, such as a TRS, at least for TypeA QCL, as defined in 5G NR.
  • the TCI state configuration can indicate only TCI states that are TypeA QCL with a DL RS.
  • the TCI state configuration may indicate at least one TCI state that is not QCL with a DL RS, which can be referred to as a floating TCI state.
  • the TCI state configuration can indicate multiple floating TCI states that may be configured.
  • Each floating TCI state can be configured with one or more parameters, which may include a group index, and/or an indication of whether the floating TCI state corresponds to a dedicated group specific to orphan PDSCHs that may be scheduled by the network node (e.g., in scheduling PDCCH) for wireless communications with the UE.
  • the orphan PDSCHs can include PDSCHs that are not QCLed with a TRS and are not QCLed with any other PDSCHs, but are standalone PDSCHs for which a QCL assumption can be derived based on the DMRS associated with the PDSCH.
  • PDSCH (s) associated with floating TCI state in a same group can be QCLed with each other and also QCLed with prior PDSCHs associated with the same group until the QCL profile is reset. If reset, PDSCH associated with floating TCI state in the same group can be QCLed with each other and not QCLed with any prior PDSCHs associated with the same group.
  • PDSCH (s) associated with floating TCI state in different group may not be QCLed with each other.
  • a TCI state configuration indicating a plurality of TCI states can be received from a network node.
  • TCI state processing component 352 e.g., in conjunction with processor (s) 312, memory/memories 316, transceiver 302, UE communicating component 342, etc., can receive, from the network node (e.g., base station 102) and/or process, the TCI state configuration indicating the plurality of TCI states.
  • TCI state processing component 352 can receive the TCI state configuration in RRC signaling from the network node.
  • the plurality of TCI states indicated in the TCI state configuration can include TCI states associated with a QCL assumption of QCL with a DL RS.
  • the plurality of TCI states can include one or more TCI states that are associated with a QCL assumption of no QCL with a DL RS (e.g., a floating TCI state that can be associated with QCL bundling) .
  • an indication to activate or select a first TCI state and a second TCI state from the plurality of TCI states can be transmitted for a UE.
  • TCI state configuring component 452 e.g., in conjunction with processor (s) 412, memory/memories 416, transceiver 402, BS communicating component 442, etc., can transmit, for the UE (e.g., UE 104) , an indication to activate or select a first TCI state and a second TCI state from the plurality of TCI states.
  • the indication can be a TCI activation MAC-CE or a beam indication DCI, which can down-select a portion of the plurality of TCI states from the TCI state configuration for possibly using in transmitting wireless communications to the UE 104.
  • the TCI activation MAC-CE or beam indication DCI can include indices of one or more TCI states in the TCI state configuration, which can be mapped to codepoints of a value for selecting one of the activated TCI states in a scheduling PDCCH.
  • the indication can activate or select the first TCI state and/or the second TCI state as a floating TCI state.
  • the floating TCI state can be associated with a QCL assumption of QCL not associated with a DL RS, which can imply to perform QCL bundling for an associated transmission with other transmissions in the same slot or previous transmissions associated with the same TCI state.
  • an indication to activate or select a first TCI state and a second TCI state from the plurality of TCI states can be received from a network node.
  • TCI state processing component 352 e.g., in conjunction with processor (s) 312, memory/memories 316, transceiver 302, UE communicating component 342, etc., can receive, from the network node (e.g., base station 102) and/or process, an indication to activate or select a first TCI state and a second TCI state from the plurality of TCI states.
  • TCI state processing component 352 can receive the indication in a TCI activation MAC-CE, in a beam indication DCI, and/or the like, as described above.
  • the indication can activate or select the first TCI state and/or the second TCI state as a floating TCI state, as described.
  • a scheduling PDCCH that schedules one or more PDSCH reception occasions can be transmitted for a UE, where a first QCL assumption for at least one of the one or more PDSCH reception occasions is that at least one of the one or more PDSCH reception occasions is not QCLed with a DL RS.
  • TCI state configuring component 452 can transmit, for the UE (e.g., UE 104) , the scheduling PDCCH that schedules the one or more PDSCH reception occasions, where the first QCL assumption for at least one of the one or more PDSCH reception occasions is that at least one of the one or more PDSCH reception occasions is not QCLed with a DL RS.
  • the scheduling PDCCH can specify one or more TCI states for the one or more PDSCH reception occasions, and the one or more TCI states can be associated with the QCL assumption using a signaling option described herein.
  • the TCI activation MAC-CE or beam indication DCI can activate or select a floating TCI state, which is associated with the first QCL assumption.
  • the scheduling PDCCH can include one or more TCI state selection fields to indicate selection of a TCI state associated with the first QCL assumption.
  • TCI state configuring component 452 can schedule one or more PDSCH occasions based on the first QCL assumption based on receiving, from the UE, a capability indicator indicating support for bundling QCL for multiple PDSCH receptions or associated TCI states.
  • a scheduling PDCCH that schedules one or more PDSCH reception occasions can be received from a network node, where a first QCL assumption for at least one of the one or more PDSCH reception occasions is that at least one of the one or more PDSCH reception occasions is not QCLed with a DL RS.
  • TCI state processing component 352 e.g., in conjunction with processor (s) 312, memory/memories 316, transceiver 302, UE communicating component 342, etc., can receive, from the network node (e.g., base station 102) and/or process, the scheduling PDCCH that schedules the one or more PDSCH reception occasions, where the first QCL assumption for at least one of the one or more PDSCH reception occasions is that at least one of the one or more PDSCH reception occasions is not QCLed with a DL RS.
  • the network node e.g., base station 102
  • the scheduling PDCCH that schedules the one or more PDSCH reception occasions, where the first QCL assumption for at least one of the one or more PDSCH reception occasions is that at least one of the one or more PDSCH reception occasions is not QCLed with a DL RS.
  • TCI state processing component 352 can obtain the first QCL assumption based on the TCI activation MAC-CE or beam indication DCI activating or selecting a floating TCI state for the one or more PDSCH reception opportunities scheduled by the PDCCH.
  • TCI state processing component 352 can obtain the first QCL assumption based on one or more TCI state selection fields included in the scheduling PDCCH and indicating selection of a TCI state associated with the first QCL assumption.
  • TCI state processing component 352 can receive PDSCH in one or more PDSCH occasions and apply QCL bundling based on transmitting, to the network entity, a capability indicator indicating support for bundling QCL for multiple PDSCH receptions or associated TCI states.
  • TCI state processing component 352 bundles QCL for PDSCHs, it can build a QCL profile for the PDSCHs based on associated DMRS of the PDSCHs, previous PDSCHs (e.g., since a time that the QCL profile is reset) , etc., as described in further detail herein.
  • TCI state processing component 352 can store the QCL profile in memory (e.g., memory/memories 316) and/or can modify the QCL profile each time a PDSCH and/or associated DMRS is received, etc.
  • the TCI state activation command in MAC-CE can be enhanced to activate or indicate a full set or a subset of ⁇ one or more regular TCI states, one or more floating TCI states ⁇ mapped to a TCI codepoint (e.g., of an existing TCI field in DCI format 1_1 or 1_2 defined in 5G NR) .
  • the regular TCI state (s) can correspond to a TCI state (e.g., joint, downlink, or uplink TCI state) associated with a TRS
  • the floating TCI state (s) can correspond to a TCI state not associated with any DL RS, as described above.
  • the TCI state activation command may also indicate that each TCI state (e.g., joint, downlink, or uplink TCI state) mapped to a TCI codepoint is the first or second TCI state.
  • the TCI state activation command may also indicate mapping order of the regular TCI state and floating TCI state, e.g., a TCI codepoint may be associated with ⁇ regular TCI #r1, floating TCI #f1 ⁇ or ⁇ floating TCI #f1, regular TCI #r1 ⁇ .
  • the existing TCI field in DCI format 1_1/1_2 in 5G NR can indicate TCI states for one or more TRPs. If joint DL/UL TCI state is configured, the existing TCI field in DCI format 1_1/1_2 indicate joint/floating TCI states for one or more TRPs. If separate DL/UL TCI state is configured, the existing TCI field in DCI format 1_1/1_2 indicate DL/UL/floating TCI state for one or more TRPs. An example is shown in FIG. 7.
  • FIG. 7 illustrates a timeline 700 of resources allocated for wireless communications over which TCI states can be activated, selected, and/or utilized, in accordance with aspects described herein.
  • timeline 700 can include a plurality of slots over which a network node can schedule one or more UEs for wireless communications.
  • the network node can transmit DCI, which may be of DCI format 1_1 or 1_2 (e.g., as defined in 5G NR) , that includes a TCI field codepoint 702 associated with activated TCI states that are activated via the TCI activation MAC-CE, as described.
  • the TCI field codepoint 702 in beam indication DCI can select one or more activated TCI states that includes a floating TCI state.
  • the TCI field codepoint 702 can select multiple TCI states including joint TCI state #r1 and floating TCI state #f1, where the joint TCI state #r1 and floating TCI state #f1 can be configured in the TCI state configuration, and down-selected to TCI field codepoint ‘010’ in TCI activation MAC-CE.
  • TCI state configuring component 452 can generate the scheduling PDCCH to indicate, and/or TCI state processing component 352 can process the scheduling PDCCH to obtain, selection of one or more of the activated TCI states for the one or more PDSCH reception occasions.
  • the scheduling PDCCH can include a TCI state selection field that indicates which one or more of the indicated TCI states (e.g., joint, downlink, or floating TCI state) can be applied to the one or more PDSCH receptions scheduled by the scheduling PDCCH.
  • the TCI state selection field may indicate one of the following possibilities: one or more regular TCI states (regular TCI state only) ; one or more floating TCI states (floating TCI state only) ; or one or more regular TCI states and one or more floating TCI states (mixed regular and floating TCI state) .
  • TCI states that are associated with a second QCL assumption of QCL with the DL RS are selected among the first TCI state and the second TCI state for the one or more PDSCH reception occasions, or optionally at Block 510, all TCI states that are associated with the first QCL assumption are selected among the first TCI state and the second TCI state for the one or more PDSCH reception occasions, or optionally at Block 512, the first TCI state is selected among the one or more TCI states that are associated with the first QCL assumption and the second TCI state can be selected among one or more TCI states that are associated with the second QCL assumption of QCL with the DL RS.
  • TCI state configuring component 452 can either select, for the one or more PDSCH reception occasions, only TCI states that are associated with a second QCL assumption of QCL with the DL RS among the first TCI state and the second TCI state (e.g., regular TCI states) , select, for the one or more PDSCH reception occasions, all TCI states that are associated with the first QCL assumption among the first TCI state and the second TCI state (e.g., floating TCI states) , or select, for the one or more PDSCH reception occasions, the first TCI state among the one or more TCI states that are associated with the first QCL assumption (e.g., floating TCI state) and the second TCI state among the one or more TCI states that are associated with the second QCL assumption (e.g., regular TCI state) .
  • TCI state configuring component 452 can either select, for the one or more PDSCH reception occasions, only TCI states that are associated with a second QCL assumption of QCL with the DL RS among
  • TCI states that are associated with a second QCL assumption of QCL with the DL RS are selected among the first TCI state and the second TCI state for the one or more PDSCH reception occasions, or optionally at Block 610, all TCI states that are associated with the first QCL assumption are selected among the first TCI state and the second TCI state for the one or more PDSCH reception occasions, or optionally at Block 612, the first TCI state is selected among the one or more TCI states that are associated with the first QCL assumption and the second TCI state can be selected among one or more TCI states that are associated with the second QCL assumption of QCL with the DL RS.
  • TCI state processing component 352 can either select, for the one or more PDSCH reception occasions, only TCI states that are associated with a second QCL assumption of QCL with the DL RS among the first TCI state and the second TCI state (e.g., regular TCI states) , select, for the one or more PDSCH reception occasions, all TCI states that are associated with the first QCL assumption among the first TCI state and the second TCI state (e.g., floating TCI states) , or select, for the one or more PDSCH reception occasions, the first TCI state among the one or more TCI states that are associated with the first QCL assumption (e.g., floating TCI state) and the second TCI state among the one or more TCI states that are associated with the second QCL assumption (e.g., regular TCI state) .
  • TCI state processing component 352 can either select, for the one or more PDSCH reception occasions, only TCI states that are associated with a second QCL assumption of QCL with the DL RS among the first
  • the TCI activation command can activate multiple TCI codepoints as shown in the left table where each TCI codepoint is mapped to a full set or a subset of ⁇ zero or more regular TCI states, zero or more floating TCI states ⁇ .
  • some TCI field codepoints may be mapped to one or more regular TCI states only (e.g., codepoints ‘000, ’ ‘011, ’ and ‘100’ ) , which can be associated with the second QCL assumption of QCL with DL RS
  • some TCI codepoint may be mapped to one or more floating TCI states only (e.g., codepoints ‘001, ’ ‘101, ’ and ‘111’ ) , which can be associated with the first QCL assumption of QCL not with DL RS, or others may be mapped to one regular TCI state and one floating TCI state (e.g., codepoints ‘010, ’ and ‘110’ ) .
  • the TCI field 702 in beam indication DCI can indicate one of the multiple TCI codepoints activated by the TCI activation command (e.g., codepoint ‘010’ which is mapped to joint TCI state #r1, floating TCI state #f1) , as described.
  • a TCI state selection field 704 in a scheduling PDCCH can be transmitted by the network to select one or more of the indicated TCI states for use in PDSCH reception occasions in slots 706, 708, 710, and 712.
  • the PDSCH reception occasions in slots 706, 708, 710, and 712 can each correspond to one of multiple TRPs (e.g., slots 706 and 710 can correspond to a first TRP, and slots 708 and 712 can correspond to a second TRP in multi-TRP operation) .
  • TCI state configuring component 452 can transmit a scheduling PDCCH that includes the TCI state selection field 704 and schedules one or more of the PDSCH reception occasions in slots 706, 708, 710, and 712.
  • the TCI state selection field 704 can be two bits where one codepoint represents using a first indicated (or activated) TCI state for the one or more scheduled PDSCH reception occasions, one codepoint represents using a second indicated (or activated) TCI state for the one or more scheduled PDSCH reception occasions, one codepoint represents using the first and second indicated (or activated) TCI state for the one or more scheduled PDSCH reception occasions (e.g., in an alternating fashion, according to a TRP associated with the PDSCH reception occasion, or according to other mapping rules that may be defined in 5G NR for applying multiple TCI states to multiple PDSCH reception occasions) , and one codepoint can be reserved.
  • TCI state processing component 352 can process the TCI state selection field 704 to obtain the codepoint value and determine which TCI state applies to which of the one or more scheduled PDSCH reception occasions, and QCL component 354 can accordingly apply the corresponding QCL for receiving each PDSCH in the one or more scheduled PDSCH reception occasions.
  • the TCI state activation command can activate one or more floating TCI state (s) without requiring changes to the TCI state activation command format in 5G NR or other wireless communication technologies.
  • the TCI state selection field in 5G NR or other wireless communication technologies can similarly be reused to select the floating TCI state (as a single TCI state or as one of multiple TCI states to be applied in alternating fashion, etc. ) , where the first or second TCI state referred to by the TCI state selection command can be a floating TCI state based on whether the first and/or second TCI state in the TCI state activation command is a floating TCI state.
  • allowing floating TCI states to be used can improve efficiency of using TCI states without requiring reception and processing of a DL RS, such as TRS.
  • TCI state configuring component 452 can generate the scheduling PDCCH to indicate, and/or TCI state processing component 352 can process the scheduling PDCCH to obtain, a TCI state selection field that indicates which one or both of regular TCI states (e.g., joint or downlink TCI states) are to be applied to the one or more PDSCH reception occasions scheduled by the scheduling PDCCH.
  • the reserved codepoint in the TCI state selection field can be used to indicate zero regular TCI states, e.g., no regular TCI state is to be applied to the one or more PDSCH reception occasions scheduled by the scheduling PDCCH.
  • TCI state configuring component 452 can also generate the scheduling PDCCH to indicate, and/or TCI state processing component 352 can also process the scheduling PDCCH to obtain a further TCI state selection field to indicate which one or more floating TCI states are to be applied to the one or more PDSCH reception occasions scheduled by the scheduling PDCCH.
  • TCI state selection field An example is shown in FIG. 8.
  • FIG. 8 illustrates a timeline 800 of resources allocated for wireless communications over which TCI states can be activated, selected, and/or utilized including a new TCI state selection field for floating TCI states, in accordance with aspects described herein.
  • timeline 800 can include a plurality of slots over which a network node can schedule one or more UEs for wireless communications.
  • the network node can transmit DCI, which may be of DCI format 1_1 or 1_2 (e.g., as defined in 5G NR) , that includes a TCI field codepoint 802 associated with activated TCI states that are activated via the TCI activation MAC-CE, as described.
  • the TCI field codepoint 802 can select one or more activated TCI states that includes a floating TCI state. For example, as shown, the TCI field codepoint 802 can select multiple TCI states including joint TCI state #r1 and floating TCI state #f1, where the joint TCI state #r1 and floating TCI state #f1 can be configured in the TCI state configuration, and down-selected to TCI field codepoint ‘010’ in TCI activation MAC-CE.
  • the selected TCI field codepoint ‘010’ can indicate ⁇ joint TCI state #r1, floating TCI state #f1 ⁇ , as described.
  • multiple TCI state selection fields 804 can be transmitted by the network to select one or more of the activated TCI states for use in PDSCH reception occasions in slots 806, 808, 810, and 812.
  • the multiple TCI state selection fields can include a first TCI state selection field indicating regular TCI states for scheduling the one or more PDSCH reception occasions, which may have a codepoint value ‘00’ in this example to indicate the first indicated regular TCI state in the activated TCI states is to be used, and a second TCI state selection field indicating floating TCI states for scheduling the one or more PDSCH reception occasions, which may have a codepoint value ‘00’ in this example to indicate the first indicated floating TCI state in the activated TCI states is to be used.
  • the first TCI state selection field may be a legacy TCI state selection field, for example having two bits (e.g., as defined in 5G NR or other wireless communication technologies) .
  • TCI state configuring component 452 and/or TCI state processing component 352 can use or apply the TCI states based on selection rules for the PDSCH reception occasions in slots 806, 808, 810, and 812 (e.g., by alternating the TCI states, selecting the TCI states for a corresponding TRP, or other selection rules) .
  • the TCI state activation command can activate one or more floating TCI state (s) without requiring changes to the TCI state activation command format in 5G NR or other wireless communication technologies.
  • the TCI state selection field in 5G NR or other wireless communication technologies can similarly be reused along with a second TCI state selection field to indicate whether a floating TCI state is to be used. As described, allowing floating TCI states to be used can improve efficiency of using TCI states without requiring reception and processing of a DL RS, such as TRS.
  • whether the second TCI state selection field is present or not can be configured by the network node (e.g., in RRC or other signaling) .
  • a configuration indicating that a new TCI state selection field is present in the scheduling PDCCH can be transmitted.
  • TCI state configuring component 452 e.g., in conjunction with processor (s) 412, memory/memories 416, transceiver 402, BS communicating component 442, etc., can transmit (e.g., to the UE 104) the configuration indicating that the new TCI state selection field is present in the scheduling PDCCH. Based on transmitting this configuration, TCI state configuring component 452 can generate the scheduling PDCCH to include the new TCI state selection field, as described above.
  • a configuration indicating that a new TCI state selection field is present in the scheduling PDCCH can be received.
  • TCI state processing component 352 e.g., in conjunction with processor (s) 312, memory/memories 316, transceiver 302, UE communicating component 342, etc., can receive (e.g., from the network node) the configuration indicating that the new TCI state selection field is present in the scheduling PDCCH.
  • TCI state configuring component 452 can obtain the new TCI state selection field from the scheduling PDCCH, as described above, and use the indicated value to determine how to apply floating TCI states to one or more PDSCH reception occasions.
  • TCI state processing component 352 can determine that floating TCI states are not used (e.g., only regular TCI state (s) are applied) for the one or more PDSCH reception occasions (e.g., as described with reference to Blocks 508 and/or 608) .
  • TCI state processing component 352 can determine that all the indicated floating TCI states are applied for the one or more PDSCH reception occasions (e.g., as described with reference to Blocks 510 and/or 610) .
  • TCI state processing component 352 can determine that the first indicated floating TCI state is applied for the one or more PDSCH reception occasions (e.g., as described with reference to Blocks 512 and/or 612) .
  • TCI state processing component 352 can determine that floating TCI states are not used (e.g., only regular TCI state (s) are applied) for the one or more PDSCH reception occasions (e.g., as described with reference to Blocks 508 and/or 608) .
  • TCI state processing component 352 (and/or TCI state configuring component 452) can determine that all the indicated floating TCI states are applied for the one or more PDSCH reception occasions (e.g., as described with reference to Blocks 510 and/or 610) regardless of the scheduling offset (e.g., time offset in scheduling) between the reception (or transmission) of the scheduling PDCCH and the one or more PDSCH reception occasions.
  • the scheduling offset e.g., time offset in scheduling
  • TCI state processing component 352 (and/or TCI state configuring component 452) can determine that all the indicated floating TCI states are applied for the one or more PDSCH reception occasions (e.g., as described with reference to Blocks 510 and/or 610) when the scheduling offset between the reception (or transmission) of the scheduling PDCCH and the one or more PDSCH reception occasions is equal to or larger than a threshold.
  • TCI state processing component 352 (and/or TCI state configuring component 452) can determine that the first indicated floating TCI state is applied for the one or more PDSCH reception occasions (e.g., as described with reference to Blocks 512 and/or 612) .
  • TCI state processing component 352, and/or TCI state configuring component 452 can apply the more than one indicated TCI states to the one or more PDSCH reception occasions scheduled/activated by the scheduling PDCCH (e.g., DCI format 1_1/1_2) based on certain mapping rules for mapping multiple QCL groups to PDSCH transmission occasions, CDM groups, or non-overlapping frequency domain resource allocations, as described (e.g., by respectively replacing the n-th QCL group with the n-th indicated TCI state) .
  • the scheduling PDCCH e.g., DCI format 1_1/1_2
  • PDSCH can be transmitted, for the UE, during the one or more PDSCH reception occasions based on the associated first TCI state or second TCI state.
  • BS communicating component 442 e.g., in conjunction with processor (s) 412, memory/memories 416, transceiver 402, etc., can transmit, for the UE (e.g., UE 104) , PDSCH during the one or more PDSCH reception occasions based on the associated first TCI state or second TCI state.
  • this may include QCL component 454 applying QCL according to the QCL assumption associated with the TCI state for transmitting the PDSCH.
  • QCL component 454 can apply QCL based on a bundled QCL profile that can be constructed based on QCL parameters of other PDSCH transmissions scheduled by the same scheduling PDCCH, associated DMRSs, and/or previous PDSCH transmissions/associated DMRSs.
  • QCL component 454 can apply QCL based on QCL with an associated DL RS (e.g., TRS) .
  • BS communicating component 442 can transmit the PDSCH using the associated QCL assumption for beamforming the transmission.
  • PDSCH can be received, from the network node, during the one or more PDSCH reception occasions based on the associated first TCI state or second TCI state.
  • UE communicating component 342 e.g., in conjunction with processor (s) 312, memory/memories 316, transceiver 302, etc., can receive, from the network node, PDSCH during the one or more PDSCH reception occasions based on the associated first TCI state or second TCI state.
  • this may include QCL component 354 applying QCL according to the QCL assumption associated with the TCI state for receiving the PDSCH.
  • QCL component 354 can apply QCL based on a bundled QCL profile that can be constructed based on QCL parameters of other PDSCH transmissions scheduled by the same scheduling PDCCH, associated DMRSs, and/or previous PDSCH transmissions/associated DMRSs.
  • QCL component 354 can apply QCL based on QCL with an associated DL RS (e.g., TRS) .
  • UE communicating component 342 can receive the PDSCH using the associated QCL assumption for beamforming for receiving the PDSCH transmission from the network node.
  • floating TCI states may not be configured in the TCI state configuration, as described above.
  • the existing TCI state configuration defined in 5G NR can be used where each TCI state is associated with one or more DL RS.
  • the TCI activation MAC-CE and/or beam indication DCI can activate or select one or more TCI states that are associated with the one or more DL RS.
  • the TCI state selection field in scheduling PDCCH can be used to indicate a QCL group for one or more of the activated TCI states.
  • TCI state configuring component 452 can generate, and/or TCI state processing component 352 can process, the TCI activation command (MAC-CE) or beam indication DCI to indicate one or more regular TCI states that can be applied to the PDSCH reception after the application time.
  • TCI state configuring component 452 can generate, and/or TCI state processing component 352 can process, a field in the scheduling PDCCH to indicate which one or more regular TCI states as activated, and/or whether or which one or more QCL groups not associated with a DL RS are applied to the one or more PDSCH reception occasions.
  • the MAC CE/beam indication DCI can indicate regular TCI states while the scheduling/activation DCI can select zero or more indicated regular TCI states and zero or more QCL groups without DL RS to be applied to the scheduled PDSCHs.
  • a TCI state selection field indicating to select zero or more TCI states associated with a second QCL assumption of QCL with the RS, among the first TCI state and the second TCI state, for a subset of the one or more PDSCH reception occasions can be transmitted.
  • TCI state configuring component 452 e.g., in conjunction with processor (s) 412, memory/memories 416, transceiver 402, BS communicating component 442, etc., can transmit (or include in the scheduling PDCCH) the TCI state selection field indicating to select zero or more TCI state associated with a second QCL assumption of QCL with the DL RS among the first TCI state and the second TCI state, for a subset of the one or more PDSCH reception occasions.
  • the TCI state selection field may be a legacy TCI state selection field, for example having two bits.
  • the TCI state selection field in the scheduling PDCCH can be generated to also include codepoints mapped to a full set or subset of ⁇ one or more regular TCI states, one or more QCL groups without DL RS ⁇ .
  • Such mapping can be defined or predefined in 5G NR or configured by RRC signaling or indicated by MAC CE, etc.
  • the TCI state selection field can be extended to allow for mapping to a number of TCI states to accommodate possible combinations of the one or more regular TCI states or one or more QCL groups without DL RS.
  • a TCI state selection field indicating to select zero or more TCI states associated with a second QCL assumption of QCL with the RS, among the first TCI state and the second TCI state, for a subset of the one or more PDSCH reception occasions can be received.
  • TCI state processing component 352 e.g., in conjunction with processor (s) 312, memory/memories 316, transceiver 302, UE communicating component 342, etc., can receive (e.g., in the scheduling PDCCH) the TCI state selection field indicating to select zero or more TCI state associated with a second QCL assumption of QCL with the DL RS among the first TCI state and the second TCI state, for a subset of the one or more PDSCH reception occasions.
  • TCI state selection field indicating to select zero or more TCI state associated with a second QCL assumption of QCL with the DL RS among the first TCI state and the second TCI state, for a subset of the one or more PDSCH reception occasions.
  • FIG. 9 illustrates a timeline 900 of resources allocated for wireless communications over which TCI states associated with different QCL groups can be activated, selected, and/or utilized, in accordance with aspects described herein.
  • timeline 900 can include a plurality of slots over which a network node can schedule one or more UEs for wireless communications.
  • the network node can transmit DCI, which may be of DCI format 1_1 or 1_2 (e.g., as defined in 5G NR) , that includes a TCI field codepoint 902 associated with activated TCI states that are activated via the TCI activation MAC-CE, as described.
  • the TCI field codepoint 902 can activate one or more activated TCI states.
  • the TCI field codepoint 902 can activate multiple TCI states including joint TCI state #a2 and joint TCI state #b2, where the joint TCI state #a2 and joint TCI state #b2 can be configured in the TCI state configuration, and down-selected to TCI field codepoint ‘011’ in TCI activation MAC-CE.
  • the TCI state selection field 904 can include codepoint ‘110’ to indicate to use a first joint TCI state (e.g., joint TCI state #a2) and QCL group #1 for the one or more PDSCH reception occasions.
  • TCI state configuring component 452 and/or TCI state processing component 352 can use or apply the TCI states based on selection rules for the PDSCH reception occasions in slots 906, 908, 910, and 912 (e.g., by alternating between the TCI states and/or QCL groups, selecting the TCI states and/or QCL groups for a corresponding TRP, or other selection rules) .
  • the TCI state activation command can activate one or more TCI state (s) without requiring changes to the TCI state activation command format in 5G NR or other wireless communication technologies.
  • the TCI state selection field in 5G NR or other wireless communication technologies can be reused and extended to allow for additional values to indicate selection of at least one TCI state associated with a QCL group that uses QCL bundling (as a single TCI state or as one of multiple TCI states to be applied in alternating fashion, etc. ) .
  • QCL bundling as a single TCI state or as one of multiple TCI states to be applied in alternating fashion, etc.
  • allowing TCI states associated with QCL groups can improve efficiency of using TCI states without requiring reception and processing of a DL RS, such as TRS.
  • a new TCI state selection field associated with multiple codepoint values to indicate to select one or more TCI states associated with the first QCL assumption of QCL for a second subset of the one or more PDSCH reception occasions can be transmitted.
  • TCI state configuring component 452 can transmit (or include in the scheduling PDCCH) the new TCI state selection field associated with the multiple codepoint values to indicate to select one or more TCI state associated with the first QCL assumption (e.g., QCL not with the DL RS) for a second subset of the one or more PDSCH reception occasions.
  • the first (legacy) TCI state selection field is used to indicate one or more regular TCI states
  • the second (new) TCI state selection field can be used to indicate one or more QCL groups without DL RS.
  • TCI state configuring component 452 can generate, and/or TCI state processing component 352 can process, a codepoint in the first TCI state selection field to indicate no regular TCI state, e.g., the reserved codepoint ‘11’ may be used for this purpose or a new indicator field can be used to disable/enable the first TCI state selection field.
  • a codepoint in the new field can be used to indicate no QCL group without DL RS, or a new indicator field can be used to disable/enable the second (new) TCI state selection field.
  • a new TCI state selection field with multiple codepoint values to indicate to select one or more TCI states associated with the first QCL assumption for a second subset of the one or more PDSCH reception occasions can be received.
  • TCI state processing component 352 e.g., in conjunction with processor (s) 312, memory/memories 316, transceiver 302, UE communicating component 342, etc., can receive (e.g., in the scheduling PDCCH) the new TCI state selection field with multiple codepoint values to indicate to select one or more TCI states associated with the first QCL assumption for a second subset of the one or more PDSCH reception occasions.
  • An example is shown in FIG. 10.
  • FIG. 10 illustrates a timeline 1000 of resources allocated for wireless communications over which TCI states associated with different QCL groups can be activated, selected, and/or utilized including a new TCI state selection field, in accordance with aspects described herein.
  • timeline 1000 can include a plurality of slots over which a network node can schedule one or more UEs for wireless communications.
  • the network node can transmit DCI, which may be of DCI format 1_1 or 1_2 (e.g., as defined in 5G NR) , that includes a TCI field codepoint 1002 associated with activated TCI states that are activated via the TCI activation MAC-CE, as described.
  • the TCI field codepoint 1002 can activate one or more activated TCI states.
  • the TCI field codepoint 1002 can activate multiple TCI states including joint TCI state #a2 and joint TCI state #b2, where the joint TCI state #a2 and joint TCI state #b2 can be configured in the TCI state configuration, and down-selected to TCI field codepoint ‘011’ in TCI activation MAC-CE.
  • TCI state selection fields 1004 can be transmitted by the network to select one or more of the activated TCI states, and/or one or more QCL groups, for use in PDSCH reception occasions in slots 1006, 1008, 1010, and 1012.
  • the TCI state selection fields 1004 can include a first TCI state selection field having possible codepoint values for indicating which of one or more activated TCI states to use for the one or more PDSCH reception occasions, and a second (new) TCI state selection field having possible codepoint values for indicating which of one or more QCL groups to use for the one or more PDSCH reception occasions.
  • TCI state configuring component 452 and/or TCI state processing component 352 can use or apply the TCI states based on selection rules for the PDSCH reception occasions in slots 1006, 1008, 1010, and 1012 (e.g., by alternating between the TCI states and/or QCL groups, selecting the TCI states and/or QCL groups for a corresponding TRP, or other selection rules) .
  • the TCI state activation command can activate one or more TCI state (s) without requiring changes to the TCI state activation command format in 5G NR or other wireless communication technologies.
  • the TCI state selection field in 5G NR or other wireless communication technologies can be reused along with a second TCI state selection field to allow selection of at least one TCI state associated with a QCL group that uses QCL bundling (as a single TCI state or as one of multiple TCI states to be applied in alternating fashion, etc. ) .
  • QCL bundling as a single TCI state or as one of multiple TCI states to be applied in alternating fashion, etc.
  • allowing TCI states associated with QCL groups can improve efficiency of using TCI states without requiring reception and processing of a DL RS, such as TRS.
  • an indication to reset the QCL profile for the one or more PDSCH reception occasions can be transmitted.
  • TCI state configuring component 452 e.g., in conjunction with processor (s) 412, memory/memories 416, transceiver 402, BS communicating component 442, etc., can transmit (e.g., to the UE 104) the indication to reset the QCL profile for the one or more PDSCH reception occasions.
  • TCI state configuring component 452 can transmit the indication to reset the QCL profile in the TCI activation MAC-CE or beam indication DCI, in the scheduling PDCCH, etc.
  • the indication to reset the QCL profile can correspond to one of multiple QCL groups, such as one or more groups of floating TCI states (e.g., based on the group index of the floating TCI state) , one or more QCL groups where floating TCI states are not used, etc.
  • the QCL profile for the one or more PDSCH reception occasions can be reset.
  • QCL component 354 e.g., in conjunction with processor (s) 312, memory/memories 316, transceiver 302, UE communicating component 342, etc., can reset the QCL profile for the one or more PDSCH reception occasions.
  • QCL component 354 can reset the QCL profile based at least in part on receiving an indication to reset the QCL profile (e.g., in TCI activation MAC-CE or beam indication DCI, scheduling PDCCH, etc. ) .
  • QCL component 354 can determine, from the indication to reset the QCL profile, a floating TCI state group or QCL group for which to reset the QCL profile.
  • resetting the QCL profile can include erasing the QCL profile that was aggregated and stored (e.g., in memory/memories 316 or 416) from previous PDSCH receptions, such that PDSCH reception occasions occurring after reset can be QCLed with one another and/or with corresponding DMRS, but not with the previous PDSCH receptions.
  • the indicator can apply to one or more floating TCI states (plus one or more regular TCI states if any) .
  • the reset can be indicated or applied per group index (e.g., in case multiple groups are supported)
  • QCL component (s) 354 and/or 454 can reset the QCL profile for the corresponding floating TCI states having the specified group index (e.g., or for QCL groups having a corresponding group index in the case that floating TCI states are not used) .
  • PDSCHs associated with the floating TCI state that is associated with the group (or PDSCH associated with the QCL group where floating TCI states are not used) after the application time are not only QCLed with other, but also QCLed with prior PDSCHs associated with the same floating TCI state (same group index, or same QCL group where floating TCI states are not used) .
  • the QCL component (s) 354 and/or 454 can reset the QCL profile (e.g., PDSCHs associated with the floating TCI state that is associated with the group after the application time are not QCLed with any prior PDSCH associated with the same floating TCI state (same group index, or same QCL group where floating TCI states are not used) ) .
  • the QCL profile e.g., PDSCHs associated with the floating TCI state that is associated with the group after the application time are not QCLed with any prior PDSCH associated with the same floating TCI state (same group index, or same QCL group where floating TCI states are not used)
  • FIG. 11 illustrates timelines 1100 and 1102 of resources allocated for wireless communications over which QCL profiles can be reset, in accordance with aspects described herein.
  • timelines 1100 and 1102 can include a plurality of slots over which a network node can schedule one or more UEs for wireless communications.
  • the network node can transmit a TCI state selection field 1104 to select TCI state #r1 and TCI state #f1, where TCI state #f1 can be a floating TCI state, but could also be a QCL group in an example where floating TCI states are not used.
  • TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI states #r1, #f1, #r1, #f1 for corresponding PDSCH reception occasions.
  • the network node can transmit a TCI state selection field 1106 to select TCI state #f1. Accordingly, TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI state #f1 for the corresponding PDSCH reception occasion.
  • the network node can also transmit TCI field codepoint at 1108 to switch to TCI states ⁇ TCI state #r2, TCI state #f1 ⁇ , and this DCI may not include a reset indicator (or may include a reset indicator indicating not to reset for the QCL group associated with the floating TCI state or otherwise) .
  • the network node can transmit a TCI state selection field 1110 to select TCI state #r2 and TCI state #f1, where TCI state #f1 can be a floating TCI state, but could also be a QCL group in an example where floating TCI states are not used. Accordingly, TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI states #r2, #f1, #r2, #f1 for corresponding PDSCH reception occasions. The network node can transmit a TCI state selection field 1112 to select TCI state #f1. Accordingly, TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI state #f1 for the corresponding PDSCH reception occasion. All of the depicted PDSCH reception occasions for TCI state (or QCL group) #f1 can be QCLed with one another, and the QCL is not reset, as an indication to reset is not received.
  • the network node can transmit a TCI state selection field 1114 to select TCI state #r1 and TCI state #f1, where TCI state #f1 can be a floating TCI state, but could also be a QCL group in an example where floating TCI states are not used. Accordingly, TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI states #r1, #f1, #r1, #f1 for corresponding PDSCH reception occasions. The network node can transmit a TCI state selection field 1116 to select TCI state #f1. Accordingly, TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI state #f1 for the corresponding PDSCH reception occasion.
  • the network node can also transmit TCI field codepoint 1118 to switch to TCI states ⁇ TCI state #r2, TCI state #f1 ⁇ , and this DCI may include a reset indicator indicating to reset for the QCL group associated with the floating TCI state or otherwise.
  • the network node can transmit a TCI state selection field 1120 to select TCI state #r2 and TCI state #f1, where TCI state #f1 can be a floating TCI state, but could also be a QCL group in an example where floating TCI states are not used. Accordingly, TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI states #r2, #f1, #r2, #f1 for corresponding PDSCH reception occasions. The network node can transmit a TCI state selection field 1122 to select TCI state #f1. Accordingly, TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI state #f1 for the corresponding PDSCH reception occasion.
  • the depicted PDSCH reception occasions for TCI state (or QCL group) #f1 in the indicated TCI state ⁇ TCI state #r1, TCI state #f1 ⁇ can be QCLed with one another, but the QCL profile can be subsequently reset.
  • the depicted PDSCH reception occasions for TCI state (or QCL group) #f1 in the indicated TCI state ⁇ TCI state #r2 can be QCLed with one another, but not with the TCI state (or QCL group) #f1 in the indicated TCI state ⁇ TCI state #r1, TCI state #f1 ⁇ .
  • the indicator can apply per group index (e.g., to one or more floating TCI states or QCL groups associated with a group index) .
  • TCI state configuring component 452 can generate, and/or TCI state processing component 352 can process, the scheduling PDCCH as including a one-bit reset indicator for each group (e.g., each group of floating TCI states or each QCL group where floating TCI states are not configured) .
  • QCL component 354 can reset the QCL profile for PDSCH associated with the group (e.g., with the floating TCI state that is associated with the group index, or with the correspond QCL group) for future PDSCH reception occasion (s) .
  • TCI state processing component 352 and/or TCI state configuring component 452 can assume that PDSCH reception occasion (s) associated with the group (e.g., with the floating TCI state that is associated with the group index, or with the corresponding QCL group) are QCLed with prior PDSCHs associated with the same group index.
  • An example is illustrated in FIG. 12.
  • FIG. 12 illustrates a timeline 1200 of resources allocated for wireless communications over which QCL profiles can be reset using a scheduling PDCCH, in accordance with aspects described herein.
  • timeline 1200 can include a plurality of slots over which a network node can schedule one or more UEs for wireless communications.
  • the network node can transmit a TCI state selection field 1204 to select TCI state #r1 and TCI state #f1, where TCI state #f1 can be a floating TCI state, but could also be a QCL group in an example where floating TCI states are not used.
  • the TCI state selection field 1204 may have a reset indicator for group zero indicating not to reset the QCL profile for group zero.
  • TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI states #r1, #f1, #r1, #f1 for corresponding PDSCH reception occasions.
  • the network node can transmit a TCI state selection field 1206 to select TCI state #f1.
  • the TCI state selection field 1206 may have a reset indicator for group zero indicating not to reset the QCL profile for group zero.
  • TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI state #f1 for the corresponding PDSCH reception occasion.
  • the network node can also transmit TCI field codepoint at 1208 to switch to TCI states ⁇ TCI state #r2, TCI state #f1 ⁇ .
  • the network node can transmit a TCI state selection field 1210 to select TCI state #r2 and TCI state #f1, where TCI state #f1 can be a floating TCI state, but could also be a QCL group in an example where floating TCI states are not used.
  • the TCI state selection field 1210 may have a reset indicator for group zero indicating not to reset the QCL profile for group zero. Accordingly, TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI states #r2, #f1, #r2, #f1 for corresponding PDSCH reception occasions.
  • the network node can transmit a TCI state selection field 1212 to select TCI state #f1.
  • the TCI state selection field 1212 may have a reset indicator for group zero indicating to reset the QCL profile for group zero. Accordingly, TCI state processing component 352 and/or TCI state configuring component 452 can apply TCI state #f1 for the corresponding PDSCH reception occasion.
  • QCL component 354 and/or 454 can reset the QCL profile for group index zero (e.g., correlated to the TCI state #f1) , and the corresponding PDSCH reception occasions occurring after receiving the TCI state selection field 1212 with the resent indicator can be QCLed with one another, but not QCLed with the PDSCH reception occasions occurring before receiving the TCI state selection field 1212 with the reset indicator.
  • FIG. 13 is a block diagram of a MIMO communication system 1300 including a base station 102 and a UE 104.
  • the MIMO communication system 1300 may illustrate aspects of the wireless communication access network 100 described with reference to FIG. 1.
  • the base station 102 may be an example of aspects of the base station 102 described with reference to FIG. 1.
  • the base station 102 may be equipped with antennas 1334 and 1335, and the UE 104 may be equipped with antennas 1352 and 1353.
  • the base station 102 may be able to send data over multiple communication links at the same time.
  • Each communication link may be called a “layer” and the “rank” of the communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system where base station 102 transmits two “layers, ” the rank of the communication link between the base station 102 and the UE 104 is two.
  • a transmit (Tx) processor 1320 may receive data from a data source.
  • the transmit processor 1320 may process the data.
  • the transmit processor 1320 may also generate control symbols or reference symbols.
  • a transmit MIMO processor 1330 may perform spatial processing (e.g., precoding) on data symbols, control symbols, or reference symbols, if applicable, and may provide output symbol streams to the transmit modulator/demodulators 1332 and 1333.
  • Each modulator/demodulator 1332 through 1333 may process a respective output symbol stream (e.g., for OFDM, etc. ) to obtain an output sample stream.
  • Each modulator/demodulator 1332 through 1333 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a DL signal.
  • DL signals from modulator/demodulators 1332 and 1333 may be transmitted via the antennas 1334 and 1335, respectively.
  • the UE 104 may be an example of aspects of the UEs 104 described with reference to FIGS. 1 and 3.
  • the UE antennas 1352 and 1353 may receive the DL signals from the base station 102 and may provide the received signals to the modulator/demodulators 1354 and 1355, respectively.
  • Each modulator/demodulator 1354 through 1355 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
  • Each modulator/demodulator 1354 through 1355 may further process the input samples (e.g., for OFDM, etc. ) to obtain received symbols.
  • a MIMO detector 1356 may obtain received symbols from the modulator/demodulators 1354 and 1355, perform MIMO detection on the received symbols, if applicable, and provide detected symbols.
  • a receive (Rx) processor 1358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE 104 to a data output, and provide decoded control information to a processor (s) 1380, or memory/memories 1382.
  • the processor (s) 1380 may in some cases execute stored instructions to instantiate a UE communicating component 342 (see e.g., FIGS. 1 and 3) .
  • a transmit processor 1364 may receive and process data from a data source.
  • the transmit processor 1364 may also generate reference symbols for a reference signal.
  • the symbols from the transmit processor 1364 may be precoded by a transmit MIMO processor 1366 if applicable, further processed by the modulator/demodulators 1354 and 1355 (e.g., for single carrier-FDMA, etc. ) , and be transmitted to the base station 102 in accordance with the communication parameters received from the base station 102.
  • the UL signals from the UE 104 may be received by the antennas 1334 and 1335, processed by the modulator/demodulators 1332 and 1333, detected by a MIMO detector 1336 if applicable, and further processed by a receive processor 1338.
  • the receive processor 1338 may provide decoded data to a data output and to the processor (s) 1340 or memory/memories 1342.
  • the processor (s) 1340 may in some cases execute stored instructions to instantiate a BS communicating component 442 (see e.g., FIGS. 1 and 4) .
  • the components of the UE 104 may, individually or collectively, be implemented with one or more ASICs adapted to perform some or all of the applicable functions in hardware.
  • Each of the noted modules may be a means for performing one or more functions related to operation of the MIMO communication system 1300.
  • the components of the base station 102 may, individually or collectively, be implemented with one or more application specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware.
  • ASICs application specific integrated circuits
  • Each of the noted components may be a means for performing one or more functions related to operation of the MIMO communication system 1300.
  • Aspect 1 is a method for wireless communication at a UE including receiving, from a network node, a TCI state configuration indicating a plurality of TCI states, receiving, from the network node, an indication to activate or select a first TCI state and a second TCI state from the plurality of TCI states, and receiving, from the network node, a scheduling PDCCH that schedules one or more PDSCH reception occasions, where a first QCL assumption for at least one of the one or more PDSCH reception occasions is that the at least one of the one or more PDSCH reception occasions is not QCL with a DL RS.
  • the method of Aspect 1 includes where the TCI state configuration indicates at least one of the plurality of TCI states is not associated with the DL RS, where the indication includes a TCI activation command to activate one or more TCI codepoints, where each of the one or more TCI codepoints is associated with one or more TCI states from the plurality of TCI states, and where at least one of the one or more TCI codepoints indicates the first TCI state as associated with a second QCL assumption of QCL with the DL RS and the second TCI state as associated with the first QCL assumption.
  • the method of Aspect 2 includes where the indication further includes a beam indication DCI to indicate one TCI codepoint from the at least one or more TCI codepoints.
  • the method of any of Aspects 2 or 3 includes where the TCI activation command indicates an order in which the first TCI state and the second TCI state are activated.
  • the method of any of Aspects 2 to 4 includes where each of the plurality of TCI states are joint uplink and downlink TCI states.
  • the method of any of Aspects 2 to 5 includes where each of the plurality of TCI states include an uplink TCI state or a downlink TCI state.
  • the method of any of Aspects 2 to 6 includes where the scheduling PDCCH includes a TCI state selection field indicating to select the first TCI state, the second TCI state, or both of the first TCI state and the second TCI state for the one or more PDSCH reception occasions.
  • the method of Aspect 7 includes where the TCI state selection field is associated with multiple values, including a value to indicate each of to select the first TCI state for a first subset of the one or more PDSCH reception occasions, to select the second TCI state for a second subset of the one or more PDSCH reception occasions.
  • the method of any of Aspects 1 to 8 includes where the scheduling PDCCH includes a first TCI state selection field related to selecting one or more TCI states that are associated with a second QCL assumption of QCL with the DL RS, and a second TCI state selection field in the scheduling PDCCH related to selecting one or more TCI states that are associated with the first QCL assumption.
  • the method of Aspect 9 includes where the first TCI state selection field in the scheduling PDCCH indicates to select the first TCI state for a first subset of the one or more PDSCH reception occasions, and where the second TCI state selection field in the scheduling PDCCH indicates to select the second TCI state for the second subset of the one or more PDSCH reception occasions.
  • the method of any of Aspects 9 or 10 includes where a reserved codepoint of the first TCI state selection field in the scheduling PDCCH indicates no selection of a TCI state that associated with the second QCL assumption.
  • the method of any of Aspects 9 to 11 includes receiving, from the network node, a configuration indicating that the second TCI state selection field is present in the scheduling PDCCH.
  • the method of any of Aspects 1 to 12 includes where the scheduling PDCCH includes a TCI state selection field related to selecting one or more TCI states that are associated with a second QCL assumption of QCL with the DL RS, and, where a configuration indicating that a further TCI state selection field related to selecting one or more TCI states that are associated with the second QCL assumption is not present, selecting, for the one or more PDSCH reception occasions, only TCI states that are associated with the second QCL assumption among the first TCI state and the second TCI state.
  • the method of Aspect 13 includes where selecting, for the one or more PDSCH reception occasions, only TCI states that are associated with the second QCL assumption among the first TCI state and the second TCI state is based at least in part on the UE not supporting TCI states that are associated with the first QCL assumption.
  • the method of any of Aspects 1 to 14 includes where the scheduling PDCCH includes a TCI state selection field related to selecting one or more TCI states that are associated with a second QCL assumption of QCL with the DL RS, and, where a configuration indicating that a further TCI state selection field related to selecting one or more TCI states that are associated with a second QCL assumption of QCL with the DL RS is not present, selecting, for the one or more PDSCH reception occasions, all TCI states that are associated with the first QCL assumption among the first TCI state and second TCI state.
  • the method of Aspect 15 includes where selecting, for the one or more PDSCH reception occasions, all TCI states that are associated with the first QCL assumption among the first TCI state and second TCI state is based at least in part on transmitting a capability indicator indicating that the UE supports bundling QCL for multiple TCI states that are associated with the first QCL assumption.
  • the method of any of Aspects 15 or 16 includes where selecting, for the one or more PDSCH reception occasions, all TCI states that are associated with the first QCL assumption among the first TCI state and second TCI state is based at least in part on a time offset between receiving the scheduling PDCCH and receiving the first PDSCH reception occasion of the one or more PDSCH reception occasions achieving a threshold time.
  • the method of any of Aspects 1 to 17 includes where the scheduling PDCCH includes a TCI state selection field related to selecting one or more TCI states that are associated with a second QCL assumption of QCL with the DL RS, and, where a configuration indicating that a further TCI state selection field related to selecting one or more TCI states that are associated with the first QCL assumption is not present, selecting, for the one or more PDSCH reception occasions, the first TCI state among the one or more TCI states that are associated with the first QCL assumption from the first TCI state and the second TCI state.
  • the method of Aspect 18 includes where selecting, for the one or more PDSCH reception occasions, the first TCI state is based at least in part on the UE not supporting bundling QCL for multiple TCI states that are associated with the first QCL assumption.
  • the method of any of Aspects 1 to 19 includes where the TCI state configuration indicates at least one of the plurality of TCI states is associated with the first QCL assumption and is associated with a group index.
  • the method of Aspect 20 includes where a reset indicator corresponding to the at least one of the plurality of TCI states that is associated with the first QCL assumption and is associated with the group index is included in one of the indication or the scheduling PDCCH.
  • the method of Aspect 21 includes resetting, based on the reset indicator, the QCL for the one or more PDSCH reception occasions associated with one or more TCI states associated with the group index.
  • the method of Aspect 21 or 22 includes resetting, based on receiving the reset indicator for the group index, the QCL for the one or more PDSCH reception occasions associated with the one or more TCI states associated with the group index after an application time.
  • the method of any of Aspects 21 to 23 includes applying, based on receiving the reset indicator indicating not to reset the QCL for a second group, the first QCL assumption that the one or more PDSCH reception occasions associated with one or more TCI states in the second group are QCLed with each other and also QCLed with prior PDSCH reception occasions associated with the one or more TCI states in the second group.
  • the method of any of Aspects 20 to 24 includes where the scheduling PDCCH includes the reset indicator.
  • the method of Aspect 25 includes resetting, based on the reset indicator indicating to reset QCL, the QCL for the one or more PDSCH reception occasions associated with the one or more TCI states associated with the group index among the one or more PDSCH reception occasions and future PDSCH reception occasions.
  • the method of any of Aspects 25 or 26 includes applying, based on receiving the reset indicator indicating not to reset the QCL for a second group, a third QCL assumption that the one or more PDSCH reception occasions associated with one or more TCI states in the second group are QCLed with each other and also QCLed with prior PDSCH reception occasions associated with the one or more TCI states in the second group.
  • the method of any of Aspects 1 to 27 includes where the TCI state configuration indicates each of the plurality of TCI states are associated with a second QCL assumption of QCL with the DL RS, and where the scheduling PDCCH indicates zero or more of the first TCI state and the second TCI state and zero or more QCL groups that are associated with the first QCL assumption for the one or more PDSCH reception occasions.
  • the method of Aspect 28 includes where the scheduling PDCCH includes a TCI state selection field that is associated with multiple codepoint values, including a codepoint value to indicate selecting zero or more of the first TCI state and the second TCI state for a first subset of the one or more PDSCH reception occasions, and selecting zero or more of the zero or more QCL groups for a second subset of the one or more PDSCH reception occasions.
  • the scheduling PDCCH includes a TCI state selection field that is associated with multiple codepoint values, including a codepoint value to indicate selecting zero or more of the first TCI state and the second TCI state for a first subset of the one or more PDSCH reception occasions, and selecting zero or more of the zero or more QCL groups for a second subset of the one or more PDSCH reception occasions.
  • the method of Aspect 29 includes where a mapping between one of the multiple codepoint values of a TCI state selection field and one or more TCI states or QCL groups are based on one of a predefined rule, a RRC configuration, or a MAC-CE.
  • the method of any of Aspects 29 or 30 includes selecting the zero or more of the zero or more QCL groups for the second subset of the one or more PDSCH reception occasions based on a new indicator field indicating no QCL group without DL RS or the new indicator field is disabled.
  • the method of any of Aspects 28 to 31 includes where receiving the scheduling PDCCH includes receiving a legacy TCI state selection field indicating to select zero or more TCI states associated with a second QCL assumption of QCL with the DL RS, among the first TCI state and second TCI states, for a first subset of the one or more PDSCH reception occasions, and receiving a new TCI state selection field associated with multiple codepoint values to indicate to select one or more QCL groups associated with the first QCL assumption, for a second subset of the one or more PDSCH reception occasions.
  • the method of Aspect 32 includes where a mapping between the codepoint of the new TCI state selection field and one or more TCI states or QCL groups are based on one of a predefined rule, a RRC configuration, or a MAC-CE.
  • the method of any of Aspects 1 to 33 includes building a QCL profile for the one or more PDSCH reception occasions based at least in part on one or more previous PDSCH reception occasions, wherein the first QCL assumption is based on the QCL profile.
  • the method of any of Aspects 1 to 34 includes where the DL RS is a tracking reference signal.
  • Aspect 36 is a method for wireless communication at a network node including transmitting, for a UE, a TCI state configuration indicating a plurality of TCI states, transmitting, for the UE, an indication to activate or select a first TCI state and a second TCI state from the plurality of TCI states, and transmitting, for the UE, a scheduling PDCCH that schedules one or more PDSCH reception occasions, where a first QCL assumption for at least one of the one or more PDSCH reception occasions is that the at least one of the one or more PDSCH reception occasions is not QCL with a DL RS.
  • the method of Aspect 36 includes where the TCI state configuration indicates at least one of the plurality of TCI states is not associated with the DL RS, where the indication includes a TCI activation command to activate one or more TCI codepoints, where each of the one or more TCI codepoints is associated with one or more TCI states from the plurality of TCI states, and where at least one of the one or more TCI codepoints indicates the first TCI state as associated with a second QCL assumption of QCL with the DL RS and the second TCI state as associated with the first QCL assumption.
  • the method of Aspect 37 includes where the indication further includes a beam indication DCI to indicate one TCI codepoint from the at least one or more TCI codepoints.
  • the method of any of Aspects 37 or 38 includes where the TCI activation command indicates an order in which the first TCI state and the second TCI state are activated.
  • the method of any of Aspects 36 to 39 includes where each of the plurality of TCI states are joint uplink and downlink TCI states.
  • the method of any of Aspects 36 to 40 includes where each of the plurality of TCI states include an uplink TCI state or a downlink TCI state.
  • the method of any of Aspects 36 to 41 includes where the scheduling PDCCH includes a TCI state selection field indicating to select the first TCI state, the second TCI state, or both of the first TCI state and the second TCI state for the one or more PDSCH reception occasions.
  • the method of Aspect 42 includes where the TCI state selection field is associated with multiple values, including a value to indicate each of to select the first TCI state for a first subset of the one or more PDSCH reception occasions, to select the second TCI state for a second subset of the one or more PDSCH reception occasions.
  • the method of any of Aspects 36 to 43 includes where the scheduling PDCCH includes a first TCI state selection field related to selecting one or more TCI states that are associated with a second QCL assumption of QCL with the DL RS, and a second TCI state selection field in the scheduling PDCCH related to selecting one or more TCI states that are associated with the first QCL assumption.
  • the method of Aspect 44 includes where the first TCI state selection field in the scheduling PDCCH indicates to select the first TCI state for a first subset of the one or more PDSCH reception occasions, and where the second TCI state selection field in the scheduling PDCCH indicates to select the second TCI state for the second subset of the one or more PDSCH reception occasions.
  • the method of any of Aspects 44 or 45 includes where a reserved codepoint of the first TCI state selection field in the scheduling PDCCH indicates no selection of a TCI state that associated with the second QCL assumption.
  • the method of any of Aspects 44 to 46 includes transmitting, for the UE, a configuration indicating that the second TCI state selection field is present in the scheduling PDCCH.
  • the method of any of Aspects 36 to 47 includes where the scheduling PDCCH includes a TCI state selection field related to selecting one or more TCI states that are associated with a second QCL assumption of QCL with the DL RS, and, where a configuration indicating that a further TCI state selection field related to selecting one or more TCI states that are associated with the second QCL assumption is not present, selecting, for the one or more PDSCH reception occasions, only TCI states that are associated with the second QCL assumption among the first TCI state and the second TCI state.
  • the method of Aspect 48 includes where selecting, for the one or more PDSCH reception occasions, only TCI states that are associated with the second QCL assumption among the first TCI state and the second TCI state is based at least in part on the UE not supporting TCI states that are associated with the first QCL assumption.
  • the method of any of Aspects 36 to 49 includes where the scheduling PDCCH includes a legacy TCI state selection field related to selecting one or more TCI states that are associated with a second QCL assumption of QCL with the DL RS, and, where a configuration indicating that a further TCI state selection field related to selecting one or more TCI states that are associated with a second QCL assumption of QCL with the DL RS is not present, selecting, for the one or more PDSCH reception occasions, all TCI states that are associated with the first QCL assumption among the first TCI state and second TCI state.
  • the method of Aspect 50 includes where selecting, for the one or more PDSCH reception occasions, all TCI states that are associated with the first QCL assumption among the first TCI state and second TCI state is based at least in part on receiving a capability indicator indicating that the UE supports bundling QCL for multiple TCI states that are associated with the first QCL assumption.
  • the method of any of Aspects 50 or 51 includes where selecting, for the one or more PDSCH reception occasions, all TCI states that are associated with the first QCL assumption among the first TCI state and second TCI state is based at least in part on a time offset between transmitting the scheduling PDCCH and transmitting the first PDSCH reception occasion of the one or more PDSCH reception occasions achieving a threshold time.
  • the method of any of Aspects 36 to 52 includes where the scheduling PDCCH includes a TCI state selection field related to selecting one or more TCI states that are associated with a second QCL assumption of QCL with the DL RS, and, where a configuration indicating that a further TCI state selection field related to selecting one or more TCI states that are associated with the first QCL assumption is not present, selecting, for the one or more PDSCH reception occasions, the first TCI state among the one or more TCI states that are associated with the first QCL assumption from the first TCI state and the second TCI state.
  • the method of Aspect 53 includes where selecting, for the one or more PDSCH reception occasions, the first TCI state is based at least in part on the UE not supporting bundling QCL for multiple TCI states that are associated with the first QCL assumption.
  • the method of any of Aspects 36 to 54 includes where the TCI state configuration indicates at least one of the plurality of TCI states is associated with the first QCL assumption and is associated with a group index.
  • the method of Aspect 55 includes where a reset indicator corresponding to the at least one of the plurality of TCI states that is associated with the first QCL assumption and is associated with the group index is included in one of the indication or the scheduling PDCCH.
  • the method of Aspect 56 includes resetting, based on the reset indicator, the QCL for the one or more PDSCH reception occasions associated with one or more TCI states associated with the group index.
  • the method of any of Aspects 56 or 57 includes resetting, based on transmitting the reset indicator for the group index, the QCL for the one or more PDSCH reception occasions associated with the one or more TCI states associated with the group index after an application time.
  • the method of any of Aspects 56 to 58 includes applying, based on transmitting the reset indicator indicating not to reset the QCL for a second group, the first QCL assumption that the one or more PDSCH reception occasions associated with one or more TCI states in the second group are QCLed with each other and also QCLed with prior PDSCH reception occasions associated with the one or more TCI states in the second group.
  • the method of any of Aspects 55 to 59 includes where the scheduling PDCCH includes the reset indicator.
  • the method of Aspect 60 includes resetting, based on the reset indicator indicating to reset QCL, the QCL for the one or more PDSCH reception occasions associated with the one or more TCI states associated with the group index among the one or more PDSCH reception occasions and future PDSCH reception occasions.
  • the method of any of Aspects 60 or 61 includes applying, based on transmitting the reset indicator indicating not to reset the QCL for a second group, a third QCL assumption that the one or more PDSCH reception occasions associated with one or more TCI states in the second group are QCLed with each other and also QCLed with prior PDSCH reception occasions associated with the one or more TCI states in the second group.
  • the method of any of Aspects 36 to 62 includes where the TCI state configuration indicates each of the plurality of TCI states are associated with a second QCL assumption of QCL with the DL RS, and where the scheduling PDCCH indicates zero or more of the first TCI state and the second TCI state and zero or more QCL groups that are associated with the first QCL assumption for the one or more PDSCH reception occasions.
  • the method of Aspect 63 includes where the scheduling PDCCH includes a TCI state selection field that is associated with multiple codepoint values, including a codepoint value to indicate selecting zero or more of the first TCI state and the second TCI state for a first subset of the one or more PDSCH reception occasions, and selecting zero or more of the zero or more QCL groups for a second subset of the one or more PDSCH reception occasions.
  • the scheduling PDCCH includes a TCI state selection field that is associated with multiple codepoint values, including a codepoint value to indicate selecting zero or more of the first TCI state and the second TCI state for a first subset of the one or more PDSCH reception occasions, and selecting zero or more of the zero or more QCL groups for a second subset of the one or more PDSCH reception occasions.
  • the method of Aspect 64 includes where a mapping between one of the multiple codepoint values of a TCI state selection field and one or more TCI states or QCL groups are based on one of a predefined rule, a RRC configuration, or a MAC-CE.
  • the method of any of Aspects 64 or 65 includes selecting the zero or more of the zero or more QCL groups for the second subset of the one or more PDSCH reception occasions based on a new indicator field indicating no QCL group without DL RS or the new indicator field is disabled.
  • the method of any of Aspects 64 to 66 includes where transmitting the scheduling PDCCH includes transmitting a first TCI state selection field indicating to select zero or more TCI states associated with a second QCL assumption of QCL with the DL RS, among the first TCI state and second TCI states, for a first subset of the one or more PDSCH reception occasions, and transmitting a second TCI state selection field associated with multiple codepoint values to indicate to select one or more QCL groups associated with the first QCL assumption, for a second subset of the one or more PDSCH reception occasions.
  • the method of Aspect 67 includes where a mapping between the codepoint of the new TCI state selection field and one or more TCI states or QCL groups are based on one of a predefined rule, a RRC configuration, or a MAC-CE.
  • the method of any of Aspects 36 to 68 includes building a QCL profile for the one or more PDSCH reception occasions based at least in part on one or more previous PDSCH reception occasions, wherein the first QCL assumption is based on the QCL profile.
  • the method of any of Aspects 1 to 69 includes where the DL RS is a tracking reference signal.
  • Aspect 71 is an apparatus for wireless communication including one or more processors, one or more memories coupled with the one or more processors, and instructions stored in the one or more memories and operable, when executed by the one or more processors, to cause the apparatus to perform any of the methods of Aspects 1 to 70.
  • Aspect 72 is an apparatus for wireless communication including means for performing any of the methods of Aspects 1 to 70.
  • Aspect 73 is one or more computer-readable media including code executable by one or more processors for wireless communications, the code including code for performing any of the methods of Aspects 1 to 70.
  • Information and signals may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof.
  • a specially programmed device such as but not limited to a processor, a digital signal processor (DSP) , an ASIC, a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein.
  • DSP digital signal processor
  • FPGA field programmable gate array
  • a specially programmed processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a specially programmed processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a non-transitory computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a specially programmed processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium may be any available medium that can be accessed by a general purpose or special purpose computer.
  • computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • Disk and disc include compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des aspects de la présente invention concernent la réception, en provenance d'un nœud de réseau, d'une configuration d'état d'indicateur de configuration de transmission (TCI) indiquant une pluralité d'états de TCI, la réception, en provenance du nœud de réseau, d'une indication d'activer ou de sélectionner un premier état de TCI et un second état de TCI parmi la pluralité d'états de TCI, ainsi que la réception, en provenance du nœud de réseau, d'un canal physique de commande de liaison descendante (PDCCH) de planification qui planifie une ou plusieurs occasions de réception de canal physique partagé de liaison descendante (PDSCH), une première hypothèse de quasi-colocalisation (QCL) pour au moins l'une de la ou des occasions de réception de PDSCH étant que la ou les occasions de réception de PDSCH ne sont pas quasi colocalisées (QCLed) avec un signal de référence de liaison descendante (RS DL). D'autres aspects concernent la transmission de la configuration d'état de TCI, de l'indication et du PDCCH de planification.
PCT/CN2023/125352 2023-10-19 2023-10-19 Techniques de groupage de quasi-colocalisation (qcl) pour des informations de commande de liaison descendante unique (s-dci) pour de multiples points d'émission/réception (mtrp) avec des états d'indication de configuration de transmission (tci) unifiés Pending WO2025081402A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/125352 WO2025081402A1 (fr) 2023-10-19 2023-10-19 Techniques de groupage de quasi-colocalisation (qcl) pour des informations de commande de liaison descendante unique (s-dci) pour de multiples points d'émission/réception (mtrp) avec des états d'indication de configuration de transmission (tci) unifiés

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/125352 WO2025081402A1 (fr) 2023-10-19 2023-10-19 Techniques de groupage de quasi-colocalisation (qcl) pour des informations de commande de liaison descendante unique (s-dci) pour de multiples points d'émission/réception (mtrp) avec des états d'indication de configuration de transmission (tci) unifiés

Publications (1)

Publication Number Publication Date
WO2025081402A1 true WO2025081402A1 (fr) 2025-04-24

Family

ID=95447655

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/125352 Pending WO2025081402A1 (fr) 2023-10-19 2023-10-19 Techniques de groupage de quasi-colocalisation (qcl) pour des informations de commande de liaison descendante unique (s-dci) pour de multiples points d'émission/réception (mtrp) avec des états d'indication de configuration de transmission (tci) unifiés

Country Status (1)

Country Link
WO (1) WO2025081402A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022126149A2 (fr) * 2021-04-05 2022-06-16 Futurewei Technologies, Inc. Système et procédé pour établir des communications à l'aide de points d'émission-réception multiples intercellulaires et intracellulaires
EP4181447A1 (fr) * 2020-07-31 2023-05-17 Huawei Technologies Co., Ltd. Procédé d'indication de qcl et dispositif associé
US20230239823A1 (en) * 2020-10-22 2023-07-27 Huawei Technologies Co., Ltd. System and Method for Uplink and Downlink in Multi-Point Communications

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4181447A1 (fr) * 2020-07-31 2023-05-17 Huawei Technologies Co., Ltd. Procédé d'indication de qcl et dispositif associé
US20230239823A1 (en) * 2020-10-22 2023-07-27 Huawei Technologies Co., Ltd. System and Method for Uplink and Downlink in Multi-Point Communications
WO2022126149A2 (fr) * 2021-04-05 2022-06-16 Futurewei Technologies, Inc. Système et procédé pour établir des communications à l'aide de points d'émission-réception multiples intercellulaires et intracellulaires

Similar Documents

Publication Publication Date Title
US20250294573A1 (en) Techniques for recycling antennas for multi-component carrier (cc) operations in wireless communications
US20240147494A1 (en) Techniques for updating transmission configuration indicator (tci) states in wireless communications
US12323245B2 (en) Techniques for transmitting repetitions in wireless communications
WO2023159530A1 (fr) Techniques de découverte de dispositifs prenant en charge une coopération dans des communications sans fil
WO2025081402A1 (fr) Techniques de groupage de quasi-colocalisation (qcl) pour des informations de commande de liaison descendante unique (s-dci) pour de multiples points d'émission/réception (mtrp) avec des états d'indication de configuration de transmission (tci) unifiés
US12501444B2 (en) Techniques for linking periodic resource grants in wireless communications
US20250274886A1 (en) Techniques for adapting transmission of wireless communications based on synchronization signal block (ssb) indication
US12207273B2 (en) Techniques for communicating over configured grant resources with high round trip times
WO2025260267A1 (fr) Techniques pour émissions de canal d'accès aléatoire multiples dans des communications sans fil denses en liaison montante
US20250119916A1 (en) Techniques for configuring multiplexing of uplink control information in wireless communications
US20250240143A1 (en) Techniques for reporting coherence type or reference signal type in wireless communications
US20240057037A1 (en) Techniques for transmission configuration indicator (tci) state indication for component carriers in different modes
US20240397423A1 (en) Techniques for scheduling uplink discovery signals in wireless communications
WO2025081404A1 (fr) Techniques de groupage de quasi-colocalisation (qcl) pour un seul point d'émission/réception multiple (mtrp) basé sur des informations de commande de liaison descendante (dci)
US12323222B2 (en) Techniques for scrambling multiple access in wireless communications
US20240414732A1 (en) Techniques for uplink transmitter frequency resource switching in wireless communications
US20240114540A1 (en) Techniques for sending assistance information for cancelling interference in wireless communications
US12213060B2 (en) Techniques for identifying synchronization signals from repeaters in wireless communications
WO2025007228A1 (fr) Précodage de communications sans fil à l'aide de techniques en boucle fermée et en boucle ouverte
WO2025076721A1 (fr) Techniques de recyclage d'opportunités de transmission inutilisées dans des communications sans fil
WO2025227416A1 (fr) Techniques de segmentation de blocs pour appliquer des codes polaires à des communications sans fil
US20250098022A1 (en) Configuring skipping of paging early indication in wireless communications
US12207206B2 (en) Techniques for reducing resource usage for dual subscription dual active wireless communications
WO2024011336A1 (fr) Techniques de configuration d'états d'indicateur de configuration de transmission (tci) pour de multiples points de transmission/réception
US20230309098A1 (en) Techniques for scheduling multi-user sidelink communications in multiple time periods

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23955729

Country of ref document: EP

Kind code of ref document: A1