User equipment (UE) mobility between non-terrestrial network (NTN) and terrestrial network (TN)

Abstract

Methods, systems, and devices for wireless communication are described. In some systems, a user equipment (UE) may support mobility between a non-terrestrial network (NTN) cell and a terrestrial network (TN) cell. If the UE connects to the NTN cell, the UE may use a reference timestamp to determine the timing of the neighboring TN cell. A first network entity supporting the NTN cell may request the reference timestamp from a second network entity supporting the TN cell. The second network entity may output the timestamp in response to the request. The first network entity may obtain the timestamp and output an indication of the timestamp to the UE in a measurement gap configuration. The UE may use the reference timestamp to determine a timing of a measurement gap, and may monitor a signal (e.g., a synchronization signal) from the second network entity supporting the TN cell during the measurement gap.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 838,052, filed by Ryu et al. on June 10, 2022, entitled “USER EQUIPMENT (UE) MOBILITY BETWEEN ANON-TERRESTRIAL NETWORK (NTN) AND A TERRESTRIAL NETWORK (TN)”, which is assigned to the assignee of this patent application and is expressly incorporated herein by reference. Background Art

[0003] The following relates to wireless communications including user equipment (UE) mobility between cells of different types.

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. 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 of a communication device, which may be referred to as a UE. Summary of the invention

[0005] A method for wireless communication at a UE is described. The method may include receiving a first signal from a first network entity associated with a first cell type and operating via a first carrier frequency, the first signal including an indication of a reference timestamp of a measurement gap corresponding to a second network entity associated with a second cell type and operating via a second carrier frequency. In some examples, the method may include monitoring the second carrier frequency as part of a cell measurement procedure and during the measurement gap to obtain a second signal from the second network entity, the measurement gap being based on the reference timestamp.

[0006] An apparatus for wireless communication at a UE is described. The apparatus may include a processor and a memory coupled to the processor. The processor may be configured to receive a first signal from a first network entity associated with a first cell type and operating via a first carrier frequency, the first signal including an indication of a reference timestamp of a measurement gap, the reference timestamp corresponding to a second network entity associated with a second cell type and operating via a second carrier frequency. In some examples, the processor may be configured to monitor the second carrier frequency as part of a cell measurement procedure and during the measurement gap to obtain a second signal from the second network entity, the measurement gap being based on the reference timestamp.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving a first signal from a first network entity associated with a first cell type and operating via a first carrier frequency, the first signal including an indication of a reference timestamp of a measurement gap, the reference timestamp corresponding to a second network entity associated with a second cell type and operating via a second carrier frequency. In some examples, the apparatus may include: means for monitoring the second carrier frequency as part of a cell measurement procedure and during the measurement gap to obtain a second signal from the second network entity, the measurement gap being based on the reference timestamp.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to receive a first signal from a first network entity associated with a first cell type and operating via a first carrier frequency, the first signal including an indication of a reference timestamp of a measurement gap, the reference timestamp corresponding to a second network entity associated with a second cell type and operating via a second carrier frequency. In some examples, the code may include instructions executable by the processor to monitor the second carrier frequency as part of a cell measurement procedure and during the measurement gap to obtain a second signal from the second network entity, the measurement gap being based on the reference timestamp.

[0009] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving the second signal from the second network entity based on the monitored second carrier frequency. In some examples, the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: switching a connection from the first network entity to the second network entity based on one or more measurements of the second signal.

[0010] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the cell measurement procedure includes a first cell measurement procedure, and the method, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for the following actions: receiving a third signal from the second network entity, the third signal including a first priority value for the first carrier frequency corresponding to the first cell type. In some examples, the first priority value is less than a second priority value corresponding to the second cell type. In some examples, the method, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for the following actions: avoiding a second cell measurement procedure for the first carrier frequency based on the first priority value.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: avoiding a second cell measurement procedure for the first carrier frequency based on a first priority value for the first carrier frequency, the first priority value being based on the first carrier frequency corresponding to the first cell type. In some examples, the first priority value is less than a second priority value corresponding to the second cell type.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first cell type corresponds to a first priority value. In some examples, the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for the following actions: receiving a third signal from the first network entity, the third signal including a second priority value for the second carrier frequency, the second priority value based on the second carrier frequency corresponding to the second cell type, the second priority value being greater than the first priority value corresponding to the first cell type, and monitoring the second carrier frequency based on the second priority value.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for operating based on connected mode mobility, the second priority value for the second carrier frequency being associated with a configuration for the connected mode mobility.

[0014] In some examples, the first cell type corresponds to a first priority value. Some examples of methods, apparatus, and non-transitory computer-readable media configured to monitor the second carrier frequency may include operations, features, components, or instructions for monitoring the second carrier frequency based on a second priority value for the second carrier frequency, the second priority value being based on the second carrier frequency corresponding to the second cell type. In some examples, the second priority value is greater than the first priority value corresponding to the first cell type.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving a synchronization signal block (SSB) from the second network entity, the synchronization signal block (SSB) including a second timestamp corresponding to the second network entity. In some examples, the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: as part of a second cell measurement procedure, monitoring a third signal from the second network entity during the measurement gap based on the second timestamp.

[0016] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending a third signal indicating location information of the UE to the first network entity, indicating that the first signal corresponding to the reference timestamp of the second network entity is based on the location information of the UE.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the reference timestamp includes a Coordinated Universal Time (UTC) timestamp, a portion of the UTC timestamp, a Global Navigation Satellite System (GNSS) timestamp, a portion of the GNSS timestamp, or a combination thereof.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the reference timestamp indicates a system frame number (SFN) having a value of 0 for the second network entity.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first signal further indicates an offset in the time domain for the measurement gap, a periodicity of the measurement gap, a duration of the measurement gap, or a combination thereof. In some examples, monitoring the second carrier frequency is also based on the offset, the periodicity, the duration, or a combination thereof.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a third signal indicating a slot level offset for the measurement gap to the first network entity based on the measurement gap, the measurement gap being based on the reference timestamp corresponding to a downlink slot boundary of the second network entity crossing the first network entity.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving a third signal from the first network entity, the third signal indicating location information and a distance threshold of a group of multiple cells associated with the second cell type, the third signal indicating at least the corresponding location and the corresponding distance threshold of the second network entity. In some examples, the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: monitoring the second signal from the second network entity based on the UE being within the corresponding distance threshold of the corresponding location of the second network entity.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first cell type includes a non-terrestrial network (NTN) cell type and the second cell type includes a terrestrial network (TN) cell type.

[0023] A method for wireless communication at a first network entity is described. The method may include: outputting a first signal, the first signal including a request for a reference timestamp corresponding to a second network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. In some examples, the method may include: obtaining a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity; and outputting a third signal, the third signal indicating the reference timestamp corresponding to the second network entity, the third signal configuring a measurement gap for a UE.

[0024] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor and a memory, the memory coupled to the processor. The processor may be configured to output a first signal, the first signal including a request for a reference timestamp corresponding to a second network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. In some examples, the processor may be configured to obtain a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity; and output a third signal, the third signal indicating the reference timestamp corresponding to the second network entity, the third signal configuring a measurement gap for a UE.

[0025] Another apparatus for wireless communication at a first network entity is described. The apparatus may include means for outputting a first signal, the first signal including a request for a reference timestamp corresponding to a second network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. In some examples, the apparatus may include: means for obtaining a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity; and means for outputting a third signal, the third signal indicating the reference timestamp corresponding to the second network entity, the third signal configuring a measurement gap for a UE.

[0026] A non-transitory computer-readable medium storing code for wireless communication at a first network entity is described. The code may include instructions executable by a processor to output a first signal, the first signal including a request for a reference timestamp corresponding to a second network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. In some examples, the code may include instructions executable by a processor to obtain a second signal indicating the reference timestamp corresponding to the second network entity; and output a third signal indicating the reference timestamp corresponding to the second network entity, the third signal configuring a measurement gap for a UE.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: obtaining a fourth signal indicating the first location information of the UE. In some examples, the third signal is based on the first location information of the UE and the second location information of the second network entity.

[0028] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: outputting a fourth signal indicating location information and a distance threshold of a group of multiple cells associated with the second cell type, the fourth signal indicating at least the location and distance threshold of the second network entity.

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for obtaining, based on a periodicity, an additional signal indicating an additional reference timestamp corresponding to the second network entity.

[0030] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, the first cell type corresponds to a first priority value. In some examples, the method, apparatus, and non-transitory computer-readable medium may also include operations, features, components, or instructions for the following actions: outputting a fourth signal based on the second carrier frequency corresponding to the second cell type, the fourth signal including a second priority value of the second carrier frequency associated with the second network entity. In some examples, the second priority value is greater than the first priority value corresponding to the first cell type.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the reference timestamp includes a UTC timestamp, a portion of the UTC timestamp, a GNSS timestamp, a portion of the GNSS timestamp, or a combination thereof.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the reference timestamp indicates a SFN having a value of 0 for the second network entity.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first cell type includes an NTN cell type and the second cell type includes a TN cell type.

[0034] A method for wireless communication at a second network entity is described. The method may include obtaining a first signal, the first signal including a request for a reference timestamp corresponding to the second network entity, the request being associated with the first network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. In some examples, the method may include outputting a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. In some examples, the method may include outputting a third signal during a measurement gap, the measurement gap being based on the reference timestamp.

[0035] An apparatus for wireless communication at a second network entity is described. The apparatus may include a processor and a memory, the memory coupled to the processor. The processor may be configured to obtain a first signal, the first signal including a request for a reference timestamp corresponding to the second network entity, the request being associated with the first network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. In some examples, the processor may be configured to output a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. In some examples, the processor may be configured to output a third signal during a measurement gap, the measurement gap being based on the reference timestamp.

[0036] Another apparatus for wireless communication at a second network entity is described. The apparatus may include means for obtaining a first signal, the first signal including a request for a reference timestamp corresponding to the second network entity, the request being associated with the first network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. In some examples, the apparatus may include means for outputting a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. In some examples, the apparatus may include means for outputting a third signal during a measurement gap, the measurement gap being based on the reference timestamp.

[0037] A non-transitory computer-readable medium storing code for wireless communication at a second network entity is described. The code may include instructions executable by a processor to obtain a first signal, the first signal including a request for a reference timestamp corresponding to the second network entity, the request being associated with the first network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. In some examples, the code may include instructions executable by the processor to output a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. In some examples, the code may include instructions executable by the processor to output a third signal during a measurement gap, the measurement gap being based on the reference timestamp.

[0038] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for establishing a connection with the UE based on the third signal.

[0039] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for outputting the SSB including a second timestamp corresponding to the second network entity.

[0040] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for outputting an additional signal based on a periodicity, the additional signal indicating an additional reference timestamp corresponding to the second network entity.

[0041] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: outputting a fourth signal, the fourth signal including a first priority value corresponding to the first cell type for the first carrier frequency, the first priority value being less than a second priority value corresponding to the second cell type.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first cell type includes an NTN cell type and the second cell type includes a TN cell type. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 An example of a wireless communication system supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is illustrated.

[0044] Figure 2 An example of a network architecture supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is illustrated.

[0045] Figure 3 and Figure 4 An example of a wireless communication system supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is illustrated.

[0046] Figure 5 An example of a process flow for supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is illustrated.

[0047] Figure 6 and Figure 7 A block diagram of a device supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown.

[0048] Figure 8 A block diagram of a communication manager supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown.

[0049] Fig. 9A diagram of a system including devices supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown.

[0050] Fig.10 and Fig.11 A block diagram of a device supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown.

[0051] Fig.12 A block diagram of a communication manager supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown.

[0052] Fig.13 A diagram of a system including devices supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown.

[0053] Figures 14 to 16 A flow chart illustrating a method of supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0054] In some wireless communication systems, a UE may be connected to a wireless network via a cell of an NTN. As described herein, a cell may refer to a combination of frequency resources (e.g., carrier frequencies) and space resources (e.g., geographic regions) used for wireless communication. NTN may refer to a wireless communication system including non-terrestrial communication devices such as satellites, zeppelins, airships, balloons, or drones, etc. An NTN cell may be supported by a non-terrestrial communication device (e.g., a non-terrestrial network entity), such as a satellite, a zeppelin, airships, balloons, drones, unmanned aerial vehicles (UAVs), or another aviation device or a device capable of air-to-ground (ATG) communication. Additionally or alternatively, a UE may be connected to a wireless network via a cell of a TN. A TN may refer to a wireless communication system including ground communication devices such as a base station, an access point, or an Internet of Things (IoT) device, as well as other examples. A TN cell may be supported by a ground communication device (e.g., a ground network entity) such as a base station, an access point, an IoT device, or another ground device.

