Timing synchronization for non-terrestrial network communications

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a message from a first non-terrestrial network cell indicating cell synchronization information for a second non-terrestrial network cell. In some examples, the cell synchronization information may indicate whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point. Additionally or alternatively, the cell synchronization information may indicate a timing offset value between a first uplink time synchronization reference point of the first non-terrestrial network cell and a second uplink time synchronization reference point of the second non-terrestrial network cell. The UE may calculate a timing associated with signaling from the second non-terrestrial network cell based at least in part on the cell synchronization information. The UE may receive one or more signals from the second non-terrestrial network cell based at least in part on the calculated timing.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. patent application No. 17 / 884,458, entitled “TIMINGSYCHRONIZATION FOR NON-TERRESTRIAL NETWORK COMMUNICATIONS,” filed by SHRESTHA et al. on August 9, 2022, which is assigned to the assignee of this patent application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following relates to wireless communications, including timing synchronization for non-terrestrial network communications. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to 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, advanced LTE (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 techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as user equipment (UE). A wireless communication system may support communication between a UE and a non-terrestrial device (such as a satellite associated with one or more non-terrestrial cells). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting timing synchronization for non-terrestrial network communications. For example, the described technology enables a first non-terrestrial network cell to determine synchronization information associated with a second non-terrestrial network cell. A UE may receive a message indicating cell synchronization information for the second non-terrestrial network cell from the first non-terrestrial network cell. In some examples, the cell synchronization information may indicate whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point. Additionally or alternatively, the cell synchronization information may indicate a timing offset value between a first uplink time synchronization reference point of the first non-terrestrial network cell and a second uplink time synchronization reference point of the second non-terrestrial network cell. The UE may calculate timing associated with signaling from the second non-terrestrial network cell based on the cell synchronization information. The UE may monitor and receive one or more signals from the second non-terrestrial network cell based at least in part on the calculated timing.

[0006] A method for wireless communication at a UE in communication with a first non-terrestrial network cell is described. The method may include: receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point; calculating timing associated with signaling from the second non-terrestrial network cell based on the cell synchronization information; and receiving one or more signals from the second non-terrestrial network cell based on the calculated timing.

[0007] An apparatus for wireless communication at a UE communicating with a first non-terrestrial network cell is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point; calculate timing associated with signaling from the second non-terrestrial network cell based on the cell synchronization information; and receive one or more signals from the second non-terrestrial network cell based on the calculated timing.

[0008] Another apparatus for wireless communication at a UE communicating with a first non-terrestrial network cell is described. The apparatus may include: a component for receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point; a component for calculating timing associated with signaling from the second non-terrestrial network cell based on the cell synchronization information; and a component for receiving one or more signals from the second non-terrestrial network cell based on the calculated timing.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE in communication with a first non-terrestrial network cell is described. The code may include instructions executable by a processor to: receive a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point; calculate timing associated with signaling from the second non-terrestrial network cell based on the cell synchronization information; and receive one or more signals from the second non-terrestrial network cell based on the calculated timing.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, calculating the timing may include operations, features, components, or instructions for performing the following operations: calculating the timing based on synchronization of a first uplink time synchronization reference point of the first non-terrestrial network cell with a second uplink time synchronization reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates that the first uplink time synchronization reference point and the second uplink time synchronization reference point are synchronized.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, calculating the timing may include operations, features, components, or instructions for performing the following operations: calculating the timing based on a timing offset value between a first uplink time synchronization reference point of the first non-terrestrial network cell and a second uplink time synchronization reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the timing offset value includes a system frame number, a subframe, a time slot number, or any combination thereof.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the message may include operations, features, components, or instructions for performing the following operations: receiving the message from the first non-terrestrial network cell, the message including a measurement object configuration for a set of one or more non-terrestrial network cells including the second non-terrestrial network cell.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: determining that the first uplink time synchronization reference point of the first non-terrestrial network cell can be synchronized with the second uplink time synchronization reference point of the second non-terrestrial network cell based on the message excluding the indication of the timing offset value.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, calculating the timing may include operations, features, components, or instructions for performing the following operations: calculating the timing based on a timing difference between a downlink transmission of the first non-terrestrial network cell and a downlink transmission of the second non-terrestrial network cell, the timing difference being based on a first reference point of the first non-terrestrial network cell and a second reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing difference.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first reference point includes a first satellite or a first platform or both that provides a first service link for the first non-terrestrial network cell, and the second reference point includes a second satellite or a second platform or both that provides a second service link for the second non-terrestrial network cell, the second service link being different from the first service link.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, calculating the timing may include operations, features, components, or instructions for performing the following operations: calculating the timing based on a timing offset between an arrival time of a first synchronization signal block at a first network node of the first non-terrestrial network cell and an arrival time of a second synchronization signal block at a second network node of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the timing offset may be based on an epoch time, a reference time, or both of the first network node.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first network node includes a first satellite or a first platform that provides a first service link for the first non-terrestrial network cell, and the second network node includes a second satellite or a second platform that provides a second service link for the second non-terrestrial network cell, the second service link being different from the first service link.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, calculating the timing may include operations, features, components, or instructions for performing the following operations: calculating the timing based on a transmission time of a synchronization signal block sent by a network node associated with the second non-terrestrial network cell, wherein the cell synchronization information indicates the transmission time.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the transmission time indicates a system frame number and a subframe based on a timing of the first non-terrestrial network cell.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message includes a radio resource control message from the first non-terrestrial network cell.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message includes a handover message from the second non-terrestrial network cell.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message further indicates a reception time associated with a time at which the first non-terrestrial network cell received a handover command from the second non-terrestrial network cell before the first non-terrestrial network cell sent the message to the UE.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message includes a system information message from the first non-terrestrial network cell or the second non-terrestrial network cell.

[0026] A method for wireless communication at a network node associated with a first non-terrestrial network cell is described. The method may include: determining one or more timing parameters of a second non-terrestrial network cell that is different from the first non-terrestrial network cell; and sending a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based on the one or more timing parameters.

[0027] An apparatus for wireless communication at a network node associated with a first non-terrestrial network cell is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: determine one or more timing parameters of a second non-terrestrial network cell that is different from the first non-terrestrial network cell; and send a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based on the one or more timing parameters.

[0028] Another apparatus for wireless communication at a network node associated with a first non-terrestrial network cell is described. The apparatus may include: means for determining one or more timing parameters of a second non-terrestrial network cell that is different from the first non-terrestrial network cell; and means for sending a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based on the one or more timing parameters.

[0029] A non-transitory computer-readable medium storing code for wireless communication at a network node associated with a first non-terrestrial network cell is described. The code may include instructions executable by a processor to: determine one or more timing parameters of a second non-terrestrial network cell different from the first non-terrestrial network cell; and send a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based on the one or more timing parameters.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the one or more timing parameters may include operations, features, components, or instructions for performing the following operations: determining that a first uplink time synchronization reference point of the first non-terrestrial network cell can be synchronized with a second uplink time synchronization reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates that the first uplink time synchronization reference point and the second uplink time synchronization reference point are synchronized.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the one or more timing parameters may include operations, features, components, or instructions for performing the following operations: generating a timing offset value corresponding to a difference between a first uplink time synchronization reference point of the first non-terrestrial network cell and a second uplink time synchronization reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset value.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the timing offset value includes a system frame number, a subframe, a time slot number, or any combination thereof.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message includes a measurement object configuration for a set of one or more non-terrestrial network cells including the second non-terrestrial network cell.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the one or more timing parameters may include operations, features, components, or instructions for performing the following operations: calculating a timing difference between a downlink transmission of the first non-terrestrial network cell and a downlink transmission of the second non-terrestrial network cell, the timing difference being based on a first reference point of the first non-terrestrial network cell and a second reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing difference.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first reference point includes a first satellite or a first platform or both that provides a first service link for the first non-terrestrial network cell, and the second reference point includes a second satellite or a second platform or both that provides a second service link for the second non-terrestrial network cell, the second service link being different from the first service link.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the one or more timing parameters may include operations, features, components, or instructions for performing the following operations: determining a timing offset between an arrival time of a first synchronization signal block at a first network node of the first non-terrestrial network cell and an arrival time of a second synchronization signal block at a second network node of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the timing offset may be based on an epoch time, a reference time, or both of the first network node.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first network node includes a first satellite or a first platform that provides a first service link for the first non-terrestrial network cell, and the second network node includes a second satellite or a second platform that provides a second service link for the second non-terrestrial network cell, the second service link being different from the first service link.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the one or more timing parameters may include operations, features, components, or instructions for performing the following operations: determining a transmission time of a synchronization signal block sent by a second network node associated with the second non-terrestrial network cell, wherein the cell synchronization information indicates the transmission time, and the transmission time indicates a system frame number and subframe based on the timing of the first non-terrestrial network cell. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 An example of a wireless communication system supporting timing synchronization for non-terrestrial network communications in accordance with one or more aspects of the present disclosure is illustrated.

[0041] Figure 2 An example of a wireless communication system supporting timing synchronization for non-terrestrial network communications in accordance with one or more aspects of the present disclosure is illustrated.

[0042] Figure 3 An example of a process flow in a system supporting timing synchronization for non-terrestrial network communications in accordance with one or more aspects of the present disclosure is illustrated.

[0043] Figure 4 and Figure 5 A block diagram of a device supporting timing synchronization for non-terrestrial network communications in accordance with one or more aspects of the present disclosure is shown.

[0044] Figure 6 A block diagram of a communications manager supporting timing synchronization for non-terrestrial network communications is shown in accordance with one or more aspects of the present disclosure.

[0045] Figure 7 A diagram of a system including a device supporting timing synchronization for non-terrestrial network communications is shown in accordance with one or more aspects of the present disclosure.

[0046] Figure 8 and Fig. 9 A block diagram of a device supporting timing synchronization for non-terrestrial network communications in accordance with one or more aspects of the present disclosure is shown.

[0047] Fig.10 A block diagram of a communications manager supporting timing synchronization for non-terrestrial network communications is shown in accordance with one or more aspects of the present disclosure.

[0048] Fig.11 A diagram of a system including a device supporting timing synchronization for non-terrestrial network communications is shown in accordance with one or more aspects of the present disclosure.

[0049] Figures 12 to 17 A flow chart illustrating a method of supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0050] Some wireless communication systems may support communication via non-terrestrial networks. A non-terrestrial network may refer to a network or one or more network segments that use radio frequency (RF) resources to communicate between a UE and a satellite, between a UE and an unmanned aerial system (UAS) platform, etc. For example, a UE may communicate with a satellite via a service link, and a satellite may be connected to a gateway (e.g., a non-terrestrial network gateway) via a feeder link. The gateway may be co-located with a network node or communicate with a network node such that signaling may be communicated between the network node and the UE via the gateway and the satellite. In such cases, a non-terrestrial network cell may be associated with one or more corresponding satellites, each of which may be associated with one or more gateways.

