Timing Advance Offset Configuration

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive information scheduling uplink resources on a carrier associated with multiple timing advance groups and associated with one or more timing advance offsets for the multiple timing advance groups. The UE may transmit on the carrier according to the one or more timing advance offsets using the uplink resources. Numerous other aspects are described.

Description

[Technical field]

[0001] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for timing advance offset configuration. [Background technology]

[0002] Wireless communication systems have been widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting 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 extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

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

[0004] The above multiple access technologies have been adopted in various telecommunications standards to provide common protocols that allow different UEs to communicate on a city, national, regional, and / or global scale. 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 support mobile broadband Internet access through improved spectral efficiency, reduced costs, improved services, utilization of new spectrum, and better integration with other open standards through the use of orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, 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 support for beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies will still be useful. Summary of the Invention

[0005] Certain aspects described herein relate to a method of wireless communication implemented by a UE. The method may include receiving information scheduling uplink resources on a carrier associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups. The method may include transmitting on the carrier using the uplink resources according to the one or more timing advance offsets.

[0006] Certain aspects described herein relate to a method of wireless communication implemented by a UE. The method may include receiving information identifying a single timing advance offset common to a plurality of carriers. The method may include transmitting a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on a plurality of carriers associated with a plurality of timing advance groups based at least in part on the single timing advance offset.

[0007] Certain aspects described herein relate to a method of wireless communication implemented by a network entity. The method may include transmitting information scheduling uplink resources on a carrier associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups. The method may include receiving on the carrier according to the one or more timing advance offsets using the uplink resources.

[0008] Certain aspects described herein relate to a method of wireless communication implemented by a network entity. The method may include transmitting information identifying a single timing advance offset common to a plurality of carriers. The method may include receiving, on a plurality of carriers associated with a plurality of timing advance groups, a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index based at least in part on the single timing advance offset.

[0009] 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 receive information scheduling uplink resources on a carrier associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups. The one or more processors may be configured to transmit on the carrier according to the one or more timing advance offsets using the uplink resources.

[0010] 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 receive information identifying a single timing advance offset common to a plurality of carriers. The one or more processors may be configured to transmit a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on a plurality of carriers associated with a plurality of timing advance groups based at least in part on the single timing advance offset.

[0011] Some aspects described herein relate to a network entity for wireless communications. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit information scheduling uplink resources on carriers associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups. The one or more processors may be configured to receive on the carriers according to the one or more timing advance offsets using the uplink resources.

[0012] Some aspects described herein relate to a network entity for wireless communications. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit information identifying a single timing advance offset common to a plurality of carriers. The one or more processors may be configured to receive, on a plurality of carriers associated with a plurality of timing advance groups, a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index based at least in part on the single timing advance offset.

[0013] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive information scheduling uplink resources on a carrier associated with multiple timing advance groups and associated with one or more timing advance offsets for the multiple timing advance groups. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to transmit on the carrier using the uplink resources in accordance with the one or more timing advance offsets.

[0014] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive information identifying a single timing advance offset common to multiple carriers. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to transmit a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on multiple carriers associated with multiple timing advance groups based at least in part on the single timing advance offset.

[0015] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to transmit information scheduling uplink resources on a carrier associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups. The set of instructions, when executed by the one or more processors of the network entity, may cause the network entity to receive on the carrier using the uplink resources according to the one or more timing advance offsets.

[0016] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to transmit information identifying a single timing advance offset common to a plurality of carriers. The set of instructions, when executed by the one or more processors of the network entity, may cause the network entity to receive, on a plurality of carriers associated with a plurality of timing advance groups, a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index based at least in part on the single timing advance offset.

[0017] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving information scheduling uplink resources on a carrier associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups. The apparatus may include means for transmitting on the carrier according to the one or more timing advance offsets using the uplink resources.

[0018] Certain aspects described herein relate to an apparatus for wireless communications. The apparatus may include means for receiving information identifying a single timing advance offset common to a plurality of carriers. The apparatus may include means for transmitting a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on a plurality of carriers associated with a plurality of timing advance groups based at least in part on the single timing advance offset.

[0019] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting information scheduling uplink resources on a carrier associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups. The apparatus may include means for receiving on the carrier according to the one or more timing advance offsets using the uplink resources.

[0020] Certain aspects described herein relate to an apparatus for wireless communications. The apparatus may include means for transmitting information identifying a single timing advance offset common to a plurality of carriers. The apparatus may include means for receiving, on a plurality of carriers associated with a plurality of timing advance groups, a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index based at least in part on the single timing advance offset.

[0021] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems substantially as described herein with reference to and as illustrated by the drawings and specification.

[0022] The foregoing has outlined rather broadly the features and technical advantages of examples according to the present disclosure in order that the following Detailed Description may be better understood. Additional features and advantages are set forth below. The concept and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics and associated advantages of both the organization of the concepts and the methods of operation disclosed herein will be better understood when the following description is considered in conjunction with the accompanying figures. Each of the figures is provided for the purpose of illustration and explanation, and not as a definition of the limits of the claims.

[0023] Although aspects are described in this disclosure by illustrating some examples, those skilled in the art will understand that such aspects can be implemented in many different configurations and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects may be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital applications (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is contemplated that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and configurations.

[0024] So that the above-enumerated features of the present disclosure can be understood in detail, a more detailed description, briefly summarized above, may be had by referring to the embodiments, some of which are shown in the attached drawings. It should be noted, however, that the attached drawings show only certain exemplary embodiments of the disclosure, and therefore should not be considered as limiting the scope of the disclosure, since the description may be given to other equally effective embodiments. The same reference symbols in different drawings may identify the same or similar elements. [Brief description of the drawings]

[0025] [Figure 1] FIG. 1 illustrates an example of a wireless network in accordance with the present disclosure. [Diagram 2] FIG. 1 illustrates an example of a base station in communication with a user equipment (UE) in a wireless network in accordance with the present disclosure. [Diagram 3] FIG. 1 illustrates an example of a non-aggregated base station architecture in accordance with the present disclosure. [Figure 4] FIG. 1 illustrates an example of multiple transmit receive point (multi-TRP) communication in accordance with the present disclosure. [Diagram 5] FIG. 1 illustrates an example associated with a timing advance offset configuration in accordance with the present disclosure. [Figure 6] FIG. 1 illustrates an example associated with a timing advance offset configuration in accordance with the present disclosure. [Figure 7] FIG. 1 illustrates an example process associated with a timing advance offset configuration in accordance with the present disclosure. [Figure 8] FIG. 1 illustrates an example process associated with a timing advance offset configuration in accordance with the present disclosure. [Figure 9] FIG. 1 illustrates an example process associated with a timing advance offset configuration in accordance with the present disclosure. [Figure 10] FIG. 1 illustrates an example process associated with a timing advance offset configuration in accordance with the present disclosure. [Figure 11] FIG. 1 is an illustration of an exemplary apparatus for wireless communication in accordance with the present disclosure. [Figure 12] FIG. 1 is an illustration of an exemplary apparatus for wireless communication in accordance with the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0026] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Those skilled in the art should understand that the scope of the disclosure herein is intended to encompass any aspect of the disclosure herein, regardless of whether it is implemented independently or in combination with any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects described herein. It is intended that the scope of the disclosure herein encompasses an apparatus or method that is implemented using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure described herein. It should be understood that any aspect of the disclosure herein can be embodied by one or more elements of a claim.

[0027] Several aspects of a telecommunications system will now be illustrated with reference to various apparatus and techniques, which are described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0028] Although aspects may be described herein using terminology commonly associated with 5G or New Radio (NR) radio access technology (RAT), aspects of the disclosure may be applicable to other RATs, such as 3G RATs, 4G RATs, and / or 5G and beyond RATs (e.g., 6G).

[0029] 1 illustrates an example of a wireless network 100 in accordance with the present disclosure. Wireless network 100 may be or include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. Wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. Base station 110 is an entity that communicates with UE 120. The base stations 110 (which may be referred to as BSs) may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, and / or transmission reception points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving this coverage area, depending on the context in which the term is used.

