Techniques for configuring timing advance groups for component carriers

By receiving configuration information, optimizing the configuration of the CORESET pool index and TAG set of component carriers, the problem of difficult management of multiple TAG configurations in the prior art is solved, and the optimization of resource configuration and communication efficiency are achieved.

CN119072982APending Publication Date: 2024-12-03QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280095212.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-29
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

When existing wireless communication systems configure timing advance groups for component carriers, it is difficult to effectively manage the configuration of multiple TAGs, resulting in waste of resources and communication errors.

Method used

By receiving configuration information, a plurality of CORESET pool indexes and TAG sets are indicated for the first component carrier and the second component carrier, and the second set is configured in part based on the first set of multiple TAGs, the configuration of the TAG is optimized to reduce resource consumption and Improve communication efficiency.

Benefits of technology

It realizes more efficient resource allocation, reduces resource consumption and communication errors, and improves communication efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072982A_ABST
    Figure CN119072982A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive configuration information indicating a first configuration of a plurality of control resource set (CORESET) pool indices for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of timing advance groups (TAGs) for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs. The UE may transmit one or more communications via the first component carrier and the second component carrier based at least in part on the first set of multiple TAGs and the second set of one or more TAGs. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for techniques for configuring timing advance groups for component carriers.

[0002] Related technologies

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0004] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0005] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0006] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include: receiving configuration information indicating: a first configuration of a plurality of control resource set (CORESET) pool indexes for a first component carrier and for a second component carrier, and a first set of a plurality of timing advance groups (TAGs) for the first component carrier and a second configuration of a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured at least in part based on the first set of the plurality of TAGs. The method may include: sending one or more communications via the first component carrier and the second component carrier based at least in part on the first set of the plurality of TAGs and the second set of the one or more TAGs.

[0007] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include sending an indication of a capability to communicate using multiple timing advances (TAs) for a single component carrier. The method may include receiving configuration information indicating: a plurality of CORESET pool indexes for communication within the single component carrier, and one or more TAGs for the single component carrier based at least in part on the capability.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending configuration information indicating a first configuration of a plurality of CORESET pool indexes for a first component carrier and for a second component carrier, and a first set of a plurality of TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of the plurality of TAGs. The method may include receiving one or more communications via the first component carrier and the second component carrier based at least in part on the first set of the plurality of TAGs and the second set of the one or more TAGs.

[0009] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving an indication of a capability to communicate using multiple TAs for a single component carrier. The method may include sending configuration information indicating: a plurality of CORESET pool indexes for communication within the single component carrier, and one or more TAGs for the single component carrier based at least in part on the capability.

[0010] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: receive a configuration information indication. The one or more processors may be configured to: send one or more communications via a first component carrier and a second component carrier based at least in part on a first set of multiple TAGs and a second set of one or more TAGs.

[0011] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: send an indication of a capability to communicate using multiple TAs for a single component carrier. The one or more processors may be configured to: receive configuration information indicating: multiple CORESET pool indexes for communication within a single component carrier, and one or more TAGs for the single component carrier based at least in part on the capability.

[0012] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: send a configuration information indication. The one or more processors may be configured to: receive one or more communications via a first component carrier and a second component carrier based at least in part on a first set of multiple TAGs and a second set of one or more TAGs.

[0013] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: receive an indication of a capability to communicate using multiple TAs for a single component carrier. The one or more processors may be configured to: send configuration information indicating: multiple CORESET pool indexes for communication within the single component carrier, and one or more TAGs for the single component carrier based at least in part on the capability.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a configuration information indication. The instruction set, when executed by one or more processors of the UE, may cause the UE to send one or more communications via a first component carrier and a second component carrier based at least in part on a first set of multiple TAGs and a second set of one or more TAGs.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication when executed by one or more processors of a UE. The instruction set, when executed by one or more processors of the one or more instructions when executed by one or more processors of the one or more instructions, may cause the one or more instructions, when executed by the one or more processors of the UE, to send an indication of the ability to communicate using multiple TAs for a single component carrier. The instruction set, when executed by one or more processors of the one or more instructions when executed by one or more processors of the one or more instructions, may cause the one or more instructions, when executed by the one or more processors of the UE, to receive configuration information indicating: multiple CORESET pool indexes for communication within a single component carrier, and one or more TAGs for a single component carrier based at least in part on the capability.

[0016] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a configuration information indication. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive one or more communications via a first component carrier and a second component carrier based at least in part on a first set of multiple TAGs and a second set of one or more TAGs.

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive an indication of the ability to communicate using multiple TAs for a single component carrier. The instruction set, when executed by one or more processors of the network node, may cause the network node to send configuration information indicating: multiple CORESET pool indexes for communication within a single component carrier, and one or more TAGs for the single component carrier based at least in part on the capability.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving configuration information indicating: a first configuration of a plurality of CORESET pool indexes for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of the plurality of TAGs. The apparatus may include means for sending one or more communications via the first component carrier and the second component carrier based at least in part on the first set of the plurality of TAGs and the second set of the one or more TAGs.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending an indication of a capability to communicate using multiple TAs for a single component carrier. The apparatus may include means for receiving configuration information indicating: multiple CORESET pool indexes for communication within the single component carrier, and one or more TAGs for the single component carrier based at least in part on the capability, multiple CORESET pool indexes for communication within the single component carrier, and one or more TAGs for the single component carrier based at least in part on the capability).

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending configuration information indicating: a first configuration of a plurality of CORESET pool indexes for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of the plurality of TAGs. The apparatus may include means for receiving one or more communications via the first component carrier and the second component carrier based at least in part on the first set of the plurality of TAGs and the second set of the one or more TAGs.

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of a capability to communicate using multiple TAs for a single component carrier. The apparatus may include means for sending configuration information indicating: a plurality of CORESET pool indexes for communication within the single component carrier, and one or more TAGs for the single component carrier based at least in part on the capability.

[0022] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the drawings and description.

[0023] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0025] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0026] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0027] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0028] Figure 4 An example logical architecture of a distributed radio access network (RAN) according to the present disclosure is illustrated.

[0029] Figure 5 is a diagram illustrating an example of multiple transmit-receive point (TRP) communications according to the present disclosure.

[0030] Figure 6 is a diagram illustrating an example of transmit reception point (TRP) differentiation at a UE based at least in part on a control resource set (CORESET) pool index according to the present disclosure.

[0031] Figure 7 is a diagram illustrating an example of downlink and uplink transmission between a network node and a UE in a wireless network according to the present disclosure.

[0032] Figure 8 is a diagram illustrating an example of carrier aggregation according to the present disclosure.

[0033] Fig. 9 is a diagram illustrating an example of configuring a timing advance group (TAG) for a component carrier according to the present disclosure.

[0034] Figures 10 to 13 is a diagram illustrating an exemplary process associated with configuring a TAG for a component carrier according to the present disclosure.

[0035] Figure 14 to Figure 15 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0036] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions other than or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

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

[0038] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0039] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0040] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0041] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 can be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0042] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in FIG, BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.

[0043] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0044] The network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0045] UE 120 may be distributed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio, etc.), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0046] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0047] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0048] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using base station 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0049] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0051] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as frequencies that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that the term "millimeter wave" or the like, if used herein, can be broadly referred to as frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0052] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive configuration information indicating: a first configuration of a plurality of control resource set (CORESET) pool indexes for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of timing advance groups (TAGs) for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of the plurality of TAGs; and sending one or more communications via the first component carrier and the second component carrier based at least in part on the first set of the plurality of TAGs and the second set of one or more TAGs. As described in more detail elsewhere herein, the communication manager 140 may send an indication of a capability to communicate using a plurality of timing advances (TAs) for a single component carrier; and receive configuration information indicating: a plurality of CORESET pool indexes for communications within a single component carrier, and one or more TAGs for a single component carrier based at least in part on the capability. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0053] In some aspects, a network node (e.g., a base station 110 or a device associated with the base station 110, etc.) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send configuration information indicating: a first configuration of a plurality of CORESET pool indexes for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of the plurality of TAGs; and receiving one or more communications via the first component carrier and the second component carrier based at least in part on the first set of the plurality of TAGs and the second set of one or more TAGs. As described in more detail elsewhere herein, the communication manager 150 may receive an indication of a capability to communicate using multiple TAs for a single component carrier; and send configuration information indicating: a plurality of CORESET pool indexes for communication within a single component carrier, and one or more TAGs for the single component carrier based at least in part on the capability. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0054] In some aspects, the term "base station" (e.g., base station 110) or "network node" or "network entity" may refer to a converged base station, a decomposed base station (e.g., a combined Fig. 9110), an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station", "network node", or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station", "network node", or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station", "network node", or "network entity" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station", "network node", or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station", "network node", or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the terms "base station," "network node," or "network entity" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0055] As indicated above, Figure 1 are provided in the form of examples. Other examples may be related to Figure 1 The examples described are different.

[0056] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0057] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0058] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0059] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0060] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0061] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 9 to 15 ) or any aspects of any of the methods described herein.

[0062] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions described herein (e.g., reference 20). Figures 9 to 15 ) or any aspects of any of the methods described herein.

[0063] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component in may perform one or more techniques associated with configuring a TAG for a component carrier, as described in more detail elsewhere herein. In some aspects, the network node described herein is a base station 110 (e.g., a TRP or a base station associated with a TRP), is included in a base station 110, or includes Figure 2 One or more components of the base station 110 are shown. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Fig.10 The process of 1000 Fig.11 Process 1100, Fig.12 The process 1200 Fig.13 1300 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example Fig.10 The process of 1000 Fig.11 Process 1100, Fig.12 The process 1200 Fig.13 The operations of the process 1300 and / or other processes described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0064] In some aspects, the UE includes means for receiving configuration information indicating: a first configuration of a plurality of CORESET pool indexes for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of the plurality of TAGs; and / or means for sending one or more communications via the first component carrier and the second component carrier based at least in part on the first set of the plurality of TAGs and the second set of one or more TAGs. In some aspects, the UE includes means for sending an indication of a capability to communicate using multiple TAs for a single component carrier; and / or means for receiving configuration information indicating: a plurality of CORESET pool indexes for communications within a single component carrier, and one or more TAGs for the single component carrier based at least in part on the capability. Means for the UE to perform operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0065] In some aspects, the network node includes means for sending configuration information indicating: a first configuration of a plurality of CORESET pool indexes for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of the plurality of TAGs; and / or means for receiving one or more communications via the first component carrier and the second component carrier based at least in part on the first set of the plurality of TAGs and the second set of one or more TAGs. In some aspects, the network node includes means for receiving an indication of a capability to communicate using multiple TAs for a single component carrier; and / or means for sending configuration information indicating: a plurality of CORESET pool indexes for communications within a single component carrier, and one or more TAGs for the single component carrier based at least in part on the capability. In some aspects, means for a network node to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0066] Although Figure 2The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0067] As indicated above, Figure 2 are provided in the form of examples. Other examples may be related to Figure 2 The examples described are different.

