Techniques for cross-component carrier scheduling with joint downlink and uplink transmission configuration indicator states

Abstract

Methods, systems, and apparatus for wireless communication are described. User equipment (UE) can receive control signaling including scheduling information. This scheduling information may include indications of the joint downlink and uplink transmission configuration indicator (TCI) status for a shared beam. The UE can apply the joint downlink and uplink TCI status at each component carrier to activate the shared beam to transmit or receive one or more uplink transmissions at the UE. The UE can use the shared beam to schedule communication with a base station, one or more transmit-receive points (TRPs), or both, across the component carriers. This communication may include transmitting at least one uplink transmission during one or more uplink resources indicated in the scheduling information, and receiving at least one downlink transmission during one or more downlink resources indicated in the scheduling information.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 107,900, filed November 30, 2021, entitled “TECHNIQUESFOR CROSS-COMPONENT CARRIER SCHEDULING OF A JOINT DOWNLINK AND UPLINKTRANSMISSION CONFIGURATION INDICATOR STATE”, which is assigned to the assignee of this application and is expressly incorporated herein by reference.

[0003] open field

[0004] The following content relates to wireless communications, including techniques for cross-component carrier scheduling for joint downlink and uplink Transport Configuration Indicator (TCI) states.

[0005] background

[0006] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems can employ various technologies, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication from multiple communication devices, which may also be referred to as User Equipment (UE).

[0007] Overview

[0008] The described technology relates to improved methods, systems, devices, and apparatuses for supporting cross-component carrier scheduling for joint downlink and uplink Transport Configuration Indicator (TCI) states. The described technology provides a User Equipment (UE) receiving control signaling including scheduling information from a base station or Transmitter Receiver Point (TRP). This scheduling information may include an indication of a joint downlink and uplink TCI state identifier for a shared beam, a Scheduling Request Indicator (SRI) field indicating the shared beam or mapped to the joint downlink and downlink TCI state, an indication of the shared beam, one or more TRP identifiers, or a combination thereof. The UE may apply the joint downlink and uplink TCI state at each component carrier to activate the shared beam to transmit one or more uplink transmissions or receive one or more downlink transmissions at the UE. In some cases, the UE may use the shared beam to schedule communication with a base station, one or more TRPs, or both, across component carriers. This communication may include transmitting at least one uplink transmission during one or more uplink resources indicated in the scheduling information, and receiving at least one downlink transmission during one or more downlink resources indicated in the scheduling information.

[0009] A method for wireless communication at a UE is described. The method may include: receiving control signaling including scheduling information based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers; and communicating with a base station based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0010] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. These instructions may be executed by the processor to cause the apparatus to: receive control signaling including scheduling information based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers; and communicate with a base station based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0011] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving control signaling including scheduling information based on a joint downlink and uplink TCI state, the scheduling information being used across one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers; and means for communicating with a base station based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0012] A non-transient computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive control signaling including scheduling information based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers; and communicate with a base station based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0013] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, receiving control signaling may include operations, features, means, or instructions for receiving indications of the combined downlink and uplink TCI status.

[0014] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, the indication may be a field in control signaling that includes joint downlink and uplink TCI status identifiers.

[0015] In some examples of the methods, apparatus (devices), and non-transient computer-readable media described herein, the indication includes fields from the SRI.

[0016] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, communicating with a base station may include operations, features, means, or instructions for receiving downlink transmissions from the base station using one or more downlink resources and transmitting uplink transmissions to the base station using one or more uplink resources.

[0017] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means or instructions for scheduling downlink and uplink transmissions across the set of multiple component carriers based on the shared analog beam of the set of multiple component carriers and the common beam corresponding to the joint downlink and uplink transmission configuration indicator states.

[0018] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means or instructions for receiving from the component carriers of the set comprising multiple component carriers an indication of a shared beam for one or more downlink channels and one or more uplink channels across the set comprising multiple component carriers.

[0019] In some examples of the methods, apparatus (devices) and nontransient computer-readable media described herein, receiving control signaling may include operations, features, means, or instructions for: receiving a first control signaling including a first indication of a component carrier list, the component carrier list containing one or more component carriers from a set comprising a plurality of component carriers; and receiving a second control signaling including a second indication of a joint downlink and uplink TCI state.

[0020] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, one or more component carriers in a set comprising multiple component carriers share the same analog beam.

[0021] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, one or more component carriers in a set comprising multiple component carriers support joint downlink and uplink TCI states.

[0022] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, one or more component carriers in the set comprising multiple component carriers support either downlink TCI state or uplink TCI state.

[0023] A method for wireless communication at a UE is described. The method may include: receiving control signaling including scheduling information for one or more downlink resources and one or more uplink resources associated with a common beam across a set of multiple TRPs; and communicating with one or more TRPs in the set of multiple TRPs across a set of multiple component carriers based on the common beam, wherein a combined downlink and uplink TCI state is associated with the communication with the one or more TRPs.

[0024] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. These instructions may be executed by the processor to cause the apparatus to: receive control signaling including scheduling information for association with one or more downlink resources and one or more uplink resources across a common beam comprising a set of multiple TRPs; and communicate with one or more TRPs in the set of multiple TRPs across a set comprising multiple component carriers based on the common beam, wherein a combined downlink and uplink TCI state is associated with communication with the one or more TRPs.

[0025] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving control signaling including scheduling information for one or more downlink resources and one or more uplink resources associated with a common beam across a set of multiple TRPs; and means for communicating with one or more TRPs in the set of multiple TRPs across a set of multiple component carriers based on the common beam, wherein a combined downlink and uplink TCI state is associated with communicating with the one or more TRPs.

[0026] A non-transient computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive control signaling including scheduling information for one or more downlink resources and one or more uplink resources associated with a common beam across a set of multiple TRPs; and communicate with one or more TRPs in the set of multiple TRPs across a set of multiple component carriers based on the common beam, wherein joint downlink and uplink TCI states are associated with communication with the one or more TRPs.

[0027] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, receiving control signaling may include operations, features, means, or instructions for: receiving indications of combined downlink and uplink TCI states and one or more TRP identifiers corresponding to the one or more TRPs, and scheduling communications based on the indications.

[0028] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, the indication may be a field in control signaling that includes a combined downlink and uplink TCI status identifier and one or more TRP identifiers.

[0029] In some examples of the methods, apparatus (devices), and non-transient computer-readable media described herein, the indication includes fields from the SRI.

[0030] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, communicating with the one or more TRPs may include operations, features, means, or instructions for receiving downlink transmissions using one or more downlink resources and transmitting uplink transmissions using one or more uplink resources.

[0031] A method for wireless communication at a base station is described. The method may include: transmitting control signaling including scheduling information to a UE based on a joint downlink and uplink TCI state, the scheduling information being used across one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers; and communicating with the UE based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0032] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. These instructions may be executed by the processor to cause the apparatus to: transmit control signaling including scheduling information to a UE based on a joint downlink and uplink TCI state, the scheduling information being used across one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers; and communicate with the UE based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0033] Another apparatus for wireless communication at a base station is described. The apparatus may include: means for transmitting control signaling including scheduling information to a UE based on a joint downlink and uplink TCI state, the scheduling information being used across one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers; and means for communicating with the UE based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0034] A non-transient computer-readable medium is described, storing code for wireless communication at a base station. The code may include instructions executable by a processor to: transmit control signaling to a UE based on a joint downlink and uplink TCI state, the scheduling information being used across one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers; and communicate with the UE based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0035] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, transmission control signaling may include operations, features, means, or instructions for transmitting indications of the combined downlink and uplink TCI status.

[0036] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, the indication may be a field in control signaling that includes joint downlink and uplink TCI status identifiers.

[0037] In some examples of the methods, apparatus (devices), and non-transient computer-readable media described herein, the indication includes fields from the SRI.

[0038] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, communicating with a UE may include operations, features, means, or instructions for transmitting downlink transmissions to the UE using one or more downlink resources and receiving uplink transmissions using one or more uplink resources.

[0039] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means or instructions for scheduling downlink and uplink transmissions across the set of multiple component carriers based on the shared analog beam of the set of multiple component carriers and the common beam corresponding to the joint downlink and uplink transmission configuration indicator states.

[0040] Examples of methods, apparatus (devices), and non-transient computer-readable media described herein may further include operations, features, means, or instructions for transmitting from the set of component carriers comprising a plurality of component carriers an indication of a common beam for one or more downlink channels and one or more uplink channels across the set of component carriers.

[0041] In some examples of the methods, apparatus (devices) and nontransient computer-readable media described herein, transmission control signaling may include operations, features, means, or instructions for: transmitting first control signaling including a first indication of a component carrier list, the component carrier list containing one or more component carriers from a set comprising a plurality of component carriers; and transmitting second control signaling including a second indication of a joint downlink and uplink TCI state.

[0042] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, one or more component carriers in a set comprising multiple component carriers share the same analog beam.

[0043] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, one or more component carriers in a set comprising multiple component carriers support joint downlink and uplink TCI states.

[0044] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, one or more component carriers in the set comprising multiple component carriers support either downlink TCI state or uplink TCI state. Brief description of the attached diagram

[0046] Figures 1 to 3 Examples of wireless communication systems that support cross-component carrier scheduling for joint downlink and uplink Transport Configuration Indicator (TCI) states according to various aspects of this disclosure are explained.

[0047] Figure 4 An example of a transmission diagram illustrating techniques for cross-component carrier scheduling of joint downlink and uplink TCI states, based on various aspects of this disclosure, is explained.

[0048] Figure 5 and 6 An example of the process flow for cross-component carrier scheduling of joint downlink and uplink TCI states, based on various aspects of this disclosure, is explained.

[0049] Figure 7 and 8 A block diagram of an apparatus for cross-component carrier scheduling of joint downlink and uplink TCI states, according to various aspects of this disclosure, is explained.

[0050] Figure 9 A block diagram of a communication manager supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown.

[0051] Figure 10 A diagram of a system including a device for supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown.

[0052] Figure 11 and 12 A block diagram of an apparatus supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown.

[0053] Figure 13 A block diagram of a communication manager supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown.

[0054] Figure 14 A diagram of a system including a device for supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown.

[0055] Figures 15 to 20 A flowchart illustrating a method for cross-component carrier scheduling of joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown.

[0056] Detailed description