[0051] The non-terrestrial network entity may perform a handover procedure to transfer the UE from a serving cell of the non-terrestrial network entity to a target cell (e.g., a neighboring cell) of another non-terrestrial network entity. The non-terrestrial network entity may send a message (e.g., a handover command) to the UE indicating timing parameters associated with the target cell. The UE may use the received parameters to perform measurements in a configuration window and may monitor information blocks associated with the target cell. However, the UE may not know the precise timing offset of the target cell relative to the serving cell timing until the UE decodes the information block for the first time. In such cases, the UE may perform blind decoding to detect information blocks from the target cell, which increases power consumption. Therefore, the UE may benefit from additional timing information provided to assist the handover procedure.

[0052] Thus, the techniques, systems, and devices described herein enable a UE to receive timing information associated with a neighboring non-terrestrial network cell from a serving non-terrestrial network cell, which timing information may be used during a handover procedure. For example, a serving non-terrestrial network entity and a target non-terrestrial network entity may be synchronized relative to a synchronization reference point, and the serving non-terrestrial network entity or the target non-terrestrial network entity may send a message indicating the synchronization information to the UE. Additionally or alternatively, the serving non-terrestrial network entity or the target non-terrestrial network entity may send a message indicating a timing offset of an arrival time of an SSB associated with the target non-terrestrial network entity, as well as an ephemeris, epoch time, or reference time point. Thus, the UE may detect the SSB with higher reliability during a handover procedure, which may improve power savings, connectivity, and communication resource efficiency.

[0053] Aspects of the disclosure are first described in the context of wireless communication systems. Aspects of the disclosure are further illustrated and described with reference to process flows, apparatus diagrams, system diagrams, and flow diagrams related to timing synchronization for non-terrestrial network communications.

[0054] Figure 1 An example of a wireless communication system 100 supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is illustrated. 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 according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0055] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0056] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.

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

[0058] In some examples, the network entities 105 may communicate with the core network 130 or with each other or both. For example, the network entities 105 may communicate with the 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, the network entities 105 may communicate with each other via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication links 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication links 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0059] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which 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 a base station 140).

[0060] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between 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, the 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 (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0061] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functions, 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 functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may 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) functions and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within a protocol layer (e.g., some functions of a protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

[0062] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may 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 nodes 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 DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a 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 nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The 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 an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the 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 the IAB node 104) may be configured to operate according to the techniques described herein.

[0063] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support timing synchronization for non-terrestrial network communications as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

[0065] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0066] The UE 115 and the network entity 105 may 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" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates 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 for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0067] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a resource of a subcarrier, in which case the symbol period and the 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 coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high rate of communication. Wireless communication resources may refer to a combination of RF spectrum resources, time 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.

[0068] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, for which Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0069] 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, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further 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 in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of 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., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

[0071] According to various techniques, physical channels may be multiplexed using carriers for communication. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may 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 sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0072] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for 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 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0073] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the 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 communication 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 commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

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

[0075] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may 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), an 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), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0076] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about 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 may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0077] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0078] The 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 technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations 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, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0079] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0080] The network entity communication manager 101 may manage communications between the network entity 105 and other devices in the wireless communication system 100. In a similar manner, the UE communication manager 102 may manage communications between the UE 115 and other devices in the wireless communication system 100. As described herein, the network entity 105 may refer to a terrestrial communication device (such as a base station 140) or a non-terrestrial communication device (such as a satellite 185, a balloon, a drone, a UAS platform, or another non-terrestrial device). The non-terrestrial network entity 105 may be connected to the terrestrial network entity 105 via a gateway 190. In some examples, the non-terrestrial network entity 105 may correspond to a first cell type (e.g., a non-terrestrial network cell type), and the terrestrial network entity 105 may correspond to a second cell type different from the first cell type (e.g., a terrestrial network cell type).

[0081] A non-terrestrial network may refer to a network or one or more network segments that use RF resources to communicate between a UE 115 and a satellite 185 or a UAS platform. For example, a UE may communicate with a non-terrestrial network entity 105 (e.g., a satellite 185 or another non-terrestrial device) via a service link, and the non-terrestrial network entity 105 may be connected to a gateway 190 (e.g., a non-terrestrial network gateway) via a feeder link. The gateway may be co-located with or in communication with another network entity 105 (e.g., a terrestrial network entity 105 such as a base station 140), and signaling may be communicated between the network entity 105 and the UE 115 via the gateway 190 and the non-terrestrial network entity 105. A non-terrestrial network cell may be associated with a respective non-terrestrial network entity 105, and each non-terrestrial network entity 105 may be associated with one or more gateways 190.

[0082] In some examples, the non-terrestrial network entity 105 may be synchronized with respect to a synchronization reference point (e.g., an uplink time synchronization reference point (ULTSRP)). The synchronization reference point may represent a point (e.g., a logical point) at which downlink messages and uplink messages may be aligned (e.g., frame aligned) with an offset associated with a timing advance (TA). In some cases, a round trip time (RTT) between the UE 115 and the synchronization reference point may correspond to the sum of a serving link RTT between the UE 115 and the serving non-terrestrial network entity 105 and a common TA between the serving non-terrestrial network entity 105 and a gateway. Additionally, the RTT between the synchronization reference point and the terrestrial network entity 105 (e.g., a base station 140 such as a gNB) may correspond to a timing parameter (e.g., K_mac).

[0083] The non-terrestrial network entity 105 may perform a handover procedure to transfer the UE 115 from the serving non-terrestrial network cell of the non-terrestrial network entity 105 to a target non-terrestrial network cell (e.g., a neighboring non-terrestrial network cell) of another non-terrestrial network entity 105. The non-terrestrial network entity 105 may send a message (e.g., a handover command) indicating parameters such as ephemeris, epoch time (e.g., subframe number and SFN), common TA parameters, or other parameters associated with the target cell to the UE 115, which may be based on the timing of the target cell. The UE 115 uses the received parameters to perform measurements in a configuration window (e.g., a synchronization signal block (SSB)-based radio resource management (RRM) timing configuration (SMTC) window), and may monitor information blocks associated with the target cell (e.g., SSB, master information block (MIB)). However, the UE 115 may not have information about the timing offset of the target cell relative to the serving cell timing until the UE 115 decodes the information block for the first time. Furthermore, the UE 115 may perform blind decoding to detect the information blocks, which may increase power consumption at the UE 115. Thus, the UE 115 may benefit from additional timing information provided to assist with handover procedures and enable communications with a target non-terrestrial network cell.

