Timing advance reporting format based on cell type

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may determine that it is communicating with a particular type of cell (e.g., an air-to-ground (ATG) cell), and may utilize a timing advance (TA) reporting format corresponding to the determined cell type. The TA reporting for the ATG cell may indicate the TA value according to a small time unit using all 16 bits of the TA reporting. A TA report for an ATG cell may utilize a subset of bits to indicate a symbol-level TA, and the remainder of the bits in the TA report may be unused. The TA report for the ATG cell may be a single eight-bit group TA report, including a reserved bit and a bit indicating a format for the TA report, and a TA value. The TA report may include a reservation bit and a TA value.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 791,804, filed August 1, 2024, entitled “TIMING ADVANCE REPORTING FORMATS BASED ON CELL TYPE”, and U.S. Provisional Patent Application No. 63 / 586,284, filed September 28, 2023, entitled “TIMING ADVANCE REPORTING FORMATS BASED ON CELL TYPE”, each of which is assigned to the assignee of this application, and each of which is expressly incorporated herein by reference. Technical Field

[0003] The following text relates to wireless communications, including time advance (TA) reporting formats based on cell type. Background Technology

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

[0005] The described technology relates to methods, systems, devices, and apparatuses supporting improved timing advance (TA) report formats based on cell type. For example, a user equipment (UE) may determine that it is communicating with a specific type of cell (e.g., an air-to-ground (ATG) cell) and may utilize a TA report format corresponding to the determined cell type. The TA report for an ATG cell may use all 16 bits of the TA report to indicate the TA value according to a small time unit (e.g., a sampling time unit). In some examples, the TA report for an ATG cell may utilize a subset of bits (e.g., 5 bits) to indicate the symbol-level TA, and the remaining bits in the TA report may be unused (e.g., empty bits). In some examples, the TA report for an ATG cell may be a single octet TA report. Two bits may be reserved, and a third bit may indicate that the TA report is an ATG cell TA report. The remaining 5 bits may indicate the TA value. Additionally or alternatively, the TA report may include three reserved bits and a 5-bit TA value (e.g., a Logical Channel Identifier (LCID) code point indicating the ATG cell report format). In some examples, TA threshold configuration can be indicated via control signaling (e.g., indicating a threshold for triggering TA reporting for a specific cell type, which may be symbol-based or based on sampling time units).

[0006] A method for wireless communication by a user equipment (UE) is described. The method may include: receiving information indicating that a cell corresponding to a network entity is an ATG cell; generating a TA report based on the information and in accordance with a format corresponding to ATG communication; and sending the TA report in accordance with the format.

[0007] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the memories. The one or more processors may be able to operate individually or jointly to execute code that causes the UE to: receive information indicating that a cell corresponding to a network entity is an ATG cell; generate a TA report based on the information and according to a format corresponding to ATG communication; and transmit the TA report according to the format.

[0008] Another UE for wireless communication is described. The UE may include: components for receiving information indicating that the cell corresponding to a network entity is an ATG cell; components for generating a TA report based on the information according to a format corresponding to ATG communication; and components for sending the TA report according to the format.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to perform the following operations: receiving information indicating that a cell corresponding to a network entity is an ATG cell; generating a TA report based on the information and in accordance with a format corresponding to ATG communication; and sending the TA report in accordance with the format.

[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, generating a TA report may include operations, features, components, or instructions for generating a TA value indicated by two octets in the TA report, each code point in the two octets corresponding to a corresponding sampling time unit in a set of multiple candidate sampling time units.

[0011] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, the reserved LCID code points include indications whose format corresponds to the granularity of the sampling time unit.

[0012] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, receiving information may include operations, features, components, or instructions for receiving a cell that supports a format corresponding to an ATG cell.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, generating a TA report may include operations, features, components, or instructions for generating a TA value indicated by a first subset of bits in a set of multiple bits of the TA report, each code point in the first subset of bits corresponding to a corresponding number of symbols, wherein a second portion of the bits in the set of multiple bits may be vacant.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the symbol duration corresponding to the TA value may be based on the subcarrier spacing that the UE can be configured with during the generation of the TA value.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, generating a TA report may include operations, features, components, or instructions for: setting the first bit of a set of multiple bits in the TA report to indicate a format corresponding to the TA report; generating a TA value indicated by a subset of bits in the set of multiple bits in the TA report, each code point in the subset of bits indicating a corresponding number of symbols; and setting one or more reserved bits to zero.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, one or more reserved bits, the first bit, and a subset of bits comprise a single octet of the TA report, and the symbol duration corresponding to the TA value may be based on the subcarrier spacing that the UE can be configured with during the generation of the TA value.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, generating a TA report may include operations, features, components, or instructions for: generating a TA value indicated by a subset of bits in a set of multiple bits of the TA report, each code point in the subset of bits indicating a corresponding number of symbols; and setting one or more reserved bits to zero.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, one or more reserved bits and subsets of bits include a single octet of the TA report, and the symbol duration corresponding to the TA value may be based on the subcarrier spacing that the UE can be configured with during the generation of the TA value.

[0019] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, one or more reserved bits, one or more bits indicating subcarrier spacing, and subsets of bits include a single octet of the TA report, and the symbol duration corresponding to the TA value may be based on the subcarrier spacing during the generation of the TA value.

[0020] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for receiving control signaling that indicates a threshold timing offset for triggering the transmission of a TA report, wherein the transmission of the TA report may be based on determining that the transmission timing value satisfies the threshold timing offset.

[0021] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, the threshold timing offset includes the number of symbols or the number of sampling time units.

[0022] A method for wireless communication by a network entity is described. The method may include: transmitting information indicating that the cell corresponding to the network entity is an ATG cell; receiving a TA report from a UE in a format corresponding to ATG communication in response to the transmission of the information; and communicating with the UE based on the TA report.

[0023] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the memories. The one or more processors may be able to operate individually or jointly to execute code to cause the network entity to: transmit information indicating that the cell corresponding to the network entity is an ATG cell; receive a TA report from a UE in a format corresponding to ATG communication in response to the transmission of the information; and communicate with the UE based on the TA report.

[0024] Another network entity for wireless communication is described. The network entity may include: components for transmitting information indicating that the cell corresponding to the network entity is an ATG cell; components for receiving a TA report from the UE in response to the transmission of information, according to a format corresponding to ATG communication; and components for communicating with the UE based on the TA report.

[0025] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to perform the following operations: sending information indicating that the cell corresponding to a network entity is an ATG cell; receiving a TA report from a UE in a format corresponding to ATG communication in response to the transmission of the information; and communicating with the UE based on the TA report.

[0026] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a TA report may include operations, features, components, or instructions for: TA values ​​indicated by bits in two octets of the TA report, each code point in the two octets of the TA report corresponding to a corresponding sampling time unit in a set of multiple candidate sampling time units.

[0027] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the reserved LCID code points include indications that correspond to the granularity of the format and the sampling time unit.

[0028] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, transmitting information may include operations, features, components, or instructions for transmitting an indication that the cell supports a format corresponding to an ATG cell.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a TA report may include operations, features, components, or instructions for: a TA value indicated by a first subset of bits in a set of multiple bits in the TA report, each code point in the first subset of bits corresponding to a corresponding number of symbols, wherein a second portion of the bits in the set of multiple bits may be vacant.

[0030] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the symbol duration corresponding to the TA value may be based on the subcarrier spacing that the UE can configure.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a TA report may include operations, features, components, or instructions for: a first bit in a set of bits indicating a format corresponding to the TA report; a TA value indicated by a subset of bits in the set of bits of the TA report, each code point in the subset of bits indicating a corresponding number of symbols; and one or more reserved bits.

[0032] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, one or more reserved bits, the first bit, and a subset of bits comprise a single octet of the TA report, and the symbol duration corresponding to the TA value may be based on the subcarrier spacing that the UE can configure.

[0033] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a TA report may include operations, features, components, or instructions for: a TA value indicated by a subset of bits in a set of multiple bits of the TA report, each code point in the subset of bits indicating a corresponding number of symbols; and one or more reserved bits.

[0034] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, one or more reserved bits and subsets of bits include a single octet of the TA report, and the symbol duration corresponding to the TA value may be based on the subcarrier spacing that the UE can configure.

[0035] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, one or more reserved bits, one or more bits indicating subcarrier spacing, and subsets of bits include a single octet of TA report, the symbol duration corresponding to the TA value being based on the subcarrier spacing that the UE can configure.

[0036] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending a threshold timing offset that indicates the transmission of a TA report, wherein receiving a TA report may satisfy the threshold timing offset based on the transmission timing value.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the threshold timing offset includes the number of symbols or the number of sampling time units. Attached Figure Description

[0038] Figure 1 Examples of wireless communication systems supporting a timing advance (TA) report format based on cell type, according to one or more aspects of this disclosure, are shown.

[0039] Figure 2 Examples of wireless communication systems supporting cell type-based TA report formats are shown in accordance with one or more aspects of this disclosure.

[0040] Figure 3 Examples of TA reporting schemes supporting cell type-based TA reporting formats are shown, according to one or more aspects of this disclosure.

[0041] Figure 4 Examples of TA reporting schemes supporting cell type-based TA reporting formats are shown, according to one or more aspects of this disclosure.

[0042] Figure 5 Examples of TA reporting schemes supporting cell type-based TA reporting formats are shown, according to one or more aspects of this disclosure.

[0043] Figure 6 Examples of TA reporting schemes supporting cell type-based TA reporting formats are shown, according to one or more aspects of this disclosure.

[0044] Figure 7 An example of a process flow supporting a cell type-based TA report format is shown, according to one or more aspects of this disclosure.

[0045] Figure 8 and Figure 9 A block diagram is shown that supports a cell type-based TA report format according to one or more aspects of this disclosure.

[0046] Figure 10 A block diagram is shown that supports a communication manager with a TA report format based on cell type, according to one or more aspects of this disclosure.

[0047] Figure 11 A diagram of a system including a device supporting a cell type-based TA report format is shown, according to one or more aspects of this disclosure.

[0048] Figure 12 and Figure 13 A block diagram is shown that supports a cell type-based TA report format according to one or more aspects of this disclosure.

[0049] Figure 14 A block diagram is shown that supports a communication manager with a TA report format based on cell type, according to one or more aspects of this disclosure.

[0050] Figure 15 A diagram of a system including a device supporting a cell type-based TA report format is shown, according to one or more aspects of this disclosure.

[0051] Figures 16 to 19 A flowchart illustrating a method for supporting a cell type-based TA report format according to one or more aspects of this disclosure is shown. Detailed Implementation

[0052] User equipment (UE) (e.g., airborne UEs, such as those on aircraft) can travel at high altitudes and at high speeds. This can cause rapid changes in the round-trip time (RTT) of signaling between the UE and terrestrial network entities. Rapidly changing Doppler effects can also be observed in radio transmissions between the UE and one or more network entities. For at least these reasons, airborne UEs can benefit from sending timing advance (TA) reports, which indicate TA values. TA values ​​can be used to offset timing issues to align wireless communications. However, some wireless communication technologies (e.g., for some cell types) support TA reports comprising two octets, capable of indicating TA values ​​at the slot-level granularity. Airborne UEs, such as those on aircraft, may be able to report TA values ​​at a different granularity (e.g., timing issues may occur at a different granularity for airborne UEs than for other terrestrial UEs).

[0053] For example, a TA report for some cells may include a 16-bit Media Access Control (MAC) control element (CE), which includes two octets (e.g., two reserved bits and 14 bits for indicating the slot-level TA value). Some cells (e.g., air-to-ground (ATG) cells) may support symbol-level TA reporting, which can be completed using fewer bits than the 14 bits available in some TA report formats. In such examples, the TA report may not utilize the increased granularity available in the two-octet TA report, or may effectively use fewer bits for the symbol-level TA report. In this case, the remaining available bits may go unused, leading to increased signaling overhead, increased processing at the UE, increased latency, and inefficient use of available computing and system resources.

[0054] According to the techniques described herein, a UE can determine that it is communicating with a specific type of cell (e.g., an ATG cell). Based on the determined cell type, the UE can utilize a TA report format corresponding to the determined cell type. For example, a TA report for an ATG cell can use all 16 bits of the TA report (e.g., up to 57,344 values) to indicate the TA value according to a small time unit (e.g., a sampling time unit). In some examples, a TA report for an ATG cell can utilize a subset of bits (e.g., 5 bits) to indicate the symbol-level TA, and the remaining bits in the TA report may be unused (e.g., empty bits). In some examples, a TA report for an ATG cell can be a single octet TA report. Two bits may be reserved, and a third bit may indicate that the TA report is an ATG cell TA report. The remaining 5 bits may indicate the TA value. Additionally or alternatively, the TA report may include three reserved bits and a 5-bit TA value (e.g., a Logical Channel Identifier (LCID) code point may indicate the ATG cell report format). In some examples, TA threshold configuration can be indicated via control signaling (e.g., indicating a threshold for triggering TA reporting for a specific cell type, which may be symbol-based or based on sampling time units).

[0055] The various aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to wireless communication systems, TA reporting schemes, and process flows. The various aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to cell type-based TA reporting formats.

[0056] Figure 1 Examples of a wireless communication system 100 supporting a cell type-based TA report format according to one or more aspects of this disclosure are shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0057] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0058] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0059] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0060] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0061] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0062] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0063] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0064] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0065] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), where the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0066] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

