Terrestrial network and non-terrestrial network mobility

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a network node may attempt to obtain capability information related to mobility operation of a user equipment (UE) transitioning from a non-terrestrial network (NTN) to a terrestrial network (TN). The network node may perform at least a portion of the mobility operation based at least in part on the capability information or an attempt to obtain the capability information. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims the priority of Indian Patent Application No. 202241044375 filed on August 3, 2022, titled “TERRESTRIAL NETWORK AND NON-TERRESTRIAL NETWORK MOBILITY” and assigned to the assignee of this application. The disclosure of the prior application is considered to be a part of this patent application and is incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatuses for terrestrial network (TN) and non-terrestrial network (NTN) mobility. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include attempting to obtain capability information related to a mobility operation of a user equipment (UE) transferred between a non-terrestrial network (NTN) and a terrestrial network (TN). The method may include performing at least a portion of the mobility operation based at least in part on the capability information or attempting to obtain the capability information.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include triggering a mobility operation associated with transferring a UE between an NTN and a TN based at least in part on at least one of: capability information associated with the UE and related to the mobility operation, or whether the capability information is available for the network node. The method may include outputting a message for the UE based at least in part on the capability information.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a trigger for a mobility operation associated with the UE between an NTN and a TN. The method may include performing at least a portion of the mobility operation based at least in part on having sent capability information indicating capabilities of the UE associated with the mobility operation, or aborting the mobility operation based at least in part on not having sent the capability information.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to attempt to obtain capability information related to a mobility operation of a UE transferred between an NTN and a TN. The one or more processors may be configured to perform at least a portion of a mobility operation based at least in part on the capability information or attempt to obtain the capability information.

[0011] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to trigger a mobility operation associated with transferring a UE between an NTN and a TN based at least in part on at least one of the following. The one or more processors may be configured to output a message for the UE based at least in part on the capability information.

[0012] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a trigger for a mobility operation between an NTN and a TN associated with the UE. The one or more processors may be configured to perform at least a portion of the mobility operation based at least in part on having sent capability information indicating capabilities of the UE associated with the mobility operation, or to abort the mobility operation based at least in part on not having sent capability information.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to attempt to obtain capability information related to a mobility operation of a UE transferring between an NTN and a TN. The instruction set, when executed by one or more processors of the network node, may cause the network node to perform at least a portion of the mobility operation based at least in part on the capability information or attempting to obtain the capability information.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to trigger a mobility operation associated with transferring a UE between an NTN and a TN based at least in part on at least one of the following. The instruction set, when executed by one or more processors of the network node, may cause the network node to output a message for the UE based at least in part on the capability information.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a trigger for a mobility operation between an NTN and a TN associated with the UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to perform at least a portion of the mobility operation based at least in part on having sent capability information indicating capabilities of the UE associated with the mobility operation, or to abort the mobility operation based at least in part on not having sent capability information.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for attempting to obtain capability information related to a mobility operation of a UE transferring between an NTN and a TN. The apparatus may include a component for performing at least a portion of the mobility operation based at least in part on the capability information or attempting to obtain the capability information.

[0017] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for triggering a mobility operation associated with transferring a UE between an NTN and a TN based at least in part on at least one of capability information associated with the UE and related to the mobility operation, or whether the capability information is available for the network node. The apparatus may include means for outputting a message for the UE based at least in part on the capability information.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a trigger for a mobility operation between an NTN and a TN associated with the UE. The apparatus may include means for performing at least a portion of the mobility operation based at least in part on having sent capability information indicating capabilities of the UE associated with the mobility operation, or aborting the mobility operation based at least in part on not having sent the capability information.

[0019] The various aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and as illustrated in the accompanying descriptions.

[0020] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0021] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0023] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0024] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0025] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0026] Figure 4 is a diagram illustrating an example of a wireless network including a terrestrial network (TN) and a non-terrestrial network (NTN) according to the present disclosure.

[0027] Figure 5 is a diagram illustrating a signaling example of capability information associated with a UE transferring from an NTN to a TN according to the present disclosure.

[0028] Figure 6 is a diagram illustrating an example of a handover mobility operation based on an X2 interface according to the present disclosure.

[0029] Figure 7 is a diagram illustrating an example of a handover mobility operation based on the S1 application protocol (AP) according to the present disclosure.

[0030] Figure 8 is a diagram illustrating an example of a redirected mobility operation based on a radio resource control (RRC) release according to the present disclosure.

[0031] Fig. 9 is a diagram illustrating an example of a redirected mobility operation involving early data transmission (EDT) or preconfigured uplink resources (PUR) according to the present disclosure.

[0032] Fig.10 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0033] Fig.11 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0034] Fig.12 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0035] Fig.13 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0036] Fig.14 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0037] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0038] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0039] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0040] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, as well as other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0041] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network node 110 may include an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0042] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with a femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0043] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0044] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0045] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0046] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0047] UE 120 can be dispersed throughout the wireless network 100, and each UE 120 can be fixed or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0048] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network node, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer site equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0049] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0050] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0051] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. 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, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as a "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as a "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0053] Considering the above examples, unless otherwise expressly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can broadly refer to frequencies that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise expressly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can broadly refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0054] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may attempt to obtain capability information related to a mobility operation of a UE transferring from an NTN to a TN; and perform at least a portion of the mobility operation based at least in part on the capability information or attempting to obtain the capability information. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0055] In some aspects, the communication manager 150 may trigger a mobility operation associated with transferring the UE from the NTN to the TN based at least in part on at least one of: capability information associated with the UE and related to the mobility operation, or whether the capability information is available for the network node; and output a message for the UE based at least in part on the capability information. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0056] In some aspects, UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive a trigger for a mobility operation associated with the UE from an NTN to a TN; and perform at least a portion of the mobility operation based at least in part on having sent capability information indicating capabilities of the UE associated with the mobility operation, or abort the mobility operation based at least in part on not having sent the capability information. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0057] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

[0058] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

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

[0060] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in a housing 284.

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

[0062] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0063] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, reference Figures 4 to 14 )Aspects of any of the methods described herein.

[0064] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform the operations described herein (e.g., with reference to Figures 4 to 14 )Aspects of any of the methods described herein.

[0065] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the UE 120 may perform one or more techniques associated with mobility operations, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.10 The process of 1000 Fig.11 Process 1100, Fig.12 1200 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), the one or more instructions may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Fig.10 The process of 1000 Fig.11 Process 1100, Fig.12 The process 1200 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.

[0066] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0067] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0068] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0069] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0070] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0071] Figure 33 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0072] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of these units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), which is configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0073] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0074] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0075] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions based on functional splits (e.g., functional splits defined by 3GPP) such as lower layer functional splits, or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0076] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RTRIC 315 configured to support the functionality of the SMO framework 305.

[0077] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

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

[0079] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.

[0080] Figure 44 is a diagram illustrating an example of a wireless network including a terrestrial network (TN) and a non-terrestrial network (NTN). A core network entity 410 (in example 400, a mobility management entity (MME)) may support both the TN and the NTN. For example, the core network entity 410 may manage operations of the TN and the NTN, such as network access control, radio resource management, mobility management, roaming management, and tracking area management, among others. Although the core network entity 410 of example 400 is an MME, in some aspects, the core network entity may be a different entity, such as one or more entities of an evolved packet core (EPC), one or more entities of a 5G core (5GC), one or more entities of a 6G network (e.g., a 6G core network), or a combination thereof. In some aspects, an eNB (or gNB, a set of network nodes 110, etc.) may support connections by a UE 120 via both a TN (e.g., a network node 110) and an NTN (e.g., a satellite 420).

[0081] The TN is associated with the network node 110. For example, the network node 110 may provide a cell (illustrated as a TN cell) to which the UE can connect to access the TN. The NTN is served by a satellite 420. For example, the satellite 420 may provide a cell (illustrated as an NTN cell) to which the UE can connect to access the NTN. As described above, the MME or eNB (or gNB, a group of network nodes 110, etc.) may support the connection of the UE 120 to the network (e.g., a public land mobile network (PLMN)) via the TN and the NTN. For example, the UE may be configured with an equivalent PLMN (e.g., PLMN parameters) for (e.g., belonging to) both the TN and the NTN. The PLMN associated with the configured equivalent PLMN may support both the TN and the NTN. Therefore, if the UE enters a radio link failure state or a suspended state with respect to a connection to one network (of the TN or the NTN), the UE may be able to continue the connection on another network (of the TN or the NTN). This may provide improved coverage and reliability, especially for UEs that are only intermittently covered by TN cells.

[0082] In some examples, the NTN may use a transparent satellite deployment, which may also be referred to as a bent-pipe satellite deployment. In a transparent satellite deployment, satellite 420 may relay signals received from gateway 450 via feeder link 460. For example, the satellite may receive an uplink RF transmission and may transmit a downlink RF transmission without demodulating the uplink RF transmission. In some aspects, the satellite may convert the frequency of the uplink RF transmission received on service link 430 to the frequency of the uplink RF transmission on feeder link 460, and may amplify and / or filter the uplink RF transmission. In some aspects, Figure 4UE 120 shown in FIG. 1 may be associated with a Global Navigation Satellite System (GNSS) capability or a Global Positioning System (GPS) capability, but not all UEs have such capabilities. Satellite 420 may provide a cell (shown as an NTN cell) covering UE 120 .