[0055] Some UEs may have the ability to switch between NTN connections and TN connections. However, compared to NTN cells (e.g., cells supported by non-terrestrial network entities), TN cells (e.g., cells supported by ground network entities) may provide improved wireless communication (e.g., higher signaling reliability, lower signaling latency, or both). For example, the ground network entity providing coverage for the TN cell may be fixed and closer to the UE than the non-terrestrial network entity providing coverage for the NTN cell, and in some cases, the non-terrestrial network entity may be mobile. Compared to the communication between the UE and the non-terrestrial network entity, the communication between the UE and the ground network entity may experience relatively low propagation delay, interference, and signal attenuation. Therefore, compared to via the non-terrestrial network entity, the UE can improve wireless communication reliability and latency by connecting to the network via the ground network entity. If the UE is located in both TN and NTN cell coverage, the UE may give priority to establishing or maintaining a connection with the ground network entity to support improved communication reliability and latency between the UE and the network (e.g., via the ground network entity).

[0056] Various aspects of the present disclosure may support techniques for managing and prioritizing TN connections while supporting mobility between TN cells and NTN cells. To support cell mobility, a UE may perform a cell measurement procedure. The cell measurement procedure may involve the UE monitoring a carrier frequency associated with a neighboring cell to obtain signaling (e.g., synchronization signals, reference signals) from the neighboring cell. The UE may monitor signaling within a measurement gap, which may be a time window during which the UE may tune the UE's radio frequency (RF) module to a carrier frequency associated with the neighboring cell. If the UE detects and receives signaling from a neighboring cell based on monitoring, the UE may measure one or more signal metrics (e.g., signal strength, signal quality) to determine whether to switch the network connection to the neighboring cell. In order to support accurate timing of measurement gap configuration for NTN to TN mobility, a non-terrestrial network entity may use the absolute timing of a terrestrial network entity (e.g., as opposed to using a measurement gap offset between the timing of the non-terrestrial network entity and the timing of the terrestrial network entity). Absolute timing of the terrestrial network entity may mitigate any potential timing misalignment between measurement gap configuration at the UE and synchronization signaling by the terrestrial network entity, thereby improving the reliability of cell measurements and synchronization signaling.

[0057] For example, the non-terrestrial network entity may request a reference timestamp (e.g., indicating absolute timing) from the terrestrial network entity. The terrestrial network entity may send the reference timestamp in response to the request. The non-terrestrial network entity may send an indication of the reference timestamp for the terrestrial network entity to the UE, and the UE may use the reference timestamp to determine the timing of the measurement gap. For example, as part of a cell measurement procedure, the UE may monitor a synchronization signal from the terrestrial network entity during the measurement gap based on the reference timestamp. In some examples, if the UE detects a synchronization signal from the terrestrial network entity, the UE may trigger NTN to TN mobility. The UE may switch the connection to the network from using the non-terrestrial network entity to using the terrestrial network entity, thereby improving signaling reliability and latency based on switching to the TN connection. Additionally or alternatively, by using a reference timestamp instead of a timing offset value between the non-terrestrial network entity and the terrestrial network entity (which may change frequently as the non-terrestrial network entity moves), the wireless communication system may reduce the signaling overhead associated with configuring the measurement gap. Additionally or alternatively, the UE, the network, or both may prioritize TN connections over NTN connections (e.g., using priority values ​​corresponding to different frequency ranges for different cell types). By prioritizing TN connections, the wireless communication system may increase the amount of time that the UE is connected to the network via a TN cell, which may be more reliable and may have less latency relative to an NTN cell.

[0058] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to process flows, device diagrams, system diagrams, and flow diagrams related to UE mobility between NTN and TN.

[0059] Figure 1 An example of a wireless communication system 100 supporting UE mobility between an NTN and a TN 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).

[0060] 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 names. 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) over 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 over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0061] 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 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 communication with various types of devices, such as Figure 1 Communications with other UEs 115 or network entities 105) as shown.

[0062] 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, 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 the second node.

[0063] 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 directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or 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), or other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0064] 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 giga 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 a converged (e.g., monolithic, standalone) 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).

[0065] 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)).

[0066] The split of functionality between CU 160, DU 165, and RU 170 is flexible and may support different functionality 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, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality 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) functionality 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 the CU 160 and the DU 165 or between the DU 165 and the RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by the other of the CU 160, DU 165, or RU 170). The CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. The CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via those communication links.

[0067] 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 the 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 host entities or IAB hosts. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a host network entity 105 (e.g., a host base station 140). One or more host network entities 105 (e.g., IAB hosts) 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 DU 165 of a coupled IAB host. 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.

[0068] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support UE mobility between an NTN and a TN 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 disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0069] 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 "device" may also be referred to as a unit, a station, a terminal, or a client, among other examples. 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, among other examples, which may be implemented in various objects such as appliances or vehicles, meters, among other examples.

[0070] 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, relay base stations, and other examples, such as Figure 1 shown.

[0071] 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 defined physical layer structure 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 with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device 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 the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

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

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

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

[0075] The signal waveform transmitted via the carrier may be composed of 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 resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The amount 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 large number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of the communication with UE 115.

[0076] One or more numerologies of carriers may be supported, and the numerologies may include subcarrier spacing ( ) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0077] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may refer to, for example, The sampling period is seconds, where 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).

[0078] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a plurality 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 plurality of symbol periods (e.g., depending on the length of a cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may also be divided into a plurality of mini-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.

[0079] A subframe, a slot, a mini-slot, or a 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 transmission 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 bursts of shortened TTIs (sTTIs)).

[0080] Physical channels may be multiplexed using carriers for communication according to various techniques. For example, physical control channels and physical data channels may be multiplexed for signaling transmission via downlink carriers 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)) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for 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 the control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the 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 a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

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

[0082] A macro cell covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by a UE 115 having a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) than a macro cell, and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 having a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0083] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.

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

[0085] 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). The UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communications may include private communications or group communications 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 applications or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency are used interchangeably herein.

[0086] In some examples, a 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 not be able or 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 occur between UEs 115 without involving network entity 105 .

[0087] 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 for UEs 115 served by network entities 105 (e.g., base stations 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 IP services 150 for 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.

[0088] 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). The 300 MHz to 3 GHz region may be referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths are in the range of from about 1 decimeter to 1 meter long. 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 service to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0089] The wireless communication system 100 may utilize both licensed RF spectrum bands 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, employing License Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating using an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on a 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.

[0090] The electromagnetic spectrum is often subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz‍–7.125 GHz) and FR2 (24.25 GHz‍–52.6 GHz). It should be understood that FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles, even though a portion of FR1 is greater than 6 GHz. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, even though it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0092] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, it can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4‍–1 or FR5, or may be within the EHF band.

[0093] 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) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can 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 set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communication with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0094] 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 sender device or a receiver device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the sender device and the receiver device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the sender device or the receiver 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 the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the sender device or the receiver device or relative to some other orientation).

[0095] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0096] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support HARQ feedback for the same time slot, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or based on some other time interval.

[0097] As described herein, a node, which may be referred to as a node, a network node, a network entity, or a wireless node, may be a base station 140 (e.g., any base station 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 network node may be a UE 115. As another example, the network node may be a base station 140. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE 115, the second network node may be a base station 140, and the third network node may be a UE 115. In another aspect of this example, the first network node may be a UE 115, the second network node may be a base station 140, and the third network node may be a base station 140. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different with respect to these examples.

[0098] Similarly, references to UE 115, base station 140, devices, equipment, computing systems, etc. may include disclosure of UE 115, base station 140, devices, equipment, computing systems, etc. as network nodes. For example, a disclosure that UE 115 is configured to receive information from base station 140 also discloses that the first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., UE 115 is configured to receive information from base station 140 also discloses that the first network node is configured to receive information from the second network node), the broader example of the narrower example may be interpreted inversely, but in a broad, open-ended manner. In the above example in which UE 115 is configured to receive information from base station 140 and also discloses that the first network node is configured to receive information from a second network node, the first network node may refer to a first UE 115 configured to receive information, a first base station 140, a first device, a first equipment, a first computing system, a first one or more components, a first processing entity, etc.; and the second network node may refer to a second UE 115, a second base station 140, a second device, a second equipment, a second computing system, a second one or more components, a second processing entity, etc.

[0099] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0100] 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). 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., an NTN cell type), and the terrestrial network entity 105 may correspond to a second cell type different from the first cell type (e.g., a TN cell type).

[0101] Some wireless communication systems 100 may support mobility between NTN cells and TN cells, which may be referred to as NTN-TN mobility. For example, a UE 115 connected to a network via a non-terrestrial network entity 105 may switch the connection to be connected to the network via a terrestrial network entity 105. This process may be referred to as NTN to TN mobility. Similarly, a UE 115 connected to a network via a terrestrial network entity 105 may switch the connection to be connected to the network via a non-terrestrial network entity 105. This process may be referred to as TN to NTN mobility. In some cases, in order to support NTN-TN mobility (e.g., supporting both NTN to TN mobility and TN to NTN mobility), the UE 115 may be an example of a dual-mode UE having both NTN capabilities and TN capabilities.

[0102] In some examples, a TN cell (e.g., a cell supported by a terrestrial network entity 105, which may include a base station 140) may provide improved wireless services (e.g., higher signaling reliability, less signaling latency, or both) compared to an NTN cell (e.g., a cell supported by a non-terrestrial network entity 105, which may include a satellite 185). For example, because the terrestrial network entity 105 providing coverage for a TN cell may be fixed and relatively closer to the UE 115 than the non-terrestrial network entity 105 providing coverage for an NTN cell, the UE 115 may improve wireless communication reliability and latency by connecting to the network via the terrestrial network entity 105 (as compared to via the non-terrestrial network entity 105). Accordingly, if the UE 115 is located in both TN and NTN cell coverage, the UE 115 may prioritize establishing a connection with the terrestrial network entity 105 to support improved communication reliability and latency between the UE 115 and the network (e.g., via the terrestrial network entity 105).

[0103] If UE 115 moves from pure NTN coverage to NTN and TN coverage, UE 115 (e.g., dual-mode UE) may trigger NTN to TN mobility. For example, in order to prioritize TN connections over NTN connections (e.g., for improved communication reliability and latency), if UE 115 is located where both TN connections and NTN connections are available, UE 115 may switch to TN connections. In contrast, if UE 115 moves from NTN and TN coverage to pure NTN coverage, UE 115 (e.g., dual-mode UE) may trigger TN to NTN mobility. For example, in order to prioritize TN connections over NTN connections, if TN connections are available to UE 115, UE 115 may avoid switching to NTN connections. However, if UE 115 is outside TN coverage but within NTN coverage, UE 115 may switch to NTN connections to maintain communication with the network.

[0104] To support NTN to TN mobility, UE 115 may perform a cell measurement procedure. For example, if UE 115 is connected to the network via non-terrestrial network entity 105, UE 115 may monitor one or more signals (e.g., synchronization signals) from terrestrial network entity 105 during a measurement gap. In some cases, non-terrestrial network entity 105 may operate via a first carrier frequency, and terrestrial network entity 105 may operate via a second carrier frequency. In order to measure the synchronization signal from terrestrial network entity 105, UE 115 may tune away from the first carrier frequency to the second carrier frequency during the measurement gap. Tuning away from the first carrier frequency may involve UE 115 suspending communication via the first carrier frequency and tuning a radio frequency (RF) module of UE 115 to communicate via the second carrier frequency for a portion of the time (e.g., during the measurement gap). That is, the duration of the signaling of the neighboring cell (e.g., terrestrial network entity 105 operating in a different frequency region) during which UE 115 suspends communication with the serving cell (e.g., non-terrestrial network entity 105) may be referred to as a measurement gap.