[0067] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0068] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support a cell type-based TA report format as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

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

[0071] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0072] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0073] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0074] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0075] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0076] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( The carrier can be divided into one or more BWPs with the same or different parameter sets. In some examples, UE 115 can be configured using multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0077] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0078] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

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

[0080] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

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

[0082] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

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

[0084] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0085] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

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

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

[0088] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0089] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

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

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

[0092] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the region from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequencies (HF) or very high frequencies (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0093] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted for transmissions using one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

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

[0095] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

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

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

[0098] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

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

[0100] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

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

[0102] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0103] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0104] According to the techniques described herein, UE 115 can determine that it is communicating with a specific type of cell (e.g., an ATG cell). Based on the determined cell type, the UE can utilize a TA report format corresponding to the determined cell type. For example, a TA report for an ATG cell can use all 16 bits of the TA report (e.g., up to 57,344 values) to indicate the TA value according to a small time unit (e.g., a sampling time unit). In some examples, a TA report for an ATG cell can utilize a subset of bits (e.g., 5 bits) to indicate the symbol-level TA, and the remaining bits in the TA report may be unused (e.g., empty bits). In some examples, a TA report for an ATG cell can be a single octet TA report. Two bits may be reserved, and a third bit may indicate that the TA report is an ATG cell TA report. The remaining 5 bits may indicate the TA value. Additionally or alternatively, the TA report may include three reserved bits and a 5-bit TA value. In some examples, TA threshold configuration can be indicated via control signaling (e.g., indicating a threshold for triggering TA reporting for a specific cell type, which may be symbol-based or based on sampling time units).

[0105] Figure 2 An example of a wireless communication system 200 supporting a cell type-based TA report format according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 115-a and one or more network entities 105 (e.g., network entity 105-a and network entity 105-b), which may be referenced... Figure 1 Examples of the corresponding devices described.

[0106] In some examples, the wireless communication system 200 may support communication between network entity 105 and one or more UEs 115. In some examples, UE 115-a may be a mobile UE moving at a high speed. For example, UE 115-a may be an airborne UE, such as an aircraft (e.g., a device carried on board or attached to an aircraft). For example, UE 115-a may operate at high altitudes (e.g., approximately 10 kilometers (km)). In some examples, network entity 105 may communicate with airborne UE 115. For example, network entity 105-a may be an ATG network entity (e.g., an ATG gNB or ATG eNB, etc.), and network entity 105-b may be an ATG network entity. In such examples, network entity 105-a may support communication in a first cell (e.g., via a first coverage area 110-a), and network entity 105-b may support communication in a second cell (e.g., via a second coverage area 110-b). Network entity 105 can support wireless communication within the corresponding cell range (e.g., 200km to 300km).

[0107] In some examples, ATG communication may rely on frequency pre-compensation due to Doppler effects (e.g., due to the high mobility, speed, and altitude of UE 115-a). UE 115-a may be GNSS-capable and have access to the location of ATG network entity 105. In some examples, UE 115-a may (e.g., via network entity 105) receive control signaling indicating ATG cell information. For example, system information (e.g., a System Information Block (SIB)) may indicate ATG network entity reference locations (e.g., for network entity 105-a and coverage area 110-a), cell-specific information (such as offset values ​​(K-offset) used for timing and communication), and so on. Such control signaling may also include broadcast information, such as neighboring cell reference locations (e.g., for network entity 105-b and coverage area 110-b).

[0108] Some cells (e.g., ATG cells) can support Time Division Duplex (TDD) operation. The network can rely on information about the latest or most recent TA (Transmission Acquisition) information at UE 115-a to efficiently schedule uplink and downlink subframes. Therefore, the UE can send TA reports indicating TA values ​​to network entities of a given cell (e.g., network entity 105-a or network entity 105-b). The network can utilize such TA values ​​to mitigate the Doppler effect of highly mobile UE 115-a. In some examples, the wireless communication system 200 can support optional TA reporting for ATG UE 115 (e.g., UE 115-a) based on mechanisms (e.g., as described herein) to assist the network in reducing protection period (GP) overhead for TDD systems. ATG cells have a coverage range of up to 300 km.