[0083] In some aspects, the NTN may use a regenerative satellite deployment. In a regenerative satellite deployment, the UE 120 is served by a satellite via a service link. For example, a satellite may include a network node 110 (e.g., network node 110a). In some aspects, a satellite may be referred to as a non-terrestrial base station, a regenerative repeater, or an onboard processing repeater. In some aspects, a satellite may demodulate an uplink radio frequency signal, and may modulate a baseband signal derived from an uplink radio signal to generate a downlink radio frequency transmission. A satellite may send a downlink radio frequency signal on a service link. A satellite may provide a cell covering a UE.

[0084] The service link 430 may include a link between the satellite 420 and the UE 120, and may include one or more of an uplink or a downlink. The feeder link 460 may include a link between the satellite 420 and the gateway 450, and may include one or more of an uplink (e.g., from the UE 120 to the gateway 450) or a downlink (e.g., from the gateway 450 to the UE 120).

[0085] The UE may perform a mobility operation to select a new serving cell for the UE. For example, the mobility operation may include a handover (wherein the primary serving cell of the UE is changed from a first cell provided by a first network node to a second cell provided by a second network node), an RRC connection release and redirection (wherein the UE is configured in RRC idle mode and is instructed to prioritize the target cell for reestablishing the RRC connection), or a tracking area update (TAU) procedure (wherein the UE initiates an update of the tracking area for the UE in idle mode). The tracking area (identified by a tracking area identifier) ​​is part of a tracking area identifier (TAI) parameter used to register with the core network entity 410, where the TAI parameter indicates a mobile country code (MCC), a mobile network code (MNC), and a tracking area code (TAC). Some types of mobility operations may involve information transmission between network nodes, such as a source network node providing a source cell for the mobility operation and a target network node providing a target cell for the mobility operation. The source cell is the serving cell of the UE before performing the mobility operation. The target cell is the selected cell for the mobility operation, and if the mobility operation is successful, the UE is connected to the selected cell. As used herein, a mobility operation is referred to as transferring a UE from a source cell (or source network or source network node) to a target cell (or target network or target network node). Depending on the type of mobility operation, the UE's connection (e.g., RRC connection) may or may not be maintained during the transfer.

[0086] The UE may report capability information (sometimes referred to as UE capability information) indicating features or operations supported by the UE. Capability information is typically reported to the network to which the UE is connected. For example, if the UE is connected to the TN of example 400, the UE may report capability information to the network node 110 of the TN. If the UE is connected to the NTN of example 400, the UE may report capability information to the network node 110 of the NTN. The TN may support capability information about mobility operations for transferring the UE from the TN to the NTN. For example, the UE may send capability information (e.g., an E-UTRA capability information element (IE) indicating an E-UTRA UE radio access capability parameter) in a UE capability TN container, wherein the capability information includes an IE (e.g., ntn-Connectivity-EPC or ntn-Connectivity-EPC-r17) indicating whether the UE supports NTN access when connected to an EPC (e.g., associated with a TN). However, although the TN supports capability information about transferring the UE from the TN to the NTN, the information may not indicate whether the UE can be transferred from the NTN to the TN. Therefore, the target network node (e.g., target eNB) may not have information indicating whether the UE can be transferred from the NTN to the TN associated with the target network node. This may negatively affect mobility operations such as handover, RRC reestablishment, capability update via non-access stratum (NAS) signaling, and UE capability processing by the core network. Therefore, the reliability of mobility operations may be reduced, and the interoperability of the TN and the NTN may be reduced.

[0087] Some of the techniques described herein provide capability information related to mobility operations of a UE transferring from an NTN to a TN. For example, the capability information may indicate whether the UE can be transferred to a TN (e.g., associated with an EPC) when connected to an NTN. Some of the techniques described herein provide signaling related to capability information, such as for providing capability information via a network node or a core network entity, or for providing capability information associated with a TAU update. In addition, some of the techniques described herein provide mobility operations based at least in part on capability information, such as X2-based handover, S1 application protocol (S1-AP)-based handover, RRC release and redirection, and mobility operations based on early data transmission (EDT) or preconfigured uplink resources (PUR) configuration. In this way, the reliability of mobility operations between the NTN and the TN is improved, and the interoperability of the TN and the NTN is improved. This may be particularly beneficial in the context of the Internet of Things (IoT) of the NTN.

[0088] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Different than described.

[0089] Figure 5 is a diagram illustrating a signaling example 500 of capability information associated with a UE transferring from an NTN to a TN in accordance with the present disclosure. As shown, example 500 includes a UE (e.g., UE 120), a first network node (e.g., network node 110), a second network node (e.g., network node 110), and a core network entity (e.g., core network entity 410). In some aspects, the core network entity may be an MME. The first network node of example 500 may be associated with the NTN. For example, the first network node of example 500 may include or be part of an eNB associated with the NTN, such as an eNB implemented on a satellite or an eNB communicating with a satellite via a feeder link, such as in conjunction with Figure 4 The second network node of example 500 may be associated with the NTN. For example, the second network node of example 500 may include or be part of an eNB associated with the TN, such as in conjunction with Figure 4 as described.

[0090] As shown, the core network entity may store or access capability information 505 about transferring the UE from the TN to the NTN. The capability information 505 may be referred to as capability information for the TN RAT. For example, the capability information 505 may be provided by the UE in a UE capability TN container (e.g., an E-UTRA capability IE indicating an E-UTRA UE radio access capability parameter) for a second network node. The capability information 505 may include an IE (e.g., ntn-Connectivity-EPC or ntn-Connectivity-EPC-r17) indicating whether the UE supports NTN access when connected to an EPC (e.g., associated with a TN), such as an EPC of the core network entity including example 500. The core network entity may receive the capability information 505 from the second network node (not shown). In some aspects, the capability information indicates whether the UE supports the same set of capabilities for NTN radio access technology and TN radio access technology to perform mobility operations.

[0091] As indicated by reference numeral 510, the UE may enter a connected mode with the first network node. For example, the UE and the first network node may establish an RRC connection, such as based at least in part on a random access channel (RACH) message 5 (which may include, for example, an RRC reconfiguration complete message or a message defined by the fifth step of a four-step RACH procedure). As further shown, the RACH message 5 may indicate a remaining GNSS validity duration. As indicated by reference numeral 515, the first network node may provide a UE initialization message to a core network entity.

[0092] As indicated by reference numeral 520, the core network entity may provide an initial context establishment request to the first network node. The initial context establishment request may indicate that the core network entity has not yet received capability information 535 from the first network node or the UE. The capability information 535 may relate to mobility operations of the UE transferring from the NTN to the TN, as described in more detail below. As indicated by reference numeral 525, the first network node may provide a context establishment response to the core network entity.

[0093] As shown, the first network node may provide the UE with a UE capability request 530. The UE capability request 530 may request capability information 535 from the UE, such as based at least in part on an initial context establishment request indicating that the core network entity has not received the capability information 535.

