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] The aspects of this disclosure generally relate to techniques and apparatus for timing advance offset configurations in relation to wireless communications. [Background technology]

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, including telephone, video, data, messaging, and broadcast. Typical wireless communication systems can employ multiple access technologies that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard published by the Third Generation Partnership Project (3GPP®).

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

[0004] The multiple access technologies described above have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, national, regional, and / or global levels. New Radio (NR), which may be called 5G, is a set of extensions to the LTE mobile standard published by 3GPP. NR is designed to better support mobile broadband internet access through improved spectral efficiency, reduced costs, enhanced service, utilization of new spectra, and better integration with other open standards through the use of orthogonal frequency division multiplexing (OFDM) with cyclic prefixes (CP) 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 remain beneficial. [Overview of the Initiative]

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

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

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

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

[0009] Some embodiments described herein relate to a UE for wireless communications. The UE may include memory and one or more processors coupled to the memory. One or more processors may be associated with a plurality of timing advance groups and configured to receive information for scheduling uplink resources on a carrier associated with one or more timing advance offsets for the plurality of timing advance groups. One or more processors may be configured to use the uplink resources to transmit on the carrier according to one or more timing advance offsets.

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

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

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

[0013] Some aspects described herein relate to a non-temporary computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions may cause the UE to receive information for scheduling uplink resources on a carrier associated with a plurality of timing advance groups and one or more timing advance offsets for the plurality of timing advance groups. When executed by one or more processors of the UE, the set of instructions may cause the UE to use the uplink resources to transmit on a carrier according to one or more timing advance offsets.

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

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

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

[0017] Some embodiments described herein relate to devices for wireless communications. The devices may include means for receiving information to schedule uplink resources on a carrier associated with a plurality of timing advance groups and one or more timing advance offsets for the plurality of timing advance groups. The devices may include means for using the uplink resources to transmit on the carrier according to one or more timing advance offsets.

[0018] Some embodiments described herein relate to devices for wireless communications. The devices may include means for receiving information identifying a single timing advance offset common to multiple carriers. The devices may include means for transmitting one or more first uplink transmissions associated with a first control resource set pool index and one or more second uplink transmissions associated with a second control resource set pool index over multiple carriers associated with multiple timing advance groups, at least in part on a single timing advance offset.

[0019] Some embodiments described herein relate to devices for wireless communications. The devices may include means for transmitting information for scheduling uplink resources on a carrier associated with a plurality of timing advance groups and one or more timing advance offsets for the plurality of timing advance groups. The devices may include means for using the uplink resources to receive on the carrier according to one or more timing advance offsets.

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

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

[0022] The above provides a fairly broad overview of the features and technical advantages of the examples provided in this disclosure, in order to better understand the following “Modes for Carrying Out the Invention.” Additional features and advantages are described below. The concepts and specific examples of the disclosure can be readily used as a basis for modifying or designing other structures to achieve the same objectives as the disclosure. Such equivalent structures will not deviate from the scope of the appended claims. The characteristics and associated advantages of both the organization and operation of the concepts disclosed herein will be better understood by considering the following description together with the accompanying figures. Each figure is provided for illustrative and explanatory purposes only, and not as a definition of the limitations of the claims.

[0023] Aspects are described in this disclosure by way of several examples, and those skilled in the art will understand that such aspects can be implemented in many different configurations and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects can be implemented via integrated chip embodiments or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented at 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 can 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 can include one or more components (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers) for analog and digital applications. It is intended that the aspects described herein can be practiced in a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and structures.

[0024] To better understand the above-listed features of the present disclosure in detail, a more detailed description, briefly summarized above, may be obtained by referring to some of the aspects shown in the accompanying drawings. However, it should be noted that the accompanying drawings show only certain exemplary aspects of the disclosure and, therefore, should not be considered as limiting the scope of the disclosure, as the description may be recognized as applicable to other equally effective aspects. Like reference numerals in different drawings can identify the same or similar elements.

Brief Description of the Drawings

[0025] [Figure 1] FIG. showing an example of a wireless network according to the present disclosure. [Figure 2] FIG. showing an example of a base station communicating with a user equipment (UE) within a wireless network according to the present disclosure. [Figure 3] FIG. showing an example of a non - aggregated base station architecture according to the present disclosure. [Figure 4] FIG. showing an example of multiple transmit receive point (multi - TRP) communication according to the present disclosure. [Figure 5] FIG. showing an example associated with a timing advance offset configuration according to the present disclosure. [Figure 6] FIG. showing an example associated with a timing advance offset configuration according to the present disclosure. [Figure 7] FIG. showing an exemplary process associated with a timing advance offset configuration according to the present disclosure. [Figure 8] FIG. showing an exemplary process associated with a timing advance offset configuration according to the present disclosure. [Figure 9] FIG. showing an exemplary process associated with a timing advance offset configuration according to the present disclosure. [Figure 10] FIG. showing an exemplary process associated with a timing advance offset configuration according to the present disclosure. [Figure 11] FIG. showing an exemplary apparatus for wireless communication according to the present disclosure. [Figure 12] FIG. showing an exemplary apparatus for wireless communication according to the present disclosure.

Modes for Carrying Out the Invention

[0026] Various aspects of this disclosure are fully described below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as being limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided to make this disclosure thorough and complete and to ensure that the scope of this disclosure is fully conveyed to those skilled in the art. Those skilled in the art should understand that the scope of this disclosure is intended to encompass any aspect of this disclosure, 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 aspects described herein. Notwithstanding that the scope of this disclosure is intended to encompass apparatus or methods that are practiced using other structures, functions, or, in addition to or otherwise, various aspects of this disclosure described herein. It should be understood that any aspect of this disclosure can be embodied by one or more elements of the claims.

[0027] Next, several embodiments of telecommunications systems are described with reference to various devices and techniques. These devices and techniques are described in embodiments for carrying out the following inventions and are shown 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 specific application and the design constraints imposed on the overall system.

[0028] The embodiments may be described herein using terms commonly associated with 5G or New Radio (NR) radio access technology (RAT), but the embodiments of this disclosure may apply to other RATs such as 3G RAT, 4G RAT, and / or 5G and later RATs (e.g., 6G).

[0029] Figure 1 shows an example of a wireless network 100 as described herein. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long-Term Evolution (LTE)) network, or may include elements thereof, among other examples. The wireless network 100 may include one or more base stations 110 (indicated as BS110a, BS110b, BS110c, and BS110d), user equipment (UE) 120 or multiple UE120s (indicated as UE120a, UE120b, UE120c, UE120d, and UE120e), and / or other network entities. A base station 110 is an entity that communicates with a UE120. A base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmission reception point (TRP). Each base station 110 may provide communication coverage to a specific geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” may, depending on the context in which the term is used, refer to the coverage area of ​​a base station 110 and / or the base station subsystems providing service to this coverage area.