[0057] In some wireless communication systems, a User Equipment (UE) can be configured to have beam indications (such as Transmission Configuration Indicators (TCIs) for both downlink and uplink resources for one or more beams. For example, the UE can receive signaling configuring the UE to operate in a TCI state. The UE can decode downlink transmissions from a base station based on the TCI state of the beam used for downlink transmissions. Similarly, the UE can transmit uplink transmissions to the base station based on the TCI state of the beam used for uplink transmissions. In some examples, such as when the UE communicates across multiple component carriers, the UE can use a shared beam to communicate downlink and uplink transmissions. Therefore, operating based on separate TCI states for uplink and downlink communication can result in additional processing time, as well as signaling and network overhead. Therefore, the UE can use joint downlink and uplink TCI states to communicate downlink and uplink transmissions across multiple component carriers using a shared beam. However, currently, there may not be a method for the UE to schedule joint downlink and uplink TCI states for multiple component carriers, multiple Transmitter-Receiver Points (TRPs), or both.

[0058] As described herein, a base station or TRP may transmit control signaling to the UE that may schedule downlink and uplink communications across multiple component carriers, multiple TRPs, or a shared beam of both. In some examples, the UE may receive control signaling, such as a downlink control information (DCI) message, from the base station or TRP on a first component carrier (CC1). This control signaling may include an indication of a joint downlink and uplink TCI state identifier for scheduling communications across multiple component carriers sharing an analog beam with the same shared beam. Additionally or alternatively, the control signaling may include fields in a scheduling request indicator (SRI) that may indicate a shared beam or be mapped to a joint downlink and uplink TCI state. The UE may determine which component carriers share the analog beam based on a list of component carriers, which may be included in different control signaling (e.g., radio resource control (RRC) signaling). The component carrier list can indicate component carriers that support joint downlink and uplink TCI states, or can reuse cross-component carrier indications for downlink or uplink TCI states.

[0059] In some other examples, the UE may communicate with multiple TRPs, each associated with one or more component carriers. The UE may receive control signaling that schedules communication with multiple TRPs using shared downlink and uplink beams. For example, the UE may receive control signaling (such as a DCI message) on CC1 from a first TRP (TRP1), which includes indications of a joint TCI status identifier or SRI, one or more TRP identifiers, or a combination thereof. The control signaling may schedule one or more TRPs based on the TRP identifiers to convey downlink and uplink transmissions using additional component carriers (e.g., a second component carrier (CC2) if the control signaling includes one TRP identifier, or multiple other component carriers if the control signaling includes multiple TRP identifiers).

[0060] The aspects of this disclosure are initially described in the context of a wireless communication system. The aspects of this disclosure are further described in the context of transmission diagrams and process flows. The aspects of this disclosure are further explained and described by means of, and with reference to, apparatus diagrams, system diagrams, and flowcharts relating to techniques for cross-component carrier scheduling of joint downlink and uplink transmission configuration indicator states.

[0061] Figure 1Examples of wireless communication systems supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, are described. Wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low latency communication, communication with low-cost and low-complexity devices, or any combination thereof.

[0062] Base station 105 can be distributed across a geographical area to form wireless communication system 100, and can be different types of devices or devices with different capabilities. Base station 105 and UE 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, and UE 115 and base station 105 can establish one or more communication links 125 on the coverage area 110. Coverage area 110 can be an example of a geographical area over which base station 105 and UE 115 can support signal communication according to one or more radio access technologies.

[0063] Each UE 115 can be distributed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. Each UE 115 can be a different type of device or a device with different capabilities. Figure 1 The document describes some example UE 115s. The UE 115 described herein can communicate with various types of devices, such as other UE 115s, base station 105, or network equipment (e.g., core network nodes, relay equipment, integrated access and backhaul (IAB) nodes, or other network equipment). Figure 1 As shown in the image.

[0064] Each base station 105 may communicate with the core network 130, or with each other, or both. For example, base station 105 may interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base stations 105 may communicate with each other directly (e.g., directly between base stations 105), indirectly (e.g., via the core network 130), or directly and indirectly on backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some examples, backhaul link 120 may be or include one or more radio links.

[0065] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art as, base transceiver station, radio base station, access point, radio transceiver, B node, evolved B node (eNB), next-generation B node or gigabit B node (any of which may be referred to as gNB), home B node, home evolved B node, or other suitable terms.

[0066] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0067] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, as well as base station 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 As shown in the image.

[0068] UE 115 and base station 105 can wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the radio spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation can be used in conjunction with frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0069] In some examples (e.g., in a carrier aggregation configuration), the carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. The carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel grid for discovery by UE 115. The carrier may operate in an autonomous mode in which initial acquisition and connection can be performed by UE 115 via that carrier, or in a non-autonomous mode in which the carrier may connect to carriers anchored using different carriers (e.g., different carriers of the same or different radio access technologies).

[0070] The communication link 125 shown in the wireless communication system 100 may include uplink transmission from UE 115 to base station 105, or downlink transmission from base station 105 to UE 115. The carrier may carry downlink or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0071] A carrier may be associated with a bandwidth of the radio frequency spectrum, and in some examples, this carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of several defined bandwidths of the carrier of a radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have a hardware configuration that supports communication over the carrier bandwidth, or may be configurable to support communication over a single carrier bandwidth within a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate over a portion (e.g., a subband, BWP) or all of the carrier bandwidth.

[0072] The signal waveform transmitted on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the code rate of the modulation scheme, or both). Thus, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate the UE 115 can achieve. Wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and using multiple spatial layers can further improve the data rate or data integrity of communication with the UE 115.

[0073] One or more parameter designs for a carrier can be supported, where the parameter design may include a subcarrier spacing (∆f) and a cyclic prefix. A carrier can be divided into one or more BWPs with the same or different parameter designs. In some examples, the UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for the UE 115 can be limited to one or more active BWPs.

[0074] The time intervals of base station 105 or UE 115 can be expressed as multiples of a basic time unit, such as a sampling period Ts = 1 / (∆fmax∙Nf) seconds, where ∆fmax represents the maximum supported subcarrier spacing and Nf represents the maximum supported Discrete Fourier Transform (DFT) size. The time intervals of communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0075] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into several time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include several symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple mini-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0076] A subframe, time slot, mini-slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0077] Physical channels can be multiplexed on a carrier using various techniques. Physical control channels and physical data channels can be multiplexed on a downlink carrier, for example, using one or more of time-division multiplexing (TDM), frequency-division multiplexing (FDM), or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for physical control channels can be defined by the number of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more of the UEs 115 can monitor or search control regions for control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for control channel candidates can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information in a control information format having a given payload size. The search space set may include a common search space set configured to send control information to multiple UEs 115 and a UE-specific search space set configured to send control information to a specific UE 115.

[0078] Each base station 105 may provide communication coverage via one or more cells (e.g., macrocells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with base station 105 (e.g., on a carrier) and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or others). In some examples, a cell may also refer to a geographic coverage area 110 or a portion of geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. The extent of such cells may vary from smaller areas (e.g., structures, subsets of structures) to larger areas depending on various factors (such as the capabilities of base station 105). For example, a cell may be or include buildings, subsets of buildings, or external space between or overlapping geographic coverage areas 110, among other examples.

[0079] Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access for UE 115 with a service subscription to a network provider supporting the macrocell. Small cells can be associated with a lower-power base station 105 (compared to macrocells) and can operate in the same or different (e.g., licensed or unlicensed) frequency bands as macrocells. Small cells can provide unrestricted access to UE 115 with a service subscription to a network provider, or can provide restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Base station 105 can support one or more cells and can also support communication on one or more cells using one or more component carriers.

[0080] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0081] In some examples, base station 105 may be mobile, and thus provide communication coverage to mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of base stations 105 use the same or different radio access technologies to provide coverage to various geographic coverage areas 110.

[0082] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately time-aligned. For asynchronous operation, base stations 105 can have different frame timing, and transmissions from different base stations 105 may not be time-aligned in some examples. The techniques described herein can be used for both synchronous and asynchronous operation.

[0083] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that have integrated sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or automate the behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wilderness survival monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial toll collection.

[0084] Some UEs 115 can be configured to operate in reduced-power modes, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication can be performed at reduced peak rates. Other power-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communication, operating on limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within the carrier, within the carrier's guard band, or outside the carrier.

[0085] Wireless communication system 100 may be configured to support ultra-reliable communication or low latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low latency communication (URLLC) or mission-critical communication. UE 115 may be designed to support ultra-reliable, low latency, or mission-critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private or group communication and may be supported by one or more mission-critical services, such as Mission-Critical Talk-to-Talk (MCPTT), Mission-Critical Video (MCVideo), or Mission-Critical Data (MCData). Support for mission-critical functions may include prioritization of services, and mission-critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low latency, mission-critical, and ultra-reliable low latency are used interchangeably herein.

[0086] In some examples, UE 115 may also be able to communicate directly with other UE 115 on a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UE 115s utilizing D2D communication may be within the geographic coverage area 110 of base station 105. Other UE 115s in such a group may be outside the geographic coverage area 110 of base station 105 or may be unable to receive transmissions from base station 105 for other reasons. In some examples, groups of UE 115s communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between the individual UE 115s without involving base station 105.

[0087] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate via vehicle-to-network (V2N) communication through one or more network nodes (e.g., base station 105) with roadside infrastructure (such as roadside units), or with the network, or with both.

[0088] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC). The EPC or 5GC may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by base station 105 associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may be connected to one or more network operator IP services 150. The IP service 150 may include access to the Internet, intranet, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0089] Some network devices (such as base station 105) may include sub-components, such as access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with each UE 115 through one or more other access network transport entities 145, which may be referred to as a radio headend, smart radio headend, or transmit / receive point (TRP). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio headends and ANCs) or combined into a single network device (e.g., base station 105).

[0090] Wireless communication system 100 can operate using one or more frequency bands in the range of, for example, 300 MHz to 300 GHz. For example, a 300 MHz to 3 GHz band is called a UHF band or decimeter band because the wavelength range is from about 1 decimeter to 1 meter. UHF waves can be blocked or redirected by buildings and environmental features, but these waves can penetrate various structures sufficiently for macrocells to provide service to UE 115 located indoors. Compared to transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, UHF wave transmission can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0091] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) zoning using a frequency band from 3 GHz to 30 GHz (also known as the centimeter band) or in the extremely high frequency (EHF) zoning using a spectrum (e.g., from 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, this can facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may suffer even greater atmospheric attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein can be employed across transmissions using one or more different frequency zonings, and the frequency band usage specified across these frequency zonings may vary by country or regulatory authority.

[0092] Wireless communication system 100 may utilize both licensed and unlicensed radio spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands, such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating in unlicensed radio spectrum bands, devices (such as base station 105 and UE 115) may employ carrier sensing for collision detection and avoidance. In some examples, operation in unlicensed frequency bands may be based on carrier aggregation configuration (e.g., LAA) in coordination with component carriers operating in licensed frequency bands. Operation in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, etc.

[0093] Base station 105 or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array with several rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0094] Base station 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. For example, a transmitting device may transmit multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device may receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0095] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating in an orientation relative to the antenna array experience constructive interference, while others experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include the transmitting or receiving device applying amplitude offset, phase offset, or both to the signals carried via the antenna elements associated with that device. The adjustments associated with each antenna element may be defined by a beamforming weight set associated with the orientation (e.g., the antenna array relative to the transmitting or receiving device, or relative to some other orientation).

[0096] Base station 105 or UE 115 may use beamsweeping technology as part of beamforming operations. For example, base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 105 in different directions. For example, base station 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmissions in different beam directions may be used (e.g., by the transmitting device (such as base station 105) or the receiving device (such as UE 115)) to identify the beam direction that base station 105 will use for later transmission or reception.