[0030] A 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 few kilometers in radius) and may allow unrestricted access by UEs 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 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 UEs 120 with an association with a femto cell (e.g., UEs 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. 1, BS 110a may be a macro base station for a macro cell 102a, BS 110b may be a pico base station for a pico cell 102b, and BS 110c may be a femto base station for a femto cell 102c. A base station may support one or multiple (e.g., three) cells.

[0031] In some examples, the cells may not necessarily be fixed, and the geographic area of ​​the cells may move according to the location of the base stations 110 that are mobile (e.g., mobile base stations). In some examples, the base stations 110 may interconnect with each other and / or with 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.

[0032] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit the transmission of the data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that can relay a transmission of another UE 120. In the example shown in FIG. 1, a BS 110d (e.g., a relay base station) may communicate with a BS 110a (e.g., a macro base station) and a UE 120d to facilitate communication between the BS 110a (e.g., a macro base station) and the UE 120d. A base station 110 that relays communication may be referred to as a relay station, a relay base station, a repeater, etc.

[0033] Wireless network 100 may be a heterogeneous network including 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 susceptibility to interference within wireless network 100. For example, macro base stations may have high transmit power levels (e.g., 5-40 Watts), while pico, femto, and relay base stations may have lower transmit power levels (e.g., 0.1-2 Watts).

[0034] A network controller 130 may couple to or communicate with a set of base stations 110 and provide coordination and control for these base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may communicate with each other directly or indirectly via wireless backhaul communication links or wireline backhaul communication links.

[0035] The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be fixed or mobile. The UEs 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. The UEs 120 may be a cellular telephone (e.g., a smartphone), 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, 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), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate over a wireless medium.

[0036] Some UEs 120 may be considered as machine-type communication (MTC) UEs or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and / or a location tag 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. The UE 120 may be included within a housing that houses components of the 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., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

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

[0039] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, etc. 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 range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that FR1 is often referred to (interchangeably) as a "sub-6 GHz" band in various documents and papers, although a portion of FR1 is higher than 6 GHz. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as a "millimeter wave" band in documents and papers, even though FR2 is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as a "millimeter wave" band by the International Telecommunications Union (ITU).

[0040] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 and / or FR2 characteristics, and thus, in effect, extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0041] With the above examples in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specified, it should be understood that terms such as "millimeter wave" as used herein may broadly refer to frequencies that may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, may include mid-band frequencies, or may be within the EHF band. Frequencies that fall within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be subject to modifications, and it is contemplated that the techniques described herein are applicable to those modified frequency ranges.

[0042] In some aspects, the UE 120 may include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 may receive information scheduling uplink resources on carriers associated with multiple timing advance groups and associated with one or more timing advance offsets for the multiple timing advance groups, and transmit on the carriers using the uplink resources according to the one or more timing advance offsets. The communications manager 140 may identify or receive information about a single timing advance offset common to the multiple carriers, and transmit a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on the multiple carriers associated with the multiple timing advance groups based at least in part on the single timing advance offset. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0043] In some aspects, a network entity (e.g., base station 110) may include a communications manager 150. As detailed elsewhere herein, the communications manager 150 may transmit information scheduling uplink resources on carriers associated with multiple timing advance groups and associated with one or more timing advance offsets for the multiple timing advance groups, and may use the uplink resources to receive on the carriers according to the one or more timing advance offsets. The communications manager 150 may identify or transmit information about a single timing advance offset common to the multiple carriers, and receive a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index based at least in part on the single timing advance offset on the multiple carriers associated with the multiple timing advance groups. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0044] As noted above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0045] 2 illustrates an example base station 200 in communication with a UE 120 in a wireless network 100 in accordance with the present disclosure. The base station 110 may be equipped with a set of antennas 234a-t, such as T antennas, where T≧1. The UE 120 may be equipped with a set of antennas 252a-r, such as R antennas, where R≧1.

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

[0047] At the UE 120, a set of antennas 252 (depicted as antennas 252a through 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), depicted as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (depicted as DEMOD) of the modems 254. Each modem 254 may use a separate 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 modems 254, perform MIMO detection on the received symbols if applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control 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 examples. In some examples, one or more components of the UE 120 may be included within a housing 284.

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

[0049] One or more antennas (e.g., antennas 234a-t and / or antennas 252a-r) may include or be contained 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, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more components of FIG.

[0050] 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 precoded by a TX MIMO processor 266, if 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 the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and / or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to implement aspects of any of the methods described herein (e.g., with reference to Figures 5-12).

[0051] 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, denoted as DEMOD), detected by a MIMO detector 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information to be transmitted by the UE 120. The receive processor 238 may provide the decoded data to a 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 for scheduling 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(s) 234, modem(s) 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 implement aspects of any of the methods described herein (e.g., with reference to FIGS. 5-12).

[0052] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component(s) of FIG. 2 may implement one or more techniques associated with timing advance offset configuration, as detailed elsewhere herein. In some aspects, a network entity or transmission / reception point (TRP) described herein is the base station 110, is included within the base station 110, or includes one or more components of the base station 110 shown in FIG. 2. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component(s) of FIG. 2 may implement or direct operations of, for example, process 700 of FIG. 7, process 800 of FIG. 8, process 900 of FIG. 9, process 1000 of FIG. 10, and / or other processes described herein. The memory 242 and the memory 282 may store data and program codes for the base station 110 and the 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, the one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly or after being compiled, translated, and / or interpreted), may cause the one or more processors, UE 120, and / or base station 110 to perform or direct operations of, for example, process 700 of FIG. 7, process 800 of FIG. 8, process 900 of FIG. 9, process 1000 of FIG. 10, and / or other processes described herein. In some examples, executing instructions may include executing instructions, translating instructions, compiling instructions, and / or interpreting instructions, among other examples.

[0053] In some aspects, the UE 120 includes means for receiving information scheduling uplink resources on carriers associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups, and / or means for transmitting on the carriers according to the one or more timing advance offsets using the uplink resources. In some aspects, the UE 120 includes means for identifying or receiving information about a single timing advance offset common to the plurality of carriers, and / or means for transmitting a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index based at least in part on the single timing advance offset on the plurality of carriers associated with the plurality of timing advance groups. The means for 120 to perform the operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0054] In some aspects, a network entity (e.g., base station 110) includes means for transmitting information scheduling uplink resources on carriers associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups, and / or means for receiving on the carriers according to the one or more timing advance offsets using the uplink resources. In some aspects, the network entity includes means for transmitting information identifying a single timing advance offset common to the plurality of carriers, and / or means for receiving a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on a plurality of carriers associated with the plurality of timing advance groups based at least in part on the single timing advance offset. In some aspects, the means for a network entity to perform the operations described herein may include, for example, one or more of the communications 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.

[0055] 2 are shown as separate components, the functionality described above with respect to the blocks may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, functionality described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be implemented by or under the control of controller / processor 280.

[0056] As noted above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.

[0057] FIG. 3 illustrates a diagram illustrating an example unaggregated base station 300 architecture. The unaggregated base station 300 architecture may include one or more CUs 310 that may communicate directly with the core network 320 via a backhaul link or indirectly with the core network 320 through one or more unaggregated base station units (such as a Near-Real Time (RT), Near-RT, RAN Intelligent Controller (RIC) 325 via an E2 link, or a Non-Real Time (Non-RT) RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CUs 310 may communicate with one or more DUs 330 via respective midhaul links, such as an F1 interface. The DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. The RUs 340 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, the UE 120 may be served simultaneously by multiple RUs 340. In some implementations, the UE 120 may include a communications manager 396 (e.g., communications manager 140) that may enable the UE 120 to communicate with other units (e.g., network entities such as the CU 310, DU 330, or RU 340, among other examples). One or more of the units, such as the RU 340, may have a communications manager 398 (e.g., communications manager 150) that may enable the unit to communicate with the UE 120.

[0058] Each of the units, i.e., CU310, DU330, RU340, and quasi-RT RIC325, non-RT RIC315, and SMO framework 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. In addition, a unit may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive or transmit signals to or transmit and receive signals to one or more of the other units over a wireless transmission medium.

[0059] In some aspects, the 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), or service data adaptation protocol (SDAP), among other examples. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (Central Unit-User Plane (CU-UP)), control plane functionality (Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface, when implemented in an O-RAN configuration. The CU 310 may be implemented to communicate with the DU 330, as necessary, for network control and signaling.

[0060] The DU 330 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, or modulation and demodulation, among other examples), at least in part according to a functional division such as that defined by 3GPP. In some aspects, the DU 330 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with a control function hosted by the CU 310.

[0061] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, the RUs 340 controlled by the DUs 330 may correspond to logical nodes hosting RF processing functions, or lower PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc., among other examples), or both, based at least in part on a functional division such as a lower layer functional division. In such an architecture, the RU(s) 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(s) 340 may be controlled by the corresponding DUs 330. In some scenarios, this configuration may enable the DU(s) 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0062] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support deployment of dedicated physical resources corresponding to RAN coverage requirements that can 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) 390) 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, the CU 310, the DU 330, the RU 340, and the quasi-RT RIC 325. In some implementations, the SMO framework 305 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via an O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0063] 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 updates, or policy-based guidance of applications / features in the quasi-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the quasi-RT RIC 325 (e.g., via an A1 interface). The quasi-RT RIC 325 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources through data collection and action on one or more CUs 310, one or more DUs 330, or both, and interfaces connecting the O-eNB to the quasi-RT RIC 325 (e.g., via an E2 interface).