[0030] Base station 110 may provide communication coverage to macrocells, picocells, femtocells, and / or other types of cells. Macrocells can cover relatively large geographical areas (e.g., a radius of several kilometers) and may enable unrestricted access by UEs 120 subscribing to the service. Picocells can cover relatively small geographical areas and may enable unrestricted access by UEs 120 subscribing to the service. Femtocells can cover relatively small geographical areas (e.g., a home) and may enable limited access by UEs 120 associated with a femtocell (e.g., UEs 120 within a closed subscriber group (CSG)). Base station 110 for macrocells may be called a macro base station. Base station 110 for picocells may be called a pico base station. Base station 110 for femtocells may be called a femto base station or home base station. In the example shown in Figure 1, BS110a can be a macro base station for macrocell 102a, BS110b can be a pico base station for picocell 102b, and BS110c can be a femto base station for femtocell 102c. A base station may support one or more (for example, three) cells.

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

[0032] The wireless network 100 may include one or more relay stations. A relay station is an entity capable of receiving data transmissions from upstream stations (e.g., base stations 110 or UE120) and transmitting that data to downstream stations (e.g., UE120 or base stations 110). A relay station may be a UE120 that can relay transmissions from other UE120s. In the example shown in Figure 1, BS110d (e.g., a relay base station) can communicate with BS110a (e.g., a macro base station) and UE120d to facilitate communication between BS110a and UE120d. The base station 110 that relays communications may be called a relay station, relay base station, repeater, etc.

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

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

[0035] UE120 may be distributed across the entire wireless network 100, and each UE120 may be fixed or mobile. UE120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE120 can be cellular telephones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablets, cameras, game devices, netbooks, smartbooks, ultrabooks, medical devices, biometric devices, wearable devices (e.g., smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings or smart bracelets)), entertainment devices (e.g., music devices, video devices, and / or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system devices, and / or any other suitable devices configured to communicate via a wireless medium.

[0036] Some UE120s may be considered machine-type communication (MTC) UEs, or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with base stations, other devices (e.g., remote devices), or any other entities. Some UE120s may be considered Internet-of-Things (IoT) devices and / or implemented as NB-IoT (narrowband IoT) devices. Some UE120s may be considered customer premises equipment. A UE120 may be contained within a housing that accommodates the components of the UE120, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0037] In general, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. RAT may be called a wireless technology, air interface, etc. Frequencies may be called carriers, frequency channels, etc. To avoid interference between wireless networks of different RATs, each frequency may support a single RAT in a given geographical area. In some cases, NR networks or 5G RAT networks may be deployed.

[0038] In some examples, two or more UE120s (for example, shown as UE120a and UE120e) may communicate directly using one or more sidelink channels (for example, without using base station 110 as an intermediary for communication with each other). For example, UE120s may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE120s may perform scheduling operations, resource selection operations, and / or other operations described elsewhere in this specification as being performed by base station 110.

[0039] Devices in wireless network 100 may communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, etc., depending on frequency or wavelength. For example, devices in wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands are identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although a portion of FR1 is higher than 6 GHz, it should be understood that FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue may arise with respect to FR2. Although FR2 is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band, it is often referred to (interchangeably) as the "millimeter wave" band in documents and papers.

[0040] The frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. In recent 5G NR research, the operating band for these intermediate band frequencies is identified as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands falling within FR3 may inherit the FR1 and / or FR2 characteristics, and therefore, in effect, the features of FR1 and / or FR2 can be extended to the intermediate 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, unless otherwise specified, terms such as “sub-6GHz” may, when used herein, broadly refer to frequencies that may be below 6GHz, within FR1, or include intermediate band frequencies. Furthermore, unless otherwise specified, terms such as “millimeter wave” may, when used herein, broadly refer to frequencies that may include intermediate band frequencies, within FR2, FR4, FR4-a or FR4-1, and / or FR5, or within the EHF band. The frequencies included within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are intended to be applicable to those modified frequency ranges.

[0042] In some embodiments, UE120 may include a communications manager 140. As detailed elsewhere in this specification, the communications manager 140 may receive information to schedule uplink resources on carriers associated with a plurality of timing advance groups and one or more timing advance offsets for the plurality of timing advance groups, and may use the uplink resources to transmit on carriers according to one or more timing advance offsets. The communications manager 140 may identify or receive information about a single timing advance offset common to a plurality of carriers, and may transmit a first one or more uplink transmission associated with a first control resource set pool index and a second one or more uplink transmission associated with a second control resource set pool index on a plurality of carriers associated with the plurality of timing advance groups, at least in part based on a single timing advance offset. In addition, or instead, the communications manager 140 may perform one or more other operations described herein.

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

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

[0045] Figure 2 shows an example 200 of a base station 110 communicating with a UE 120 within a wireless network 100 according to this disclosure. The base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≧1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≧1).

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

[0047] In UE120, a set of antennas 252 (indicated as antennas 252a to 252r) may receive downlink signals from 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), indicated as modems 254a to 254r. For example, each received signal may be provided to a demodulator component (indicated as DEMOD) of a modem 254. Each modem 254 may use a separate demodulator component to adjust the received signal (e.g., filter, amplify, downconvert, and / or digitize) in order to acquire an input sample. Each modem 254 may use a demodulator component to further process the input sample (e.g., for OFDM) in order to acquire a received symbol. A MIMO detector 256 may acquire a received symbol from a modem 254, perform MIMO detection on the received symbol where applicable, and provide the detected symbol. The receiving processor 258 may process the detected symbols (e.g., demodulate and decode), provide the decoded data for UE120 to the data sink 260, and provide the 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, among other examples, determine the reference signal received power (RSRP) parameter, the received signal strength indicator (RSSI) parameter, the reference signal received quality (RSRQ) parameter, and / or the CQI parameter. In some examples, one or more components of UE120 may be contained within the housing 284.

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

[0049] One or more antennas (for example, antennas 234a-234t and / or antennas 252a-252r) 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 in Figure 2.