[0105] The network may configure the UE 115 with the measurement gap configuration. For example, the non-terrestrial network entity 105 may send a control signal to the UE 115 that configures one or more parameters for the measurement gap. Such parameters may configure the UE 115 to perform a cell measurement procedure concurrently with when the terrestrial network entity 105 is transmitting at least one synchronization signal, thereby enabling the UE 115 to receive the synchronization signal from the terrestrial network entity 105. Aligning the measurement gap of the UE 115 with the transmission of the synchronization signal by the terrestrial network entity 105 may involve timing coordination between the non-terrestrial network entity 105 and the terrestrial network entity 105. For example, a first timing tracked at the non-terrestrial network entity 105 may be different from a second timing tracked at the terrestrial network entity 105. However, because the timing of the non-terrestrial network entity 105 drifts over time (e.g., due to movement of the satellite 185) while the timing of the terrestrial network entity 105 remains relatively constant, the timing offset between the first timing tracked at the non-terrestrial network entity 105 and the second timing tracked at the terrestrial network entity 105 may change relatively quickly (e.g., may change by a threshold amount within a threshold time period).

[0106] To support accurate timing of measurement gap configuration, the non-terrestrial network entity 105 may use absolute timing of the terrestrial network entity 105 (e.g., as opposed to a measurement gap offset between the timing of the non-terrestrial network entity 105 and the timing of the terrestrial network entity 105). The absolute timing of the terrestrial network entity 105 may mitigate any potential timing misalignment between the measurement gap configuration and synchronization signaling of the terrestrial network entity 105 at the UE 115.

[0107] For example, the non-terrestrial network entity 105 (e.g., using the network entity communication manager 101) may request a reference timestamp (e.g., absolute timing) from the terrestrial network entity 105. The terrestrial network entity 105 (e.g., using the network entity communication manager 101) may send the reference timestamp in response to the request. The non-terrestrial network entity 105 may send an indication of the reference timestamp of the terrestrial network entity 105 to the UE 115. The UE 115 (e.g., using the UE communication manager 102) may use the reference timestamp to determine the timing of the measurement gap. For example, as part of a cell measurement procedure, the UE 115 may monitor a synchronization signal from the terrestrial network entity 105 during the measurement gap based on the reference timestamp. In some examples, if the UE 115 detects the synchronization signal from the terrestrial network entity 105, the UE 115 may trigger NTN to TN mobility. The UE 115 may switch the connection to the network from using the non-terrestrial network entity 105 to using the terrestrial network entity 105, thereby improving signaling reliability and latency based on the switch to the TN connection.

[0108] Figure 2 An example of a network architecture 200 that supports UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is illustrated. The network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with a core network 130-a through one or more decomposed network entities 105 (e.g., a near-RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a may be associated with a respective coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a may be served by multiple RUs 170-a simultaneously.

[0109] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals over a wireless transmission medium, or to send signals over a wireless transmission medium to one or more of the other network entities 105, or both.

[0110] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0111] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented with an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU160-a.

[0112] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0113] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0114] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

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

[0116] The network architecture 200 may support NTN-TN mobility. For example, any combination of network entities included in the network architecture 200 may support non-terrestrial network entities 105, terrestrial network entities 105, or a combination thereof. The non-terrestrial network entity 105 may include RU 170-a, DU 165-a, CU 160-a, or any combination thereof (e.g., as a component or otherwise connected to a satellite 185 or other non-terrestrial network entity 105). Similarly, the terrestrial network entity 105 may include RU 170-a, DU 165-a, CU 160-a, or any combination thereof (e.g., as a component or otherwise connected to a base station 140 or other terrestrial network entity 105). The network may hand over UE 115-a from the non-terrestrial network entity 105 to the terrestrial network entity 105 (or vice versa) to maintain a connection with UE 115-a. In some examples, the network, UE 115-a, or both may prioritize TN connections over NTN connections (e.g., to improve signaling reliability and reduce signaling latency).

[0117] Figure 3 An example of a wireless communication system 300 supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 may be as shown in FIG. Figure 1 In some examples, the wireless communication system 300 may include the wireless communication system 100 described above. Figure 2 The wireless communication system 300 may include: UE 115-b, which may be as described in reference Figure 1 and Figure 2 The example of UE 115 described; and network entity 105-a and network entity 105-b, which may be as described in reference Figure 1 and Figure 21 and 10. Examples of network entities 105 are described. In some cases, network entity 105-a may be an example of a terrestrial network entity 105-a, such as base station 140-a, and network entity 105-b may be an example of a non-terrestrial network entity 105-b, such as satellite 185-a. Wireless communication system 300 may use reference timestamp 330 to indicate timing of terrestrial network entity 105-a to support NTN to TN mobility of UE 115-b.

[0118] The ground network entity 105-a may provide network coverage for a first cell 310-a (e.g., a TN cell 310-a). The non-ground network entity 105-b may provide network coverage for a second cell 310-b (e.g., an NTN cell 310-b). In some cases, the UE 115-b may initially connect to the network via the non-ground network entity 105-b, which may include or may be an example of a satellite 185-a. For example, the UE 115-b may be located within the coverage area of ​​the second cell 310-b. The UE 115-b may communicate with the non-ground network entity 105-b via a downlink channel 315-a, an uplink channel 320, or both. In some examples, the UE 115-b may be connected to the non-ground network entity 105-b based on the UE 115-b being in pure NTN coverage (e.g., located within the coverage area of ​​one or more NTN cells but outside the coverage area of ​​TN cells). To improve signaling reliability and latency, UE 115 - b may prioritize handover to a TN cell (eg, TN cell 310 - a ) if such a TN cell is available to UE 115 - b .

[0119] UE 115-b may move from pure NTN coverage to NTN and TN coverage (e.g., where UE 115-b is located within a coverage area of ​​one or more NTN cells and one or more TN cells). UE 115-b may perform a cell measurement procedure to detect TN cells. For example, as part of the cell measurement procedure, UE 115-b may monitor a synchronization signal 360 from a ground network entity 105-a, such as an SSB on a downlink channel 315-b or a broadcast channel. If UE 115-b receives a synchronization signal 360 from a ground network entity 105-a (e.g., via a downlink channel 315-b) and a cell measurement associated with the ground network entity 105-a satisfies a threshold (e.g., a reference signal received power (RSRP) of the ground network entity 105-a is greater than a threshold RSRP or some other cell measurement condition is satisfied), UE 115-b may initiate a handover procedure from a non-ground network entity 105-b to a ground network entity 105-a. UE 115 - b may establish a connection with the terrestrial network entity 105 - a and may deactivate a connection with the non-terrestrial network entity 105 - b .

[0120] To support cell measurement procedures at UE 115-b, non-terrestrial network entity 105-b may send measurement gap configuration 335 to UE 115-b. Measurement gap configuration 335 may configure UE 115-b with parameters associated with performing cell measurements for a particular neighboring cell, such as TN cell 310-a supported by terrestrial network entity 105-a. The parameters may indicate to UE 115-b how to perform inter-frequency measurements, inter-RAT measurements, or both for the neighboring cell. For example, if terrestrial network entity 105-a operates via a different carrier frequency than non-terrestrial network entity 105-b, measurement gap configuration 335 may indicate a time period for UE 115-b to perform cell measurements for the carrier frequency of terrestrial network entity 105-a.

[0121] The measurement gap configuration 335 may indicate a measurement gap period, a measurement gap duration, a measurement gap offset, or any combination thereof. The measurement gap period may indicate the periodicity of the measurement gap. The measurement gap duration may indicate the length of time spanned by one instance of the measurement gap. The measurement gap offset may indicate a timing offset between a serving cell (e.g., a primary cell such as an NTN cell 310-b) and a neighboring cell (e.g., such as a TN cell 310-a). In some cases, the measurement gap offset may be defined relative to the timing of the primary cell. For TN mobility (e.g., mobility from a first TN cell to a second TN cell), the timing offset variation between the primary cell and the neighboring cell (both of which are TN cells) may be relatively small (e.g., below a threshold or otherwise negligible). Therefore, if the UE 115-b uses a fixed measurement gap offset received from the primary cell for a cell measurement procedure (e.g., radio resource management (RRM) measurement), the UE 115-b may maintain timing alignment.

[0122] However, for NTN to TN mobility, the timing offset change between the primary cell (e.g., NTN cell 310-b) and the neighboring cell (e.g., TN cell 310-a) may be significant (e.g., above a threshold) due to the drifting timing of the NTN cell 310-b. For example, if the TN cell 310-a is stationary, the timing of the TN cell 310-a may remain relatively constant, while if the NTN cell 310-b is mobile (e.g., the satellite 185-a moves in orbit), the timing of the NTN cell 310-b may change over time. The timing of a cell may correspond to the reception timing of the UE 115-b served by the cell. As the non-terrestrial network entity 105-b moves, the distance between the non-terrestrial network entity 105-b and the UE 115-b may change significantly (e.g., change greater than a threshold distance). Thus, the propagation delay of signaling between the non-terrestrial network entity 105-b and the UE 115-b may change based on the change in the distance the signal travels, resulting in a change in the timing of the signal reception at the UE 115-b. This may be referred to as a timing drift of the NTN cell 310-b. If the drift timing of the NTN cell 310-b exceeds a threshold, the timing offset change between the NTN cell 310-b and the TN cell 310-a may similarly exceed a threshold. In order to maintain the timing alignment of the measurement gaps at the UE 115-b, the non-terrestrial network entity 105-b may use the absolute timing of the TN cell 310-a (as opposed to or in addition to the measurement gap offset value) to mitigate the timing drift of the NTN cell 310-b.

[0123] For example, the measurement gap configuration 335 may include a reference timestamp 330 indicating an absolute timing of the TN cell 310-a. In some examples, the non-terrestrial network entity 105-b may send a reference timestamp request 325 to the terrestrial network entity 105-a via the gateway 305. The terrestrial network entity 105-a may receive the reference timestamp request 325 and determine a reference timestamp 330 for reporting to the non-terrestrial network entity 105-b. In some examples, the reference timestamp 330 may be an example of a UTC timestamp, a portion of a UTC timestamp (e.g., some least significant bits of a UTC timestamp), a GNSS timestamp, a portion of a GNSS timestamp (e.g., some least significant bits of a GNSS timestamp), or some other indication of an absolute timing of the TN cell 310-a. In some cases, the reference timestamp 330 may indicate a timing of a start of a frame corresponding to SFN 0. For example, the reference timestamp 330 may be a timestamp of a SFN=0 boundary at the terrestrial network entity 105-a.

[0124] In response to the reference timestamp request 325, the ground network entity 105-a may send a reference timestamp 330 to the non-ground network entity 105-b. Additionally or alternatively, the ground network entity 105-a may send the reference timestamp 330 according to a periodicity. For example, the ground network entity 105-a may periodically provide the reference timestamp 330 indicating the SFN=0 boundary of the ground network entity 105-a to the non-ground network entity 105-b via the gateway 305.

[0125] The non-terrestrial network entity 105-b may receive the reference timestamp 330 and may send the reference timestamp 330 (or an indication of the reference timestamp 330) to the UE 115-b. For example, the non-terrestrial network entity 105-b may indicate the reference timestamp 330 in a measurement gap configuration 335. The measurement gap configuration 335 may be an example of a control signal (e.g., a first signal) such as an RRC signal. The measurement gap configuration 335 may include a field indicating the reference timestamp 330. The field may include a value indicating a UTC timestamp, a portion of a UTC timestamp (e.g., some least significant bits of a UTC timestamp), a GNSS timestamp, a portion of a GNSS timestamp (e.g., some least significant bits of a GNSS timestamp), or some other indication of the absolute timing of the TN cell 310-a. In some cases, the non-terrestrial network entity may send the measurement gap configuration 335 including a field indicating the reference timestamp 330, while the terrestrial network entity may send the measurement gap configuration 335 without a field indicating the reference timestamp 330. Alternatively, the ground network entity may send a measurement gap configuration 335 having a field indicating a reference timestamp 330, which is set to a reference timestamp of a neighboring cell (e.g., a neighboring TN cell or a neighboring NTN cell for cell measurement), set to a default value, set to a random value, reused to indicate other information, or any combination thereof.