[0068] Figure 3 is a diagram illustrating an example 300 decomposed base station architecture according to the present disclosure.

[0069] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access node (RAN) node, a core network node, a network element or a network equipment, such as a base station (BS, for example, base station 110), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an eNB, an NR BS, a 5G NB, an access node (AP), a TRP, a cell, etc.) can be implemented as an aggregated base station (also called a stand-alone BS or a monolithic BS) or a decomposed base station.

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

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

[0072] Figure 3 The decomposed base station architecture shown may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more decomposed base station units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. The RU 340 may communicate with corresponding UEs 120 via one or more RF access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0073] Each of these units (e.g., CU 310, DU 330, RU 340), as well as near-RT RIC 325, non-RTRIC 315, and SMO framework 305 may include one or more interfaces, or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

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

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

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

[0077] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 335) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. In addition, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0078] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

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

[0080] As indicated above, Figure 3 are provided in the form of examples. Other examples may be related to Figure 3 The examples described are different.

[0081] Figure 4 An example logical architecture of a distributed RAN 400 according to the present disclosure is illustrated.

[0082] The 5G access node 405 may include an access node controller 410. The access node controller 410 may be a CU of the distributed RAN 400. In some aspects, a backhaul interface to the 5G core network 415 may terminate at the access node controller 410. The 5G core network 415 may include a 5G control plane component 420 and a 5G user plane component 425 (e.g., a 5G gateway), and a backhaul interface for one or both of the 5G control plane and the 5G user plane may terminate at the access node controller 410. Additionally or alternatively, a backhaul interface to one or more neighbor access nodes 430 (e.g., another 5G access node 405 and / or an LTE access node) may terminate at the access node controller 410.

[0083] The access node controller 410 may include one or more TRPs 435 and / or may communicate with one or more TRPs (e.g., via an F1 control (F1-C) interface and / or an F1 user (F1-U) interface). The TRP 435 may be a DU of the distributed RAN 400. In some aspects, the TRP 435 may correspond to the above combined Figure 1 The base station 110 described herein may be a base station 110. For example, different TRPs 435 may be included in different base stations 110. Additionally or alternatively, multiple TRPs 435 may be included in a single base station 110. In some aspects, a base station 110 may include a CU (e.g., an access node controller 410) and / or one or more DUs (e.g., one or more TRPs 435). In some cases, a TRP 435 may be referred to as a cell, a panel, an antenna array, or an array.

[0084] The TRP 435 may be connected to a single access node controller 410 or to multiple access node controllers 410. In some aspects, there may be a dynamic configuration of split logical functions within the architecture of the distributed RAN 400. For example, the PDCP layer, the RLC layer, and / or the MAC layer may be configured to terminate at the access node controller 410 or the TRP 435.

[0085] In some aspects, multiple TRPs 435 may transmit communications (e.g., the same communication or different communications) in the same transmit time interval (TTI) (e.g., time slot, mini-slot, subframe, or symbol) or in different TTIs using different quasi-co-location (QCL) relationships (e.g., different spatial parameters, different transmit configuration indicator (TCI) states, different pre-coding parameters, and / or different beamforming parameters). In some aspects, the TCI state may be used to indicate one or more QCL relationships. A TRP 435 may be configured to provide services to a UE individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs 435).

[0086] As indicated above, Figure 4 are provided in the form of examples. Other examples may be related to Figure 4 The examples described are different.

[0087] Figure 5 5 is a diagram illustrating an example 500 of multi-TRP communication (sometimes referred to as multi-panel communication) according to the present disclosure. Figure 5 As shown, multiple TRPs 505 can communicate with the same UE. TRP 505 can correspond to the above combination Figure 4 TRP 435 as described.

[0088] Multiple TRPs 505 (shown as TRP A and TRP B) may communicate with the same UE in a coordinated manner (e.g., using coordinated multipoint transmission) to improve reliability and / or increase throughput. TRPs 505 may coordinate such communications via interfaces between TRPs 505 (e.g., backhaul interfaces and / or access node controllers 410). When TRPs 505 are co-located at the same base station 110 (e.g., when TRPs 505 are different antenna arrays or panels of the same base station 110), the interface may have less latency and / or higher capacity, and when TRPs 505 are located at different base stations 110, the interface may have greater latency and / or lower capacity (compared to co-location). Different TRPs 505 may communicate with UEs using different QCL relationships (e.g., different TCI states), different DMRS ports, and / or different layers (e.g., different layers in multi-layer communications).

[0089] In the first multi-TRP transmission mode (e.g., Mode 1), a single physical downlink control channel (PDCCH) can be used to schedule downlink data communications of a single physical downlink shared channel (PDSCH). In this case, multiple TRPs 505 (e.g., TRP A and TRP B) can send communications to the UE on the same PDSCH. For example, a single codeword with different spatial layers for different TRPs 505 can be used to send communications (e.g., where one codeword is mapped to a first set of layers sent by a first TRP 505 and is mapped to a second set of layers sent by a second TRP 505). As another example, multiple codewords can be used to send communications, where different codewords are sent by different TRPs 505 (e.g., using different sets of layers). In either case, different TRPs 505 can use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, the first TRP 505 may use a first QCL relationship or a first TCI state for a first set of DMRS ports corresponding to a first set of layers, and the second TRP 505 may use a second (different) QCL relationship or a second (different) TCI state for a second (different) set of DMRS ports corresponding to a second (different) set of layers. In some aspects, the TCI state in the downlink control information (DCI) (e.g., sent on the PDCCH, such as DCI format 1_0 or DCI format 1_1) may indicate a first QCL relationship (e.g., by indicating a first TCI state) and a second QCL relationship (e.g., by indicating a second TCI state). The first TCI state and the second TCI state may be indicated using a TCI field in the DCI. Typically, in this multi-TRP transmission mode (e.g., mode 1), the TCI field may indicate a single TCI state (for single TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed herein).

[0090] In a second multi-TRP transmission mode (e.g., Mode 2), multiple PDCCHs may be used to schedule downlink data communications for multiple corresponding PDSCHs (e.g., one PDCCH for each PDSCH). In this case, a first PDCCH may schedule a first codeword to be transmitted by the first TRP 505, and a second PDCCH may schedule a second codeword to be transmitted by the second TRP 505. In addition, a first DCI (e.g., transmitted by the first TRP 505) may schedule a first PDSCH communication associated with a first DMRS port set having a first QCL relationship (e.g., indicated by a first TCI state) for the first TRP 505, and a second DCI (e.g., transmitted by the second TRP 505) may schedule a second PDSCH communication associated with a second DMRS port set having a second QCL relationship (e.g., indicated by a second TCI state) for the second TRP 505. In this case, the DCI (e.g., having DCI format 1_0 or DCI format 1_1) may indicate a corresponding TCI state for the TRP 505 corresponding to the DCI. The TCI field of the DCI indicates a corresponding TCI state (eg, the TCI field of the first DCI indicates a first TCI state and the TCI field of the second DCI indicates a second TCI state).

[0091] As indicated above, Figure 5 are provided in the form of examples. Other examples may be related to Figure 5 The examples described are different.

[0092] Figure 6 600 is a diagram illustrating an example of TRP differentiation at a UE based at least in part on a CORESET pool index in accordance with the present disclosure. In some aspects, a CORESET pool index (or CORESETPoolIndex) value may be used by a UE (UE) to identify a TRP associated with an uplink grant received on a PDCCH.

[0093] A CORESET may refer to a control region that is structured to support efficient use of resources, such as by flexible configuration or reconfiguration of resources for one or more PDCCHs associated with a UE. In some aspects, a CORESET may occupy the first symbol of an orthogonal frequency division multiplexing (OFDM) slot, the first two symbols of an OFDM slot, or the first three symbols of an OFDM slot. Thus, a CORESET may include multiple resource blocks (RBs) in the frequency domain, and one, two, or three symbols in the time domain. In 5G, the number of resources included in a CORESET may be flexibly configured, such as by using RRC signaling to indicate the frequency domain region (e.g., the number of resource blocks) or the time domain region (e.g., the number of symbols) of a CORESET.

[0094] like Figure 6 As illustrated, a UE may be configured to have multiple CORESETs in a given serving cell. Each CORESET configured for the UE may be associated with a CORESET identifier (CORESET ID). For example, a first CORESET configured for the UE may be associated with CORESET ID 1, a second CORESET configured for the UE may be associated with CORESET ID 2, a third CORESET configured for the UE may be associated with CORESET ID 3, and a fourth CORESET configured for the UE may be associated with CORESET ID 4.

[0095] like Figure 6 As further illustrated in , two or more (e.g., up to five) CORESETs may be grouped into CORESET pools. Each CORESET pool may be associated with a CORESET pool index. For example, CORESET ID 1 and CORESET ID 2 may be grouped into CORESET pool index 0, and CORESET ID 3 and CORESET ID 4 may be grouped into CORESET pool index 1. In a multi-TRP configuration, each CORESET pool index value may be associated with a particular TRP 605. For example, Figure 6 As illustrated, the first TRP 605 (TRP A) may be associated with CORESET pool index 0, and the second TRP 605 (TRP B) may be associated with CORESET pool index 1. The UE may be configured with information identifying the association between the TRP and the CORESET pool index value assigned to the TRP via a higher layer parameter such as PDCCH-Config. Thus, the UE may identify the TRP that sent the DCI uplink grant by determining the CORESET ID of the CORESET in which the PDCCH carrying the DCI uplink grant was sent, determining the CORESET pool index value associated with the CORESET pool in which the CORESET ID is included, and identifying the TRP associated with the CORESET pool index value.

[0096] As indicated above, Figure 6 are provided in the form of examples. Other examples may be related to Figure 6 The examples described are different.

[0097] Figure 7700 is a diagram illustrating an example of downlink and uplink transmissions between a network node (e.g., a TRP) and a UE in a wireless network according to the present disclosure. In some examples, the downlink and / or uplink transmissions are based at least in part on timing advances and / or protection periods between communications. As an example, the network node (e.g., a TRP) may configure the downlink transmission to end before the start of the protection period. As another example, the UE may advance the start time for the uplink transmission based at least in part on the timing advance.