[0050] On the uplink, in UE120, the transmit processor 264 may receive and process data from data source 262 and control information (for reporting, including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. 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 the TX MIMO processor 266 where applicable, further processed by the modem 254 (for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some examples, the modem 254 in UE120 may include a modulator and demodulator. In some examples, UE120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modem(s) 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., a controller / processor 280) and memory 282 to carry out any embodiment of the method described herein (referring, for example, to Figures 5 to 12).

[0051] At base station 110, uplink signals from UE 120 and / or other UEs are received by antenna 234, processed by modem 232 (e.g., the demodulator component of modem 232, indicated as DEMOD), detected by MIMO detector 236 where applicable, and may be further processed by receiving processor 238 to obtain decoded data and control information transmitted by UE 120. The receiving processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include a communication unit 244, which may communicate with network controller 130 via the communication unit 244. Base station 110 may include a scheduler 246 for scheduling one or more UE 120 for downlink and / or uplink communication. In some examples, the modem 232 of base station 110 may include a modulator and a demodulator. In some examples, base station 110 includes a transceiver. The transceiver may include any combination of an antenna(s) 234, a modem(s) 232, a MIMO detector 236, a receiving processor 238, a transmitting processor 220, and / or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., a controller / processor 240) and memory 242 to carry out any aspect of the method described herein (referring, for example, to Figures 5 to 12).

[0052] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component(s) in Figure 2 may implement one or more techniques associated with the timing advance offset configuration, as detailed elsewhere in this specification. In some embodiments, the network entity or transmit / receive point (TRP) described herein is base station 110, contained within base station 110, or includes one or more components of base station 110 shown in Figure 2. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component(s) in Figure 2 may implement or direct the operation of, for example, process 700 in Figure 7, process 800 in Figure 8, process 900 in Figure 9, process 1000 in Figure 10, and / or other processes described herein. Memories 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include non-temporary computer-readable media storing one or more instructions for wireless communication (e.g., code and / or program code). For example, when one or more instructions are executed by one or more processors in base station 110 and / or UE 120 (e.g., directly or after compilation, translation, and / or interpretation), one or more processors, UE 120, and / or base station 110 may perform or direct the operation of, for example, process 700 in Figure 7, process 800 in Figure 8, process 900 in Figure 9, process 1000 in Figure 10, and / or other processes described herein. In some examples, executing an instruction may include, among other examples, executing the instruction, translating the instruction, compiling the instruction, and / or interpreting the instruction.

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

[0054] In some embodiments, a network entity (e.g., base station 110) is associated with a plurality of timing advance groups and includes means for transmitting information to schedule uplink resources on carriers associated with one or more timing advance offsets for the plurality of timing advance groups, and / or means for using the uplink resources to receive on carriers according to one or more timing advance offsets. In some embodiments, the network entity includes means for transmitting information to identify a single timing advance offset common to a plurality of carriers, and / or means for receiving a first one or more uplink transmission associated with a first control resource set pool index and a second one or more uplink transmission associated with a second control resource set pool index on a plurality of carriers associated with a plurality of timing advance groups, at least in part on a single timing advance offset. In some embodiments, the means by which a network entity performs the operations described herein may include, for example, one or more of the following: a communications manager 150, a transmitting processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receiving processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

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

[0056] As stated above, Figure 2 is provided as an example. Other examples may differ from those described in Figure 2.

[0057] Figure 3 shows an example architecture of a non-aggregated base station 300. The architecture of the non-aggregated base station 300 may include one or more CU310s that can communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more non-aggregated 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) RIC315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU310s may communicate with one or more DU330s via their respective midhaul links, such as an F1 interface. The DU330s may communicate with one or more RU340s via their respective fronthaul links. The RU340s may communicate with their respective UE120s via one or more radio frequency (RF) access links. In some implementations, UE120 may be served simultaneously by multiple RU340s. In some implementations, UE120 may include a communications manager 396 (e.g., communications manager 140) which can enable UE120 to communicate with other units (e.g., network entities such as CU310, DU330, or RU340, among other examples). One or more of the units such as RU340 may have a communications manager 398 (e.g., communications manager 150) which can enable the unit to communicate with UE120.

[0058] Each of the units, namely CU310, DU330, RU340, and the 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 communication interfaces of a unit, 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 with one or more of the other units over a wired transmission medium. In addition, a unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or transmit signals with one or more of the other units over a wireless transmission medium.

[0059] In some embodiments, the CU310 may host one or more higher-layer control functions. Such control functions may include, among other examples, radio resource control (RRC), packet data convergence protocol (PDCP), or service data adaptation protocol (SDAP). Each control function may be implemented using an interface configured to communicate signals using other control functions hosted by the CU310. The CU310 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 CU310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. The CU310 can be implemented to communicate with the DU330 as needed for network control and signaling.

[0060] The DU330 may correspond to a logic unit containing one or more base station functions for controlling the operation of one or more RU340s. In some embodiments, the DU330 may host one or more of the following, at least in part, depending on a functional decomposition such as that defined by 3GPP: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (among other examples, modules for forward error correction (FEC) coding and decoding, scrambling, or modulation and demodulation). In some embodiments, the DU330 may further host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU330, or with control functions hosted by the CU310.

[0061] Lower-layer functionality can be implemented by one or more RU340s. In some deployments, RU340s controlled by DU330s may correspond to logical nodes hosting RF processing functions, or lower PHY layer functions (among other examples, such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering), or both, at least partially based on functional partitioning such as lower-layer functional partitioning. In such architectures, the RU(s)340 can be implemented to handle over-the-air (OTA) communication with one or more UE120s. In some implementations, real-time and non-real-time modes of control plane communication and user plane communication with the RU(s)40 can be controlled by the corresponding DU330s. In some scenarios, this configuration can enable the DU(singular or plural)330 and CU310 to be implemented in cloud-based RAN architectures such as vRAN architectures.

[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 the deployment of dedicated physical resources to address RAN coverage requirements, which can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as the 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 the O2 interface). Such virtualized network elements may include, but are not limited to, the CU310, DU330, RU340, and quasi-RT RIC325. In some implementations, the SMO framework 305 may communicate with 4G RAN hardware embodiments such as the open eNB (O-eNB) 311 via the O1 interface. In addition, in some implementations, the SMO framework 305 can communicate directly with one or more RU340s via the O1 interface. The SMO framework 305 may also include a non-RT RIC315 configured to support the functionality of the SMO framework 305.

[0063] Non-RT RIC315 may be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance for applications / features in quasi-RT RIC325. Non-RT RIC315 may be coupled to or communicate with quasi-RT RIC325 (e.g., via the A1 interface). Quasi-RT RIC325 may be configured to include logical functions that enable quasi-real-time control and optimization of RAN elements and resources via data acquisition and actions on an interface connecting one or more CU310s, one or more DU330s, or both, and O-eNBs to quasi-RT RIC325 (e.g., via the E2 interface).