[0064] In some implementations, the non-RT RIC 315 may receive parameters or external enrichment information from an external server to generate AI / ML models to be deployed to the quasi-RT RIC 325. Such information may be utilized by the quasi-RT RIC 325 or may be received at the SMO framework 305 or the non-RT RIC 315 from non-network data sources or from network functions. In some examples, the non-RT RIC 315 or the quasi-RT RIC 325 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 315 may employ AI / ML models to monitor long-term trends and patterns in performance and implement corrective actions through the SMO framework 305 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policies).

[0065] As noted above, Figure 3 is provided as an example. Other examples may differ from those described with respect to Figure 3.

[0066] 4 is a diagram illustrating an example 400 of multi-TRP communication (sometimes referred to as multi-panel communication) according to the present disclosure. As shown in FIG. 4, multiple TRPs 405 may communicate with the same UE 120. The TRPs 405 may correspond to one or more of the CU 310, DU 330, or RU 340, among other examples described above in connection with FIG. 3.

[0067] Multiple TRPs 405 (depicted as TRP A and TRP B) may communicate with the same UE 120 in a coordinated manner (e.g., using coordinated multipoint transmission) to improve reliability, improve coverage, and / or increase throughput to a serving cell. The TRPs 405 may coordinate such communications over an interface (e.g., a backhaul interface and / or an access node controller) between the TRPs 405. The interface may have lower latency and / or higher capacity when the TRPs 405 are collocated at the same base station 110 (e.g., when the TRPs 405 are different antenna arrays or panels of the same base station 110) and may have higher latency and / or lower capacity (compared to collocation) when the TRPs 405 are located at different base stations 110. Different TRPs 405 may communicate with UE 120 using different quasi-co-location (QCL) relationships (e.g., different transmission configuration indicator (TCI) states), different demodulation reference signal (DMRS) ports, and / or different layers (e.g., of a multi-layer communication).

[0068] In a first multi-TRP transmission mode (e.g., mode 1), a single physical downlink control channel (PDCCH) may be used to schedule uplink data communications for physical uplink shared channel (PUSCH) transmissions to multiple TRPs 405. In this case, multiple TRPs 405 (e.g., TRP A and TRP B) may receive PUSCH communications from the UE 120 using resources scheduled by a single downlink control information (DCI) message carried using a single PDCCH. For example, a PUSCH communication may be transmitted using a single codeword (e.g., one codeword is mapped to a first set of layers transmitted to a first TRP 405 and to a second set of layers transmitted to a second TRP 405) with different spatial layers for the different TRPs 405. As another example, a PUSCH communication may be transmitted using multiple codewords, where different codewords are transmitted to different TRPs 405 (e.g., using different sets of layers). In either case, different TRPs 405 and UEs 120 may use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, UEs 120 and a first TRP 405 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 UEs 120 and a second TRP 405 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, a TCI state in a DCI (e.g., DCI format 1_0 or DCI format 1_1 transmitted on a PDCCH, etc.) 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 and second TCI states may be indicated using a TCI field in the DCI.In general, the TCI field may indicate a single TCI state (for single-TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed herein) in this multi-TRP transmission mode (eg, mode 1).

[0069] In a second multi-TRP transmission mode (e.g., mode 2), multiple PDCCHs may be used to schedule respective uplink data communications for multiple corresponding PUSCHs (e.g., one PDCCH for each PDSCH). In this case, a first PDCCH may schedule a first codeword to be transmitted to a first TRP 405, and a second PDCCH may schedule a second codeword to be transmitted to a second TRP 405. Furthermore, a first DCI (e.g., transmitted by a first TRP 405) may schedule a first PUSCH communication associated with a first set of DMRS ports having a first QCL relationship (e.g., indicated by a first TCI state) for the first TRP 405, and a second DCI (e.g., transmitted by a second TRP 405) may schedule a second PUSCH communication associated with a second set of DMRS ports having a second QCL relationship (e.g., indicated by a second TCI state) for the second TRP 405. In this case, a DCI (e.g., having DCI format 1_0 or DCI format 1_1) may indicate a corresponding TCI state for the TRP 405 corresponding to the DCI. The TCI field of the DCI indicates the corresponding TCI state (e.g., 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). If two control resource set (CORESET) Pool Index (CORESETPoolIndex) values ​​are configured for a CORESET of a bandwidth part (BWP) within a carrier, a second multi-TRP transmission mode may be configured for a BWP within a carrier (also referred to as a "component carrier" or "CC"). If a CORESETPoolIndex value is not provided for a CORESET within a BWP within a carrier, the UE 120 may be configured to use a default value.

[0070] As noted above, Figure 4 is provided as an example. Other examples may differ from those described with respect to Figure 4.

[0071] Each serving cell providing connectivity to one or more UEs may be associated with a single timing advance group (TAG), which may correspond to a timing advance (TA) value that the serving cell (e.g., a network entity such as a TRP) and the UE may use to determine the timing of one or more communications. The serving cell may send a TA command to indicate an adjustment to the TA value that the serving cell and the UE are using. Further details regarding the TA command are described with respect to 3GPP Technical Specification (TS) 38.321, Release 16, Version 16.7.0. Each serving cell may be associated with a timing advance offset, which may indicate an amount of offset to apply to the timing advance value for the serving cell relative to the timing advance value of one or more other serving cells. The network entity may indicate the timing advance offset value by sending an n-TimingAdvanceOffset information element (IE). When the UE is not provided with an explicit indication of the timing advance offset value, the UE may be configured to use a default value for the timing advance offset value. Further details regarding timing advance offset values ​​are described in 3GPP TS 38.133, Release 17, Version 17.4.0.

[0072] A network entity may configure a single TAG identifier (TAG-ID) for each serving cell for a UE. In this case, a first timing advance value for transmission to a first TRP may be based at least in part on an indication in a TA command received by the UE, and a second timing advance value for transmission to a second TRP may be based at least in part on a timing advance offset applied to the first timing advance value for the first TRP. However, when a UE is configured to communicate on multiple uplink carriers, transmitting information identifying multiple TA commands and multiple timing advance offset values ​​may result in over-utilization of network resources.

[0073] Thus, some aspects described herein may enable a UE to apply a common timing advance offset value across multiple carriers associated with multiple TAGs, for example. For example, the UE may apply the same timing advance offset value within a group of carriers even when a first carrier has a different TAG identifier than a second carrier. In this manner, the UE enables reduced signaling for carriers associated with a single TAG. Additionally or alternatively, the UE may apply a common timing advance offset value across multiple carriers associated with the same TAG. For example, the UE may apply the same timing advance offset value within two carriers of a group of carriers having a common TAG ID, but a different timing advance offset value within a third carrier of a group of carriers having a different TAG ID.

[0074] When a UE is configured with two uplink carriers for one serving cell, the same timing advance offset value may be applied to both uplink carriers. Similarly, when there are multiple uplink carriers in the same TAG, the UE may be configured to assume the same value of n-TimingAdvanceOffset for each of the multiple uplink carriers. In some cases, in the case of a multi-DCI, multi-TRP deployment, a single serving cell may be configured with two TAGs. As an example, a first carrier (first carrier, C1) may be configured with a first TAG (first TAG, TAG1) and a first timing advance offset (n-TimingAdvanceOffset1), a second carrier (second carrier, C2) may be configured with a second TAG (second TAG, TAG2) and a second timing advance offset (n-TimingAdvanceOffset2), and a third carrier may be configured with two TAGs (e.g., TAG1 and TAG2). In this case, the UE may not have information to configure one or more timing advance offset values ​​for the third carrier with two TAGs, which may result in a lack of flexibility in multi-DCI, multi-TRP deployments and / or a lack of synchronization between communications.

[0075] Some aspects described herein enable timing advance offset configuration. For example, a timing advance offset value may be configured per carrier. Additionally or alternatively, a timing advance offset value may be configured across carriers such that a timing advance offset value is configured per TAG. Additionally or alternatively, a timing advance offset value may be configured differently for each TAG within each carrier such that common TAGs are constrained to have the same value configured. In this manner, a UE may determine a timing advance offset value that enables the UE to determine timing for communications in a multi-DCI, multi-TRP deployment.

[0076] 5 is a diagram illustrating an example 500 associated with a timing advance offset configuration according to the present disclosure. As shown in FIG. 5, network entities 505 (e.g., TRP 405, RU 340, DU 330, CU 310, base station 110, among other examples) and UE 120 may communicate with each other.