[0098] As shown in the figure 702-1, the network node may start downlink transmission 704-1 to the UE at a first time point. In some examples, the first time point may be based at least in part on a timing scheme defined by a telecommunications system and / or a telecommunications standard. For illustration, a telecommunications standard may define various time partitions for scheduling transmissions between devices. As an example, a timing scheme may define a radio frame (sometimes referred to as a frame), wherein each radio frame has a predetermined duration (e.g., 10 milliseconds (msec)). Each radio frame may be further divided into a group of Z (Z≥1) subframes, wherein each subframe may have a predetermined duration (e.g., 1 msec). Each subframe may be further divided into a group of time slots and / or each time slot may include a group of L symbol periods (e.g., fourteen symbol periods, seven symbol periods, or another number of symbol periods). Therefore, the first time point shown in the figure 702-1 may be based at least in part on a time partition (e.g., frame, subframe, time slot, microslot and / or symbol) defined by a telecommunications system.

[0099] In some examples, the network node and the UE can communicate with each other wirelessly based on the defined time partition at least in part. However, each device can have different timing references for the time partition. For illustration, and as shown in the figure numeral 702-1, the network node can start downlink transmission 704-1 at a specific physical time point, and the specific physical time point can be associated with the defined time partition at least in part based on the time perspective of the network node. For example, the network node can associate a specific physical time point with a defined time partition (such as the beginning of a symbol, the beginning of a time slot, the beginning of a subframe and / or the beginning of a frame). However, the downlink transmission may cause a propagation delay 706 in physical time, such as a time delay traveling between the network node and the UE based at least in part on the downlink transmission. As shown in the figure numeral 702-2, the UE can receive a downlink transmission 704-2 (corresponding to the downlink transmission 704-1 transmitted by the network node) at a second physical time point, and the second physical time point is later in time relative to the first physical time point. However, from the time perspective of the UE, the UE may associate the second physical time point shown in reference numeral 702-2 with the same specific time point of the defined time partition as the network node (e.g., the start of the same symbol, the start of the same mini-time slot, the start of the same time slot, the start of the same subframe, and / or the start of the same frame). Therefore, as shown in example 700, the time perspective of the UE and the time perspective of the network node may be delayed in physical time.

[0100] In wireless communication technologies such as 4G / LTE and 5G / NR, the TA value is used to control the timing of uplink transmissions of a UE (e.g., UE, etc.) so that a network node (e.g., TRP and / or RU, etc.) receives the uplink transmission at a time aligned with the internal timing of the network node. The network node may indicate the TA value to the UE by measuring the time difference between the reception of the uplink transmission from the UE and the subframe timing used by the network node (e.g., by determining the difference between the time when the network node should receive the uplink transmission according to the subframe timing and the time when the uplink transmission is actually received), and by sending a TA command (TAC) to instruct the UE to send future uplink communications earlier or later, thereby reducing or eliminating the time difference and aligning the timing between the UE and the network node. The TA command is used to offset the timing difference between the UE and the network node due to different propagation delays that occur when the UE is at different distances from the network node. If the TA command is not used, uplink transmissions from different UEs (eg, located at different distances from the network node) may collide due to timing errors even if the uplink transmissions are scheduled for different subframes.

[0101] For illustration, without adjusting the start time of uplink transmission, the UE may be configured to start uplink transmission at a scheduling time point based at least in part on a defined time partition, as described elsewhere herein. As shown in reference numeral 710-1, the start of the scheduling time point may occur at a third physical time point based at least in part on the timing perspective of the UE. However, and as shown in reference numeral 710-2, the scheduling time point with reference to the timing perspective of the network node may occur at a fourth physical time point, which occurs before the third physical time point shown in reference numeral 710-1. Therefore, the network node may instruct the UE to apply timing advance 708 to the uplink transmission to better align the reception of the uplink transmission with the timing perspective of the network node. However, in some examples, the fourth time point shown by reference numeral 710-2 may occur at or near the same physical time point as the third time point shown by reference numeral 710-1, so that the uplink transmission from the UE to the network node incurs a propagation delay 706. In such a scenario, the network node may instruct the UE to apply a timing advance having a duration corresponding to the propagation delay 706 .

[0102] As shown in example 700, the UE may adjust the start time of uplink transmission 712-1 based at least in part on timing advance 708 and the start of the scheduled time point (e.g., at the third physical time point shown in reference numeral 710-1). Based at least in part on the propagation delay, the network node may receive uplink transmission 712-2 (corresponding to uplink transmission 712-1 sent by the UE) at the fourth physical time point shown in reference numeral 710-2.

[0103] In some examples, the timing advance value may be based at least in part on twice the estimated propagation delay (e.g., propagation delay 706) and / or may be based at least in part on a round trip time (RTT). The network node may estimate the propagation delay and / or select the timing advance value based at least in part on communications with the UE. As an example, the network node may estimate the propagation delay based at least in part on a network access request message from the UE. Additionally or alternatively, the network node may estimate and / or select the timing advance value from a set of fixed timing advance values.

[0104] In some examples, the telecommunications system and / or telecommunications standard may define a protection period 714 (e.g., duration) between transmissions to provide the device with sufficient time to switch between different transmission and / or reception modes, for transient stabilization, to provide margin for timing misalignment and / or propagation delays between devices. In some examples, the protection period is a time period during which no transmission or reception is scheduled and / or allowed to occur. The protection period may provide the device with sufficient time to reconfigure the hardware and / or allow the hardware to stabilize within a threshold to enable subsequent transmissions. The protection period 714 may sometimes be referred to as a gap, a switching protection period, or a guard interval.

[0105] In some examples, a transmitting device (e.g., a network node, a CU, a DU, and / or a RU) may select a start transmission time and / or a transmission duration based at least in part on a receiving device and / or a protection period. For example, a network node may select the amount of content (e.g., data and / or control information) to be sent in downlink transmission 704-1 based at least in part on starting transmission at a first physical time point shown by reference numeral 702-1 and / or the UE completing reception of downlink transmission 704-2 before the start point of protection period 714. Alternatively or additionally, the UE may select the amount of content (e.g., data and / or control information) to be sent in uplink transmission 712-1 based at least in part on timing advance 708, a third physical time point shown by reference numeral 710-1, and / or avoiding the start of uplink transmission 712-1 until protection period 714 has ended.

[0106] As indicated above, Figure 7 are provided in the form of examples. Other examples may be related to Figure 7 The examples described are different.

[0107] Figure 8 is a diagram illustrating an example 800 of carrier aggregation according to the present disclosure.

[0108] Carrier aggregation is a technique that enables two or more component carriers (CCs, sometimes referred to as carriers) to be combined (e.g., combined into a single channel) for a single UE to enhance data capacity. As shown, carriers may be combined in the same or different frequency bands. Additionally or alternatively, contiguous or non-contiguous carriers may be combined. A network node may configure carrier aggregation for a UE (such as in an RRC message, a DCI, and / or another signaling message).

[0109] As indicated by reference numeral 805, in some aspects, carrier aggregation may be configured in an intra-band contiguous mode, where the aggregated carriers are contiguous with each other and in the same frequency band. As indicated by reference numeral 810, in some aspects, carrier aggregation may be configured in an intra-band discontiguous mode, where the aggregated carriers are discontiguous with each other and in the same frequency band. As indicated by reference numeral 815, in some aspects, carrier aggregation may be configured in an inter-band discontiguous mode, where the aggregated carriers are discontiguous with each other and in different frequency bands.

[0110] In carrier aggregation, a UE may be configured with a primary carrier or primary cell (PCell) and one or more secondary carriers or secondary cells (SCells). In some aspects, the primary carrier may carry control information (e.g., downlink control information and / or scheduling information) for scheduling data communications on one or more secondary carriers, which may be referred to as cross-carrier scheduling. In some aspects, a carrier (e.g., a primary carrier or a secondary carrier) may carry control information for scheduling data communications on the carrier, which may be referred to as self-carrier scheduling or carrier self-scheduling.

[0111] As indicated above, Figure 8 are provided in the form of examples. Other examples may be related to Figure 8 The examples described are different.

[0112] In some networks, a multi-TRP configuration based on multiple DCIs includes a first DCI (sent from a first TRP) that schedules a first data channel (e.g., a first PDSCH) to be sent to or received from the first TRP. The multi-TRP configuration based on multiple DCIs also includes a second DCI (e.g., sent from a second TRP) that schedules a second data channel (e.g., a second PDSCH) to be sent from a second TRP.

[0113] The UE may distinguish communications (e.g., DCI or data communications) from a first TRP and a second TRP based at least in part on a CORESET pool index (e.g., CORESETPoolIndex) associated with the DCI. Based at least in part on receiving the DCI in resources of a CORESET having the CORESET pool index, the UE may associate the DCI and scheduled data communications with a TRP. For example, the UE may associate a first DCI and a first scheduled data communication with a first TRP based at least in part on receiving the first DCI in a CORESET having a CORESET pool index of 0, and may associate a second DCI and a second scheduled data communication with a second TRP based at least in part on receiving the DCI in a CORESET having a CORESET pool index of 1. The CORESETPoolIndex of the CORESET in which the DCI is received may be used for different purposes, such as for sending hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) feedback to the TRP that sent the DCI and the scheduled data communication.

[0114] In some networks, the UE may determine whether the UE is configured with a multi-DCI based multi-TRP configuration in a given component carrier based at least in part on the UE being configured with multiple different values ​​of the CORESET pool index for the active bandwidth part (BWP) of the serving cell. For example, the UE may be configured by a higher layer parameter (e.g., an RRC parameter such as PDCCH-Configure) including two different values ​​of CORESETPoolIndex in the CORESET for the active BWP of the serving cell.

[0115] In some networks, each serving cell may be associated with a TAG. For example, a TA value selected from the TAG may be applied to uplink transmissions on the serving cell. This may be based at least in part on the TAG being applied to communications with a single network node and / or TRP. In this case, only a single TA may be required for communications with a single network node and / or TRP that may follow the same beam path and whose propagation times may not differ by an amount that satisfies a threshold (e.g., the difference does not result in a communication error, such as the difference not exceeding the cyclic prefix).