[0126] The UE 115-b that receives the measurement gap configuration 335 may use the reference timestamp 330 of the TN cell 310-a to determine a measurement gap window for measuring the TN cell 310-a. For example, the UE 115-b may determine the timing of the TN cell 310-a based on the reference timestamp 330, the measurement gap offset value indicated in the measurement gap configuration 335, or both. By using the parameters indicated in the measurement gap configuration 335, the UE 115-b may determine the periodicity of the measurement gap, the duration of the measurement gap, and the start time of the measurement gap, thereby allowing the UE 115-b to tune the RF module of the UE 115-b to the carrier frequency of the TN cell 310-a during the measurement gap (e.g., within at least a portion of the measurement gap). The UE 115-b may monitor the carrier frequency of the TN cell 310-a during the measurement gap to obtain the synchronization signal 360, thereby supporting NTN to TN mobility based on the reference timestamp 330.

[0127] If the UE 115-b detects the TN cell 310-a (e.g., based on receiving the synchronization signal 360 during the measurement gap), the UE 115-b may determine the timing of the TN cell 310-a based on the reference timestamp 330 received from the terrestrial network entity 105-a. For example, the UE 115-b may initially determine the timing of the TN cell 310-a based on the reference timestamp 330 received from the non-terrestrial network entity 105-b (e.g., in the measurement gap configuration 335). If the UE 115-b receives the synchronization signal 360 from the terrestrial network entity 105-a, the UE 115-b may receive a timestamp (e.g., a GNSS timestamp) indicated in the synchronization signal 360 or in another signal from the terrestrial network entity 105-a. UE 115-b (e.g., when camped on the network or otherwise connected to the network via NTN cell 310-b) may use the timestamp to determine the timing of TN cell 310-a (e.g., rather than using a measurement gap offset calculation based on measurement gap configuration 335).

[0128] In some examples, if UE 115-b detects a timing misalignment, UE 115-b may report to the non-terrestrial network entity 105-b. For example, UE 115-b may determine whether a measurement gap offset based on absolute timing (e.g., based on reference timestamp 330) for TN cell 310-a determined at UE 115-b crosses a downlink time slot boundary of NTN cell 310-b. UE 115-b may trigger sending a time slot level offset indication 355 (e.g., reporting a time slot level measurement gap offset determined at UE 115-b) to the non-terrestrial network entity 105-b (e.g., via an uplink MAC control element (CE) or another uplink control signal). In some cases, the non-terrestrial network entity 105-b may send an additional reference timestamp request 325 to the terrestrial network entity 105-a in response to the slot level offset indication 355, and the non-terrestrial network entity 105-b may send another measurement gap configuration 335 with an updated reference timestamp 330 to the UE 115-b based on the additional reference timestamp request 325.

[0129] UE 115-b and non-terrestrial network entity 105-b may communicate location information to support NTN to TN mobility. For example, UE 115-b may send UE location information 345 to non-terrestrial network entity 105-b. The UE location information 345 may be an example of coarse location information (e.g., indicating an area or region) or precise location information (e.g., indicating specific coordinates of UE 115-b). UE 115-b may include UE location information 345 in a control signal (e.g., uplink MAC-CE, uplink control information (UCI)) or a data signal. By using UE location information 345, non-terrestrial network entity 105-b may determine neighboring cells that are relatively close to UE 115-b. For example, based on UE location information 345 of UE 115-b, non-terrestrial network entity 105-b may determine that UE 115-b is entering or within the coverage area of ​​TN cell 310-a. The non-terrestrial network entity 105-b may send a control signal to the UE 115-b indicating a frequency layer (e.g., carrier frequency) of the TN cell 310-a, a reference location of the TN cell 310-a, or both (e.g., in the cell information 340). Additionally or alternatively, the non-terrestrial network entity 105-b may send a measurement gap configuration 335 with a reference timestamp 330 for the TN cell 310-a based on the UE location information 345.

[0130] In some cases, the non-terrestrial network entity 105-b may send cell information 340 for multiple cells to the UE 115-b. The cell information 340 may include an indication of a reference location of a neighboring cell (e.g., a TN cell 310-a), an indication of a distance threshold for the neighboring cell (e.g., the TN cell 310-a), or both. The reference location may be coarse-grained (e.g., indicating an area, such as a city center location close to the UE location) or fine-grained (e.g., indicating specific coordinates of the terrestrial network entity 105-a serving the TN cell 310-a). In some examples, the non-terrestrial network entity 105-b may provide cell information 340 for cells within a specific distance threshold from the UE 115-b (e.g., based on the UE location information 345). In some such examples, the non-terrestrial network entity 105-b may send a list of TN cell reference location and distance threshold pairs corresponding to the respective TN cells to the UE 115-b. UE 115-b may use cell information 340 to trigger cell measurement for a neighboring cell (e.g., a TN cell). For example, if the distance from the UE to the TN cell reference location is less than a distance threshold for a particular TN cell 310-a, UE 115-b may initiate a cell measurement procedure for TN cell 310-a and, in some cases, initiate a cell measurement report to the network. Alternatively, UE 115-b may use a default distance threshold for triggering cell measurement instead of a cell-specific distance threshold.

[0131] Additionally or alternatively, the UE 115-b, the non-terrestrial network entity 105-b, or both may use frequency prioritization to prioritize TN cell connections. In some examples, the UE 115-b may support different priority values ​​for different frequency layers (e.g., carrier frequencies, frequency ranges). In some cases, the non-terrestrial network entity 105-b may indicate a frequency priority value 350 of a target frequency layer (e.g., a carrier frequency of a neighboring TN cell 310-a) to the UE 115-b. The non-terrestrial network entity 105-b may indicate the frequency priority value 350 in a measurement object configuration for connection mode inter-frequency mobility, inter-RAT mobility, or both. For example, the non-terrestrial network entity 105-b may configure a relatively higher priority for a TN frequency layer (e.g., a carrier frequency of a TN cell) than for an NTN frequency layer (e.g., a carrier frequency of an NTN cell), or configure at least equal priorities for the TN and NTN frequency layers. In some examples, the non-terrestrial network entity 105-b may include an integer value (e.g., between 0 and 7) in the cell selection or reselection configuration that indicates a particular priority of the carrier frequency (e.g., where 0 may indicate the lowest priority and 7 may indicate the highest priority). Additionally or alternatively, the non-terrestrial network entity 105-b may include an indication of a decimal value to be added to the integer value to calculate the priority level of the carrier frequency. The non-terrestrial network entity 105-b may indicate a frequency priority value 350 for connected mode mobility at the UE 115-b, idle mode mobility at the UE 115-b, or both.

[0132] Alternatively, the UE 115-b may determine the frequency priority value 350 for the carrier frequency based on the corresponding cell type (e.g., TN cell). For example, if the non-terrestrial network entity 105-b does not indicate that the TN frequency layer has a relatively higher priority than the NTN frequency layer, then in the case where the UE 115-b identifies the cell type of the TN frequency layer, the NTN frequency layer, or both, the UE 115-b may override the priority setting for the TN frequency layer, the NTN frequency layer, or both. The UE 115-b may determine the cell type for the frequency layer (e.g., carrier frequency or frequency range) based on other information (such as the band number of the frequency layer, operator information in a subscriber identity module (SIM), or other auxiliary information). For example, the UE 115-b may determine that the first frequency layer corresponds to the TN cell 310-a, and may assign a frequency priority value 350 to the first frequency layer that is greater than the frequency priority value 350 of the second frequency layer corresponding to the NTN cell.

[0133] The UE 115-b may perform a cell measurement procedure based on the frequency priority value 350 of the carrier frequency of the neighboring cell. For example, the UE 115-b may trigger cell measurement and reporting of cell measurement information for a neighboring cell corresponding to a relatively large frequency priority value 350, and the UE 115-b may avoid performing cell measurement and reporting of cell measurement information for a neighboring cell corresponding to a relatively low frequency priority value 350. If the UE 115-b fails to detect a neighboring cell having an equal or relatively large frequency priority value 350, or if the quality of the neighboring cell having an equal or relatively large frequency priority value 350 fails to meet a quality threshold, the UE 115-b may trigger cell measurement and cell measurement reporting for a relatively low priority cell (e.g., corresponding to a frequency layer to which a relatively low frequency priority value 350 is assigned). By assigning a relatively greater frequency priority value 350 to the TN cell 310-a than to the NTN cell 310-b (e.g., based on a determination at the UE 115-b or based on signaling from the non-terrestrial network entity 105-b), the UE 115-b may effectively prioritize performing cell measurements on the TN cell relative to the NTN cell, such that if a TN cell 310-a that meets a quality threshold is available (e.g., regardless of the availability of the NTN cell 310-b), the UE 115-b performs NTN to TN mobility. In some cases, if the UE 115-b does not detect any neighboring TN cells, the UE 115-b may explicitly indicate this to the non-terrestrial network entity 105-b in a measurement report.

[0134] Figure 4 An example of a wireless communication system 400 supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is illustrated. The wireless communication system 400 may be as described in reference Figure 1 and Figure 3 Examples of wireless communication system 100 or wireless communication system 300 described herein. In some examples, wireless communication system 300 may include a wireless communication system 100 or wireless communication system 300 as described herein. Figure 2 The wireless communication system 400 may include: a UE 115-c, which may be as described in reference Figures 1 to 3 The example of UE 115 described; and network entity 105-c and network entity 105-d, which may be as described in reference Figures 1 to 3 4. In some cases, network entity 105-c may be an example of a terrestrial network entity 105-c, such as base station 140-b, and network entity 105-d may be an example of a non-terrestrial network entity 105-d, such as satellite 185-b. Network entity 105-c and network entity 105-d may communicate via gateway 405. Wireless communication system 400 may use, for example, a system similar to that described in reference Figure 3 The frequency priority value 440 is described to support TN to NTN mobility of the UE 115-c.

[0135] The ground network entity 105-c may provide network coverage for a first cell 410-a (e.g., a TN cell 410-a). The non-ground network entity 105-d may provide network coverage for a second cell 410-b (e.g., an NTN cell 410-b). In some cases, the UE 115-c may be connected to the network via the ground network entity 105-c, which may include a base station 140-b or may be an example of the base station. For example, the UE 115-c may be located within the coverage area of ​​the first cell 410-a and may camp on the first cell 410-a (e.g., connected to the network via the first cell 410-a). The UE 115-c may communicate with the ground network entity 105-c via a downlink channel 415-a, an uplink channel 420, or both. The UE 115-c may move to a location that supports NTN coverage (e.g., a location of the UE 115-c in NTN and TN coverage). However, switching from TN cell 410-a to NTN cell 410-b may reduce signaling reliability for UE 115-c. To improve signaling reliability and latency, UE 115-c may prioritize remaining connected to the network via TN cell 410-a.

[0136] The UE 115-c, the ground network entity 105-c, or both may use frequency prioritization to prioritize TN cell connections. In some cases, the ground network entity 105-c may indicate a frequency priority value 440 of a target frequency layer (e.g., a carrier frequency of a neighboring NTN cell 410-b) to the UE 115-c. The ground network entity 105-c may indicate the frequency priority value 440 in a measurement object configuration (e.g., a measurement gap configuration 425 or other message) for connected mode inter-frequency mobility, inter-RAT mobility, or both. For example, the ground network entity 105-c may configure a relatively lower priority for the NTN frequency layer (e.g., a carrier frequency of the NTN cell) than the TN frequency layer (e.g., a carrier frequency of the TN cell), or configure at least equal priority for the NTN and TN frequency layers. The ground network entity 105-c may indicate a frequency priority value 440 for connected mode mobility at the UE 115-c, idle mode mobility at the UE 115-c, or both.

[0137] Alternatively, the UE 115-c may determine the frequency priority value 440 of the carrier frequency based on the corresponding cell type (e.g., NTN cell). For example, if the ground network entity 105-c does not indicate that the NTN frequency layer has a relatively lower priority than the TN frequency layer, then in the case where the UE 115-c identifies the cell type of the NTN frequency layer, the TN frequency layer, or both, the UE 115-c may override the priority setting for the NTN frequency layer, the TN frequency layer, or both. The UE 115-c may determine the cell type (e.g., carrier frequency or frequency range) of the frequency layer based on other information (such as the frequency band number of the frequency layer, operator information in the SIM, or other auxiliary information). For example, the UE 115-c may determine that the first frequency layer corresponds to the NTN cell 410-b, and may assign a frequency priority value 440 to the first frequency layer, which is less than the frequency priority value 440 of the second frequency layer corresponding to the TN cell (e.g., TN cell 410-a).