[0064] In some implementations, the non-RT RIC315 may receive parameter or external enrichment information from an external server to generate an AI / ML model that will be deployed to the quasi-RT RIC325. Such information may be utilized by the quasi-RT RIC325 and may be received in the SMO framework 305 or the non-RT RIC315 from a non-network data source or from a network function. In some examples, the non-RT RIC315 or quasi-RT RIC325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC315 may employ an AI / ML model to monitor long-term trends and patterns in performance and take corrective actions through the SMO framework 305 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policy).

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

[0066] Figure 4 shows an example of multi-TRP communication (sometimes called multi-panel communication) 400 as described herein. As shown in Figure 4, multiple TRP405s can communicate with the same UE120. TRP405 may correspond to one or more of CU310, DU330, or RU340, among other examples described above in relation to Figure 3.

[0067] Multiple TRP405s (indicated as TRP A and TRP B) may communicate with the same UE120 in coordination (e.g., using coordinated multipoint transmission) to improve reliability, coverage, and / or throughput for a serving cell. The TRP405s may coordinate such communications via interfaces between the TRP405s (e.g., backhaul interfaces and / or access node controllers). The interfaces may have lower latency and / or higher capacity when the TRP405s are co-located at the same base station 110 (e.g., when the TRP405s are different antenna arrays or panels at the same base station 110), and may have higher latency and / or lower capacity (compared to co-location) when the TRP405s are located at different base stations 110. Different TRP405s may communicate with the UE120 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., multilayer 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 TRP405s. In this case, multiple TRP405s (e.g., TRP A and TRP B) may receive PUSCH communications from the UE120 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 having different spatial layers for different TRP405s (e.g., one codeword maps to a first set of layers transmitted to a first TRP405 and to a second set of layers transmitted to a second TRP405). As another example, a PUSCH communication may be transmitted using multiple codewords, with different codewords being transmitted to different TRP405s (e.g., using different sets of layers). In any case, different TRP405s and UE120s may use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, a UE120 and a first TRP405 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 a UE120 and a second TRP405 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 embodiments, a TCI state in a DCI (e.g., DCI format 1_0 or DCI format 1_1 transmitted over a PDCCH) 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 TCI fields in a DCI.In general, the TCI field in this multi-TRP transmission mode (e.g., mode 1) can exhibit a single TCI state (for single-TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed here).

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

[0070] As stated 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 can use to determine the timing of one or more communications. A serving cell may transmit a TA command to indicate adjustments to the TA value being used by the serving cell and the UE. Further details regarding TA commands are described in 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 the amount of offset to be applied to the timing advance value for the serving cell relative to the timing advance values ​​of one or more other serving cells. A network entity may indicate a timing advance offset value by transmitting an n-TimingAdvanceOffset information element (IE). When the UE is not provided with explicit instructions for the timing advance offset value, the UE may be configured to use a default value for the timing advance offset value. Further details regarding the timing advance offset value are described in 3GPP TS 38.133, Release 17, Version 17.4.0.

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

[0073] Therefore, some embodiments 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, a 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 way, the UE enables signaling reduction for carriers associated with a single TAG. In addition, or instead, a UE may apply a common timing advance offset value across multiple carriers associated with the same TAG. For example, a UE may apply the same timing advance offset value within two carriers in a group of carriers having a common TAG ID, but apply a different timing advance offset value within a third carrier in a group of carriers having different TAG IDs.

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

[0075] Several embodiments described herein enable timing advance offset configurations. For example, the timing advance offset value may be configured per carrier. In addition, or instead, the timing advance offset value may be configured across carriers such that the timing advance offset value is configured per TAG. In addition, or instead, the timing advance offset value may be configured differently for each TAG within each carrier such that the same value is configured for common TAGs. In this way, the UE can determine the timing advance offset value that enables the UE to determine the timing for communications in a multi-DCI, multi-TRP deployment.

[0076] Figure 5 shows an example 500 associated with a timing advance offset configuration as described herein. As shown in Figure 5, network entities 505 (for example, among other examples, TRP405, RU340, DU330, CU310, base station 110) and UE120 can communicate with each other.

[0077] As indicated by reference numeral 510, UE120 may receive timing advance configuration information. For example, UE120 may receive information identifying one or more timing advance offset values ​​for one or more carriers. In this case, UE120 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 media access control (MAC) control element (CE) signaling).

[0078] In some embodiments, the UE120 may receive information identifying one or more timing advance offset values ​​configured for each carrier (for example, three timing advance offset values ​​for three carriers, as shown). For example, as shown by reference numeral 550-1, the UE120 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, at least in part, based on the fact that at least one carrier is configured with two TAGs and timing advance offsets, network entity 505 configures the same value in UE120 for the timing advance offsets on any other carrier having either of the two TAGs. In other words, 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 three different carriers. In addition, or instead, network entity 505 may transmit a single timing advance offset IE to identify the common timing advance offset value for three carriers.

[0079] In some embodiments, UE120 may receive information identifying one or more timing advance offset values ​​configured for each carrier. In addition, or instead, for a serving cell configured with two control resource set pool index values ​​and two TAGs, UE may be configured with two timing advance offset values, each associated with one TAG. For example, as shown by reference numeral 550-2, UE120 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 a third carrier. In other words, the network entity 505 provides four different timing advance offsets IE to configure n-TimingAdvanceOffset 1 and n-TimingAdvanceOffset 3_1, respectively, to have a first common timing advance offset value for TAG1 on the first and third carriers, and to configure n-TimingAdvanceOffset 2 and n-TimingAdvanceOffset 3_2, respectively, to have a second common timing advance value for TAG2 on the second and third carriers.

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

[0081] As indicated by reference numeral 520, UE120 may transmit using timing advance values ​​that are at least partially based on timing advance configuration information. For example, UE120 may transmit over one or more carriers using one or more timing advance offset values ​​received from network entity 505.

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

[0083] Figure 6 shows an example 600 associated with a timing advance offset configuration as described herein. As shown in Figure 6, network entities 605 (for example, among other examples, network entities 505, TRP405, RU340, DU330, CU310, base station 110) and UE120 can communicate with each other.

[0084] As indicated by reference numeral 610, UE120 may receive timing advance configuration information. For example, UE120 may receive information identifying one or more timing advance offset values ​​for one or more carriers. In this case, UE120 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 UE120 may receive information in a particular type of MAC CE that identifies the timing advance configuration. For example, the UE120 may receive a MAC CE that has 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 the common timing advance offset value and two reserved bits within the same octet. For example, a single MAC CE may carry a timing advance command that includes a first octet having 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 having two reserved bits and six bits to identify the common timing advance offset value. In this case, the UE120 may apply a timing advance command to the identified TAG, as described in more detail below, and may apply a timing advance offset value to derive a timing advance command for the identified TAG. Alternatively, the first octet may be contained within the first MAC CE (e.g., TA command MAC CE), and the second octet may be contained within the second MAC CE (e.g., timing advance offset MAC CE). In this case, the second MAC CE contains two bits to identify the TAG ID to which a common timing advance offset may be applied.

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