[0116] In some networks, two TAs may be specified for the uplink in a multi-DCI multi-TRP configuration. In this case, different TRPs may have different TA values. For example, the first TRP may have a TA value greater than the second TRP. Figure 7The timing advance 708 may be smaller. This can be based at least in part on communications with different TRPs that follow different beam paths and whose propagation times differ by an amount that satisfies a threshold. For example, a first TRP may communicate with a UE via a communication path that is shorter than a propagation path for communications between the UE and a second TRP, resulting in a propagation delay 706 for communications with the first TRP that is shorter than a propagation delay for communications with the second TRP. The difference in propagation path lengths can be based at least in part on the first TRP being located closer to the UE and / or at least in part on the first TRP having fewer reflections in a propagation path (e.g., a line-of-sight path).

[0117] In some networks, in a multi-DCI multi-TRP configuration, the UE may be configured with two CORESET pool index values ​​in the CORESET of the active BWP for the serving cell. Some component carriers may be configured with multiple CORESET pool index values ​​(e.g., if in a multi-DCI multi-TRP configuration), while other component carriers may be configured with a single CORESET pool index value (e.g., if not in a multi-DCI multi-TRP configuration).

[0118] In some networks, when multiple uplink TAs are supported, the UE may be configured with two TAGs for the component carrier. In this case, some component carriers may be configured with multiple TAGs while other component carriers may be configured with a single TAG. If the component carrier is not configured with multiple CORESET pool index values ​​(e.g., multiple TRPs based on multiple DCIs), the component carrier may be configured with only a single TAG. However, if the serving cell is configured with multiple CORESET pool index values, the UE and / or network node may not be able to determine whether a single TAG or multiple TAGs can be configured for the component carrier. In this way, when an unnecessary large number of TAGs are configured, the network node and the UE may unnecessarily consume power, computing, network and / or communication resources to identify and transmit TAs. For example, based at least in part on configuring multiple TAGs when fewer TAGs are needed, overhead may increase and / or control channel monitoring may be excessive.

[0119] In some aspects described herein, configuration of a TAG for a component carrier may be prohibited or allowed based at least in part on the number of CORESET pool indices configured for the component carrier. Similarly, the number of CORESET pool indices that can be configured for a component carrier may be prohibited or allowed based at least in part on the number of TAGs configured for the component carrier.

[0120] In some aspects, if a UE is configured with multiple component carriers, then for any two component carriers that are each configured with two CORESET pool index values, the UE may not be configured (e.g., may not be expected to be configured) with a first component carrier configured with two TAGs and a second component carrier configured with a single TAG. For example, if a first component carrier is configured with two CORESET pool index values ​​and two TAGs, then if the second component carrier is configured with two CORESETPoolIndex values, the second component carrier should also be configured with multiple TAGs (e.g., the same number of TAGs as the first component carrier). Similarly, if a first component carrier is configured with two CORESET pool index values ​​and two TAGs, then if the second component carrier is configured with a single TAG, the second component carrier is not allowed to be configured with multiple CORESET pool index values.

[0121] In some aspects, if a UE is configured with multiple component carriers, then for any two component carriers that are each configured with two CORESET pool index values, the UE may be configurable such that, if one or more conditions are met, the first component carrier is configured with two TAGs and the second component carrier is configured with a single TAG. For example, the second component carrier may be configured with a single TAG based at least in part on the single TAG of the second component carrier being different from each of the two TAGs of the first component carrier. Additionally or alternatively, the second component carrier may be configured with a single TAG based at least in part on the first component carrier and the second component carrier being on different frequency bands (e.g., as combined with Figure 8 described).

[0122] Based at least in part on the number of TAGs for different component carriers depending on one or more conditions, the UE and the network node can save power, computation, network, and / or communication resources that otherwise might have been used to identify and transmit the TA when an unnecessarily large number of TAGs are configured. For example, when multiple TAGs may be used (e.g., when different component carriers may be used for communications using different TAs, propagation paths, and / or propagation delays), based at least in part on configuring multiple TAGs, overhead can be saved and / or control channel monitoring can be reduced.

[0123] In some networks, a UE may be configured with a single component carrier for communications. If the component carrier is configured with multiple CORESET pool index values, the UE may communicate with different TRPs within the single component carrier. As described herein, the propagation paths used to communicate with different TRPs may be different, which may result in different TAs. However, some UEs may support multiple TAGs for communications within a single component carrier, while other UEs may not support multiple TAGs for communications within a single component carrier. If the UE supports multiple TAGs, the use of multiple TAGs may improve the TA and reduce communication errors caused by configuring a single TA for communications with different TRPs with different propagation delays. However, if the UE does not support multiple TAGs for a single component carrier, attempting to configure the UE with multiple TAGs may result in communication errors, at least in part based on the UE's inability to correctly identify the indicated TA from the multiple TAGs.

[0124] In some aspects, a UE may be configured with multiple TAGs for a single component carrier based at least in part on UE capabilities. For example, if the UE is capable of multiple TA operation for a single component carrier, the UE may be allowed to be configured with multiple TAGs. If the UE is not capable of multiple TA operation for a single component carrier, the UE may be prohibited from being configured with multiple TAGs. In this case, only a single TAG may be configured for the component carrier.

[0125] Based at least in part on the number of TAGs available for configuring the UE being based at least in part on the capabilities of the UE (e.g., as indicated to a network node), the UE may improve TA application when supporting multiple TAGs, which may reduce communication errors and communication, network, power, and / or computing resources that may otherwise be consumed to detect and correct communication errors. Additionally or alternatively, when only a single TAG is supported, the UE may improve TA application based at least in part on the UE's ability to correctly identify the indicated TA from a single TAG rather than multiple tags, which may reduce communication errors caused by failure to apply the indicated TA.

[0126] Fig. 9 is a diagram of an example 900 associated with configuring a TAG for a component carrier according to the present disclosure. Fig. 9 As shown, a network node (e.g., base station 110, CU, DU, and / or RU) may communicate with a UE (e.g., UE 120). In some aspects, the network node and the UE may be part of a wireless network (e.g., wireless network 100). The UE and the network node may be in Fig. 9The operations shown have previously established a wireless connection. In some aspects, the network node may communicate with the UE via one or more TRPs, relays, forwarding nodes, and / or repeater nodes, etc. One or more TRPs, relays, forwarding nodes, and / or repeater nodes, etc. may be associated with different beam paths, propagation paths, and / or propagation delays, etc.

[0127] As indicated by reference numeral 905, the network node may send, and the UE may receive, configuration information. In some aspects, the UE may receive the configuration information via one or more of RRC signaling, one or more MAC control elements (CEs), and / or DCI, etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for the UE to select (e.g., known to the UE and / or previously indicated by the network node or other network device) and / or explicit configuration information for the UE to configure the UE, etc.

[0128] In some aspects, the configuration information may indicate that the UE will send an indication of support for multiple TAGs for a single component carrier and / or support for multiple TAGs for different component carriers. In some aspects, the UE may indicate the number of component carriers supported by the UE and / or the number of TAGs supported by the UE.

[0129] The UE may configure itself based at least in part on the configuration information.In some aspects, the UE may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0130] As indicated by reference numeral 910, the UE may send an indication of a capability to support TAGs for one or more component carriers, and the network node may receive the indication. For example, the UE may indicate a capability to support multiple TAGs for a single component carrier. Additionally or alternatively, the UE may indicate support for multiple TAGs and / or CORESET pool indexes for component carriers used for communicating with a network node (e.g., a TRP associated with the network node). For example, the UE may indicate that the UE supports multiple CORESET pool indexes for one or more component carriers (e.g., all component carriers) and / or may indicate support for multiple CORESET pool indexes for component carriers based at least in part on the frequency band of the component carrier, etc.

[0131] In some aspects, the indication of the capability may indicate that the UE supports communication using multiple TAs for a single component carrier. For example, the UE may have the capability based at least in part on the configuration of the UE, communication resources at the UE (e.g., antennas and / or transmit chains, etc.), power resources available at the UE, and / or computing resources available at the UE, etc.

[0132] In some aspects, the UE may receive a first portion of the configuration information described in conjunction with reference numeral 905 prior to sending the indication of the capabilities and may receive a second portion of the configuration information after sending the indication of the capabilities.

[0133] As indicated by reference numeral 915, the UE may receive configuration information associated with one or more CORESET pool indexes and one or more TAGs for one or more component carriers, and the network node may send the configuration information. For example, the UE may receive an indication of a first component carrier, an indication of one or more CORESET pool indexes for the component carrier, and an indication of one or more TAGs associated with the component carrier and / or mapped to the one or more CORESET pool indexes (e.g., a first TAG mapped to a first CORESET pool index value and / or a second TAG mapped to a second CORESET pool index value, or a single TAG mapped to a component carrier and multiple or all CORESET pool index values ​​of the component carrier, etc.).

[0134] In some aspects, the configuration information may indicate a first configuration of a plurality of CORESET pool indexes for a first component carrier and for a second component carrier. The configuration information may also indicate a second configuration of a first set of a plurality of TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier. The second set of one or more TAGs may be configured based at least in part on the first set of a plurality of TAGs. For example, the second set of one or more TAGs may be configured with a plurality of TAGs based at least in part on the first set of a plurality of TAGs being configured with a plurality of TAGs. Additionally or alternatively, the second set of one or more TAGs may be configured with the same number of TAGs as the first set of a plurality of TAGs.

[0135] In some aspects, the second set of one or more TAGs may be configured dependent on a first set of multiple TAGs, the first set of multiple TAGs being based at least in part on: the first component carrier being configured with multiple CORESET pool indexes, and the second component carrier being configured with multiple CORESET pool indexes. Additionally or alternatively, the second set of one or more TAGs may be configured without being dependent on (not dependent on) the first set of multiple TAGs, the first set of multiple TAGs being based at least in part on: the first component carrier being configured with a single CORESET pool index, or the second component carrier being configured with a single CORESET pool index.

[0136] In some aspects, the second component carrier may be configured with multiple CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with multiple TAGs. For example, the UE may be configured such that the UE may be configured with multiple component carriers as long as each component carrier with multiple CORESET pool indexes has the same number of TAGs.