[0138] By using the frequency priority value 440, the UE 115-c may avoid performing cell measurement procedures on the neighboring NTN cell 410-b. For example, the UE 115-c may avoid tuning to the carrier frequency of the NTN cell 410-b during the measurement gap. Therefore, the UE 115-c may avoid monitoring the synchronization signal 445 (e.g., SSB transmitted on the downlink channel 415-b or the broadcast channel) from the non-terrestrial network entity 105-d during the measurement gap, and may avoid including cell measurements about the NTN cell 410-b in the measurement report 430. In contrast, the UE 115-c may perform one or more cell measurement procedures on one or more TN cells (e.g., such as the serving cell 410-a or a neighboring TN cell) corresponding to the relatively larger frequency priority value 440. Because the measurement report 430 includes cell measurements about the TN cell instead of the NTN cell, if there is an available TN cell that meets the quality threshold, the UE 115-c may remain connected to the network via the TN cell. By using the priority value 440, if the UE 115-c is in both NTN and TN coverage, the UE 115-c may establish or maintain a connection with the TN cell 410-a instead of the NTN cell 410-b.

[0139] Figure 5 An example of a process flow 500 for supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is illustrated. The process flow 500 may be described in reference to Figure 1 , Figure 3 and Figure 4 The process flow 500 may include a UE 115-d, which may be implemented in the wireless communication system 100, the wireless communication system 300, or the wireless communication system 400 described above. Figures 1 to 4The example of UE 115 described herein may include a first network entity 105-e and a second network entity 105-f, which may be as described in reference Figures 1 to 4 An example of a network entity 105 is described. Process flow 500 may support NTN-TN mobility of UE 115-d. In the following description of process flow 500, operations performed by the device may be performed in a different order or at a different time. Additionally or alternatively, some operations may also be omitted from process flow 500 and other operations may be added to process flow 500.

[0140] The first network entity 105-e may be associated with a first cell type and may operate via a first carrier frequency, and the second network entity 105-f may be associated with a second cell type (e.g., different from the first cell type) and may operate via a second carrier frequency (e.g., different from the first carrier frequency). For example, the first cell type may be an NTN cell type (e.g., the first network entity 105-e may be a non-terrestrial network entity 105-e), and the second cell type may be a TN cell type (e.g., the second network entity 105-f may be a terrestrial network entity 105-f).

[0141] At 505, in some examples, UE 115-d may send a signal indicating location information of UE 115-d to first network entity 105-e. The signal indicating the UE location information may be an example of a control signal, such as an RRC signal, a MAC-CE, a UCI, or any combination thereof. The first network entity 105-e may obtain the signal indicating location information (e.g., first location information) of UE 115-d.

[0142] At 510, in some examples, the first network entity 105-e may output a signal indicating cell information for a set of cells. For example, the first network entity 105-e may output a signal indicating location information and a distance threshold for a set of cells associated with a second cell type (e.g., TN cells). The signal may indicate at least the location and the distance threshold of the second network entity 105-f. The UE 115-d may receive the signal indicating the cell information and may use the cell information to initiate a cell measurement procedure. For example, the UE 115-d may receive an indication of the location and the distance threshold of the second network entity 105-f, and may initiate monitoring for signaling (e.g., synchronization signaling) from the second network entity 105-f if the UE 115-d is within the distance threshold of the location of the second network entity 105-f.

[0143] At 515, in some examples, the first network entity 105-e may output a signal indicating a priority value (e.g., a frequency priority value) of a frequency layer of the second network entity 105-f. For example, a first cell type (e.g., an NTN cell) and a corresponding first carrier frequency may correspond to a first priority value, and the signal may indicate a second priority value of a second carrier frequency associated with the second network entity 105-f based on a second carrier frequency corresponding to a second cell type (e.g., a TN cell). For example, the second priority value may be greater than the first priority value so that TN cell measurements are prioritized over NTN cell measurements. In some examples, the signal indicating the priority value may be a signal including an indication of a reference timestamp of a measurement gap (e.g., a measurement gap configuration message). The UE 115-d may receive the signal indicating the priority value of the frequency layer of the second network entity 105-f, and may monitor signaling (e.g., synchronization signaling) from the second network entity 105-f based on the priority value of the frequency layer of the second network entity 105-f. In some examples, UE 115-d may operate according to connected mode mobility, and the second priority value for the second carrier frequency may correspond to a configuration for connected mode mobility.

[0144] Alternatively, if the first network entity 105-e does not configure the priority value, the UE 115-d may determine the priority value of the frequency layer of the second network entity 105-f, or the UE 115-d may override the configuration of the priority value by the first network entity 105-e. For example, the UE 115-d may monitor the second carrier frequency based on a second priority value of the second carrier frequency, wherein the second priority value is based on the second carrier frequency corresponding to the second cell type (e.g., TN cell), and the second priority value is greater than the first priority value corresponding to the first cell type (e.g., NTN cell).

[0145] At 520, the first network entity 105-e may output a signal including a request for a reference timestamp corresponding to the second network entity 105-f. For example, the reference timestamp request may be sent via a gateway between the first network entity 105-e and the second network entity 105-f. The first network entity 105-e may request the reference timestamp based on the first network entity 105-e being a non-terrestrial network entity and the second network entity 105-f being a terrestrial network entity. The second network entity 105-f may obtain the signal including the request for a reference timestamp corresponding to the second network entity 105-f.

[0146] At 525, the second network entity 105-f may output a signal indicating a reference timestamp corresponding to the second network entity 105-f based on the request. The reference timestamp may be an example of a UTC timestamp, a portion of a UTC timestamp, a GNSS timestamp, a portion of a GNSS timestamp, or a combination thereof. In some examples, the reference timestamp may indicate a SFN having a value of 0 for the second network entity 105-f. The first network entity 105-e may obtain a signal indicating a reference timestamp corresponding to the second network entity 105-f based on the request. Additionally or alternatively, the second network entity 105-f may output an additional signal according to a periodicity, the additional signal indicating an additional reference timestamp corresponding to the second network entity 105-f. For example, the second network entity 105-f may repeatedly send an indication of the reference timestamp to the first network entity 105-e according to a periodicity.

[0147] At 530, the first network entity 105-e may output a signal including an indication of a reference timestamp corresponding to the second network entity 105-f, the signal configuring a measurement gap for the UE 115-d. In some cases, the signal may include a measurement gap configuration for the UE 115-d, the measurement gap supporting a cell measurement procedure associated with the second network entity 105-f. In some cases, the first network entity 105-e may output a signal indicating a reference timestamp based on location information of the UE (e.g., the first location information) and location information of the second network entity 105-f (e.g., the second location information). The UE 115-d may receive the signal including an indication of a reference timestamp of the measurement gap, the reference timestamp corresponding to the second network entity 105-f.

[0148] At 535, UE 115-d may perform a cell measurement procedure. In some examples, UE 115-d may trigger a cell measurement procedure for second network entity 105-f based on the proximity of the UE to second network entity 105-f (e.g., when UE 115-d is within a threshold distance from the location of second network entity 105-f). In some examples, UE 115-d may perform a cell measurement procedure for second network entity 105-f based on a priority value corresponding to a second carrier frequency of second network entity 105-f (e.g., a TN cell) being relatively greater than a priority value corresponding to a first carrier frequency of first network entity 105-e (e.g., an NTN cell).

[0149] The cell measurement procedure may involve, at 540, the UE 115-d monitoring the second carrier frequency during a measurement gap to obtain a signal (e.g., a synchronization signal) from the second network entity, the measurement gap being based on a reference timestamp. For example, the UE 115-d may determine the timing of the second network entity 105-f and the timing of the measurement gap accordingly using a reference timestamp indicating an absolute timing of the second network entity 105-f. At 545, the second network entity 105-f may output a signal during the measurement gap, wherein the measurement gap is based on the reference timestamp (e.g., absolute timing) of the second network entity 105-f. The signal may be an example of a synchronization signal, such as an SSB including a second timestamp corresponding to the second network entity 105-f. In some examples, the UE 115-d may receive the signal (e.g., a synchronization signal) based on the monitoring. If the UE 115-d receives the synchronization signal, the UE 115-d may determine whether the synchronization signal satisfies a threshold (e.g., a signal strength threshold, a signal quality threshold) for the UE 115-d to switch to the second network entity 105-f. For example, at 550 UE 115 - d may switch a connection from the first network entity 105 - e to the second network entity 105 - f based on one or more measurements of the synchronization signal.

[0150] At 555, in some examples, the second network entity 105-f may output a signal indicating a first priority value (e.g., frequency priority value) of a frequency layer of a network entity (such as the first network entity 105-e) corresponding to a first cell type (e.g., NTN cell). The first priority value may be less than a second priority value corresponding to a second cell type (e.g., TN cell). The UE 115-d may receive the signal indicating the priority value of the frequency layer of the first network entity 105-e, and may avoid monitoring signaling (e.g., synchronization signaling) from the first network entity 105-e based on the priority value of the frequency layer of the first network entity 105-e. Alternatively, if the second network entity 105-f is not configured with a priority value, the UE 115-d may determine the priority value of the frequency layer of the first network entity 105-e, or the UE 115-d may override the configuration of the priority value by the second network entity 105-f. For example, UE 115-d may avoid monitoring the first carrier frequency based on a first priority value for the first carrier frequency, the first priority value being based on the first carrier frequency corresponding to a first cell type (e.g., an NTN cell), the first priority value being less than a second priority value corresponding to a second cell type (e.g., a TN cell).

[0151] Figure 6A block diagram 600 of a device 605 supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0152] The receiver 610 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to UE mobility between NTN and TN), user data, control information, or any combination thereof. The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

[0153] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to UE mobility between NTN and TN), user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0154] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of UE mobility between the NTN and the TN as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0155] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). 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 as or otherwise supports means 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).

[0156] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, 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 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means 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.

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

[0158] According to examples as disclosed herein, the communication manager 620 may support wireless communication at a UE. For example, the communication manager 620 may be configured to or otherwise support a component for receiving a first signal from a first network entity associated with a first cell type and operating via a first carrier frequency, the first signal including an indication of a reference timestamp of a measurement gap, the reference timestamp corresponding to a second network entity associated with a second cell type and operating via a second carrier frequency. The communication manager 620 may be configured to or otherwise support a component for monitoring the second carrier frequency as part of a cell measurement procedure and during the measurement gap to obtain a second signal from the second network entity, the measurement gap being based on the reference timestamp.

[0159] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof or otherwise coupled thereto) can support techniques for improving the reliability of timing alignment and cell measurements. By aligning the measurement gap with the synchronization signaling from the TN cell using a reference timestamp, the device 605 can improve the reliability of detecting the synchronization signaling. Improving the detection of the synchronization signaling can reduce the amount of time that the device 605 monitors the synchronization signaling, thereby effectively reducing the processing overhead at the device 605. Additionally or alternatively, prioritizing the TN connection over the NTN connection can improve the signaling reliability, thereby effectively reducing the processing overhead involved in retransmitting the signal.

[0160] Figure 7A block diagram 700 of a device 705 supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0161] The receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to UE mobility between NTN and TN), user data, control information, or any combination thereof. The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a set of multiple antennas.

[0162] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to UE mobility between NTN and TN), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.

[0163] The device 705 or its various components may be examples of components for performing various aspects of UE mobility between NTN and TN as described herein. For example, the communication manager 720 may include a measurement gap configuration component 725, a cell measurement component 730, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to use or otherwise cooperate with the receiver 710, the transmitter 715, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0164] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. The measurement gap configuration component 725 may be configured to or otherwise support a means for receiving a first signal from a first network entity associated with a first cell type and operating via a first carrier frequency, the first signal including an indication of a reference timestamp of a measurement gap, the reference timestamp corresponding to a second network entity associated with a second cell type and operating via a second carrier frequency. The cell measurement component 730 may be configured to or otherwise support a means for monitoring the second carrier frequency as part of a cell measurement procedure and during the measurement gap to obtain a second signal from the second network entity, the measurement gap being based on the reference timestamp.