[0109] Different cell types may support TA values ​​at different granularities. For example, some wireless communication systems (e.g., non-terrestrial network (NTN) systems) may support TA reporting at a first granularity. In such an example, TA reporting triggering can be configured at UE 115, and the TA report may be based on a 1ms slot length. This TA report may include a fixed MAC-CE length of two bytes, and the MAC-CE may include 16 bits (e.g., two octets): two reserved bits and 14 bits for the TA value that can be used for the TA report. For some cells (e.g., NTN cells), the TA report format may indicate at least an integer number of slots based on the subcarrier spacing (e.g., 15kHz), where the integer number of slots is greater than or equal to the TA value.

[0110] However, some cells can support TA values ​​at different granularities. For example, ATG cells support different thresholds for TA reporting (e.g., timing offset) and TA values ​​for ATG cells can be defined based on symbols (e.g., rather than time slots). TA reporting for ATG cells can be performed at the symbol level (e.g., for coverage areas up to 300 km). Symbol duration can be based on SCS (e.g., 15 kHz or 30 kHz). In some examples, TA values ​​for ATG cells can range from 1 symbol to 29 symbols.

[0111] UE 115-a can support TA reporting for a single cell type (e.g., NTN cell). However, reporting TA values ​​at the symbol level (e.g., rather than the slot level) may not utilize the same number of bits. That is, while 14 bits of the two octet MAC-CE can be used to indicate (e.g., for NTN cells) slot-based TA values, fewer bits are available to efficiently indicate (e.g., for ATG cells) symbol-based TA values. In some examples, using a different TA reporting format to report ATG TA values ​​may result in inefficiently sending large TA reports (e.g., requiring only a smaller number of bits for TA values), increased signaling overhead, reduced throughput, increased latency, and increased system latency. Additionally, without a mechanism for identifying other TA formats by the receiving network entity 105, using another TA format may lead to communication failures, timing problems, and further increased system latency, etc.

[0112] The techniques described herein describe mechanisms for making TA reports using a cell-specific TA report format. For example, UE 115-a may use a first TA report format to communicate with a first type of cell (e.g., an NTN cell) and a second TA report format to communicate with a second type of cell (e.g., an ATG cell). The techniques described herein may also support rules or procedures for network entity 105 to interpret such TA report formats (e.g., techniques for indicating or determining when a TA report is an ATG TA report or another type of TA report). Although described and illustrated with reference to ATG cells in some cases, the techniques described herein are applicable to a variety of cell types (e.g., different TA report formats for different types of cells may include ATG cells, NTN cells, cells for onboard UE 115, high mobility cells, etc.).

[0113] Figure 3 An example of a TA reporting scheme 300 supporting a cell type-based TA reporting format according to one or more aspects of this disclosure is shown. The TA reporting scheme 300 may be implemented by, or by, aspects of wireless communication system 100 and wireless communication system 200. For example, a UE (e.g., such as UE 115-a) and one or more network entities (e.g., network entity 105, such as network entity 105-a and network entity 105-b) may communicate with each other according to the TA reporting scheme 300.

[0114] In some examples, a UE connected to a specific cell type (e.g., an ATG cell) may report TA granularity with one symbol and TA values ​​ranging from one to 28 symbols. This TA reporting granularity may correspond to one or more SCSs (e.g., 15 kHz and 30 kHz). Symbol duration may depend on the SCS (e.g., 66.67 μs for a 15 kHz SCS and 33.33 μs for a 30 kHz SCS). However, as described herein, fewer bits than are available in the TA reporting message can be used to indicate TA values ​​ranging from one to 28 symbols. For example, a TA reporting message for slot-based TA values ​​may include two octets (e.g., 16 bits). One or more (e.g., two) bits may be reserved, and one or more bits (e.g., 14 bits) may be used to indicate TA values. However, a UE (e.g., UE 115-a connected to an ATG cell) may be able to use fewer bits to indicate symbol-level TA values ​​(e.g., 5 bits).