[0097] Some signals (such as data signals associated with a receiving device) may be transmitted by base station 105 in a single beam direction (e.g., the direction associated with the receiving device, such as UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0098] In some examples, transmissions performed by a device (e.g., by base station 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate combined beams for transmission (e.g., from base station 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and this feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. Base station 105 may transmit reference signals that can be precoded or unprecoded (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)). UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0099] A receiver device (e.g., UE 115) may attempt multiple receive configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105. For example, the receiver device may attempt multiple receive directions by: receiving via different antenna subarrays; processing received signals according to different antenna subarrays; receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array, any of which may be referred to as "listening" according to different receive configurations or receive directions. In some examples, the receiver device may use a single receive configuration to receive along a single beam direction (e.g., when a data signal is received). The single receive configuration may be aligned on a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0100] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer performs packet segmentation and reassembly for communication on logical channels. The Media Access Control (MAC) layer performs priority handling and multiplexes logical channels into transport channels. The MAC layer can also use error detection, error correction, or both to support MAC layer retransmissions to improve link efficiency. In the control plane, the RRC protocol layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and the base station 105 or core network 130 that support user plane data radio bearers. At the physical layer, transport channels can be mapped to physical channels.

[0101] UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data on communication link 125. HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve MAC layer throughput in poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support simultaneous time-slot HARQ feedback, where the device can provide HARQ feedback in a specific time slot for data received in previous symbols within that time slot. In other cases, the device may provide HARQ feedback in subsequent time slots or according to some other time interval.

[0102] As used herein, TCI or TCI state are examples of beam configurations or beam configuration states, and the techniques described herein for TCI or TCI state can also be applied to beam configurations or beam configuration states other than TCI or TCI state. For example, TCI state activation or deactivation for a set of TCI states can be applied to beam configuration activation or deactivation for a set of beam configuration states, and so on. Similarly, the techniques described herein for beam configurations or beam configuration states can also be applied to more specific examples of TCI or TCI state.

[0103] In some scenarios, UE 115 may receive indications of TCI or TCI states from base station 105, TRPs, etc. For example, base station 105 may indicate a TCI state for downlink communication from base station 105 to UE 115. However, base station 105 and UE 115 may manage uplink communication independently, which may incur additional processing time and signaling and network overhead. Therefore, UE 115 and base station 105 may use a single TCI state (which may be referred to as a joint downlink and uplink TCI state) to indicate quasi-co-location (QCL) rules to provide attributes for one or more shared beams for communication in both the downlink and uplink directions. In some scenarios, UE 115 may use the joint downlink and uplink TCI state to communicate using a shared beam across one or more TRPs, multiple component carriers (e.g., where UE 115 supports carrier aggregation or multi-carrier operation), or both, in both the downlink and uplink directions. For example, UE 115 can apply the combined downlink and uplink TCI states to each component carrier, to each BWP of each component carrier, or both to activate each component carrier. However, there may not be a method for UE 115 to schedule communication across multiple component carriers, multiple TRPs, or both based on the combined downlink and uplink TCI states.

[0104] In some examples, UE 115 may receive control signaling (such as a DCI message) that includes scheduling information. This scheduling information may include an indication of a joint downlink and uplink TCI state identifier for a shared beam, an SRI field indicating the shared beam or mapped to the joint downlink and uplink TCI state, an indication of the shared beam, one or more TRP identifiers, or a combination thereof. UE 115 may apply the joint downlink and uplink TCI state at each component carrier to activate the shared beam to transmit one or more uplink transmissions or receive one or more downlink transmissions at UE 115. In some examples, base station 105 or the TRP may transmit to UE 115 an indication of a list of component carriers supporting the joint downlink and uplink TCI state (e.g., in control signaling, such as RRC signaling). UE 115 may receive additional control signaling, such as dynamic control signaling (e.g., a DCI message), indicating which component carriers to activate. In some scenarios, UE 115 may use a shared beam to schedule communication with base station 105, one or more TRPs, or both across component carriers. This communication may include transmitting at least one uplink transmission during one or more uplink resources indicated in the scheduling information, and receiving at least one downlink transmission during one or more downlink resources indicated in the scheduling information.

[0105] Figure 2 Examples of wireless communication systems supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, are described. In some examples, wireless communication system 200 may implement various aspects of wireless communication system 100 and may include UE 215, base station 205, and communication link 240, which may be referenced... Figure 1 Examples of the described UE 115, base station 105, and communication link 125 are provided. In some examples, UE 215 may communicate with base station 205 by receiving control signaling or data via communication link 240 in downlink transmission using one or more downlink resources, transmitting control signaling or data via communication link 240 in uplink transmission using one or more uplink resources, or both. For example, base station 205 may transmit control signaling to UE 215 that may include scheduling information 220 for communication 225 across a common beam 230 of multiple component carriers 235 in both the downlink and uplink directions.

[0106] In some scenarios, UE 215 may receive an indication of TCI or TCI status from base station 205 (e.g., included in a DCI message). This indication may include one or more beam configurations or beam configuration states, such as the QCL relationship between downlink reference signals and demodulation reference signals (DMRS) ports. For example, the TCI status may include one or more QCL rules that associate reference signals (e.g., synchronization signals such as SSB; CSI-RS; positioning reference signals (PRS); or other reference signals) with channel characteristics (e.g., Doppler shift; Doppler spread; average delay; delay spread; one or more spatial parameters such as spatial filters; or other characteristics). Different types of QCLs (e.g., QCL type A, QCL type B, QCL type C, or QCL type D) may exist, each type based on a different set of QCL rules. Base station 205 may indicate the TCI status for downlink communication from base station 205 to UE 215. However, base station 205 and UE 215 can manage uplink communication independently, which may incur additional processing time and signaling and network overhead. Therefore, UE 215 and base station 205 can reduce signaling and network overhead (e.g., related to beam indication) by using a single TCI state (which may be referred to as a joint downlink and uplink TCI state) to indicate the QCL rules for communication in both the downlink and uplink directions. The joint downlink and uplink TCI state enables a unified TCI framework, which simplifies beam management procedures for downlink and uplink channels, data and control channels, or both, in wireless communication system 200.

[0107] In some examples, the joint downlink and uplink TCI state can indicate any number of QCL rules (e.g., three or more QCL rules) to provide attributes of one or more shared beams 230, where base station 205 and UE 215 use each shared beam 230 for both downlink and uplink. UE 215 can use the joint downlink and uplink TCI state to communicate across multiple component carriers 235 in both the downlink and uplink directions using the shared beam 230. For example, UE 215 can support carrier aggregation or multi-carrier operation, where base station 205 configures UE 215 with multiple downlink component carriers 235 and one or more uplink component carriers 235 according to carrier aggregation configuration. UE 215 can activate the joint downlink and uplink TCI state for one or more supported component carriers 235 sharing the shared beam 230 (e.g., based on receiving control signaling indicating component carriers 235). For example, UE 215 may apply the joint downlink and uplink TCI state to each component carrier 235, to each BWP of each component carrier 235, or both, to activate the component carrier 235. However, there may not be a method for UE 215 to schedule communication across multiple component carriers 235, multiple TRPs, or both based on the joint downlink and uplink TCI state.

[0108] In some examples, UE 215 can efficiently perform downlink and uplink beam management by reducing latency and signaling overhead for inter-cellular mobility (e.g., for intra-cell and Layer 1 (L1) or Layer 2 (L2) centered inter-cellular mobility), for a relatively large number of configured TCI states, or both. For example, UE 215 can use a shared beam 230 to perform multi-beam operation in a frequency range (such as frequency range 2 (FR2) or frequency range 1 (FR1)) for data and control signaling in both the downlink and uplink directions (e.g., for in-band carrier aggregation with a unified TCI framework for downlink and uplink link beam indication). Additionally or alternatively, if UE 215 is equipped with multiple antenna panels, UE 215 can identify and specify characteristics (e.g., by taking into account uplink coverage loss mitigation due to maximum permissible exposure (MPE)) to facilitate uplink beam selection based on uplink beam indication, leveraging a unified TCI framework for fast uplink panel selection.

[0109] In some scenarios, UE 215 may receive scheduling information 220 from base station 205, which indicates one or more uplink resources and one or more downlink resources for communication between UE 215 and base station 205. For example, UE 215 may receive the indication of scheduling information 220 in a DCI message, MAC control unit (MAC-CE), etc. In some scenarios, UE 215 and base station 205-b may improve signaling mechanisms by using dynamic control signaling (e.g., DCI messages or MAC-CE, instead of RRC signaling) to indicate scheduling information 220, thereby reducing latency and improving efficiency. In some examples, scheduling information 220 may include an indication of joint downlink and uplink TCI status identifiers and may be transmitted on component carrier 235-a. In some other examples, scheduling information 220 may include an SRI field that may include an indication of a shared beam 230 across component carrier 235. In some scenarios, UE 215 may use information in the SRI field to map to the joint downlink and uplink TCI states for the shared beam 230. In some examples, the shared beam 230 may be shared for transmitting uplink transmissions and receiving downlink transmissions at UE 215, base station 205, or both. Component carrier 235-a may indicate a shared downlink and uplink beam across one or more downlink and uplink channels (e.g., component carrier 235-a to component carrier 235-c), which may include inter-band channels.

[0110] In some examples, UE 215 may receive additional control signaling indicating a component carrier list. For example, UE 215 may receive RRC signaling that includes an indication of one or more component carriers 235 sharing the same analog beam as the common beam 230. Additionally or alternatively, UE 215 may receive dynamic control signaling (such as DCI messages, MAC-CE, etc.) activating one or more component carriers 235 (e.g., component carriers 235-a to 235-c) from the component carrier list. In some cases, the component carrier list may be dedicated to component carriers 235 supporting joint downlink and uplink TCI states. In other cases, the component carrier list may include component carriers 235 that previously supported downlink TCI states or uplink TCI but can be configured to have joint downlink and uplink TCI states for cross-component carrier indication.

[0111] In some cases, UE 215 may base its actions on scheduling information 220 (which will refer to...) Figure 4(As described in further detail) to schedule communication 225 across multiple component carriers 235 (e.g., communication 225-a to communication 225-c across component carriers 235-a to 235-c respectively). For example, UE 215 may use one or more downlink resources included in scheduling information 220 to receive downlink transmissions from base station 205. Additionally, UE 215 may use one or more uplink resources included in scheduling information 220 to transmit uplink transmissions to base station 205. UE 215 may use component carriers 235-a, 235-b, 235-c, or a combination thereof on a common beam 230 to receive downlink transmissions and transmit uplink transmissions (e.g., based on applying joint downlink and uplink TCI states to component carriers 235).

[0112] Figure 3 Examples of wireless communication systems supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, are described. In some examples, wireless communication system 300 may implement aspects of wireless communication system 100, wireless communication system 200, or both. Wireless communication system 300 may include UE 315 and communication links 340-a to 340-c, which may be as described in reference... Figure 1 and 2 Examples of UE 115, UE 215, communication link 125, communication link 240, or combinations thereof are described. Additionally, the wireless communication system 300 may include one or more TRPs 305 (such as TRPs 305-a to TRPs 305c), which are operable as described with reference to Figure 1 The described base station 105, network nodes, relay equipment, etc. In some examples, UE 315 may communicate with TRP 305-a to TRP 305-c via communication links 340-a to 340-c during downlink transmissions using one or more downlink resources, during uplink transmissions using one or more uplink resources, or both. For example, TRP 305-a may transmit control signaling, including scheduling information 320, to UE 315 via communication link 340-a for communication 325 across a common beam 330 of multiple component carriers 335 in both the downlink and uplink directions.