[0137] In some aspects, when a first TAG set (e.g., associated with a first component carrier) is configured with a plurality of TAGs, a second TAG set (e.g., associated with a second component carrier) may be able to be configured based at least in part on a single TAG in the second TAG set being a different TAG than each TAG in the first TAG set (e.g., the single tag is not included in the first set of the plurality of TAGs and / or the first component carrier and the second component carrier are in different frequency bands (e.g., Figure 8 In some aspects, the first component carrier may have a different number of TAGs than the second component carrier based at least in part on the frequency band of the first component carrier having different propagation characteristics (e.g., propagation loss, reflected signals, or objects through which signals pass) than the propagation characteristics of the second component carrier. For example, the first component carrier may be on a frequency band that passes through objects (such as branches, leaves, and / or other objects), while the second component carrier may be on a frequency band that is reflected from branches, leaves, and / or other objects. In this case, the UE may send communications to the TRP using different beam paths based at least in part on the propagation characteristics of the component carriers at different frequency bands.

[0138] In some aspects, the configuration information may indicate multiple CORESET pool indexes for communication within a single component carrier and one or more TAGs for the single component carrier based at least in part on the capabilities of the UE. For example, the UE may be configured to communicate using multiple TAGs within a single component carrier based at least in part on the UE indicating the capability to support multiple TAGs within the single component carrier. In some aspects, the configuration information also indicates multiple TAGs for a single component carrier based in part on multiple CORESET pool indexes being associated with different propagation times to one or more network nodes (e.g., TRPs). In some aspects, the UE may be configured with multiple TAGs for a single component carrier based at least in part on the propagation times to one or more network nodes differing by an amount that satisfies a threshold. For example, the threshold may be based at least in part on a cyclic prefix associated with communication via a first component carrier or a second component carrier.

[0139] As indicated by reference numeral 920, the UE may receive an indication of an allocation of one or more component carriers associated with one or more TAs of one or more TAGs, and the network node may send the indication.

[0140] As shown by reference numeral 925, the UE may identify a CORESET pool index for receiving an indication of an allocation and apply a TA based at least in part on the CORESET pool index. For example, the UE may receive an indication of an allocation within a CORESET of a component carrier and having a CORESET pool index mapped to a TAG. The indication of the allocation may indicate a TA for the TAG of the allocation. For example, the indication of the allocation may indicate an index of a TA within the TAG that maps to the CORESET pool index (e.g., the UE determines the TAG to which the index of the TA applies based at least in part on the CORESET pool index).

[0141] As shown by reference numeral 930, the UE may transmit one or more communications via one or more component carriers based at least in part on the one or more TAGs. In some aspects, the UE may transmit one or more communications using inter-band carrier aggregation via a first component carrier and a second component carrier (e.g., if configured with multiple component carriers). In some aspects, the UE may transmit one or more communications using a single component carrier and / or one or more TAs (e.g., if configured with a single component carrier) based at least in part on the capabilities of the UE.

[0142] Based at least in part on the number of TAGs for different component carriers depending on one or more conditions, the UE and the network node can save power, computation, network, and / or communication resources that otherwise might have been used to identify and transmit the TA when an unnecessarily large number of TAGs are configured. For example, when multiple TAGs may be used (e.g., when different component carriers may be used for communications using different TAs, propagation paths, and / or propagation delays), based at least in part on configuring multiple TAGs, overhead can be saved and / or control channel monitoring can be reduced.

[0143] Additionally or alternatively, based at least in part on the number of TAGs that the UE can be configured to use for a single component carrier being based at least in part on the capabilities of the UE (e.g., as indicated to a network node), the UE can improve TA application when supporting multiple TAGs. This can reduce communication errors and communication, network, power, and / or computing resources that may otherwise be consumed to detect and correct communication errors. Additionally or alternatively, when only a single TAG is supported, the UE can improve TA application based at least in part on the UE's ability to correctly identify an indicated TA from a single TAG rather than multiple tags, which can reduce communication errors caused by failure to apply the indicated TA.

[0144] As indicated above, Fig. 9 are provided in the form of examples. Other examples may be related to Fig. 9 The examples described are different.

[0145] Fig.10 is a diagram illustrating an example process 1000, performed, for example, by a UE, according to the present disclosure. Example process 1000 is an example in which a UE (eg, UE 120) performs operations associated with configuring a timing advance group for a component carrier.

[0146] like Fig.10 As shown, in some aspects, process 1000 may include: receiving configuration information indicating: a first configuration of a plurality of CORESET pool indexes for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of the plurality of TAGs (block 1010). For example, a UE (e.g., using Fig.14 The communication manager 140 and / or receiving component 1402 depicted in the figure can receive configuration information indicating: a first configuration of multiple CORESET pool indexes for a first component carrier and for a second component carrier, and a first set of multiple TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured at least in part based on the first set of multiple TAGs, as described above.

[0147] like Fig.10 As further shown, in some aspects, process 1000 may include: sending one or more communications via a first component carrier and a second component carrier based at least in part on a first set of a plurality of TAGs and a second set of one or more TAGs (block 1020). Fig.14 The communication manager 140 and / or the sending component 1404 depicted in FIG. 1 may send one or more communications via the first component carrier and the second component carrier based at least in part on the first set of multiple TAGs and the second set of one or more TAGs, as described above.

[0148] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0149] In a first aspect, the second set of one or more TAGs is configured with the same number of TAGs as the first set of the plurality of TAGs.

[0150] In a second aspect, alone or in combination with the first aspect, a second set of one or more TAGs is configured with a plurality of TAGs based at least in part on the first set of a plurality of TAGs being configured with a plurality of TAGs.

[0151] In a third aspect, alone or in combination with one or more of the first and second aspects, a second set of one or more TAGs is configured at least in part based on a first set of multiple TAGs, and the first set of multiple TAGs is at least in part based on: the first component carrier is configured with multiple CORESET pool indexes, and the second component carrier is configured with multiple CORESET pool indexes.

[0152] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the second component carrier can be configured with multiple CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with multiple TAGs.

[0153] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, a second set of one or more TAGs may be configured with a single TAG based at least in part on one or more of the following: the single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or the first component carrier and the second component carrier are in different frequency bands.

[0154] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, sending one or more communications via the first component carrier and the second component carrier includes: sending one or more communications via the first component carrier and the second component carrier using inter-band carrier aggregation.

[0155] In a seventh aspect, alone or in combination with one or more of aspects 1 to 6, process 1000 includes: receiving configuration information indicating whether a second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of the following: the single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or the first component carrier and the second component carrier are in different frequency bands.

[0156] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more of the blocks in the process 1000 may be performed in parallel.

[0157] Fig.11is a diagram illustrating an example process 1100, performed, for example, by a UE, according to the present disclosure. Example process 1100 is an example in which a UE (eg, UE 120) performs operations associated with configuring a TAG for a component carrier.

[0158] like Fig.11 As shown, in some aspects, process 1100 may include sending an indication of an ability to communicate using multiple TAs for a single component carrier (block 1110). Fig.14 The communication manager 140 and / or transmitting component 1404 depicted in FIG. 140 may transmit an indication of the ability to communicate using multiple TAs for a single component carrier, as described above.

[0159] like Fig.11 As further shown, in some aspects, process 1100 may include receiving configuration information indicating a plurality of CORESET pool indices for communication within a single component carrier and one or more TAGs for the single component carrier based at least in part on capabilities (block 1120). Fig.14 The communication manager 140 and / or receiving component 1402 depicted in FIG. 1 may receive configuration information indicating: multiple CORESET pool indexes for communication within a single component carrier, and one or more TAGs for the single component carrier based at least in part on capabilities, as described above.

[0160] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0161] In a first aspect, configuration information indicates multiple TAGs for a single component carrier based at least in part on a capability to support multiple TAGs for the single component carrier.

[0162] In a second aspect, alone or in combination with the first aspect, the configuration information further indicates multiple TAGs for a single component carrier based in part on multiple CORESET pool indexes being associated with different propagation times to one or more network nodes.

[0163] In a third aspect, alone or in combination with one or more of the first and second aspects, the configuration information indicates a single TAG for a single component carrier based at least in part on associating multiple CORESET pool indexes with propagation times that differ by an amount satisfying a threshold.

[0164] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be performed in parallel.

[0165] Fig.12 is a diagram illustrating an example process 1200 performed, for example, by a network node according to the present disclosure. The example process 1200 is an example in which a network node (eg, base station 110, CU, DU, and / or CU) performs operations associated with configuring a TAG for a component carrier.

[0166] like Fig.12 As shown, in some aspects, process 1200 may include: sending configuration information indicating: a first configuration of a plurality of CORESET pool indexes for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of the plurality of TAGs (block 1210). For example, a network node (e.g., using Fig.15 The communication manager 150 and / or sending component 1504 depicted in the figure can send configuration information indicating: a first configuration of multiple CORESET pool indexes for a first component carrier and for a second component carrier, and a first set of multiple TAGs for the first component carrier and a second configuration of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured at least in part based on the first set of multiple TAGs, as described above.

[0167] like Fig.12 As further shown, in some aspects, process 1200 may include receiving one or more communications via a first component carrier and a second component carrier based at least in part on a first set of a plurality of TAGs and a second set of one or more TAGs (block 1220). Fig.15 The communication manager 150 and / or receiving component 1502 depicted in FIG. 1 may receive one or more communications via the first component carrier and the second component carrier based at least in part on the first set of multiple TAGs and the second set of one or more TAGs, as described above.

[0168] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0169] In a first aspect, the second set of one or more TAGs is configured with the same number of TAGs as the first set of the plurality of TAGs.

[0170] In a second aspect, alone or in combination with the first aspect, a second set of one or more TAGs is configured with a plurality of TAGs based at least in part on the first set of a plurality of TAGs being configured with a plurality of TAGs.

[0171] In a third aspect, alone or in combination with one or more of the first and second aspects, a second set of one or more TAGs is configured at least in part based on a first set of multiple TAGs, and the first set of multiple TAGs is at least in part based on: the first component carrier is configured with multiple CORESET pool indexes, and the second component carrier is configured with multiple CORESET pool indexes.

[0172] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the second component carrier can be configured with multiple CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with multiple TAGs.

[0173] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, a second set of one or more TAGs may be configured with a single TAG based at least in part on one or more of the following: the single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or the first component carrier and the second component carrier are in different frequency bands.

[0174] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the reception of one or more communications via the first component carrier and the second component carrier includes: receiving the one or more communications via the first component carrier and the second component carrier using inter-band carrier aggregation.

[0175] In a seventh aspect, alone or in combination with one or more of aspects 1 to 6, process 1200 includes sending configuration information indicating whether a second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of the following: the single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or the first component carrier and the second component carrier are in different frequency bands.

[0176] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1200. Additionally or alternatively, two or more blocks of the blocks of process 1200 may be performed in parallel.

[0177] Fig.13 is a diagram illustrating an example process 1300 performed, for example, by a network node according to the present disclosure. The example process 1300 is an example in which a network node (eg, base station 110, CU, DU, and / or CU) performs operations associated with configuring a TAG for a component carrier.

[0178] like Fig.13 As shown, in some aspects, process 1300 may include receiving an indication of an ability to communicate using multiple TAs for a single component carrier (block 1310). For example, a network node (e.g., using Fig.15 The communication manager 150 and / or receiving component 1502 depicted in FIG. 1 may receive an indication of an ability to communicate using multiple TAs for a single component carrier, as described above.

[0179] like Fig.13 As further shown, in some aspects, process 1300 may include sending configuration information indicating a plurality of CORESET pool indexes for communication within a single component carrier and one or more TAGs for the single component carrier based at least in part on capabilities (block 1320). For example, a network node (e.g., using Fig.15 The communication manager 150 and / or sending component 1504 depicted in FIG. 1 may send configuration information indicating: multiple CORESET pool indexes for communication within a single component carrier, and one or more TAGs for a single component carrier based at least in part on capabilities, as described above.

[0180] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0181] In a first aspect, configuration information indicates multiple TAGs for a single component carrier based at least in part on a capability to support multiple TAGs for the single component carrier.

[0182] In a second aspect, alone or in combination with the first aspect, the configuration information further indicates multiple TAGs for a single component carrier based in part on multiple CORESET pool indexes being associated with different propagation times to one or more network nodes.

[0183] In a third aspect, alone or in combination with one or more of the first and second aspects, the configuration information indicates a single TAG for a single component carrier based at least in part on associating multiple CORESET pool indexes with propagation times that differ by an amount satisfying a threshold.

[0184] although Fig.13 Example blocks of process 1300 are shown, but in some aspects, process 1300 may include Fig.13 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1300. Additionally or alternatively, two or more blocks of the blocks of process 1300 may be performed in parallel.

[0185] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0186] Fig.14 1 is a diagram of an example apparatus 1400 for wireless communication. Apparatus 1400 may be a UE, or a UE may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402 and a transmitting component 1404 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using receiving component 1402 and transmitting component 1404. As further shown, apparatus 1400 may include a communication manager 1408 (e.g., communication manager 140).

[0187] In some aspects, the apparatus 1400 may be configured to perform Fig. 9 Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Fig.10 The process of 1000 Fig.11 In some aspects, Fig.14 The device 1400 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.14 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0188] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1406. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1400. In some aspects, the receiving component 1402 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0189] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some aspects, one or more other components of the device 1400 may generate communications and may provide the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1404 can be co-located with the receive component 1402 in a transceiver.