[0094] As shown, the UE may send capability information 535. For example, the UE may send a UE capability report indicating the capability information 535. The capability information 535 may indicate that the UE is connected to the NTN (e.g., Figure 5 In some aspects, the capability information 535 may indicate whether the UE is capable of being transferred to a TN when connected to an NTN (e.g., an NTN associated with an EPC, 5GC, or UTRA network). In some aspects, the capability information 535 may indicate one or more frequency bands supported by the UE. For example, the capability information 535 may be for each frequency band. In some aspects, the capability information 535 may include a bit indicating whether the UE is capable of being transferred to a TN when connected to an NTN. As indicated by reference numeral 540, the first network node may provide an indication of the capability information 535 to the core network entity. For example, the indication may include the capability information 535. As indicated by reference numeral 545, the core network entity may store or access the capability information 505 and the capability information 535. As indicated by reference numeral 550, the UE may perform uplink or downlink data communication, such as via an NTN associated with the first network node and the core network entity.

[0095] As indicated by reference numeral 555, two or more of the UE, the first network node, the second network node, and the core network entity may perform a mobility operation. For example, the UE may perform one or more steps of the mobility operation (e.g., at least a portion of the mobility operation). For another example, the first network node (e.g., the source network node or the target network node of the mobility operation) may perform one or more steps of the mobility operation (e.g., at least a portion of the mobility operation). For another example, the second network node (e.g., the source network node or the target network node of the mobility operation) may perform one or more steps of the mobility operation (e.g., at least a portion of the mobility operation). For another example, the core network entity may perform one or more steps of the mobility operation (e.g., at least a portion of the mobility operation). The UE, the first network node, the second network node, and / or the core network entity may perform the mobility operation based at least in part on the capability information 505 and / or the capability information 535. For example, if the mobility operation involves transferring the UE from a TN associated with the first network node to an NTN associated with the second network node, the mobility operation may be based at least in part on the capability information 505. As another example, if the mobility operation involves transferring the UE from an NTN associated with a second network node to a TN associated with a first network, the mobility operation may be based at least in part on the capability information 535. The mobility operation may be based at least in part on the capability information 535 because a target network node may be selected based on the capability information 535 (e.g., a target network node associated with a frequency band that the UE supports transferring from the NTN to the TN, or a target network associated with the TN because the UE supports transferring from the NTN to the TN).

[0096] The mobility operation may include, for example, a handover based on an X2 interface, a handover based on an S1-AP, a redirection based on an RRC release, a redirection based on an EDT, a redirection based on a PUR, a redirection without RACH, or a TAU update. Specific examples of mobility operations and examples of mobility operations in a scenario where the target network node cannot obtain capability information 535 are described in Figures 6 to 9 Available in.

[0097] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Different than described.

[0098] Figure 6 600 is a diagram illustrating an example of a handover mobility operation based on an X2 interface according to the present disclosure. In a handover based on an X2 interface, the primary serving cell of the UE is changed from a first network node to a second network node, wherein the first network node and the second network node are connected using an X2 interface. Example 600 is also applicable to a handover based on an Xn interface between network nodes connected using an Xn interface.

[0099] Example 600 includes a UE 605 (eg, UE 120), a source network node 610 (eg, network node 110), a target network node 615 (eg, network node 110), and a core network entity 620 (eg, Figure 4 410 of the core network entity 410). In example 600, the source network node is associated with the NTN and the target network node is associated with the TN. For example, the UE 605 may be connected to the NTN (e.g., the source network node associated with the NTN). As shown in the figure, in some examples, the core network entity 620 may store or access capability information, such as capability information associated with a transfer from the TN to the NTN (e.g., capability information 505) and / or capability information associated with a transfer from the NTN to the TN (e.g., capability information 535). In some aspects, the core network entity 620 may only store or access capability information associated with a transfer from the TN to the NTN. In some aspects, the core network entity 620 may only store or access capability information associated with a transfer from the NTN to the TN. In some aspects, the core network entity 620 may store or access capability information associated with a transfer from the TN to the NTN and capability information associated with a transfer from the NTN to the TN. The technology described in relation to example 600 may also be applied to mobility operations for transferring the UE 605 from the TN to the NTN.

[0100] As shown, source network node 610 may provide handover request 625 to target network node 615. Handover request 625 may indicate, for example, the identity of source network node 610, a reason for the handover, an identifier of target network node 615, UE context, and so forth.

[0101] Thus, source network node 610 may trigger a mobility operation associated with transferring UE 605 from NTN to TN. Source network node 610 may trigger the mobility operation based at least in part on at least one of the following: capability information associated with the transfer from NTN to TN, or whether the capability information is available at source network node 610.

[0102] For example, the handover request 625 may indicate to the target network node 615 that no capability information associated with the transfer from the NTN to the TN is available, and that the target network node 615 will attempt to obtain the capability information from the core network entity 620 (e.g., instead of transmitting an "X2 Handover (HO) Failed" message to the source network node 610). In this case, triggering the mobility operation may include: outputting the handover request 625 including an empty UE capability container to the target network node 615 for the mobility operation based at least in part on the capability information not being available to the source network node 610. For example, the empty UE capability container may indicate that the capability information is not available to the source network node 610. For example, the source network node 610 may create a source-to-target transparent container such that the UE radio capability container is empty within the S1 Handover Required message.

[0103] In some aspects, the target network node 615 may identify that the source network node 610 is a different network type (e.g., TN or NTN), and may initiate a UE capability request to the core network entity 620 without checking the UE capability container received from the source network node 610. An IE may be added to the Xn (e.g., X2) to establish the serving cell information to notify the neighboring cell (e.g., network node) that the cell network type is TN or NTN. In some aspects, the target network node 615 may identify that the source network node 610 is a different network type based at least in part on a cause value indicating NTN to TN mobility or a cause value indicating TN to NTN mobility. In some aspects, the target network node 615 may identify that the source network node 610 is a different network type based at least in part on the eNB identity of the source network node 610. Therefore, the target network node 615 may request capability information from the core network entity 620 based at least in part on the mobility operation being from NTN to TN. For example, the target network node 615 may determine that the mobility operation is from the NTN to the TN based at least in part on an indication of the source network node 610 from the UE 605 as to whether the source network node 610 is associated with the NTN or the TN.

[0104] In some aspects, the source network node 610 may make a handover decision. However, the source network node 610 may not know or have access to information indicating the capabilities of the UE 605 for the target network type (e.g., a transfer from NTN to TN). The source network node 610 may request the core network entity 620 to transmit capability information of the UE 605 for the target network type (e.g., for a transfer from NTN to TN). Therefore, the source network node 610 may request the capability information from the core network entity 620. If the core network entity 620 has stored the capability information of the UE 605, the core network entity 620 may transmit the capability information of the UE 605 for the target network type to the source network node 610. Otherwise, the source network node 610 may determine that a handover is not possible and may release the UE 605 by redirection to the target network node 615, as described elsewhere herein. Thus, source network node 610 may determine that capability information was not received, and the message to UE 605 may include an indication to cause UE 605 to enter idle mode (based at least in part on the capability information being unavailable to the network node). As used herein, "releasing the UE" may include providing an indication to cause the UE to enter idle mode (e.g., RRC idle mode).

[0105] As shown, the target network node 615 may provide a UE capability request 630 to the core network entity 620. Thus, the target network node 615 may attempt to obtain capability information related to the mobility operation of transferring the UE from the NTN to the TN by requesting the capability information from the core network entity 620. In some aspects, requesting the capability information from the core network entity 620 (e.g., via the UE capability request 630) is based at least in part on an indication from the source network node 610 of the UE 605 that the capability information is not available at the source network node (e.g., a handover request 625 including an empty UE capability container). The UE capability request may indicate an S1-AP identifier (e.g., of the target network node 615).

[0106] As shown, the core network entity 620 may provide a UE capability response 635 to the target network node 615. If the core network entity 620 has stored or accessed capability information about the transfer from the NTN to the TN, the UE capability response 635 may include the capability information. If the core network entity 620 has not stored or cannot access capability information about the transfer from the NTN to the TN, the capability response 635 may omit the capability information. As further shown, the UE capability response 635 may indicate the S1-AP identifier received in the UE capability request 630.

[0107] As shown, the target network node 615 may provide a handover request confirmation 640 to the source network node 610. If the target network node 615 cannot obtain capability information regarding the transfer from the NTN to the TN, the target network node 615 may initiate a basic handover. The basic handover may include a handover with minimum required capabilities for the RRC connection. For example, the basic handover may be equivalent to an RRC connection establishment (if the UE 605 supports the transfer from the NTN to the TN) or an RRC release (if the UE 605 does not support the transfer from the NTN to the TN). Therefore, the target network node 615 may not be able to obtain capability information (e.g., from the core network entity 620), and may trigger a handover associated with the minimum required capabilities of the RRC connection (e.g., a basic handover) based at least in part on the inability to obtain capability information. In the case of an S1-AP based handover (regarding Figure 7 As described above), the target network node 615 may request the core network entity 620 to release the UE 605, and the core network entity 620 may initiate an RRC release procedure.

[0108] In some aspects, if the target network node 615 determines (e.g., knows) that the UE 605 does not support the frequency band of the target network node 615 (such as in TN or NTN), the target network node 615 may request the source network node 610 to release the UE 605 to idle mode. For example, if the capability information indicates that the UE 605 does not support the frequency band of the target radio access technology of TN or NTN, performing at least a portion of the mobility operation may include the target network node 615 requesting the source network node 610 or the core network entity 620 associated with the UE 605 to release the UE 605 to idle mode. For example, the source network node 610 may obtain an indication from the target network node 615 of the mobility operation to release the UE 605 to idle mode based at least in part on the capability information indicating that the UE cannot transfer from NTN to TN.

[0109] As shown, source network node 610 may output a handover command 645 for UE 605. Thus, source network node 610 may output a message (e.g., handover command 645) for UE 605 based at least in part on capability information. Handover command 645 may identify target network node 615 and may instruct UE 605 to perform at least a portion of a mobility operation (i.e., a handover to target network node 615). As indicated by reference numeral 650, UE 605 may transfer to target network node 615. For example, UE 605 and target network node 615 may synchronize with each other, as described below with respect to Figure 7 as described.

[0110] In some aspects, the UE 605 may ignore the handover command 645 and may enter an idle mode, as indicated by reference numeral 655. For example, in some aspects, the UE may receive a handover command 645 that instructs the UE 605 to handover to a target network node 615 associated with a RAT (e.g., TN or NTN) that is not supported by the UE 605. In this case, the UE may ignore the handover command 645 and may enter an idle mode.

[0111] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Different than described.

[0112] Figure 7 is a diagram illustrating an example 700 of an S1-AP based handover mobility operation according to the present disclosure. An S1-AP based handover is a mobility operation in which there is no direct interface (e.g., an X2 or Xn interface) between a source network node and a target network node of the mobility operation. In an S1-AP based handover, a source core network entity (e.g., a source MME) selects a target core network entity associated with a target network node to which the UE is to be transferred. Thus, in example 700, the handover may be handled by a core network entity.

[0113] Example 700 includes a UE 705 (eg, UE 120), a source network node 710 (eg, network node 110), a target network node 715 (eg, network node 110), and a core network entity 720 (eg, Figure 4 410). The source network node is associated with the NTN and the target network node is associated with the TN. For example, the UE 705 may be connected to the NTN (e.g., the source network node associated with the NTN). As shown in the figure, in some examples, the core network entity 720 may store or access capability information, such as capability information associated with a transfer from the TN to the NTN (e.g., capability information 505) and / or capability information associated with a transfer from the NTN to the TN (e.g., capability information 535). In some aspects, the core network entity 720 may only store or access capability information associated with a transfer from the TN to the NTN. In some aspects, the core network entity 720 may only store or access capability information associated with a transfer from the NTN to the TN. In some aspects, the core network entity 720 may store or access capability information associated with a transfer from the TN to the NTN and capability information associated with a transfer from the NTN to the TN. The technology described with respect to the example 700 may also be applied to mobility operations for transferring the UE 705 from the TN to the NTN. For example, source network node 710 may be associated with a TN and target network node 715 may be associated with an NTN.

[0114] As shown, at reference numeral 725, source network node 710 may determine to perform a mobility operation from NTN to TN. For example, source network node 710 may determine that criteria associated with a handover of UE 705 are met.

[0115] As shown, the source network node 710 may provide a handover required message 730 to the core network entity 720. Thus, the source network node 710 may trigger a mobility operation. In some aspects, the handover required message indicates that the mobility operation is from NTN to TN. For example, the handover required message 730 may include a handover type IE. The handover type IE may include a code point (e.g., a value) indicating a handover type (e.g., a handover to NTN or a handover to TN) or a field indicating a handover type.

[0116] As shown, the core network entity 720 may provide a handover request message 735 to the target network node 715. In some aspects, the core network entity 720 may determine that the handover is between different RAT types (from NTN to TN or vice versa). For example, the core network entity 720 may make this determination based at least in part on the S1-AP identifier of the target network node 715, or at least in part on the handover type IE of the handover required message 730 (if included).

[0117] As shown, in some aspects, the core network entity 720 may provide the target network node 715 with a UE information transmission 740. In some aspects, receiving the UE information transmission 740 may be referred to as obtaining or attempting to obtain capability information related to the mobility operation of transferring the UE from the NTN to the TN. For example, attempting to obtain the capability information may include receiving the capability information from the core network entity. In some aspects, when transmitting the handover request message 735 from the core network entity 720 to the target network node 715, if the core network entity 720 has stored the capability information, the core network entity 720 may (e.g., always) include a UE capability container (including capability information) in the handover request message 735 to provide the target network node 715 with the capability information. In this example, the UE information transmission 740 may be included in the handover request message 735. For example, the handover request message 735 may be extended to include UE radio capabilities (indicating capability information). For another example, a UE information transmission message (i.e., UE information transmission 740) separated from the handover request message 735 may be used. As another example, if the handover is between a TN and an NTN, the downlink NAS transport message of the UE 705 may (e.g., always) follow the handover request message 735. In this case, the NAS protocol data unit (PDU) field may be an empty string, may be omitted (e.g., not included), or may be ignored by the UE 705. In some aspects, if the core network entity 720 does not store (or cannot access) capability information, the core network entity 720 may provide an indication to the target network node 715 to perform a basic handover (e.g., with minimum capabilities as described above). The indication may be provided in one or more of the above messages, or in a separate message. As shown, the target network node 715 may provide a handover request confirmation 745 to the core network entity 720. The handover request confirmation 745 may include an empty source-to-target transparent container.

[0118] As shown, core network entity 720 may provide handover command 750 to source network node 710. For example, core network entity 720 may provide handover command 750 based at least in part on handover request confirmation 745. As shown, source network node 710 may provide handover command 755 to UE 705. Handover command 755 may instruct UE 705 to perform at least a portion of a mobility operation to transfer UE 705 from source network node 710 to target network node 715.

[0119] As shown by reference numeral 760, UE 705 may be synchronized with target network node 715. For example, target network node 715 may output (e.g., transmit, provide for transmission, configure another network node to transmit) one or more reference signals. UE 705 may synchronize to the timing and / or frequency of target network node 715 by reference to the one or more reference signals. Thus, target network node 715 and UE 705 may be synchronized with each other.

[0120] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 Different than described.

[0121] Figure 8 800 is a diagram illustrating an example of RRC release based redirection mobility operation according to the present disclosure. Redirection based on RRC release involves releasing the RRC connection with the source network node (e.g., causing the UE to enter idle mode) and instructing the UE to establish an RRC connection with the target network node. The instruction to cause the UE to establish an RRC connection with the target network node is referred to as redirection to the target network node.

[0122] Example 800 includes a UE 805 (eg, UE 120), a source network node 810 (eg, network node 110), a target network node 815 (eg, network node 110), and a core network entity 820 (eg, Figure 4 410). The source network node is associated with the NTN and the target network node is associated with the TN. For example, the UE 805 may be connected to the NTN (e.g., the source network node associated with the NTN). As shown in the figure, in some examples, the core network entity 820 may store or access capability information, such as capability information associated with a transfer from the TN to the NTN (e.g., capability information 505) and / or capability information associated with a transfer from the NTN to the TN (e.g., capability information 535). In some aspects, the core network entity 820 may only store or access capability information associated with a transfer from the TN to the NTN. In some aspects, the core network entity 820 may only store or access capability information associated with a transfer from the NTN to the TN. In some aspects, the core network entity 820 may store or access capability information associated with a transfer from the TN to the NTN and capability information associated with a transfer from the NTN to the TN. The technology described with respect to example 800 may also be applied to mobility operations for transferring the UE 805 from the TN to the NTN. For example, source network node 810 may be associated with a TN and target network node 815 may be associated with an NTN.

[0123] As shown, at reference numeral 825, source network node 810 may determine to perform mobility operations from NTN to TN, such as, for example, regarding Figure 7 As described by reference number 725.

[0124] As shown, source network node 810 may provide a handover request 830 to target network node 815. In some aspects (e.g., for S1-AP based handover), source network node 810 may provide a handover required message to core network entity 820. As shown, target network node 815 may provide a UE capability request 835 to core network entity 820. Thus, target network node 815 may attempt to obtain capability information related to mobility operations for transferring the UE from the NTN to the TN.

[0125] As shown, the core network entity 820 may provide a UE capability response message 840 (e.g., a retrieval UE information failure message) to the target network node 815. For example, the core network entity 820 may not store or may not access the capability information associated with the transfer from NTN to TN. Therefore, the target network node 815 may not be able to obtain the capability information associated with the transfer from NTN to TN. In this case, the target network node 815 may not know whether the UE 805 supports the applicable frequency band or the network type (e.g., TN or NTN) associated with the target network node 815. In some aspects, the target network node 815 may initiate a redirection via an RRC release message to be transmitted by the source network node 810 based at least in part on the inability to obtain the capability information.

[0126] As shown, the target network node 815 may provide a handover preparation failure message 845 to the source network node 810. Initiating redirection also includes providing a handover preparation failure message 845 (e.g., an X2AP or S1AP handover failure message) to the source network node of the UE, the handover preparation failure message indicating a release cause associated with an inability to obtain capability information. The release cause may indicate, for example, that no UE capabilities (e.g., no capability information) are available for the target network node 815. Therefore, the source network node 810 may obtain an indication of initiating redirection of the UE 805 from the target network node 815 of the mobility operation, wherein the indication indicates that the target network node 815 cannot obtain capability information, and wherein the message for the UE 805 includes an RRC connection release message (e.g., an RRC connection release message 850). Whether UE 805 is able to perform redirection to the indicated frequency, cell identifier, and / or network type (e.g., indicated by RRC connection release message 850) may depend on UE 805, based at least in part on whether UE 805 supports the indicated frequency, cell identifier, and / or network type (e.g., TN or NTN). As shown, source network node 810 may provide RRC connection release message 850 to UE 805.

[0127] In some aspects, the RRC connection release message 850 may include a dedicated frequency priority list. A dedicated frequency priority list is a list of frequencies. A dedicated frequency priority list may be specific to (e.g., dedicated to) UE 805. A dedicated frequency priority list may indicate the frequencies at which UE 805 can receive a paging message from the network requesting UE 805 to hand over to active mode. In some aspects, a dedicated frequency priority list may be specific to a TN (e.g., a TN using E-UTRA or NR). In some aspects, a dedicated frequency priority list may be specific to an NTN. In some aspects, a dedicated frequency priority list (e.g., an existing dedicated frequency priority list) may include an indication of whether the dedicated frequency priority list is associated with a TN or an NTN.

[0128] As indicated by reference numeral 855, the UE 805 may prioritize selection of cells indicated by the RRC connection release message 850. For example, the UE may perform cell reselection and may prioritize selection of cells associated with the indicated frequency, cell identifier, and / or frequency type.

[0129] After redirection, UE 805 may handover from NTN mode (or TN mode) to TN mode (or NTN mode), depending on whether UE 805 is transferred to TN or NTN. For handover mode, the RAT type may be indicated to UE 805 (indicating whether the target network node 815 is associated with TN or NTN). The RRC connection release message 850 may indicate the cell identifier, RAT type, and core network (CN) type (e.g., 5GC, UTRA, E-UTRA, EPC) associated with the target network node 815 in the redirection carrier information of the RRC connection release message 850. This may also be indicated in the EDT complete message or the PUR complete message, as described in detail in relation to the Fig. 9 as described.

[0130] In some aspects, the mobility operations of example 800 may be implemented in a control plane (e.g., without access layer security). In such examples, the mobility operations may include NAS message-based redirection with NAS security (e.g., using NAS messages to source network node 810). For example, target network node 815 and / or core network entity 820 may provide a NAS message to source network node 810 to initiate the NAS message-based redirection with NAS security.

[0131] As shown by reference numeral 860 , UE 805 may synchronize with target network node 815 , as described above with respect to reference numeral 760 .

[0132] As shown, target network node 815 may provide UE capability request 865 to core network entity 820. As shown, core network entity 820 may provide UE capability response 870 to target network node 815. For example, target network node 815 may request (and / or obtain) capability information of UE 805 regarding mobility operations and / or other operations of UE 805.

[0133] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 Different than described.

[0134] Fig. 9 900 is a diagram illustrating an example of redirected mobility operation involving EDT or PUR according to the present disclosure. EDT is a small data transmission (SDT) performed using random access resources. In some examples, EDT may be referred to as SDT based on random access. EDT may involve data transmission of shared radio resources using a random access procedure. In some examples, shared radio resources may be indicated via system information. SDT may also be performed using PUR. PUR may be configured by one or more RRC parameters sent together with an RRC connection suspension indication in an RRC release message. Therefore, PUR facilitates transmission from an RRC inactive state on PUR. The technology described in example 900 may also be applied to mobility operations for transferring UE 905 from TN to NTN. For example, a source network node 910 may be associated with a TN and a target network node 915 may be associated with an NTN.

[0135] Example 900 includes a UE 905 (eg, UE 120), a source network node 910 (eg, network node 110), a target network node 915 (eg, network node 110), and a core network entity 920 (eg, Figure 4 410). The source network node is associated with the NTN and the target network node is associated with the TN. For example, the UE 905 may be connected to the NTN (e.g., a source network node associated with the NTN). As shown in the figure, in some examples, the core network entity 920 may store or access capability information, such as capability information associated with a transfer from the TN to the NTN (e.g., capability information 505) and / or capability information associated with a transfer from the NTN to the TN (e.g., capability information 535). In some aspects, the core network entity 920 may only store or access capability information associated with a transfer from the TN to the NTN. In some aspects, the core network entity 920 may only store or access capability information associated with a transfer from the NTN to the TN. In some aspects, the core network entity 920 may store or access capability information associated with a transfer from the TN to the NTN and capability information associated with a transfer from the NTN to the TN.

[0136] As indicated by reference numeral 925, the UE may be in an RRC connected state with the source network node 910, with access stratum (AS) security enabled.

[0137] As shown, the source network node 910 may provide the target network node 915 with an RRC connection request 930 for the UE 905. In some aspects, the RRC connection request 930 may include or be based on Msg3 of the four-step RACH process. In some aspects, the RRC connection request 930 may indicate EDT resources (e.g., shared radio resources), PUR resources (e.g., shared radio resources), or uplink grants (e.g., no RACH uplink grants) for the target network node 915. For example, if the source network node 910 can determine the location of the UE 905, and if the UE 905 is moving from an NTN (e.g., a coverage area or cell of the NTN) to a TN (e.g., a coverage area or cell of the TN), then EDT, PUR, and / or no RACH uplink grants may also be enabled for the target network node 915 to facilitate mobility operations. In this example, the source network node 910 may perform handover preparation (i.e., transmit Msg3 and RRC connection establishment message 940 between the source network node 910 and the target network node 915). Therefore, the source network node 910 may trigger the mobility operation by outputting an EDT configuration (e.g., resources for EDT) or PUR for an RRC setup complete message 945 of the UE 905 associated with the mobility operation to the target network node 915 for the mobility operation.

[0138] As shown, target network node 915 may provide RRC connection setup message 935 to source network node 910. For example, source network node 910 may obtain RRC connection setup message 935 from target network node 915 before outputting RRC connection setup message 935 to UE 905. Source network node 910 may then forward RRC connection setup message 935 (e.g., Msg4) to UE 905. RRC connection setup message 935 may be referred to as a message.

[0139] As shown, UE 905 may provide RRC setup complete message 945 to target network node 915. For example, UE may provide RRC setup complete message 945 to target network node 915 as Msg5 (e.g., the fifth step) of a four-step RACH procedure (e.g., without sending Msg3 of the four-step RACH procedure).

[0140] As shown, the target network node 915 may provide a UE capability request 950 to the core network entity 920. As shown, the core network entity 920 may provide a UE capability response 955 to the target network node 915. For example, the target network node 915 may request (and / or obtain) capability information of the UE 905 regarding mobility operations and / or other operations of the UE 905.

[0141] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 Different than described.

[0142] Figures 5 to 9 The source network node, target network node, and UE are described as performing "at least a portion of a mobility operation". For a given device or node, performing at least a portion of a mobility operation includes sending (e.g., outputting), receiving (e.g., inputting, obtaining information), and Figures 5 to 9 The determinations shown in , performed by the given device or node. Figure 6 In the example, the source network node 610 may perform at least a portion of the mobility operation by one or more of: providing a handover request 625, making a handover decision, obtaining a handover request confirmation 640, and outputting a handover command 645, and Figure 6 The other operations described and / or affect the source network node 610 as part of the mobility operation.

[0143] Although the mobility operation involving transfer from NTN to TN is described Figures 5 to 9 The capability information may be used to indicate whether the UE supports the mobility operation involving transferring the UE from the NTN to the TN, but it should be understood that these operations may also be applied to the transfer from the TN to the NTN. In such a specific implementation, the source network node may be associated with the TN, and the target network node may be associated with the NTN. Instead of indicating whether the UE supports the mobility operation involving transferring the UE from the NTN to the TN, the capability information may indicate whether the UE supports the mobility operation involving transferring the UE from the TN to the NTN.

[0144] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a network node according to the present disclosure. The example process 1000 is a diagram in which a network node (e.g., network node 110, Figure 5 An example of a target network node (, target network node 615, target network node 715, target network node 815, target network node 915) performing operations associated with terrestrial network and non-terrestrial network mobility.

[0145] like Fig.10As shown in FIG. 1 , in some aspects, process 1000 may include attempting to obtain capability information related to mobility operations of the UE transferred between the NTN and the TN (block 1010). For example, a network node (e.g., using Fig.13 The communications manager 150 and / or receiving component 1302 depicted in FIG. 1 may attempt to obtain capability information related to mobility operations of the UE transferring from an NTN to a TN or from a TN to an NTN, as described above.

[0146] like Fig.10 As further shown in FIG. 10 , in some aspects, process 1000 may include performing at least a portion of the mobility operation based at least in part on capability information or attempting to obtain capability information (block 1020). For example, a network node (e.g., using Fig.13 The communications manager 150 and / or mobility component 1308 depicted in FIG. 1 may perform at least a portion of mobility operations based at least in part on the capability information or attempt to obtain capability information, as described above.

[0147] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0148] In a first aspect, the capability information indicates whether the UE supports transfer from an NTN to a TN radio access technology associated with at least one of an EPC, a 5G core, or an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) (E-UTRA) technology.

[0149] In a second aspect, alone or in combination with the first aspect, attempting to obtain capability information further comprises requesting capability information from a core network entity.

[0150] In a third aspect, alone or in combination with one or more of the first and second aspects, the network node is a target network node for a mobility operation, and requesting capability information from a core network entity is based at least in part on an indication from the UE that capability information of the source network node is not available at the source network node.

[0151] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the indication that capability information is not available at the source network node is an omission of the UE's radio capabilities in the handover prepare message (eg, an empty capability container).

[0152] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the indication that the capability information is not available at the source network node is an indication that the source network node is associated with a different network type than the target network node.

[0153] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, requesting capability information from the core network entity is based at least in part on the mobility operation being from the NTN to the TN.

[0154] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 1000 includes determining that the mobility operation is from the NTN to the TN based at least in part on an indication from a source network node of the UE as to whether the source network node is associated with the NTN or the TN.

[0155] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 1000 includes triggering a handover associated with a minimum required capability of the RRC connection based at least in part on an inability to obtain capability information.

[0156] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, the capability information indicates that the UE does not support frequency bands of the target radio access technology of TN and NTN, and wherein performing at least part of the mobility operation also includes requesting a source network node or core network entity associated with the UE to release the UE to an idle mode.

[0157] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, attempting to obtain capability information includes receiving capability information from a core network entity.

[0158] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, performing at least a portion of the mobility operation includes at least one of: outputting an acknowledgement associated with the capability information, or synchronizing with the UE.

[0159] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, process 1000 includes failing to obtain capability information and initiating redirection of the UE based at least in part on failing to obtain capability information.

[0160] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, initiating redirection further comprises providing a radio resource control (RRC) release message with redirection information to the UE.

[0161] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the redirection information includes one or more of the following: a dedicated frequency priority list for TN, a dedicated frequency priority list for NTN, or an NTN indication in an existing dedicated frequency priority list, the NTN indication indicating whether the existing dedicated frequency priority list is for NTN or for TN.

[0162] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, initiating redirection further comprises providing a handover failure message to a source network node of the UE, the handover failure message indicating a release cause associated with an inability to obtain capability information.

[0163] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, initiating redirection of the UE further comprises providing a NAS message to a source network node of the UE.

[0164] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the mobility operation comprises a handover or redirection from a cell associated with the NTN to a cell associated with the TN.

[0165] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more of the blocks in the process 1000 may be performed in parallel.

[0166] Fig.11 1 is a diagram illustrating an example process 1100 performed, for example, by a network node according to the present disclosure. The example process 1100 is a diagram in which a network node (e.g., network node 110, Figure 5 An example of a source network node of the invention, source network node 610, source network node 710, source network node 810, source network node 910) performing operations associated with terrestrial network and non-terrestrial network mobility.

[0167] like Fig.11 As shown in , in some aspects, process 1100 may include triggering a mobility operation associated with transferring a UE between an NTN and a TN based at least in part on at least one of: capability information associated with the UE and related to the mobility operation, or whether the capability information is available for the network node (block 1110). For example, the network node (e.g., using Fig.13 The communication manager 150 and / or trigger component 1310 depicted in the figure may trigger a mobility operation associated with transferring the UE from the NTN to the TN (or from the TN to the NTN) based at least in part on at least one of the following: capability information associated with the UE and related to the mobility operation, or whether the capability information is capable of being used for the network node, as described above.

[0168] like Fig.11As further shown in FIG. 1 , in some aspects, process 1100 may include outputting a message for the UE based at least in part on the capability information (block 1120). For example, a network node (e.g., using Fig.13 The communications manager 150 and / or sending component 1304 depicted in FIG. 1 may output a message for the UE based at least in part on the capability information, as described above.

[0169] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0170] In a first aspect, triggering the mobility operation further comprises outputting a handover request including an empty UE capabilities container to a target network node of the mobility operation based at least in part on the capability information being unavailable for the network node.

[0171] In a second aspect, alone or in combination with the first aspect, process 1100 includes obtaining, from a target network node of the mobility operation, an indication to release the UE to an idle mode based at least in part on capability information indicating that the UE cannot transfer from the NTN to the TN.

[0172] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1100 includes requesting the capability information from a core network entity based at least in part on the capability information being unavailable for the network node.

[0173] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1100 includes determining that capability information is not received, wherein the message includes an indication to cause the UE to enter idle mode based at least in part on the capability information being unavailable for the network node.

[0174] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, triggering the mobility operation further comprises outputting a handover required message to a core network entity.

[0175] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the handover required message indicates that the mobility operation is from the NTN to the TN.

[0176] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1100 includes obtaining an indication from a target network node of a mobility operation to initiate redirection of the UE, wherein the indication indicates that the target network node is unable to obtain capability information, and wherein the message for the UE includes an RRC connection release.

[0177] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, triggering a mobility operation further comprises: for a target network node of the mobility operation, outputting an early data transmission configuration or preconfigured uplink resources for an RRC establishment completion message of a UE associated with the mobility operation, and wherein the message comprises an RRC connection establishment message associated with the mobility operation.

[0178] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the process 1100 includes obtaining the RRC connection establishment message from the target network node before outputting the RRC connection establishment message.

[0179] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the mobility operation omits a RACH procedure.

[0180] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the capability information indicates that the UE does not support frequency bands of the target radio access technology of TN and NTN, and wherein performing at least part of the mobility operation also includes requesting a core network entity associated with the UE to release the UE to an idle mode.

[0181] In a twelfth aspect, either alone or in combination with one or more of aspects 1 to eleven, process 1100 comprises requesting capability information from a core network entity, wherein the capability information is not received from the core network entity, and wherein performing at least a portion of the mobility operation further comprises requesting the core network entity to release the UE to an idle mode.

[0182] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be performed in parallel.

[0183] Fig.12 1 is a diagram illustrating an example process 1200 performed, for example, by a UE according to the present disclosure. The example process 1200 is a diagram in which a UE (e.g., UE 120, Figure 5 An example of a UE, UE 605, UE 705, UE 805, UE 905) performing operations associated with terrestrial network and non-terrestrial network mobility.

[0184] like Fig.12As shown in FIG. 1 , in some aspects, process 1200 may include receiving a trigger for a mobility operation associated with transferring a UE between an NTN and a TN (block 1210). For example, a UE (e.g., using Fig.14 The communication manager 140 and / or receiving component 1402 depicted in FIG. 1 may receive a trigger for a mobility operation associated with the UE from an NTN to a TN or from a TN to an NTN, as described above. The trigger may include, for example, a handover command received from a network node (such as a source network node or a target network node described elsewhere herein). The mobility operation may include a handover, an RRC re-establishment, a redirection, and the like.

[0185] like Fig.12 As further shown in FIG. 1 , in some aspects, process 1200 may include performing at least a portion of the mobility operation based at least in part on having sent capability information indicating capabilities of the UE associated with the mobility operation (block 1220). Fig.14 140 and / or mobility component 1408) may perform at least a portion of the mobility operation based at least in part on having sent capability information indicating capabilities of the UE associated with the mobility operation, as described above. For example, the UE may remember (e.g., store information indicating) whether the UE reported capability information only in the TN, only in the NTN, or in both the TN and the NTN. If the UE has sent capability information to a network node associated with the network (e.g., the TN or the NTN), and if a trigger for the mobility operation is received from the network node associated with the network, the UE may perform at least a portion of the mobility operation for the network.

[0186] like Fig.12 As further shown in FIG. 1 , in some aspects, process 1200 may include suspending the mobility operation based at least in part on not having sent capability information (block 1230). Fig.14 ) may suspend the mobility operation based at least in part on not having sent the capability information, as described above. If the UE has not sent the capability information to a network node associated with the network (e.g., TN or NTN), and if a trigger for the mobility operation is received from the network node associated with the network, the UE may suspend the mobility operation for the network (e.g., may ignore the trigger).

[0187] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0188] In a first aspect, suspending the mobility operation further comprises suspending the mobility operation based at least in part on receiving a trigger from a network node and based at least in part on not having sent capability information to the network node from which the trigger was received.

[0189] In a second aspect, alone or in combination with the first aspect, suspending the mobility operation further comprises initiating a tracking area update procedure. For example, if the UE has not reported capability information to a network from which a trigger for the mobility operation has been received (e.g., associated with a transfer from an NTN to a TN or from a TN to an NTN), the UE may initiate a tracking area update procedure.

[0190] In a third aspect, alone or in combination with one or more of the first and second aspects, the mobility operation is a radio resource control re-establishment after a radio link failure. For example, after a radio link failure, if the UE has not reported capability information to the network in which the UE experienced the radio link failure, the UE may abort the triggered RRC re-establishment and initiate a tracking area update procedure.

[0191] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1200 includes sending the capability information during a tracking area update procedure. For example, during a tracking area update procedure associated with a network, the UE may trigger a UE capability update procedure for the network. In this example, the UE may include the capability information in an uplink message (e.g., associated with a tracking area update procedure) without receiving a network request, which may save the overhead associated with the UE reporting the capability after receiving a network request (because a network request does not need to be sent).

[0192] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1200 includes sending information indicating a preference associated with performing a mobility operation prior to receiving a trigger, wherein the mobility operation includes a redirection based at least in part on the preference. For example, the preference may indicate whether the UE prefers to perform a handover from the NTN to the TN (e.g., separate from the capability for the mobility operation). If the preference indicates that the handover is not to be performed, the network (e.g., a source network node, as described elsewhere herein) may release the UE by redirection, as described elsewhere herein. For example, the network may release the UE by redirection, rather than performing a basic handover (e.g., with minimum capabilities, as described elsewhere herein). In this case, the network may not know which TN bands the UE supports or does not support, or whether the UE supports 5GC. Therefore, the network may release the UE by redirection to the NTN, so that the UE can determine whether to connect to the redirection cell or target cell associated with the release.

[0193] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the trigger indicates a cell identifier and a RAT type of a target network node for the mobility operation, wherein the RAT type indicates whether the target network node is associated with a TN or an NTN.

[0194] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the trigger comprises an early data transmission completion message or a pre-configured uplink resource completion message (e.g., as described in relation to Fig. 9 described).

[0195] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1200. Additionally or alternatively, two or more blocks of the blocks of process 1200 may be performed in parallel.

[0196] Fig.13 1 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a network node, or a network node may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and transmitting component 1304. As further shown, apparatus 1300 may include a communication manager 150. Communication manager 150 may include one or more of a mobility component 1308 or a triggering component 1310, among others.

[0197] In some aspects, the apparatus 1300 may be configured to perform Figures 4 to 9 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.10 The process of 1000 Fig.11 In some aspects, Fig.13 The apparatus 1300 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown in the figure may be combined with Figure 2Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0198] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0199] The transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1306. In some aspects, one or more other components of the device 1300 may generate communications and may provide the generated communications to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1306. In some aspects, the transmitting component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0200] Receiving component 1302 can attempt to obtain capability information related to a mobility operation of the UE transferring from the NTN to the TN. Mobility component 1308 can perform at least a portion of the mobility operation based at least in part on the capability information or attempt to obtain the capability information.