[0084] Thus, the techniques, systems, and devices described herein enable the UE 115 to receive additional information during a handover procedure. For example, the serving non-terrestrial network entity 105 and the target non-terrestrial network entity 105 may be synchronized with respect to a synchronization reference point, and the serving non-terrestrial network entity 105 or the target non-terrestrial network entity 105 may send a message indicating synchronization information to the UE 115. Additionally or alternatively, the serving non-terrestrial network entity 105 or the target non-terrestrial network entity 105 may send a message indicating a timing offset of an arrival time of an SSB associated with the target non-terrestrial network entity 105 and an ephemeris, epoch time, or reference time point. Thus, the UE 115 may detect the SSB with greater reliability during a handover procedure, which may improve power savings, connectivity, and communication resource efficiency.

[0085] Figure 2 An example of a wireless communication system 200 supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may be as described herein with reference to Figure 1 An example of the wireless communication system 100 described herein. The wireless communication system 200 may include: a UE 115-a, which may be as described in reference Figure 1 The examples of UE 115 described; and network entity 105-a, network entity 105-b and network entity 105-c, which may be as described in reference Figure 1In some cases, network entity 105-a and network entity 105-b may be examples of non-terrestrial network entities 105 (e.g., non-terrestrial network cells) as described herein and may be connected to gateway 215, which may be an example of a non-terrestrial network entity 105 as described herein. Figure 1 Similarly, the network entity 105-c may be an example of a gateway 190 as described herein. Figure 1 Examples of ground network entities 105 (eg, base stations 140) are depicted.

[0086] The network entity 105-a and the network entity 105-b may be associated with coverage areas 205-a and 205-b, respectively, and these coverage areas may be as described in reference Figure 1 An example of coverage area 110 is described. Network entity 105-a and network entity 105-b may communicate with UE 115-a via communication link 210-a and communication link 210-b (eg, serving link), respectively, which communication links may be as described herein. Figure 1 An example of described communication link 125. In some examples, network entity 105-a and network entity 105-b may be or be associated with a satellite or platform that provides communication link 210-a and communication link 210-b (eg, service links), respectively.

[0087] The network entity 105-a and the network entity 105-b may each be synchronized with respect to a reference point 225 (e.g., ULTSRP). The reference point 225 may represent a point at which downlink messages and uplink messages may be aligned with an offset frame associated with the same TA. The reference point 225 may be located, for example, at a gateway 215 (as illustrated), at a platform, at one of the network entities 105, or at a point between the network entity 105 and the gateway. The network entity 105-a and the network entity 105-b may have the same reference point 225 or may each have a different reference point 225.

[0088] In some examples, the RTT between the UE 115-a and the reference point 225 for communication between the UE 115-a and the network entity 105-c via the network entity 105-a may correspond to the sum of the service link RTT 230-a between the UE 115 and the network entity 105-a and the common TA 235-a between the network entity 105-a and the gateway 215. Similarly, the RTT between the UE 115-a and the reference point 225 for communication between the UE 115-a and the network entity 105-c via the network entity 105-b may correspond to the sum of the service link RTT 230-b between the UE 115 and the network entity 105-b and the common TA 235-b between the network entity 105-b and the gateway 215. In addition, the RTT between the reference point 225 and the ground network entity 105-c may correspond to the timing delay 240 (e.g., K_mac). K_mac may represent a scheduling offset when the downlink frame timing and the uplink frame timing are not aligned at the network entity 105-c (e.g., at the gNB).

[0089] The network entity 105-c (which may be the serving network entity 105 of the UE 115-a) may perform a handover procedure to handover the UE 115-a from the serving cell (e.g., associated with the network entity 105-a) to a target cell (e.g., a neighboring cell) (e.g., associated with the network entity 105-b). In some examples, the target cell may be associated with the same gateway as the serving cell, the same ground network entity (e.g., a gNB), or both. In some other examples, the target cell may be associated with a different gateway than the serving cell, a different ground network entity (e.g., a gNB), or both. In any case, the network entity 105-c may send a message (e.g., a handover command or message) to the UE 115-a (e.g., in an NTN-Config-r17 information element) indicating timing parameters such as ephemeris, epoch time (e.g., subframe number and SFN), common TA parameters, K_mac, and / or other parameters associated with the target cell of the network entity 105-b. UE 115-a may be configured to perform measurements in a configured window (e.g., an SMTC window) and may monitor information blocks 245 (e.g., SSBs, MIBs) associated with network entity 105-b. However, for example, based solely on timing parameters, UE 115-a may not know the timing associated with a target cell associated with network entity 105-b relative to the timing of a serving cell associated with network entity 105-a (e.g., the precise timing offset of the target cell) until UE 115 reads information block 245 for the first time.

[0090] To assist UE 115-a in receiving information block 245, network entity 105-c may send a message indicating synchronization information 220 to UE 115-a. In some examples, network entity 105-a and network entity 105-b may share the same gateway 215 and may have the same reference point 225 (e.g., UL SRP). Network entity 105-c may send a message (e.g., an RRC message) indicating synchronization information 220. Additionally or alternatively, network entity 105-c may send a message (e.g., a handover message) indicating synchronization information 220. Synchronization information 220 may indicate to UE 115-a that network entity 105-a and network entity 105-b have the same reference point 225. Thus, UE 115-a may determine timing information corresponding to information block 245 based on the received timing parameters and synchronization information 220, and UE 115-a may detect (e.g., receive) information block 245.

[0091] In some cases, the synchronization information 220 may be indicated to the UE 115-a via an indication field of an information element (e.g., SSB-ConfigMobility indicated by a measurement object configuration (e.g., MeasObjectNR)) or other message. For example, the synchronization information 220 may be signaled using a field (e.g., deriveSSB-IndexFromCell), which, if set to true, the UE 115-a may use to assume that the SNF and frame boundaries of cells across the same frequency carrier are aligned (e.g., the UE 115-a may be configured to utilize the timing of the serving cell to derive the index of the SSB sent by the target cell or other neighboring cells). For non-terrestrial network cells, the field may indicate whether the UE 115-a may use a reference point 225 (e.g., ULTSRP) of one or more detected cells on the target frequency to derive the SSB index of one or more neighboring cells on the target frequency.

[0092] In another example, the synchronization information 220 may be indicated via a field (e.g., deriveSSB-IndexFromCellInter), which may be used to configure the UE to assume SFN and frame boundary alignment between a reference serving cell indicated by an index (e.g., ServCellIndex) and one or more neighboring cells (e.g., cells in MeasObjectNR). For non-terrestrial network cells, the UE 115-a may be further configured to assume reference point alignment (e.g., ULTSRP alignment) between the reference serving cell (e.g., indicated by ServCellIndex) and one or more neighboring cells (e.g., indicated by MeasObjectNR).

[0093] In some examples, the reference point 225 of the network entity 105-a may be different from the reference point 225 of the network entity 105-b. For example, the network entity 105-a and the network entity 105-b may be associated with different gateways. In such examples, the synchronization information 220 may indicate to the UE 115-a a timing offset (e.g., a timing offset value) between the reference point 225 associated with the serving non-terrestrial network cell and the reference point 225 associated with the target non-terrestrial network cell. In some examples, the timing offset may be indicated to the UE 115-a in a handover message that includes one or more other timing parameters. Additionally or alternatively, the UE 115-a may receive a measurement object configuration from the network entity 105-a (e.g., the serving network entity 105-a), and the measurement object configuration may include a timing offset for a list of one or more cells (including the target cell of the network entity 105-b). In another example, UE 115-a may receive a broadcast indicating a list of inter-frequency cells, intra-frequency cells, neighboring non-terrestrial network entities 105, or a combination thereof, and the broadcast may indicate a timing offset for corresponding cells including the target non-terrestrial network cell. In some examples, if UE 115-a does not receive the timing offset, UE 115-a may determine (e.g., assume) that reference points 225 associated with the serving cell and the target cell are the same (e.g., synchronized).

[0094] In some aspects, the network entity 105-c may send a message to the UE 115-a indicating a time difference (e.g., a downlink time difference) at a particular reference point (e.g., at a reference point corresponding to the network entity 105-a and / or the network entity 105-b), which the UE 115-a may use to calculate the timing of a target non-terrestrial network cell (e.g., associated with the network entity 105-b). Additionally or alternatively, the network entity 105-c may send a message (e.g., via the communication link 210-a) indicating a timing offset associated with receiving the information block 245. The network entity 105-c may know the arrival time of the information block at the network entity 105-b. Thus, the network entity 105-c may provide a timing offset associated with the difference between the arrival time of the information block 245 at the target cell and the ephemeris of the serving cell, the epoch time of the serving cell, or a reference time point. UE 115-a may calculate the arrival time of information block 245 based on a timing offset received from network entity 105-a (and, in some examples, by calculating a service link RTT 230-b between UE 115-a and network entity 105-b).