[0165] Figure 8 A block diagram 800 of a communication manager 820 supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of UE mobility between an NTN and a TN as described herein. For example, the communication manager 820 may include a measurement gap configuration component 825, a cell measurement component 830, a handover component 835, a frequency priority management component 840, an SSB component 845, a UE location component 850, an offset reporting component 855, a cell information component 860, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0166] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. The measurement gap configuration component 825 may be configured to or otherwise support a means for receiving a first signal from a first network entity associated with a first cell type and operating via a first carrier frequency, the first signal including an indication of a reference timestamp of a measurement gap, the reference timestamp corresponding to a second network entity associated with a second cell type and operating via a second carrier frequency. The cell measurement component 830 may be configured to or otherwise support a means for monitoring the second carrier frequency as part of a cell measurement procedure and during the measurement gap to obtain a second signal from the second network entity, the measurement gap being based on the reference timestamp.

[0167] In some examples, cell measurement component 830 may be configured or otherwise support a component for receiving the second signal from the second network entity based on the monitoring. In some examples, handover component 835 may be configured or otherwise support a component for switching a connection from the first network entity to the second network entity based on one or more measurements of the second signal.

[0168] In some examples, the frequency priority management component 840 may be configured to or otherwise support a means for receiving a third signal from the second network entity, the third signal including a first priority value for the first carrier frequency corresponding to the first cell type, the first priority value being less than a second priority value corresponding to the second cell type. In some examples, the frequency priority management component 840 may be configured to or otherwise support a means for avoiding monitoring the first carrier frequency based on the first priority value.

[0169] In some examples, the frequency priority management component 840 may be configured to or otherwise support components for avoiding monitoring the first carrier frequency based on a first priority value for the first carrier frequency, the first priority value being based on the first carrier frequency corresponding to the first cell type, the first priority value being less than a second priority value corresponding to the second cell type.

[0170] In some examples, the first cell type corresponds to a first priority value, and the frequency priority management component 840 may be configured to or otherwise support a component for receiving a third signal from the first network entity, the third signal including a second priority value for the second carrier frequency, the second priority value being based on the second carrier frequency corresponding to the second cell type, the second priority value being greater than the first priority value corresponding to the first cell type, and monitoring of the second carrier frequency being based on the second priority value.

[0171] In some examples, frequency priority management component 840 can be configured as or otherwise support means for operating in accordance with connected mode mobility, the second priority value for the second carrier frequency corresponding to a configuration for the connected mode mobility.

[0172] In some examples, the frequency priority management component 840 may be configured to or otherwise support components for monitoring the second carrier frequency based on a second priority value for the second carrier frequency, the second priority value being based on the second carrier frequency corresponding to the second cell type, the second priority value being greater than the first priority value corresponding to the first cell type.

[0173] In some examples, SSB component 845 can be configured or otherwise support means for receiving an SSB from the second network entity, the SSB including a second timestamp corresponding to the second network entity. In some examples, cell measurement component 830 can be configured or otherwise support means for monitoring a third signal from the second network entity during the measurement gap based on the second timestamp as part of a second cell measurement procedure.

[0174] In some examples, the UE location component 850 may be configured as or otherwise support a component for sending a third signal indicating location information of the UE to the first network entity, including the first signal indicating the reference timestamp corresponding to the second network entity based on the location information of the UE.

[0175] In some examples, the indication of the reference timestamp includes a UTC timestamp, a portion of the UTC timestamp, a GNSS timestamp, a portion of the GNSS timestamp, or a combination thereof. In some examples, the reference timestamp indicates a SFN having a value of 0 for the second network entity.

[0176] In some examples, the first signal also indicates an offset in the time domain for the measurement gap, a periodicity of the measurement gap, a duration of the measurement gap, or a combination thereof, and the monitoring is also based on the offset, the periodicity, the duration, or a combination thereof.

[0177] In some examples, the offset reporting component 855 may be configured to or otherwise support a component for sending a third signal to the first network entity indicating a slot level offset for the measurement gap based on the measurement gap, the measurement gap being based on the reference timestamp corresponding to a downlink timestamp boundary of the second network entity across the first network entity.

[0178] In some examples, the cell information component 860 may be configured or otherwise support a component for receiving a third signal from the first network entity, the third signal indicating location information and a distance threshold of a set of multiple cells associated with the second cell type, the third signal indicating at least the corresponding location and the corresponding distance threshold of the second network entity. In some examples, the cell measurement component 830 may be configured or otherwise support a component for monitoring the second signal from the second network entity based on the UE being within the corresponding distance threshold of the corresponding location of the second network entity. In some examples, the first cell type includes an NTN cell type. In some examples, the second cell type includes a TN cell type.

[0179] Fig. 9A diagram of a system 900 including a device 905 supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein or include components of these devices. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0180] I / O controller 910 can manage input and output signals of device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize an operating system such as iOS. ® ANDROID ® , MS-DOS ® 、MS-WINDOWS ® , OS / 2 ® ,UNIX ® 、LINUX ® or another known operating system. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor such as processor 940. In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0181] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be able to send or receive multiple wireless transmissions concurrently. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired link, or a wireless link as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 925 for transmission, and demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 may be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or components thereof as described herein.

[0182] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 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 935 may not be directly executable by the processor 940, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, among other things, the memory 930 may include a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0183] The processor 940 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 940 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 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) so that the device 905 performs various functions (e.g., functions or tasks that support UE mobility between an NTN and a TN). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform various functions described herein.

[0184] According to examples as disclosed herein, the communication manager 920 may support wireless communication at a UE. For example, the communication manager 920 may be configured to or otherwise support a component for receiving a first signal from a first network entity associated with a first cell type and operating via a first carrier frequency, the first signal including an indication of a reference timestamp of a measurement gap, the reference timestamp corresponding to a second network entity associated with a second cell type and operating via a second carrier frequency. The communication manager 920 may be configured to or otherwise support a component for monitoring the second carrier frequency as part of a cell measurement procedure and during the measurement gap to obtain a second signal from the second network entity, the measurement gap being based on the reference timestamp.

[0185] By including or configuring a communications manager 920 according to examples as described herein, the device 905 may support techniques for improving communications reliability, reducing latency, improving coordination of timing information for cell measurement procedures (eg, for NTN to TN mobility), or any combination thereof.

[0186] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with the transceiver 915, one or more antennas 925, or any combination thereof to perform various operations (e.g., receive, monitor, transmit). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that are executable by the processor 940 to cause the device 905 to perform various aspects of UE mobility between the NTN and the TN as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0187] Fig.10 A block diagram 1000 of a device 1005 supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of a network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0188] The receiver 1010 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 communicated to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0189] The transmitter 1015 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 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 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 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 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0190] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may be examples of means for performing various aspects of UE mobility between an NTN and a TN as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0191] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). 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 means 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).

[0192] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, 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 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functionality 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.

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

[0194] The communication manager 1020 may support wireless communication at a first network entity according to examples as disclosed herein. For example, the communication manager 1020 may be configured to or otherwise support a component for outputting a first signal, the first signal including a request for a reference timestamp corresponding to a second network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. The communication manager 1020 may be configured to or otherwise support a component for obtaining a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. The communication manager 1020 may be configured to or otherwise support a component for outputting a third signal, the third signal including an indication of the reference timestamp corresponding to the second network entity, the third signal configuring a measurement gap for the UE.

[0195] Additionally or alternatively, according to examples disclosed herein, the communication manager 1020 may support wireless communication at a second network entity. For example, the communication manager 1020 may be configured to or otherwise support a component for obtaining a first signal, the first signal including a request for a reference timestamp corresponding to the second network entity, the second network entity being associated with a second cell type, the request being associated with the first network entity, and the first network entity being associated with the first cell type and operating via a first carrier frequency, the second network entity operating via a second carrier frequency. The communication manager 1020 may be configured to or otherwise support a component for outputting a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. The communication manager 1020 may be configured to or otherwise support a component for outputting a third signal during a measurement gap, the measurement gap being based on the reference timestamp.

[0196] By including or configuring the communication manager 1020 according to examples as described herein, the device 1005 (e.g., a processor controlling the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof or otherwise coupled thereto) may support techniques for improving timing alignment between measurement gaps at the UE 115 and synchronization signaling of a terrestrial network entity. As a result, the UE 115 may more reliably detect and measure synchronization signaling, thereby effectively reducing processing overhead associated with performing synchronization signaling.

[0197] Fig.11A block diagram 1100 of a device 1105 supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0198] The receiver 1110 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 communicated to other components of the device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

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

[0200] The device 1105 or its various components may be examples of components for performing various aspects of UE mobility between NTN and TN as described herein. For example, the communication manager 1120 may include a reference timestamp request component 1125, a reference timestamp indication component 1130, a measurement gap configuration component 1135, a synchronization signaling component 1140, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to use or otherwise cooperate with the receiver 1110, the transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0201] The communication manager 1120 may support wireless communication at a first network entity according to examples as disclosed herein. The reference timestamp request component 1125 may be configured to or otherwise support means for outputting a first signal, the first signal including a request for a reference timestamp corresponding to a second network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. The reference timestamp indication component 1130 may be configured to or otherwise support means for obtaining a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. The measurement gap configuration component 1135 may be configured to or otherwise support means for outputting a third signal, the third signal including an indication of the reference timestamp corresponding to the second network entity, the third signal configuring a measurement gap for the UE.

[0202] Additionally or alternatively, according to examples disclosed herein, the communication manager 1120 may support wireless communications at a second network entity. The reference timestamp request component 1125 may be configured to or otherwise support a component for obtaining a first signal, the first signal including a request for a reference timestamp corresponding to the second network entity, the second network entity being associated with a second cell type, the request being associated with the first network entity, and the first network entity being associated with the first cell type and operating via a first carrier frequency, the second network entity operating via a second carrier frequency. The reference timestamp indication component 1130 may be configured to or otherwise support a component for outputting a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. The synchronization signaling component 1140 may be configured to or otherwise support a component for outputting a third signal during a measurement gap, the measurement gap being based on the reference timestamp.

[0203] Fig.12 A block diagram 1200 of a communication manager 1220 supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of means for performing various aspects of UE mobility between an NTN and a TN as described herein. For example, the communication manager 1220 may include a reference timestamp request component 1225, a reference timestamp indication component 1230, a measurement gap configuration component 1235, a synchronization signaling component 1240, a UE location component 1245, a cell information component 1250, a frequency priority management component 1255, a connection component 1260, 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 the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0204] The communication manager 1220 may support wireless communication at a first network entity according to examples as disclosed herein. The reference timestamp request component 1225 may be configured to or otherwise support means for outputting a first signal, the first signal including a request for a reference timestamp corresponding to a second network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. The reference timestamp indication component 1230 may be configured to or otherwise support means for obtaining a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. The measurement gap configuration component 1235 may be configured to or otherwise support means for outputting a third signal, the third signal including an indication of the reference timestamp corresponding to the second network entity, the third signal configuring a measurement gap for the UE.

[0205] In some examples, the UE location component 1245 may be configured as or otherwise support a component for obtaining a fourth signal indicating first location information of the UE, the third signal being output based on the first location information of the UE and the second location information of the second network entity.

[0206] In some examples, the cell information component 1250 may be configured as or otherwise support a component for outputting a fourth signal indicating location information and a distance threshold for a group of multiple cells associated with the second cell type, the fourth signal indicating at least the location and distance threshold of the second network entity.

[0207] In some examples, reference timestamp indicating component 1230 may be configured to or otherwise support means for obtaining an additional signal according to a periodicity, the additional signal indicating an additional reference timestamp corresponding to the second network entity.

[0208] In some examples, the first cell type corresponds to a first priority value, and the frequency priority management component 1255 may be configured to or otherwise support a component for outputting a fourth signal based on the second carrier frequency corresponding to the second cell type, the fourth signal including a second priority value for the second carrier frequency associated with the second network entity, the second priority value being greater than the first priority value corresponding to the first cell type.

[0209] In some examples, the indication of the reference timestamp includes a UTC timestamp, a portion of the UTC timestamp, a GNSS timestamp, a portion of the GNSS timestamp, or a combination thereof. In some examples, the reference timestamp indicates a SFN having a value of 0 for the second network entity. In some examples, the first cell type includes an NTN cell type. In some examples, the second cell type includes a TN cell type.