[0113] In some cases, UE 315 may receive indications of TCI or TCI states from TRP 305 (e.g., included in a DCI message). For example, TRP 305 may indicate the TCI state for downlink communication from TRP 305 to UE 315. However, TRP 305 and UE 315 may manage uplink communication independently, which may incur additional processing time, signaling, and network overhead. Therefore, UE 315 and TRP 305 can reduce signaling and network overhead (e.g., related to beam indication) by using a single TCI state (which may be referred to as a combined downlink and uplink TCI state) to indicate the QCL rules for communication in both the downlink and uplink directions.

[0114] In some examples, the combined downlink and uplink TCI state can indicate one or more QCL rules to provide attributes for one or more shared beams 330, wherein one or more TRPs 305 and UE 315 use each shared beam 330 for both downlink and uplink. UE 315 can use the combined downlink and uplink TCI state to communicate using the shared beam 330 across one or more TRPs 305, multiple component carriers 335, or both in both the downlink and uplink directions. For example, UE 315 can support carrier aggregation or multi-carrier operation, wherein base station 105 or TRP 305 is configured according to carrier aggregation and configures UE 315 across one or more TRPs (e.g., TRPs 305-a to TRP 305-c) using multiple downlink component carriers 335 and one or more uplink component carriers 335. UE 315 can activate a joint downlink and uplink TCI state for one or more supported component carriers 335 across one or more TRPs 305 sharing a common beam 330 (e.g., based on received control signaling indicating the component carrier 335). For example, UE 315 can apply the joint downlink and uplink TCI state to each component carrier 335, to each BWP of each component carrier 335, or both to activate the component carrier 335. However, there may not be a method for UE 315 to schedule communication across multiple component carriers 335, multiple TRPs 305, or both based on the joint downlink and uplink TCI state.

[0115] In some scenarios, UE 315 may receive scheduling information 320 from TRP 305, which indicates one or more uplink resources and one or more downlink resources for communication between UE 315 and one or more TRPs 305 (e.g., including TRP 305). For example, UE 315 may receive the indication of scheduling information 320 from TRP 305-a on component carrier 335-a in a DCI message, MAC-CE, etc. In some examples, scheduling information 320 may include indications of joint downlink and uplink TCI state identifiers. In some other examples, scheduling information 320 may include an SRI field, which may include an indication of a common beam 330 across component carrier 335. In some scenarios, UE 315 may use the information in the SRI field to map to joint downlink and uplink TCI states for the common beam 330. In some examples, the shared beam 330 can be shared for transmitting uplink transmissions and receiving downlink transmissions at UE 315, TRP 305, or both.

[0116] In some cases, UE 315 may base its decisions on scheduling information 320 (which will refer to...) Figure 4 (As described in further detail) to schedule communication 325 across multiple component carriers 335 (e.g., communication 325-a to communication 325-c across component carriers 335-a to 335-c respectively). For example, UE 315 may schedule communication with TRP 305a using component carrier 335-a, communication with TRP 305-b using component carrier 335-b, and communication with TRP 304-c using component carrier 335-c based on one or more TRP identifiers in the control signaling. In some cases, UE 315 may use one or more downlink resources included in the scheduling information 320 to receive downlink transmissions from TRP 305-a to TRP 305-c. Additionally, UE 315 may use one or more uplink resources included in the scheduling information 320 to transmit uplink transmissions to TRP 305-a to TRP 305-c. UE 315 may use component carriers 335-a, 335-b, 335-c or a combination thereof on the common beam 330 to receive downlink transmissions and transmit uplink transmissions (e.g., based on applying joint downlink and uplink TCI states to component carrier 335).

[0117] Figure 4Examples of transmission diagrams supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, are explained. In some examples, transmission diagram 400 may implement aspects of wireless communication system 100, wireless communication system 200, wireless communication system 300, or a combination thereof. For example, transmission diagram 400 can be implemented by referring to... Figure 1 , 2 This can be implemented using UE 115, UE 215, UE 315, base station 105, base station 205, or one or more TRPs 305 as described in section 3. In some cases, the base station or TRP may transmit control signaling to the UE including scheduling information 405, which can be used for communication 410 across multiple component carriers 420, multiple TRPs, or a shared beam across both in the downlink and uplink directions. In some examples, the shared beam 415 may be shared for one or more downlink channels and one or more uplink channels across multiple component carriers 420.

[0118] In some examples, the UE may receive control signaling (such as a DCI message) including scheduling information 405. Scheduling information 405 may include a joint downlink and uplink TCI status identifier for a shared beam 415, an indication of the shared beam 415 or an SRI field mapped to the joint downlink and uplink TCI status, or both. Additionally or alternatively, scheduling information 405 may include an indication of the shared beam 415, one or more TRP identifiers, or both. The UE may apply the joint downlink and uplink TCI status at each component carrier 420 to activate the shared beam 415 to transmit one or more uplink transmissions or receive one or more downlink transmissions at the UE. For example, the UE may use the shared beam 415 to activate component carrier 420-a for communication 410-a, component carrier 420-b for communication 410-b, component carrier 420-c for communication 410-c, or a combination thereof. In some examples, the base station or TRP may transmit to the UE an indication of a list of component carriers 420 that support joint downlink and uplink TCI states (e.g., in control signaling, such as RRC signaling). The UE may receive additional control signaling, such as dynamic control signaling (e.g., DCI messages), indicating which component carriers 420 to activate.

[0119] In some scenarios, the UE may schedule communications 410-a to 410-c based on scheduling information 405. For example, the UE may use a shared beam to communicate with a base station, one or more TRPs, or both across component carriers. Communication 410 may include transmitting at least one uplink transmission during one or more uplink resources indicated in scheduling information 405, and receiving at least one downlink transmission during one or more downlink resources indicated in scheduling information 405.

[0120] Figure 5 Examples of process flows supporting techniques for cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, are described. In some examples, process flow 500 may implement aspects of wireless communication systems 100 to 300, transmission diagram 400, or combinations thereof. Process flow 500 may illustrate an example of base station 505 transmitting control signaling including scheduling information to UE 515. The scheduling information may be used for communication between base station 505 and UE 515 in the downlink and uplink directions for a shared beam across multiple component carriers. Alternative examples are possible, some of which may be performed in a different order than described or not performed at all. In some cases, the processes may include additional features not mentioned below, or further processes may be added.

[0121] At 520, UE 515 may receive an indication of the component carrier list (e.g., via RRC signaling). In some cases, the component carrier list may be based on one or more component carriers sharing the same analog beam. In other cases, the component carrier list may be based on one or more component carriers supporting joint downlink and uplink TCI states, and one or more component carrier capabilities for using joint downlink and downlink TCI states for uplink communication and for downlink communication.

[0122] At 525, base station 505 may transmit scheduling information to UE 515. For example, base station 505 may transmit control signaling (such as DCI messages, MAC-CE, etc.) including scheduling information, which UE 515 may use to schedule communication between base station 505 and UE 515. The scheduling information may be used for one or more downlink resources and one or more uplink resources across multiple component carriers, and may be based on the joint downlink and uplink TCI states. For example, UE 515 may determine that each component carrier supports the joint downlink and uplink TCI states based on a list of component carriers received at 520. Control signaling may include indications of the component carriers on which communication is to be scheduled (e.g., dynamic indications in DCI messages).

[0123] At 530, UE 515 may receive an indication of the joint downlink and uplink TCI states from base station 505. For example, UE 515 may receive the indication in a field of control signaling that includes joint downlink and uplink TCI state identifiers for the joint downlink and uplink TCI states (e.g., a field in a DCI message). In some other examples, UE 515 may receive a field in SRI indicating shared beams or mapping to the joint downlink and uplink TCI states. At 535, UE 515 may apply the joint downlink and uplink TCI states to each component carrier based on the component carrier list received at 520. In some cases, UE 515 may receive dynamic control signaling (e.g., a DCI message, MAC-CE, etc.) indicating the component carriers to be scheduled from the component carrier list.

[0124] At locations 540 and 545, base station 505 and UE 515 can schedule downlink and uplink transmissions across multiple component carriers. In some cases, multiple component carriers may share the same analog beam with a common beam for joint downlink and uplink TCI states. In some cases, UE 515 may receive indication of the common beam from a component carrier (e.g., CC1). The common beam 415 may be shared for one or more downlink channels and one or more uplink channels across multiple component carriers.

[0125] At 550, UE 515 and base station 505 can communicate using a shared beam with joint downlink and uplink TCI states. For example, UE 515 can receive downlink transmissions from base station 505 using one or more downlink resources indicated in the scheduling information at 525, and can transmit uplink transmissions to base station 505 using one or more uplink resources indicated in the scheduling information at 525.

[0126] Figure 6 Examples of process flows supporting techniques for cross-component carrier scheduling of combined downlink and uplink TCI states, according to various aspects of this disclosure, are described. In some examples, process flow 600 may implement aspects of wireless communication systems 100 to 300, transmission diagram 400, or combinations thereof. Process flow 600 may describe an example of TRP 605 (such as TRP 605-a) transmitting control signaling including scheduling information to UE 615. The scheduling information may be used for communication between one or more TRPs 605 and UE 615 in the downlink and uplink directions for a shared beam across multiple component carriers. Alternative examples are possible, some of which may be performed in a different order than described or not performed at all. In some cases, the processes may include additional features not mentioned below, or further processes may be added.

[0127] At 620, TRP 605-a may transmit scheduling information to UE 615. For example, TRP 605-a may transmit control signaling (such as DCI messages, MAC-CE, etc.) including scheduling information, which UE 615 may use to schedule communication between TRP 605-a and UE 615, between TRP 605-b and UE 615, or both. The scheduling information may be used across multiple component carriers, multiple TRPs 605, or one or more downlink resources and one or more uplink resources, and may be based on joint downlink and uplink TCI states. For example, UE 615 may determine that each component carrier supports joint downlink and uplink TCI states based on a list of component carriers (e.g., received in control signaling, such as RRC signaling). Control signaling may include indications of component carriers on which communication is to be scheduled (e.g., dynamic indications in DCI messages).

[0128] At 625, UE 615 may receive indications of the joint downlink and uplink TCI states from TRP 605-a. For example, UE 615 may receive the indication in a field of control signaling that includes joint downlink and uplink TCI state identifiers for the joint downlink and uplink TCI states (e.g., a field in a DCI message). In some other examples, UE 615 may receive a field in SRI indicating shared beams or mapping to the joint downlink and uplink TCI states. At 630, UE 615 may apply the joint downlink and uplink TCI states to individual component carriers based on a component carrier list, indications of multiple component carriers, or both. For example, UE 615 may receive dynamic control signaling (e.g., a DCI message, MAC-CE, etc.) indicating the component carriers to be scheduled from the component carrier list.