[0190] The receiving component 1402 can receive configuration information indicating: a first configuration of a plurality of CORESET pool indexes for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of the plurality of TAGs. The sending component 1404 can send one or more communications via the first component carrier and the second component carrier based at least in part on the first set of the plurality of TAGs and the second set of the one or more TAGs.

[0191] The receiving component 1402 can receive configuration information indicating whether a second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of the following: the single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or the first component carrier and the second component carrier are in different frequency bands.

[0192] Transmitting component 1404 can transmit an indication of capability to communicate using multiple TAs for a single component carrier. Receiving component 1402 can receive configuration information indicating: multiple CORESET pool indexes for communication within a single component carrier and one or more TAGs for the single component carrier based at least in part on the capability.

[0193] The communication manager 1408 can provide / receive information to / from the receiving component 1402 and / or the sending component 1404 in conjunction with one or more operations of the receiving component 1402 and / or the sending component 1404 .

[0194] Fig.14 The number and arrangement of components shown are provided by way of example. Fig.14 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.14 Two or more components shown may be implemented in a single component, or Fig.14 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.14 The component set (one or more components) shown may perform the operations described as being performed by Fig.14 Another set of components shown performs one or more functions.

[0195] Fig.15 1 is a diagram of an example apparatus 1500 for wireless communication. Apparatus 1500 may be a network node, or a network node may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502 and a transmitting component 1504 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1500 may communicate with another apparatus 1506 (such as a UE, a base station, or another wireless communication device) using receiving component 1502 and transmitting component 1504. As further shown, apparatus 1500 may include a communication manager 1508 (e.g., communication manager 150).

[0196] In some aspects, the apparatus 1500 may be configured to perform Fig. 9Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Fig.12 The process 1200 Fig.13 In some aspects, Fig.15 The device 1500 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.15 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0197] The receiving component 1502 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1506. The receiving component 1502 may provide the received communications to one or more other components of the device 1500. In some aspects, the receiving component 1502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1500. In some aspects, the receiving component 1502 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0198] Transmit component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1506. In some aspects, one or more other components of device 1500 may generate communications and may provide the generated communications to transmit component 1504 for transmission to device 1506. In some aspects, transmit component 1504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1506. In some aspects, transmit component 1504 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1504 can be co-located with the receive component 1502 in a transceiver.

[0199] The transmitting component 1504 can transmit configuration information indicating: a first configuration of a plurality of CORESET pool indexes for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of TAGs for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of the plurality of TAGs. The receiving component 1502 can receive one or more communications via the first component carrier and the second component carrier based at least in part on the first set of the plurality of TAGs and the second set of the one or more TAGs.

[0200] The sending component 1504 can send configuration information that indicates whether the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of the following: the single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or the first component carrier and the second component carrier are in different frequency bands.

[0201] Receiving component 1502 can receive an indication of capability to communicate using multiple TAs for a single component carrier.Sending component 1504 can send configuration information indicating: multiple CORESET pool indexes for communication within the single component carrier and one or more TAGs for the single component carrier based at least in part on the capability.

[0202] The communication manager 1508 can provide / receive information to / from the receiving component 1502 and / or the sending component 1504 in conjunction with one or more operations of the receiving component 1502 and / or the sending component 1504 .

[0203] Fig.15 The number and arrangement of components shown are provided by way of example. Fig.15 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.15 Two or more components shown may be implemented in a single component, or Fig.15 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.15 The component set (one or more components) shown may perform the operations described as being performed by Fig.15 Another set of components shown performs one or more functions.

[0204] The following provides an overview of some aspects of the disclosure:

[0205] Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: receiving configuration information, the configuration information indicating: a first configuration of multiple control resource set (CORESET) pool indexes for a first component carrier and for a second component carrier, and a first set of multiple timing advance groups (TAGs) for the first component carrier and a second configuration of a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured at least in part based on the first set of multiple TAGs; and sending one or more communications via the first component carrier and the second component carrier based at least in part on the first set of multiple TAGs and the second set of one or more TAGs.

[0206] Aspect 2: The method according to aspect 1, wherein the second set of one or more TAGs is configured with the same number of TAGs as the first set of multiple TAGs.

[0207] Aspect 3: The method according to any one of aspects 1 to 2, wherein the second set of one or more TAGs is configured with multiple TAGs based at least in part on the first set of multiple TAGs being configured with multiple TAGs.

[0208] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the second set of one or more TAGs is configured at least in part based on the first set of multiple TAGs, and the first set of multiple TAGs is at least in part based on: the first component carrier is configured with multiple CORESET pool indexes, and the second component carrier is configured with multiple CORESET pool indexes.

[0209] Aspect 5: The method according to any one of aspects 1 to 4, wherein the second component carrier can be configured with multiple CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with multiple TAGs.

[0210] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the second set of one or more TAGs is capable of being configured with a single TAG based at least in part on one or more of the following: the single TAG in the second set of one or more TAGs is a TAG different from each TAG in the first set of multiple TAGs, or the first component carrier and the second component carrier are in different frequency bands.

[0211] Aspect 7: The method according to aspect 6, wherein the sending of the one or more communications via the first component carrier and the second component carrier includes: sending the one or more communications via the first component carrier and the second component carrier using inter-band carrier aggregation.

[0212] Aspect 8: According to any one of Aspects 1 to 7, the method further includes: receiving configuration information, the configuration information indicating whether the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of the following: the single TAG in the second set of one or more TAGs is a TAG different from each TAG in the first set of multiple TAGs, or the first component carrier and the second component carrier are in different frequency bands.

[0213] Aspect 9: A method of wireless communication performed by a user equipment (UE), the method comprising: sending an indication of the ability to communicate using multiple timing advances (TAs) for a single component carrier; and receiving configuration information, the configuration information indicating: multiple control resource set (CORESET) pool indexes for communication within the single component carrier, and one or more timing advance groups (TAGs) for the single component carrier based at least in part on the capability.

[0214] Aspect 10: The method of aspect 9, wherein the configuration information indicates multiple TAGs for the single component carrier based at least in part on the capability supporting multiple TAGs for the single component carrier.

[0215] Aspect 11: The method of aspect 10, wherein the configuration information further indicates multiple TAGs for the single component carrier based in part on the multiple CORESET pool indexes being associated with different propagation times to one or more network nodes.

[0216] Aspect 12: The method according to any one of aspects 9 to 11, wherein the configuration information indicates a single TAG for the single component carrier based at least in part on the multiple CORESET pool indexes being associated with propagation times that differ by an amount that satisfies a threshold.

[0217] Aspect 13: A method for wireless communication performed by a network node, the method comprising: sending configuration information, the configuration information indicating: a first configuration of multiple control resource set (CORESET) pool indexes for a first component carrier and for a second component carrier, and a first set of multiple timing advance groups (TAGs) for the first component carrier and a second configuration of a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured at least in part based on the first set of multiple TAGs; and receiving one or more communications via the first component carrier and the second component carrier based at least in part on the first set of multiple TAGs and the second set of one or more TAGs.

[0218] Aspect 14: The method according to aspect 13, wherein the second set of one or more TAGs is configured with the same number of TAGs as the first set of multiple TAGs.

[0219] Aspect 15: The method according to any one of aspects 13 to 14, wherein the second set of one or more TAGs is configured with multiple TAGs based at least in part on the first set of multiple TAGs being configured with multiple TAGs.

[0220] Aspect 16: A method according to any one of Aspects 13 to 15, wherein the second set of one or more TAGs is configured at least in part based on the first set of multiple TAGs, and the first set of multiple TAGs is at least in part based on: the first component carrier is configured with multiple CORESET pool indexes, and the second component carrier is configured with multiple CORESET pool indexes.

[0221] Aspect 17: The method according to any one of aspects 13 to 16, wherein the second component carrier can be configured with multiple CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with multiple TAGs.