[0210] Additionally or alternatively, according to examples disclosed herein, the communication manager 1220 may support wireless communication at a second network entity. In some examples, the reference timestamp request component 1225 may be configured to or otherwise support a component for obtaining a first signal, the first signal including a request for a reference timestamp corresponding to the second network entity, the second network entity being associated with a second cell type, the request being associated with the first network entity, and the first network entity being associated with the first cell type and operating via a first carrier frequency, the second network entity operating via a second carrier frequency. In some examples, the reference timestamp indication component 1230 may be configured to or otherwise support a component for outputting a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. The synchronization signaling component 1240 may be configured to or otherwise support a component for outputting a third signal during a measurement gap, the measurement gap being based on the reference timestamp.

[0211] In some examples, connection component 1260 may be configured to or otherwise support means for establishing a connection with the UE based on the third signal.

[0212] In some examples, synchronization signaling component 1240 may be configured or otherwise support components for outputting an SSB that includes a second timestamp corresponding to the second network entity.

[0213] In some examples, reference timestamp indicating component 1230 may be configured to or otherwise support means for outputting an additional signal according to a periodicity, the additional signal indicating an additional reference timestamp corresponding to the second network entity.

[0214] In some examples, the frequency priority management component 1255 may be configured to or otherwise support means for outputting a fourth signal, the fourth signal comprising a first priority value corresponding to the first cell type for the first carrier frequency, the first priority value being less than a second priority value corresponding to the second cell type. In some examples, the first cell type comprises an NTN cell type. In some examples, the second cell type comprises a TN cell type.

[0215] Fig.13A diagram of a system 1300 including a device 1305 supporting UE mobility between an NTN and a TN according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein, or include components of these devices. The device 1305 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 1305 may include components that support output and acquisition of communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0216] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1310 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and for demodulating a signal. Where applicable, transceiver 1310 or transceiver 1310 and one or more antennas 1315 or wired interfaces may be examples of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

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

[0218] The processor 1335 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, a discrete hardware component, or any combination thereof). In some cases, the processor 1335 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 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1325) so that the device 1305 performs various functions (e.g., functions or tasks that support UE mobility between NTN and TN). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform various functions described herein. Processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functionality (e.g., by executing code 1330 ) to perform the functions of device 1305 .

[0219] In some examples, bus 1340 may support communications of a protocol layer of a protocol stack (e.g., within the protocol layer). In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1305 or between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system where one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

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

[0221] The communication manager 1320 may support wireless communication at a first network entity according to examples as disclosed herein. For example, the communication manager 1320 may be configured to or otherwise support a component for outputting a first signal, the first signal including a request for a reference timestamp corresponding to a second network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. The communication manager 1320 may be configured to or otherwise support a component for obtaining a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. The communication manager 1320 may be configured to or otherwise support a component for outputting a third signal, the third signal including an indication of the reference timestamp corresponding to the second network entity, the third signal configuring a measurement gap for the UE.

[0222] Additionally or alternatively, according to examples disclosed herein, the communication manager 1320 may support wireless communications at a second network entity. For example, the communication manager 1320 may be configured to or otherwise support a component for obtaining a first signal, the first signal including a request for a reference timestamp corresponding to the second network entity, the second network entity being associated with a second cell type, the request being associated with the first network entity, and the first network entity being associated with the first cell type and operating via a first carrier frequency, the second network entity operating via a second carrier frequency. The communication manager 1320 may be configured to or otherwise support a component for outputting a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. The communication manager 1320 may be configured to or otherwise support a component for outputting a third signal during a measurement gap, the measurement gap being based on the reference timestamp.

[0223] By including or configuring a communications manager 1320 according to examples as described herein, the device 1305 may support techniques for improving communications reliability, reducing latency, improving timing coordination between devices for TN cell measurements, or any combination thereof.

[0224] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1335, the memory 1325, the code 1330, the transceiver 1310, or any combination thereof. For example, the code 1330 may include instructions that are executable by the processor 1335 to cause the device 1305 to perform various aspects of UE mobility between the NTN and the TN as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0225] Fig.14 A flowchart illustrating a method 1400 for supporting UE mobility between an NTN and a TN 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 9 The described UE 115 may be performed. 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.

[0226] At 1405, the method may include: receiving a first signal from a first network entity associated with a first cell type and operating via a first carrier frequency, the first signal including an indication of a reference timestamp of a measurement gap corresponding to a second network entity associated with a second cell type and operating via a second carrier frequency. 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 a second network entity as disclosed herein. Figure 8 The described measurement gap configuration component 825 is performed.

[0227] At 1410, the method may include: as part of a cell measurement procedure and during the measurement gap, monitoring the second carrier frequency to obtain a second signal from the second network entity, the measurement gap being based on the reference timestamp. 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 8 The cell measurement component 830 described above is performed.

[0228] Fig.15 A flowchart illustrating a method 1500 for supporting UE mobility between an NTN and a TN 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 in reference to Figures 1 to 5 as well as Figures 10 to 13 The network entity described herein may be executed by the network entity described herein. 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.

[0229] At 1505, the method may include: outputting a first signal including a request for a reference timestamp corresponding to a second network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency. 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 by Fig.12 The described reference timestamp request component 1225 is executed.

[0230] At 1510, the method may include: obtaining a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. The operations of 1510 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1510 may be performed by reference to Fig.12 The reference timestamps described indicate component 1230 to execute.

[0231] At 1515, the method may include: outputting a third signal, the third signal including an indication of the reference timestamp corresponding to the second network entity, the third signal configuring the measurement gap for the UE. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by Fig.12 The described measurement gap configuration component 1235 is performed.

[0232] Fig.16 A flowchart illustrating a method 1600 for supporting UE mobility between an NTN and a TN 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 5 as well as Figures 10 to 13The network entity described herein may be executed by the network entity described herein. 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.

[0233] At 1605, the method may include obtaining a first signal, the first signal including a request for a reference timestamp corresponding to a second network entity, the second network entity being associated with a second cell type, the request being associated with a first network entity, and the first network entity being associated with the first cell type and operating via a first carrier frequency, the second network entity operating via a second carrier frequency. 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 by Fig.12 The described reference timestamp request component 1225 is executed.

[0234] At 1610, the method may include: outputting a second signal based on the request, the second signal indicating the reference timestamp corresponding to the second network entity. The operations of 1610 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed by reference to Fig.12 The reference timestamps described indicate component 1230 to execute.

[0235] At 1615, the method may include: outputting a third signal during a measurement gap, the measurement gap being based on the reference timestamp. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed by reference to Fig.12 The described synchronization signaling component 1240 is performed.

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

[0237] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a first signal from a first network entity associated with a first cell type and operating via a first carrier frequency, the first signal comprising an indication of a reference timestamp of a measurement gap, the reference timestamp corresponding to a second network entity associated with a second cell type and operating via a second carrier frequency; and monitoring the second carrier frequency as part of a cell measurement procedure and during the measurement gap to obtain a second signal from the second network entity, the measurement gap being based at least in part on the reference timestamp.

[0238] Aspect 2: According to the method of Aspect 1, the method also includes: receiving the second signal from the second network entity at least in part based on the monitored second carrier frequency; and switching the connection from the first network entity to the second network entity at least in part based on one or more measurements of the second signal.

[0239] Aspect 3: A method according to Aspect 2, wherein the cell measurement procedure includes a first cell measurement procedure, and the method further includes: receiving a third signal from the second network entity, the third signal including a first priority value of the first carrier frequency corresponding to the first cell type, the first priority value being less than a second priority value corresponding to the second cell type; and avoiding performing a second cell measurement procedure on the first carrier frequency based at least in part on the first priority value.

[0240] Aspect 4: According to the method described in Aspect 2, the method also includes: avoiding performing a second cell measurement procedure on the first carrier frequency based at least in part on a first priority value of the first carrier frequency, the first priority value being at least in part based on the first carrier frequency corresponding to the first cell type, and the first priority value being less than a second priority value corresponding to the second cell type.

[0241] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the first cell type corresponds to a first priority value, and the method further includes: receiving a third signal from the first network entity, the third signal including a second priority value of the second carrier frequency, the second priority value being at least partially based on the second carrier frequency corresponding to the second cell type, the second priority value being greater than the first priority value corresponding to the first cell type, and monitoring of the second carrier frequency being at least partially based on the second priority value.

[0242] Aspect 6: The method according to aspect 5, further comprising: operating at least in part based on connected mode mobility, the second priority value of the second carrier frequency being associated with a configuration for the connected mode mobility.

[0243] Aspect 7: A method according to any one of Aspects 1 to 4, wherein the first cell type corresponds to a first priority value, and the monitoring of the second carrier frequency further includes: monitoring the second carrier frequency based at least in part on a second priority value of the second carrier frequency, the second priority value being at least in part based on the second carrier frequency corresponding to the second cell type, the second priority value being greater than the first priority value corresponding to the first cell type.

[0244] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method further includes: receiving an SSB from the second network entity, the SSB including a second timestamp corresponding to the second network entity; and as part of a second cell measurement procedure, monitoring a third signal from the second network entity during the measurement gap at least partially based on the second timestamp.

[0245] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: sending a third signal indicating location information of the UE to the first network entity, indicating that the first signal corresponding to the reference timestamp of the second network entity is at least partially based on the location information of the UE.

[0246] Aspect 10: The method according to any one of aspects 1 to 9, wherein the reference timestamp comprises a UTC timestamp, a portion of the UTC timestamp, a GNSS timestamp, a portion of the GNSS timestamp, or a combination thereof.

[0247] Aspect 11: The method according to any one of aspects 1 to 10, wherein the reference timestamp indicates a SFN having a value of 0 for the second network entity.

[0248] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the first signal also indicates an offset in the time domain for the measurement gap, the periodicity of the measurement gap, the duration of the measurement gap, or a combination thereof, and monitoring the second carrier frequency is also at least partially based on the offset, the periodicity, the duration, or a combination thereof.

[0249] Aspect 13: According to the method described in any one of Aspects 1 to 12, the method further includes: sending a third signal indicating a time slot level offset for the measurement gap to the first network entity based at least in part on the measurement gap, wherein the measurement gap is at least in part based on the reference timestamp, and the reference timestamp corresponds to the downlink time slot boundary of the second network entity crossing the first network entity.

[0250] Aspect 14: According to the method described in any one of Aspects 1 to 13, the method further includes: receiving a third signal from the first network entity, the third signal indicating location information and a distance threshold of multiple cells associated with the second cell type, the third signal at least indicating a corresponding location and a corresponding distance threshold of the second network entity; and monitoring the second signal from the second network entity at least in part based on the UE being within the corresponding distance threshold of the corresponding location of the second network entity.

[0251] Aspect 15: The method according to any one of aspects 1 to 14, wherein the first cell type comprises a non-terrestrial network (NTN) cell type; and the second cell type comprises a terrestrial network (TN) cell type.

[0252] Aspect 16: A method for performing wireless communications at a first network entity, the method comprising: outputting a first signal, the first signal comprising a request for a reference timestamp corresponding to a second network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency; obtaining a second signal based at least in part on the request, the second signal indicating the reference timestamp corresponding to the second network entity; and outputting a third signal, the third signal indicating the reference timestamp corresponding to the second network entity, the third signal configuring a measurement gap for a UE.

[0253] Aspect 17: According to the method according to Aspect 16, the method also includes: obtaining a fourth signal, the fourth signal indicating the first location information of the UE, and the third signal is received at least in part based on the first location information of the UE and the second location information of the second network entity.

[0254] Aspect 18: According to the method described in any one of Aspects 16 to 17, the method further includes: outputting a fourth signal, the fourth signal indicating location information and distance threshold of multiple cells associated with the second cell type, the fourth signal at least indicating the location and distance threshold of the second network entity.

[0255] Aspect 19: The method according to any one of aspects 16 to 18, the method further comprising: obtaining an additional signal based at least in part on periodicity, the additional signal indicating an additional reference timestamp corresponding to the second network entity.

[0256] Aspect 20: A method according to any one of Aspects 16 to 19, wherein the first cell type corresponds to a first priority value, and the method further includes: outputting a fourth signal based at least in part on the second carrier frequency corresponding to the second cell type, the fourth signal including a second priority value of the second carrier frequency associated with the second network entity, the second priority value being greater than the first priority value corresponding to the first cell type.