[0201] The triggering component 1310 can trigger a mobility operation associated with transferring the UE from the NTN to the TN based at least in part on at least one of the following: capability information associated with the UE and related to the mobility operation, or whether the capability information can be used for the network node. The sending component 1304 can output a message for the UE based at least in part on the capability information.

[0202] Fig.13 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.13 Two or more components shown in may be implemented in a single component, or Fig.13 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The assembly of (one or more) components shown in the executable is described as being composed of Fig.13 Another collection of components shown in the figure performs one or more functions.

[0203] Fig.14 1 is a diagram of an example apparatus 1400 for wireless communication according to the present disclosure. Apparatus 1400 may be a UE, or a UE may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402 and a transmitting component 1404 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using receiving component 1402 and transmitting component 1404. As further shown, apparatus 1400 may include a communication manager 140. Communication manager 140 may include mobility component 1408, among other things.

[0204] In some aspects, the apparatus 1400 may be configured to perform Figures 4 to 9 Additionally or alternatively, the apparatus 1400 may be configured to perform one or more of the processes described herein (such as Fig.12 In some aspects, the apparatus 1400 and / or Fig.14 One or more of the components shown in the figure may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Fig.14 One or more of the components shown in the figure may be combined with Figure 2Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0205] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1406. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1400. In some aspects, the receiving component 1402 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the UE.