[0222] Aspect 18: A method according to any one of Aspects 13 to 17, wherein the second set of one or more TAGs is capable of being configured with a single TAG based at least in part on one or more of the following: the single TAG in the second set of one or more TAGs is a TAG different from each TAG in the first set of multiple TAGs, or the first component carrier and the second component carrier are in different frequency bands.

[0223] Aspect 19: The method according to aspect 18, wherein the receiving of the one or more communications via the first component carrier and the second component carrier comprises: receiving the one or more communications via the first component carrier and the second component carrier using inter-band carrier aggregation.

[0224] Aspect 20: According to any one of Aspects 13 to 19, the method further includes: sending configuration information, wherein the configuration information indicates whether the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of the following: the single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or the first component carrier and the second component carrier are in different frequency bands.

[0225] Aspect 21: A method of wireless communication performed by a network node, the method comprising: receiving an indication of the capability to communicate using multiple timing advances (TAs) for a single component carrier; and sending configuration information, the configuration information indicating: multiple control resource set (CORESET) pool indexes for communication within the single component carrier, and one or more timing advance groups (TAGs) for the single component carrier based at least in part on the capability.

[0226] Aspect 22: The method according to aspect 21, wherein the configuration information indicates multiple TAGs for the single component carrier based at least in part on the capability supporting multiple TAGs for the single component carrier.

[0227] Aspect 23: The method of aspect 22, wherein the configuration information further indicates multiple TAGs for the single component carrier based in part on the multiple CORESET pool indexes being associated with different propagation times to one or more network nodes.

[0228] Aspect 24: The method according to any one of Aspects 21 to 23, wherein the configuration information indicates a single TAG for the single component carrier based at least in part on the multiple CORESET pool indexes being associated with propagation times that differ by an amount that satisfies a threshold.

[0229] Aspect 25: An apparatus for performing wireless communications at a device, the apparatus 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 one or more of the methods described in Aspects 1 to 24.

[0230] Aspect 26: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 24.

[0231] Aspect 27: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 24.

[0232] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 24.

[0233] Aspect 29: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 24.

[0234] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0235] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0236] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0237] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0238] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an entry, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "at least partially based on", unless explicitly stated otherwise. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise explicitly stated (for example, if used in combination with "any" or "only one").

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: Receive configuration information, the configuration information indicating: a first configuration of a plurality of control resource set (CORESET) pool indices for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of timing advance groups (TAGs) for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs; as well as One or more communications are sent via the first component carrier and the second component carrier based at least in part on the first set of a plurality of TAGs and the second set of one or more TAGs. 2 . The method of claim 1 , wherein the second set of one or more TAGs is configured with the same number of TAGs as the first set of multiple TAGs. 3 . The method of claim 1 , wherein the second set of one or more TAGs is configured with multiple TAGs based at least in part on the first set of multiple TAGs being configured with multiple TAGs.

4. The method of claim 1 , wherein the second set of one or more TAGs is configured based at least in part on the first set of multiple TAGs, the first set of multiple TAGs being based at least in part on: The first component carrier is configured with a plurality of CORESET pool indexes, and The second component carrier is configured with a plurality of CORESET pool indexes. 5 . The method of claim 1 , wherein the second component carrier is capable of being configured with a plurality of CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with a plurality of TAGs.

6. The method of claim 1 , wherein the second set of one or more TAGs is configurable with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

7. The method of claim 6, wherein the sending of the one or more communications via the first component carrier and the second component carrier comprises: The one or more communications are sent using inter-band carrier aggregation via the first component carrier and the second component carrier.

8. The method according to claim 1, further comprising: receiving configuration information indicating whether the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

9. A method of wireless communication performed by a user equipment (UE), the method comprising: sending an indication of a capability to communicate using multiple timing advances (TAs) for a single component carrier; as well as Receive configuration information, the configuration information indicating: a plurality of control resource set (CORESET) pool indices for communications within the single component carrier, and One or more timing advance groups (TAGs) for the single component carrier based at least in part on the capabilities.

10. The method of claim 9, wherein the configuration information indicates multiple TAGs for the single component carrier based at least in part on the capability to support multiple TAGs for the single component carrier.

11. The method of claim 10, wherein the configuration information further indicates multiple TAGs for the single component carrier based in part on the multiple CORESET pool indexes being associated with different propagation times to one or more network nodes.

12. The method of claim 9, wherein the configuration information indicates a single TAG for the single component carrier based at least in part on the plurality of CORESET pool indexes being associated with propagation times that differ by an amount satisfying a threshold.

13. A method of wireless communication performed by a network node, the method comprising: Send configuration information, the configuration information indicating: a first configuration of a plurality of control resource set (CORESET) pool indices for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of timing advance groups (TAGs) for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs; as well as One or more communications are received via the first component carrier and the second component carrier based at least in part on the first set of a plurality of TAGs and the second set of one or more TAGs. 14 . The method of claim 13 , wherein the second set of one or more TAGs is configured with the same number of TAGs as the first set of multiple TAGs.

15. The method of claim 13, wherein the second set of one or more TAGs is configured with multiple TAGs based at least in part on the first set of multiple TAGs being configured with multiple TAGs.

16. The method of claim 13, wherein the second set of one or more TAGs is configured based at least in part on the first set of multiple TAGs, the first set of multiple TAGs being based at least in part on: The first component carrier is configured with a plurality of CORESET pool indexes, and The second component carrier is configured with a plurality of CORESET pool indexes.

17. The method of claim 13, wherein the second component carrier is capable of being configured with a plurality of CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with a plurality of TAGs.

18. The method of claim 13, wherein the second set of one or more TAGs is configurable with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

19. The method of claim 18, wherein receiving the one or more communications via the first component carrier and the second component carrier comprises: The one or more communications are received via the first component carrier and the second component carrier using inter-band carrier aggregation.

20. The method according to claim 13, further comprising: Sending configuration information indicating whether the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

21. A method of wireless communication performed by a network node, the method comprising: receiving an indication of a capability to communicate using multiple timing advances (TAs) for a single component carrier; as well as Send configuration information, the configuration information indicating: a plurality of control resource set (CORESET) pool indices for communications within the single component carrier, and One or more timing advance groups (TAGs) for the single component carrier based at least in part on the capabilities.

22. The method of claim 21, wherein the configuration information indicates multiple TAGs for the single component carrier based at least in part on the capability to support multiple TAGs for the single component carrier.

23. The method of claim 22, wherein the configuration information further indicates multiple TAGs for the single component carrier based in part on the multiple CORESET pool indexes being associated with different propagation times to one or more network nodes.

24. The method of claim 21, wherein the configuration information indicates a single TAG for the single component carrier based at least in part on the plurality of CORESET pool indexes being associated with propagation times that differ by an amount satisfying a threshold.

25. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: Receive configuration information, the configuration information indicating: a first configuration of a plurality of control resource set (CORESET) pool indices for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of timing advance groups (TAGs) for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs; as well as Based at least in part on the first set of a plurality of TAGs and the second set of one or more TAGs, One or more communications are sent via the first component carrier and the second component carrier.

26. The UE of claim 25, wherein the second set of one or more TAGs is configured with the same number of TAGs as the first set of multiple TAGs.

27. The UE of claim 25, wherein the second set of one or more TAGs is configured with multiple TAGs based at least in part on the first set of multiple TAGs being configured with multiple TAGs.

28. The UE of claim 25, wherein the second set of one or more TAGs is configured based at least in part on the first set of multiple TAGs, the first set of multiple TAGs being based at least in part on: The first component carrier is configured with a plurality of CORESET pool indexes, and The second component carrier is configured with a plurality of CORESET pool indexes.

29. The UE of claim 25, wherein the second component carrier is capable of being configured with a plurality of CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with a plurality of TAGs.

30. The UE of claim 25, wherein the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

31. The UE of claim 30, wherein the sending of the one or more communications via the first component carrier and the second component carrier comprises: The one or more communications are sent using inter-band carrier aggregation via the first component carrier and the second component carrier.

32. The UE of claim 25, wherein the one or more processors are further configured to: receiving configuration information indicating whether the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

33. A UE for wireless communication, the UE comprising: Memory; and one or more processors coupled to the memory and configured to: sending an indication of a capability to communicate using multiple timing advances (TAs) for a single component carrier; as well as Receive configuration information, the configuration information indicating: a plurality of control resource set (CORESET) pool indices for communications within the single component carrier, and One or more timing advance groups (TAGs) for the single component carrier based at least in part on the capabilities.

34. The UE of claim 33, wherein the configuration information indicates multiple TAGs for the single component carrier based at least in part on the capability supporting multiple TAGs for the single component carrier.

35. The UE of claim 34, wherein the configuration information further indicates multiple TAGs for the single component carrier based in part on the multiple CORESET pool indexes being associated with different propagation times to one or more network nodes.

36. The UE of claim 33, wherein the configuration information indicates a single TAG for the single component carrier based at least in part on the plurality of CORESET pool indexes being associated with propagation times that differ by an amount satisfying a threshold.

37. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to: Send configuration information, the configuration information indicating: a first configuration of a plurality of control resource set (CORESET) pool indices for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of timing advance groups (TAGs) for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs; as well as One or more communications are received via the first component carrier and the second component carrier based at least in part on the first set of a plurality of TAGs and the second set of one or more TAGs.

38. The network node of claim 37, wherein the second set of one or more TAGs is configured with the same number of TAGs as the first set of multiple TAGs.

39. The network node of claim 37, wherein the second set of one or more TAGs is configured with a plurality of TAGs based at least in part on the first set of a plurality of TAGs being configured with a plurality of TAGs.

40. The network node of claim 37, wherein the second set of one or more TAGs is configured based at least in part on the first set of multiple TAGs, the first set of multiple TAGs being based at least in part on: The first component carrier is configured with a plurality of CORESET pool indexes, and The second component carrier is configured with a plurality of CORESET pool indexes.

41. The network node of claim 37, wherein the second component carrier is configurable with a plurality of CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with a plurality of TAGs.

42. The network node of claim 37, wherein the second set of one or more TAGs is configurable with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

43. The network node of claim 42, wherein the receiving of the one or more communications via the first component carrier and the second component carrier comprises: The one or more communications are received via the first component carrier and the second component carrier using inter-band carrier aggregation.

44. The network node of claim 37, wherein the one or more processors are further configured to: Sending configuration information indicating whether the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

45. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to: receiving an indication of an ability to communicate using multiple timing advances (TAs) for a single component carrier; and Send configuration information, the configuration information indicating: a plurality of control resource set (CORESET) pool indices for communications within the single component carrier, and One or more timing advance groups (TAGs) for the single component carrier based at least in part on the capabilities.