[0115] In some examples, to effectively utilize the available bits in the TA report, the UE may report the exact TA value (e.g., instead of reporting an integer value representing the number of symbols greater than the exact TA value). Exact TA value reporting can utilize a higher number of bits and is more specific and precise than symbol-level TA reporting. The exact TA value calculation can be a fraction of a time interval (e.g., a fraction of symbols) and can be referred to as the smallest unit of time. (For example, (ns) or sampling time unit ((For example, (ns). For example, the smallest unit of time. It can be defined as ,in Hz and among them The sampling time unit can be defined. ,in ,in Hz, and among them .

[0116] The TA reporting granularity can be defined (e.g., in one or more standard documents) based on a format that supports any SCS (e.g., based on the smallest time unit). For example, such TA reporting granularity could be applicable to a 60kHz SCS, etc. For a 15kHz SCS, in order to report the threshold number of 28 symbols, the threshold number of code points could be defined as... Therefore, 16 code points can be used to indicate the exact TA value using small time increments (e.g., or ).

[0117] In some examples, the UE can access an ATG cell and can send a TA report indicating an exact TA value (e.g., or a near-exact TA value). In such examples, for an ATG cell, the TA report can use a complete two-octet bit string indicating the TA value (e.g., each code point in 16 bits indicates one of 57,344 values). Each candidate TA value (e.g., each code point in the 16-bit TA value) can indicate a small time unit, such as a sampling time unit. .

[0118] In some examples, the TA report format used by the UE may depend on the type of cell the UE is communicating with. For a first type of cell (e.g., an NTN cell), the UE may send a TA report according to a first TA report format, which may include a MAC-CE consisting of 16 bits: one or two reserved bits and 14 bits for a time slot-based TA value. This TA report format may include (e.g., for the TA value) a TA field, which uses a specific SCS (e.g., 15 kHz) greater than or equal to the exact TA value to indicate the minimum integer number of time slots. For a second type of cell (e.g., an ATG cell), the UE may send a TA report according to a second TA report format (e.g., including a 16-bit MAC-CE, all 16 bits being based on...). The TA report is sent using a granularity (indicating the TA value). This TA report format for ATG cells can be defined in one or more standard documents or configured by the network at the UE. In an ATG cell, the TA field indicating the TA value can indicate a small time unit (e.g., sampling time unit). The number of TA fields is specified, and the length of the TA field can be 16 bits. The UE can determine which TA report format to use based on the cell type (e.g., it can receive information indicating the cell type from network entities, such as cell identifier, list of neighboring cells, cell location, coverage area, etc.).

[0119] The network entity receiving the TA report can determine the type of the TA report and thus successfully decode and read it. In some examples, the type of the TA report can be implicit (e.g., if the network entity supports ATG cells, it can expect to receive TA reports according to the ATG TA report format). In some examples, the UE can send an explicit indication of the type of TA report. For example, a reserved LCID code point can be used to indicate the TA format type (e.g., the LCID code point can indicate that the TA report corresponds to the TA format used for ATG cells, including a 16-bit TA report indicating the exact TA value according to the sampling time unit or minimum time unit).

[0120] Figure 4An example of a TA reporting scheme 400 supporting a cell type-based TA reporting format according to one or more aspects of this disclosure is shown. TA reporting scheme 400 may be implemented by or by aspects of wireless communication system 100, wireless communication system 200, and TA reporting scheme 300. For example, a UE (e.g., such as UE 115-a) and one or more network entities (e.g., network entity 105, such as network entity 105-a and network entity 105-b) (which may be referenced) Figures 1 to 3 (Examples of the corresponding devices described) can communicate with each other according to TA report scheme 400.

[0121] In some examples, the UE may send a TA report including a TA value 405, which utilizes only the bits required to indicate the number of symbols (e.g., 1-28 symbols). For example, the UE may use 5 bits from the available bits in the TA report to indicate the symbol-level TA value 405. If the TA report includes one or more reserved bits 410 (e.g., reserved bit 410-a and reserved bit 410-b, both set to 0), the remaining bits of the TA report may be ignored. For example, 14 bits of the TA report may be used (e.g., without changing the report size for different cell types), with only values ​​from 1 to 28 indicated by the code points of TA value 405, and the remaining available values ​​(e.g., all other code points in the TA field) ignored. In some examples, only 5 bits of the TA report are available for TA value 405, and the remaining bits (e.g., 9 bits) may be ignored.

[0122] In some examples, the use of the TA report (e.g., which code point is available for TA value 405) may depend on the cell type with which the UE is communicating. For example, for some cell types (e.g., NTN cell type) and in some frequency bands (e.g., FR 1), the TA field may use an SCS greater than or equal to TA value 405 (e.g., 15 kHz) to indicate the minimum integer number of time slots. In the case of ATG access, the TA field may indicate the minimum integer number of symbols greater than or equal to TA value 405. Symbol duration may be based on the SCS currently configured for the UE (e.g., via control signaling indicating the SCS used for the UE). In some examples, the SCS may be 15 kHz or 30 kHz, in which case the UE may indicate a value from 1 to 28 for TA value 405 in an ATG cell. In some examples, the UE may determine which TA report format to use based on the cell type (e.g., information indicating the cell type, such as cell identifier, list of neighboring cells, cell location, coverage area, etc., may be received from network entities).

[0123] Figure 5An example of a TA reporting scheme 500 supporting a cell type-based TA reporting format according to one or more aspects of this disclosure is shown. TA reporting scheme 500 may implement, or be implemented by, aspects of wireless communication system 100, wireless communication system 200, TA reporting scheme 300, or TA reporting scheme 400. For example, a UE (e.g., such as UE 115-a) and one or more network entities (e.g., network entity 105, such as network entity 105-a and network entity 105-b) (which may be referenced) Figures 1 to 4 The example of the corresponding device described can communicate with each other according to TA report scheme 500.

[0124] In some examples, the UE may send a TA report that is smaller for some cell types and larger for others. For example, for an ATG cell, the UE may use one or more bits (e.g., 5 bits) to indicate the TA value. The TA report may include one or more reserved bits 510 (e.g., reserved bits 510-a and 510-b). One or more bits (such as bit 515 (e.g., another reserved bit or a specially designated bit)) may be used to indicate the TA format of the TA report (e.g., a TA format that indicates the TA value in units of the number of symbols). Such a TA report may include a fixed-size MAC-CE (e.g., one octet). The TA report may include one or more reserved bits 510 (e.g., set to 0). Bit 515 may indicate the type of TA report format. For example, in a first-type cell (e.g., an NTN cell), bit 515 may be set to 0 (e.g., in this case, the TA report may include a MAC-CE size of two octets). In a second-type cell (e.g., an ATG cell), bit 515 may be set to the value 1. When bit 515 is set to 1, TA reports that MAC-CE can have a fixed size of an octet.

[0125] In Type 1 cells (e.g., NTN cells) and in some frequency bands (e.g., FR 1), when bit 515 is set to 0, the TA field 505 can use an SCS greater than or equal to the TA value (e.g., 15 kHz) to indicate the minimum integer number of time slots. If bit 515 is set to 0, the length of the TA field 505 can be larger (e.g., 14 bits). In some frequency bands (e.g., FR 1), when bit 515 is set to 1, the TA field 505 can indicate the minimum integer number of symbols greater than or equal to the TA value. The symbol duration can be based on the SCS currently configured for the UE (e.g., in some examples, the SCS can be 15 kHz or 30 kHz). When bit 515 is set to 1, the length of the TA field can be smaller (e.g., 5 bits). Reference Figure 5The described technique can be similarly applied to different bit values ​​(e.g., for bit 515, where 0 or 1 can be defined to indicate an ATG cell or another type of cell), or to indicators of different sizes (e.g., a larger number of bits (such as one or more reserved bits 510) can be used to indicate various types of cells and TA report formats).

[0126] In some examples, if a cell supports this type of TA report, then this TA report format can be used in any cell. In some examples, a cell (e.g., a network entity corresponding to the cell) can send control signaling instructing the network entity to support the TA report format of TA report scheme 500, and the UE can send this TA report based on the control signaling.

[0127] Figure 6 An example of a TA report scheme 600 supporting a cell type-based TA report format according to one or more aspects of this disclosure is shown. TA report scheme 600 may implement, or be implemented by, aspects of wireless communication system 100, wireless communication system 200, TA report scheme 300, TA report scheme 400, or TA report scheme 500. For example, a UE (e.g., such as UE 115-a) and one or more network entities (e.g., network entity 105, such as network entity 105-a and network entity 105-b) (which may be referenced) Figures 1 to 5 The example of the corresponding device described can communicate with each other according to TA report scheme 600.

[0128] In some examples, the UE may send a TA report that is smaller for some cell types and larger for others. For example, for an ATG cell, the UE may use one or more bits (e.g., 5 bits) to indicate the TA value. The TA report may include one or more reserved bits 610 (e.g., reserved bits 610-a, 610-b, and 610-c). This type of TA report may include a fixed-size MAC-CE (e.g., one octet). The TA report may also include one or more reserved bits 610 (e.g., set to 0).

[0129] In some examples, the format of the TA report (e.g., a single octet including one or more bits indicating the TA value and one or more (e.g., 3) reserved bits) may be reserved for a specific cell type (e.g., for an ATG cell). In some examples, reserved LCID code points (e.g., separate from the octet) may be used to indicate the format of the TA report.

[0130] In first-type cells (e.g., NTN cells) and in some frequency bands (e.g., FR 1), the TA field 605 may use an SCS greater than or equal to the TA value (e.g., 15 kHz) to indicate the minimum integer number of time slots. The length of the TA field 605 may be relatively large (e.g., 14 bits). In some frequency bands (e.g., FR 1), for second-type cells (e.g., ATG cells), the TA field 605 may indicate the minimum integer number of symbols greater than or equal to the TA value. The symbol duration may be based on the SCS currently configured for the UE (e.g., in some examples, the SCS may be 15 kHz or 30 kHz). The length of the TA field for second-type cells (e.g., for symbol-level TA values) may be relatively small (e.g., 5 bits).

[0131] In some examples, the UE may include an indication of the SCS interval used to determine symbol duration in the TA report. For example, one or more of the reserved bits 610 or one or more additional bits (e.g., code points or reserved bits 610 in the TA report) may indicate the number of symbols indicated by TA field 605 and which SCS is used to determine symbol duration. For example, one of the reserved bits 610 may be used to indicate the SCS (e.g., 15 kHz or 30 kHz).

[0132] Figure 7 An example of a process flow 700 supporting a cell type-based TA report format according to one or more aspects of this disclosure is shown. Process flow 700 may implement, or be implemented by, aspects of wireless communication system 100, wireless communication system 200, TA report scheme 300, TA report scheme 400, TA report scheme 500, or TA report scheme 600. For example, the process flow may include one or more network entities 105-c and UE 115-b, which may be references... Figures 1 to 6 Examples of the corresponding devices described.

[0133] In some examples, at 705, UE 115-b may receive (e.g., from network entity 105, such as network entity 105-c) a threshold timing offset for a cell type (e.g., for an ATG cell). The threshold timing offset (e.g., a threshold) may be an information element (IE) in control signaling (e.g., RRC signaling). In some examples, UE 115-b may receive configuration signaling (e.g., advance timing report configuration signaling (such as TAR-Config IE), which may include TAR-Config-r17 or TAR-Config-r18 IE).

[0134] In some examples, a threshold timing offset can indicate the timing offset experienced by UE 115-b, which triggers the generation and transmission of a TA report. In some examples, UE 115-b can generate a TA report (e.g., at 715) and transmit a TA report (e.g., at 720) based on receiving a threshold timing offset at 705 (e.g., based on determining that the timing offset meets a timing threshold).

[0135] Threshold timing offsets can be provided based on the number of symbols (e.g., ranging from 1 to 14 symbols, with spare values) (e.g., via control signaling at 705). For example, the TAR-Config IE may include the following information:

[0136]

[0137] In some examples, it can be based on, for example, sampling time units. (For example, a time unit with a 16-bit integer value) to provide (for example, via control signaling 705) a threshold timing offset. In such an example, the TAR-Config IE may include the following information:

[0138]

[0139]

[0140] At 710, UE 115-b may receive information indicating that the cell corresponding to network entity 105-c is a specific type of cell (e.g., an ATG cell). This information may include explicit signaling (e.g., cell discovery information, a list of neighboring cells, a cell identifier, etc.). In some examples, UE 115-b may infer the existence of an ATG cell (e.g., based on signaling, utilized resources, one or more rules or conditions, etc.).

[0141] At 715, UE 115-b can generate a TA report based on information received or identified at 710 (e.g., based on determining that the cell served by network entity 105-c is an ATG cell). The TA report can be generated according to a format corresponding to ATG communication (e.g., specific to ATG cells).

[0142] In some examples, such as reference Figure 3 In more detail, generating a TA report may include generating a TA value indicated by the bits of two octets in the TA report. Each code point in the two octets of the TA report may be associated with a corresponding sampling time unit in a plurality of candidate sampling time units (e.g., Correspondingly, in such examples, 16 bits of the TA report (e.g., two octets) can be used to indicate the exact TA value or a value closer to the exact TA value (e.g., rather than rounding up to the next integer value of the symbol or time slot). This allows for increased granularity of the TA report and improved accuracy. In some examples, reserved LCID code points can indicate that the format corresponds to the granularity of the sampling time unit (e.g., rather than the symbol or time slot). In some examples, UE 115-b can receive, for example, an indication from network entity 105-c that network entity 105-c supports this format for TA reports (e.g., via cell information at 710 or via other control signaling), and can send TA reports based on this according to the supported TA report format.

[0143] In some examples, such as reference Figure 4 In more detail, generating a TA report may include generating a TA value indicated by a first subset of the bits in the TA report. Each code point in the first subset of bits (e.g., 5 bits) may correspond to a corresponding number of symbols (e.g., 1 to 28 symbols). In such examples, a second portion of the bits (e.g., 9 bits) may be omitted (e.g., it may be a blank bit). In some examples, the symbol duration corresponding to the TA value may be based on the SCS configured for UE 115-b during the generation of the TA value (e.g., the TA report indicates the number of symbols, each with a symbol duration based on the SCS currently configured for UE 115-b).

[0144] In some examples, such as reference Figure 5 In more detail, generating a TA report may include setting the first bit of the TA report to indicate the format of the TA report (e.g., indicating a fixed 1-byte MAC-CE size for an ATG cell). The UE 115-b may generate a TA value indicated by a subset of the bits in the TA report (e.g., 5 bits), and may set one or more reserved bits to zero. In some examples, one or more reserved bits, the first bit indicating the format, and the TA value may be included in a single octet of the TA report. In some examples, the symbol duration corresponding to the TA value may be based on the SCS configured on the UE 115-b during the generation of the TA value (e.g., the number of symbols indicated in the TA report, each symbol having a symbol duration based on the currently configured SCS for the UE 115-b).

[0145] In some examples, such as reference Figure 6In more detail, generating a TA report may include setting one or more reserved bits (e.g., 3 bits) to zero, and generating a TA value indicated by a subset of the bits in the TA report (e.g., 5 bits), each code point indicating a corresponding number of symbols. In some examples, one or more reserved bits and the subset of bits indicating the TA value may be a single octet of the TA report. In some examples, one or more reserved bits, one or more bits indicating the SCS, and the subset of bits indicating the TA value may be included in a single octet of the TA report. In some examples, the symbol duration corresponding to the TA value may be based on the SCS configured on the UE 115-b during the generation of the TA value, or the SCS indicated by the UE 115-b in the TA report (e.g., the TA report indicates the number of symbols, each symbol having a symbol duration based on the currently configured SCS or the SCS reported in the TA report).

[0146] At 720, UE 115-b may (e.g., send a TA report to network entity 105-c). At 725, network entity 105-c may communicate with UE 115-b based on the received TA report (e.g., timing may be compensated based on the TA value reported in the TA report).

[0147] Figure 8 A block diagram 800 of a device 805 supporting a cell type-based TA report format according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805 or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0148] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with cell type-based TA report formats). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0149] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with cell type-based TA report formats). In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0150] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the cell type-based TA report format as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0151] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0152] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0153] In some examples, the communication manager 820 may be configured to use or otherwise cooperate with the receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0154] The communication manager 820 can support wireless communication according to the examples disclosed herein. For example, the communication manager 820 can be configured or operable to support components for receiving information indicating that the cell corresponding to a network entity is an ATG cell. The communication manager 820 can be configured or operable to support components for generating TA reports based on information according to a format corresponding to ATG communication. The communication manager 820 can be configured or operable to support components for sending TA reports according to a specified format.