[0206] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some aspects, one or more other components of the device 1400 may generate communications and may provide the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE. In some aspects, the transmit component 1404 can be co-located with the receive component 1402 in a transceiver.

[0207] The receiving component 1402 can receive a trigger for a mobility operation from the NTN to the TN associated with the apparatus 1400. The mobility component 1408 can perform at least a portion of the mobility operation based at least in part on having sent capability information indicating capabilities of the UE associated with the mobility operation. Alternatively, the mobility component 1408 can abort the mobility operation based at least in part on not having sent the capability information.

[0208] Sending component 1404 can send the capability information during a tracking area update procedure.

[0209] The sending component 1404 can send information indicating a preference associated with performing the mobility operation prior to receiving the trigger, wherein the mobility operation includes redirection based at least in part on the preference.

[0210] Fig.14 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.14 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.14 Two or more components shown in may be implemented in a single component, or Fig.14 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.14 The assembly of (one or more) components shown in the executable is described as being composed of Fig.14 Another collection of components shown in the figure performs one or more functions.

[0211] The following provides an overview of some aspects of the disclosure:

[0212] Aspect 1: A method of wireless communication performed by a network node, the method comprising: attempting to obtain capability information related to a mobility operation of a user equipment (UE) transferred between a non-terrestrial network (NTN) and a terrestrial network (TN); and performing at least a portion of the mobility operation based at least in part on the capability information or attempting to obtain the capability information.