[0087] In some implementations, UE120 may receive information identifying common timing advance offset values ​​that are applicable across carriers but specific to a particular TAG. For example, UE120 may receive a first offset value 2δ1 for a first TAG (for example, for a first and third carrier, each having a first TAG ID) and a second offset value 2δ2 for a second TAG (for example, 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 applies across multiple carriers having the same TAG ID (for example, the first and third carriers), and the second timing advance offset value applies across one or more carriers having the same TAG ID (for example, the second carrier). While some embodiments 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, UE120 may transmit using timing advance values ​​that are at least partially based on timing advance configuration information. For example, UE120 may transmit over one or more carriers using one or more timing advance offset values ​​received from network entity 605.

[0089] As stated above, Figure 6 is provided as an example. Other examples may differ from those described in relation to Figure 6.

[0090] Figure 7 shows an exemplary process 700 performed by, for example, a UE according to the present disclosure. The exemplary process 700 is an example in which a UE (e.g., UE120) performs an operation associated with a timing advance offset configuration.

[0091] As shown in Figure 7, in some embodiments, process 700 may include receiving information (block 710) to schedule uplink resources on a carrier associated with a plurality of timing advance groups and one or more timing advance offsets for the plurality of timing advance groups. For example, the UE may receive information to schedule uplink resources on a carrier associated with a plurality of timing advance groups and one or more timing advance offsets for the plurality of timing advance groups, as described above (for example, using the communication manager 140 and / or receiving component 1102 shown in Figure 11).

[0092] As further shown in Figure 7, in some embodiments, process 700 may include using uplink resources to transmit on the carrier according to one or more timing advance offsets (block 720). For example, the UE may use uplink resources (for example, using the communications manager 140 and / or transmit component 1104 shown in Figure 11) to transmit on the carrier according to one or more timing advance offsets, as described above.

[0093] Process 700 may include additional embodiments, such as any single embodiment or any combination of embodiments, described below with respect to one or more other processes described elsewhere in this Specified Specification.

[0094] In the first embodiment, one or more timing advance offsets are configured for each carrier, and each carrier is associated with a single timing advance offset applicable to each of several timing advance groups.

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

[0096] In the third embodiment, either alone or in combination with one or more of the first and second embodiments, one or more timing advance offsets are configured per carrier, and 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 a plurality of timing advance groups.

[0097] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, 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.

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

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

[0100] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, each first carrier among 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 among 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] Figure 7 shows an exemplary block of process 700, but in some embodiments, process 700 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the block shown in Figure 7. In addition, or instead, two or more of the blocks of process 700 may be performed in parallel.

[0102] Figure 8 shows an exemplary process 800 performed by, for example, a UE according to the present disclosure. The exemplary process 800 is an example in which a UE (e.g., UE120) performs an operation associated with a timing advance offset configuration.

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

[0104] As further shown in Figure 8, in some embodiments, process 800 may include transmitting a first one or more uplink transmission associated with a first control resource set pool index and a second one or more uplink transmission associated with a second control resource set pool index over multiple carriers associated with multiple timing advance groups, at least partially based on a single timing advance offset (block 820). For example, the UE may transmit a first one or more uplink transmission associated with a first control resource set pool index and a second one or more uplink transmission associated with a second control resource set pool index over multiple carriers associated with multiple timing advance groups, at least partially based on a single timing advance offset, using (for example, the communication manager 140 and / or transmission component 1104 shown in Figure 11).

[0105] Process 800 may include additional embodiments, such as any single embodiment or any combination of embodiments, described below with respect to one or more other processes described elsewhere in this Specified Specification.

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

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

[0108] In the third aspect, either 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 among multiple 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 among multiple carriers associated with a second timing advance group identifier.

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

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

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

[0112] Figure 8 shows an exemplary block of process 800, but in some embodiments, process 800 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the block shown in Figure 8. In addition, or instead, two or more of the blocks of process 800 may be performed in parallel.

[0113] Figure 9 shows an exemplary process 900 performed by, for example, a network entity as described herein. The exemplary process 900 is an example in which a network entity (for example, among other examples, base station 110, CU310, DU330, RU340, TRP405, network entity 505, network entity 605) performs an operation associated with a timing advance offset configuration.

[0114] As shown in Figure 9, in some embodiments, process 900 may include transmitting information (block 910) that schedules uplink resources on a carrier associated with a plurality of timing advance groups and one or more timing advance offsets for the plurality of timing advance groups. For example, a network entity may transmit information that schedules uplink resources on a carrier associated with a plurality of timing advance groups and one or more timing advance offsets for the plurality of timing advance groups, as described above (for example, using the communication manager 150 and / or transmission component 1204 shown in Figure 12).

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

[0116] Process 900 may include additional embodiments, such as any single embodiment or any combination of embodiments, described below with respect to one or more other processes described elsewhere in this Specified Specification.

[0117] In the first embodiment, one or more timing advance offsets are configured for each carrier, and each carrier is associated with a single timing advance offset applicable to each of several timing advance groups.

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

[0119] In the third embodiment, either alone or in combination with one or more of the first and second embodiments, one or more timing advance offsets are configured per carrier, and 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 a plurality of timing advance groups.

[0120] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, 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.

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

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

[0123] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, each first carrier among 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 among 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] Figure 9 shows an exemplary block of process 900, but in some embodiments, process 900 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the block shown in Figure 9. In addition, or instead, two or more of the blocks of process 900 may be executed in parallel.

[0125] Figure 10 shows an exemplary process 1000 performed by, for example, a network entity as described herein. The exemplary process 1000 is an example in which a network entity (for example, among other examples, base station 110, CU310, DU330, RU340, TRP405, network entity 505, network entity 605) performs an operation associated with a timing advance offset configuration.

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

[0127] As further shown in Figure 10, in some embodiments, process 1000 may include receiving a first one or more uplink transmission associated with a first control resource set pool index and a second one or more uplink transmission associated with a second control resource set pool index on multiple carriers associated with multiple timing advance groups, at least partially based on a single timing advance offset (block 1020). For example, a network entity may, as described above, receive a first one or more uplink transmission associated with a first control resource set pool index and a second one or more uplink transmission associated with a second control resource set pool index on multiple carriers associated with multiple timing advance groups, at least partially based on a single timing advance offset (for example, using the communication manager 150 and / or receiving component 1202 shown in Figure 12).