[0077] As indicated by reference numeral 510, UE 120 may receive timing advance configuration information. For example, UE 120 may receive information identifying one or more timing advance offset values ​​for one or more carriers. In this case, UE 120 may receive information identifying one or more timing advance offset values ​​in static signaling (e.g., radio resource control (RRC) signaling) or dynamic signaling (e.g., DCI signaling or medium access control (MAC) control element (CE) signaling).

[0078] In some aspects, UE 120 may receive information identifying one or more timing advance offset values ​​configured per carrier (e.g., three timing advance offset values ​​for three carriers as shown). For example, as indicated by reference numeral 550-1, UE 120 may receive information identifying a first timing advance offset (n-TimingAdvanceOffset 1) for a first TAG (TAG1) configured for a first carrier, a second timing advance offset (n-TimingAdvanceOffset 2) for a second TAG (TAG2) configured for a second carrier, and a third timing advance offset (n-TimingAdvanceOffset 3) for the first and second TAGs configured for a third carrier. In this case, based at least in part on at least one carrier being configured with two TAGs and a timing advance offset, the network entity 505 configures the UE 120 with the same value for the timing advance offset in any other carrier having either of the two TAGs. In other words, the network entity 505 configures n-TimingAdvanceOffset 3, n-TimingAdvanceOffset 2, and n-TimingAdvanceOffset 1 to have a common timing advance offset value, but transmits three different timing advance offset IEs to identify the common timing advance offset value for the three different carriers. Additionally or alternatively, the network entity 505 may transmit a single timing advance offset IE to identify the common timing advance offset value for the three carriers.

[0079] In some aspects, UE 120 may receive information identifying one or more timing advance offset values ​​configured per carrier. Additionally or alternatively, for a serving cell configured with two control resource set pool index values ​​and two TAGs, the UE may be configured with two timing advance offset values, each associated with one TAG. For example, as indicated by reference numeral 550-2, UE 120 may receive information identifying n-TimingAdvanceOffset 1 for TAG1 for a first carrier, n-TimingAdvanceOffset 2 for TAG2 configured for a second carrier, n-TimingAdvanceOffset 3_1 for TAG1 for a third carrier, and n-TimingAdvanceOffset 3_2 for TAG2 for the third carrier. In other words, the network entity 505 provides four different timing advance offset IEs to configure n-TimingAdvanceOffset 1 and n-TimingAdvanceOffset 3_1 to have a first common timing advance offset value for TAG1 on the first carrier and the third carrier, respectively, and to configure n-TimingAdvanceOffset 2 and n-TimingAdvanceOffset 3_2 to have a second common timing advance value for TAG2 on the second carrier and the third carrier, respectively.

[0080] Additionally or alternatively, the network entity 505 may transmit two timing advance offset IEs to identify a first common timing advance offset value and a second common timing advance offset value. For example, as indicated by reference numeral 550-3, the network entity 505 may provide information configuring n-TimingAdvanceOffset 1 for TAG1 across all of the carriers (e.g., of a group of scheduled carriers for the PUSCH) and n-TimingAdvanceOffset 2 for TAG2 across all of the carriers.

[0081] As indicated by reference numeral 520, the UE 120 may transmit using a timing advance value based at least in part on the timing advance configuration information. For example, the UE 120 may transmit on one or more carriers using one or more timing advance offset values ​​received from the network entity 505.

[0082] As noted above, Figure 5 is provided as an example. Other examples may differ from those described with respect to Figure 5.

[0083] 6 is a diagram illustrating an example 600 associated with a timing advance offset configuration according to the present disclosure. As shown in FIG. 6, a network entity 605 (e.g., a network entity 505, a TRP 405, a RU 340, a DU 330, a CU 310, a base station 110, among other examples) and a UE 120 may communicate with each other.

[0084] As indicated by reference numeral 610, UE 120 may receive timing advance configuration information. For example, UE 120 may receive information identifying one or more timing advance offset values ​​for one or more carriers. In this case, UE 120 may receive information identifying one or more timing advance offset values ​​in static signaling (e.g., RRC signaling) or dynamic signaling (e.g., DCI signaling or MAC CE signaling).

[0085] In some implementations, the UE 120 may receive information identifying a timing advance configuration in a particular type of MAC CE. For example, the UE 120 may receive a MAC CE with a field configured to identify a common timing advance command (e.g., a timing advance command applicable across multiple carriers and / or multiple TAGs). In this case, the MAC CE may include six bits to identify a common timing advance offset value and two reserved bits in the same octet. For example, a single MAC CE may carry a timing advance command that includes a first octet with two bits to identify the TAG ID of the timing advance command and six bits to identify the value of the timing advance command, and a second octet with two reserved bits and six bits to identify the common timing advance offset value. In this case, UE 120 may apply a timing advance command to the identified TAG and may apply a timing advance offset value to derive a timing advance command for the identified TAG, as described in more detail below. Alternatively, the first octet may be included in a first MAC CE (e.g., a TA command MAC CE) and the second octet may be included in a second MAC CE (e.g., a timing advance offset MAC CE). In this case, the second MAC CE includes two bits to identify a TAG ID to which a common timing advance offset may be applied.

[0086] In some implementations, the UE 120 may receive information identifying a common timing advance offset to apply across TAGs. For example, as indicated by reference numeral 650-1, the UE 120 may receive from the network entity 605 a timing advance offset value δ that the UE 120 may apply in a first carrier having a first TAG ID, a second carrier having a second TAG ID, and a third carrier having a first TAG ID. In this case, for example, in the first carrier having the first TAG ID, a first transmission to a first TRP may be a timing advance offset value δ that corresponds to the start of the corresponding downlink reception. TA1 = 2 × T1 = 2T, where T TA1 is the timing advance applied to the transmission to the first TRP, and the second transmission to the second TRP is the timing advance of the start of the corresponding downlink reception with an additional timing advance offset relative to the timing advance for the first TRP in the first carrier. TA2 =2×T2=2×(T+δ)=T TA1 +2δ, where 2δ is the timing advance offset value. In this manner, the UE 120 may issue a second timing advance command T TA2 A single timing advance command (T TA1 Similarly, in a second carrier having a second TAG ID, the first transmission may be T TA3 = 2T3, where T3 represents the propagation delay of the transmission to the first TRP, and T TA3 represents a timing advance for the first TRP in the second carrier, and the second transmission is a timing advance offset T of the start of the corresponding downlink reception with an additional timing advance offset relative to the timing advance for the first TRP in the second carrier. TA4 =2×T4=2×(T3+δ)=T TA3+2δ before the start of the corresponding downlink reception. In this way, the UE 120 reuses the timing advance offset value across carriers and TAGs. Furthermore, in the third carrier having the first TAG ID, the UE 120 may TA5 =T TA2 =2(T1+δ) before the second TRP. In this way, the UE 120 reuses the timing advance offset value across carriers and in a common TAG (e.g., the same offset value is used in the first TAG on multiple carriers).

[0087] In some implementations, the UE 120 may receive information identifying a common timing advance offset value that is applicable across carriers but is TAG-specific. For example, the UE 120 may receive a first offset value 2δ1 for a first TAG (e.g., for a first carrier and a third carrier, each having a first TAG ID) and a second offset value 2δ2 for a second TAG (e.g., for a second carrier). In this case, as indicated by reference numeral 650-2, the first timing advance offset value is a common timing advance offset that is applied across multiple carriers (e.g., the first carrier and the third carrier) having the same TAG ID, and the second timing advance offset value is applied across one or more carriers (e.g., the second carrier) having the same TAG ID. Although some aspects have been described with respect to two TAG IDs and three carriers, other numbers of TAG IDs and / or carriers are possible.

[0088] As indicated by reference numeral 620, the UE 120 may transmit using a timing advance value based at least in part on the timing advance configuration information. For example, the UE 120 may transmit on one or more carriers using one or more timing advance offset values ​​received from the network entity 605.

[0089] As noted above, Figure 6 is provided as an example. Other examples may differ from those described with respect to Figure 6.

[0090] 7 illustrates an example process 700 implemented, for example, by a UE, in accordance with the present disclosure. The example process 700 is an example in which a UE (for example, the UE 120) implements operations associated with a timing advance offset configuration.

[0091] 7, in some aspects, process 700 may include receiving information scheduling uplink resources on a carrier associated with multiple timing advance groups and associated with one or more timing advance offsets for the multiple timing advance groups (block 710). For example, a UE may receive (e.g., using the communications manager 140 and / or the receiving component 1102 shown in FIG. 11) information scheduling uplink resources on a carrier associated with multiple timing advance groups and associated with one or more timing advance offsets for the multiple timing advance groups, as described above.

[0092] 7, in some aspects, process 700 may include transmitting on a carrier according to one or more timing advance offsets using uplink resources (block 720). For example, a UE may transmit on a carrier according to one or more timing advance offsets using uplink resources (e.g., using communications manager 140 and / or transmission component 1104 shown in FIG. 11) as described above.

[0093] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or with respect to one or more other processes described elsewhere herein.

[0094] In a first aspect, one or more timing advance offsets are configured per carrier, with the carrier being associated with a single timing advance offset applicable to each of a number of timing advance groups.

[0095] In a second aspect, either alone or in combination with the first aspect, one or more other carriers associated with at least one of the multiple timing advance groups are associated with respective one or more other timing advance offsets, where the one or more timing advance offsets and the one or more other timing advance offsets have a common value.

[0096] In a third aspect, alone or in combination with one or more of the first and second aspects, one or more timing advance offsets are configured per carrier, the one or more timing advance offsets including a first timing advance offset associated with a first timing advance group of the multiple timing advance groups and a second timing advance offset associated with a second timing advance group of the multiple timing advance groups.

[0097] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a first timing advance offset, each associated with a first common timing advance group, and another first timing advance offset, each associated with a first other carrier, have a first common value, and a second timing advance offset, each associated with a second common timing advance group, and another second timing advance offset, each associated with a second common timing advance group, have a second common value.

[0098] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the first common value is different from the second common value.

[0099] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, one or more timing advance offsets are configured for each timing advance group, and each timing advance group is configured with a corresponding timing advance offset.

[0100] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, each first carrier of a plurality of carriers associated with a first timing advance group is associated with a first timing advance offset corresponding to the first timing advance group, and each second carrier of a plurality of carriers associated with a second timing advance group is associated with a second timing advance offset corresponding to the second timing advance group.

[0101] Although Figure 7 illustrates example blocks of process 700, in some aspects process 700 may include additional, fewer, different, or differently configured blocks compared to the blocks illustrated in Figure 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0102] 8 illustrates an example process 800 implemented, for example, by a UE, in accordance with the present disclosure. The example process 800 is an example in which a UE (for example, the UE 120) implements operations associated with a timing advance offset configuration.