[0213] Aspect 2: A method according to Aspect 1, wherein the capability information indicates whether the UE supports transfer from an NTN to a TN radio access technology associated with at least one of an evolved packet core (EPC), a 5G core, or an evolved universal mobile telecommunications system (UMTS) terrestrial radio access technology.

[0214] Aspect 3: The method according to any one of aspects 1 to 2, wherein attempting to obtain the capability information further comprises requesting the capability information from a core network entity.

[0215] Aspect 4: A network node according to aspect 3, wherein the network node is a target network node for the mobility operation, and wherein requesting the capability information from the core network entity is at least partly based on an indication from a source network node of the UE that the capability information is not available at the source network node.

[0216] Aspect 6: The method of aspect 4, wherein the indication that the capability information is not available at the source network node is an indication that the source network node is associated with a different network type than the target network node.

[0217] Aspect 7: The method according to aspect 3, wherein requesting the capability information from the core network entity is based at least in part on the mobility operation being from the NTN to the TN.

[0218] Aspect 8: According to the method of aspect 7, the method also includes: determining that the mobility operation is from the NTN to the TN based at least in part on an indication from a source network node of the UE as to whether the source network node is associated with the NTN or the TN.

[0219] Aspect 9: According to any one of the methods in Aspects 1 to 8, the method also includes: the capability information cannot be obtained, wherein performing at least part of the mobility operation also includes: triggering a handover associated with the minimum required capability of the radio resource control (RRC) connection based at least in part on the inability to obtain the capability information.

