Techniques for non-terrestrial network mobility with mobile cells
By receiving coverage and location information, the UE or network device sends timing information to determine whether the handover is completed in time, solving the mobility management problem of mobile cells in non-terrestrial networks, improving the robustness of the system and resource utilization efficiency.
Patent Information
- Application Number
- CN202480010524.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-02-08
- Filing Date
- 2024-01-09
- Publication Date
- 2025-09-02
AI Technical Summary
In non-terrestrial networks, in the mobility management of mobile cells, it is difficult for the prior art to effectively manage the mobility of wireless devices within the cell coverage area, resulting in the possible failure of measurement-based handovers to be completed in a timely manner, resulting in waste of resources and robustness problems.
By receiving coverage information and location information, the UE or network device sends timing information to determine whether to complete measurement-based handover in a timely manner and configure non-measurement-based handover as needed to optimize mobility management.
Improve mobility robustness, reduce resource waste, and enhance the mobility management capabilities of wireless communication systems.
Smart Images

Figure CN120584468A_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims the benefit of U.S. patent application No. 18 / 166,411, filed by JI et al. on February 8, 2023, entitled “TECHNIQUES FOR NON-TERRESTRIAL NETWORK MOBILITY WITH A MOVING CELL,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Background Art
[0003] The following relates to wireless communications, including mobility in non-terrestrial networks (NTNs) with mobile cells.
[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and more. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as user equipment (UE). Summary of the Invention
[0005] A method for wireless communication at a UE is described. The method may include receiving an indication of coverage information of a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication; and sending a message indicating timing information associated with a measurement-based handover of the UE from the first cell to a second cell associated with the NTN based on location information of the UE and the coverage information.
[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 an indication of coverage information of a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication; and send a message indicating timing information associated with a measurement-based handover of the UE from the first cell to a second cell associated with the NTN based on location information of the UE and the coverage information.
[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving an indication of coverage information of a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication; and means for sending a message indicating timing information associated with a measurement-based handover of the UE from the first cell to a second cell associated with the NTN based on location information of the UE and the coverage information.
[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 an indication of coverage information of a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication; and send a message indicating timing information associated with a measurement-based handover of the UE from the first cell to a second cell associated with the NTN based on location information of the UE and the coverage information.
[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling associated with a non-measurement-based handover of the UE from the first cell to the second cell in response to the message indicating the timing information.
[0010] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the non-measurement-based handover from the first cell to the second cell based on the control signaling.
[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a configuration from the NTN for sending the message indicating the timing information, the message indicating the timing information being sent in response to the configuration received from the NTN.
[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the configuration may be associated with one of a satellite type or a non-terrestrial cell type of the first cell or the second cell or both.
[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of a timing threshold, the message being sent based on a failure to satisfy the timing threshold for a duration of time associated with the UE remaining within the coverage area supported by the first cell.
[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the duration of time associated with the UE remaining within the coverage area supported by the first cell may be based on the location information of the UE, ephemeris of a satellite associated with the first cell, a reference location of the first cell, a radius of the first cell, the coverage information, or any combination thereof.
[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be sent based on a first time duration associated with the UE being within the coverage area supported by the first cell being less than a second time duration associated with a UE characteristic for the measurement-based handover.
[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second time duration associated with the UE characteristics may be based on the number or characteristics of the UE's antennas, the round-trip time between the UE and the first cell or the second cell, or any combination thereof.
[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of one or more parameters associated with the measurement-based handover of the UE, the message being sent based on a first time duration associated with the UE being within the coverage area supported by the first cell being less than a second time duration associated with the UE performing the measurement-based handover, the second time duration being based on the one or more parameters associated with the measurement-based handover or a UE characteristic associated with the measurement-based handover, or any combination of both.
[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more parameters associated with the measurement-based handover include a measurement periodicity, a measurement gap repetition period, or both.
[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the one or more parameters may be received via a system information block (SIB), a radio resource control (RRC) message, a medium access control (MAC) message, or any 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 receiving an indication of parameters for performing measurements for the measurement-based handover from the first cell to the second cell, the one or more parameters associated with the measurement-based handover being based on the parameters for performing the measurements for the measurement-based handover.
[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the message may include operations, features, components, or instructions for sending the message indicating: a recommendation for the UE to perform one of the measurement-based handover or the non-measurement-based handover, whether the UE can complete the measurement-based handover before leaving the coverage area of the first cell, an estimated time duration associated with the UE remaining in the coverage area of the first cell, the location of the UE, or any combination thereof.
[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, from the NTN, a configuration indicating one or more parameters of the timing information or a granularity of the timing information, the timing information being based on the configuration received from the NTN.
[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be sent via a third message or a fifth message of the random access procedure, an uplink message following the random access procedure, a random access preamble, a random access opportunity, or any combination thereof.
[0024] A method for wireless communication at a UE is described. The method may include receiving an indication of coverage information of a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication; and receiving a handover command associated with measurement-based handover of the UE after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and the UE.
[0025] 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 an indication of coverage information of a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication; and receive a handover command associated with measurement-based handover of the UE after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and the UE.
[0026] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving an indication of coverage information of a first cell associated with an NTN, the coverage information indicating a coverage area for wireless communication supported by the first cell; and means for receiving a handover command associated with measurement-based handover of the UE after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and the UE.
[0027] 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 an indication of coverage information of a first cell associated with an NTN, the coverage information indicating a coverage area for wireless communication supported by the first cell; and receive a handover command associated with measurement-based handover of the UE after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and the UE.
[0028] 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 message indicating timing information associated with the measurement-based handover from the first cell to a second cell associated with the NTN based on the location information of the UE and the coverage information.
[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message indicates that the UE can perform the measurement-based handover before leaving the coverage area supported by the first cell.
[0030] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the measurement-based handover from the first cell to the second cell based on the handover command.
[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of a timing threshold, the handover command being received based on a duration of time associated with the UE remaining within the coverage area supported by the first cell satisfying the timing threshold.
[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the duration of time associated with the UE remaining within the coverage area supported by the first cell may be based on location information of the UE, ephemeris of a satellite associated with the first cell, a reference location of the first cell, a radius of the first cell, the coverage information, or any combination thereof.
[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the handover command may be received based on a first time duration associated with the UE being within the coverage area supported by the first cell being greater than a second time duration associated with the UE characteristics for the measurement-based handover.
[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second time duration associated with the UE characteristics may be based on the number or characteristics of the UE's antennas, the round-trip time between the UE and the first cell or the second cell associated with the handover command, or any combination thereof.
[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of one or more parameters associated with the measurement-based handover, the handover command being received based on a first time duration associated with the UE being within the coverage area supported by the first cell being greater than a second time duration associated with the UE performing the measurement-based handover, the second time duration being based on the one or more parameters associated with the measurement-based handover or a UE characteristic associated with the measurement-based handover, or any combination of both.
[0036] A method for wireless communication at a network device is described. The method may include: outputting an indication of coverage information for a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication; and monitoring for a message indicating timing information associated with a measurement-based handover from the first cell to a second cell associated with the NTN.
[0037] An apparatus for wireless communication at a network device is described. The apparatus may include a processor and a memory coupled to the processor. The processor may be configured to: output an indication of coverage information for a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication; and monitor for a message indicating timing information associated with a measurement-based handover from the first cell to a second cell associated with the NTN.
[0038] Another apparatus for wireless communication at a network device is described. The apparatus may include: means for outputting an indication of coverage information for a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication; and means for monitoring a message indicating timing information associated with a measurement-based handover from the first cell to a second cell associated with the NTN.
[0039] A non-transitory computer-readable medium storing code for wireless communication at a network device is described. The code may include instructions executable by a processor to: output an indication of coverage information for a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication; and monitor for a message indicating timing information associated with a measurement-based handover from the first cell to a second cell associated with the NTN.
[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, monitoring the message may include operations, features, components, or instructions for obtaining the message indicating the timing information associated with the measurement-based handover from the first cell to the second cell associated with the NTN.
[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, control signaling associated with a non-measurement-based handover from the first cell to the second cell is output in response to the message indicating the timing information.
[0042] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a configuration for sending the message indicating the timing information, the message indicating the timing information being received based on the configuration.
[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the configuration may be associated with one of a satellite type or a non-terrestrial cell type of the first cell or the second cell or both.
[0044] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting an indication of a timing threshold, the message indicating that a duration of time associated with remaining within the coverage area supported by the first cell failed to meet the timing threshold.
[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message indicates that a first time duration associated with being within the coverage area supported by the first cell may be less than a second time duration associated with a wireless device characteristic for the measurement-based handover.
[0046] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting an indication of one or more parameters associated with the measurement-based handover, the message indicating that a first time duration associated with being within the coverage area supported by the first cell may be less than a second time duration associated with the wireless device performing the measurement-based handover, the second time duration being based on either or both of the one or more parameters associated with the measurement-based handover, a wireless device characteristic associated with the measurement-based handover, or both.
[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more parameters associated with the measurement-based handover include a measurement periodicity, a measurement gap repetition period, or both.
[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message indicates a recommendation for the measurement-based handover or the non-measurement-based handover, an inability of the wireless device to complete the measurement-based handover before leaving the coverage area of the first cell, an estimated duration of time associated with the wireless device remaining in the coverage area of the first cell, a location of the wireless device, or any combination thereof.
[0049] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a configuration indicating one or more parameters of the timing information or a granularity of the timing information, the timing information being based on the configuration.
[0050] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be obtained via a third message or a fifth message of the random access procedure, an uplink message following the random access procedure, a random access preamble, a random access opportunity, or any combination thereof.
[0051] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message indicates that the wireless device can perform the measurement-based handover before leaving the coverage area supported by the first cell.
[0052] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message indicates that the wireless device cannot perform the measurement-based handover before leaving the coverage area supported by the first cell.
[0053] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a handover command associated with the measurement-based handover of the wireless device is output after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and the wireless device.
[0054] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the coverage information may be sent via a SIB, an RRC message, a MAC message, or any combination thereof.
[0055] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting an indication of one or more parameters for performing measurements for the measurement-based handover from the first cell to the second cell, the message being received in response to the indication of the one or more parameters.
[0056] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining a second message indicating a recommendation to perform the measurement-based handover or the non-measurement-based handover, an indication of whether the measurement-based handover can be completed before the wireless device leaves the coverage area of the first cell, an estimated duration of time associated with the wireless device remaining in the coverage area of the first cell, a location of the wireless device, or any combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS
[0057] Figure 1 An example of a wireless communication system supporting technology for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated.
[0058] Figure 2 An example of a network architecture supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated.
[0059] Figure 3An example of a wireless communication system supporting technology for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated.
[0060] Figure 4 An example of a mobile cell scenario supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated.
[0061] Figure 5 An example of a process flow supporting techniques for NTN mobility with mobile cells in accordance with one or more aspects of the present disclosure is illustrated.
[0062] Figure 6 and Figure 7 A block diagram illustrating a device supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated.
[0063] Figure 8 A block diagram illustrating a communications manager supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated.
[0064] Figure 9 A diagram illustrating a system including devices supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated.
[0065] Figure 10 and Figure 11 A block diagram illustrating a device supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated.
[0066] Figure 12 A block diagram illustrating a communications manager supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated.
[0067] Figure 13 A diagram illustrating a system including devices supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated.
[0068] Figures 14 to 18 A flow chart illustrating a method of supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION
[0069] Some wireless communication systems may include non-terrestrial entities, such as aircraft, UAVs, Zeppelins, satellites, and the like. In some cases, when a wireless device (e.g., a UE) is outside the cellular coverage of a terrestrial network entity (such as a base station or other network entity), the wireless device may be able to communicate with the non-terrestrial entity. In such cases, the UE may be able to connect to the non-terrestrial entity, allowing the non-terrestrial entity to relay wireless communications to and from the UE. For the purposes of this disclosure, different types of non-terrestrial entities may be referred to as non-terrestrial relay nodes (e.g., aircraft, UAVs, etc.) or NTN nodes (e.g., satellites). Non-terrestrial relay nodes may function as UEs, integrated access and backhaul (IAB) nodes, network entities, or any combination thereof, and may be configured to relay communications between wireless devices (e.g., between a UE and a terrestrial entity, other non-terrestrial entities, or both). NTN nodes may include non-terrestrial entities (e.g., satellites) that are associated with an NTN and communicatively coupled to terrestrial entities (e.g., NTN gateways). The NTN may support both measurement-based handover and non-measurement-based handover. For measurement-based handover, a wireless device, such as a UE, accessing a cell or coverage area supported by an NTN can perform measurements on a different cell or beam (such as a cell or beam transmitted by another non-terrestrial entity) in order to reselect another beam for handover. For non-measurement-based handover, the UE or the NTN can select a new cell or beam for the UE based on, for example, the UE's positioning information.
[0070] Non-terrestrial entities can be mobile, such as satellites moving through space. Some wireless communication systems can provide a quasi-Earth-fixed beam or cell scenario, in which the coverage area of a beam or cell remains static on Earth for a specific amount of time while the non-terrestrial entity moves. For example, the non-terrestrial entity can adjust the projection angle of the coverage area so that the beam or cell coverage area covers the same location on Earth for a certain period of time. Additionally or alternatively, some wireless communication systems can support an Earth-mobile beam or cell scenario, in which the coverage area of a beam or cell moves on Earth along with the non-terrestrial entity.
[0071] In the case of an earth mobile cell, network equipment at different locations in the cell coverage area may move out, exit or leave the cell coverage at different timings. For example, a UE that accesses a cell when it is in the middle of the cell coverage may be connected for a longer time than a UE that accesses the cell near the cell edge or when the cell is gradually disappearing. If the UE accesses the cell when the cell is gradually disappearing, the UE may go out of coverage before completing the measurement-based handover, which may reduce the robustness for supporting mobility. However, even if the UE cannot complete the measurement-based handover before leaving the cell coverage, the non-ground entity may still configure the UE with measurement-based events and configurations for the measurement-based handover, and configuring unused measurement-based events and configurations to the UE may waste resources. In some examples, if the UE initiates a measurement-based handover and is handed over to another cell before leaving the cell coverage of the first cell, the UE may be considered to be able to complete the handover process. If the UE is not handed over to another cell before leaving the cell coverage of the first cell, the UE may not be considered to have completed the measurement-based handover process.
[0072] Therefore, one or more aspects of the present disclosure relate to timing information indicating whether a UE can complete a measurement-based handover before exiting the coverage area of a cell in an NTN or before the coverage area of a cell in the NTN moves away from the UE such that the UE is no longer within the coverage area of the cell. For example, when a UE accesses a cell, the UE may send an indication to a network node or network device of the NTN. This indication may assist the NTN in determining a solution for supporting NTN mobility for the UE. For example, the NTN may determine whether there is sufficient time to perform a measurement-based handover for the UE before the UE exits the coverage area of the cell. In some examples, if the UE does not have sufficient time to perform a measurement-based handover, the UE may send an indication. If the UE sends the indication, in response, according to one aspect, the UE may be configured to perform a non-measurement-based handover. If the UE has sufficient time to perform a measurement-based handover before leaving the coverage area of the cell, the NTN may configure the UE to perform a measurement-based handover. In some examples, if the UE has sufficient time to perform a measurement-based handover, the UE may not send an indication, or the UE may send an indication indicating that the UE does have sufficient time to perform a measurement-based handover.
[0073] A UE may determine whether it can complete a measurement-based handover before leaving the coverage area of a cell based on a configuration received from the NTN. For example, the NTN may transmit a timing threshold to the UE, and the UE may determine whether to send an indication based on the timing threshold and the UE's estimated time duration before leaving the coverage of the serving cell. In some examples, the UE may estimate a first time duration until the UE leaves the cell and a second time duration associated with performing a measurement-based handover. If the first time duration exceeds the second time duration (e.g., the UE estimates that a measurement-based handover can be performed before leaving the cell), the UE may send an indication. Additional techniques for configuring an estimate or determination of whether a measurement-based handover can be performed in a timely manner are described herein. If the UE can perform a measurement-based handover in a timely manner, the NTN may configure the UE for a measurement-based handover, or if the UE cannot perform a measurement-based handover in a timely manner, the NTN may configure the UE for a non-measurement-based handover, which may improve mobility robustness. Additionally, if the UE cannot perform a measurement-based handover in a timely manner, the NTN may not configure the UE with measurement-based events and configurations, which may increase resource availability and reduce overhead.
[0074] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to techniques for NTN mobility with mobile cells.
[0075] Figure 1 An example of a wireless communication system 100 supporting techniques for NTN mobility with mobile cells 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 an LTE network, an LTE-A network, an LTE-A Pro network, an NR network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).
[0076] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entities 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entities 105 and the UEs 115 may support signal communication based on one or more radio access technologies (RATs).
[0077] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices that take different forms or have different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 105) as shown.
[0078] As described herein, a node of wireless communication system 100 (which may be referred to as a network node or 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 UE 115. As another example, the node may be 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 UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.
[0079] In some examples, network entities 105 can communicate with core network 130, with each other, or both. For example, network entities 105 can communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 can communicate with each other via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130). In some examples, network entities 105 can 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. Backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 can be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .
[0080] 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 base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an eNodeB (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home eNodeB, or other suitable terminology). In some examples, the network entity 105 (e.g., the base station 140) may be implemented in a converged (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as the base station 140).
[0081] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an 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 can 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, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit receive point (TRP). One or more components of the network entity 105 in the disaggregated 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 disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0082] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of the protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of the protocol stack and DU 165 can support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., 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, 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 can be within the protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via these communication links.
[0083] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources used for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by one another. One or more IAB nodes 104 may be referred to as a donor entity or IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication link 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the disaggregated 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.
[0084] For example, an access network (AN) or RAN may include communications between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). In other words, the IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170). In this case, the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via the F1 interface according to a protocol that defines signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of part of a backhaul link).
[0085] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). A DU 165 may act as a distributed scheduling node for child nodes associated with the IAB node 104, and an IAB-MT may act as a scheduled node for a parent node associated with the IAB node 104. In other words, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of an IAB node 104 may provide a Uu interface for child IAB nodes 104 to receive signaling from the parent IAB node 104, and a DU interface (e.g., DU 165) may provide a Uu interface for the parent IAB node 104 to signal to child IAB nodes 104 or UE 115.
[0086] For example, IAB node 104 may be referred to as a parent node supporting communications for child IAB nodes, or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection to the core network 130 (e.g., backhaul communication link 120) and may serve as a parent node for IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to UE 115 via IAB node 104, or may directly signal the transmissions to UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to IAB node 104 via the F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via the DU 165. In other words, data may be relayed to and from IAB node 104 via signaling via the NR Uu interface of the MT to IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .
[0087] 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 the techniques described herein for NTN mobility with mobile cells. 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).
[0088] 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 terminology, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects, such as appliances or vehicles, meters, etc.
[0089] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.
[0090] UE 115 and network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure that defines the communication link 125. For example, a carrier used for communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (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 operation, user data, or other signaling. The wireless communication system 100 may support communications with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between those devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of 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).
[0091] 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 by UE 115 may occur via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.
[0092] 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, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in an FDD mode) or may be configured to carry both downlink and uplink communications (e.g., in a TDD mode).
[0093] A carrier may be associated with a particular bandwidth of RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communication using a particular carrier bandwidth, or may be configurable to support communication using one of the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.
[0094] The signal waveform transmitted via a carrier wave may include multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In systems employing MCM techniques, a resource element may refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in a 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, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communications with UE 115.
[0095] One or more parameter sets for a carrier may be supported, and the parameter set may include subcarrier spacing ( ) and cyclic prefix. A carrier can be divided into one or more BWPs with the same or different parameter sets. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communications by UE 115 can be constrained to one or more active BWPs.
[0096] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period. seconds, of which can represent the supported subcarrier spacing, and The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each of which has a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).
[0097] 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 (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to the front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.
[0098] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a Transmit Time Interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).
[0099] Physical channels may be multiplexed according to various techniques for communication using carriers. For example, physical control channels and physical data channels may be multiplexed using one or more of time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques for signaling via downlink carriers. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of a carrier or a subset of that bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of 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 a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .
[0100] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with network entity 105 (e.g., using a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) used to distinguish between adjacent cells. In some examples, a cell may also refer to a cell coverage area, coverage area 110, or a portion (e.g., a sector) of coverage area 110 in which a logical communication entity operates (e.g., within which wireless communications for devices such as UE 115 are supported). Depending on various factors (e.g., the capabilities of 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 include a building, a subset of buildings, or an external space between or overlapping coverage areas 110.
[0101] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. Compared to a macro cell, a small cell may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different frequency bands (e.g., licensed or unlicensed) as the macro cell. A small cell may provide unrestricted access to UEs 115 that have a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG) or UEs 115 associated with users 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 the one or more cells.
[0102] 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 to different types of devices.
[0103] In some examples, network entities 105 (e.g., base stations 140, RUs 170) can be mobile and, therefore, provide communication coverage for mobile coverage areas 110. For example, a satellite can be an example of a network entity 105 or aspects of a network entity 105 and can support or provide mobile cells or mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but the different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.
[0104] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.
[0105] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application, which uses the information or presents it to a human interacting with the application. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other equipment. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.
[0106] Some UEs 115 may be configured to employ a reduced power consumption operating mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception, but not concurrent transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power conservation techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.
[0107] 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 functionality. Ultra-reliable communication may include private 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 functionality may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
[0108] In some examples, a UE 115 can 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 performing D2D communication can be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which can 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 can be outside of the coverage area 110 of the network entity 105 or can otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can 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, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.
[0109] In some systems, D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. Vehicles may signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units) or with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.
[0110] 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, which may be an evolved packet core (EPC) or a 5G core (5GC), 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 external networks. The control plane entities 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 transferred through the user plane entities, which may provide IP address allocation and other functions. The user plane entities may connect to one or more network operators' IP services 150. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0111] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, despite a portion of FR1 exceeding 6 GHz, FR1 is often (and interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes arises with FR2, which is often (and interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being distinct from the extremely high frequency (EHF) band (30 GHz-300 GHz), which is designated as a "millimeter wave" band by the International Telecommunication Union (ITU).
[0112] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz-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.
[0113] In view of the above aspects, unless otherwise specified, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can be broadly referred to as frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as frequencies that may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may include mid-band frequencies.
[0114] The wireless communication system 100 can operate using one or more frequency bands that can range from 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features (which can be referred to as clusters), but these waves can penetrate structures sufficiently for a macrocell to provide service to UEs 115 located indoors. Communication using UHF waves can be associated with smaller antennas and a shorter range (e.g., less than 100 kilometers) compared to communication using the smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0115] The wireless communication system 100 may also operate in the very high frequency (SHF) region (also known as the centimeter band) using spectrum in the 3 GHz to 30 GHz range, or in the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices may be smaller and more closely spaced than UHF antennas. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to even greater attenuation and a shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory agency.
[0116] The wireless communication system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can employ license-assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands, such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using the unlicensed bands can be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using the unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.
[0117] A network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input, multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which 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 geographic locations. The network entity 105 may include an antenna array having a set of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications 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 panels may support RF beamforming for signals transmitted via the antenna ports.
[0118] The network entity 105 or the UE 115 may use MIMO communication to exploit multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.
[0119] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals communicated via the antenna elements can include the transmitting or receiving device applying an amplitude shift, a phase shift, or both to the signals carried by the antenna elements associated with the device. The adjustments associated with each of these antenna elements can be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other direction).
[0120] The network entity 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the network entity 105 along different directions. For example, the network entity 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as the network entity 105) or by a receiving device (such as the UE 115)) the beam direction for later transmission or reception by the network entity 105.
[0121] Some signals (such as data signals associated with a particular receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (e.g., receiving network entity 105 or receiving UE 115)). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals transmitted along one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.
[0122] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across the system bandwidth or one or more subbands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, or a port-selective codebook). Although these techniques are described with reference to signals sent by a network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques to send signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115) or to send signals in a single direction (e.g., to send data to a receiving device).
[0123] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array (e.g., different sets of directional listening weights), or processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when receiving data signals). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).
[0124] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly for communication via logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also support retransmission using error detection, error correction, or both to improve link efficiency. In the control plane, the RRC layer may provide for the establishment, configuration, and maintenance of RRC connections between the UE 115 and the network entity 105 or core network 130 for radio bearers supporting user plane data. The PHY layer may map transport channels to physical channels.
[0125] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correct data reception 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 can 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 same-slot HARQ feedback, in which case the device may provide HARQ feedback in a particular slot for data received via previous symbols in that slot. In other examples, the device may provide HARQ feedback in subsequent slots or based on some other time interval.
[0126] Wireless communication system 100 may support NTN communications between network nodes of wireless communication system 100. For example, wireless communication system 100 may be an example of an NTN that supports communications between NTN nodes and terrestrial network nodes. For example, as described herein, network entity 105 may refer to a terrestrial communication device (such as base station 140) or a non-terrestrial communication device (such as satellite 185, balloon, drone, non-terrestrial node 195, high altitude platform (HAP) station, or another non-terrestrial device). NTN network entity 105 may be connected to (e.g., communicate with) terrestrial network entity 105 via gateway 190. In some examples, NTN network entity 105 may correspond to a first cell type (e.g., an NTN cell type), and terrestrial network entity 105 may correspond to a second cell type (e.g., a terrestrial cell type) different from the first cell type.
[0127] In some examples, the NTN network entity 105 can provide coverage to areas where the terrestrial network entity 105 may not be available. The channel corresponding to the NTN network entity 105 can be characterized by a strong line-of-sight condition because the signal provided by the NTN network entity 105 can reflect off the sky (e.g., as opposed to a signal corresponding to the terrestrial network entity 105, which can travel on the ground). The coverage area of the beam radiated from the NTN network entity 105 can have relatively clear boundaries (e.g., compared to the terrestrial network entity 105 beam boundaries), and the UE 115 can operate within a single beam service area (e.g., except when the UE 115 is located at the boundary between two service areas). In some examples, the service area of the beam corresponding to the NTN network entity 105 can be larger than the service area of the beam corresponding to the terrestrial network entity 105.
[0128] The NTN network entity 105, such as the satellite 185, can move over time and support various coverage scenarios. For example, the NTN network entity 105 can support a mobile cell or beam coverage scenario, in which the cell coverage area or beam coverage area moves along with the satellite 185. Alternatively, the NTN network entity 105 can support a quasi-Earth-fixed cell or beam coverage scenario, in which the cell coverage area of the beam coverage area remains static for a certain period of time as the NTN network entity 105 moves through space.
[0129] Additionally or alternatively, the wireless communication system 100 may support one or more non-ground nodes 195. For the purposes of this disclosure, non-ground nodes 195 may include, but are not limited to, aircraft, UAVs, drones, HAPs, etc. For example, Figure 1 As shown, UE 115 may be communicatively coupled to satellite 185 (eg, NTN node), non-terrestrial node 195 , or both via one or more communication links 125 .
[0130] The network entity 105 may include a network entity communication manager 101 to 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.
[0131] NTNs can support both measurement-based and non-measurement-based handovers. For measurement-based handover, a wireless device, such as UE 115, accessing a cell provided by the NTN can perform measurements on different cells or beams (such as those transmitted by another non-terrestrial entity) to reselect another beam for handover. In some examples, UE 115 can perform measurements such as reference signal received power (RSRP) measurements, channel quality information (CQI) measurements, signal-to-noise ratio (SNR) measurements, and the like. For non-measurement-based handover, UE 115 or the NTN can select a new cell or beam for UE 115 without requiring UE 115 to provide measurement reports. In some examples, non-measurement-based handover can be based on, for example, positioning information of UE 115. In some examples, conditional handover can be an example of non-measurement-based or measurement-based handover, where, when one or more configured conditions are met, such as measurements of a first cell meeting a threshold (e.g., failing to exceed a threshold), UE 115 can perform a handover from the first cell to a second cell.
[0132] In some examples, the non-terrestrial entity providing the cell may be mobile, such as a satellite moving through space. Some wireless communication systems may provide a quasi-Earth-fixed beam or cell scenario, in which the coverage area of the beam or cell, such as the coverage area of the beam or cell, remains static on Earth for a specific amount of time while the non-terrestrial entity moves. For example, the non-terrestrial entity may adjust the projection angle of the coverage area so that the beam or cell coverage area covers the same location or area on Earth for a certain period of time. Additionally or alternatively, some wireless communication systems may support Earth-mobile or Earth-mobile beam or cell scenarios, in which the coverage area of the beam or cell moves on Earth along with the non-terrestrial entity.
[0133] In the case of a mobile cell scenario, network equipment at different locations in the cell coverage area may move out of the cell coverage at different timings. For example, a UE 115 accessing a cell in the middle of the cell coverage may be connected for a longer period of time than a UE 115 accessing a cell near the cell edge or when the cell is gradually disappearing. For example, the UE 115 may not move, but the cell (for example, provided by a satellite or NTN node) may move as the cell provider moves. Therefore, a UE 115 that is closer to the edge of the cell and is approaching the UE 115 may move out, exit, leave, or otherwise exceed the coverage of the cell in a shorter period of time than another UE 115 that is far away from the edge of the cell. In some examples, the UE 115 may be considered to have entered an area or region that is not covered by the cell or is covered by a different cell. If the UE 115 accesses the cell when the cell is gradually disappearing, the UE 115 may exceed the coverage before completing the measurement-based handover. However, even if the UE 115 cannot complete the measurement-based handover before leaving, exiting, or moving out of cell coverage, the non-terrestrial entity may still configure the UE 115 with measurement-based events and configurations for the measurement-based handover.
[0134] One or more aspects of the present disclosure relate to timing information indicating whether a UE 115 can complete a measurement-based handover before exiting the coverage area of a cell in an NTN. For example, when a UE 115 accesses a cell, the UE 115 may send an indication to the NTN that assists the NTN in determining a solution for supporting NTN mobility for the UE 115. For example, the NTN may determine whether there is sufficient time to perform a measurement-based handover for the UE 115 before the UE 115 exits the coverage area of the cell. In some examples, if the UE 115 does not have sufficient time to perform a measurement-based handover, the UE 115 may send an indication. If the UE 115 sends the indication, the UE 115 may be configured to perform a non-measurement-based handover in response. If the UE 115 has sufficient time to perform a measurement-based handover before leaving the coverage area of the cell, the NTN may configure the UE 115 to perform a measurement-based handover. In some examples, UE 115 may not send an indication if UE 115 has sufficient time to perform a measurement-based handover, or UE 115 may send an indication that UE 115 does have sufficient time to perform a measurement-based handover.
[0135] Figure 2An example network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) illustrating techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure 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 that may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a via one or more disaggregated network entities 105 (e.g., a near-RT RIC 175-b via an E2 link, a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both). The CUs 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DUs 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. A RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with a UE 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be simultaneously served by multiple RUs 170-a.
[0136] 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 transmit 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 the transmission medium. For example, these network entities 105 may include a wired interface configured to receive signals on the wired transmission medium or to transmit signals to one or more of the other network entities 105 over the 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 transmit signals over a wireless transmission medium to one or more of the other network entities 105, or both.
[0137] 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 using 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 units may communicate bidirectionally with the CU-CP units 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.
[0138] 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., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on functional partitioning, 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 using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.
[0139] 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 functionality or low PHY layer functionality (e.g., performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). 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 implementations, real-time and non-real-time aspects of control 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.
[0140] SMO 180-a can be configured to support RAN deployment and provisioning for both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, SMO 180-a can 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 can include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some implementations, SMO 180-a can communicate with components configured according to a 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an 01 interface.The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.
[0141] The non-RT RIC 175-a may be configured to include logic that enables 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 in communication 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 that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over 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).
[0142] In some examples, non-RT RIC 175-a may receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in near-RT RIC 175-b. This information may be utilized by near-RT RIC 175-b and may be received at SMO 180-a or non-RT RIC 175-a from a non-network data source or from a network function. In some examples, non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to execute corrective actions through SMO 180-a (e.g., via reconfiguration of O1) or through the generation of RAN management policies (such as A1 policies).
[0143] One or more aspects of the present disclosure relate to timing information indicating whether a UE 115, such as UE 115-a, can complete a measurement-based handover before exiting the coverage area of a cell in an NTN. For example, RU 170-a may be an example of an NTN node or NTN device, such as a satellite, that can provide a cell for UE 115-a, or examples of aspects thereof. When UE 115-a accesses a cell, UE 115-a may send an indication to the NTN that assists the NTN in determining a scheme for supporting NTN mobility for UE 115-a. In some examples, CU 160-a or DU 165-a may determine a scheme for supporting NTN mobility for UE 115-a. For example, the NTN (such as via CU 160-a or DU 165-a) may determine whether sufficient time exists to perform a measurement-based handover for UE 115-a before UE 115-a exits the coverage area of the cell. In some examples, if UE 115-a does not have sufficient time to perform a measurement-based handover, UE 115-a may send an indication. If UE 115-a sends an indication, in response, UE 115-a may be configured to perform a non-measurement-based handover. For example, RU 170-a may send control signaling to configure UE 115-a to perform a non-measurement-based handover. If UE 115-a has sufficient time to perform a measurement-based handover before leaving the coverage area of the cell, the NTN may configure UE 115-a to perform a measurement-based handover. For example, RU 170-a may send control signaling to configure UE 115-a to perform a measurement-based handover. In some examples, if UE 115-a has sufficient time to perform a measurement-based handover, UE 115-a may not send an indication, or UE 115-a may send an indication that UE 115-a does have sufficient time to perform a measurement-based handover.
[0144] Figure 3 An example of a wireless communication system 300 supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 may be implemented as shown in FIG. Figure 1 and Figure 2 Aspects of the described wireless communication system 100 or network architecture 200 or both may include these aspects. In some examples, the wireless communication system 300 may be an example of an NTN.
[0145] The wireless communication system 300 may include one or more NTN nodes 310, one or more non-terrestrial network entities 105-b, one or more UEs 115, or one or more terrestrial entities 105-a, or any combination thereof. An NTN node 310, such as NTN node 310-a, may include one or more of the following or aspects of one or more of the following: a satellite, a network entity 105 (such as a terrestrial network entity 105-a or a non-terrestrial network entity 105-b or both), a network device, or any combination thereof, each of which may be as described in reference Figure 1 and Figure 2 Similarly, NTN node 310-b may include one or more of the following or aspects of one or more of the following: a satellite, a network entity 105 (such as a terrestrial network entity 105-c or a non-terrestrial network entity 105-d or both), a network device, or any combination thereof, each of which may be as described in reference Figure 1 and 2 Examples of corresponding devices described. The wireless communication system 300 may include UE 115-b and UE 115-c, each of which may be as described in reference Figure 1 and Figure 2 An example of a UE 115 is described. The ground network entity 105-a may be as described in reference Figure 1 An example of a network node or network entity 105 is described.
[0146] In some examples, NTN node 310-a may include ground network entity 105-a and non-ground network entity 105-b. In some examples, ground network entity 105-a and non-ground network entity 105-b may communicate, such as via gateway 190-a. Ground network entity 105-c and non-ground network entity 105-d may also communicate via a gateway, such as gateway 190-b. Gateway 190-a and gateway 190-b may each be a gateway as described in reference Figure 110. In some examples, a UE 115 is described as being in communication with an NTN node 310-a. The UE 115 in communication with the NTN node 310-a may correspond to a UE 115 in communication with a terrestrial network entity 105-a, a non-terrestrial network entity 105-b, a satellite, a network device, or any combination thereof.
[0147] In some examples, the wireless communication system 300 may implement aspects of an earth-moving cell solution. In an earth-moving cell solution, a satellite, such as a non-terrestrial network entity 105-b, may project a cell coverage area 305-a onto the earth, and the cell coverage area 305-a may move with the satellite. For example, if the satellite moves from east to west, the cell coverage area 305-a projected onto the earth may move with the satellite from east to west. In another example, in an earth-moving cell solution, the satellite antenna may not be steerable. Figure 4 An example of an earth mobile cell solution is described in more detail.
[0148] In an Earth-mobile cell scenario, UEs 115 at different locations may move out of cell coverage at different times. For example, based on the direction of satellite movement, UE 115-b may be near the edge of cell coverage area 305-a, which is approaching UE 115-b. Based on the direction of satellite movement, UE 115-c may be closer to the edge of cell coverage area 305-a, which is moving away from UE 115-c. As a result, UE 115-b may leave cell coverage area 305-a before UE 115-c, or UE 115-c may remain in cell coverage longer than UE 115-b.
[0149] If UE 115 accesses cell coverage area 305-a while UE 115 is at the beginning of the cell, NTN node 310-a may configure measurement configurations for mobility support to UE 115. For example, if UE 115-c accesses a cell provided by NTN node 310-a, based on the positioning of UE 115-c within cell coverage area 305-a and the direction of movement of satellites, UE 115-c may be located in cell coverage area 305-a for a longer duration than UE 115-b. In some examples, NTN node 310-a may configure measurement configurations (such as measurement events) for mobility support (such as measurement-based handover) to UE 115-c. In some examples, UE 115-c may be configured to perform measurement-based handover to be handed over to a second cell provided by another NTN node 310, such as a cell having cell coverage 305-b provided by NTN node 310-b, another cell provided by NTN node 310-a, network entity 105, or another wireless device of the wireless communication system 300.
[0150] However, if UE 115 accesses cell coverage 305-a while the cell is fading, UE 115 may exceed the coverage of the serving cell before a measurement-based handover is performed. For example, if UE 115-b joins a cell provided by a satellite while located near the edge of cell coverage 305-a approaching UE 115-b, UE 115-b may not have sufficient time to perform a measurement-based handover before leaving cell coverage 305-a. The NTN may use other information to support mobility for UE 115-b, such as using the location of UE 115-b to hand over UE 115-b to another neighboring cell.
[0151] The measurement-based handover process may take a certain duration before the measurement-based handover is performed and UE 115 is handed over. In some examples, the duration may be based on the signaling delay for sending the measurement configuration or the measurement report, or both. Additionally or alternatively, the duration may be based on the time lag for UE 115 to detect that a measurement report event has been triggered. In some examples, very small aperture terminal (VSAT)-type NTN equipment may take a long time (e.g., approximately 1 second) to mechanically tune an antenna, antenna panel, antenna array, or dish antenna toward a neighboring cell for measurement.
[0152] Based on the time it takes to perform a measurement-based handover and the duration until UE 115-b leaves the cell coverage area, if UE 115-b is configured with a measurement-based event, UE 115-b may not even have an opportunity to perform a measurement-based handover before UE 115-b leaves the cell coverage area. Therefore, configuring UE 115-b with a measurement-based event may waste resources.
[0153] The wireless communication system 300 may support or implement techniques for NTN mobility to efficiently perform measurement-based handover or non-measurement-based handover for the UE 115. For example, the UE 115 may be configured to send an indication to the NTN node 310-a, where the indication assists the NTN node in determining an appropriate scheme for supporting NTN mobility for the UE 115, such as determining whether there is sufficient time to perform a measurement-based handover.
[0154] In some examples, UE 115 may send a message 320 indicating timing information based on a configuration received from NTN node 310-a. In some examples, the configuration may indicate a satellite type or an NTN cell type. For example, if the satellite provides an Earth mobile cell, UE 115 may send an indication, but if the satellite provides a quasi-Earth fixed cell, UE 115 may not send an indication.
[0155] In one example, NTN node 310-a may send an indication 315-a of coverage information to UE 115-b. In some examples, NTN node 310-a may send control signaling indicating a configuration including indication 315-a of coverage information. In some examples, indication 315-a of coverage information may indicate a satellite type or an NTN cell type of NTN node 310-a or a satellite of NTN node 310-a. Indication 315-a of coverage information may configure UE 115-b to report an indication when an estimated duration of time that UE 115-b remains within cell coverage area 305-a is insufficient to perform measurement-based handover or conditional handover.
[0156] Based on the indication 315-a of the coverage information, UE 115-b may estimate a duration of time to remain in coverage of the serving cell provided by the satellite. UE 115-b may determine that there is insufficient time for UE 115-b to perform a measurement-based handover before UE 115-b leaves the cell coverage area 305-a, and UE 115-b may send a message 320-a indicating timing information to NTN node 310-a. For example, message 320-a may indicate that there is insufficient time for UE 115-b to perform a measurement-based handover before leaving the cell coverage area.
[0157] Upon receiving an indication (e.g., message 320-a) from UE 115-b, the network may determine to support UE 115-b without using measurement-based handover. For example, NTN node 310-a may not transmit a measurement configuration to UE 115-b in cell coverage area 305-a, or NTN node 310-a may configure UE 115-b to perform a handover without a measurement report from UE 115-b (e.g., a conditional handover). For example, NTN node 310-a may send control signaling 325 to configure UE 115-b to perform a non-measurement-based handover or a handover without associated measurement reports (e.g., a conditional handover). In some examples, NTN node 310-a may configure UE 115-b to perform a non-measurement-based handover based on, for example, location information of UE 115-b. In some examples, geographic location information such as Global Positioning System (GPS) information may be an example of location information for UE 115 - b , which may be reported by UE 115 - b or determined by NTN node 310 - a .
[0158] In some examples, message 320 may include a UE recommendation not to use measurement-based handover for UE 115. For example, message 320-a may recommend not using measurement-based handover for UE 115-b. In some examples, message 320 may indicate an estimated duration of time that UE 115 will remain within the coverage of a serving cell (e.g., cell coverage area 305-a). In some examples, message 320 may indicate that the estimated duration of time for the UE is not long enough for measurement-based handover. In some examples, message 320 may indicate location information or positioning information for UE 115.
[0159] In another example, the NTN node 310-a may send an indication 315-b of coverage information to the UE 115-c. The UE 115-c may estimate the duration of time that the UE 115-c remains in coverage of the serving cell or cell coverage area 305-a and determine whether the estimated time duration is long enough for a measurement-based handover.
[0160] UE 115-c may determine that there is sufficient time for UE 115-c to perform a measurement-based handover before leaving cell coverage area 305-a. In some examples, UE 115-c may not send message 320-b indicating timing information. For example, the absence of message 320-b indicating timing information may indicate that UE 115-c has sufficient time to perform a measurement-based handover. After a window, opportunity, resource, or time span associated with UE 115-c sending message 320-b has elapsed, NTN node 310-a may determine that UE 115-c did not send message 320-b, and UE 115-c may perform a measurement-based handover before leaving cell coverage area 305-a.
[0161] In some other examples, UE 115-c may send message 320-b indicating timing information, and message 320-b may indicate that UE 115-c does have sufficient time to perform measurement-based handover. For example, UE 115-c may send message 320-b indicating a recommendation for UE 115-c to use measurement-based handover, or an indication that an estimated time duration is sufficient for UE 115-c to perform measurement-based handover before leaving cell coverage area 305-a.
[0162] Based on not receiving the indication, or receiving the indication that the UE 115-c can perform a measurement-based handover, the NTN node 310-a can send control signaling 330 to configure the UE 115-c for measurement-based handover. For example, the control signaling 330 can indicate or configure one or more measurement events for measurement-based reporting / handover to the UE 115-c. In some examples, the UE 115-c can be configured to perform measurement-based reporting or measurement-based handover to another cell provided by the NTN node 310-a, a different NTN node 310 (e.g., NTN node 310-b), or another network entity 105.
[0163] In some examples, NTN node 310-a may indicate a timing threshold. UE 115 may determine whether to send message 320 based on the timing threshold and the time duration until UE 115 leaves cell coverage area 305-a. For example, if the estimated time duration that UE 115 remains in coverage of the serving cell is less than the timing threshold, UE 115 may determine to send message 320 indicating that UE 115 does not have sufficient time to perform a measurement-based handover. In some examples, the network may determine the timing threshold based on an estimated minimum time duration for performing a measurement-based handover procedure. In some examples, UE 115 may estimate the time duration to remain in coverage of the serving cell (e.g., remain in cell coverage area 305-a) based at least on UE 115's location, satellite information (e.g., satellite ephemeris), a reference location of the cell or cell coverage area 305-a, a radius of the serving cell or cell coverage area 305-a, or any combination thereof. In some examples, ephemeris for a satellite may refer to a set of data or information associated with the position of a satellite at an associated epoch and the movement of the satellite (such as the satellite's trajectory or velocity), among other information. In some examples, UE 115 may implement a satellite motion propagator to predict or estimate the position of a satellite at a given time. In some examples, the timing threshold may be indicated along with indication of coverage information 315 or separately.
[0164] In some examples, UE 115 may determine whether to send message 320 based on a first estimated duration that UE 115 remains in cell coverage area 305-a and a second estimated duration that UE 115 performs measurement-based handover. For example, UE 115 may estimate both the first duration and the second duration, and UE 115 may determine whether to send message 320 based on the estimates. In some examples, UE 115 may estimate the second time duration associated with performing measurement-based handover based on parameters associated with the specific implementation of UE 115, such as the number of antennas, antenna panels, or antenna arrays in a VSAT UE (e.g., which may affect the time duration that UE 115 tunes to different neighboring cells). Additionally or alternatively, UE 115 may determine the second time duration associated with performing measurement-based handover based on one or more parameters that may affect signaling propagation delay, such as UE-to-satellite round-trip time.
[0165] In some examples, the NTN node 310-a may send one or more parameters associated with a network configuration for mobility, measurement, or handover to the UE 115. For example, the one or more parameters may include a synchronization signal block (SSB) measurement timing configuration (SMTC) periodicity, a measurement gap repetition period (MGRP), or both. The SMTC periodicity and / or the MGRP may affect the time duration for the UE 115 to detect that a measurement reporting event has been triggered. Accordingly, the UE 115 may consider the one or more parameters (e.g., associated with the network configuration and / or network implementation) and parameters of the UE 115 (e.g., the number of antennas at the UE 115) to estimate the time duration for the UE 115 to perform a measurement-based handover. For example, the UE 115 may estimate the time duration for the UE 115 to perform a measurement-based handover based on the SMTC periodicity, the MGRP, the number of antennas or antenna arrays at the UE 115, the type of antennas or antenna arrays at the UE 115, the RTT to the satellite, or any combination thereof.
[0166] The NTN node 310-a may indicate the timing threshold or any of the one or more parameters to the UE 115 via control signaling or system information signaling. For example, the timing threshold or any of the one or more parameters may be indicated via a SIB, an RRC message, a MAC control element or a MAC message, or any combination thereof. In some examples, the timing threshold or any of the one or more parameters, or both, may be indicated using or via an indication of coverage information 315.
[0167] In some examples, NTN node 310-a may indicate one or more parameters to UE 115 via existing signaling, and UE 115 may use the one or more parameters indicated via existing signaling to estimate the time duration until UE 115 leaves cell coverage area 305-a. For example, NTN node 310-a may indicate the one or more parameters via existing information elements in an RRC message or SIB message. In some examples, UE 115 may determine whether to send message 320 after UE 115 receives a measurement configuration, which may include one or more parameters that UE 115 may use to estimate the time duration until UE 115 needs to perform measurement-based handover. For example, the measurement configuration may indicate SMTC periodicity or MGRP, and UE 115 may estimate the time duration required for UE 115 to perform measurement-based handover based on the SMTC periodicity or MGRP indicated via the measurement configuration. In some examples, if UE 115 sends message 320 indicating that UE 115 does not have sufficient time to perform measurements, UE 115 may not perform the measurements configured by the measurement configuration.
[0168] In some examples, UE 115 may indicate information, such as location information of UE 115 or an estimated duration of time UE 115 will remain within cell coverage, to NTN node 310-a. UE 115 may indicate the information via message 320 or via a separate transmission. In some examples, UE 115 may indicate the information based on a first configuration (such as a configuration including indication 315 of cell coverage information) or based on a second, separate configuration. In one example, UE 115-b may send message 320-a indicating that UE 115-b does not have sufficient time to perform a measurement-based handover, and NTN node 310-a may send control signaling 325 configuring UE 115-b to perform a non-measurement-based handover or a handover without associated measurement reporting (e.g., a conditional handover). In response to control signaling 325, UE 115-b may send a second message indicating an estimated duration of time until UE 115-b leaves cell coverage or positioning information for UE 115-b.
[0169] In some examples, UE 115 may transmit a message 320 indicating timing information during or after a random access channel (RACH) procedure. For example, UE 115 may transmit message 320 to NTN node 310-a in message 3 or message 5 of the RACH procedure or in the next uplink message after UE 115 performs the RACH procedure. In some examples, UE 115 may transmit message 320 using a configured RACH preamble and / or a configured RACH opportunity. For example, NTN node 310-a may transmit an SIB indicating a RACH preamble and / or a RACH opportunity for message 320 indicating timing information, and UE 115 may transmit message 320 indicating timing information using the RACH preamble or RACH opportunity indicated by the SIB.
[0170] Figure 4 The example of the earth mobile cell scenario 400 and the quasi earth fixed cell scenario supporting the technology for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated. The earth mobile cell scenario 400 and the quasi earth fixed cell scenario can each be implemented as shown in FIG. Figures 1 to 3 Aspects of the described wireless communication system 100, network architecture 200, or wireless communication system 300. In some cases, the Earth mobile cell scenario 400 may be an example of a planetary mobile cell scenario, and the quasi-Earth fixed cell scenario may be an example of a quasi-planetary fixed cell scenario.
[0171] In some examples, a wireless communication system such as NTN may implement aspects of a mobile earth cell scenario 400. In the mobile earth cell scenario 400, a satellite 410-a may project a cell coverage area 405 onto the earth, and the cell coverage area 405 may move with the satellite 410-a. If the satellite 410-a moves from east to west, the cell coverage area 405 projected onto the earth may move from east to west with the satellite 410-a. For example, at a first time, the satellite 410-a may project the cell coverage area 405-a. As the satellite 410-a moves from left to right, the cell coverage area 405 of the cell of the satellite 410-a may also move from left to right. For example, at a second time, the satellite 410-a may have moved, and the satellite 410-a may project the cell coverage area 405-b at a different location.
[0172] For the quasi-Earth-fixed cell scenario 401, satellite 410-b may project a cell coverage area 405 that remains static for a specific duration of time. For example, at a first time, satellite 410-b may project cell coverage area 405-c. Even as satellite 410-b moves from left to right, satellite 410-b may adjust the direction of the projected coverage area, and cell coverage area 405-c may remain statically fixed to the same position on Earth. For example, at a first time, cell coverage area 405-c from satellite 410-b may be projected at angle 415-a, and at a second time, cell coverage area 405-c may be projected from satellite 410-b at angle 415-b. In some examples, satellite 410-b may change the position of cell coverage area 405-c after a certain period of time. For example, satellite 410-b may adjust the position of cell coverage area once satellite 410-b moves a configured distance from cell coverage area 405-c or the angle between cell coverage area 405-c and satellite 410-b meets a threshold.
[0173] The techniques described herein may support mobility for NTNs in an Earth-mobile cell scenario 400. For example, a UE may indicate to an NTN node, which may include a satellite 410, whether the UE has sufficient time to perform a measurement-based handover before leaving the cell coverage area 405-a or before the cell coverage area 405-a moves such that the UE is no longer covered by the cell. Additionally, some aspects may be implemented in a quasi-Earth-fixed cell scenario 401.
[0174] Figure 5 An example of a process flow 500 for supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 500 can implement or be implemented by aspects of the wireless communication system 100, the network architecture 200, the wireless communication system 300, the Earth mobile cell scenario 400, the Quasi Earth Fixed Cell scenario 401, or any combination thereof.
[0175] In some cases, process flow 500 may include UE 115-d, UE 115-e, and network device 505, which may be examples of corresponding devices as described herein. For example, UE 115-d and UE 115-e may each be a network device as described in reference Figures 1 to 4 The network device 505 may be an example of a UE 115 as described above. Figures 1 to 4 Examples of NTN nodes, non-terrestrial equipment, satellites, network entities 105 (such as non-terrestrial network entities or terrestrial network entities), or any combination thereof are described or include aspects thereof.
[0176] In some examples, the operations illustrated in process flow 500 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software or firmware), or any combination thereof. The following alternative examples may be implemented in which some steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not described below, or additional steps may be added.
[0177] At 510, network device 505 may transmit or output an indication of coverage information for a first cell associated with the NTN. The coverage information may indicate a coverage area for wireless communications supported by the first cell. In some examples, the first cell may be provided by an NTN node, such as a satellite. In some examples, when the estimated duration of time that the UE remains in coverage of the serving cell is insufficient to perform a measurement-based handover, network device 505 may transmit a configuration for UE 115 (e.g., UE 115-d or UE 115-e, or both) to report an indication. In some examples, when the estimated duration of time that the UE remains in coverage of the serving cell is insufficient to perform a measurement-based handover, network device 505 may transmit a configuration for UE 115 (e.g., UE 115-d or UE 115-e, or both) indicating fields, parameters, or content to be included in the reported indication.
[0178] UE 115-d may be an example of a UE 115 that does not have sufficient time to perform a measurement-based handover before leaving the coverage area supported by the first cell for wireless communication. At 515-a, UE 115-d may estimate a duration of time to stay in coverage of the serving cell, and UE 115-d may determine whether the estimated duration of time is long enough to complete the measurement-based handover.
[0179] At 525-a, UE 115-d may send a message indicating timing information associated with a measurement-based handover of the UE from the first cell to a second cell associated with the NTN. For example, UE 115-d may send a message indicating that there is insufficient time for UE 115-d to perform a measurement-based handover before UE 115-d leaves the coverage area of the first cell. In some examples, the message may indicate a recommendation for UE 115-d to perform a non-measurement-based handover, an indication that UE 115-d is unable to complete the measurement-based handover before leaving the coverage area of the first cell, an estimated duration of time associated with UE 115-d remaining in the coverage area of the first cell, a location of UE 115-d, or any combination thereof.
[0180] In some examples, UE 115-d may receive an indication of a timing threshold. UE 115-d may send a message at 525 based on a failure to meet the timing threshold for a duration of time associated with UE 115-d remaining within the coverage area supported by the first cell. For example, UE 115-d may estimate a duration of time to remain in cell coverage, and UE 115-d may determine that the estimated duration of time that UE 115-d will remain in cell coverage does not meet the indicated timing threshold.
[0181] In some examples, UE 115-d may receive an indication of one or more parameters associated with a measurement-based handover of the UE (e.g., from network device 505). UE 115-d may send the message at 525-a based on a first time duration associated with UE 115-d being within the coverage area supported by the first cell being less than a second time duration associated with UE 115-d performing the measurement-based handover.
[0182] In some examples, the first time duration may be based on location information of UE 115-d, ephemeris of a satellite associated with the first cell, a reference location of the first cell, a radius of the first cell, coverage information, or any combination thereof.
[0183] The second time duration may be based on one or more parameters associated with measurement-based handover, or UE characteristics associated with measurement-based handover, or any combination thereof. For example, the one or more parameters associated with measurement-based handover may include a measurement periodicity, a measurement gap repetition period, or both. The UE characteristics may include, for example, the number or characteristics of antennas or antenna arrays of UE 115-d, a round-trip time between UE 115-d and the first cell or the second cell, or both.
[0184] In some examples, UE 115-d may receive an indication of parameters for performing measurements for a measurement-based handover from a first cell to a second cell. In some examples, one or more parameters associated with the measurement-based handover may be based on the parameters for performing measurements for the measurement-based handover. For example, UE 115-d may receive a measurement configuration indicating a measurement periodicity or a measurement gap repetition period, and UE 115-d may estimate a time duration for performing the measurement-based handover based on the measurement periodicity or the measurement gap repetition period indicated by the measurement configuration.
[0185] The network device 505 may obtain or receive a message indicating the timing information from the UE 115-d. At 530, the network device 505 may send a configuration for a non-measurement-based handover in response to the message indicating the timing information. For example, upon receiving the indication from the UE 115-d, the network device 505 may decide to support the UE 115-d without using measurement-based handover. For example, the network device 505 may transmit the measurement configuration to the UE 115-d, or the network device 505 may configure the UE 115-d to perform a handover without a measurement report from the UE 115-d (e.g., a conditional handover).
[0186] UE 115-e may be an example of a UE 115 that does have sufficient time to perform a measurement-based handover before leaving the coverage area supported by the first cell for wireless communication. At 515-b, UE 115-e may estimate the duration of time remaining in the coverage of the serving cell, and UE 115-e may determine whether the estimated duration of time is long enough to complete the measurement-based handover. In some examples, similar to UE 115-e, UE 115-e may receive a configuration or parameter for determining whether UE 115-e has sufficient time to perform the measurement-based handover. For example, UE 115-e may receive an indication of a timing threshold, parameters associated with the measurement-based handover, measurement timing or periodicity, and the like.
[0187] In some examples, UE 115-e may refrain from sending a message indicating timing information to network device 505 at 520. For example, because UE 115-e has sufficient time to perform measurement handover, UE 115-e may not send a message indicating that UE 115-e cannot perform measurement handover in a timely manner.
[0188] At 535, UE 115-e may receive a handover command associated with a measurement-based handover for UE 115-e. In some examples, UE 115-e may receive the handover command after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and UE 115-e. For example, after a timing or window associated with the UE 115-e sending a message indicating timing information has elapsed, network device 505 may determine that UE 115-e may perform a measurement-based handover before UE 115-e leaves the coverage area of the cell. In some examples, after a RACH opportunity configured for UE 115-e to indicate timing information has elapsed, or after the UE completes its connection establishment procedure without an indication of timing information, network device 505 may determine that UE 115-e did not indicate timing information and, therefore, may complete the measurement-based handover in a timely manner. Based on determining that the UE 115 - e can perform measurement-based handover in a timely manner, the network device 505 may output or send a configuration for measurement-based handover or a handover command associated with measurement-based handover to the UE 115 - e.
[0189] In some examples, UE 115-e may send a message at 525-b to network device 505 indicating timing information associated with performing a measurement-based handover. For example, UE 115-e may send a message indicating that UE 115-e may perform a measurement-based handover before leaving the coverage area supported by the first cell. For example, UE 115-e may determine that UE 115-e may complete the measurement-based handover and be handed over to the second cell before UE 115-e moves within the coverage area of the cell such that UE 115-e is no longer within the coverage area of the cell.
[0190] Figure 6 Block diagram 600 illustrates a device 605 supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure. Device 605 may be an example of aspects of UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).
[0191] Receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies for NTN mobility with mobile cells). The information may be delivered to other components of device 605. Receiver 610 may utilize a single antenna or a collection of multiple antennas.
[0192] Transmitter 615 may provide means for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies for NTN mobility with mobile cells). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.
[0193] 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 the techniques for NTN mobility with mobile cells 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.
[0194] 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). 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 components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0195] Additionally or alternatively, in some examples, the communication manager 620, receiver 610, 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, receiver 610, 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 herein), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.
[0196] In some examples, communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 610, transmitter 615, or both. For example, communication manager 620 can receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.
[0197] According to examples disclosed herein, the communication manager 620 can support wireless communications at a UE. For example, the communication manager 620 can be configured to or otherwise support components for receiving an indication of coverage information for a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The communication manager 620 can be configured to or otherwise support components for sending a message indicating timing information associated with a measurement-based handover of the UE from the first cell to a second cell associated with the NTN based on the UE's location information and coverage information.
[0198] Additionally or alternatively, according to examples disclosed herein, the communication manager 620 may support wireless communications at the UE. For example, the communication manager 620 may be configured to or otherwise support means for receiving an indication of coverage information for a first cell associated with the NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The communication manager 620 may be configured to or otherwise support means for receiving a handover command associated with a measurement-based handover of the UE after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and the UE.
[0199] 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 more efficiently utilizing communication resources. For example, by indicating whether the UE 115 is able to complete a measurement-based handover before leaving the coverage area of a cell in the NTN, the network device or network node can determine whether to transmit signaling for configuring a measurement event for the measurement-based handover to the UE 115. If the UE 115 is unable to complete the measurement-based handover in a timely manner, the network device or network node may not configure the measurement event to the UE 115, thereby reducing overhead and improving resource availability.
[0200] Figure 7A block diagram 700 illustrates a device 705 supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure. 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).
[0201] Receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies for NTN mobility with mobile cells). The information may be delivered to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.
[0202] Transmitter 715 may provide means for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies for NTN mobility with mobile cells). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.
[0203] Device 705 or its various components may be examples of components for performing various aspects of the techniques for NTN mobility with mobile cells as described herein. For example, communications manager 720 may include coverage information indication component 725, timing information indication component 730, handover configuration component 735, or any combination thereof. Communications manager 720 may be an example of aspects of communications manager 620 as described herein. In some examples, communications manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 710, transmitter 715, or both. For example, communications manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated with receiver 710, transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.
[0204] According to examples disclosed herein, the communication manager 720 can support wireless communications at a UE. The coverage information indicating component 725 can be configured to or otherwise support means for receiving an indication of coverage information of a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The timing information indicating component 730 can be configured to or otherwise support means for sending a message indicating timing information associated with a measurement-based handover of the UE from the first cell to a second cell associated with the NTN based on the UE's location information and coverage information.
[0205] Additionally or alternatively, according to examples disclosed herein, the communication manager 720 can support wireless communications at the UE. The coverage information indicating component 725 can be configured to or otherwise support means for receiving an indication of coverage information of a first cell associated with the NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The handover configuration component 735 can be configured to or otherwise support means for receiving a handover command associated with a measurement-based handover of the UE after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and the UE.
[0206] Figure 8 Block diagram 800 illustrates a communications manager 820 supporting techniques for NTN mobility with mobile cells, according to one or more aspects of the present disclosure. Communications manager 820 may be an example of communications manager 620, communications manager 720, or aspects of both, as described herein. Communications manager 820 or its various components may be examples of components for performing various aspects of the techniques for NTN mobility with mobile cells, as described herein. For example, communications manager 820 may include a coverage information indication component 825, a timing information indication component 830, a handover configuration component 835, a non-measurement-based handover component 840, a timing information configuration component 845, a measurement-based handover component 850, or any combination thereof. Each of these components may communicate with one another, directly or indirectly (e.g., via one or more buses).
[0207] According to examples disclosed herein, a communication manager 820 can support wireless communications at a UE. A coverage information indicating component 825 can be configured to or otherwise support means for receiving an indication of coverage information of a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. A timing information indicating component 830 can be configured to or otherwise support means for sending a message indicating timing information associated with a measurement-based handover of the UE from the first cell to a second cell associated with the NTN based on location information and coverage information of the UE.
[0208] In some examples, non-measurement based handover component 840 may be configured or otherwise support means for receiving control signaling associated with a non-measurement based handover of a UE from a first cell to a second cell in response to a message indicating timing information.
[0209] In some examples, non-measurement based handover component 840 can be configured as or otherwise support means for performing a non-measurement based handover from a first cell to a second cell based on control signaling.
[0210] In some examples, timing information configuration component 845 can be configured or otherwise support means for receiving a configuration from the NTN for sending a message indicating timing information, the message indicating timing information being sent in response to the configuration received from the NTN.
[0211] In some examples, the configuration is associated with one of a satellite type or a non-terrestrial cell type for the first cell or the second cell or both.
[0212] In some examples, the timing information configuration component 845 may be configured as or otherwise support components for receiving an indication of a timing threshold, the message being sent based on a failure to satisfy the timing threshold for a duration of time associated with the UE remaining within the coverage area supported by the first cell.
[0213] In some examples, the time duration associated with the UE remaining within the coverage area supported by the first cell is based on the UE's location information, ephemeris of a satellite associated with the first cell, a reference location of the first cell, a radius of the first cell, coverage information, or any combination thereof.
[0214] In some examples, the message is sent based on a first time duration associated with the UE being within the coverage area supported by the first cell being less than a second time duration associated with a UE characteristic for measurement-based handover.
[0215] In some examples, the second time duration associated with the UE characteristic is based on the number or characteristics of the UE's antennas, the round-trip time between the UE and the first cell or the second cell, or any combination thereof.
[0216] In some examples, the timing information configuration component 845 may be configured as or otherwise support means for receiving an indication of one or more parameters associated with a measurement-based handover of the UE, the message being sent based on a first time duration associated with the UE being within a coverage area supported by the first cell being less than a second time duration associated with the UE performing the measurement-based handover, the second time duration being based on one or more parameters associated with the measurement-based handover or a UE characteristic associated with the measurement-based handover, or any combination of both.
[0217] In some examples, one or more parameters associated with measurement-based handover include measurement periodicity, measurement gap repetition period, or both.
[0218] In some examples, the indication of one or more parameters is sent via a SIB, an RRC message, a MAC message, or any combination thereof.
[0219] In some examples, the handover configuration component 835 may be configured as or otherwise support means for receiving an indication of parameters for performing measurements for a measurement-based handover from a first cell to a second cell, wherein one or more parameters associated with the measurement-based handover are based on the parameters for performing measurements for the measurement-based handover.
[0220] In some examples, to support sending messages, the timing information indication component 830 may be configured as or otherwise support components for sending messages indicating: a recommendation for the UE to perform measurement-based handover or non-measurement-based handover, the UE's inability to complete measurement-based handover before leaving the coverage area of the first cell, an estimated time duration associated with the UE remaining in the coverage area of the first cell, the UE's location, or any combination thereof.
[0221] In some examples, timing information configuration component 845 can be configured or otherwise support means for receiving from the NTN a configuration indicating one or more parameters of timing information or a granularity of the timing information, the timing information being based on the configuration received from the NTN.
[0222] In some examples, the message is sent via the third message or the fifth message of the random access procedure, an uplink message after the random access procedure, a random access preamble, a random access opportunity, or any combination thereof.
[0223] Additionally or alternatively, according to examples disclosed herein, the communication manager 820 can support wireless communications at the UE. In some examples, the coverage information indicating component 825 can be configured to or otherwise support means for receiving an indication of coverage information of a first cell associated with the NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The handover configuration component 835 can be configured to or otherwise support means for receiving a handover command associated with a measurement-based handover of the UE after a timing associated with a time resource allocated for sending an indication of a time estimate associated with a connection between the first cell and the UE.
[0224] In some examples, timing information indicating component 830 may be configured as or otherwise support means for sending a message indicating timing information associated with a measurement-based handover from a first cell to a second cell associated with an NTN based on location information and coverage information of the UE.
[0225] In some examples, the message indicates that the UE may perform a measurement-based handover before leaving the coverage area supported by the first cell.
[0226] In some examples, measurement-based handover component 850 can be configured or otherwise support means for performing a measurement-based handover from a first cell to a second cell based on a handover command.
[0227] In some examples, the timing information configuration component 845 may be configured as or otherwise support means for receiving an indication of a timing threshold, the handover command being received based on the UE remaining within the coverage area supported by the first cell for a duration of time satisfying the timing threshold.
[0228] In some examples, the time duration associated with the UE remaining within the coverage area supported by the first cell is based on the UE's location information, ephemeris of a satellite associated with the first cell, a reference location of the first cell, a radius of the first cell, coverage information, or any combination thereof.
[0229] In some examples, the handover command is received based on a first time duration associated with the UE being within the coverage area supported by the first cell being greater than a second time duration associated with a UE characteristic for measurement-based handover.
[0230] In some examples, the second time duration associated with the UE characteristic is based on the number or characteristics of the UE's antennas, the round trip time between the UE and the first cell or the second cell associated with the handover command, or any combination thereof.
[0231] In some examples, the timing information configuration component 845 may be configured as or otherwise support means for receiving an indication of one or more parameters associated with measurement-based handover, the handover command being received based on a first time duration associated with the UE being within a coverage area supported by the first cell being greater than a second time duration associated with the UE performing the measurement-based handover, the second time duration being based on one or more parameters associated with the measurement-based handover or a UE characteristic associated with the measurement-based handover, or any combination of both.
[0232] Figure 9 A diagram illustrates a system 900 including a device 905 supporting techniques for NTN mobility with mobile cells, according to one or more aspects of the present disclosure. Device 905 may be an example of, or include components of, device 605, device 705, or UE 115 as described herein. Device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 905 may include components for two-way voice and data communication, 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, memory 930, code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 945).
[0233] I / O controller 910 can manage input and output signals for 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.
[0234] 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 capable of concurrently transmitting or receiving multiple wireless transmissions. 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 the one or more antennas 925 for transmission; and demodulating packets received from the one or more antennas 925. The transceiver 915, or the transceiver 915 and the one or more antennas 925, may be examples of the transmitter 615, the transmitter 715, the receiver 610, the receiver 710, or any combination thereof, or components thereof, as described herein.
[0235] 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 the various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium such as 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, the memory 930 may also contain, among other things, a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.
[0236] 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, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 940 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 940. Processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause device 905 to perform various functions (e.g., functions or tasks supporting technologies for NTN mobility with mobile cells). For example, device 905 or a component of device 905 may include processor 940 and memory 930 coupled to or coupled to processor 940, with processor 940 and memory 930 configured to perform the various functions described herein.
[0237] According to examples disclosed herein, the communication manager 920 can support wireless communications at a UE. For example, the communication manager 920 can be configured to or otherwise support components for receiving an indication of coverage information for a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The communication manager 920 can be configured to or otherwise support components for sending a message indicating timing information associated with a measurement-based handover of the UE from the first cell to a second cell associated with the NTN based on the UE's location information and coverage information.
[0238] Additionally or alternatively, according to examples disclosed herein, the communication manager 920 may support wireless communications at the UE. For example, the communication manager 920 may be configured to or otherwise support means for receiving an indication of coverage information for a first cell associated with the NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The communication manager 920 may be configured to or otherwise support means for receiving a handover command associated with a measurement-based handover of the UE after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and the UE.
[0239] By including or configuring the communication manager 920 according to the examples described herein, the device 905 can support techniques for more efficiently utilizing communication resources. For example, by indicating whether the UE 115 can complete a measurement-based handover before leaving the coverage area of a cell in the NTN, the network device or network node can determine whether to transmit signaling for configuring a measurement event for the measurement-based handover to the UE 115. If the UE 115 cannot complete the measurement-based handover in a timely manner, the network device or network node may not configure the measurement event to the UE 115, thereby reducing overhead and improving resource availability. Additionally, these techniques can improve communication reliability and reduce service interruption time by utilizing efficient mobility schemes (e.g., measurement-based handover or non-measurement-based handover) based on whether the UE 115 can perform the measurement-based handover in a timely manner.
[0240] In some examples, the communication manager 920 can be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise coordinating with the transceiver 915, one or more antennas 925, or any combination thereof. 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 can be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 can include instructions executable by the processor 940 to cause the device 905 to perform various aspects of the techniques for NTN mobility with mobile cells as described herein, or the processor 940 and the memory 930 can be otherwise configured to perform or support such operations.
[0241] Figure 10 Block diagram 1000 illustrates a device 1005 supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure. Device 1005 may be an example of aspects of a network entity 105 as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).
[0242] 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 device 1005. In some examples, receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, 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.
[0243] Transmitter 1015 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, 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, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 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, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.
[0244] 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 the techniques for NTN mobility with mobile cells 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.
[0245] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in this disclosure. In some examples, the processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0246] 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., a DSP, a CPU, an ASIC, an FPGA, a microcontroller), or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting components for performing the functions described herein).
[0247] In some examples, communication manager 1020 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 can receive information from receiver 1010, transmit information to transmitter 1015, or be integrated with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.
[0248] According to examples disclosed herein, the communication manager 1020 can support wireless communications at a network device. For example, the communication manager 1020 can be configured to or otherwise support components for outputting an indication of coverage information for a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The communication manager 1020 can be configured to or otherwise support components for monitoring a message indicating timing information associated with a measurement-based handover from the first cell to a second cell associated with the NTN.
[0249] By including or configuring the communication manager 1020 according to the examples described herein, device 1005 (e.g., a processor controlling receiver 1010, transmitter 1015, communication manager 1020, or a combination thereof or otherwise coupled thereto) may support techniques for more efficient utilization of communication resources. For example, by indicating whether UE 115 is able to complete a measurement-based handover before leaving the coverage area of a cell in an NTN, a network device or network node may determine whether to transmit signaling for configuring a measurement event for measurement-based handover to UE 115. If UE 115 is unable to complete the measurement-based handover in a timely manner, the network device or network node may not configure the measurement event to UE 115, thereby reducing overhead and improving resource availability. Additionally, these techniques may improve communication reliability and reduce service interruption time by utilizing efficient mobility schemes (e.g., measurement-based handover or non-measurement-based handover) based on whether UE 115 is able to perform a measurement-based handover in a timely manner.
[0250] Figure 11 Block diagram 1100 illustrates a device 1105 supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure. Device 1105 may be an example of aspects of device 1005 or network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).
[0251] 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 device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, 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.
[0252] Transmitter 1115 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, 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, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, 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, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.
[0253] Device 1105 or its various components may be examples of components for performing various aspects of the techniques for NTN mobility with mobile cells as described herein. For example, communications manager 1120 may include coverage information indication component 1125, timing information indication component 1130, or any combination thereof. Communications manager 1120 may be examples of aspects of communications manager 1020 as described herein. In some examples, communications manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 1110, transmitter 1115, or both. For example, communications manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.
[0254] According to examples disclosed herein, a communication manager 1120 can support wireless communications at a network device. A coverage information indicating component 1125 can be configured to or otherwise support means for outputting an indication of coverage information for a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. A timing information indicating component 1130 can be configured to or otherwise support means for monitoring a message indicating timing information associated with a measurement-based handover from the first cell to a second cell associated with the NTN.
[0255] Figure 12 Block diagram 1200 illustrates a communications manager 1220 supporting techniques for NTN mobility with mobile cells, according to one or more aspects of the present disclosure. Communications manager 1220 may be an example of aspects of communications manager 1020, communications manager 1120, or both, as described herein. Communications manager 1220 or its various components may be examples of means for performing various aspects of the techniques for NTN mobility with mobile cells, as described herein. For example, communications manager 1220 may include a coverage information indication component 1225, a timing information indication component 1230, a handover configuration component 1235, a timing information configuration component 1240, or any combination thereof. Each of these components may communicate with one another directly or indirectly (e.g., via one or more buses). This communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualized component associated with network entity 105, or between devices, components, or virtualized components associated with network entity 105), or any combination thereof.
[0256] According to examples disclosed herein, a communication manager 1220 can support wireless communications at a network device. A coverage information indicating component 1225 can be configured to or otherwise support means for outputting an indication of coverage information for a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. A timing information indicating component 1230 can be configured to or otherwise support means for monitoring a message indicating timing information associated with a measurement-based handover from the first cell to a second cell associated with the NTN.
[0257] In some examples, to support monitoring messages, timing information indicating component 1230 can be configured or otherwise support means for obtaining a message indicating timing information associated with a measurement-based handover from a first cell to a second cell associated with an NTN.
[0258] In some examples, handover configuration component 1235 may be configured to or otherwise support means for outputting control signaling associated with a non-measurement-based handover from a first cell to a second cell in response to a message indicating timing information.
[0259] In some examples, timing information configuration component 1240 can be configured or otherwise support means for outputting a configuration for sending a message indicating timing information, the message indicating timing information being received based on the configuration.
[0260] In some examples, the configuration is associated with one of a satellite type or a non-terrestrial cell type for the first cell or the second cell or both.
[0261] In some examples, timing information configuration component 1240 may be configured as or otherwise support means for outputting an indication of a timing threshold, the message indicating that a duration of time associated with remaining within the coverage area supported by the first cell failed to meet the timing threshold.
[0262] In some examples, the message indicates that a first time duration associated with being within a coverage area supported by the first cell is less than a second time duration associated with a wireless device characteristic for measurement-based handover.
[0263] In some examples, timing information configuration component 1240 may be configured as or otherwise support means for outputting an indication of one or more parameters associated with measurement-based handover, the message indicating that a first time duration associated with being within a coverage area supported by the first cell is less than a second time duration associated with the wireless device performing measurement-based handover, the second time duration being based on either or both of the one or more parameters associated with measurement-based handover, a wireless device characteristic associated with measurement-based handover.
[0264] In some examples, one or more parameters associated with measurement-based handover include measurement periodicity, measurement gap repetition period, or both.
[0265] In some examples, the message indicates a recommendation for measurement-based handover or non-measurement-based handover, an inability of the wireless device to complete a measurement-based handover before leaving the coverage area of the first cell, an estimated duration of time associated with the wireless device remaining in the coverage area of the first cell, a location of the wireless device, or any combination thereof.
[0266] In some examples, timing information configuration component 1240 can be configured as or otherwise support means for outputting a configuration indicating one or more parameters of timing information or a granularity of timing information based on the configuration.
[0267] In some examples, the message is obtained via the third message or the fifth message of the random access procedure, an uplink message after the random access procedure, a random access preamble, a random access opportunity, or any combination thereof.
[0268] In some examples, the message indicates that the wireless device may perform a measurement-based handover before leaving the coverage area supported by the first cell.
[0269] In some examples, the message indicates that the wireless device cannot perform a measurement-based handover before leaving a coverage area supported by the first cell.
[0270] In some examples, handover configuration component 1235 may be configured as or otherwise support components for outputting a handover command associated with measurement-based handover of the wireless device after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and the wireless device.
[0271] In some examples, the indication of coverage information is sent via a SIB, an RRC message, a MAC message, or any combination thereof.
[0272] In some examples, handover configuration component 1235 may be configured as or otherwise support means for outputting an indication of one or more parameters for performing measurements for a measurement-based handover from a first cell to a second cell, the message being received in response to the indication of the one or more parameters.
[0273] In some examples, timing information indication component 1230 may be configured to or otherwise support components for obtaining a second message indicating a recommendation to perform a measurement-based handover or a non-measurement-based handover, an indication of whether a measurement-based handover can be completed before the wireless device leaves the coverage area of the first cell, an estimated duration of time associated with the wireless device remaining in the coverage area of the first cell, a location of the wireless device, or any combination thereof.
[0274] Figure 13A diagram illustrates a system 1300 including a device 1305 supporting techniques for NTN mobility with mobile cells, in accordance with one or more aspects of the present disclosure. Device 1305 may be an example of, or include components of, device 1005, device 1105, or network entity 105, as described herein. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof. This communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1305 may include components that support outgoing and incoming communications, such as a communications manager 1320, a transceiver 1310, an antenna 1315, memory 1325, code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1340).
[0275] The transceiver 1310 may support bidirectional communication as described herein via a wired link, a wireless link, or both. 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 transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 may also include a modem to: modulate a signal; provide the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receive the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulate the signal. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335 or memory 1325 or both) may be included in a chip or chip assembly installed in the device 1305. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125 , backhaul communication link 120 , midhaul communication link 162 , fronthaul communication link 168 ).
[0276] 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 the 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, memory 1325 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0277] 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, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1335 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1335. Processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) to cause device 1305 to perform various functions (e.g., functions or tasks supporting technologies for NTN mobility with mobile cells). For example, device 1305 or a component of device 1305 may include processor 1335 and memory 1325 coupled to processor 1335, with processor 1335 and memory 1325 configured to perform the 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 can host functionality for performing the functions of device 1305 (e.g., by executing code 1330). Processor 1335 may be any suitable processor or processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within memory 1325). In some implementations, processor 1335 may be a component of a processing system. A processing system generally refers to a system or series of machines or components that receives inputs and processes those inputs to produce a set of outputs (which may be passed to other systems or components of device 1305, for example). For example, a processing system of device 1305 may refer to a system that includes various other components or subcomponents of device 1305 (such as processor 1335, transceiver 1310, communications manager 1320, or other components or combinations of components of device 1305). The processing system of device 1305 can interface with other components of device 1305 and can process information (such as input or signals) received from other components or output information to other components. For example, a chip or modem of device 1305 may include a processing system and one or more interfaces for outputting information, receiving information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to receive information, or the same interface configured to output and receive information, among other implementations. In some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, allowing device 1305 to transmit information output from the chip or modem. Additionally or alternatively, in some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, allowing device 1305 to receive information or signal input and pass this information to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.
[0278] In some examples, bus 1340 may support communications for protocol layers of a protocol stack (e.g., within a 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 components 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 in which 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).
[0279] In some examples, communication manager 1320 can manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1320 can manage the delivery of data communications to client devices, such as one or more UEs 115. In some examples, communication manager 1320 can manage communications with other network entities 105 and can include a controller or scheduler for controlling communications with UEs 115 in coordination with other network entities 105. In some examples, communication manager 1320 can support an X2 interface within LTE / LTE-A wireless communication network technology to provide communications between network entities 105.
[0280] According to examples disclosed herein, the communication manager 1320 can support wireless communications at a network device. For example, the communication manager 1320 can be configured to or otherwise support components for outputting an indication of coverage information for a first cell associated with an NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The communication manager 1320 can be configured to or otherwise support components for monitoring a message indicating timing information associated with a measurement-based handover from the first cell to a second cell associated with the NTN.
[0281] By including or configuring communication manager 1320 according to the examples described herein, device 1305 can support techniques for more efficiently utilizing communication resources. For example, by indicating whether UE 115 can complete a measurement-based handover before leaving the coverage area of a cell in the NTN, a network device or network node can determine whether to transmit signaling for configuring a measurement event for measurement-based handover to UE 115. If UE 115 is unable to complete the measurement-based handover in a timely manner, the network device or network node may not configure the measurement event to UE 115, thereby reducing overhead and improving resource availability. Additionally, these techniques can improve communication reliability and reduce service interruption time by utilizing efficient mobility schemes (e.g., measurement-based handover or non-measurement-based handover) based on whether UE 115 can perform a measurement-based handover in a timely manner.
[0282] In some examples, the communication manager 1320 can be configured to perform various operations (e.g., receive, acquire, monitor, output, transmit) using or otherwise coordinating 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 can be supported or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof. For example, the code 1330 can include instructions executable by the processor 1335 to cause the device 1305 to perform various aspects of the techniques for NTN mobility with mobile cells as described herein, or the processor 1335 and the memory 1325 can be otherwise configured to perform or support such operations.
[0283] Figure 14 A flow chart illustrating a method 1400 for supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated. The operations of the method 1400 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The described functions may be performed by the UE 115. 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.
[0284] At 1405, the method may include receiving an indication of coverage information for a first cell associated with the NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication. 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 as described in reference to Figure 8The described coverage information instructs component 825 to execute.
[0285] At 1410, the method may include sending a message indicating timing information associated with a measurement-based handover of the UE from a first cell to a second cell associated with the NTN based on the location information and coverage information of the UE. 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 described timing information instructs component 830 to execute.
[0286] Figure 15 A flow chart illustrating a method 1500 for supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated. The operations of the method 1500 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The described functions may be performed by the UE 115. 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.
[0287] At 1505, the method may include receiving an indication of coverage information for a first cell associated with the NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The described coverage information instructs component 825 to execute.
[0288] At 1510, the method may include sending a message indicating timing information associated with a measurement-based handover of the UE from a first cell to a second cell associated with the NTN based on the location information and coverage information of the UE. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The described timing information instructs component 830 to execute.
[0289] At 1515, the method may include receiving control signaling associated with a non-measurement-based handover of the UE from the first cell to the second cell in response to the message indicating the timing information. 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 as described in reference to Figure 8 The described non-measurement based handover component 840 is performed.
[0290] Figure 16A flow chart illustrating a method 1600 for supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated. The operations of the method 1600 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The described functions may be performed by the UE 115. 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.
[0291] At 1605, the method may include receiving an indication of coverage information for a first cell associated with the NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 8 The described coverage information instructs component 825 to execute.
[0292] At 1610, the method may include receiving a configuration from the NTN for sending a message indicating timing information, the message indicating timing information being sent in response to the configuration received from the NTN. The operations of 1610 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1610 may be implemented as described in reference to Figure 8 The described timing information configures component 845 to execute.
[0293] At 1615, the method may include sending a message indicating timing information associated with a measurement-based handover of the UE from the first cell to the second cell associated with the NTN based on the location information and coverage information of the UE. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 8 The described timing information instructs component 830 to execute.
[0294] Figure 17 A flowchart illustrating a method 1700 for supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated. The operations of the method 1700 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The described functions may be performed by the UE 115. 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.
[0295] At 1705, the method may include receiving an indication of coverage information of a first cell associated with the NTN, the coverage information indicating a coverage area supported by the first cell for wireless communication. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figure 8 The described coverage information instructs component 825 to execute.
[0296] At 1710, the method may include receiving a handover command associated with a measurement-based handover of the UE after a timing associated with a time resource allocated for sending an indication of a time estimate associated with a connection between the first cell and the UE. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Figure 8 The described handover configuration component 835 is performed.
[0297] Figure 18 A flow chart illustrating a method 1800 for supporting techniques for NTN mobility with mobile cells according to one or more aspects of the present disclosure is illustrated. The operations of the method 1800 may be implemented by a network entity or component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 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.
[0298] At 1805, the method may include outputting an indication of coverage information for a first cell associated with the NTN, the coverage information indicating a coverage area supported by the first cell for wireless communications. The operations of 1805 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Figure 12 The described coverage information instructs component 1225 to execute.
[0299] At 1810, the method may include monitoring for a message indicating timing information associated with a measurement-based handover from a first cell to a second cell associated with an NTN. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Figure 12 The described timing information instructs component 1230 to execute.
[0300] The following provides an overview of various aspects of the disclosure:
[0301] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving an indication of coverage information of a first cell associated with a non-terrestrial network, the coverage information indicating a coverage area for wireless communication supported by the first cell; and sending a message indicating timing information associated with measurement-based handover of the UE from the first cell to a second cell associated with the non-terrestrial network based at least in part on location information of the UE and the coverage information.
[0302] Aspect 2: The method according to aspect 1, further comprising: receiving control signaling associated with a non-measurement-based handover of the UE from the first cell to the second cell in response to the message indicating the timing information.
[0303] Aspect 3: The method according to aspect 2, further comprising: performing the non-measurement based handover from the first cell to the second cell based at least in part on the control signaling.
[0304] Aspect 4: According to the method described in any one of Aspects 1 to 3, the method further includes: receiving a configuration for sending the message indicating the timing information from the non-terrestrial network, and the message indicating the timing information is sent in response to the configuration received from the non-terrestrial network.
[0305] Aspect 5: The method of aspect 4, wherein the configuration is associated with one of a satellite type or a non-terrestrial cell type of the first cell or the second cell or both.
[0306] Aspect 6: According to any one of Aspects 1 to 5, the method also includes: receiving an indication of a timing threshold, the message being sent at least in part based on the time duration associated with the UE remaining within the coverage area supported by the first cell failing to meet the timing threshold.
[0307] Aspect 7: A method according to Aspect 6, wherein the time duration associated with the UE remaining within the coverage area supported by the first cell is at least partially based on the position information of the UE, the ephemeris of the satellite associated with the first cell, the reference position of the first cell, the radius of the first cell, the coverage information, or any combination thereof.
[0308] Aspect 8: A method according to any one of Aspects 1 to 7, wherein the message is sent at least in part based on a first time duration associated with the UE being within the coverage area supported by the first cell being less than a second time duration, the second time duration being associated with UE characteristics for the measurement-based handover.
[0309] Aspect 9: The method according to aspect 8, wherein the second time duration associated with the UE characteristic is based at least in part on the number or characteristics of antennas of the UE, the round-trip time between the UE and the first cell or the second cell, or any combination thereof.
[0310] Aspect 10: According to any one of Aspects 1 to 9, the method further includes: receiving an indication of one or more parameters associated with the measurement-based handover of the UE, the message being sent at least in part based on a first time duration associated with the UE being within the coverage area supported by the first cell being less than a second time duration associated with the UE performing the measurement-based handover, the second time duration being at least in part based on the one or more parameters associated with the measurement-based handover or UE characteristics associated with the measurement-based handover or any combination of the two.
[0311] Aspect 11: The method according to aspect 10, wherein the one or more parameters associated with the measurement-based handover include measurement periodicity, measurement gap repetition period, or both.
[0312] Aspect 12: The method according to any one of aspects 10 to 11, wherein the indication of the one or more parameters is received via a system information block, a radio resource control message, a medium access control message, or any combination thereof.
[0313] Aspect 13: According to any one of Aspects 10 to 12, the method further includes: receiving an indication of parameters for performing measurements for the measurement-based handover from the first cell to the second cell, the one or more parameters associated with the measurement-based handover being at least partially based on the parameters for performing the measurements for the measurement-based handover.
[0314] Aspect 14: A method according to any one of Aspects 1 to 13, wherein sending the message includes: sending the message indicating the following: a recommendation for the UE to perform one of the measurement-based handover or the non-measurement-based handover, whether the UE can complete the measurement-based handover before leaving the coverage area of the first cell, an estimated time duration associated with the UE remaining in the coverage area of the first cell, the positioning of the UE, or any combination thereof.
[0315] Aspect 15: According to the method of Aspect 14, the method also includes: receiving a configuration indicating one or more parameters of the timing information or the granularity of the timing information from the non-terrestrial network, and the timing information is at least partially based on the configuration received from the non-terrestrial network.
[0316] Aspect 16: A method according to any one of aspects 1 to 15, wherein the message is sent via the third message or the fifth message of the random access procedure, an uplink message after the random access procedure, a random access preamble, a random access opportunity, or any combination thereof.
[0317] Aspect 17: A method for wireless communication at a UE, the method comprising: receiving an indication of coverage information of a first cell associated with a non-terrestrial network, the coverage information indicating a coverage area for wireless communication supported by the first cell; and receiving a handover command associated with a measurement-based handover of the UE after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and the UE.
[0318] Aspect 18: The method according to aspect 17 further includes: sending a message indicating timing information associated with the measurement-based handover from the first cell to the second cell associated with the non-terrestrial network based at least in part on the location information of the UE and the coverage information.
[0319] Aspect 19: The method of aspect 18, wherein the message indicates that the UE may perform the measurement-based handover before leaving the coverage area supported by the first cell.
[0320] Aspect 20: The method according to any one of aspects 17 to 19, further comprising: performing the measurement-based handover from the first cell to the second cell based at least in part on the handover command.
[0321] Aspect 21: The method according to any one of Aspects 17 to 20, further comprising: receiving an indication of a timing threshold, the handover command being received at least in part based on the time duration associated with the UE remaining within the coverage area supported by the first cell satisfying the timing threshold.
[0322] Aspect 22: A method according to Aspect 21, wherein the time duration associated with the UE remaining within the coverage area supported by the first cell is at least partially based on the location information of the UE, the ephemeris of the satellite associated with the first cell, the reference position of the first cell, the radius of the first cell, the coverage information, or any combination thereof.
[0323] Aspect 23: A method according to any one of Aspects 17 to 22, wherein the handover command is received at least in part based on a first time duration associated with the UE being within the coverage area supported by the first cell being greater than a second time duration associated with the UE characteristics for the measurement-based handover.
[0324] Aspect 24: A method according to Aspect 23, wherein the second time duration associated with the UE characteristic is based at least in part on the number or characteristics of antennas of the UE, the round-trip time between the UE and the first cell or the second cell associated with the handover command, or any combination thereof.
[0325] Aspect 25: According to any one of Aspects 17 to 24, the method further includes: receiving an indication of one or more parameters associated with the measurement-based handover, the handover command being received at least in part based on a first time duration associated with the UE being within the coverage area supported by the first cell being greater than a second time duration associated with the UE performing the measurement-based handover, the second time duration being at least in part based on the one or more parameters associated with the measurement-based handover or UE characteristics associated with the measurement-based handover or any combination of the two.
[0326] Aspect 26: A method for wireless communication at a network device, the method comprising: outputting an indication of coverage information of a first cell associated with a non-terrestrial network, the coverage information indicating a coverage area for wireless communication supported by the first cell; and monitoring a message indicating timing information associated with a measurement-based handover from the first cell to a second cell associated with the non-terrestrial network.
[0327] Aspect 27: The method of aspect 26, wherein monitoring the message comprises obtaining the message indicating the timing information associated with the measurement-based handover from the first cell to the second cell associated with the non-terrestrial network.
[0328] Aspect 28: The method according to aspect 27, further comprising: outputting control signaling associated with a non-measurement based handover from the first cell to the second cell in response to the message indicating the timing information.
[0329] Aspect 29: The method according to any one of aspects 27 to 28, further comprising: outputting a configuration for sending the message indicating the timing information, the message indicating the timing information being received based at least in part on the configuration.
[0330] Aspect 30: The method of aspect 29, wherein the configuration is associated with one of a satellite type or a non-terrestrial cell type of the first cell or the second cell or both.
[0331] Aspect 31: The method according to any one of aspects 27 to 30, further comprising: outputting an indication of a timing threshold, the message indicating that a time duration associated with remaining within the coverage area supported by the first cell fails to meet the timing threshold.
[0332] Aspect 32: A method according to any one of Aspects 27 to 31, wherein the message indicates that a first time duration associated with being within the coverage area supported by the first cell is less than a second time duration, and the second time duration is associated with a wireless device characteristic for the measurement-based handover.
[0333] Aspect 33: According to any one of Aspects 27 to 32, the method further includes: outputting an indication of one or more parameters associated with the measurement-based handover, the message indicating that a first time duration associated with being within the coverage area supported by the first cell is less than a second time duration associated with the wireless device performing the measurement-based handover, the second time duration being at least partially based on either or both of the one or more parameters associated with the measurement-based handover and the wireless device characteristics associated with the measurement-based handover.
[0334] Aspect 34: The method according to aspect 33, wherein the one or more parameters associated with the measurement-based handover include measurement periodicity, measurement gap repetition period, or both.
[0335] Aspect 35: A method according to any one of Aspects 27 to 34, wherein the message indicates a recommendation for the measurement-based handover or the non-measurement-based handover, the inability of the wireless device to complete the measurement-based handover before leaving the coverage area of the first cell, an estimated time duration associated with the wireless device remaining in the coverage area of the first cell, the positioning of the wireless device, or any combination thereof.
[0336] Aspect 36: The method according to aspect 35, further comprising: outputting a configuration indicating one or more parameters of the timing information or a granularity of the timing information, the timing information being based at least in part on the configuration.
[0337] Aspect 37: A method according to any one of Aspects 27 to 36, wherein the message is obtained via a third message or a fifth message of a random access procedure, an uplink message after the random access procedure, a random access preamble, a random access opportunity, or any combination thereof.
[0338] Aspect 38: The method of any one of aspects 27 to 37, wherein the message indicates that the wireless device may perform the measurement-based handover before leaving the coverage area supported by the first cell.
[0339] Aspect 39: The method of any one of aspects 27 to 38, wherein the message indicates that the wireless device cannot perform the measurement-based handover before leaving the coverage area supported by the first cell.
[0340] Aspect 40: A method according to any one of Aspects 26 to 39, the method further comprising: receiving a handover command associated with the measurement-based handover of the wireless device after a timing associated with time resources allocated for sending an indication of a time estimate associated with the connection between the first cell and the wireless device.
[0341] Aspect 41: The method according to any one of aspects 26 to 40, wherein the indication of the coverage information is sent via a system information block, a radio resource control message, a medium access control message, or any combination thereof.
[0342] Aspect 42: The method according to any one of Aspects 26 to 41, further comprising: outputting an indication of one or more parameters for performing measurements for the measurement-based handover from the first cell to the second cell, the message being received in response to the indication of the one or more parameters.
[0343] Aspect 43: A method according to any one of Aspects 26 to 42, the method further comprising: obtaining a second message, the second message indicating a recommendation to perform the measurement-based handover or the non-measurement-based handover, an indication of whether the measurement-based handover can be completed before the wireless device leaves the coverage area of the first cell, an estimated time duration associated with the wireless device remaining in the coverage area of the first cell, the positioning of the wireless device, or any combination thereof.
[0344] Aspect 44: An apparatus for wireless communication at a UE, the apparatus comprising: a processor; and a memory coupled to the processor, the processor being configured to perform the method according to any one of aspects 1 to 16.
[0345] Aspect 45: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing the method according to any one of aspects 1 to 16.
[0346] Aspect 46: A non-transitory computer-readable medium storing 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 16.
[0347] Aspect 47: An apparatus for wireless communication at a UE, the apparatus comprising: a processor; and a memory coupled to the processor, the processor being configured to perform the method according to any one of aspects 17 to 25.
[0348] Aspect 48: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing the method according to any one of aspects 17 to 25.
[0349] Aspect 49: A non-transitory computer-readable medium storing 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 17 to 25.
[0350] Aspect 50: An apparatus for wireless communication at a network device, the apparatus comprising: a processor; and a memory coupled to the processor, the processor configured to perform the method according to any one of aspects 26 to 43.
[0351] Aspect 51: An apparatus for wireless communication at a network device, the apparatus comprising: at least one component for performing the method according to any one of aspects 26 to 43.
[0352] Aspect 52: A non-transitory computer-readable medium storing code for wireless communication at a network device, the code comprising instructions executable by a processor to perform the method of any one of aspects 26 to 43.
[0353] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.
[0354] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and the terminology of LTE, LTE-A, LTE-A Pro, or NR may be used throughout much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.
[0355] The information and signals described herein may be represented by any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0356] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).
[0357] 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 one or more instructions or codes of a computer-readable medium. Other examples and 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 a combination of any of these. Features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations.
[0358] Computer-readable media includes both non-transitory computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included within the definition of computer-readable media. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks can reproduce data magnetically, and discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.
[0359] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this 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."
[0360] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, searching (such as by searching in a table, database, or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), and the like. Furthermore, "determining" may include resolving, retrieving, selecting, choosing, establishing, and other such similar actions.
[0361] 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 can apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.
[0362] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that can be implemented or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.
[0363] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those 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 accorded 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, the processor being configured to: receiving an indication of coverage information for a first cell associated with a non-terrestrial network, the coverage information indicating a coverage area supported by the first cell for wireless communications; and A message is sent indicating timing information associated with a measurement-based handover of the UE from the first cell to a second cell associated with the non-terrestrial network based at least in part on the location information of the UE and the coverage information.
2. The apparatus according to claim 1, further comprising: transceiver, wherein the processor is further configured to: Control signaling associated with a non-measurement based handover of the UE from the first cell to the second cell is received, via the transceiver and in response to the message indicating the timing information.
3. The apparatus of claim 2, wherein the processor is further configured to: The non-measurement based handover from the first cell to the second cell is performed based at least in part on the control signaling.
4. The apparatus of claim 1 , wherein the processor is further configured to: A configuration for sending the message indicating the timing information is received from the non-terrestrial network, the message indicating the timing information being sent in response to the configuration received from the non-terrestrial network.
5. The apparatus of claim 4, wherein the configuration is associated with one of a satellite type or a non-terrestrial cell type of the first cell or the second cell or both.
6. The apparatus of claim 1 , wherein the processor is further configured to: Upon receiving an indication of a timing threshold, the processor is further configured to send the message based at least in part on a failure of the timing threshold to be satisfied for a duration of time associated with the UE remaining within the coverage area supported by the first cell.
7. The apparatus of claim 6 , wherein the duration of time associated with the UE remaining within the coverage area supported by the first cell is based at least in part on the location information of the UE, ephemeris of a satellite associated with the first cell, a reference location of the first cell, a radius of the first cell, the coverage information, or any combination thereof.
8. The apparatus of claim 1 , wherein the processor is further configured to send the message based at least in part on a first time duration associated with the UE being within the coverage area supported by the first cell being less than a second time duration associated with a UE characteristic for the measurement-based handover.
9. The apparatus of claim 8, wherein the second time duration associated with the UE characteristic is based at least in part on the number or characteristics of antennas of the UE, a round trip time between the UE and the first cell or the second cell, or any combination thereof.
10. The apparatus of claim 1 , wherein the processor is further configured to: receiving an indication of one or more parameters associated with the measurement-based handover of the UE, the processor being further configured to send the message based at least in part on a first time duration associated with the UE being within the coverage area supported by the first cell being less than a second time duration associated with the UE performing the measurement-based handover, the second time duration being based at least in part on the one or more parameters associated with the measurement-based handover or a UE characteristic associated with the measurement-based handover, or any combination of both.
11. The apparatus of claim 10, wherein the one or more parameters associated with the measurement-based handover include a measurement periodicity, a measurement gap repetition period, or both.
12. The apparatus of claim 10, wherein the indication of the one or more parameters is received via a system information block, a radio resource control message, a medium access control message, or any combination thereof.
13. The apparatus of claim 10, wherein the processor is further configured to: An indication of parameters for performing measurements for the measurement-based handover from the first cell to the second cell is received, the one or more parameters associated with the measurement-based handover being based at least in part on the parameters for performing the measurements for the measurement-based handover.
14. The apparatus of claim 1 , wherein to send the message, the processor is configured to: The message is sent indicating: a recommendation for the UE to perform one of the measurement-based handover or the non-measurement-based handover, whether the UE can complete the measurement-based handover before leaving the coverage area of the first cell, an estimated time duration associated with the UE remaining in the coverage area of the first cell, a location of the UE, or any combination thereof.
15. The apparatus of claim 14, wherein the processor is further configured to: A configuration is received from the non-terrestrial network indicating one or more parameters of the timing information or a granularity of the timing information, the timing information being based at least in part on the configuration received from the non-terrestrial network.
16. The apparatus of claim 1, wherein the message is sent via a third message or a fifth message of a random access procedure, an uplink message after the random access procedure, a random access preamble, a random access opportunity, or any combination thereof.
17. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; and a memory coupled to the processor, the processor being configured to: receiving an indication of coverage information for a first cell associated with a non-terrestrial network, the coverage information indicating a coverage area supported by the first cell for wireless communications; as well as A handover command associated with measurement-based handover of the UE is received after a timing associated with time resources allocated for sending an indication of a time estimate associated with a connection between the first cell and the UE.
18. The apparatus of claim 17, wherein the processor is further configured to: A message is sent indicating timing information associated with the measurement-based handover from the first cell to a second cell associated with the non-terrestrial network based at least in part on the location information of the UE and the coverage information.
19. The apparatus of claim 18, wherein the message indicates that the UE may perform the measurement-based handover before leaving the coverage area supported by the first cell.
20. The apparatus of claim 17, wherein the processor is further configured to: The measurement-based handover from the first cell to a second cell is performed based at least in part on the handover command.
21. The apparatus of claim 17, wherein the processor is further configured to: Receiving an indication of a timing threshold, the processor is further configured to receive the handover command based at least in part on a duration of time associated with the UE remaining within the coverage area supported by the first cell satisfying the timing threshold.
22. The apparatus of claim 17, wherein the processor is further configured to: receiving an indication of one or more parameters associated with the measurement-based handover, the processor being further configured to: receive the handover command based at least in part on a first time duration associated with the UE being within the coverage area supported by the first cell being greater than a second time duration associated with the UE performing the measurement-based handover, the second time duration being based at least in part on the one or more parameters associated with the measurement-based handover or a UE characteristic associated with the measurement-based handover, or any combination of both.
23. An apparatus for wireless communication at a network device, the apparatus comprising: processor; and a memory coupled to the processor, the processor being configured to: outputting an indication of coverage information for a first cell associated with a non-terrestrial network, the coverage information indicating a coverage area supported by the first cell for wireless communications; as well as Monitoring for a message indicating timing information associated with a measurement-based handover from the first cell to a second cell associated with the non-terrestrial network.
24. The apparatus of claim 23, wherein to monitor the message, the processor is configured to: The message is obtained indicating the timing information associated with the measurement-based handover from the first cell to the second cell associated with the non-terrestrial network.
25. The apparatus of claim 24, wherein the processor is further configured to: Control signaling associated with a non-measurement based handover from the first cell to the second cell is output in response to the message indicating the timing information.
26. The apparatus of claim 24, wherein the processor is further configured to: A configuration for sending the message indicating the timing information is output, the message indicating the timing information being received based at least in part on the configuration.
27. The apparatus of claim 24, wherein the processor is further configured to: An indication of a timing threshold is output, the message indicating that a duration of time associated with remaining within the coverage area supported by the first cell fails to meet the timing threshold.
28. The apparatus of claim 24, wherein the processor is further configured to: and outputting an indication of one or more parameters associated with the measurement-based handover, the message indicating that a first time duration associated with being within the coverage area supported by the first cell is less than a second time duration associated with a wireless device performing the measurement-based handover, the second time duration being based at least in part on either or both of the one or more parameters associated with the measurement-based handover, a wireless device characteristic associated with the measurement-based handover.
29. The apparatus of claim 24, wherein the processor is further configured to: A configuration indicative of one or more parameters of the timing information or a granularity of the timing information is output, the timing information being based at least in part on the configuration.
30. A method for wireless communication at a user equipment (UE), the method comprising: receiving an indication of coverage information for a first cell associated with a non-terrestrial network, the coverage information indicating a coverage area supported by the first cell for wireless communications; as well as A message is sent indicating timing information associated with a measurement-based handover of the UE from the first cell to a second cell associated with the non-terrestrial network based at least in part on the location information of the UE and the coverage information.