[0155] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for TA reporting, thereby enabling more efficient use of system resources, increased throughput, improved communication reliability and reduced system latency.

[0156] Figure 9 A block diagram 900 is shown of a device 905 supporting a cell type-based TA report format according to one or more aspects of this disclosure. Device 905 may be an example of aspects of device 805 or UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905 or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0157] Receiver 910 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with cell type-based TA report formats). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

[0158] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with cell type-based TA report formats). In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0159] Device 905 or its various components may be examples of parts for performing various aspects of the cell type-based TA report format as described herein. For example, communication manager 920 may include cell type manager 925, TA report format manager 930, TA report manager 935, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use or otherwise cooperate with receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0160] The communication manager 920 can support wireless communication according to the examples disclosed herein. The cell type manager 925 is capable of, configured to, or operable to support components for receiving information indicating that a cell corresponding to a network entity is an ATG cell. The TA report format manager 930 is capable of, configured to, or operable to support components for generating TA reports based on information according to a format corresponding to ATG communication. The TA report manager 935 is capable of, configured to, or operable to support components for sending TA reports according to a format.

[0161] Figure 10A block diagram 1000 is shown of a communication manager 1020 supporting a cell type-based TA report format according to one or more aspects of this disclosure. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of parts for performing various aspects of the cell type-based TA report format as described herein. For example, the communication manager 1020 may include a cell type manager 1025, a TA report format manager 1030, a TA report manager 1035, a timing offset manager 1040, an SCS manager 1045, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0162] The communication manager 1020 can support wireless communication according to the examples disclosed herein. The cell type manager 1025 is capable of, configured to, or operable to support components for receiving information indicating that a cell corresponding to a network entity is an ATG cell. The TA report format manager 1030 is capable of, configured to, or operable to support components for generating TA reports based on information according to a format corresponding to ATG communication. The TA report manager 1035 is capable of, configured to, or operable to support components for sending TA reports according to a format.

[0163] In some examples, to support the generation of TA reports, the TA report format manager 1030 is capable of, configured to, or operable to support components for generating TA values ​​indicated by bits in two octets of the TA report, each code point in the two octets of the TA report corresponding to a corresponding sampling time unit in a set of multiple candidate sampling time units.

[0164] In some examples, the reserved logical channel identifier code points include an indication of the format corresponding to the granularity of the sampling time unit.

[0165] In some examples, to support receiving information, the cell type manager 1025 can be configured or operable to support components for receiving instructions that the cell supports a format corresponding to an ATG cell.

[0166] In some examples, in order to support the generation of TA reports, the TA report format manager 1030 is capable of, configured to, or operable to support components for generating TA values ​​indicated by a first subset of bits in a set of multiple bits in a TA report, each code point in the first subset of bits corresponding to a corresponding number of symbols, wherein a second portion of the bits in the set of multiple bits is a vacancy.

[0167] In some examples, the symbol duration corresponding to the TA value is based on the subcarrier spacing configured for the UE during the generation of the TA value.

[0168] In some examples, to support the generation of TA reports, the TA report format manager 1030 is capable of, configured to, or operable to support a component for setting the first bit of a set of multiple bits in the TA report to indicate a format corresponding to the TA report. In some examples, to support the generation of TA reports, the TA report format manager 1030 is capable of, configured to, or operable to support a component for generating a TA value indicated by a subset of bits in the set of multiple bits in the TA report, each code point in the subset of bits indicating a corresponding number of symbols. In some examples, to support the generation of TA reports, the TA report format manager 1030 is capable of, configured to, or operable to support a component for setting one or more reserved bits to zero.

[0169] In some examples, one or more reserved bits, the first bit, and a subset of bits comprise a single octet of the TA report. In some examples, the symbol duration corresponding to the TA value is based on the subcarrier spacing configured for the UE during the generation of the TA value.

[0170] In some examples, to support the generation of TA reports, the TA report format manager 1030 is capable of, configured to, or operable to support components for generating TA values ​​indicated by a subset of bits in a set of multiple bits of the TA report, each code point in the subset of bits indicating a corresponding number of symbols. In some examples, to support the generation of TA reports, the TA report format manager 1030 is capable of, configured to, or operable to support components for setting one or more reserved bits to zero.

[0171] In some examples, one or more reserved bits and subsets of bits comprise a single octet of the TA report. In some examples, the symbol duration corresponding to the TA value is based on the subcarrier spacing configured for the UE during the generation of the TA value.

[0172] In some examples, one or more reserved bits, one or more bits indicating the subcarrier spacing, and subsets of bits comprise a single octet of the TA report. In some examples, the symbol duration corresponding to the TA value is based on the subcarrier spacing during the generation of the TA value.

[0173] In some examples, the timing offset manager 1040 is capable of, configured to, or operable to support components for receiving control signaling for a threshold timing offset that indicates the transmission of a TA report, wherein the transmission of the TA report is based on determining that the transmission timing value meets the threshold timing offset.

[0174] In some examples, the threshold timing offset includes the number of symbols or the number of sampling time units.

[0175] Figure 11 A diagram of a system 1100 including device 1105 supporting a cell type-based TA report format, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or UE 115 as described herein, or may include components thereof. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, at least one memory 1130, code 1135, and at least one processor 1140. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1145).

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

[0177] In some cases, device 1105 may include a single antenna 1125. However, in other cases, device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125, a wired link, or a wireless link as described herein. For example, transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1115 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. Transceiver 1115, or transceiver 1115 and one or more antennas 1125, may be an example of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or components thereof as described herein.

[0178] At least one memory 1130 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1130 may store computer-readable, computer-executable code 1135, including instructions that, when executed by at least one processor 1140, cause device 1105 to perform the various functions described herein. Code 1135 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1135 may not be directly executable by at least one processor 1140, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, among other things, at least one memory 1130 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0179] At least one processor 1140 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 1140. At least one processor 1140 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks supporting cell type-based TA report formats). For example, device 1105 or components of device 1105 may include at least one processor 1140 and at least one memory 1130 coupled to or coupled to at least one processor 1140, at least one processor 1140 and at least one memory 1130 configured to perform various functions described herein. In some examples, at least one processor 1140 may include multiple processors, and at least one memory 1130 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1140 may be a component of a processing system, which may refer to a machine (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1140) and memory circuitry (which may include at least one memory 1130)) or system of components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 1140 or a processing system including at least one processor 1140 may be configured, configurable, or operable to cause device 1105 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “configurable to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1130 or otherwise.