[0103] 8, in some aspects, process 800 may include receiving information identifying a single timing advance offset common to multiple carriers (block 810). For example, the UE may receive information identifying a single timing advance offset common to multiple carriers (e.g., using the communications manager 140 and / or the receiving component 1102 shown in FIG. 11) as described above.

[0104] 8, in some aspects, the process 800 may include transmitting a first one or more uplink transmissions associated with the first control resource set pool index and a second one or more uplink transmissions associated with the second control resource set pool index on multiple carriers associated with multiple timing advance groups based at least in part on the single timing advance offset (block 820). For example, the UE may transmit (e.g., using the communications manager 140 and / or the transmission component 1104 shown in FIG. 11) a first one or more uplink transmissions associated with the first control resource set pool index and a second one or more uplink transmissions associated with the second control resource set pool index on multiple carriers associated with multiple timing advance groups based at least in part on the single timing advance offset, as described above.

[0105] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or with respect to one or more other processes described elsewhere herein.

[0106] In a first aspect, a first timing advance value for a first one or more uplink transmissions associated with a first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of a plurality of timing advance groups, and a second timing advance value for a second one or more uplink transmissions associated with a second control resource set pool index is based at least in part on a single timing advance offset common to a plurality of carriers and the first timing advance value of the corresponding timing advance group.

[0107] In a second aspect, alone or in combination with the first aspect, receiving information identifying a single timing advance offset includes receiving a MAC CE conveying a single timing advance offset common to multiple timing advance groups.

[0108] In a third aspect, alone or in combination with one or more of the first and second aspects, a single timing advance offset is applied to one or more first transmissions associated with a second control resource set pool index on a first set of carriers of the plurality of carriers associated with the first timing advance group identifier, and another timing advance offset is applied to one or more second transmissions associated with a second control resource set pool index on a second set of carriers of the plurality of carriers associated with the second timing advance group identifier.

[0109] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a first timing advance value for a first one or more uplink transmissions associated with a first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of a plurality of timing advance groups, and a second timing advance value for a second one or more uplink transmissions associated with a second control resource set pool index is based at least in part on a single timing advance offset for the corresponding timing advance group and the first timing advance value of the corresponding timing advance group.

[0110] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, receiving information identifying a single timing advance offset includes receiving a first MAC CE carrying the single timing advance offset associated with a timing advance group identifier, and receiving a second MAC CE carrying a timing advance command associated with the timing advance group identifier.

[0111] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, receiving information identifying a single timing advance offset includes receiving a single MAC CE carrying the single timing advance offset associated with a timing advance group identifier and carrying a timing advance command associated with the timing advance group identifier.

[0112] Although Figure 8 illustrates example blocks of process 800, in some aspects process 800 may include additional, fewer, different, or differently configured blocks compared to the blocks illustrated in Figure 8. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0113] 9 illustrates an example process 900 implemented, for example, by a network entity, according to the present disclosure. The example process 900 is an example of a network entity (e.g., base station 110, CU 310, DU 330, RU 340, TRP 405, network entity 505, network entity 605, among other examples) implementing operations associated with a timing advance offset configuration.

[0114] 9, in some aspects, process 900 may include transmitting information scheduling uplink resources on a carrier associated with multiple timing advance groups and associated with one or more timing advance offsets for the multiple timing advance groups (block 910). For example, a network entity may transmit (e.g., using communications manager 150 and / or transmission component 1204 shown in FIG. 12) information scheduling uplink resources on a carrier associated with multiple timing advance groups and associated with one or more timing advance offsets for the multiple timing advance groups, as described above.

[0115] 9, in some aspects, process 900 may include receiving on a carrier according to one or more timing advance offsets using uplink resources (block 920). For example, a network entity may receive on a carrier according to one or more timing advance offsets using uplink resources (e.g., using communications manager 150 and / or receiving component 1202 shown in FIG. 12) as described above.

[0116] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or with respect to one or more other processes described elsewhere herein.

[0117] In a first aspect, one or more timing advance offsets are configured per carrier, with the carrier being associated with a single timing advance offset applicable to each of a number of timing advance groups.

[0118] In a second aspect, either alone or in combination with the first aspect, one or more other carriers associated with at least one of the multiple timing advance groups are associated with respective one or more other timing advance offsets, where the one or more timing advance offsets and the one or more other timing advance offsets have a common value.

[0119] In a third aspect, alone or in combination with one or more of the first and second aspects, one or more timing advance offsets are configured per carrier, the one or more timing advance offsets including a first timing advance offset associated with a first timing advance group of the multiple timing advance groups and a second timing advance offset associated with a second timing advance group of the multiple timing advance groups.

[0120] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a first timing advance offset, each associated with a first common timing advance group, and another first timing advance offset, each associated with a first other carrier, have a first common value, and a second timing advance offset, each associated with a second common timing advance group, and another second timing advance offset, each associated with a second common timing advance group, have a second common value.

[0121] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the first common value is different from the second common value.

[0122] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, one or more timing advance offsets are configured for each timing advance group, and each timing advance group is configured with a corresponding timing advance offset.

[0123] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, each first carrier of a plurality of carriers associated with a first timing advance group is associated with a first timing advance offset corresponding to the first timing advance group, and each second carrier of a plurality of carriers associated with a second timing advance group is associated with a second timing advance offset corresponding to the second timing advance group.

[0124] 9 illustrates example blocks of process 900, in some aspects process 900 may include additional, fewer, different, or differently configured blocks compared to the blocks illustrated in FIG 9. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0125] 10 illustrates an example process 1000 implemented, for example, by a network entity, according to the present disclosure. The example process 1000 is an example in which a network entity (e.g., base station 110, CU 310, DU 330, RU 340, TRP 405, network entity 505, network entity 605, among other examples) implements operations associated with a timing advance offset configuration.

[0126] 10, in some aspects, process 1000 may include transmitting information identifying a single timing advance offset common to the multiple carriers (block 1010). For example, a network entity may transmit information identifying a single timing advance offset common to the multiple carriers (e.g., using communications manager 150 and / or transmitting component 1204 shown in FIG. 12) as described above.

[0127] 10, in some aspects, the process 1000 may include receiving (block 1020) a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on a plurality of carriers associated with a plurality of timing advance groups based at least in part on the single timing advance offset. For example, the network entity may receive (e.g., using the communications manager 150 and / or the receiving component 1202 shown in FIG. 12) a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on a plurality of carriers associated with a plurality of timing advance groups based at least in part on the single timing advance offset, as described above.

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