[0129] At 635, UE 615 can schedule downlink and uplink transmissions across multiple component carriers, multiple TRPs 605 (e.g., TRP 605-a, TRP 605-b, or both), or both. In some cases, multiple component carriers may share the same analog beam with a shared beam for joint downlink and uplink TCI states. In some cases, UE 615 may receive indication of the shared beam from the component carriers (e.g., CC1). The shared beam 415 may be shared for one or more downlink channels and one or more uplink channels across multiple component carriers and TRPs 605.

[0130] At locations 640 and 645, UE 615 and TRP 605-a, UE 615 and TRP 605-b, or both, may communicate using a shared beam for joint downlink and uplink TCI states. For example, UE 615 may receive downlink transmissions from TRP 605-a using one or more downlink resources indicated in the scheduling information at 620, and may transmit uplink transmissions to TRP 605-a using one or more uplink resources indicated in the scheduling information at 620. Similarly, UE 615 may receive downlink transmissions from TRP 605-b using one or more downlink resources indicated in the scheduling information at 620, and may transmit uplink transmissions to TRP 605-b using one or more uplink resources indicated in the scheduling information at 620.

[0131] Figure 7 A block diagram of an apparatus supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown. Block diagram 700 may include apparatus 700, which may be an example of various aspects of UE 115 as described herein. Apparatus 705 may include receiver 710, transmitter 715, and communication manager 720. Apparatus 705 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0132] Receiver 710 may provide means for receiving information, such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to cross-component carrier scheduling techniques for joint downlink and uplink TCI states). The information may be transferred to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0133] Transmitter 715 may provide means for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to cross-component carrier scheduling techniques for joint downlink and uplink TCI states). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver assembly. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0134] The communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or various components thereof, may be examples of apparatuses for performing various aspects of the techniques described herein for joint downlink and uplink TCI states for cross-component carrier scheduling. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0135] In some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). This hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to serve as or otherwise support means for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0136] Additionally or alternatively, in some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented by code executed by a processor (e.g., as communication management software or firmware). If implemented by code executed by a processor, the functionality of the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be performed by a general-purpose processor, DSP, central processing unit (CPU), ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., means configured or otherwise supported for performing the functions described in this disclosure).

[0137] In some examples, the communication manager 720 may be configured to use or otherwise cooperate with the receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 720 may receive information from the receiver 710, send information to the transmitter 715, or be integrated with the receiver 710, transmitter 715, or both to receive information, transmit information, or perform various other operations described herein.

[0138] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. For example, the communication manager 720 may be configured or otherwise support means for receiving control signaling including scheduling information based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. The communication manager 720 may be configured or otherwise support means for communicating with a base station based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0139] Additionally or alternatively, according to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. For example, the communication manager 720 may be configured or otherwise support means for receiving control signaling including scheduling information for one or more downlink resources and one or more uplink resources associated with a common beam across a set comprising multiple TRPs. The communication manager 720 may be configured or otherwise support means for communicating with one or more TRPs in the set comprising multiple TRPs across a set comprising multiple component carriers based on the common beam, wherein joint downlink and uplink TCI states are associated with communication with the one or more TRPs.

[0140] By including or configuring a communication manager 720 according to an example as described herein, device 705 (e.g., a processor that controls or otherwise couples to receiver 710, transmitter 715, communication manager 720, or a combination thereof) can support techniques for receiving control signaling at the UE that indicates scheduling information for communicating across multiple component carriers, multiple TRPs, or both using a shared beam with combined downlink and uplink TCI states, which can reduce processing power and provide more efficient utilization of communication resources.

[0141] Figure 8 A block diagram of an apparatus supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown. Block diagram 800 may include apparatus 805, which may be an example of apparatus 705 as described herein, or aspects of UE 115, UE 215, UE 315, UE 515, or UE 615. Apparatus 805 may include receiver 810, transmitter 815, and communication manager 820. Apparatus 805 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0142] Receiver 810 may provide means for receiving information, such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to cross-component carrier scheduling techniques for joint downlink and uplink TCI states). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0143] Transmitter 815 may provide means for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to cross-component carrier scheduling techniques for joint downlink and uplink TCI states). In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver assembly. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0144] Device 805 or its various components may be examples of means for performing various aspects of cross-component carrier techniques for coordinating downlink and uplink TCI states as described herein. For example, communication manager 820 may include scheduling component 825, TCI component 830, beaming component 835, or any combination thereof. Communication manager 820 may be examples of various aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using receiver 810, transmitter 815, or both, or otherwise cooperating with receiver 810, transmitter 815, or both. For example, communication manager 820 may receive information from receiver 810, send information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to receive information, transmit information, or perform various other operations described herein.

[0145] According to the examples disclosed herein, the communication manager 820 can support wireless communication at the UE. The scheduling component 825 can be configured or otherwise supported to support means for receiving control signaling including scheduling information based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. The TCI component 830 can be configured or otherwise supported to support means for communicating with a base station based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0146] Additionally or alternatively, according to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. The scheduling component 825 may be configured or otherwise supported for receiving control signaling including scheduling information for one or more downlink resources and one or more uplink resources associated with a common beam across a set comprising multiple TRPs. The beamforming component 835 may be configured or otherwise supported for communicating with one or more TRPs in the set comprising multiple TRPs across a set comprising multiple component carriers based on the common beam, wherein joint downlink and uplink TCI states are associated with communication with the one or more TRPs.

[0147] Figure 9 A block diagram of a communication manager supporting techniques for joint downlink and uplink TCI states according to various aspects of this disclosure is shown. Block diagram 900 may include a communication manager 920, which may be an example of aspects of the communication manager 720, communication manager 820, or both described herein. The communication manager 920 or its various components may be examples of means for implementing various aspects of the techniques for joint downlink and uplink TCI states as described herein. For example, the communication manager 920 may include a scheduling component 925, a TCI component 930, a beamforming component 935, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0148] According to the examples disclosed herein, the communication manager 920 can support wireless communication at the UE. The scheduling component 925 can be configured or otherwise supported for receiving control signaling including scheduling information based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. The TCI component 930 can be configured or otherwise supported for communicating with a base station based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0149] In some examples, to support the reception of control signaling, the TCI component 930 may be configured or otherwise supported for receiving indications of the combined downlink and uplink TCI states. In some examples, this indication is a field in the control signaling that includes joint downlink and uplink TCI state identifiers. In some examples, the indication includes fields from the SRI. This field may indicate a shared beam or provide a mapping to the joint downlink and uplink TCI states.

[0150] In some examples, to support communication with a base station, scheduling component 925 may be configured or otherwise supported to support means for receiving downlink transmissions from a base station using one or more downlink resources. In some examples, to support communication with a base station, scheduling component 925 may be configured or otherwise supported to support means for transmitting uplink transmissions to a base station using one or more uplink resources. In some examples, scheduling component 925 may be configured or otherwise supported to support means for scheduling downlink and uplink transmissions across the set of component carriers based on sharing the same analog beam with a common beam corresponding to the joint downlink and uplink transmission configuration indicator state.

[0151] In some examples, beamforming component 935 may be configured or otherwise supported for means of receiving indications of a shared beam for one or more downlink channels and one or more uplink channels across the set of multiple component carriers from among the component carriers.

[0152] In some examples, to support receive control signaling, the TCI component 930 may be configured or otherwise supported to support means for receiving first control signaling including a first indication of a component carrier list, which is one or more component carriers in a set comprising a plurality of component carriers. In some examples, to support receive control signaling, the TCI component 930 may be configured or otherwise supported to support means for receiving second control signaling including a second indication of a joint downlink and uplink TCI state. In some examples, the one or more component carriers in the set comprising a plurality of component carriers share the same analog beam. In some examples, the one or more component carriers in the set comprising a plurality of component carriers support joint downlink and uplink TCI states. In some examples, the one or more component carriers in the set comprising a plurality of component carriers support either a downlink TCI state or an uplink TCI state.

[0153] Additionally or alternatively, according to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. In some examples, the scheduling component 925 may be configured or otherwise supported to support means for receiving control signaling including scheduling information for one or more downlink resources and one or more uplink resources associated with a common beam across a set comprising multiple TRPs. The beamforming component 935 may be configured or otherwise supported to support means for communicating with one or more TRPs in the set comprising multiple TRPs across a set comprising multiple component carriers based on the common beam, wherein joint downlink and uplink TCI states are associated with communication with the one or more TRPs.

[0154] In some examples, to support the reception of control signaling, the TCI component 930 may be configured or otherwise supported for receiving indications of the combined downlink and uplink TCI status and one or more TRP identifiers corresponding to one or more TRPs. In some examples, to support the reception of control signaling, the scheduling component 925 may be configured or otherwise supported for scheduling communications based on the indication. In some examples, the indication is a field in the control signaling that includes the combined downlink and uplink TCI status identifiers and one or more TRP identifiers. In some examples, the indication includes a field from the SRI. This field may indicate a shared beam or provide a mapping to the combined downlink and uplink TCI status.

[0155] In some examples, to support communication with one or more TRPs, the scheduling component 925 may be configured or otherwise supported to enable means for receiving downlink transmissions using one or more downlink resources. In some examples, to support communication with one or more TRPs, the scheduling component 925 may be configured or otherwise supported to enable transmitting uplink transmissions using one or more uplink resources.

[0156] Figure 10A diagram of a system including devices supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown. System 1000 may include device 1005, which may be an example of or include components of device 705, device 805, or UE 115, UE 215, UE 315, UE 515, or UE 615 as described herein. Device 1005 may wirelessly communicate with one or more base stations 105, base station 205, UE 115, UE 215, UE 315, UE 515, or UE 615, or any combination thereof. Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be in electronic communication or otherwise coupled via one or more buses (e.g., bus 1045, operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0157] I / O controller 1010 manages the input and output signals of device 1005. I / O controller 1010 can also manage peripheral devices not integrated into device 1005. In some cases, I / O controller 1010 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, I / O controller 1010 may be implemented as part of a processor (such as processor 1040). In some cases, a user may interact with device 1005 via I / O controller 1010 or via hardware components controlled by I / O controller 1010.

[0158] In some cases, device 1005 may include a single antenna 1025. However, in other cases, device 1005 may have more than one antenna 1025, which may be capable of transmitting or receiving multiple wireless transmissions concurrently. Transceiver 1015 may communicate bidirectionally via one or more antennas 1025, wired or wireless links, as described herein. For example, transceiver 1015 may represent a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. Transceiver 1015 may also include a modem for modulating packets and providing modulated packets to one or more antennas 1025 for transmission, and for demodulating packets received from one or more antennas 1025. Transceiver 1015, or transceiver 1015 and one or more antennas 1025, may be an example of transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination thereof or components thereof as described herein.

[0159] Memory 1030 may include random access memory (RAM) and read-only memory (ROM). Memory 1030 may store computer-readable, computer-executable code 1035, including instructions that, when executed by processor 1040, cause device 1005 to perform the various functions described herein. Code 1035 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 1035 may not be directly executable by processor 1040, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1030 may, in particular, include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0160] Processor 1040 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1040 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks supporting techniques for cross-component carrier scheduling of combined downlink and uplink TCI states). For example, device 1005 or components thereof may include processor 1040 and memory 1030 coupled to processor 1040, wherein processor 1040 and memory 1030 are configured to perform the various functions described herein.