[0180] The communication manager 1120 can support wireless communication according to the examples disclosed herein. For example, the communication manager 1120 can be configured or operable to support components for receiving information indicating that the cell corresponding to a network entity is an ATG cell. The communication manager 1120 can be configured or operable to support components for generating TA reports based on information according to a format corresponding to ATG communication. The communication manager 1120 can be configured or operable to support components for sending TA reports according to a specific format.

[0181] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support technologies for TA reporting, thereby enabling more efficient use of system resources, increased throughput, improved communication reliability, improved coordination and timing between devices, more efficient use of computing resources, and reduced system latency.

[0182] In some examples, the communication manager 1120 may be configured to use or otherwise coordinate with the transceiver 1115, one or more antennas 1125, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or executed by at least one processor 1140, at least one memory 1130, code 1135, or any combination thereof. For example, code 1135 may include instructions that can be executed by at least one processor 1140 to cause the device 1105 to perform various aspects of the cell type-based TA report format as described herein, or at least one processor 1140 and at least one memory 1130 may be otherwise configured to perform or support such operations individually or jointly.

[0183] Figure 12 A block diagram 1200 is shown of a device 1205 supporting a cell type-based TA report format according to one or more aspects of this disclosure. Device 1205 may be an example of aspects of network entity 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. Device 1205 or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, and communication manager 1220) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0184] Receiver 1210 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0185] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0186] The communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the cell type-based TA report format as described herein. For example, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0187] In some examples, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0188] Additionally or alternatively, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0189] In some examples, the communication manager 1220 may be configured to use or otherwise coordinate with the receiver 1210, transmitter 1215, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated in combination with the receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0190] The communication manager 1220 may support wireless communication according to the examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for transmitting information indicating that the cell corresponding to a network entity is an ATG cell. The communication manager 1220 may be capable of, configured to, or operable to support components for receiving a TA report from the UE in a format corresponding to ATG communication in response to the transmission of information. The communication manager 1220 may be capable of, configured to, or operable to support components for communicating with the UE based on the TA report.

[0191] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 (e.g., controlling receiver 1210, transmitter 1215, communication manager 1220 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for TA reporting, thereby enabling more efficient use of system resources, increased throughput, improved communication reliability and reduced system latency.

[0192] Figure 13 A block diagram 1300 is shown of a device 1305 supporting a cell type-based TA report format according to one or more aspects of this disclosure. Device 1305 may be an example of aspects of device 1205 or network entity 105 as described herein. Device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. Device 1305 or one or more components of device 1305 (e.g., receiver 1310, transmitter 1315, and communication manager 1320) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0193] Receiver 1310 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1305. In some examples, receiver 1310 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0194] Transmitter 1315 may provide components for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of device 1305. For example, transmitter 1315 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1315 and receiver 1310 may be co-located in a transceiver, which may include or be coupled to a modem.

[0195] Device 1305 or its various components may be examples of parts for performing various aspects of the cell type-based TA report format as described herein. For example, communication manager 1320 may include cell type manager 1325, TA report manager 1330, timing manager 1335, or any combination thereof. Communication manager 1320 may be examples of aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to use or otherwise cooperate with receiver 1310, transmitter 1315, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or be integrated in combination with receiver 1310, transmitter 1315, or both to acquire information, output information, or perform various other operations as described herein.

[0196] Communication Manager 1320 can support wireless communication according to the examples disclosed herein. Cell Type Manager 1325 is capable of, configured to, or operable to support components for transmitting information indicating that the cell corresponding to a network entity is an ATG cell. TA Report Manager 1330 is capable of, configured to, or operable to support components for receiving TA reports from the UE in a format corresponding to ATG communication in response to the transmission of information. Timing Manager 1335 is capable of, configured to, or operable to support components for communicating with the UE based on TA reports.

[0197] Figure 14A block diagram 1400 is shown of a communication manager 1420 supporting a cell type-based TA report format according to one or more aspects of this disclosure. The communication manager 1420 may be an example of a communication manager 1220, a communication manager 1320, or aspects thereof as described herein. The communication manager 1420 or its various components may be examples of parts for implementing various aspects of the cell type-based TA report format as described herein. For example, the communication manager 1420 may include a cell type manager 1425, a TA report manager 1430, a timing manager 1435, a TA report format manager 1440, a timing offset manager 1445, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0198] Communication Manager 1420 can support wireless communication according to the examples disclosed herein. Cell Type Manager 1425 is capable of, configured to, or operable to support components for transmitting information indicating that the cell corresponding to a network entity is an ATG cell. TA Report Manager 1430 is capable of, configured to, or operable to support components for receiving TA reports from the UE in a format corresponding to ATG communication in response to the transmission of information. Timing Manager 1435 is capable of, configured to, or operable to support components for communicating with the UE based on TA reports.

[0199] In some examples, to support TA reports, the TA report format manager 1440 is capable of, configured to, or operable to support components for TA values ​​indicated by bits in two octets of the TA report, each code point in the two octets of the TA report corresponding to a corresponding sampling time unit in a set of multiple candidate sampling time units.

[0200] In some examples, the reserved LCID code points include an indication of the format corresponding to the granularity of the sampling time unit.

[0201] In some examples, in order to support the transmission of information, the cell type manager 1425 can be configured or operable to support components for transmitting instructions that the cell supports a format corresponding to an ATG cell.

[0202] In some examples, to support TA reports, the TA report format manager 1440 is capable of, configured to, or operable to support components for TA values ​​indicated by a first subset of bits in a set of multiple bits reported by the TA, each code point in the first subset of bits corresponding to a corresponding number of symbols, wherein a second portion of the bits in the set of multiple bits is a vacancy.

[0203] In some examples, the symbol duration corresponding to the TA value is based on the subcarrier spacing configured for the UE.

[0204] In some examples, to support TA reports, the TA report format manager 1440 is capable of, configured to, or operable to support components for: the first bit of a set of multiple bits indicating a format corresponding to the TA report; a TA value indicated by a subset of bits in the set of multiple bits of the TA report, each code point in the subset of bits indicating a corresponding number of symbols; and one or more reserved bits.

[0205] In some examples, one or more reserved bits, the first bit, and a subset of bits comprise a single octet of the TA report, and the symbol duration corresponding to the TA value is based on the subcarrier spacing configured for the UE.

[0206] In some examples, to support TA reports, the TA report format manager 1440 is capable of, configured to, or operable to support components for: TA values ​​indicated by a subset of bits in a set of multiple bits of the TA report, each code point in the subset of bits indicating a corresponding number of symbols; and one or more reserved bits.

[0207] In some examples, one or more reserved bits and subsets of bits include a single octet of the TA report, and the symbol duration corresponding to the TA value is based on the subcarrier spacing configured for the UE.

[0208] In some examples, one or more reserved bits, one or more bits indicating the subcarrier interval, and subsets of bits include a single octet of the TA report, with the symbol duration corresponding to the TA value based on the subcarrier interval configured for the UE.

[0209] In some examples, the timing offset manager 1445 is capable of, configured to, or operable to support components for sending control signaling for sending a threshold timing offset that indicates the triggering of a TA report, wherein receiving a TA report is based on the transmission timing value satisfying the threshold timing offset.

[0210] In some examples, the threshold timing offset includes the number of symbols or the number of sampling time units.

[0211] Figure 15A diagram of a system 1500 including device 1505 supporting a cell type-based TA report format, according to one or more aspects of this disclosure, is shown. Device 1505 may be an example of device 1205, device 1305, or network entity 105 as described herein, or may include components thereof. Device 1505 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1505 may include components supporting output and acquisition of communication, such as a communication manager 1520, a transceiver 1510, an antenna 1515, at least one memory 1525, code 1530, and at least one processor 1535. These components may communicate electronically via one or more buses (e.g., bus 1540) or be otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically).