[0129] In a first aspect, a first timing advance value for a first one or more uplink transmissions associated with a first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of a plurality of timing advance groups, and a second timing advance value for a second one or more uplink transmissions associated with a second control resource set pool index is based at least in part on a single timing advance offset common to a plurality of carriers and the first timing advance value of the corresponding timing advance group.

[0130] In a second aspect, alone or in combination with the first aspect, transmitting information identifying a single timing advance offset includes transmitting a MAC CE conveying a single timing advance offset common to multiple timing advance groups.

[0131] In a third aspect, alone or in combination with one or more of the first and second aspects, a single timing advance offset is applied to one or more first transmissions associated with a second control resource set pool index on a first set of carriers of the plurality of carriers associated with the first timing advance group identifier, and another timing advance offset is applied to one or more second transmissions associated with a second control resource set pool index on a second set of carriers of the plurality of carriers associated with the second timing advance group identifier.

[0132] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a first timing advance value for a first one or more uplink transmissions associated with a first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of a plurality of timing advance groups, and a second timing advance value for a second one or more uplink transmissions associated with a second control resource set pool index is based at least in part on a single timing advance offset for the corresponding timing advance group and the first timing advance value of the corresponding timing advance group.

[0133] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, transmitting information identifying a single timing advance offset includes transmitting a first MAC CE carrying the single timing advance offset associated with a timing advance group identifier, and transmitting a second MAC CE carrying a timing advance command associated with the timing advance group identifier.

[0134] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, transmitting information identifying the single timing advance offset includes transmitting a single MAC CE carrying the single timing advance offset associated with the timing advance group identifier and carrying a timing advance command associated with the timing advance group identifier.

[0135] Although Figure 10 illustrates example blocks of process 1000, in some aspects process 1000 may include additional, fewer, different, or differently configured blocks compared to the blocks illustrated in Figure 10. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0136] FIG. 11 is a diagram of an example apparatus 1100 for wireless communication. The apparatus 1100 may be a UE, or a UE may include the apparatus 1100. In some aspects, the apparatus 1100 comprises a receiving component 1102 and a transmitting component 1104 that may communicate with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using the receiving component 1102 and the transmitting component 1104. As further shown, the apparatus 1100 may comprise a communications manager 140. The communications manager 140 may include a timing component 1108, among other examples.

[0137] In some aspects, the apparatus 1100 may be configured to perform one or more operations described herein with respect to FIGS. 5-6. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as process 700 of FIG. 7, process 800 of FIG. 8, or a combination thereof. In some aspects, the apparatus 1100 and / or one or more components illustrated in FIG. 11 may include one or more components of a UE described with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 11 may be implemented within one or more components described with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components 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 executable by a controller or processor to perform the functions or operations of the component.

[0138] The receiving component 1102 may receive communications from the device 1106, such as a reference signal, control information, data communications, or a combination thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of a UE as described with respect to FIG.

[0139] The transmitting component 1104 may transmit a communication, such as a reference signal, control information, a data communication, or a combination thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate a communication and provide the generated communication to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and transmit the processed signal to the device 1106. In some aspects, the transmitting component 1104 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of a UE as described with respect to FIG. 2. In some aspects, the transmitting component 1104 may be co-located with the receiving component 1102 in a transceiver.

[0140] The receiving component 1102 may receive information scheduling uplink resources on carriers associated with multiple timing advance groups and associated with one or more timing advance offsets for the multiple timing advance groups. The transmitting component 1104 may transmit on the carriers according to the one or more timing advance offsets using the uplink resources. The timing component 1108 may determine timing for one or more transmissions on the one or more carriers in association with the one or more timing advance groups. The receiving component 1102 may receive information identifying a single timing advance offset common to the multiple carriers. The transmitting component 1104 may transmit a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on the multiple carriers associated with the multiple timing advance groups based at least in part on the single timing advance offset.

[0141] The number and configuration of components shown in Figure 11 are provided as an example. In practice, there may be additional, fewer, different, or differently configured components than those shown in Figure 11. Furthermore, two or more of the components shown in Figure 11 may be implemented within a single component, or a single component shown in Figure 11 may be implemented as multiple distributed components. Additionally, or instead, a set of components (one or more) shown in Figure 11 may perform one or more functions that are described as being performed by another set of components shown in Figure 11.

[0142] 12 is a diagram of an example apparatus 1200 for wireless communication. The apparatus 1200 may be a network entity, or a network entity may include the apparatus 1200. In some aspects, the apparatus 1200 comprises a receiving component 1202 and a transmitting component 1204 that may communicate with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using the receiving component 1202 and the transmitting component 1204. As further shown, the apparatus 1200 may comprise a communications manager 150. The communications manager 150 may include a timing configuration component 1208, among other examples.

[0143] In some aspects, the device 1200 may be configured to perform one or more operations described herein with respect to Figures 5-6. Additionally or alternatively, the device 1200 may be configured to perform one or more processes described herein, such as process 900 of Figure 9, process 1000 of Figure 10, or a combination thereof. In some aspects, the device 1200 and / or one or more components illustrated in Figure 12 may include one or more components of a network entity described with respect to Figure 2. Additionally or alternatively, one or more components illustrated in Figure 12 may be implemented within one or more components described with respect to Figure 2. Additionally or alternatively, one or more components of the set of components 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 executable by a controller or processor to perform the function or operation of the component.

[0144] The receiving component 1202 may receive communications from the device 1206, such as a reference signal, control information, data communications, or a combination thereof. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of the network entities described with respect to FIG.

[0145] The transmitting component 1204 may transmit a communication, such as a reference signal, control information, a data communication, or a combination thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate a communication and provide the generated communication to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and transmit the processed signal to the device 1206. In some aspects, the transmitting component 1204 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof of the network entities described with respect to FIG. 2. In some aspects, the transmitting component 1204 may be co-located with the receiving component 1202 in a transceiver.

[0146] The transmitting component 1204 may transmit information scheduling uplink resources on carriers associated with multiple timing advance groups and associated with one or more timing advance offsets for the multiple timing advance groups. The receiving component 1202 may use the uplink resources to receive on the carriers according to the one or more timing advance offsets. The transmitting component 1204 may transmit information identifying a single timing advance offset common to the multiple carriers. The receiving component 1202 may receive a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on the multiple carriers associated with the multiple timing advance groups based at least in part on the single timing advance offset. The timing configuration component 1208 may configure transmission timing for the device 1206 by configuring one or more timing advance commands or timing advance offset values.

[0147] The number and configuration of components shown in Figure 12 are provided as an example. In practice, there may be additional, fewer, different, or differently configured components than those shown in Figure 12. Furthermore, two or more of the components shown in Figure 12 may be implemented within a single component, or a single component shown in Figure 12 may be implemented as multiple distributed components. Additionally, or instead, a set of components shown in Figure 12 may perform one or more functions that are described as being performed by another set of components shown in Figure 12.

[0148] The following provides a summary of several aspects of the disclosure.

[0149] Aspect 1: A method of wireless communication implemented by a user equipment (UE), comprising: receiving information scheduling uplink resources on a carrier associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups; and transmitting on the carrier using the uplink resources in accordance with the one or more timing advance offsets.

[0150] Aspect 2: The method of aspect 1, wherein one or more timing advance offsets are configured per carrier, and a carrier is associated with a single timing advance offset applicable to each of a plurality of timing advance groups.

[0151] Aspect 3: A method according to any one of aspects 1 to 2, wherein one or more other carriers associated with at least one of a plurality of timing advance groups are associated with respective one or more other timing advance offsets, and the one or more timing advance offsets and the one or more other timing advance offsets have a common value.

[0152] Aspect 4: A method as described in any of aspects 1 to 3, wherein one or more timing advance offsets are configured per carrier, and the one or more timing advance offsets include a first timing advance offset associated with a first timing advance group of a plurality of timing advance groups and a second timing advance offset associated with a second timing advance group of the plurality of timing advance groups.

[0153] Aspect 5: The method of aspect 4, wherein a first timing advance offset and another first timing advance offset associated with a first other carrier, each associated with a first common timing advance group, have a first common value, and a second timing advance offset and another second timing advance offset associated with a second other carrier, each associated with a second common timing advance group, have a second common value.

[0154] Aspect 6: The method of aspect 5, wherein the first common value is different from the second common value.

[0155] Aspect 7: The method of any one of aspects 1 to 6, wherein one or more timing advance offsets are configured for each timing advance group, each timing advance group being configured with a corresponding timing advance offset.

[0156] Aspect 8: The method of aspect 7, wherein each first carrier of a plurality of carriers associated with a first timing advance group is associated with a first timing advance offset corresponding to the first timing advance group, and each second carrier of a plurality of carriers associated with a second timing advance group is associated with a second timing advance offset corresponding to the second timing advance group.