[0128] Process 1000 may include additional embodiments, such as any single embodiment or any combination of embodiments, described below with respect to one or more other processes described elsewhere in this Specified Specification.

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

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

[0131] In the third aspect, either 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 among multiple 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 among multiple carriers associated with a second timing advance group identifier.

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

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

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

[0135] Figure 10 shows an exemplary block of process 1000, but in some embodiments, process 1000 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the block shown in Figure 10. In addition, or instead, two or more of the blocks of process 1000 may be executed in parallel.

[0136] Figure 11 shows an exemplary device 1100 for wireless communication. The device 1100 may be a UE, or a UE may include the device 1100. In some embodiments, the device 1100 comprises a receiving component 1102 and a transmitting component 1104 that can communicate with each other (for example, via one or more buses and / or one or more other components). As shown, the device 1100 may use the receiving component 1102 and the transmitting component 1104 to communicate with another device 1106 (such as a UE, base station, or another wireless communication device). As further shown, the device 1100 may include a communications manager 140. The communications manager 140 may include a timing component 1108, among other examples.

[0137] In some embodiments, the device 1100 may be configured to perform one or more operations described herein with respect to Figures 5-6. In addition, or instead, the device 1100 may be configured to perform one or more processes described herein, such as process 700 in Figure 7, process 800 in Figure 8, or a combination thereof. In some embodiments, the device 1100 and / or one or more components shown in Figure 11 may include one or more components of the UE described with respect to Figure 2. In addition, or instead, one or more components shown in Figure 11 may be implemented within one or more components described with respect to Figure 2. In addition, or instead, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-temporary computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0138] The receiving component 1102 may receive communications from the device 1106, such as reference signals, 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 embodiments, the receiving component 1102 may perform signal processing on the received communications (among other examples, filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) and provide the processed signals to one or more other components of the device 1100. In some embodiments, the receiving component 1102 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof, as described with respect to Figure 2.

[0139] The transmitting component 1104 can transmit communications such as reference signals, control information, data communications, or a combination thereof to the device 1106. In some embodiments, one or more other components of the device 1100 can generate communications and provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some embodiments, the transmitting component 1104 can perform signal processing on the generated communications (among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 1106. In some embodiments, the transmitting component 1104 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or a combination thereof, as described with respect to Figure 2. In some embodiments, the transmitting component 1104 can be collated with the receiving component 1102 in a transceiver.

[0140] The receiving component 1102 is associated with multiple timing advance groups and may receive information for scheduling uplink resources on carriers associated with one or more timing advance offsets for multiple timing advance groups. The transmitting component 1104 may use the uplink resources to transmit on carriers according to one or more timing advance offsets. The timing component 1108 may determine the timing for one or more transmissions on one or more carriers in relation to one or more timing advance groups. The receiving component 1102 may receive information identifying a single timing advance offset common to multiple carriers. The transmitting component 1104 may transmit one or more first uplink transmissions associated with a first control resource set pool index and one or more second uplink transmissions associated with a second control resource set pool index on multiple carriers associated with multiple timing advance groups, at least in part based on a 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 components, fewer components, different components, or differently configured components compared to those shown in Figure 11. Furthermore, two or more 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. In addition, or instead, a set of (one or more) components 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] Figure 12 shows an exemplary device 1200 for wireless communication. The device 1200 may be a network entity, or a network entity may include the device 1200. In some embodiments, the device 1200 comprises a receiving component 1202 and a transmitting component 1204 that can communicate with each other (for example, via one or more buses and / or one or more other components). As shown, the device 1200 may use the receiving component 1202 and the transmitting component 1204 to communicate with another device 1206 (such as a UE, base station, or another wireless communication device). As further shown, the device 1200 may include a communications manager 150. The communications manager 150 may include a timing configuration component 1208, among other examples.

[0143] In some embodiments, the device 1200 may be configured to perform one or more operations described herein with respect to Figures 5-6. In addition, or instead, the device 1200 may be configured to perform one or more processes described herein, such as process 900 in Figure 9, process 1000 in Figure 10, or a combination thereof. In some embodiments, the device 1200 and / or one or more components shown in Figure 12 may include one or more components of the network entity described with respect to Figure 2. In addition, or instead, one or more components shown in Figure 12 may be implemented within one or more components described with respect to Figure 2. In addition, or instead, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-temporary 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 reference signals, 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 embodiments, the receiving component 1202 may perform signal processing on the received communications (among other examples, filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) and provide the processed signals to one or more other components of the device 1200. In some embodiments, the receiving component 1202 may include one or more of the network entities described with respect to Figure 2, such as antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof.

[0145] The transmitting component 1204 may transmit communications such as reference signals, control information, data communications, or a combination thereof to the device 1206. In some embodiments, one or more other components of the device 1200 may generate communications and provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some embodiments, the transmitting component 1204 may perform signal processing on the generated communications (among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 1206. In some embodiments, the transmitting component 1204 may include one or more network entities described with respect to Figure 2, such as antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or a combination thereof. In some embodiments, the transmitting component 1204 may collate with the receiving component 1202 in a transceiver.

[0146] The transmitting component 1204 is associated with multiple timing advance groups and can transmit information scheduling uplink resources on carriers associated with one or more timing advance offsets for multiple timing advance groups. The receiving component 1202 can use the uplink resources to receive on carriers according to one or more timing advance offsets. The transmitting component 1204 can transmit information identifying a single timing advance offset common to multiple carriers. The receiving component 1202 can receive a first set of one or more uplink transmissions associated with a first control resource set pool index and a second set of one or more uplink transmissions associated with a second control resource set pool index on multiple carriers associated with multiple timing advance groups, at least in part based on a single timing advance offset. The timing configuration component 1208 can configure the 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 components, fewer components, different components, or differently configured components compared to those shown in Figure 12. Furthermore, two or more 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. In addition, or instead, a set of (one or more) 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 an overview of some aspects of this disclosure.

[0149] Embodiment 1: A method of wireless communication performed by a user device (UE), comprising: 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 a plurality of timing advance groups; and using the uplink resources to transmit on the carrier according to one or more timing advance offsets.

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

[0151] Embodiment 3: The method according to any one of Embodiments 1 to 2, wherein one or more other carriers associated with at least one of a plurality of timing advance groups are associated with one or more individual 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] Embodiment 4: The method according to any one of Embodiments 1 to 3, wherein one or more timing advance offsets are configured for each carrier, and one or more timing advance offsets include a first timing advance offset associated with a first timing advance group among a plurality of timing advance groups, and a second timing advance offset associated with a second timing advance group among a plurality of timing advance groups.