[0212] Transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1510 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1510 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1505 may include one or more antennas 1515, which may be capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1510 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1515, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1515, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1515 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1510 may include one or more processors or one or more memory components or be configured to couple to one or more processors or one or more memory components capable of operating to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1510, or transceiver 1510 and one or more antennas 1515, or transceiver 1510 and one or more antennas 1515, and one or more processors or one or more memory components (e.g., at least one processor 1535, at least one memory 1525, or both) may be included in a chip or chip assembly mounted in device 1505. In some examples, transceiver 1510 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0213] At least one memory 1525 may include RAM, ROM, or any combination thereof. At least one memory 1525 may store computer-readable, computer-executable code 1530 including instructions that, when executed by one or more processors of at least one processor 1535, cause device 1505 to perform the various functions described herein. Code 1530 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1530 may not be directly executable by a processor of at least one processor 1535, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, in addition to these, at least one memory 1525 may also include a BIOS that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1535 may include multiple processors, and at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0214] At least one processor 1535 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1535. At least one processor 1535 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1525) to cause device 1505 to perform various functions (e.g., functions or tasks supporting cell type-based TA report formats). For example, device 1505 or components of device 1505 may include at least one processor 1535 and at least one memory 1525 coupled to one or more processors in at least one processor 1535, wherein at least one processor 1535 and at least one memory 1525 are configured to perform the various functions described herein. At least one processor 1535 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions for performing the functions of device 1505 (e.g., by executing code 1530). At least one processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1505 (such as within one or more memories of at least one memory 1525). In some examples, at least one processor 1535 may include multiple processors, and at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1535 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1535) and memory circuitry (which may include at least one memory 1525)) or components that receive or receive input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1535 or a processing system including at least one processor 1535 may be configured, configurable, or operable to cause the device 1505 to perform one or more of the functions described herein.Furthermore, as described herein, “configurable to,” “configurable to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1525 or otherwise.

[0215] In some examples, bus 1540 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1540 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1505, or communication performed between different components of device 1505 that are co-addressable or may be located in different locations (e.g., where device 1505 may refer to a system in which one or more of communication manager 1520, transceiver 1510, at least one memory 1525, code 1530 and at least one processor 1535 may be located in one component of different components or partitioned between different components).

[0216] In some examples, the communication manager 1520 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1520 can manage the transfer of data communication by client devices such as one or more UEs 115. In some examples, the communication manager 1520 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating other network entities 105 to control communication with UE 115. In some examples, the communication manager 1520 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0217] The communication manager 1520 may support wireless communication according to the examples disclosed herein. For example, the communication manager 1520 may be capable of, configured to, or operable to support components for transmitting information indicating that the cell corresponding to a network entity is an ATG cell. The communication manager 1520 may be capable of, configured to, or operable to support components for receiving a TA report from the UE in a format corresponding to ATG communication in response to the transmission of information. The communication manager 1520 may be capable of, configured to, or operable to support components for communicating with the UE based on the TA report.

[0218] By including or configuring a communication manager 1520 according to an example as described herein, device 1505 can support technologies for TA reporting, thereby enabling more efficient use of system resources, increased throughput, improved communication reliability, improved coordination and timing between devices, more efficient use of computing resources, and reduced system latency.

[0219] In some examples, the communication manager 1520 may be configured to use or otherwise coordinate with the transceiver 1510, one or more antennas 1515 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by the transceiver 1510, one or more processors in at least one processor 1535, one or more memories in at least one memory 1525, code 1530, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1535, at least one memory 1525, code 1530, or any combination thereof). For example, code 1530 may include instructions that can be executed by one or more of the at least one processor 1535 to cause the device 1505 to perform various aspects of the cell type-based TA report format as described herein, or at least one processor 1535 and at least one memory 1525 may be otherwise configured to perform or support such operations individually or jointly.

[0220] Figure 16 A flowchart illustrating a method 1600 supporting a cell type-based TA report format according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be performed by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0221] At 1605, the method may include receiving information indicating that the cell corresponding to the network entity is an ATG cell. The operation of block 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1605 may be derived from references... Figure 10 The described cell type manager 1025 is executed.

[0222] At 1610, the method may include generating a TA report based on information and according to a format corresponding to ATG communication. The operation of box 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be derived from references... Figure 10 The TA report format manager 1030 described is executed.

[0223] At 1615, the method may include sending a TA report according to a format. The operation of box 1615 can be performed according to examples disclosed herein. In some examples, aspects of the operation of 1615 may be derived from references... Figure 10 The TA Report Manager 1035 described is executed.

[0224] Figure 17 A flowchart illustrating a method 1700 supporting a cell type-based TA report format according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be performed by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0225] At 1705, the method may include receiving control signaling indicating a threshold timing offset for triggering the transmission of a TA report, wherein the transmission of the TA report is based on determining that a transmission timing value satisfies the threshold timing offset. The operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to [reference needed]. Figure 10 The described timing offset manager 1040 is executed.

[0226] At 1710, the method may include receiving information indicating that the cell corresponding to the network entity is an ATG cell. The operation of block 1710 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1710 may be derived from references... Figure 10 The described cell type manager 1025 is executed.

[0227] At 1715, the method may include generating a TA report based on information and according to a format corresponding to ATG communication. The operation of box 1715 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1715 may be derived from references... Figure 10 The TA report format manager 1030 described is executed.

[0228] At 1720, the method may include sending a TA report according to a format. The operation of box 1720 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1720 may be derived from references... Figure 10 The TA Report Manager 1035 described is executed.

[0229] Figure 18A flowchart illustrating a method 1800 supporting a cell type-based TA report format according to various aspects of this disclosure is shown. The operation of method 1800 can be implemented by a network entity or its components as described herein. For example, the operation of method 1800 can be implemented by, as referenced... Figures 1 to 7 as well as Figures 12 to 15 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0230] At 1805, the method may include sending information indicating that the cell corresponding to the network entity is an ATG cell. The operation of block 1805 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1805 may be derived from references... Figure 14 The described cell type manager 1425 is executed.

[0231] At 1810, the method may include receiving a TA report from the UE in a format corresponding to ATG communication in response to the transmission of information. Operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1810 may be provided by reference to... Figure 14 The TA Report Manager 1430 described is executed.

[0232] At 1815, the method may include communicating with the UE based on a TA report. The operation of block 1815 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1815 may be referenced. Figure 14 The described timer manager 1435 is executed.

[0233] Figure 19 A flowchart illustrating a method 1900 supporting a cell type-based TA report format according to various aspects of this disclosure is shown. The operation of method 1900 can be implemented by a network entity or its components as described herein. For example, the operation of method 1900 can be implemented by, as referenced... Figures 1 to 7 as well as Figures 12 to 15 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0234] At 1905, the method may include sending control signaling indicating a threshold timing offset for triggering the transmission of a TA report, wherein the received TA report satisfies the threshold timing offset based on a transmission timing value. The operation of block 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1905 may be derived from references... Figure 14The described timing offset manager 1445 is executed.

[0235] At 1910, the method may include sending information indicating that the cell corresponding to the network entity is an ATG cell. The operation of block 1910 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1910 may be provided by reference to [reference needed]. Figure 14 The described cell type manager 1425 is executed.

[0236] At 1915, the method may include receiving a TA report from the UE in a format corresponding to ATG communication in response to the transmission of information. The operation of block 1915 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1915 may be provided by reference to... Figure 14 The TA Report Manager 1430 described is executed.

[0237] At 1920, the method may include communicating with the UE based on a TA report. The operation of block 1920 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1920 may be referenced. Figure 14 The described timer manager 1435 is executed.

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

[0239] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving information indicating that a cell corresponding to a network entity is an ATG cell; generating a TA report according to a format corresponding to ATG communication, at least in part based on the information; and transmitting the TA report according to the format.

[0240] Aspect 2: According to the method of aspect 1, generating the TA report includes: generating TA values ​​indicated by bits of two octets in the TA report, each code point in the two octets of the TA report corresponding to a corresponding sampling time unit among a plurality of candidate sampling time units.

[0241] Aspect 3: According to the method of aspect 2, the reserved logical channel identifier code point includes an indication corresponding to the granularity of the format and the sampling time unit.

[0242] Aspect 4: The method according to any one of Aspects 2 to 3, wherein receiving the information includes: receiving an indication that the cell supports the format corresponding to the ATG cell.

[0243] Aspect 5: The method according to any one of Aspects 1 to 4, wherein generating the TA report comprises: generating a TA value indicated by a first subset of bits of a plurality of bits in the TA report, each code point in the first subset of bits corresponding to a corresponding number of symbols, wherein a second portion of the bits of the plurality of bits is a vacancy.

[0244] Aspect 6: According to the method of aspect 5, the symbol duration corresponding to the TA value is at least partially based on the subcarrier spacing configured for the UE during the generation of the TA value.

[0245] Aspect 7: The method according to any one of Aspects 1 to 6, wherein generating the TA report comprises: setting the first bit of a plurality of bits of the TA report to indicate the format corresponding to the TA report; generating a TA value indicated by a subset of bits of the plurality of bits of the TA report, each code point in the subset of bits indicating a corresponding number of symbols; and setting one or more reserved bits to zero.

[0246] Aspect 8: According to the method of aspect 7, wherein the subset of the one or more reserved bits, the first bit, and the bit includes a single octet of the TA report, and the symbol duration corresponding to the TA value is at least partially based on the subcarrier spacing configured for the UE during the generation of the TA value.

[0247] Aspect 9: The method according to any one of Aspects 1 to 8, wherein generating the TA report comprises: generating a TA value indicated by a subset of bits of a plurality of bits in the TA report, each code point in the subset of bits indicating a corresponding number of symbols; and setting one or more reserved bits to zero.