[0095] The network entity 105-c may send a message to the UE 115-a (e.g., via the communication link 210-a) indicating the time at which the information block 245 was sent by the ground network entity 105 associated with the network entity 105-b. For example, the network entity 105-c may send an indication of the SFN and subframe (e.g., time slot number) associated with the transmission of the information block 245. The UE 115-a may determine the arrival time of the information block 245 based on the indication and based on the serving link RTT 230-b, the common TA 235-b, the timing delay 240 (e.g., K_mac), the SMTC configuration, or any combination thereof.

[0096] In some examples, network entity 105-c may send a message to UE 115-a indicating timing information associated with a handover command received by network entity 105-c from a different network entity associated with a target non-terrestrial network cell (e.g., in the case where network entity 105-b is associated with a network entity different from network entity 105-c). For example, the message may indicate the time of receipt of the handover command by network entity 105-c. In some cases, the message may be multiplexed in a MAC service data unit (SDU) carrying the handover command (e.g., to UE 115-a). Alternatively, the message may be sent separately using a MAC control element (MAC-CE), an RRC message, etc. In some aspects, such as in a conditional handover case, the RRC message carrying the conditional handover command may be extended to include a message indicating timing information. In some aspects, the timing information may be used to determine a validity time of a parameter of a target cell or an epoch time of a target cell. In some aspects of the time-based conditional handover, the time information for the epoch time or parameter validity time is a frame associated with the time at which the time-based conditional handover becomes valid.

[0097] Thus, UE 115-a may receive synchronization information 220 from network entity 105-a or network entity 105-b, which synchronization information may be used to efficiently calculate timing information for a target non-terrestrial network cell, thereby improving the reliability of reception of information block 245 and reducing blind decoding performed by UE 115-a.

[0098] Figure 3 An example of a process flow 300 in a system supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is illustrated. The process flow may illustrate communications between UE 115-b and network entities 105-d and 105-e, which may be as described herein with reference to Figure 1 and Figure 2Examples of corresponding devices described. In some examples, network entity 105-d may correspond to serving network entity 105-d for UE 115-d, and network entity 105-e may correspond to a target network entity for a handover procedure. In some examples, network entity 105-d and network entity 105-e may be examples of non-terrestrial network entity 105 and may be associated with a non-terrestrial network cell.

[0099] At 305, the network entity 105-d may send timing information to the UE 115-b. For example, the network entity 105-d may send (e.g., via the NTN-Config-r17 information element) a message to the UE 115-b indicating timing parameters such as ephemeris, epoch time (e.g., subframe number and SFN), common TA parameters, K_mac, or other parameters for the UE 115-b to access a network (e.g., an NR network) via a non-terrestrial network.

[0100] At 310, the network entity 105-d may determine one or more timing parameters of the network entity 105-e, and may determine synchronization information (e.g., cell synchronization information) associated with the network entity 105-d and the network entity 105-e. For example, the network entity 105-d may determine that the network entity 105-d and the second network entity 105-e are synchronized at a reference point (e.g., UL T SRP). Additionally or alternatively, the network entity 105-d may generate a timing offset value corresponding to a difference between a synchronization reference point of the network entity 105-d and a synchronization reference point of the network entity 105-e. The timing offset may be or include a SFN, a subframe, a time slot number, or a combination thereof. In some examples, the network entity 105-d may calculate a timing difference between a downlink transmission of the network entity 105-d and a downlink transmission of the network entity 105-e. The timing difference may be based on a reference point of network entity 105-d and a reference point of network entity 105-e, and the reference points may be or correspond to a satellite, platform, gateway, or combination thereof that provides a service link to network entity 105-d or network entity 105-e. In some examples, network entity 105-d may determine a timing offset between an SSB arrival time at a node of network entity 105-d and an SSB arrival time at a node of network entity 105-e, and the timing offset may be based on an epoch time of network entity 105-d, a reference time, or both. Additionally or alternatively, network entity 105-d may determine a transmit time of one or more SSBs transmitted by network entity 105-e, and the transmit time may be or indicate an SFN and subframe based on the timing of network entity 105-d.

[0101] At 315, UE 115-b may receive a message indicating synchronization information from network entity 105-d (eg, in an RRC message, a handover message, or a system information message), as described herein with reference to Figure 2 Described. For example, network entity 105-d may send a message to UE 115-b indicating synchronization information determined by network entity 105-d. In some examples, the synchronization information may include an indication that network entity 105-d and network entity 105-e are synchronized at a reference point (e.g., UL T SRP). In other examples, the synchronization information may indicate to UE 115-b a timing offset value between a synchronization reference point of network entity 105-d and a synchronization reference point of network entity 105-e. The timing offset value may be or include an SFN, a subframe, a time slot number, or a combination thereof. In some cases, the synchronization information may be received in a measurement object configuration for a set of one or more non-terrestrial network entities 105 that may include network entity 105-e.

[0102] In some examples, UE 115-a may determine that network entity 105-d and network entity 105-e are synchronized at a reference point based on the synchronization information excluding an indication of a timing offset value. In some examples, the synchronization information may indicate a timing offset between a first SSB arrival time at a node of network entity 105-d and a second SSB arrival time at a node of network entity 105-e, and the timing offset may be based on an epoch time, a reference time, or both of network entity 105-d. In some cases, the synchronization information may indicate to UE 115-b a transmission time of one or more SSBs transmitted by network entity 105-e, and the transmission time may be or indicate an SFN and subframe based on the timing of network entity 105-d. In some cases, the message indicating the synchronization information may indicate to UE 115-a a reception time of a handover command transmitted from network entity 105-e to network entity 105-d.

[0103] At 320, UE 115-a may calculate timing associated with signaling from network entity 105 based on timing information received from network entity 105-d and synchronization information (e.g., cell synchronization information) received from network entity 105-d.

[0104] At 325, UE 115-b may monitor one or more signals from network entity 105-e based on the calculated timing. Network entity 105-e may send one or more signals to UE 115-b. For example, network entity 105-e may send one or more information blocks (e.g., SSBs) to UE 115-b that may indicate cell or timing information. Based on the monitoring, UE 115-b may receive signals from network entity 105-e using (e.g., at 320) the calculated timing.

[0105] Figure 4 A block diagram 400 of a device 405 supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The device 405 may be an example of aspects of a UE 115 as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. The device 405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0106] Receiver 410 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to timing synchronization for non-terrestrial network communications, data channels, information channels). The information may be communicated to other components of device 405. Receiver 410 may utilize a single antenna or a collection of multiple antennas.

[0107] Transmitter 415 may provide means for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information associated with various information channels (e.g., control channels related to timing synchronization for non-terrestrial network communications, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0108] The communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of timing synchronization for non-terrestrial network communications as described herein. For example, the communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0109] In some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0110] Additionally or alternatively, in some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0111] In some examples, communication manager 420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 410, transmitter 415, or both. For example, communication manager 420 may receive information from receiver 410, transmit information to transmitter 415, or be integrated in conjunction with receiver 410, transmitter 415, or both to obtain information, output information, or perform various other operations as described herein.

[0112] The communication manager 420 may support wireless communication at a UE communicating with a first non-terrestrial network cell according to examples as disclosed herein. For example, the communication manager 420 may be configured to or otherwise support a component for receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point. The communication manager 420 may be configured to or otherwise support a component for calculating timing associated with signaling from the second non-terrestrial network cell based on the cell synchronization information. The communication manager 420 may be configured to or otherwise support a component for receiving one or more signals from the second non-terrestrial network cell based on the calculated timing.

[0113] By including or configuring a communications manager 420 according to examples as described herein, a device 405 (e.g., a processor controlling or otherwise coupled to a receiver 410, a transmitter 415, a communications manager 420, or a combination thereof) may support techniques for timing synchronization for non-terrestrial network communications using reduced power consumption and more efficient utilization of communications resources.

[0114] Figure 5A block diagram 500 of a device 505 supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the device 405 or UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0115] Receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to timing synchronization for non-terrestrial network communications, data channels, information channels). The information may be communicated to other components of device 505. Receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0116] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information associated with various information channels (e.g., control channels related to timing synchronization for non-terrestrial network communications, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0117] Device 505 or its various components may be examples of components for performing various aspects of timing synchronization for non-terrestrial network communications as described herein. For example, communication manager 520 may include synchronization component 525, timing component 530, signal monitoring component 535, or any combination thereof. Communication manager 520 may be an example of various aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in combination with receiver 510, transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0118] The communication manager 520 may support wireless communication at a UE communicating with a first non-terrestrial network cell according to examples as disclosed herein. The synchronization component 525 may be configured to or otherwise support a component for receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point. The timing component 530 may be configured to or otherwise support a component for calculating a timing associated with signaling from the second non-terrestrial network cell based on the cell synchronization information. The signal monitoring component 535 may be configured to or otherwise support a component for receiving one or more signals from the second non-terrestrial network cell based on the calculated timing.