[0161] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. For example, the communication manager 1020 may be configured or otherwise support means for receiving control signaling including scheduling information based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. The communication manager 1020 may be configured or otherwise support means for communicating with a base station based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0162] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. For example, the communication manager 1020 may be configured or otherwise support means for receiving control signaling including scheduling information for one or more downlink resources and one or more uplink resources associated with a common beam across a set comprising multiple TRPs. The communication manager 1020 may be configured or otherwise support means for communicating with one or more TRPs in the set comprising multiple TRPs across a set comprising multiple component carriers based on the common beam, wherein joint downlink and uplink TCI states are associated with communication with the one or more TRPs.

[0163] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 can support techniques for scheduling communication across multiple component carriers, one or more TRPs, or both, using a shared beam for joint downlink and uplink TCI states in both the downlink and uplink directions, which can reduce latency and signaling and network overhead (e.g., related to beam indication).

[0164] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is described as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by processor 1040, memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions executable by processor 1040 to cause device 1005 to perform aspects of cross-component carrier scheduling techniques for coordinating downlink and uplink TCI states as described herein, or processor 1040 and memory 1030 may be otherwise configured to perform or support such operations.

[0165] Figure 11 A block diagram of an apparatus supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown. Block diagram 1100 may include apparatus 1105, which may be an example of aspects of base station 105, base station 205, TRP 305, or TRP 605 as described herein. Apparatus 1105 may include receiver 1110, transmitter 1115, and communication manager 1120. Apparatus 1105 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0166] Receiver 1110 may provide means for receiving information, such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to cross-component carrier scheduling techniques for joint downlink and uplink TCI states). The information may be passed to other components of device 1105. Receiver 1110 may utilize a single antenna or a collection of multiple antennas.

[0167] Transmitter 1115 may provide means for transmitting signals generated by other components of device 1105. For example, transmitter 1115 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to cross-component carrier scheduling techniques for joint downlink and uplink TCI states). In some examples, transmitter 1115 may be co-located with receiver 1110 in a transceiver assembly. Transmitter 1115 may utilize a single antenna or a collection of multiple antennas.

[0168] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or various components thereof, may be examples of apparatuses for performing various aspects of the cross-component carrier scheduling techniques for jointly managing downlink and uplink TCI states as described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0169] In some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured or otherwise supported for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0170] Additionally or alternatively, in some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented by code executed by a processor (e.g., as communication management software or firmware). If implemented by code executed by a processor, the functionality of the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., means configured or otherwise supported for performing the functions described in this disclosure).

[0171] In some examples, the communication manager 1120 may be configured to use or otherwise cooperate with the receiver 1110, transmitter 1115, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or be integrated with the receiver 1110, transmitter 1115, or both to receive information, transmit information, or perform various other operations described herein.

[0172] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at a base station. For example, the communication manager 1120 may be configured or otherwise support means for transmitting control signaling, including scheduling information, to the UE based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. The communication manager 1120 may be configured or otherwise support means for communicating with the UE based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0173] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 (e.g., a processor that controls or is otherwise coupled to receiver 1110, transmitter 1115, communication manager 1120, or a combination thereof) can support techniques for transmitting control signaling to the UE indicating scheduling information for communication across multiple component carriers, multiple TRPs, or both using a shared beam with combined downlink and uplink TCI states, which can reduce processing power and provide more efficient utilization of communication resources.

[0174] Figure 12 A block diagram of an apparatus supporting cross-component carrier scheduling for joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown. Block diagram 1200 may include apparatus 1205, which may be an example of apparatus 1105 as described herein, or aspects of base station 105, base station 205, TRP 305, or TRP 605. Apparatus 1205 may include receiver 1210, transmitter 1215, and communication manager 1220. Apparatus 1205 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0175] Receiver 1210 may provide means for receiving information, such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to cross-component carrier scheduling techniques for joint downlink and uplink TCI states). The information may be passed to other components of device 1205. Receiver 1210 may utilize a single antenna or a collection of multiple antennas.

[0176] Transmitter 1215 may provide means for transmitting signals generated by other components of device 1205. For example, transmitter 1215 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to cross-component carrier scheduling techniques for joint downlink and uplink TCI states). In some examples, transmitter 1215 may be co-located with receiver 1210 in a transceiver assembly. Transmitter 1215 may utilize a single antenna or a collection of multiple antennas.

[0177] Device 1205 or its various components may be examples of means for performing various aspects of cross-component carrier techniques for coordinating downlink and uplink TCI states as described herein. For example, communication manager 1220 may include scheduling component 1225, TCI component 1230, or any combination thereof. Communication manager 1220 may be examples of various aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using receiver 1210, transmitter 1215, or both, or otherwise in cooperation with receiver 1210, transmitter 1215, or both. For example, communication manager 1220 may receive information from receiver 1210, send information to transmitter 1215, or be integrated with receiver 1210, transmitter 1215, or both to receive information, transmit information, or perform various other operations described herein.

[0178] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at a base station. The scheduling component 1225 may be configured or otherwise support means for transmitting control signaling, including scheduling information, to the UE based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. The TCI component 1230 may be configured or otherwise support means for communicating with the UE based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0179] Figure 13A block diagram of a communication manager supporting techniques for joint downlink and uplink TCI states according to various aspects of this disclosure is shown. Block diagram 1300 may include a communication manager 1320, which may be an example of aspects of the communication manager 1120, communication manager 1220, or both described herein. The communication manager 1320 or its various components may be examples of means for implementing various aspects of the techniques for joint downlink and uplink TCI states as described herein. For example, the communication manager 1320 may include a scheduling component 1325, a TCI component 1330, a beamforming component 1335, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0180] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at a base station. The scheduling component 1325 may be configured or otherwise supported to provide means for transmitting control signaling, including scheduling information, to the UE based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. The TCI component 1330 may be configured or otherwise supported to provide means for communicating with the UE based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0181] In some examples, to support the transmission of control signaling, the TCI component 1330 may be configured or otherwise supported for means of transmitting indications of the combined downlink and uplink TCI states. In some examples, this indication is a field in the control signaling that includes joint downlink and uplink TCI state identifiers. In some examples, the indication includes fields from the SRI. This field may indicate a shared beam or provide a mapping to the joint downlink and uplink TCI states.

[0182] In some examples, to support communication with the UE, the scheduling component 1325 may be configured or otherwise supported to provide means for transmitting downlink transmissions to the UE using one or more downlink resources. In some examples, to support communication with the UE, the scheduling component 1325 may be configured or otherwise supported to provide means for receiving uplink transmissions from the UE using one or more uplink resources.

[0183] In some examples, scheduling component 1325 may be configured or otherwise supported for means of scheduling downlink and uplink transmissions across the set of multiple component carriers based on the shared analog beam of the set of multiple component carriers and the shared beam corresponding to the joint downlink and uplink transmission configuration indicator state.

[0184] In some examples, beam assembly 1335 may be configured or otherwise support means for transmitting indications of a shared beam for one or more downlink channels and one or more uplink channels across the set of multiple component carriers from the component carriers of the set of multiple component carriers.

[0185] In some examples, to support the transmission of control signaling, the TCI component 1330 may be configured or otherwise support means for transmitting first control signaling including a first indication of a component carrier list, the component carrier list containing one or more component carriers from the set comprising multiple component carriers. In some examples, to support the transmission of control signaling, the TCI component 1330 may be configured or otherwise support means for transmitting second control signaling including a second indication of a joint downlink and uplink TCI state. In some examples, the one or more component carriers from the set comprising multiple component carriers share the same analog beam. In some examples, the one or more component carriers from the set comprising multiple component carriers support joint downlink and uplink TCI states. In some examples, the one or more component carriers from the set comprising multiple component carriers support either a downlink TCI state or an uplink TCI state.

[0186] Figure 14A diagram of a system including devices supporting cross-component carrier scheduling for joint downlink and uplink TCI states is shown according to various aspects of this disclosure. System 1400 may include device 1405, which may be an example of device 1105, device 1205, or base station 105, base station 205, TRP 305, or TRP 605, or include these components as described herein. Device 1405 may wirelessly communicate with one or more base stations 105, base station 205, UE 115, UE 215, UE 315, UE 515, or UE 615, or any combination thereof. Device 1405 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communication manager 1420, a network communication manager 1410, a transceiver 1415, an antenna 1425, a memory 1430, code 1435, a processor 1440, and an inter-site communication manager 1445. These components may be in electronic communication or otherwise coupled via one or more buses (e.g., bus 1450) (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0187] The network communication manager 1410 can manage communication with the core network 130 (e.g., via one or more wired backhaul links). For example, the network communication manager 1410 can manage the delivery of data communications by client devices (such as one or more UE 115, UE 215, UE 315, UE 515, or UE 615).

[0188] In some cases, device 1405 may include a single antenna 1425. However, in other cases, device 1405 may have more than one antenna 1425, which may be capable of transmitting or receiving multiple wireless transmissions concurrently. Transceiver 1415 may communicate bidirectionally via one or more antennas 1425, wired or wireless links, as described herein. For example, transceiver 1415 may represent a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. Transceiver 1415 may also include a modem for modulating packets and providing modulated packets to one or more antennas 1425 for transmission, and for demodulating packets received from one or more antennas 1425. Transceiver 1415, or transceiver 1415 and one or more antennas 1425, may be an example of transmitter 1115, transmitter 1215, receiver 1110, receiver 1210, or any combination thereof or components thereof as described herein.

[0189] Memory 1430 may include RAM and ROM. Memory 1430 may store computer-readable, computer-executable code 1435, including instructions that, when executed by processor 1440, cause device 1405 to perform the various functions described herein. Code 1435 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 1435 may not be directly executable by processor 1440, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1430 may, in particular, include a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0190] Processor 1440 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1440 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1440. Processor 1440 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1430) to cause device 1405 to perform various functions (e.g., functions or tasks supporting techniques for cross-component carrier scheduling of combined downlink and uplink TCI states). For example, device 1405 or components thereof may include processor 1440 and memory 1430 coupled to processor 1440, wherein processor 1440 and memory 1430 are configured to perform the various functions described herein.

[0191] Inter-site communication manager 1445 manages communication with other base stations 105 or 205, and may include a controller or scheduler for cooperating with other base stations 105 or 205 to control communication with UE 115, UE 215, UE 315, UE 515, or UE 615. For example, inter-site communication manager 1445 may coordinate the scheduling of transmissions to UE 115, UE 215, UE 315, UE 515, or UE 615 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, inter-site communication manager 1445 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0192] According to the examples disclosed herein, the communication manager 1420 may support wireless communication at a base station. For example, the communication manager 1420 may be configured or otherwise support means for transmitting control signaling, including scheduling information, to the UE based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. The communication manager 1420 may be configured or otherwise support means for communicating with the UE based on a shared beam corresponding to the joint downlink and uplink TCI state.

[0193] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 can support techniques for scheduling communication across multiple component carriers, one or more TRPs, or both using a shared beam for joint downlink and uplink TCI states in both the downlink and uplink directions, which can reduce latency and signaling and network overhead (e.g., related to beam indication).