[0248] Aspect 10: According to the method of aspect 9, wherein the subset of the one or more reserved bits and bits includes a single octet of the TA report, and the symbol duration corresponding to the TA value is at least partially based on the subcarrier spacing configured for the UE during the generation of the TA value.

[0249] Aspect 11: The method according to any one of Aspects 9 to 10, wherein the one or more reserved bits, the one or more bits indicating the subcarrier interval, and the subset of bits comprise a single octet of the TA report, and the symbol duration corresponding to the TA value is based at least in part on the subcarrier interval during the generation of the TA value.

[0250] Aspect 12: The method according to any one of Aspects 1 to 11, the method further comprising: receiving control signaling indicating a threshold timing offset for triggering the transmission of the TA report, wherein the transmission of the TA report is based at least in part on determining that a transmission timing value satisfies the threshold timing offset.

[0251] Aspect 13: According to the method of aspect 12, the threshold timing offset includes the number of symbols or the number of sampling time units.

[0252] Aspect 14: A method for wireless communication at a network entity, the method comprising: transmitting information indicating that a cell corresponding to the network entity is an ATG cell; receiving a TA report from a UE in a format corresponding to ATG communication in response to the transmission of the information; and communicating with the UE in accordance with the TA report.

[0253] Aspect 15: The method according to aspect 14, wherein the TA report includes: TA values ​​indicated by bits of two octets in the TA report, each code point in the two octets of the TA report corresponding to a corresponding sampling time unit among a plurality of candidate sampling time units.

[0254] Aspect 16: According to the method of aspect 15, the reserved logical channel identifier code point includes an indication corresponding to the granularity of the format and the sampling time unit.

[0255] Aspect 17: The method according to any one of Aspects 15 to 16, wherein sending the information includes: sending an indication that the cell supports the format corresponding to the ATG cell.

[0256] Aspect 18: The method according to any one of Aspects 14 to 17, wherein the TA report comprises: a TA value indicated by a first subset of bits of a plurality of bits of the TA report, each code point in the first subset of bits corresponding to a corresponding number of symbols, wherein a second portion of the bits of the plurality of bits is a vacancy.

[0257] Aspect 19: According to the method of aspect 18, the symbol duration corresponding to the TA value is at least partially based on the subcarrier spacing configured for the UE.

[0258] Aspect 20: The method according to any one of Aspects 14 to 19, wherein the TA report comprises: a first bit of a plurality of bits indicating the format corresponding to the TA report; a TA value indicated by a subset of bits of the plurality of bits of the TA report, each code point in the subset of bits indicating a corresponding number of symbols; and one or more reserved bits.

[0259] Aspect 21: According to the method of aspect 20, wherein the subset of the one or more reserved bits, the first bit, and the bit includes a single octet of the TA report, and the symbol duration corresponding to the TA value is at least partially based on the subcarrier spacing configured for the UE.

[0260] Aspect 22: The method according to any one of Aspects 14 to 21, wherein the TA report comprises: a TA value indicated by a subset of bits of a plurality of bits of the TA report, each code point in the subset of bits indicating a corresponding number of symbols; and one or more reserved bits.

[0261] Aspect 23: According to the method of aspect 22, the subset of the one or more reserved bits and bits includes a single octet of the TA report, and the symbol duration corresponding to the TA value is at least partially based on the subcarrier spacing configured for the UE.

[0262] Aspect 24: The method according to any one of Aspects 22 to 23, wherein the one or more reserved bits, the one or more bits indicating the subcarrier interval, and the subset of bits include a single octet of the TA report, and the symbol duration corresponding to the TA value is at least partially based on the subcarrier interval configured for the UE.

[0263] Aspect 25: The method according to any one of Aspects 14 to 24, the method further comprising: sending control signaling indicating a threshold timing offset for triggering the transmission of the TA report, wherein receiving the TA report is based at least in part on a transmission timing value satisfying the threshold timing offset.

[0264] Aspect 26: According to the method of aspect 25, the threshold timing offset includes the number of symbols or the number of sampling time units.

[0265] Aspect 27: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 13.

[0266] Aspect 28: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 1 to 13.

[0267] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the method according to any one of aspects 1 to 13.

[0268] Aspect 30: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of aspects 14 to 26.

[0269] Aspect 31: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 14 to 26.

[0270] Aspect 32: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform a method according to any one of aspects 14 to 26.

[0271] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

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

[0273] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0274] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0275] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

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

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

[0278] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0279] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0280] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0281] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

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

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: The received instruction indicates that the cell corresponding to the network entity is an air-to-ground cell; Based at least in part on the information, a timing advance report is generated in a format corresponding to air-to-ground communication; as well as Send the advance timing report according to the specified format.

2. The UE of claim 1, wherein, in order to generate the timing advance report, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: A timing advance value is generated, indicated by a first subset of the bits in the multiple bits reported in the timing advance report, wherein each code point in the first subset of bits corresponds to a corresponding number of symbols, and a second portion of the bits in the multiple bits is a vacancy.

3. The UE of claim 2, wherein the symbol duration corresponding to the timing advance value is at least partially based on the subcarrier spacing configured for the UE during the generation of the timing advance value.

4. The UE of claim 2, wherein the symbol duration corresponding to the timing advance value is at least partially based on the subcarrier spacing configured by the UE via control signaling.

5. The UE of claim 1, wherein, in order to generate the timing advance report, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The first bit of the multiple bits in the advance timing report is set to indicate the format corresponding to the advance timing report; Generate a timing advance value indicated by a subset of bits from the plurality of bits reported in the timing advance report, wherein each code point in the subset of bits indicates a corresponding number of symbols; as well as Set one or more remaining bits to zero.

6. The UE according to claim 5, wherein: The subset of the one or more remaining bits, the first bit, and the bit includes the single octet of the timing advance report, and The symbol duration corresponding to the timing advance value is at least partially based on the subcarrier spacing configured for the UE during the generation of the timing advance value.

7. The UE according to claim 5, wherein: The symbol duration corresponding to the timing advance value is at least partially based on the subcarrier spacing configured by the UE via control signaling.

8. The UE of claim 1, wherein, in order to generate the timing advance report, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Generate timing advance values ​​indicated by the bits of two octets in the timing advance report, each code point in the two octets in the timing advance report corresponding to a corresponding sampling time unit among a plurality of candidate sampling time units.

9. The UE according to claim 8, wherein the reserved logical channel identifier code point includes an indication corresponding to the granularity of the format and the sampling time unit.

10. The UE of claim 8, wherein, in order to receive the information, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Receive an indication that the cell supports the format corresponding to the air-to-ground cell.

11. The UE of claim 1, wherein, in order to generate the timing advance report, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Generate a timing advance value indicated by a subset of bits from the plurality of bits reported in the timing advance report, wherein each code point in the subset of bits indicates a corresponding number of symbols; and Set one or more reserved bits to zero.

12. The UE according to claim 11, wherein: The subset of the one or more reserved bits and bits includes a single octet of the timing advance report, and The symbol duration corresponding to the timing advance value is at least partially based on the subcarrier spacing configured for the UE during the generation of the timing advance value.

13. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive control signaling indicating a threshold timing offset that triggers the transmission of the timing advance report, wherein the transmission of the timing advance report is based at least in part on determining that the transmission timing value satisfies the threshold timing offset.

14. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: Send information indicating that the cell corresponding to the network entity is an air-to-ground cell; In response to the transmission of the information, a timed advance report is received from the user equipment (UE) in a format corresponding to air-to-ground communication; as well as The system communicates with the UE based on the aforementioned advance timing report.

15. The network entity of claim 14, wherein the timing advance report includes a timing advance value indicated by a first subset of bits of the plurality of bits of the timing advance report, each code point in the first subset of bits corresponding to a corresponding number of symbols, wherein a second portion of the bits of the plurality of bits is a vacancy.

16. The network entity of claim 15, wherein the symbol duration corresponding to the timing advance value is at least partially based on the subcarrier spacing configured for the UE.

17. The network entity of claim 14, wherein the advance timing report comprises: The first bit of the format in which the indication of multiple bits corresponds to the timing advance report; A timing advance value indicated by a subset of bits in the timing advance report, each code point in the subset of bits indicating a corresponding number of symbols; and one or more reserved bits.

18. The network entity of claim 17, wherein the subset of the one or more reserved bits, the first bit, and the bit comprises a single octet of the timing advance report, and the symbol duration corresponding to the timing advance value is at least partially based on the subcarrier spacing configured for the UE.

19. The network entity of claim 14, wherein the advance timing report comprises: A timing advance value indicated by a subset of bits in the multiple bits of the timing advance report, wherein each code point in the subset of bits indicates a corresponding number of symbols; and one or more reserved positions.

20. The network entity of claim 19, wherein the subset of the one or more reserved bits and bits comprises a single octet of the timing advance report, and the symbol duration corresponding to the timing advance value is at least partially based on the subcarrier spacing configured for the UE.

Images