[0157] Aspect 9: A method of wireless communication implemented by a user equipment (UE), comprising: receiving information identifying a single timing advance offset common to a plurality of carriers; and transmitting a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on a plurality of carriers associated with a plurality of timing advance groups based at least in part on the single timing advance offset.

[0158] Aspect 10: The method of aspect 9, wherein a first timing advance value for a first one or more uplink transmissions associated with a first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of a plurality of timing advance groups, and a second timing advance value for a second one or more uplink transmissions associated with a second control resource set pool index is based at least in part on a single timing advance offset common to a plurality of carriers and the first timing advance value of the corresponding timing advance group.

[0159] Aspect 11: A method as described in any of aspects 9 or 10, wherein receiving information identifying a single timing advance offset includes receiving a medium access control (MAC) control element (CE) conveying a single timing advance offset common to multiple timing advance groups.

[0160] Aspect 12: A method as described in any of aspects 9 to 111, wherein a single timing advance offset is applied to one or more first transmissions associated with a second control resource set pool index on a first set of carriers of a plurality of carriers associated with a first timing advance group identifier, and another timing advance offset is applied to one or more second transmissions associated with a second control resource set pool index on a second set of carriers of a plurality of carriers associated with a second timing advance group identifier.

[0161] Aspect 13: A method as described in any of aspects 9 to 12, wherein a first timing advance value for a first one or more uplink transmissions associated with a first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of a plurality of timing advance groups, and a second timing advance value for a second one or more uplink transmissions associated with a second control resource set pool index is based at least in part on a single timing advance offset for the corresponding timing advance group and the first timing advance value of the corresponding timing advance group.

[0162] Aspect 14: A method as described in any of aspects 9 to 13, wherein receiving information identifying a single timing advance offset includes receiving a first medium access control (MAC) control element (CE) carrying the single timing advance offset associated with a timing advance group identifier, and receiving a second MAC CE carrying a timing advance command associated with the timing advance group identifier.

[0163] Aspect 15: A method as described in any of aspects 9 to 13, wherein receiving information identifying a single timing advance offset includes receiving a single medium access control (MAC) control element (CE) carrying the single timing advance offset associated with a timing advance group identifier and carrying a timing advance command associated with the timing advance group identifier.

[0164] Aspect 16: A method of wireless communication implemented by a network entity, the method including: transmitting information scheduling uplink resources on a carrier associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups; and receiving on the carrier according to the one or more timing advance offsets using the uplink resources.

[0165] Aspect 17: The method of aspect 16, wherein one or more timing advance offsets are configured per carrier, and a carrier is associated with a single timing advance offset applicable to each of a plurality of timing advance groups.

[0166] Aspect 18: A method as described in aspect 16 or aspect 17, wherein one or more other carriers associated with at least one of a plurality of timing advance groups are associated with respective one or more other timing advance offsets, and the one or more timing advance offsets and the one or more other timing advance offsets have a common value.

[0167] Aspect 19: A method as described in any of aspects 16 to 18, wherein one or more timing advance offsets are configured per carrier, and the one or more timing advance offsets include a first timing advance offset associated with a first timing advance group of a plurality of timing advance groups and a second timing advance offset associated with a second timing advance group of the plurality of timing advance groups.

[0168] Aspect 20: The method of aspect 19, wherein a first timing advance offset and another first timing advance offset associated with a first other carrier, each associated with a first common timing advance group, have a first common value, and a second timing advance offset and another second timing advance offset associated with a second other carrier, each associated with a second common timing advance group, have a second common value.

[0169] Example 21: The method of example 20, wherein the first common value is different from the second common value.

[0170] Aspect 22: A method according to any of aspects 16 to 21, wherein one or more timing advance offsets are configured for each timing advance group, each timing advance group being configured with a corresponding timing advance offset.

[0171] Aspect 23: The method of aspect 22, wherein each first carrier of a plurality of carriers associated with a first timing advance group is associated with a first timing advance offset corresponding to the first timing advance group, and each second carrier of a plurality of carriers associated with a second timing advance group is associated with a second timing advance offset corresponding to the second timing advance group.

[0172] Aspect 24: A method of wireless communication implemented by a network entity, the method including: transmitting information identifying a single timing advance offset common to a plurality of carriers; and receiving, on a plurality of carriers associated with a plurality of timing advance groups, a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index based at least in part on the single timing advance offset.

[0173] Aspect 25: The method of aspect 24, wherein a first timing advance value for a first one or more uplink transmissions associated with a first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of a plurality of timing advance groups, and a second timing advance value for a second one or more uplink transmissions associated with a second control resource set pool index is based at least in part on a single timing advance offset common to a plurality of carriers and the first timing advance value of the corresponding timing advance group.

[0174] Aspect 26: The method of any of aspects 24 or 25, wherein transmitting information identifying the single timing advance offset includes transmitting a medium access control (MAC) control element (CE) conveying a single timing advance offset common to multiple timing advance groups.

[0175] Aspect 27: A method as described in any of aspects 24 to 26, wherein a single timing advance offset is applied to one or more first transmissions associated with a second control resource set pool index on a first set of carriers of a plurality of carriers associated with a first timing advance group identifier, and another timing advance offset is applied to one or more second transmissions associated with a second control resource set pool index on a second set of carriers of a plurality of carriers associated with a second timing advance group identifier.

[0176] Aspect 28: The method of any of aspects 24 to 27, wherein a first timing advance value for a first one or more uplink transmissions associated with a first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of a plurality of timing advance groups, and a second timing advance value for a second one or more uplink transmissions associated with a second control resource set pool index is based at least in part on a single timing advance offset for the corresponding timing advance group and the first timing advance value of the corresponding timing advance group.

[0177] Aspect 29: A method as described in any of aspects 24 to 28, wherein transmitting information identifying a single timing advance offset includes transmitting a first medium access control (MAC) control element (CE) carrying the single timing advance offset associated with a timing advance group identifier, and transmitting a second MAC CE carrying a timing advance command associated with the timing advance group identifier.

[0178] Aspect 30: A method as described in any of aspects 24 to 28, wherein transmitting information identifying the single timing advance offset includes transmitting a single medium access control (MAC) control element (CE) carrying the single timing advance offset associated with the timing advance group identifier and carrying a timing advance command associated with the timing advance group identifier.

[0179] Aspect 31: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform one or more of the methods of aspects 1 to 8.

[0180] Aspect 32: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform one or more of the methods of aspects 1 to 8.

[0181] Aspect 33: An apparatus for wireless communication, comprising at least one means for performing one or more of the methods of aspects 1 to 8.

[0182] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform one or more of the methods of aspects 1 to 8.

[0183] Aspect 35: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods of aspects 1 to 8.

[0184] Aspect 36: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform one or more of the methods of aspects 9 to 15.

[0185] Aspect 37: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform one or more of the methods of aspects 9 to 15.

[0186] Aspect 38: An apparatus for wireless communication, comprising at least one means for performing one or more of the methods of aspects 9 to 15.

[0187] Aspect 39: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform one or more of the methods of aspects 9 to 15.

[0188] Aspect 40: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods of aspects 9 to 15.

[0189] Aspect 41: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform one or more of the methods of aspects 16 to 23.

[0190] Aspect 42: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform one or more of the methods of aspects 16 to 23.

[0191] Aspect 43: An apparatus for wireless communication comprising at least one means for performing one or more of the methods of aspects 16 to 23.

[0192] Aspect 44: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to implement one or more of the methods of aspects 16 to 23.

[0193] Aspect 45: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods of aspects 16 to 23.

[0194] Aspect 46: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform one or more of the methods of aspects 24 to 30.

[0195] Aspect 47: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform one or more of the methods of aspects 24 to 30.

[0196] Aspect 48: An apparatus for wireless communication, comprising at least one means for performing one or more of the methods of aspects 24 to 30.

[0197] Aspect 49: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to implement one or more of the methods of aspects 24 to 30.

[0198] Aspect 50: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods of aspects 24 to 30.

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

[0200] As used herein, the term "component" is intended to be broadly construed as hardware and / or a combination of hardware and software. "Software" is intended to be broadly construed to mean, among other examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not intended to limit aspects. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, as one skilled in the art will appreciate that software and hardware may be designed to implement the systems and / or methods based at least in part on the description herein.

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

[0202] Although particular combinations of features are recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. The disclosure of the various aspects includes each dependent claim in combination with all other claims within the set of claims. As used herein, phrases referring to "at least one of" a list of items refer to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other permutation of a, b, and c).