[0194] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the transceiver 1415, one or more antennas 1425, or any combination thereof. Although the communication manager 1420 is described as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the processor 1440, memory 1430, code 1435, or any combination thereof. For example, code 1435 may include instructions executable by the processor 1440 to cause the device 1405 to perform aspects of the cross-component carrier scheduling techniques for coordinating downlink and uplink TCI states as described herein, or the processor 1440 and memory 1430 may be otherwise configured to perform or support such operations.

[0195] Figure 15 A flowchart illustrating a method for cross-component carrier scheduling supporting joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be implemented by, as referred to... Figures 1 to 10The described UE 115, UE 215, UE 315, UE 515, or UE 615 shall perform this function. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0196] At 1505, the method may include receiving control signaling including scheduling information based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. The operation of 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to... Figure 9 The described scheduling component 925 is used for execution.

[0197] At 1510, the method may include communicating with the base station based on a shared beam corresponding to the joint downlink and uplink TCI states. Operation of 1510 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1510 may be provided as referenced... Figure 9 The TCI component 930 described is used for execution.

[0198] Figure 16 A flowchart illustrating a method for cross-component carrier scheduling supporting joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be implemented by, as referred to... Figures 1 to 10 The described UE 115, UE 215, UE 315, UE 515, or UE 615 shall perform this function. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0199] At 1605, the method may include receiving indications of the combined downlink and uplink TCI states. The operation of 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to... Figure 9 The TCI component 930 described is used for execution.

[0200] At 1610, the method may include receiving control signaling including scheduling information based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. Operation of 1610 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1610 may be provided by reference to [reference needed]. Figure 9 The described scheduling component 925 is used for execution.

[0201] At 1615, the method may include communicating with the base station based on a shared beam corresponding to the joint downlink and uplink TCI states. The operation of 1615 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1615 may be provided as referenced... Figure 9 The TCI component 930 described is used for execution.

[0202] Figure 17 A flowchart illustrating a method for cross-component carrier scheduling supporting joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be implemented by, as referred to... Figures 1 to 10 The described UE 115, UE 215, UE 315, UE 515, or UE 615 shall perform this function. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0203] At 1705, the method may include receiving control signaling including scheduling information for one or more downlink resources and one or more uplink resources associated with a common beam spanning a set comprising multiple TRPs. Operation of 1705 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1705 may be provided as referenced... Figure 9 The described scheduling component 925 is used for execution.

[0204] At 1710, the method may include communicating with one or more TRPs in a set comprising multiple component carriers across a shared beam, wherein joint downlink and uplink TCI states are associated with communication with the one or more TRPs. Operation of 1710 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1710 may be provided as referenced... Figure 9The beamforming component 935 described is used to perform this.

[0205] Figure 18 A flowchart illustrating a method for cross-component carrier scheduling supporting joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown. Operation of method 1800 can be implemented by a UE or its components as described herein. For example, operation of method 1800 can be implemented by, as referred to... Figures 1 to 10 The described UE 115, UE 215, UE 315, UE 515, or UE 615 shall perform this function. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0206] At 1805, the method may include receiving indications of the combined downlink and uplink TCI states and one or more TRP identifiers corresponding to one or more TRPs in a set comprising a plurality of TRPs. The operation of 1805 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1805 may be provided by reference to [reference needed]. Figure 9 The TCI component 930 described is used for execution.

[0207] At 1810, the method may include receiving control signaling including scheduling information for one or more downlink resources and one or more uplink resources associated with a common beam spanning a set comprising multiple TRPs. Operation of 1810 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1810 may be provided as referenced... Figure 9 The described scheduling component 925 is used for execution.

[0208] At 1815, the method may include scheduling communication based on the instruction. The operation of 1815 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1815 may be determined by reference to... Figure 9 The described scheduling component 925 is used for execution.

[0209] At 1820, the method may include communicating with one or more TRPs in the set of multiple TRPs across a shared beam, wherein joint downlink and uplink TCI states are associated with the communication with the one or more TRPs. Operation of 1820 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1820 may be provided as referenced. Figure 9 The beamforming component 935 described is used to perform this.

[0210] Figure 19A flowchart illustrating a method for cross-component carrier scheduling supporting joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown. Operation of method 1900 can be implemented by a base station or its components as described herein. For example, operation of method 1900 can be implemented by, as referred to... Figures 1 to 6 and Figures 11 to 14 The described base stations 105, 205, TRP 305, and TRP 605 perform this function. In some examples, the base station can execute a set of instructions to control the functional elements of the base station to perform the described function. Alternatively, the base station may use dedicated hardware to perform aspects of the described function.

[0211] At 1905, the method may include transmitting control signaling to the UE, based on a joint downlink and uplink TCI state, the scheduling information being used across one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. The operation of 1905 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1905 may be provided by reference to [reference needed]. Figure 13 The described scheduling component 1325 is used for execution.

[0212] At 1910, the method may include communicating with the UE based on a shared beam corresponding to the joint downlink and uplink TCI states. Operation at 1910 may be performed according to the examples disclosed herein. In some examples, aspects of operation at 1910 may be provided as referenced... Figure 13 The TCI component 1330 described is used for execution.

[0213] Figure 20 A flowchart illustrating a method for cross-component carrier scheduling supporting joint downlink and uplink TCI states, according to various aspects of this disclosure, is shown. Operation of method 2000 can be implemented by a base station or its components as described herein. For example, operation of method 2000 can be implemented by, as referred to... Figures 1 to 6 and Figures 11 to 14 The described base stations 105, 205, TRP 305, and TRP 605 perform this function. In some examples, the base station can execute a set of instructions to control the functional elements of the base station to perform the described function. Alternatively, the base station may use dedicated hardware to perform aspects of the described function.

[0214] At 2005, the method may include transmitting control signaling including scheduling information to the UE based on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources comprising a set of multiple component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers in the set of multiple component carriers based on a list of component carriers. Operation of 2005 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 2005 may be provided by reference to [reference needed]. Figure 13 The described scheduling component 1325 is used for execution.

[0215] At 2010, the method may include communicating with the UE based on a shared beam corresponding to the joint downlink and uplink TCI states. Operation of 2010 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 2010 may be provided as referenced. Figure 13 The TCI component 1330 described is used for execution.

[0216] At 2015, the method may include transmitting downlink transmissions to the UE using one or more downlink resources. Operation of 2015 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 2015 may be provided as referenced. Figure 13 The described scheduling component 1325 is used for execution.

[0217] At 2020, the method may include receiving uplink transmissions from the UE using one or more uplink resources. Operation of 2020 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 2020 may be provided as referenced. Figure 13 The described scheduling component 1325 is used for execution.

[0218] The following provides an overview of the various aspects of this disclosure:

[0219] Aspect 1: A method for wireless communication at a UE, comprising: receiving control signaling including scheduling information for one or more downlink resources and one or more uplink resources across a plurality of component carriers, at least in part based on a joint downlink and uplink TCI state, wherein the joint downlink and uplink TCI state is associated with one or more component carriers of the plurality of component carriers at least in part based on a list of component carriers; and communicating with a base station at least in part based on a shared beam corresponding to the joint downlink and uplink transmission configuration indicator state.

[0220] Aspect 2: The method of aspect 1, wherein receiving control signaling includes: receiving an indication of the status of the combined downlink and uplink transmission configuration indicator.

[0221] Aspect 3: The method of aspect 2, wherein the indication is a field in the control signaling that includes a combined downlink and uplink transmission configuration indicator status identifier.

[0222] Aspect 4: The method of aspect 2, wherein the indication includes fields in the scheduling request indicator.

[0223] Aspect 5: The method of any of Aspects 1 to 4, wherein communicating with the base station includes: receiving downlink transmissions from the base station using one or more downlink resources, and transmitting uplink transmissions to the base station using one or more uplink resources.

[0224] Aspect 6: The method of aspect 5 further includes: scheduling downlink and uplink transmissions across the multiple component carriers based at least in part on the fact that the multiple component carriers share the same analog beam with a common beam corresponding to the joint downlink and uplink transmission configuration indicator state.

[0225] Aspect 7: The method of any of Aspects 1 to 6 further includes: receiving from a component carrier of the plurality of component carriers an indication of a common beam for one or more downlink channels and one or more uplink channels across the plurality of component carriers.

[0226] Aspect 8: A method of any of Aspects 1 to 7, wherein receiving control signaling includes: receiving first control signaling including a first indication of a component carrier list, the component carrier list including one or more component carriers among the plurality of component carriers; and receiving second control signaling including a second indication of a joint downlink and uplink transmission configuration indicator status.

[0227] Aspect 9: The method of aspect 8, wherein one or more component carriers of the plurality of component carriers share the same analog beam.

[0228] Aspect 10: The method of any of Aspects 8 to 9, wherein one or more of the plurality of component carriers support joint downlink and uplink transmission configuration indicator states.

[0229] Aspect 11: The method of any of Aspects 8 to 9, wherein one or more of the plurality of component carriers support a downlink transmission configuration indicator state or an uplink transmission configuration indicator state.

[0230] Aspect 12: A method for wireless communication at a UE, comprising: receiving control signaling including scheduling information for association with one or more downlink resources and one or more uplink resources across a common beam of multiple transmit / receive points; communicating with one or more of the multiple transmit / receive points across multiple component carriers at least in part based on the common beam, wherein a combined downlink and uplink transmission configuration indicator state is associated with the communication with the one or more transmit / receive points.

[0231] Aspect 13: The method of aspect 12, wherein receiving control signaling further includes: receiving an indication of the combined downlink and uplink transmission configuration indicator status and one or more transmission receiving point identifiers corresponding to one or more transmission receiving points; and scheduling communications based at least in part on the indication.

[0232] Aspect 14: The method of aspect 13, wherein the indication is a field in the control signaling that includes a combined downlink and uplink transmission configuration indicator status identifier and one or more transmission receiving point identifiers.

[0233] Aspect 15: The method of aspect 13, wherein the indication includes fields in the scheduling request indicator.

[0234] Aspect 16: The method of any of Aspects 12 to 15, wherein communicating with one or more transmission receiving points includes: receiving downlink transmissions using one or more downlink resources; and transmitting uplink transmissions using one or more uplink resources.

[0235] Aspect 17: A method for wireless communication at a base station, comprising: transmitting control signaling including scheduling information to a UE based at least in part on a joint downlink and uplink TCI state for one or more downlink resources and one or more uplink resources across a plurality of component carriers, wherein the joint downlink and uplink TCI state is associated with one or more component carriers of the plurality of component carriers based at least in part on a list of component carriers; and communicating with the UE based at least in part on a shared beam corresponding to the joint downlink and uplink transmission configuration indicator state.

[0236] Aspect 18: The method of aspect 17, wherein the transmission control signaling includes: transmitting an indication of the combined downlink and uplink transmission configuration indicator status.

[0237] Aspect 19: The method of aspect 18, wherein the indication is a field in the control signaling that includes a combined downlink and uplink transmission configuration indicator status identifier.

[0238] Aspect 20: The method of aspect 18, wherein the indication includes fields in the scheduling request indicator.

[0239] Aspect 21: The method of any of Aspects 17 to 20, wherein communicating with the UE includes: transmitting downlink transmissions to the UE using one or more downlink resources; and receiving uplink transmissions using one or more uplink resources.