[0119] Figure 6 A block diagram 600 of a communication manager 620 supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The communication manager 620 can be an example of aspects of the communication manager 420, the communication manager 520, or both as described herein. The communication manager 620 or its various components can be examples of components for performing various aspects of timing synchronization for non-terrestrial network communications as described herein. For example, the communication manager 620 can include a synchronization component 625, a timing component 630, a signal monitoring component 635, a synchronization signal block component 640, a measurement object component 645, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0120] The communication manager 620 may support wireless communication at a UE communicating with a first non-terrestrial network cell according to examples as disclosed herein. The synchronization component 625 may be configured to or otherwise support a component for receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point. The timing component 630 may be configured to or otherwise support a component for calculating a timing associated with signaling from the second non-terrestrial network cell based on the cell synchronization information. The signal monitoring component 635 may be configured to or otherwise support a component for receiving one or more signals from the second non-terrestrial network cell based on the calculated timing.

[0121] In some examples, to support calculating timing, the timing component 630 may be configured as or otherwise support a component for calculating timing based on synchronizing a first uplink time synchronization reference point of a first non-terrestrial network cell with a second uplink time synchronization reference point of a second non-terrestrial network cell, wherein cell synchronization information indicates that the first uplink time synchronization reference point and the second uplink time synchronization reference point are synchronized.

[0122] In some examples, to support calculating timing, the timing component 630 may be configured to or otherwise support a component for calculating timing based on a timing offset value between a first uplink time synchronization reference point of a first non-terrestrial network cell and a second uplink time synchronization reference point of a second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset. In some examples, the timing offset value includes a system frame number, a subframe, a time slot number, or any combination thereof.

[0123] In some examples, to support receiving a message, the measurement object component 645 may be configured as or otherwise support components for receiving a message from a first non-terrestrial network cell that includes a measurement object configuration for a set of one or more non-terrestrial network cells including a second non-terrestrial network cell.

[0124] In some examples, the synchronization component 625 may be configured as or otherwise support components for determining that a first uplink time synchronization reference point of a first non-terrestrial network cell is synchronized with a second uplink time synchronization reference point of a second non-terrestrial network cell based on excluding an indication of a timing offset value in the message.

[0125] In some examples, the message includes a radio resource control message from the first non-terrestrial network cell. In some examples, the message includes a handover message from the second non-terrestrial network cell, and the message may indicate a reception time associated with a time when the first non-terrestrial network cell received a handover command from the second non-terrestrial network cell before the first non-terrestrial network cell sent the message to the UE. In some examples, the message includes a system information message from the first non-terrestrial network cell or the second non-terrestrial network cell.

[0126] In some examples, to support calculating timing, the timing component 630 may be configured as or otherwise support a component for calculating timing based on a timing difference between a downlink transmission of a first non-terrestrial network cell and a downlink transmission of a second non-terrestrial network cell, wherein the timing difference is based on a first reference point of the first non-terrestrial network cell and a second reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing difference.

[0127] In some examples, the first reference point includes a first satellite or a first platform or both that provides a first service link for a first non-terrestrial network cell. In some examples, the second reference point includes a second satellite or a second platform or both that provides a second service link for a second non-terrestrial network cell, the second service link being different from the first service link.

[0128] In some examples, to support calculating timing, the synchronization signal block component 640 may be configured as or otherwise support components for calculating timing based on a timing offset between an arrival time of a first synchronization signal block at a first network node in a first non-terrestrial network cell and an arrival time of a second synchronization signal block at a second network node in a second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset.

[0129] In some examples, the timing offset is based on an epoch time, a reference time, or both of the first network node. In some examples, the first network node includes a first satellite or a first platform that provides a first service link for a first non-terrestrial network cell. In some examples, the second network node includes a second satellite or a second platform that provides a second service link for a second non-terrestrial network cell, the second service link being different from the first service link.

[0130] In some examples, to support calculating timing, the synchronization signal block component 640 can be configured to or otherwise support components for calculating timing based on a transmission time of a synchronization signal block transmitted by a network node associated with the second non-terrestrial network cell, wherein the cell synchronization information indicates the transmission time. In some examples, the transmission time indicates an SFN and a subframe based on the timing of the first non-terrestrial network cell.

[0131] Figure 7 A diagram of a system 700 including a device 705 supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The device 705 may be an example of a device 405, a device 505, or a UE 115 as described herein or include components thereof. The device 705 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 705 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, a memory 730, a code 735, and a processor 740. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745).

[0132] I / O controller 710 can manage input signals and output signals of device 705. I / O controller 710 can also manage peripheral devices that are not integrated into device 705. In some cases, I / O controller 710 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 710 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 710 may be implemented as part of a processor (such as processor 740). In some cases, a user may interact with device 705 via I / O controller 710 or via hardware components controlled by I / O controller 710.

[0133] In some cases, the device 705 may include a single antenna 725. However, in some other cases, the device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 715 may communicate bidirectionally via one or more antennas 725, a wired or wireless link, as described herein. For example, the transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 715 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 725 for transmission, and for demodulating packets received from one or more antennas 725. The transceiver 715 or the transceiver 715 and the one or more antennas 725 may be examples of transmitters 415, transmitters 515, receivers 410, receivers 510, or any combination thereof or components thereof as described herein.

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

[0135] The processor 740 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 730) so that the device 705 performs various functions (e.g., functions or tasks that support timing synchronization for non-terrestrial network communications). For example, the device 705 or a component of the device 705 may include a processor 740 and a memory 730 coupled to or coupled to the processor 740, and the processor 740 and the memory 730 are configured to perform the various functions described herein.

[0136] The communication manager 720 may support wireless communication at a UE communicating with a first non-terrestrial network cell according to examples as disclosed herein. For example, the communication manager 720 may be configured to or otherwise support a component for receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point. The communication manager 720 may be configured to or otherwise support a component for calculating timing associated with signaling from the second non-terrestrial network cell based on the cell synchronization information. The communication manager 720 may be configured to or otherwise support a component for receiving one or more signals from the second non-terrestrial network cell based on the calculated timing.

[0137] By including or configuring the communication manager 720 according to examples as described herein, the device 705 may support techniques for timing synchronization for non-terrestrial networks with improved communication reliability, improved coordination between devices, and reduced power consumption.

[0138] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 715, one or more antennas 725, or any combination thereof. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or performed by the processor 740, the memory 730, the code 735, or any combination thereof. For example, the code 735 may include instructions that are executable by the processor 740 to cause the device 705 to perform various aspects of timing synchronization for non-terrestrial network communications as described herein, or the processor 740 and the memory 730 may be otherwise configured to perform or support such operations.

[0139] Figure 8 A block diagram 800 of a device 805 supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0140] The receiver 810 may provide means for obtaining (e.g., receiving, determining, identifying) 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). The information may be passed to other components of the device 805. In some examples, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0141] The transmitter 815 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 805. For example, the transmitter 815 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, the transmitter 815 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 815 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0142] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of timing synchronization for non-terrestrial network communications as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0143] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0144] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0145] In some examples, the communication manager 820 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or integrate with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0146] The communication manager 820 may support wireless communications at a network node associated with a first non-terrestrial network cell according to examples as disclosed herein. For example, the communication manager 820 may be configured to or otherwise support components for determining one or more timing parameters of a second non-terrestrial network cell that is different from the first non-terrestrial network cell. The communication manager 820 may be configured to or otherwise support components for sending a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based on the one or more timing parameters.

[0147] By including or configuring a communications manager 820 according to examples as described herein, a device 805 (e.g., a processor controlling or otherwise coupled to a receiver 810, a transmitter 815, a communications manager 820, or a combination thereof) may support techniques for timing synchronization for non-terrestrial networks with reduced power consumption and more efficient use of communications resources.

[0148] Fig. 9 A block diagram 900 of a device 905 supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0149] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) 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). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0150] The transmitter 915 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 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, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0151] The device 905 or its various components may be examples of components for performing various aspects of timing synchronization for non-terrestrial network communications as described herein. For example, the communication manager 920 may include a timing parameter manager 925, a synchronization information transmitter 930, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0152] The communication manager 920 may support wireless communication at a network node associated with a first non-terrestrial network cell according to examples as disclosed herein. The timing parameter manager 925 may be configured to or otherwise support components for determining one or more timing parameters of a second non-terrestrial network cell that is different from the first non-terrestrial network cell. The synchronization information sender 930 may be configured to or otherwise support components for sending a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based on the one or more timing parameters.