[0203] No element, act, or instruction used herein should be construed as critical or essential unless expressly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Additionally, as used herein, the definite article "the" is intended to include one or more items referred to in relation to the definite article "the" and may be used interchangeably with "one or more." Additionally, as used herein, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more." When only one item is intended, the phrase "only one" or similar language is used. Also, as used herein, terms such as "has," "have," and "having" are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that "has" A may also have B). Additionally, the phrase "based on" is intended to mean "based at least in part on," unless expressly stated otherwise. Also, as used herein, the term "or" is intended to be inclusive when used in conjunction and may be used interchangeably with "and / or," unless expressly stated otherwise (e.g., when used in combination with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communications, comprising: Memory, one or more processors coupled to the memory, receiving information for scheduling uplink resources on a carrier associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups; transmitting on the carrier according to the one or more timing advance offsets using the uplink resources; one or more processors configured to A user equipment (UE) comprising:

2. 2. The UE of claim 1, wherein the one or more timing advance offsets are configured on a per carrier basis, the carrier being associated with a single timing advance offset applicable to each of the plurality of timing advance groups.

3. one or more other carriers associated with at least one of the plurality of timing advance groups are associated with a respective one or more other timing advance offsets; The UE of claim 1 , wherein the one or more timing advance offsets and the one or more other timing advance offsets have a common value.

4. the one or more timing advance offsets are configured per carrier; 2. The UE of claim 1, wherein the one or more timing advance offsets include a first timing advance offset associated with a first timing advance group of the plurality of timing advance groups and a second timing advance offset associated with a second timing advance group of the plurality of timing advance groups.

5. the first timing advance offset and another first timing advance offset associated with a first other carrier, each associated with a first common timing advance group, have a first common value; 5. The UE of claim 4, wherein the second timing advance offset and another second timing advance offset associated with a second other carrier, each associated with a second common timing advance group, have a second common value.

6. The UE of claim 5 , wherein the first common value is different from the second common value.

7. the one or more timing advance offsets are configured for each timing advance group; The UE of claim 1 , wherein each timing advance group is configured with a corresponding timing advance offset.

8. 8. The UE of claim 7, wherein each first carrier of a plurality of carriers associated with a first timing advance group is associated with a first timing advance offset corresponding to the first timing advance group, and each second carrier of the plurality of carriers associated with a second timing advance group is associated with a second timing advance offset corresponding to the second timing advance group.

9. A user equipment (UE) for wireless communications, comprising: Memory, one or more processors coupled to the memory, receiving information identifying a single timing advance offset common to a plurality of carriers; one or more processors configured to transmit a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index on the multiple carriers associated with multiple timing advance groups based at least in part on the single timing advance offset; A user equipment (UE) comprising:

10. a first timing advance value for the first one or more uplink transmissions associated with the first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of the plurality of timing advance groups; 10. The UE of claim 9, wherein a second timing advance value for the second one or more uplink transmissions associated with the second control resource set pool index is based at least in part on the single timing advance offset common to the multiple carriers and the first timing advance value of the corresponding timing advance group.

11. wherein the one or more processors receive the information identifying the single timing advance offset.

10. The UE of claim 9, configured to receive a Medium Access Control (MAC) Control Element (CE) that conveys the single timing advance offset common to the multiple timing advance groups.

12. the single timing advance offset is applied to one or more first transmissions associated with the second control resource set pool index on a first set of carriers of the plurality of carriers associated with a first timing advance group identifier; 10. The UE of claim 9, wherein a different timing advance offset is applied to one or more second transmissions associated with the second control resource set pool index on a second set of carriers of the plurality of carriers associated with a second timing advance group identifier.

13. a first timing advance value for the first one or more uplink transmissions associated with the first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of the plurality of timing advance groups; 10. The UE of claim 9, wherein a second timing advance value for the second one or more uplink transmissions associated with the second control resource set pool index is based at least in part on the single timing advance offset for the corresponding timing advance group and the first timing advance value of the corresponding timing advance group.

14. wherein the one or more processors receive the information identifying the single timing advance offset. receiving a first medium access control (MAC) control element (CE) carrying the single timing advance offset associated with a timing advance group identifier; The UE of claim 9 , configured to receive a second MAC CE carrying a timing advance command associated with the timing advance group identifier.

15. wherein the one or more processors receive the information identifying the single timing advance offset.

10. The UE of claim 9, configured to receive a single Medium Access Control (MAC) Control Element (CE) carrying the single timing advance offset associated with a timing advance group identifier and carrying a timing advance command associated with the timing advance group identifier.

16. A network entity for wireless communication, comprising: Memory, one or more processors coupled to the memory, transmitting information scheduling uplink resources on a carrier associated with a plurality of timing advance groups and associated with one or more timing advance offsets for the plurality of timing advance groups; receiving on the carrier according to the one or more timing advance offsets using the uplink resources; one or more processors configured to A network entity comprising:

17. 17. The network entity of claim 16, wherein the one or more timing advance offsets are configured on a per carrier basis, the carrier being associated with a single timing advance offset applicable to each of the plurality of timing advance groups.

18. one or more other carriers associated with at least one of the plurality of timing advance groups are associated with a respective one or more other timing advance offsets; The network entity of claim 16 , wherein the one or more timing advance offsets and the one or more other timing advance offsets have a common value.

19. the one or more timing advance offsets are configured per carrier; 17. The network entity of claim 16, wherein the one or more timing advance offsets include a first timing advance offset associated with a first timing advance group of the plurality of timing advance groups and a second timing advance offset associated with a second timing advance group of the plurality of timing advance groups.

20. the first timing advance offset and another first timing advance offset associated with a first other carrier, each associated with a first common timing advance group, have a first common value; 20. The network entity of claim 19, wherein the second timing advance offset and another second timing advance offset associated with a second other carrier, each associated with a second common timing advance group, have a second common value.

21. The network entity of claim 20 , wherein the first common value is different from the second common value.

22. the one or more timing advance offsets are configured for each timing advance group; The network entity of claim 16, wherein each timing advance group is configured with a corresponding timing advance offset.

23. 23. The network entity of claim 22, wherein each first carrier of a plurality of carriers associated with a first timing advance group is associated with a first timing advance offset corresponding to the first timing advance group, and each second carrier of the plurality of carriers associated with a second timing advance group is associated with a second timing advance offset corresponding to the second timing advance group.

24. A network entity for wireless communication, comprising: Memory, one or more processors coupled to the memory, transmitting information identifying a single timing advance offset common to a plurality of carriers; one or more processors configured to receive, on the plurality of carriers associated with a plurality of timing advance groups, a first one or more uplink transmissions associated with a first control resource set pool index and a second one or more uplink transmissions associated with a second control resource set pool index based at least in part on a single timing advance offset; A network entity comprising:

25. a first timing advance value for the first one or more uplink transmissions associated with the first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of the plurality of timing advance groups; 25. The network entity of claim 24, wherein a second timing advance value for the second one or more uplink transmissions associated with the second control resource set pool index is based at least in part on the single timing advance offset common to the multiple carriers and the first timing advance value of the corresponding timing advance group.

26. wherein the one or more processors transmit the information identifying the single timing advance offset.

25. The network entity of claim 24, configured to transmit a Medium Access Control (MAC) Control Element (CE) carrying the single timing advance offset common to the multiple timing advance groups.

27. the single timing advance offset is applied to one or more first transmissions associated with the second control resource set pool index on a first set of carriers of the plurality of carriers associated with a first timing advance group identifier; 25. The network entity of claim 24, wherein a different timing advance offset is applied to one or more second transmissions associated with the second control resource set pool index on a second set of carriers of the plurality of carriers associated with a second timing advance group identifier.

28. a first timing advance value for the first one or more uplink transmissions associated with the first control resource set pool index is based at least in part on a timing advance command for a corresponding timing advance group of the plurality of timing advance groups; 25. The network entity of claim 24, wherein a second timing advance value for the second one or more uplink transmissions associated with the second control resource set pool index is based at least in part on the single timing advance offset for the corresponding timing advance group and the first timing advance value of the corresponding timing advance group.

29. wherein the one or more processors transmit the information identifying the single timing advance offset. transmitting a first medium access control (MAC) control element (CE) carrying the single timing advance offset associated with a timing advance group identifier; 25. The network entity of claim 24, configured to transmit a second MAC CE carrying a timing advance command associated with the timing advance group identifier.

30. wherein the one or more processors transmit the information identifying the single timing advance offset.

25. The network entity of claim 24, configured to transmit a single Medium Access Control (MAC) Control Element (CE) carrying the single timing advance offset associated with a timing advance group identifier and carrying a timing advance command associated with the timing advance group identifier.

Images