[0240] Aspect 22: The method of aspect 21 further includes: scheduling downlink and uplink transmissions across the multiple component carriers based at least in part on the fact that the multiple component carriers share the same analog beam with a common beam corresponding to the joint downlink and uplink transmission configuration indicator state.

[0241] Aspect 23: The method of any of Aspects 17 to 22 further includes: transmitting from the component carriers of the plurality of component carriers an indication of a common beam for one or more downlink channels and one or more uplink channels across the plurality of component carriers.

[0242] Aspect 24: The method of any of Aspects 17 to 23, wherein transmitting control signaling includes: transmitting first control signaling including a first indication of a component carrier list, the component carrier list including one or more component carriers among the plurality of component carriers; and transmitting second control signaling including a second indication of a combined downlink and uplink transmission configuration indicator status.

[0243] Aspect 25: The method of aspect 24, wherein one or more component carriers of the plurality of component carriers share the same analog beam.

[0244] Aspect 26: The method of any of Aspects 24 to 25, wherein one or more of the plurality of component carriers support joint downlink and uplink transmission configuration indicator states.

[0245] Aspect 27: The method of any of Aspects 24 to 25, wherein one or more of the plurality of component carriers support a downlink transmission configuration indicator state or an uplink transmission configuration indicator state.

[0246] Aspect 28: An apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in any of Aspects 1 to 11.

[0247] Aspect 29: An apparatus for wireless communication at a UE, comprising at least one means for performing the method of any one of Aspects 1 to 11.

[0248] Aspect 30: A non-transient computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform methods as described in any of Aspects 1 to 11.

[0249] Aspect 31: An apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in any of Aspects 12 to 16.

[0250] Aspect 32: An apparatus for wireless communication at a UE, comprising at least one means for performing the method of any one of aspects 12 to 16.

[0251] Aspect 33: A non-transient computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform methods as described in any of Aspects 12 to 16.

[0252] Aspect 34: An apparatus for wireless communication at a base station, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the methods of any of Aspects 17 to 27.

[0253] Aspect 35: An apparatus for wireless communication at a base station, comprising at least one means for performing the method of any one of aspects 17 to 27.

[0254] Aspect 36: A non-transient computer-readable medium storing code for wireless communication at a base station, the code including instructions executable by a processor to perform methods as described in any of Aspects 17 to 27.

[0255] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0256] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein can also be applied to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0257] The information and signals described herein can be represented using any of a wide variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0258] The various illustrative boxes and components described herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternatives, the processor may be any processor, controller, microcontroller, or state machine. The 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 working in conjunction with a DSP core, or any other such configuration).

[0259] 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 or transmitted as one or more instructions or code on a computer-readable medium. Other examples and implementations fall within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed such that different parts of the function are implemented at different physical locations.

[0260] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible to a general-purpose or special-purpose computer. By way of example and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Similarly, any connection is also legitimately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then such coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable media. As used in this article, disk and disc include CDs, laser discs, optical discs, DVDs, floppy disks, and Blu-ray discs, where disks often magnetically reproduce data while discs optically reproduce data using lasers. Combinations of these media are also included within the scope of computer-readable media.

[0261] As used herein (including in the claims), the word "or" in an enumeration of items (e.g., an enumeration of items accompanied by phrases such as "at least one of" or "one or more of") indicates an inclusive enumeration, such that an enumeration of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Similarly, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0262] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, components of the same type may be distinguished by a dash following the reference numeral and a second reference numeral used to differentiate between similar components. If only the first reference numeral is used in the description, the description may apply to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0263] The descriptions herein, illustrated with reference to the accompanying drawings, depict exemplary configurations and are not representative of all examples that may be implemented or fall within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and does not imply "superior" or "outperforming" other examples. This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0264] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the universal principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for conducting wireless communication at a user equipment (UE), comprising: Receive a first control signaling indicating a component carrier list, the component carrier list including one or more component carriers in a set of component carriers; The second control signaling, including scheduling information, is received at least in part based on the joint downlink and uplink transmission configuration indicator state, the scheduling information being used for one or more downlink resources and one or more uplink resources across the component carrier set, wherein the joint downlink and uplink transmission configuration indicator state is associated with the one or more component carriers in the component carrier set of the component carrier list; as well as Communication with network entities is based at least in part on a shared beam corresponding to the state of the joint downlink and uplink transmission configuration indicator.

2. The method of claim 1, wherein receiving the second control signaling comprises: Receive an indication of the status of the combined downlink and uplink transmission configuration indicator.

3. The method of claim 2, wherein the indication is a field in the second control signaling that includes a combined downlink and uplink transmission configuration indicator status identifier.

4. The method of claim 2, wherein the indication includes a field in the scheduling request indicator.

5. The method of claim 1, wherein communicating with the network entity comprises: Receive downlink transmissions from the network entity using one or more downlink resources; as well as Uplink transmissions are delivered to the network entity using one or more uplink resources.

6. The method of claim 5, further comprising: The downlink and uplink transmissions are scheduled across the component carrier set, at least in part, based on the fact that the component carrier set shares the same analog beam with the shared beam corresponding to the joint downlink and uplink transmission configuration indicator state.

7. The method of claim 1, further comprising: Instructions for the shared beam are received from the component carriers in the component carrier set for one or more downlink channels and one or more uplink channels across the component carrier set.

8. The method of claim 1, wherein the second control signaling includes an indication of the status of the combined downlink and uplink transmission configuration indicator.

9. The method of claim 8, wherein the one or more component carriers in the component carrier set share the same analog beam.

10. The method of claim 8, wherein one or more component carriers in the component carrier set support the joint downlink and uplink transmission configuration indicator state.

11. The method of claim 8, wherein one or more component carriers in the component carrier set support a downlink transmission configuration indicator state or an uplink transmission configuration indicator state.

12. A method for conducting wireless communication at a user equipment (UE), comprising: Receive a first control signaling indicating a component carrier list, the component carrier list including one or more component carriers in a set of component carriers; Receive a second control signaling message including scheduling information for associating one or more downlink resources and one or more uplink resources with a shared beam across multiple transmit and receive points; as well as Communication with one or more of the plurality of transmit / receive points across the component carrier set is based at least in part on the shared beam and the component carrier list, wherein the combined downlink and uplink transmission configuration indicator status is associated with communication with the one or more transmit / receive points.

13. The method of claim 12, wherein receiving the second control signaling further comprises: Receive indications of the combined downlink and uplink transmission configuration indicator status and one or more transmission receive point identifiers corresponding to the one or more transmission receive points; as well as The communication is scheduled at least in part based on the instructions.

14. The method of claim 13, wherein the indication is a field in the second control signaling that includes a combined downlink and uplink transmission configuration indicator status identifier and the one or more transmission receiving point identifiers.

15. The method of claim 13, wherein the indication includes a field in the scheduling request indicator.

16. The method of claim 12, wherein communicating with the one or more transmit / receive points comprises: Receive downlink transmissions using the one or more downlink resources; as well as Uplink transmissions are delivered using one or more uplink resources.

17. A method for conducting wireless communication at a network entity, comprising: Transmit a first control signaling indicating a component carrier list, the component carrier list including one or more component carriers from a set of component carriers; A second control signaling, including scheduling information, is transmitted based at least in part on a joint downlink and uplink transmission configuration indicator state for one or more downlink resources and one or more uplink resources across the component carrier set, wherein the joint downlink and uplink transmission configuration indicator state is associated with the one or more component carriers in the component carrier set of the component carrier list; as well as Communication with the user equipment (UE) is based at least in part on a shared beam corresponding to the state of the joint downlink and uplink transmission configuration indicator.

18. The method of claim 17, wherein transmitting the second control signaling comprises: Transmits an indication of the status of the combined downlink and uplink transmission configuration indicator.

19. The method of claim 18, wherein the indication is a field in the second control signaling that includes a combined downlink and uplink transmission configuration indicator status identifier.

20. The method of claim 18, wherein the indication includes a field in the scheduling request indicator.

21. The method of claim 17, wherein communicating with the UE comprises: Use one or more downlink resources to transmit downlink transmissions to the UE; as well as Receive uplink transmissions from the UE using one or more uplink resources.

22. The method of claim 21, further comprising: The downlink and uplink transmissions are scheduled across the component carrier set, at least in part, based on the fact that the component carrier set shares the same analog beam with the shared beam corresponding to the joint downlink and uplink transmission configuration indicator state.

23. The method of claim 17, further comprising: Indications for the shared beam are transmitted from the component carriers in the component carrier set for one or more downlink channels and one or more uplink channels across the component carrier set.

24. The method of claim 17, wherein the second control signaling includes an indication of the status of the combined downlink and uplink transport configuration indicator.

25. The method of claim 24, wherein the one or more component carriers in the component carrier set share the same analog beam.

26. The method of claim 24, wherein one or more component carriers in the component carrier set support the joint downlink and uplink transmission configuration indicator state.

27. The method of claim 24, wherein one or more component carriers in the component carrier set support a downlink transmission configuration indicator state or an uplink transmission configuration indicator state.

28. An apparatus for wireless communication at a user equipment (UE), comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor to cause the device to perform the following operations: Receive a first control signaling indicating a component carrier list, the component carrier list including one or more component carriers in a set of component carriers; The second control signaling, including scheduling information, is received at least in part based on the joint downlink and uplink transmission configuration indicator state, the scheduling information being used for one or more downlink resources and one or more uplink resources across the component carrier set, wherein the joint downlink and uplink transmission configuration indicator state is associated with the one or more component carriers in the component carrier set of the component carrier list; as well as Communication with network entities is based at least in part on a shared beam corresponding to the state of the joint downlink and uplink transmission configuration indicator.

29. An apparatus for wireless communication at a user equipment (UE), comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor to cause the device to perform the method as described in any one of claims 2-11.

30. An apparatus for conducting wireless communication at a user equipment (UE), comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor to cause the device to perform the following operations: Receive a first control signaling indicating a component carrier list, the component carrier list including one or more component carriers in a set of component carriers; Receive a second control signaling message including scheduling information for associating one or more downlink resources and one or more uplink resources with a shared beam across multiple transmit and receive points; as well as Communication with one or more of the plurality of transmit / receive points across the component carrier set is based at least in part on the shared beam and the component carrier list, wherein the combined downlink and uplink transmission configuration indicator status is associated with communication with the one or more transmit / receive points.

31. An apparatus for conducting wireless communication at a user equipment (UE), comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor to cause the device to perform the method as described in any one of claims 13-16.

32. An apparatus for wireless communication at a network entity, comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor to cause the device to perform the following operations: Transmit a first control signaling indicating a component carrier list, the component carrier list including one or more component carriers from a set of component carriers; A second control signaling, including scheduling information, is transmitted based at least in part on a joint downlink and uplink transmission configuration indicator state for one or more downlink resources and one or more uplink resources across the component carrier set, wherein the joint downlink and uplink transmission configuration indicator state is associated with the one or more component carriers in the component carrier set of the component carrier list; as well as Communication with the user equipment (UE) is based at least in part on a shared beam corresponding to the state of the joint downlink and uplink transmission configuration indicator.

33. An apparatus for wireless communication at a network entity, comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor to cause the device to perform the method as described in any one of claims 18-27.

Images