[0153] Fig.10 A block diagram 1000 of a communication manager 1020 supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of components for performing various aspects of timing synchronization for non-terrestrial network communications as described herein. For example, the communication manager 1020 may include a timing parameter manager 1025, a synchronization information transmitter 1030, a reference point manager 1035, a timing offset manager 1040, a timing difference manager 1045, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0154] The communication manager 1020 may support wireless communication at a network node associated with a first non-terrestrial network cell according to examples as disclosed herein. The timing parameter manager 1025 may be configured to or otherwise support components for determining one or more timing parameters of a second non-terrestrial network cell that is different from the first non-terrestrial network cell. The synchronization information transmitter 1030 may be configured to or otherwise support components for sending a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based on one or more timing parameters. In some examples, the message includes a measurement object configuration for a set of one or more non-terrestrial network cells including the second non-terrestrial network cell.

[0155] In some examples, to support determining one or more timing parameters, the reference point manager 1035 may be configured as or otherwise support components for determining that a first uplink time synchronization reference point of a first non-terrestrial network cell is synchronized with a second uplink time synchronization reference point of a second non-terrestrial network cell, wherein cell synchronization information indicates that the first uplink time synchronization reference point and the second uplink time synchronization reference point are synchronized.

[0156] In some examples, to support determining one or more timing parameters, the timing offset manager 1040 may be configured to or otherwise support components for generating a timing offset value corresponding to a difference between a first uplink time synchronization reference point of a first non-terrestrial network cell and a second uplink time synchronization reference point of a second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset value. In some examples, the timing offset value includes a system frame number, a subframe, a time slot number, or any combination thereof.

[0157] In some examples, to support determining one or more timing parameters, the timing difference manager 1045 may be configured as or otherwise support components for calculating a timing difference between a downlink transmission of a first non-terrestrial network cell and a downlink transmission of a second non-terrestrial network cell, the timing difference being based on a first reference point of the first non-terrestrial network cell and a second reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing difference.

[0158] In some examples, the first reference point includes a first satellite or a first platform or both that provides a first service link for a first non-terrestrial network cell. In some examples, the second reference point includes a second satellite or a second platform or both that provides a second service link for a second non-terrestrial network cell, the second service link being different from the first service link.

[0159] In some examples, to support determining one or more timing parameters, the timing offset manager 1040 can be configured to or otherwise support components for determining a timing offset between a first synchronization signal block arrival time at a first network node of a first non-terrestrial network cell and a second synchronization signal block arrival time at a second network node of a second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset. In some examples, the timing offset is based on an epoch time, a reference time, or both of the first network node.

[0160] In some examples, the first network node includes a first satellite or a first platform that provides a first service link for a first non-terrestrial network cell. In some examples, the second network node includes a second satellite or a second platform that provides a second service link for a second non-terrestrial network cell, the second service link being different from the first service link.

[0161] In some examples, to support determining one or more timing parameters, the timing parameter manager 1025 can be configured to or otherwise support components for determining a transmission time of a synchronization signal block transmitted by a second network node associated with a second non-terrestrial network cell, wherein the cell synchronization information indicates the transmission time, and the transmission time indicates a SFN and a subframe based on the timing of the first non-terrestrial network cell. In some examples, the message includes a radio resource control message, a handover message, system information, or any combination thereof.

[0162] Fig.11 A diagram of a system 1100 including a device 1105 supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a network entity 105 as described herein or include components thereof. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support output and receive communications, such as a communication manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, a code 1130, and a processor 1135. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1140).

[0163] As described herein, the transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1105 may include one or more antennas 1115, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1110 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1115, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1115, from a wired receiver), and for demodulating the signal. In some implementations, the transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1115 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1115 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1110 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform the following operations: perform or support operations based on received or obtained information or signals, or generate information or other signals for transmission or other output, or any combination of these operations. In some implementations, the transceiver 1110 or the transceiver 1110 and one or more antennas 1115 or the transceiver 1110 and one or more antennas 1115 and one or more processors or memory components (e.g., processor 1135 or memory 1125 or both) may be included in a chip or chip component installed in the device 1105. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0164] Memory 1125 may include RAM and ROM. Memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by processor 1135, cause device 1105 to perform various functions described herein. Code 1130 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1130 may not be directly executable by processor 1135, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1125 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0165] The processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic element, a discrete hardware component, or any combination thereof). In some cases, the processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1135. The processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1125) so that the device 1105 performs various functions (e.g., various functions or tasks supporting timing synchronization for non-terrestrial network communications). For example, the device 1105 or a component of the device 1105 may include a processor 1135 and a memory 1125 coupled to the processor 1135, and the processor 1135 and the memory 1125 are configured to perform the various functions described herein. The processor 1135 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software, such as an operating system, a virtual machine, or a container instance) that can host functions (e.g., by executing code 1130) to perform functions of the device 1105. The processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1105 (such as in the memory 1125). In some specific implementations, the processor 1135 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be delivered to, for example, other systems or components of the device 1105). For example, the processing system of the device 1105 may refer to a system including various other components or subcomponents of the device 1105, such as the processor 1135, or the transceiver 1110, or the communication manager 1120, or other components or combinations of components of the device 1105. The processing system of device 1105 can interface with other components of device 1105, and can process information (such as input or signal) received from other components or output information to other components. For example, a chip or modem of device 1105 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that device 1105 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1105 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0166] In some examples, bus 1140 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1140 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1105, or communications performed between different components of device 1105 that may be co-located or located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, memory 1125, code 1130, and processor 1135 may be located in one of the different components or divided between the different components).

[0167] In some examples, the communication manager 1120 can manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1120 can manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1120 can manage communications with other network entities 105 and can include a controller or scheduler for controlling communications with the UE 115 in coordination with the other network entities 105. In some examples, the communication manager 1120 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0168] The communication manager 1120 may support wireless communications at a network node associated with a first non-terrestrial network cell according to examples as disclosed herein. For example, the communication manager 1120 may be configured to or otherwise support components for determining one or more timing parameters of a second non-terrestrial network cell that is different from the first non-terrestrial network cell. The communication manager 1120 may be configured to or otherwise support components for sending a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based on the one or more timing parameters.

[0169] By including or configuring a communication manager 1120 according to examples as described herein, the device 1105 may support techniques for timing synchronization for non-terrestrial networks with improved communication reliability, improved coordination between devices, and reduced power consumption.

[0170] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof. 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 performed by the transceiver 1110, the processor 1135, the memory 1125, the code 1130, or any combination thereof. For example, the code 1130 may include instructions that are executable by the processor 1135 to cause the device 1105 to perform various aspects of timing synchronization for non-terrestrial network communications as described herein, or the processor 1135 and the memory 1125 may be otherwise configured to perform or support such operations.

[0171] Fig.12 A flowchart illustrating a method 1200 for supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0172] At 1205, the method may include receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed by Figure 6 The described synchronization component 625 performs.

[0173] At 1210, the method may include calculating timing associated with signaling from a second non-terrestrial network cell based on the cell synchronization information. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference to Figure 6 The timing component 630 is described to perform.

[0174] At 1215, the method may include receiving one or more signals from a second non-terrestrial network cell based on the calculated timing. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Figure 6 The signal monitoring component 635 is described to perform.

[0175] Fig.13 A flowchart illustrating a method 1300 for supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0176] At 1305, the method may include receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point, wherein the cell synchronization information indicates that a first uplink time synchronization reference point of the first non-terrestrial network cell is synchronized with a second uplink time synchronization reference point of the second non-terrestrial network cell. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by Figure 6 The described synchronization component 625 performs.

[0177] At 1310, the method may include calculating timing associated with signaling from a second non-terrestrial network cell based on the cell synchronization information and synchronization of the first uplink time synchronization reference point with the second uplink time synchronization reference point. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by as described in reference to Figure 6 The timing component 630 is described to perform.

[0178] At 1315, the method may include receiving one or more signals from a second non-terrestrial network cell based on the calculated timing. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figure 6 The signal monitoring component 635 is described to perform.

[0179] Fig.14A flowchart illustrating a method 1400 for supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0180] At 1405, the method may include receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point, wherein the cell synchronization information indicates a timing offset between a first uplink time synchronization reference point of the first non-terrestrial network cell and a second uplink time synchronization reference point of the second non-terrestrial network cell. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by Figure 6 The described synchronization component 625 performs.

[0181] At 1410, the method may include calculating timing associated with signaling from a second non-terrestrial network cell based on the cell synchronization information and the timing offset value. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 6 The timing component 630 is described to perform.