[0153] Embodiment 5: The method according to Embodiment 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] Embodiment 6: The method according to Embodiment 5, wherein the first common value is different from the second common value.

[0155] Embodiment 7: The method according to any one of Embodiments 1 to 6, wherein one or more timing advance offsets are configured for each timing advance group, and each timing advance group is configured using the corresponding timing advance offset.

[0156] Embodiment 8: The method according to Embodiment 7, wherein each first carrier among 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 among 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] Embodiment 9: A method of wireless communication performed by a user device (UE), comprising: receiving information identifying a single timing advance offset common to a plurality of carriers; and transmitting a first uplink transmission associated with a first control resource set pool index and a second uplink transmission associated with a second control resource set pool index over a plurality of carriers associated with a plurality of timing advance groups, at least in part on a single timing advance offset.

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

[0159] Embodiment 11: The method according to either Embodiment 9 or Embodiment 10, wherein receiving information identifying a single timing advance offset includes receiving a media access control (MAC) control element (CE) that carries a single timing advance offset common to a plurality of timing advance groups.

[0160] Embodiment 12: The method according to any one of embodiments 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 among 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 among a plurality of carriers associated with a second timing advance group identifier.

[0161] Embodiment 13: The method according to any one of Embodiments 9 to 12, wherein a first timing advance value for one or more first uplink transmissions associated with a first control resource set pool index is at least partially based on a timing advance command for a corresponding timing advance group among a plurality of timing advance groups, and a second timing advance value for one or more second uplink transmissions associated with a second control resource set pool index is at least partially based on a single timing advance offset for a corresponding timing advance group and a first timing advance value for the corresponding timing advance group.

[0162] Embodiment 14: The method according to any one of Embodiments 9 to 13, wherein receiving information identifying a single timing advance offset includes receiving a first media access control (MAC) control element (CE) carrying a single timing advance offset associated with a timing advance group identifier, and receiving a second MAC CE carrying a timing advance command associated with a timing advance group identifier.

[0163] Embodiment 15: The method according to any one of Embodiments 9 to 13, wherein receiving information identifying a single timing advance offset includes receiving a single media access control (MAC) control element (CE) that carries a single timing advance offset associated with a timing advance group identifier and a timing advance command associated with the timing advance group identifier.

[0164] Embodiment 16: A method of wireless communication performed by a network entity, comprising transmitting 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 a plurality of timing advance groups, and using the uplink resources to receive on the carrier according to one or more timing advance offsets.

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

[0166] Embodiment 18: The method according to Embodiment 16 or Embodiment 17, wherein one or more other carriers associated with at least one of a plurality of timing advance groups are associated with one or more individual 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] Embodiment 19: The method according to any one of Embodiments 16 to 18, wherein one or more timing advance offsets are configured for each carrier, and one or more timing advance offsets include a first timing advance offset associated with a first timing advance group among a plurality of timing advance groups, and a second timing advance offset associated with a second timing advance group among a plurality of timing advance groups.

[0168] Embodiment 20: The method according to Embodiment 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] Embodiment 21: The method according to Embodiment 20, wherein the first common value is different from the second common value.

[0170] Embodiment 22: The method according to any one of Embodiments 16 to 21, wherein one or more timing advance offsets are configured for each timing advance group, and each timing advance group is configured using the corresponding timing advance offset.

[0171] Embodiment 23: The method of Embodiment 22, wherein each first carrier among 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 among 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] Embodiment 24: A method of wireless communication performed by a network entity, comprising: transmitting information identifying a single timing advance offset common to a plurality of carriers; and receiving a first uplink transmission associated with a first control resource set pool index and a second uplink transmission associated with a second control resource set pool index on a plurality of carriers associated with a plurality of timing advance groups, at least in part on a single timing advance offset.

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

[0174] Embodiment 26: The method of either Embodiment 24 or 25, wherein transmitting information identifying a single timing advance offset includes transmitting a medium access control (MAC) control element (CE) that carries a single timing advance offset common to multiple timing advance groups.

[0175] Embodiment 27: The method according to any one of Embodiments 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 among 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 among a plurality of carriers associated with a second timing advance group identifier.

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

[0177] Embodiment 29: The method according to any one of Embodiments 24 to 28, wherein transmitting information identifying a single timing advance offset includes transmitting a first media access control (MAC) control element (CE) that carries a single timing advance offset associated with a timing advance group identifier, and transmitting a second MAC CE that carries a timing advance command associated with a timing advance group identifier.

[0178] Embodiment 30: The method according to any one of embodiments 24 to 28, wherein transmitting information identifying a single timing advance offset includes transmitting a single media access control (MAC) control element (CE) that carries a single timing advance offset associated with a timing advance group identifier and a timing advance command associated with the timing advance group identifier.

[0179] Embodiment 31: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, which are executable by the processor to cause the device to perform one or more of the methods from Embodiments 1 to 8.

[0180] Embodiment 32: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, each configured to implement one or more of the methods of Embodiments 1 to 8.

[0181] Embodiment 33: A wireless communication device comprising at least one means for carrying out one or more methods from Embodiments 1 to 8.

[0182] Embodiment 34: A non-temporary computer-readable medium storing code for wireless communication, wherein the code includes instructions that can be executed by a processor to implement one or more of the methods of Embodiments 1 to 8.

[0183] Embodiment 35: A non-temporary computer-readable medium storing a set of instructions for wireless communication, wherein the set of instructions includes 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 Embodiments 1 to 8.

[0184] Embodiment 36: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, which are executable by the processor to cause the device to perform one or more of the methods from Embodiments 9 to 15.

[0185] Embodiment 37: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, each configured to implement one or more of the methods of Embodiments 9 to 15.

[0186] Embodiment 38: A wireless communication device comprising at least one means for carrying out one or more methods from Embodiments 9 to 15.

[0187] Embodiment 39: A non-temporary computer-readable medium storing code for wireless communication, wherein the code includes instructions that can be executed by a processor to implement one or more of the methods of Embodiments 9 to 15.

[0188] Embodiment 40: A non-temporary computer-readable medium storing a set of instructions for wireless communication, wherein the set of instructions includes 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 Embodiments 9 to 15.

[0189] Embodiment 41: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, which are executable by the processor to cause the device to perform one or more of the methods from Embodiments 16 to 23.

[0190] Embodiment 42: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, each configured to implement one or more of the methods of Embodiments 16 to 23.

[0191] Embodiment 43: A wireless communication device comprising at least one means for carrying out one or more methods from Embodiments 16 to 23.