[0220] Aspect 10: A method according to any one of Aspects 1 to 8, wherein the capability information indicates that the UE does not support the frequency band of the target radio access technology of the TN and the NTN, and wherein performing at least part of the mobility operation also includes requesting a source network node or core network entity associated with the UE to release the UE to idle mode.

[0221] Aspect 11: The method according to any one of aspects 1 to 10, wherein attempting to obtain the capability information comprises receiving the capability information from a core network entity.

[0222] Aspect 12: The method according to aspect 11, wherein performing at least a portion of the mobility operation includes at least one of: outputting an acknowledgement associated with the capability information, or synchronizing with the UE.

[0223] Aspect 13: According to any one of aspects 1 to 8, the method also includes: failing to obtain the capability information, wherein performing at least part of the mobility operation also includes: initiating redirection of the UE based at least in part on failing to obtain the capability information.

[0224] Aspect 14: The method according to aspect 13, wherein initiating the redirection further comprises providing a radio resource control (RRC) release message with redirection information to the UE.

[0225] Aspect 15: A method according to Aspect 14, wherein the redirection information includes one or more of the following: a dedicated frequency priority list of the TN, a dedicated frequency priority list of the NTN, or an NTN indication in an existing dedicated frequency priority list, the NTN indication indicating whether the existing dedicated frequency priority list is used for the NTN or for the TN.

[0226] Aspect 16: The method according to aspect 13, wherein initiating the redirection further comprises: providing a handover failure message indicating a release cause associated with an inability to obtain the capability information to a source network node of the UE.

[0227] Aspect 17: The method according to aspect 13, wherein initiating the redirection of the UE further comprises: providing a non-access stratum (NAS) message to a source network node of the UE.

[0228] Aspect 18: The method according to any one of aspects 1 to 17, wherein the mobility operation comprises a handover or redirection from a cell associated with the NTN to a cell associated with the TN.

[0229] Aspect 19: A method of wireless communication performed by a network node, the method comprising: triggering a mobility operation associated with transferring a user equipment (UE) between a non-terrestrial network (NTN) and a terrestrial network (TN) based at least in part on at least one of: capability information associated with the UE and related to the mobility operation, or whether the capability information can be used for the network node; and outputting a message for the UE based at least in part on the capability information.

[0230] Aspect 20: The method according to aspect 19, wherein triggering the mobility operation further comprises: outputting a handover request including an empty UE capability container to a target network node of the mobility operation based at least in part on the capability information being unavailable for the network node.

[0231] Aspect 21: According to any one of Aspects 19 to 20, the method also includes: obtaining an indication from the target network node of the mobility operation to release the UE to idle mode based at least in part on the capability information indicating that the UE cannot be transferred from the NTN to the TN.

[0232] Aspect 22: The method according to any one of aspects 19 to 21, further comprising: requesting the capability information from a core network entity based at least in part on the capability information being unavailable for the network node.

[0233] Aspect 23: The method according to aspect 22, the method also includes: determining that the capability information is not received, wherein the message includes an indication to cause the UE to enter an idle mode based at least in part on the capability information being unavailable for the network node.

[0234] Aspect 24: The method according to any one of aspects 19 to 23, wherein triggering the mobility operation further comprises outputting a handover required message to a core network entity.

[0235] Aspect 25: The method according to aspect 24, wherein the handover required message indicates that the mobility operation is from the NTN to the TN.

[0236] Aspect 26: According to any one of Aspects 19 to 25, the method also includes: obtaining an indication from a target network node of the mobility operation to initiate redirection of the UE, wherein the indication indicates that the target network node cannot obtain the capability information, and wherein the message for the UE includes a radio resource control (RRC) connection release.

[0237] Aspect 27: A method according to any one of Aspects 19 to 26, wherein triggering the mobility operation also includes outputting, for a target network node of the mobility operation, an early data transmission configuration or preconfigured uplink resources for a radio resource control (RRC) establishment completion message of the UE associated with the mobility operation, and wherein the message includes an RRC connection establishment message associated with the mobility operation.

[0238] Aspect 28: The method according to aspect 27 further comprises: obtaining the RRC connection establishment message from the target network node before outputting the RRC connection establishment message.

[0239] Aspect 29: The method according to aspect 27, wherein the mobility operation omits a random access channel (RACH) procedure.