[0182] At 1415, the method may include receiving one or more signals from a second non-terrestrial network cell based on the calculated timing. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 6 The signal monitoring component 635 is described to perform.

[0183] Fig.15 A flow chart illustrating a method 1500 for supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 3 as well as Figures 8 to 11 The described network entity performs. In some examples, the network entity may execute an instruction set 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 various aspects of the described functions.

[0184] At 1505, the method may include determining one or more timing parameters of a second non-terrestrial network cell that is different from the first non-terrestrial network cell. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.10 The described timing parameter manager 1025 performs.

[0185] At 1510, the method may include sending a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based on one or more timing parameters. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by Fig.10 The described synchronization information sender 1030 performs.

[0186] Fig.16 A flow chart illustrating a method 1600 for supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 3 as well as Figures 8 to 11 The described network entity performs. In some examples, the network entity may execute an instruction set 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 various aspects of the described functions.

[0187] At 1605, the method may include determining one or more timing parameters of a second non-terrestrial network cell that is different from the first non-terrestrial network cell. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.10 The described timing parameter manager 1025 performs.

[0188] At 1610, the method may include determining that a first uplink time synchronization reference point of a first non-terrestrial network cell is synchronized with a second uplink time synchronization reference point of a second non-terrestrial network cell. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.10 The reference point manager 1035 described performs.

[0189] At 1615, the method may include sending a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based on one or more timing parameters, wherein the cell synchronization information indicates that the first uplink time synchronization reference point is synchronized with the second uplink time synchronization reference point. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed by Fig.10 The described synchronization information sender 1030 performs.

[0190] Fig.17 A flowchart illustrating a method 1700 for supporting timing synchronization for non-terrestrial network communications according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 3 as well as Figures 8 to 11 The described network entity performs. In some examples, the network entity may execute an instruction set 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 various aspects of the described functions.

[0191] At 1705, the method may include determining one or more timing parameters of a second non-terrestrial network cell that is different from the first non-terrestrial network cell. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.10 The described timing parameter manager 1025 performs.

[0192] At 1710, the method may include generating a timing offset value corresponding to a difference between a first uplink time synchronization reference point of a first non-terrestrial network cell and a second uplink time synchronization reference point of a second non-terrestrial network cell. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.10 The described timing offset manager 1040 performs.

[0193] At 1715, the method may include sending a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based on one or more timing parameters, wherein the cell synchronization information indicates a timing offset value. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by Fig.10 The described synchronization information sender 1030 performs.

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

[0195] Aspect 1: A method for performing wireless communications at a UE communicating with a first non-terrestrial network cell, comprising: receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell have synchronization timing parameters; calculating timing associated with signaling from the second non-terrestrial network cell based at least in part on the cell synchronization information; and monitoring one or more signals from the second non-terrestrial network cell based at least in part on the calculated timing.

[0196] Aspect 2: A method according to Aspect 1, wherein calculating the timing includes: calculating the timing based at least in part on synchronization of a first uplink time synchronization reference point of the first non-terrestrial network cell with a second uplink time synchronization reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates that the first uplink time synchronization reference point and the second uplink time synchronization reference point are synchronized.

[0197] Aspect 3: A method according to Aspect 1, wherein calculating the timing includes: calculating the timing based at least in part on a timing offset value between a first uplink time synchronization reference point of the first non-terrestrial network cell and a second uplink time synchronization reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset.

[0198] Aspect 4: The method according to aspect 3, wherein the timing offset value comprises a system frame number, a subframe, a time slot number, or any combination thereof.

[0199] Aspect 5: A method according to any one of Aspects 1 to 4, wherein receiving the message includes: receiving the message from the first non-terrestrial network cell, the message including a measurement object configuration for a set of one or more non-terrestrial network cells including the second non-terrestrial network cell.

[0200] Aspect 6: The method according to any one of Aspects 1, 2 and 5 further includes: determining that the first uplink time synchronization reference point of the first non-terrestrial network cell is synchronized with the second uplink time synchronization reference point of the second non-terrestrial network cell based at least in part on the message excluding the indication of the timing offset value.

[0201] Aspect 7: A method according to Aspect 1, wherein calculating the timing includes: calculating the timing based at least in part on a timing difference between a downlink transmission of the first non-terrestrial network cell and a downlink transmission of the second non-terrestrial network cell, the timing difference being based at least in part on a first reference point of the first non-terrestrial network cell and a second reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing difference.

[0202] Aspect 8: A method according to Aspect 7, wherein the first reference point includes a first satellite or a first platform or both that provides a first service link for the first non-terrestrial network cell; and the second reference point includes a second satellite or a second platform or both that provides a second service link for the second non-terrestrial network cell, and the second service link is different from the first service link.

[0203] Aspect 9: A method according to any one of Aspect 1, wherein calculating the timing includes: calculating the timing based at least in part on a timing offset between an arrival time of a first synchronization signal block at a first network node of the first non-terrestrial network cell and an arrival time of a second synchronization signal block at a second network node of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset.

[0204] Aspect 10: The method according to aspect 9, wherein the timing offset is based at least in part on an epoch time, a reference time, or both of the first network node.

[0205] Aspect 11: A method according to any one of Aspects 9 to 10, wherein the first network node includes a first satellite or a first platform that provides a first service link for the first non-terrestrial network cell; and the second network node includes a second satellite or a second platform that provides a second service link for the second non-terrestrial network cell, and the second service link is different from the first service link.

[0206] Aspect 12: A method according to any one of Aspects 1 to 11, wherein calculating the timing includes: calculating the timing at least partially based on the sending time of a synchronization signal block sent by a network node associated with the second non-terrestrial network cell, wherein the cell synchronization information indicates the sending time.

[0207] Aspect 13: The method according to aspect 12, wherein the transmission time indication is based at least in part on a system frame number and subframe of timing of the first non-terrestrial network cell.

[0208] Aspect 14: The method according to any one of aspects 1 to 13, wherein the message comprises a radio resource control message from the first non-terrestrial network cell.

[0209] Aspect 15: The method according to any one of aspects 1 to 14, wherein the message comprises a handover message from the second non-terrestrial network cell.

[0210] Aspect 16: The method according to Aspect 15, wherein the message further indicates a reception time associated with a time when the first non-terrestrial network cell received a handover command from the second non-terrestrial network cell before the first non-terrestrial network cell sent the message to the UE.

[0211] Aspect 17: The method according to any one of aspects 1 to 16, wherein the message comprises a system information message from the first non-terrestrial network cell or the second non-terrestrial network cell.

[0212] Aspect 18: A method for performing wireless communications at a network node associated with a first non-terrestrial network cell, comprising: determining one or more timing parameters of a second non-terrestrial network cell that is different from the first non-terrestrial network cell; and sending a message indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based at least in part on the one or more timing parameters.

[0213] Aspect 19: A method according to Aspect 18, wherein determining the one or more timing parameters includes: determining that a first uplink time synchronization reference point of the first non-terrestrial network cell is synchronized with a second uplink time synchronization reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates that the first uplink time synchronization reference point and the second uplink time synchronization reference point are synchronized.

[0214] Aspect 20: A method according to Aspect 18, wherein determining the one or more timing parameters includes: generating a timing offset value corresponding to the difference between a first uplink time synchronization reference point of the first non-terrestrial network cell and a second uplink time synchronization reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset value.

[0215] Aspect 21: The method according to aspect 20, wherein the timing offset value comprises a system frame number, a subframe, a time slot number, or any combination thereof.

[0216] Aspect 22: The method according to any one of aspects 20 to 21, wherein the message comprises a measurement object configuration for a set of one or more non-terrestrial network cells including the second non-terrestrial network cell.

[0217] Aspect 23: A method according to Aspect 18, wherein determining the one or more timing parameters includes: calculating the timing difference between the downlink transmission of the first non-terrestrial network cell and the downlink transmission of the second non-terrestrial network cell, the timing difference being at least partially based on a first reference point of the first non-terrestrial network cell and a second reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing difference.

[0218] Aspect 24: A method according to Aspect 23, wherein the first reference point includes a first satellite or a first platform or both that provides a first service link for the first non-terrestrial network cell; and the second reference point includes a second satellite or a second platform or both that provides a second service link for the second non-terrestrial network cell, and the second service link is different from the first service link.

[0219] Aspect 25: A method according to Aspect 18, wherein determining the one or more timing parameters includes: determining a timing offset between an arrival time of a first synchronization signal block at a first network node of the first non-terrestrial network cell and an arrival time of a second synchronization signal block at a second network node of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset.

[0220] Aspect 26: The method according to aspect 25, wherein the timing offset is based at least in part on an epoch time, a reference time, or both of the first network node.