[0257] Aspect 21: The method according to any one of Aspects 16 to 20, wherein the reference timestamp comprises a UTC timestamp, a portion of the UTC timestamp, a GNSS timestamp, a portion of the GNSS timestamp, or a combination thereof.

[0258] Aspect 22: The method according to any one of aspects 16 to 21, wherein the reference timestamp indicates a SFN having a value of 0 for the second network entity.

[0259] Aspect 23: A method according to any one of aspects 16 to 22, wherein the first cell type comprises an NTN cell type; and the second cell type comprises a TN cell type.

[0260] Aspect 24: A method for performing wireless communications at a second network entity, the method comprising: obtaining a first signal, the first signal comprising a request for a reference timestamp corresponding to the second network entity, the request being associated with the first network entity, the first network entity being associated with a first cell type and operating via a first carrier frequency, and the second network entity being associated with a second cell type and operating via a second carrier frequency; outputting a second signal based at least in part on the request, the second signal indicating the reference timestamp corresponding to the second network entity; and outputting a third signal during a measurement gap, the measurement gap being based at least in part on the reference timestamp.

[0261] Aspect 25: The method according to aspect 24, the method further comprising: establishing a connection with a UE based at least in part on the third signal.

[0262] Aspect 26: The method according to any one of Aspects 24 to 25, further comprising: outputting an SSB, the SSB comprising a second timestamp corresponding to the second network entity.

[0263] Aspect 27: The method according to any one of aspects 24 to 26, the method further comprising: outputting an additional signal based at least in part on periodicity, the additional signal indicating an additional reference timestamp corresponding to the second network entity.

[0264] Aspect 28: According to the method described in any one of Aspects 24 to 27, the method further includes: outputting a fourth signal, the fourth signal including a first priority value corresponding to the first cell type of the first carrier frequency, the first priority value being less than a second priority value corresponding to the second cell type.

[0265] Aspect 29: A method according to any one of Aspects 24 to 28, wherein the first cell type comprises an NTN cell type; and the second cell type comprises a TN cell type.

[0266] Aspect 30: An apparatus for wireless communication at a UE, the apparatus comprising: a processor; and a memory, the memory being coupled to the processor, the processor being configured to execute the method according to any one of aspects 1 to 15.

[0267] Aspect 31: An apparatus for wireless communication at a UE, the apparatus comprising at least one means for performing the method according to any one of aspects 1 to 15.

[0268] Aspect 32: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 15.

[0269] Aspect 33: An apparatus for wireless communication at a first network entity, the apparatus comprising: a processor; and a memory coupled to the processor, the processor being configured to perform a method according to any one of aspects 16 to 23.

[0270] Aspect 34: An apparatus for wireless communication at a first network entity, the apparatus comprising at least one means for performing a method according to any one of aspects 16 to 23.

[0271] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 16 to 23.

[0272] Aspect 36: An apparatus for wireless communication at a second network entity, the apparatus comprising: a processor; and a memory coupled to the processor, the processor being configured to perform a method according to any one of aspects 24 to 29.

[0273] Aspect 37: An apparatus for wireless communication at a second network entity, the apparatus comprising at least one means for performing a method according to any one of aspects 24 to 29.

[0274] Aspect 38: A non-transitory computer-readable medium storing code for wireless communication at a second network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 24 to 29.

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

[0276] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system 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 described techniques 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.

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

[0278] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed 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, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0279] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium or sent using the one or more instructions or codes. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0280] Computer-readable media include both non-transient computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location to another.Non-transient storage media can be any available media that can be accessed by a general or special computer.By way of example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or can be used to carry or store desired program code components in the form of instructions or data structures and any other non-transient media that can be accessed by a general or special computer, or a general or special processor.Moreover, any connection is appropriately referred to as a computer-readable medium.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of computer-readable media. Disks and optical disks as used herein include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. 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.

[0281] 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, such 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" may be based on 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."

[0282] 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, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.

[0283] 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 reference label, or other subsequent reference labels.

[0284] 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 "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described technology. However, these technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0285] 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. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; and a memory coupled to the processor, wherein the processor is configured to: receiving a first signal from a first network entity associated with a first cell type operating via a first carrier frequency, the first signal indicating a reference timestamp of a measurement gap corresponding to a second network entity associated with a second cell type operating via a second carrier frequency; as well as The second carrier frequency is monitored for a second signal from the second network entity as part of a cell measurement procedure and during the measurement gap, the measurement gap being based at least in part on the reference timestamp.

2. The apparatus of claim 1, wherein the processor is further configured to: receiving the second signal from the second network entity based at least in part on the monitored second carrier frequency; and A connection is switched from the first network entity to the second network entity based at least in part on one or more measurements of the second signal.

3. The apparatus of claim 2, wherein the cell measurement procedure comprises a first cell measurement procedure, and the processor is further configured to: receiving a third signal from the second network entity, the third signal comprising a first priority value corresponding to the first cell type for the first carrier frequency, wherein the first priority value is less than a second priority value corresponding to the second cell type; and A second cell measurement procedure is avoided on the first carrier frequency based at least in part on the first priority value.

4. The apparatus of claim 2, wherein the processor is further configured to: Avoiding a second cell measurement procedure for the first carrier frequency based at least in part on a first priority value for the first carrier frequency, the first priority value being based at least in part on the first carrier frequency corresponding to the first cell type, the first priority value being less than a second priority value corresponding to the second cell type.

5. The apparatus of claim 1 , wherein the first cell type corresponds to a first priority value, and the processor is further configured to: A third signal is received from the first network entity, the third signal comprising a second priority value for the second carrier frequency, the second priority value being based at least in part on the second carrier frequency corresponding to the second cell type, the second priority value being greater than the first priority value corresponding to the first cell type, wherein the second carrier frequency is monitored based at least in part on the second priority value.

6. The apparatus of claim 5, wherein the processor is further configured to: The operation is based at least in part on connected mode mobility, the second priority value for the second carrier frequency being associated with a configuration for the connected mode mobility.

7. The apparatus of claim 1 , wherein the first cell type corresponds to a first priority value, and the processor configured to monitor the second carrier frequency is configured to: The second carrier frequency is monitored based at least in part on a second priority value for the second carrier frequency, the second priority value being based at least in part on the second carrier frequency corresponding to the second cell type, wherein the second priority value is greater than the first priority value corresponding to the first cell type.

8. The apparatus of claim 1, wherein the processor is further configured to: receiving a synchronization signal block from the second network entity, the synchronization signal block comprising a second timestamp corresponding to the second network entity; and As part of a second cell measurement procedure, a third signal from the second network entity is monitored during the measurement gap based at least in part on the second timestamp.

9. The apparatus of claim 1, wherein the processor is further configured to: A third signal indicating location information of the UE is sent to the first network entity, the first signal indicating that the reference timestamp corresponding to the second network entity is based at least in part on the location information of the UE.

10. The apparatus of claim 1, wherein the reference timestamp comprises a Coordinated Universal Time (UTC) timestamp, a portion of the UTC timestamp, a Global Navigation Satellite System (GNSS) timestamp, a portion of the GNSS timestamp, or a combination thereof.

11. The apparatus of claim 1, wherein the reference timestamp indicates a system frame number (SFN) having a value of 0 for the second network entity.

12. The apparatus of claim 1 , wherein the first signal further indicates an offset in the time domain for the measurement gap, a periodicity of the measurement gap, a duration of the measurement gap, or a combination thereof, and wherein the second carrier frequency is monitored based at least in part on the offset, the periodicity, the duration, or a combination thereof.

13. The apparatus of claim 1, wherein the processor is further configured to: A third signal indicating a slot level offset for the measurement gap is sent to the first network entity according to the measurement gap, the measurement gap being based at least in part on the reference timestamp corresponding to a downlink slot boundary of the second network entity crossing the first network entity.

14. The apparatus of claim 1, wherein the processor is further configured to: receiving a third signal from the first network entity, the third signal indicating location information and a distance threshold of a plurality of cells associated with the second cell type, wherein the third signal indicates at least a corresponding location and a corresponding distance threshold of the second network entity; and The second signal from the second network entity is monitored based at least in part on the UE being within the respective distance threshold of the respective location of the second network entity.

15. The device according to claim 1, wherein: The first cell type comprises a non-terrestrial network (NTN) cell type; and The second cell type comprises a terrestrial network (TN) cell type.

16. An apparatus for wireless communication at a first network entity, the apparatus comprising: processor; and a memory coupled to the processor, wherein the processor is configured to: outputting a first signal including a request for a reference timestamp corresponding to a second network entity, the first network entity being associated with a first cell type operating via a first carrier frequency and the second network entity being associated with a second cell type operating via a second carrier frequency; obtaining, based at least in part on the request, a second signal indicating the reference timestamp corresponding to the second network entity; as well as A third signal is outputted, the third signal indicating the reference timestamp corresponding to the second network entity and configuring a measurement gap for a user equipment (UE).

17. The apparatus of claim 16, wherein the processor is further configured to: A fourth signal is obtained, wherein the fourth signal indicates first location information of the UE, and the third signal is at least partially based on the first location information of the UE and second location information of the second network entity.

18. The apparatus of claim 16, wherein the processor is further configured to: A fourth signal is output, the fourth signal indicating location information and a distance threshold of a plurality of cells associated with the second cell type, wherein the fourth signal at least indicates the location and the distance threshold of the second network entity.

19. The apparatus of claim 16, wherein the processor is further configured to: An additional signal is obtained based at least in part on the periodicity, the additional signal indicating an additional reference timestamp corresponding to the second network entity.

20. The apparatus of claim 16, wherein the first cell type corresponds to a first priority value, and the processor is further configured to: A fourth signal is output based at least in part on the second carrier frequency corresponding to the second cell type, the fourth signal comprising a second priority value for the second carrier frequency associated with the second network entity, wherein the second priority value is greater than the first priority value corresponding to the first cell type.

21. The apparatus of claim 16, wherein the reference timestamp comprises a Coordinated Universal Time (UTC) timestamp, a portion of the UTC timestamp, a Global Navigation Satellite System (GNSS) timestamp, a portion of the GNSS timestamp, or a combination thereof.

22. The apparatus of claim 16, wherein the reference timestamp indicates a system frame number (SFN) having a value of 0 for the second network entity.

23. The apparatus of claim 16, wherein: The first cell type comprises a non-terrestrial network (NTN) cell type; and The second cell type comprises a terrestrial network (TN) cell type.

24. An apparatus for wireless communication at a second network entity, the apparatus comprising: processor; and a memory coupled to the processor, wherein the processor is configured to: obtaining a first signal, the first signal comprising a request for a reference timestamp corresponding to the second network entity, the request being associated with the first network entity, the first network entity being associated with a first cell type operating via a first carrier frequency, and the second network entity being associated with a second cell type operating via a second carrier frequency; outputting, based at least in part on the request, a second signal indicating the reference timestamp corresponding to the second network entity; as well as A third signal is output during a measurement gap, the measurement gap being based at least in part on the reference timestamp.

25. The apparatus of claim 24, wherein the processor is further configured to: A connection with a user equipment (UE) is established based at least in part on the third signal.

26. The apparatus of claim 24, wherein the processor is further configured to: A synchronization signal block is output, wherein the synchronization signal block includes a second timestamp corresponding to the second network entity.

27. The apparatus of claim 24, wherein the processor is further configured to: An additional signal is output based at least in part on the periodicity, the additional signal indicating an additional reference timestamp corresponding to the second network entity.

28. The apparatus of claim 24, wherein the processor is further configured to: A fourth signal is output, the fourth signal including a first priority value corresponding to the first cell type for the first carrier frequency, wherein the first priority value is less than a second priority value corresponding to the second cell type.

29. The apparatus of claim 24, wherein: The first cell type comprises a non-terrestrial network (NTN) cell type; and The second cell type comprises a terrestrial network (TN) cell type.

30. A method for wireless communication at a user equipment (UE), the method comprising: receiving a first signal from a first network entity associated with a first cell type operating via a first carrier frequency, the first signal comprising an indication of a reference timestamp of a measurement gap, the reference timestamp corresponding to a second network entity associated with a second cell type operating via a second carrier frequency; as well as The second carrier frequency is monitored for a second signal from the second network entity as part of a cell measurement procedure and during the measurement gap, the measurement gap being based at least in part on the reference timestamp.

Images