46. ​​The network node of claim 45, wherein the configuration information indicates multiple TAGs for the single component carrier based at least in part on the capability supporting multiple TAGs for the single component carrier.

47. The network node of claim 46, wherein the configuration information further indicates multiple TAGs for the single component carrier based in part on the multiple CORESET pool indexes being associated with different propagation times to one or more network nodes.

48. The network node of claim 45, wherein the configuration information indicates a single TAG for the single component carrier based at least in part on the plurality of CORESET pool indexes being associated with propagation times that differ by an amount satisfying a threshold.

49. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: Receive configuration information, the configuration information indicating: a first configuration of a plurality of control resource set (CORESET) pool indices for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of timing advance groups (TAGs) for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs; as well as One or more communications are sent via the first component carrier and the second component carrier based at least in part on the first set of a plurality of TAGs and the second set of one or more TAGs.

50. The non-transitory computer readable medium of claim 49, wherein the second set of one or more TAGs is configured with the same number of TAGs as the first set of multiple TAGs.

51. The non-transitory computer-readable medium of claim 49, wherein the second set of one or more TAGs is configured with a plurality of TAGs based at least in part on the first set of a plurality of TAGs being configured with a plurality of TAGs.

52. The non-transitory computer-readable medium of claim 49, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs, the first set of a plurality of TAGs being based at least in part on: The first component carrier is configured with a plurality of CORESET pool indexes, and The second component carrier is configured with a plurality of CORESET pool indexes.

53. The non-transitory computer-readable medium of claim 49, wherein the second component carrier is capable of being configured with a plurality of CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with a plurality of TAGs.

54. The non-transitory computer-readable medium of claim 49, wherein the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

55. The non-transitory computer readable medium of claim 54, wherein the one or more instructions further cause the UE to: The one or more communications are sent using inter-band carrier aggregation via the first component carrier and the second component carrier.

56. The non-transitory computer readable medium of claim 49, wherein the one or more instructions further cause the UE to: receiving configuration information indicating whether the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

57. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions which, when executed by one or more processors of a UE, cause the UE to: sending an indication of a capability to communicate using multiple timing advances (TAs) for a single component carrier; as well as Receive configuration information, the configuration information indicating: A plurality of control resource set (CORESET) pool indexes for communications within the single component carrier, and one or more timing advance groups (TAGs) for the single component carrier based at least in part on the capabilities.

58. The non-transitory computer-readable medium of claim 57, wherein the configuration information indicates a plurality of TAGs for the single component carrier based at least in part on the capability supporting a plurality of TAGs for the single component carrier.

59. The non-transitory computer-readable medium of claim 58, wherein the configuration information further indicates a plurality of TAGs for the single component carrier based in part on the plurality of CORESET pool indexes being associated with different propagation times to one or more network nodes.

60. The non-transitory computer-readable medium of claim 57, wherein the configuration information indicates a single TAG for the single component carrier based at least in part on the plurality of CORESET pool indexes being associated with propagation times that differ by an amount satisfying a threshold.

61. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a network node, cause the network node to: Send configuration information, the configuration information indicating: a first configuration of a plurality of control resource set (CORESET) pool indices for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of timing advance groups (TAGs) for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs; as well as Based at least in part on the first set of a plurality of TAGs and the second set of one or more TAGs, One or more communications are received via the first component carrier and the second component carrier.

62. The non-transitory computer-readable medium of claim 61, wherein the second set of one or more TAGs is configured with the same number of TAGs as the first set of multiple TAGs.

63. The non-transitory computer-readable medium of claim 61, wherein the second set of one or more TAGs is configured with a plurality of TAGs based at least in part on the first set of a plurality of TAGs being configured with a plurality of TAGs.

64. The non-transitory computer-readable medium of claim 61, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs, the first set of a plurality of TAGs being based at least in part on: The first component carrier is configured with a plurality of CORESET pool indexes, and The second component carrier is configured with a plurality of CORESET pool indexes.

65. The non-transitory computer-readable medium of claim 61, wherein the second component carrier is capable of being configured with a plurality of CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with a plurality of TAGs.

66. The non-transitory computer-readable medium of claim 61, wherein the second set of one or more TAGs is configurable with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

67. The non-transitory computer readable medium of claim 66, wherein the one or more instructions further cause the network node to: The one or more communications are received via the first component carrier and the second component carrier using inter-band carrier aggregation.

68. The non-transitory computer readable medium of claim 61, wherein the one or more instructions further cause the network node to: Sending configuration information indicating whether the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

69. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a network node, cause the network node to: receiving an indication of an ability to communicate using multiple timing advances (TAs) for a single component carrier; and Send configuration information, the configuration information indicating: a plurality of control resource set (CORESET) pool indices for communications within the single component carrier, and One or more timing advance groups (TAGs) for the single component carrier based at least in part on the capabilities.

70. The non-transitory computer-readable medium of claim 69, wherein the configuration information indicates a plurality of TAGs for the single component carrier based at least in part on the capability supporting multiple TAGs for the single component carrier.

71. The non-transitory computer-readable medium of claim 70, wherein the configuration information further indicates a plurality of TAGs for the single component carrier based in part on the plurality of CORESET pool indexes being associated with different propagation times to one or more network nodes.

72. The non-transitory computer-readable medium of claim 69, wherein the configuration information indicates a single TAG for the single component carrier based at least in part on the plurality of CORESET pool indexes being associated with propagation times that differ by an amount satisfying a threshold.

73. An apparatus for wireless communication, the apparatus comprising: A component for receiving configuration information, the configuration information indicating: a first configuration of a plurality of control resource set (CORESET) pool indices for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of timing advance groups (TAGs) for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs; as well as Means for transmitting one or more communications via the first component carrier and the second component carrier based at least in part on the first set of a plurality of TAGs and the second set of one or more TAGs.

74. The apparatus of claim 73, wherein the second set of one or more TAGs is configured with the same number of TAGs as the first set of multiple TAGs.

75. The apparatus of claim 73, wherein the second set of one or more TAGs is configured with multiple TAGs based at least in part on the first set of multiple TAGs being configured with multiple TAGs.

76. The apparatus of claim 73, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs, the first set of a plurality of TAGs being based at least in part on: The first component carrier is configured with a plurality of CORESET pool indexes, and The second component carrier is configured with a plurality of CORESET pool indexes.

77. The apparatus of claim 73, wherein the second component carrier is capable of being configured with a plurality of CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with a plurality of TAGs.

78. The apparatus of claim 73, wherein the second set of one or more TAGs is configurable with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

79. The apparatus of claim 78, further comprising: Means for transmitting the one or more communications via the first component carrier and the second component carrier using inter-band carrier aggregation.

80. The apparatus of claim 73, further comprising: Means for receiving configuration information indicating whether the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

81. An apparatus for wireless communication, the apparatus comprising: means for sending an indication of an ability to communicate using multiple timing advances (TAs) for a single component carrier; as well as A component for receiving configuration information, the configuration information indicating: a plurality of control resource set (CORESET) pool indices for communications within the single component carrier, and One or more timing advance groups (TAGs) for the single component carrier based at least in part on the capabilities.

82. The apparatus of claim 81, wherein the configuration information indicates multiple TAGs for the single component carrier based at least in part on the capability supporting multiple TAGs for the single component carrier.

83. The apparatus of claim 82, wherein the configuration information further indicates multiple TAGs for the single component carrier based in part on the multiple CORESET pool indexes being associated with different propagation times to one or more network nodes.

84. The apparatus of claim 81, wherein the configuration information indicates a single TAG for the single component carrier based at least in part on the plurality of CORESET pool indexes being associated with propagation times that differ by an amount satisfying a threshold.

85. An apparatus for wireless communication, the apparatus comprising: A component for sending configuration information, wherein the configuration information indicates: a first configuration of a plurality of control resource set (CORESET) pool indices for a first component carrier and for a second component carrier, and a second configuration of a first set of a plurality of timing advance groups (TAGs) for the first component carrier and a second set of one or more TAGs for the second component carrier, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs; as well as Means for receiving one or more communications via the first component carrier and the second component carrier based at least in part on the first set of a plurality of TAGs and the second set of one or more TAGs.

86. The apparatus of claim 85, wherein the second set of one or more TAGs is configured with the same number of TAGs as the first set of multiple TAGs.

87. The apparatus of claim 85, wherein the second set of one or more TAGs is configured with multiple TAGs based at least in part on the first set of multiple TAGs being configured with multiple TAGs.

88. The apparatus of claim 85, wherein the second set of one or more TAGs is configured based at least in part on the first set of a plurality of TAGs, the first set of a plurality of TAGs being based at least in part on: The first component carrier is configured with a plurality of CORESET pool indexes, and The second component carrier is configured with a plurality of CORESET pool indexes.

89. The apparatus of claim 85, wherein the second component carrier is capable of being configured with a plurality of CORESET pool indexes based at least in part on the second set of one or more TAGs being configured with a plurality of TAGs.

90. The apparatus of claim 85, wherein the second set of one or more TAGs is configurable with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

91. The apparatus of claim 90, further comprising: Means for receiving the one or more communications using inter-band carrier aggregation via the first component carrier and the second component carrier.

92. The apparatus of claim 85, further comprising: Means for sending configuration information indicating whether the second set of one or more TAGs can be configured with a single TAG based at least in part on one or more of: The single TAG in the second set of one or more TAGs is a different TAG from each TAG in the first set of multiple TAGs, or The first component carrier and the second component carrier are in different frequency bands.

93. An apparatus for wireless communication, the apparatus comprising: means for receiving an indication of an ability to communicate using multiple timing advances (TAs) for a single component carrier; and A component for sending configuration information, wherein the configuration information indicates: a plurality of control resource set (CORESET) pool indices for communications within the single component carrier, and One or more timing advance groups (TAGs) for the single component carrier based at least in part on the capabilities.

94. The apparatus of claim 93, wherein the configuration information indicates multiple TAGs for the single component carrier based at least in part on the capability supporting multiple TAGs for the single component carrier.

95. The apparatus of claim 94, wherein the configuration information further indicates multiple TAGs for the single component carrier based in part on the multiple CORESET pool indexes being associated with different propagation times to one or more network nodes.

96. The apparatus of claim 93, wherein the configuration information indicates a single TAG for the single component carrier based at least in part on the plurality of CORESET pool indexes being associated with propagation times that differ by an amount satisfying a threshold.