[0240] Aspect 30: A method according to any one of Aspects 19 to 29, wherein the capability information indicates that the UE does not support the frequency band of the target radio access technology of the TN and the NTN, and wherein performing at least part of the mobility operation also includes requesting a core network entity associated with the UE to release the UE to an idle mode.

[0241] Aspect 31: According to the method described in any one of Aspects 19 to 30, the method also includes: requesting the capability information from a core network entity, wherein the capability information is not received from the core network entity, and wherein performing at least part of the mobility operation also includes requesting the core network entity to release the UE to idle mode.

[0242] Aspect 32: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a trigger for a mobility operation between a non-terrestrial network (NTN) and a terrestrial network (TN) associated with the UE; and performing at least a portion of the mobility operation based at least in part on having sent capability information indicating the capability of the UE associated with the mobility operation, or terminating the mobility operation based at least in part on not having sent the capability information.

[0243] Aspect 33: A method according to Aspect 32, wherein terminating the mobility operation further comprises: terminating the mobility operation based at least in part on receiving the trigger from the network node and at least in part on not having sent capability information associated with a target network type of the mobility operation.

[0244] Aspect 34: The method according to any one of aspects 32 to 33, wherein suspending the mobility operation further comprises initiating a tracking area update procedure.

[0245] Aspect 35: The method according to any one of aspects 32 to 34, wherein the mobility operation is radio resource control re-establishment following a radio link failure.

[0246] Aspect 36: The method according to any one of aspects 32 to 35, the method further comprising: sending the capability information during a tracking area update procedure.

[0247] Aspect 37: A method according to any one of Aspects 32 to 36, the method further comprising: before receiving the trigger, sending information indicating a preference associated with performing the mobility operation, and wherein the mobility operation includes a redirection based at least in part on the preference.

[0248] Aspect 38: A method according to any one of Aspects 32 to 37, wherein the trigger indicates a cell identifier and a radio access technology (RAT) type of a target network node for the mobility operation, wherein the RAT type indicates whether the target network node is associated with the TN or the NTN.

[0249] Aspect 39: The method according to aspect 38, wherein the trigger comprises an early data transmission completion message or a pre-configured uplink resource completion message.

[0250] Aspect 40: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 39.

[0251] Aspect 41: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 39.

[0252] Aspect 42: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 39.

[0253] Aspect 43: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 39.

[0254] Aspect 44: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 39.

[0255] Aspect 45: The method according to one or more of aspects 1 to 39, wherein the capability information indicates whether the UE supports the same capability set to perform mobility operations for the NTN radio access technology and the TN radio access technology.

[0256] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0257] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be clear that the system and / or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code to describe the operation and behavior of the system and / or method herein, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0258] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0259] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the item list refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other sorting of a, b and c).

[0260] Any element, action or instruction used herein should not be interpreted as key or necessary, unless otherwise explicitly stated. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms are used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to: attempting to obtain capability information related to mobility operations of a user equipment (UE) transferred between a non-terrestrial network (NTN) and a terrestrial network (TN); as well as At least a portion of the mobility operation is performed based at least in part on the capability information or attempting to obtain the capability information.

2. The network node of claim 1 , wherein the capability information indicates whether the UE supports a transfer from an NTN to a TN radio access technology associated with at least one of an evolved packet core (EPC), a 5G core, or an evolved universal mobile telecommunications system (UMTS) terrestrial radio access technology. 3 . The network node according to claim 2 , wherein the capability information indicates whether the UE supports the same capability set for performing mobility operations for the NTN radio access technology and the TN radio access technology. 4 . The network node of claim 1 , wherein to attempt to obtain the capability information, the one or more processors are configured to request the capability information from a core network entity.

5. The network node of claim 4, wherein the network node is a target network node for the mobility operation, and wherein requesting the capability information from the core network entity is based at least in part on an indication from a source network node of the UE that the capability information is not available at the source network node.

6. The network node of claim 5, wherein the indication that the capability information is not available at the source network node is an omission of the radio capabilities of the UE in a handover prepare message.

7. The network node of claim 5, wherein the indication that the capability information is not available at the source network node is an indication that the source network node is associated with a different network type than the target network node.

8. The network node of claim 4, wherein requesting the capability information from the core network entity is based at least in part on the mobility operation being from the NTN to the TN.

9. The network node of claim 1 , wherein the one or more processors are further configured to be unable to obtain the capability information, wherein to perform at least a portion of the mobility operation, the one or more processors are further configured to trigger a handover associated with a minimum required capability of a radio resource control (RRC) connection based at least in part on the inability to obtain the capability information.

10. The network node of claim 1 , wherein the capability information indicates that the UE does not support frequency bands of target radio access technologies of the TN and the NTN, and wherein in order to perform at least a portion of the mobility operation, the one or more processors are configured to request a source network node or a core network entity associated with the UE to release the UE to an idle mode.

11. The network node of claim 1, wherein to attempt to obtain the capability information, the one or more processors are configured to receive the capability information from a core network entity.

12. The network node of claim 1 , wherein the one or more processors are further configured to be unable to obtain the capability information, wherein to perform at least a portion of the mobility operation, the one or more processors are further configured to initiate a redirection of the UE based at least in part on the inability to obtain the capability information.

13. The network node of claim 12, wherein to initiate the redirection, the one or more processors are configured to provide a radio resource control (RRC) release message with redirection information to the UE.

14. The network node according to claim 13, wherein the redirection information comprises one or more of the following: The TN's dedicated frequency priority list, the NTN's dedicated frequency priority list, or An NTN indication in the existing dedicated frequency priority list, the NTN indication indicating whether the existing dedicated frequency priority list is for the NTN or for the TN.

15. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to: Triggering a mobility operation associated with transferring a user equipment (UE) between a non-terrestrial network (NTN) and a terrestrial network (TN) based at least in part on at least one of: capability information associated with the UE and relevant to the mobility operation, or whether the capability information can be used for the network node; as well as A message for the UE is output based at least in part on the capability information.

16. The network node of claim 15, wherein to trigger the mobility operation, the one or more processors are configured to output a handover request including an empty UE capabilities container to a target network node of the mobility operation based at least in part on the capability information being unavailable for the network node.

17. The network node of claim 15, wherein the one or more processors are further configured to obtain an indication from a target network node of the mobility operation to release the UE to idle mode based at least in part on the capability information indicating that the UE cannot be transferred from the NTN to the TN.

18. The network node of claim 15, wherein the one or more processors are further configured to request the capability information from a core network entity based at least in part on the capability information being unavailable for the network node.

19. The network node of claim 15, wherein to trigger the mobility operation, the one or more processors are configured to output a handover required message to a core network entity.

20. The network node of claim 15, wherein the one or more processors are further configured to obtain an indication from a target network node of the mobility operation to initiate redirection of the UE, wherein the indication indicates that the target network node is unable to obtain the capability information, and wherein the message for the UE comprises a radio resource control (RRC) connection release.

21. The network node of claim 15, wherein triggering the mobility operation further comprises outputting, for a target network node of the mobility operation, an early data transmission configuration or preconfigured uplink resources for a radio resource control (RRC) setup complete message of the UE associated with the mobility operation, and wherein the message comprises an RRC connection setup message associated with the mobility operation.

22. The network node of claim 15, wherein the capability information indicates that the UE does not support frequency bands of target radio access technologies of the TN and the NTN, and wherein in order to perform at least a portion of the mobility operation, the one or more processors are configured to request a core network entity associated with the UE to release the UE to an idle mode.

23. The network node of claim 15, wherein the one or more processors are further configured to request the capability information from a core network entity, wherein the capability information is not received from the core network entity, and wherein at least a portion of the mobility operation is performed, wherein the one or more processors are further configured to request the core network entity to release the UE to an idle mode.

24. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a trigger for a mobility operation associated with the UE between a non-terrestrial network (NTN) and a terrestrial network (TN); as well as performing at least a portion of the mobility operation based at least in part on having sent capability information indicating capabilities of the UE associated with the mobility operation, or The mobility operation is suspended based at least in part on not having sent the capability information.

25. The UE of claim 24, wherein to suspend the mobility operation, the one or more processors are configured to suspend the mobility operation based at least in part on receiving the trigger from a network node and at least in part on not having sent capability information associated with a target network type for the mobility operation.

26. The UE of claim 24, wherein to suspend the mobility operation, the one or more processors are configured to initiate a tracking area update procedure.

27. The UE of claim 24, wherein the mobility operation is radio resource control re-establishment following a radio link failure.

28. A method of wireless communication performed by a network node, the method comprising: attempting to obtain capability information related to mobility operations of a user equipment (UE) transferred between a non-terrestrial network (NTN) and a terrestrial network (TN); as well as At least a portion of the mobility operation is performed based at least in part on the capability information or attempting to obtain the capability information.

29. The method of claim 28, wherein the capability information indicates whether the UE supports transfer from an NTN to a TN radio access technology associated with at least one of an evolved packet core (EPC), a 5G core, or an evolved universal mobile telecommunications system (UMTS) terrestrial radio access technology.

30. The method of claim 28, wherein attempting to obtain the capability information further comprises requesting the capability information from a core network entity.

Images