[0221] Aspect 27: A method according to any one of Aspects 25 to 26, wherein the first network node includes a first satellite or a first platform that provides a first service link for the first non-terrestrial network cell; and the second network node includes a second satellite or a second platform that provides a second service link for the second non-terrestrial network cell, and the second service link is different from the first service link.

[0222] Aspect 28: A method according to any one of Aspects 18 to 27, wherein determining the one or more timing parameters includes: determining a sending time of a synchronization signal block sent by a second network node associated with the second non-terrestrial network cell, wherein the cell synchronization information indicates the sending time, and the sending time indication is at least partially based on the system frame number and subframe of the timing of the first non-terrestrial network cell.

[0223] Aspect 29: An apparatus for performing wireless communications at a UE communicating with a first non-terrestrial network cell, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 17.

[0224] Aspect 30: An apparatus for wireless communications at a UE in communication with a first non-terrestrial network cell, comprising at least one component for performing a method according to any one of aspects 1 to 17.

[0225] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication at a UE in communication with a first non-terrestrial network cell, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 17.

[0226] Aspect 32: An apparatus for wireless communication at a network node associated with a first non-terrestrial network cell, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 18 to 28.

[0227] Aspect 33: An apparatus for wireless communications at a network node associated with a first non-terrestrial network cell, comprising at least one component for performing a method according to any one of aspects 18 to 28.

[0228] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a network node associated with a first non-terrestrial network cell, the code comprising instructions executable by a processor to perform the method according to any one of aspects 18 to 28.

[0229] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0230] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0231] The information and signals described herein may 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 specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0232] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0233] 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 codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of the present 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, hard wiring, or a combination of any of these items. Features that implement the functions can also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0234] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, while optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0235] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of 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). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0236] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0237] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0238] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. A method for wireless communication at a user equipment (UE) in communication with a first non-terrestrial network cell, comprising: receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point; calculating timing associated with signaling from the second non-terrestrial network cell based at least in part on the cell synchronization information; as well as One or more signals are received from the second non-terrestrial network cell based at least in part on the calculated timing.

2. The method of claim 1 , wherein calculating the timing comprises: The timing is calculated at least in part based on synchronization of a first uplink time synchronization reference point of the first non-terrestrial network cell with a second uplink time synchronization reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates that the first uplink time synchronization reference point and the second uplink time synchronization reference point are synchronized.

3. The method of claim 1 , wherein calculating the timing comprises: The timing is calculated based at least in part on a timing offset value between a first uplink time synchronization reference point of the first non-terrestrial network cell and a second uplink time synchronization reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset.

4. The method of claim 3, wherein the timing offset value comprises a system frame number, a subframe, a time slot number, or any combination thereof.

5. The method of claim 3, wherein receiving the message comprises: The message is received from the first non-terrestrial network cell, the message including a measurement object configuration for a set of one or more non-terrestrial network cells including the second non-terrestrial network cell.

6. The method according to claim 1, further comprising: Determining that a first uplink time synchronization reference point of the first non-terrestrial network cell is synchronized with a second uplink time synchronization reference point of the second non-terrestrial network cell based at least in part on the message excluding an indication of a timing offset value.

7. The method of claim 1 , wherein calculating the timing comprises: The timing is calculated at least in part based on a timing difference between a downlink transmission of the first non-terrestrial network cell and a downlink transmission of the second non-terrestrial network cell, the timing difference being at least in part based on a first reference point of the first non-terrestrial network cell and a second reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing difference.

8. The method according to claim 7, wherein: The first reference point includes a first satellite or a first platform or both that provides a first service link for the first non-terrestrial network cell; and The second reference point includes a second satellite or a second platform or both providing a second service link for the second non-terrestrial network cell, the second service link being different from the first service link.

9. The method of claim 1 , wherein calculating the timing comprises: The timing is calculated at least in part based on a timing offset between an arrival time of a first synchronization signal block at a first network node of the first non-terrestrial network cell and an arrival time of a second synchronization signal block at a second network node of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset.

10. The method of claim 9, wherein the timing offset is based at least in part on an epoch time, a reference time, or both of the first network node.

11. The method according to claim 9, wherein: The first network node comprises a first satellite or a first platform providing a first service link for the first non-terrestrial network cell; and The second network node includes a second satellite or a second platform providing a second service link for the second non-terrestrial network cell, the second service link being different from the first service link.

12. The method of claim 1, wherein calculating the timing comprises: The timing is calculated based at least in part on a transmission time of a synchronization signal block transmitted by a network node associated with the second non-terrestrial network cell, wherein the cell synchronization information indicates the transmission time.

13. The method of claim 12, wherein the transmit time indication is based at least in part on a system frame number and subframe of timing of the first non-terrestrial network cell.

14. The method of claim 1, wherein the message comprises a radio resource control message from the first non-terrestrial network cell.

15. The method of claim 1, wherein the message comprises a handover message from the second non-terrestrial network cell.

16. The method of claim 15, wherein the message further indicates a reception time associated with a time at which the first non-terrestrial network cell received a handover command from the second non-terrestrial network cell before the first non-terrestrial network cell sent the message to the UE.

17. The method of claim 1, wherein the message comprises a system information message from the first non-terrestrial network cell or the second non-terrestrial network cell.

18. A method for wireless communication at a network node associated with a first non-terrestrial network cell, comprising: determining one or more timing parameters of a second non-terrestrial network cell different from the first non-terrestrial network cell; as well as A message is sent indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based at least in part on the one or more timing parameters.

19. The method of claim 18, wherein determining the one or more timing parameters comprises: Determine that a first uplink time synchronization reference point of the first non-terrestrial network cell is synchronized with a second uplink time synchronization reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates that the first uplink time synchronization reference point and the second uplink time synchronization reference point are synchronized.

20. The method of claim 18, wherein determining the one or more timing parameters comprises: A timing offset value corresponding to a difference between a first uplink time synchronization reference point of the first non-terrestrial network cell and a second uplink time synchronization reference point of the second non-terrestrial network cell is generated, wherein the cell synchronization information indicates the timing offset value.

21. The method of claim 20, wherein the timing offset value comprises a system frame number, a subframe, a time slot number, or any combination thereof.

22. The method of claim 20, wherein the message comprises a measurement object configuration for a set of one or more non-terrestrial network cells including the second non-terrestrial network cell.

23. The method of claim 18, wherein determining the one or more timing parameters comprises: Calculate a timing difference between a downlink transmission of the first non-terrestrial network cell and a downlink transmission of the second non-terrestrial network cell, the timing difference being based at least in part on a first reference point of the first non-terrestrial network cell and a second reference point of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing difference.

24. The method of claim 23, wherein: The first reference point includes a first satellite or a first platform or both that provides a first service link for the first non-terrestrial network cell; and The second reference point includes a second satellite or a second platform or both providing a second service link for the second non-terrestrial network cell, the second service link being different from the first service link.

25. The method of claim 18, wherein determining the one or more timing parameters comprises: Determine a timing offset between an arrival time of a first synchronization signal block at a first network node of the first non-terrestrial network cell and an arrival time of a second synchronization signal block at a second network node of the second non-terrestrial network cell, wherein the cell synchronization information indicates the timing offset.

26. The method of claim 25, wherein the timing offset is based at least in part on an epoch time, a reference time, or both of the first network node.

27. The method of claim 25, wherein: The first network node comprises a first satellite or a first platform providing a first service link for the first non-terrestrial network cell; and The second network node includes a second satellite or a second platform providing a second service link for the second non-terrestrial network cell, the second service link being different from the first service link.

28. The method of claim 18, wherein determining the one or more timing parameters comprises: Determine a sending time of a synchronization signal block sent by a second network node associated with the second non-terrestrial network cell, wherein the cell synchronization information indicates the sending time, and the sending time indication is at least partially based on a system frame number and subframe of the timing of the first non-terrestrial network cell.

29. An apparatus for wireless communication at a user equipment (UE) in communication with a first non-terrestrial network cell, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a message indicating cell synchronization information for a second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point; calculating timing associated with signaling from the second non-terrestrial network cell based at least in part on the cell synchronization information; as well as One or more signals are received from the second non-terrestrial network cell based at least in part on the calculated timing.

30. An apparatus for wireless communication at a network node associated with a first non-terrestrial network cell, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: determining one or more timing parameters of a second non-terrestrial network cell different from the first non-terrestrial network cell; as well as A message is sent indicating cell synchronization information for the second non-terrestrial network cell, the cell synchronization information indicating whether the first non-terrestrial network cell and the second non-terrestrial network cell are synchronized at a reference point based at least in part on the one or more timing parameters.

Images