[0192] Embodiment 44: A non-temporary computer-readable medium storing code for wireless communication, wherein the code includes instructions that can be executed by a processor to implement one or more of the methods of Embodiments 16 to 23.

[0193] Embodiment 45: A non-temporary computer-readable medium storing a set of instructions for wireless communication, wherein the set of instructions includes 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 Embodiments 16 to 23.

[0194] Apparatus 46: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, which are executable by the processor to cause the device to perform one or more of the methods from Apparatus 24 to Apparatus 30.

[0195] Embodiment 47: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, each processor configured to implement one or more of the methods of Embodiments 24 to 30.

[0196] Embodiment 48: A wireless communication device comprising at least one means for carrying out one or more methods from Embodiments 24 to 30.

[0197] Apparatus 49: A non-temporary computer-readable medium storing code for wireless communication, wherein the code includes instructions that can be executed by a processor to implement one or more of the methods of Apparatus 24 to 30.

[0198] Embodiment 50: A non-temporary computer-readable medium storing a set of instructions for wireless communication, wherein the set of instructions includes 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 Embodiments 24 to 30.

[0199] The foregoing disclosures are illustrative and descriptive, but are not intended to be exhaustive or to limit the embodiments disclosed to the exact forms. Modifications and variations may be made in light of the foregoing disclosures or derived from the practices of the embodiments.

[0200] Where used herein, the term “component” is intended to be broadly interpreted as hardware and / or combinations of hardware and software. “Software” is broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, whether referred to by other names, including but not limited to software, firmware, middleware, microcode, hardware description language, or other similar terms. Where used herein, “processor” is implemented in hardware and / or combinations 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 combinations of hardware and software. The actual specialized control hardware code or software code used to implement these systems and / or methods is not limited to these embodiments. Therefore, a person skilled in the art will understand that software and hardware can be designed to implement systems and / or methods, at least in part, based on the descriptions herein; thus, the operation and behavior of systems and / or methods are described herein without reference to specific software code.

[0201] As used herein, "meeting a threshold" may, depending on the context, mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, or not equal to a threshold.

[0202] Where particular combinations of features are enumerated in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of various embodiments. Many of these features may be combined in ways not specifically enumerated in the claims and / or disclosed herein. The disclosure of various embodiments includes each dependent claim combined with all other claims within the set of claims. Where used herein, the phrase “at least one of” the list of items refers to any combination of those items, including a single member. 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 (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other order of a, b, and c).

[0203] None of the elements, actions, or commands used herein should be construed as important or essential unless expressly stated otherwise. Furthermore, 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 being referred to with respect to the definite article “the” and may be used interchangeably with “one or more.” Furthermore, 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 “just one” or similar words are 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 (for example, an element that “has” A may also have B). Furthermore, unless otherwise specified, the phrase "based on" is intended to mean "at least partially based on." Also, as used herein, the term "or" is intended to be inclusive when used consecutively, and may be used interchangeably with "and / or" unless otherwise specified (for example, when used in combination with "either" or "only one of").

Claims

1. User equipment (UE) for wireless communication, Memory and One or more processors coupled to the memory, Information is received to schedule uplink resources on a carrier associated with one or more timing advance offsets for multiple timing advance groups, which are associated with multiple timing advance groups. Using the uplink resource, transmit on the carrier according to the one or more timing advance offsets: One or more processors configured in such a way, A user device (UE) comprising, wherein the one or more timing advance offsets are configured for each carrier, and the carrier is associated with a single timing advance offset applicable to each of the multiple timing advance groups.

2. User equipment (UE) for wireless communication, Memory and One or more processors coupled to the memory, Information is received to schedule uplink resources on a carrier associated with one or more timing advance offsets for multiple timing advance groups, which are associated with multiple timing advance groups. Using the uplink resource, transmit on the carrier according to the one or more timing advance offsets: One or more processors configured in such a way, The system comprises, wherein one or more other carriers associated with at least one of the plurality of timing advance groups are associated with one or more individual timing advance offsets. A user device (UE) in which the one or more timing advance offsets and the one or more other timing advance offsets have a common value.

3. User equipment (UE) for wireless communication, Memory and One or more processors coupled to the memory, Information is received to schedule uplink resources on a carrier associated with one or more timing advance offsets for multiple timing advance groups, which are associated with multiple timing advance groups. Using the uplink resource, transmit on the carrier according to the one or more timing advance offsets: One or more processors configured in such a way, The system includes such that the one or more timing advance offsets are configured for each carrier. User equipment (UE) wherein the one or more timing advance offsets include a first timing advance offset associated with a first timing advance group among the plurality of timing advance groups, and a second timing advance offset associated with a second timing advance group among the plurality of timing advance groups.

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

5. The UE according to claim 4, wherein the first common value is different from the second common value.

6. A network entity for wireless communications, Memory and One or more processors coupled to the memory, Information is transmitted on a carrier associated with multiple timing advance groups and one or more timing advance offsets for said multiple timing advance groups to schedule uplink resources. Using the uplink resource, receive on the carrier according to the one or more timing advance offsets: One or more processors configured in such a way, A network entity comprising, wherein the one or more timing advance offsets are configured for each carrier, and the carrier is associated with a single timing advance offset applicable to each of the multiple timing advance groups.

7. A network entity for wireless communication, Memory and One or more processors coupled to the memory, Information is transmitted on a carrier associated with multiple timing advance groups and one or more timing advance offsets for said multiple timing advance groups to schedule uplink resources. Using the uplink resource, receive on the carrier according to the one or more timing advance offsets: One or more processors configured in such a way, The system comprises, wherein one or more other carriers associated with at least one of the plurality of timing advance groups are associated with one or more individual timing advance offsets. A network entity in which the one or more timing advance offsets and the one or more other timing advance offsets have a common value.

8. A network entity for wireless communication, Memory and One or more processors coupled to the memory, Information is transmitted on a carrier associated with multiple timing advance groups and one or more timing advance offsets for said multiple timing advance groups to schedule uplink resources. Using the uplink resource, receive on the carrier according to the one or more timing advance offsets: One or more processors configured in such a way, The system includes such that the one or more timing advance offsets are configured for each carrier. A network entity in which the one or more timing advance offsets include a first timing advance offset associated with a first timing advance group among the plurality of timing advance groups, and a second timing advance offset associated with a second timing advance group among the plurality of timing advance groups.

9. The first timing advance offset, each associated with a first common timing advance group, and another first timing advance offset associated with a first other carrier, have a first common value. The network entity according to claim 8, wherein the second timing advance offset, each associated with a second common timing advance group, and another second timing advance offset associated with a second other carrier, have a second common value.

10. The network entity according to claim 9, wherein the first common value is different from the second common value.

Images