RRC reconstruction between TN and ntn

By using information identifying the source network during the RRC reconstruction process between TN and NTN, the connection interruption problem of UE when moving between TN and NTN is solved, and the stability of seamless switching and data transmission is achieved.

CN118975393APending Publication Date: 2024-11-15QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380029380.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-30
Filing Date
2023-03-24
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

In a wireless communication system, when the UE moves between TN and NTN, the RRC reconstruction process may cause the target network to fail to determine the source network for registering the update request, resulting in lost pending data and interruption of connection.

Method used

Provides a method that allows the UE to perform an RRC reconstruction process between TN and NTN. By including information identifying the source network in the RRC connection request, the target network can identify the source network and reconfigure resources to ensure the transmission of pending data and Connection stability.

Benefits of technology

The seamless switching between TN and NTN is realized, which avoids pending data loss and improves the stability and reliability of network connections.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118975393A_ABST
    Figure CN118975393A_ABST
Patent Text Reader

Abstract

A method and apparatus for an RRC reestablishment procedure between a TN and an NTN. The apparatus may be on a first network associated with one of the TN or the NTN. The apparatus transmits an RRC connection request for establishing a connection with a second network associated with one of the NTN or the TN. The apparatus receives an RRC reconnection message from a network entity associated with the second network. The apparatus sends an RRC reconnection completion message to the network entity associated with one of the NTN or the TN of the second network. The apparatus may send a registration update request to the network entity associated with one of the NTN or the TN of the second network.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 657,334, filed on March 30, 2022, and entitled “RRC REESTABLISHMENT BETWEENTN AND NTN,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to configurations for radio resource control (RRC) re-establishment between a terrestrial network (TN) and a non-terrestrial network (NTN). Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus at a UE. The apparatus may be a processor and / or a modem at the UE or the UE itself. The apparatus may be a UE on a first network associated with one of a terrestrial network (TN) or a non-terrestrial network (NTN). The apparatus sends a radio resource control (RRC) connection request for establishing a connection with a second network associated with one of the NTN or the TN. The apparatus receives an RRC reconnection message from a network entity associated with the second network. The apparatus sends an RRC reconnection completion message to the network entity associated with one of the NTN or the TN of the second network.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a network entity. The apparatus may be a processor and / or a modem at a network entity or the network entity itself. The apparatus may be a network entity on a second network associated with one of a non-terrestrial network (NTN) or a terrestrial network (TN). The apparatus receives a radio resource control (RRC) connection request for establishing a connection with the second network from a user equipment (UE) on a first network associated with one of the TN or the NTN. The apparatus sends an RRC reconnection message in response to receiving the RRC connection request. The apparatus receives an RRC reconnection completion message from the UE previously associated with the first network.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2Dis a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 is a diagram illustrating examples of TN and NTN systems.

[0017] Figure 5 is a diagram illustrating an example of a reconstruction information element (IE).

[0018] Figure 6 is a diagram illustrating an example of rebuilding IE.

[0019] Figure 7 It is a call flow diagram of signaling between UE and network entity.

[0020] Figure 8 is a flow chart of a method of wireless communication.

[0021] Fig. 9 is a flow chart of a method of wireless communication.

[0022] Fig.10 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0023] Fig.11 is a flow chart of a method of wireless communication.

[0024] Fig.12 is a flow chart of a method of wireless communication.

[0025] Fig.13 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0026] In wireless communication, UE can access different networks. For example, UE can access TN and NTN systems. In some cases, the mobility management entity (MME) of the core network can support both TN and NTN systems, so that MME is connected to both TN and NTN systems. In some cases, the base station can also be configured to support connections via both TN and NTN systems. In some cases, such as when UE enters a radio link failure state, a suspended state, or an RRC inactive state in one network (e.g., TN or NTN), the UE may be able to continue to connect in other networks (e.g., NTN or TN). However, when moving between TN and NTN, UE will need to trigger registration updates, because handover is considered to be a radio access technology (RAT) inter-cell selection, and RRC reconstruction may be impossible. The target network (e.g., NTN) may be confused by the registration update request from the UE because the target network may not be able to determine whether the registration update request is from the same or different network (e.g., TN). The aspects given herein provide a configuration that allows RRC reconstruction between TN and NTN. The aspects given herein may allow UE to perform an RRC reconstruction process between different network types. For example, the UE may perform an RRC re-establishment procedure when moving from a TN to an NTN, or vice versa.At least one advantage of the present disclosure is that the UE may perform an RRC re-establishment and switch between a TN and an NTN without losing pending data packets.

[0027] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0028] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any 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.

[0029] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, functions, or any combination thereof.

[0030] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. For example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0031] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, clustered or disaggregated components, end-user devices, etc.

[0032] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts 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 radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0033] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0034] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access and backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0035] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0036] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0037] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 110. CU110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 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 110 may be implemented to communicate with DU 130 for network control and signaling.

[0038] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by 3GPP. In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

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

[0040] The SMO framework 105 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 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 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) 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 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 111 via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0041] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 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 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

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

[0043] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may pass through one or more carriers. For each carrier allocated in a carrier aggregation of up to YxMHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to YMHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0044] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0045] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

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

[0047] 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, and therefore 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 FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0048] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0049] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0050] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a clustered (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or clustered base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0051] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculation based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0052] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0053] Refer again Figure 1 In certain aspects, the UE 104 may include a request component 198 configured to: send a radio resource control (RRC) connection request for establishing a connection with a second network associated with one of the NTN or the TN; receive an RRC reconnection message from a network entity associated with the second network; and send an RRC reconnection complete message to a network entity associated with one of the NTN or the TN of the second network.

[0054] Refer again Figure 1 In certain aspects, the base station 102 may include a connection component 199 configured to: receive an RRC connection request for establishing a connection with a second network from a UE on a first network associated with one of the TN or the NTN; send an RRC reconnection message in response to receiving the RRC connection request; and receive an RRC reconnection complete message from a UE previously associated with the first network.

[0055] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0056] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2CFIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0057] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of equal size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0058]

[0059] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0060] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0061] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0062] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.

[0063] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the combs in the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0064] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0065] Figure 3 3 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0066] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived based on reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0067] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0068] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0069] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0070] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0071] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0072] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0073] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The request component 198 combines various aspects.

[0074] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The connection assembly 199 combines various aspects.

[0075] In wireless communication, a UE may access different networks. For example, a UE may access a TN system and an NTN system. In some cases, a mobility management entity (MME) of a core network may support both the TN system and the NTN system, so that the MME is connected to both the TN system and the NTN system. Figure 4 400, a base station 402 may provide a first cell 404 as part of a TN system, and a satellite 406 may provide a second cell 408 as part of an NTN system. A UE 410 may be able to connect to the first cell 404 or the second cell 408. The base station 402 may communicate with an MME 416. The satellite 406 may also communicate with the MME 416 via a gateway 412 and a base station 414 that provide a communication link between the MME 416 and the satellite 406. In some cases, the base station may also be configured to support connections via both TN and NTN systems.

[0076] UE 410 may be configured with an equivalent PLMN belonging to both TN and NTN, so that the PLMN supports both TN and NTN. In such cases, when UE 410 enters a radio link failure state, a suspended state, or an RRC inactive state in one network (e.g., TN or NTN), the UE may be able to continue to connect in other networks (e.g., NTN or TN). However, when moving between TN and NTN, the UE will need to trigger a registration update, because the handover is considered to be a radio access technology (RAT) inter-cell selection, and RRC reconstruction may not be possible. Initiating a registration update may result in pending downlink data loss. In some cases, when moving from a TN to an NTN, the UE (e.g., a narrowband (NB) IoT using a control plane (CP) cellular IoT (CIoT)) may be allowed to continue RRC reconstruction, because RRC reconstruction is based on the mobility of the MME.

[0077] When resuming from a suspended state or reestablishing a connection after a radio link failure, the target network may be confused about the registration update request from the UE because the target network may not be able to determine whether the registration update request is from the same or different network. This confusion may cause the target network to reject the registration update request from the UE. However, a target network rejection is unnecessary and should be avoided.

[0078] In the case where the UE is performing a reestablishment procedure, the target network entity may identify the source network entity based on the identifier provided by the UE in the request message. Figure 5 500, the request message may include an indication 502 including a Request UE-Identity that may identify a source network entity of the UE. The target network entity may retrieve the UE capabilities and any pending downlink packets to be delivered to the UE based on the indication 502. The Request UE-Identity includes a C-RNTI and a physical (PHY) cell identifier (ID), but the target network entity may not be able to determine whether a particular combination of C-RNTI and PHY cell ID is associated with a TN or NTN system. Problems may arise when the C-RNTI is the same between the TN and the NTN. Similar problems may occur if the UE is resumed from a suspended state or an RRC inactive state.

[0079] Aspects presented herein provide configurations that allow RRC reestablishment between TN and NTN. Aspects presented herein may allow a UE to perform an RRC reestablishment procedure between different network types. For example, a UE may perform an RRC reestablishment procedure when moving from a TN to an NTN, or vice versa. At least one advantage of the present disclosure is that a UE may perform an RRC reestablishment and switch between a TN and an NTN without losing pending data packets.

[0080] In the case where the UE selects a cell belonging to a different network, the target network may configure a different set of tracking area identifiers for the UE so that the UE can trigger a registration update. The UE that initially selects a cell on TN to NTN indicates to the UE that the UE has moved out of its registration area. The target network may indicate in the system information whether the cell associated with the target network supports reconstruction between TN and NTN, which may be for each public land mobile network (PLMN). In such a case, the UE may continue to reconstruct or recover, and after a successful connection, the UE may transmit a registration update request. The RRC reconstruct complete message (e.g., Msg5, ACK for Msg4) may be extended to include DedicatedInfoNAS to carry the registration update request. The network may identify the change of TN / NTN and provide the UE with a larger grant (e.g., uplink shared channel (UL-SCH) resources) to include a non-access stratum (NAS) packet data unit.

[0081] To avoid delays in pending downlink data delivery, the RRC reestablishment message in the downlink (e.g., Msg4) may also be extended to include DedicatedInfoNAS to carry any downlink NAS PDUs. This may be allowed before the UE transmits a Tracking Area Update or Registration Update request to the core network. In some cases, a Registration Request (e.g., TAU request) procedure may take precedence over any uplink or downlink data transmission. In some cases, uplink or downlink data transmission may take precedence over a Registration Request.

[0082] In some aspects, the UE may continue the reestablishment or recovery process without transmitting a registration update request. In such cases, the core network may detect that the UE has changed the tracking area configuration and implicitly configure a new registration area for the new network for the UE when the UE is in the RRC connected state.

[0083] In some aspects, the UE may abort the reestablishment or recovery process and may enter an RRC idle state. In such cases, the UE may restart the cell selection process and select a new cell belonging to a different network (e.g., TN or NTN). In the event that the UE selects a cell associated with a different network, the UE may abort the reestablishment or recovery process. For example, the UE may be on the TN and select a cell associated with the NTN in the process of selecting a new cell, and the UE may abort the reestablishment or recovery process in response to selecting the cell associated with the NTN.

[0084] In some aspects, to determine network differentiation, the network may blindly poll one or more base stations in the target network and the source network that may know the PHY cell ID and C-RNTI of the UE. For example, the target network (e.g., NTN) may poll base stations of the NTN and the source network (TN). In some cases, there may be another combination of the same cell ID and C-RNTI used by another UE, and the MAC-I cannot be verified.

[0085] In some aspects, to determine network differentiation, the network may provide PHY cell IDs between the TN and NTN such that there is no overlap of PHY cell IDs between the TN and NTN. In some cases, the PHY cell IDs may be grouped between the TN and NTN. In such cases, the network may determine based on the PHY cell ID whether the UE was previously connected to the TN or NTN. In some cases, the UE may have previously been connected to a high altitude platform system (HAPS), where the PHY cell IDs may overlap or move apart when the target network attempts to interrogate; grouping of the PHY cell IDs between the TN and NTN may resolve such issues.

[0086] In some aspects, the PHY cell IDs for TN and NTN may include integer identifiers. The integer identifier (e.g., PhysCellIdNR-r15, PhysCellIdNTN-r17) may allow identification of the source network (e.g., TN or NTN). The identifier may be included in the RRC connection reestablishment request. For example, a new key extension may be defined in the RRC connection reestablishment request including the identifier. System information may be configured to indicate whether the cell supports integer identifiers.

[0087] In some aspects, the RRC Reestablishment Request message may include a flag identifier. The flag identifier may indicate that the UE is reestablishing a connection from a different network. For example, if the RRC Reestablishment Request message is transmitted to the NTN, the UE was previously on the TN. The flag identifier may be included in the spare bit. Figure 6 In the diagram 600, the alternate 604 of the RRC reestablishment request message 602 may be used as a flag identifier. In such a case, if the target network does not support the reestablishment between the TN and the NTN, the target network may transmit a rejection message or an RRC connection establishment message.

[0088] In some aspects, dedicated or PRACH partitioning may be used to differentiate. For example, dedicated or PRACH partitioning may be used to differentiate from Msg1.

[0089] Figure 7 700 is a call flow diagram of signaling between a UE 702 and a network entity (eg, a base station) 704. The UE 702 may be configured to communicate with the base station 704. For example, in Figure 1 In the context of , base station 704 may correspond to base station 102. In addition, UE 702 may correspond to at least UE 104. In another example, in Figure 3 In the context of , base station 704 may correspond to base station 310 and UE 702 may correspond to UE 350.

[0090] At 706, the UE may send an RRC connection request for establishing a connection with a second network associated with one of the NTN or TN. The UE may be on a first network associated with one of the TN or NTN. The UE may send an RRC connection request to a network entity associated with the second network (e.g., base station 704). The base station 704 may receive the RRC connection request from the UE 702. In some aspects, the RRC connection request may include at least one of an RRC reestablishment request or an RRC recovery request. In some aspects, the RRC reconnect message may include one or more downlink NAS packet data units. In some aspects, the RRC connection request includes a physical (PHY) cell identifier (ID) for one of the NTN or TN of the first network and a PHY cell ID for one of the NTN or TN of the second network. For example, the PHY cell ID may include an integer value identifying the NTN and / or an integer value identifying the TN. In some aspects, the system information may indicate whether the cell associated with the network supports PHY cell IDs for TN and NTN. In some aspects, the RRC connection request may include a network field indicating that the UE was previously connected to a TN or NTN associated with the first network. The network field may include a one-bit field. A one-bit field may indicate that the UE is reestablishing a connection from a different network. For example, if the request is transmitted to the NTN, the UE was previously connected to the TN. If the request is transmitted to the TN, the UE was previously connected to the TN. In some aspects, a spare bit may be used for the network field. In some aspects, if the network entity does not support the reconstruction between the TN and the NTN, the network entity may transmit a rejection message or an RRC connection establishment message. In some aspects, a dedicated or physical random access channel (PRACH) partition may be used to distinguish from the RRC connection request. In some cases, a dedicated or PRACH partition may be used to distinguish from a message 1 (Msg1). In some aspects, an RRC connection request for a set of allowed public land mobile networks (PLMNs) may be received. In the case of establishing a connection with a second network from the first network, an RRC connection request for a set of allowed PLMNs may be received. For example, for the allowed PLMN, when moving between TN and NTN, the UE may be allowed to perform RRC reconstruction, or vice versa. The UE may be configured as to whether reconstruction between TN and NTN is allowed. The UE may be configured via RRC signaling or system information. In some aspects, the NTN may include at least one of a low earth orbit (LEO) NTN, a medium earth orbit (MEO) NTN, or a geostationary earth orbit (GEO) NTN. In some aspects, the first network and the second network are associated with different radio access technology (RAT) networks. For example, the UE may be on a first network associated with the TN, while the network entity is on a second network associated with the NTN. In another example, the UE may be on a first network associated with the NTN, while the network entity is on a second network associated with the TN.In some aspects, a timer associated with at least one of a packet data convergence protocol (PDCP), a radio link control (RLC), or a MAC may be adjusted or restarted for unacknowledged data or undelivered data from a first network during a reestablishment process in a second network. A timer associated with at least one of a PDCP, RLC, or MAC may be adjusted based on a new configuration of the second network. For example, in the case of unacknowledged data, a timer (such as, but not limited to, a PDCPDiscardTimer) may continue without restarting, or may be restarted or may be adjusted when a DRB is reconfigured and a data radio bearer (DRB) is reestablished. In addition, the quality of service (QoS) and radio configuration from the second network may be applied to any pending, unacknowledged, and / or undelivered data from the first network.

[0091] At 708, the base station 704 may send an RRC reconnect message in response to receiving the RRC connection request. The base station 704 may send the RRC reconnect message to the UE 702. The UE 702 may receive the RRC reconnect message from the base station 704. In some aspects, the RRC reconnect message may include at least one of an RRC reestablishment message, an RRC resume message, an RRC setup message, or an RRC reject message.

[0092] At 710, UE 702 may send an RRC reconnection complete message to base station 704. Base station 704 is associated with one of the NTN or TN of the second network. Base station 704 may receive an RRC reconnection complete message from UE 702. For example, in the case where the UE is on a first network associated with the TN, the UE may send an RRC reconnection complete message to a network entity on a second network associated with the NTN. In the case where the UE is on a first network associated with the NTN, the UE may send an RRC reconnection complete message to a network entity on a second network associated with the TN. In some aspects, the RRC reconnection complete message may include at least one of an RRC reestablishment complete message, an RRC recovery complete message, or an RRC establishment complete message. In some aspects, the RRC reconnection complete message may be configured to confirm the receipt of the RRC reconnection message. The RRC reconnection complete message may include a registration update request.

[0093] At 712, UE 702 may send a registration update request to a base station 704 associated with one of the NTN or TN of the second network. Base station 704 may receive the registration update request from UE 702. The UE sends the registration update request in response to selecting a cell associated with a different network. For example, a UE previously on a TN selecting a cell on an NTN indicates to the UE that the UE has moved outside its registration area. In some cases, system information provided to the UE may indicate whether a selected cell associated with a different network supports or allows reconstruction between different networks. For example, a UE on a TN may select a cell associated with an NTN of the second network. The NTN may indicate in the system information provided to the UE whether the cell allows reconstruction between the TN and the NTN. In some aspects, the indication indicating whether the selected cell supports or allows reconstruction between different networks (e.g., between the TN and the NTN) may be for each public land mobile network (PLMN).

[0094] At 714, UE 702 may refrain from sending a registration update request. In some aspects, the second network may configure a new registration area for the UE when establishing a connection with one of the TN or NTN associated with the second network so that the UE may refrain from sending a registration update request. For example, the second network may detect that the UE is on a new network and has changed the tracking area configuration, and may configure a new registration area for the second network for the UE when the UE is connected (e.g., RRC_CONNECTED) with the second network.

[0095] At 716, UE 702 may abort the RRC connection procedure. The UE may abort the RRC connection procedure (e.g., a reestablishment or recovery procedure) and enter an idle mode (e.g., RRC_IDLE). In the case where the UE switches networks, the UE may abort the RRC connection procedure. For example, in the case where the UE switches from a TN to an NTN, the UE may abort the RRC connection procedure, or vice versa. The UE may switch from a TN to an NTN in the process of discovering a new cell, and the UE discovers a cell associated with the NTN.

[0096] At 718, UE 702 may select a new cell to establish a new connection. The UE may select a new cell to establish a new connection in response to suspending the RRC connection process. The new cell may be associated with the first network or the second network. The first network or the second network may be associated with one of the TN or the NTN.

[0097] At 720, the base station 704 may poll one or more network entities of the first network and / or the second network. The base station may poll one or more network entities associated with one of the NTN or TN of the first network. The base station may poll one or more network entities associated with one of the NTN or TN of the second network. In some aspects, the base station may poll one or more network entities associated with one of the NTN or TN of the first network and one or more network entities associated with one of the NTN or TN of the second network that know the PHY cell ID and cell radio network temporary identifier (C-RNTI) of the UE. The base station may poll one or more network entities of the first and / or second networks to determine whether the same PHY cell ID and C-RNTI are being used for other UEs.

[0098] At 722, the base station 704 may provide a PHY cell ID between the first network and the second network such that no overlap of the PHY cell ID occurs between the first network and the second network. For example, the first network may include a TN and the second network may include an NTN such that the PHY cell ID may be provided to the TN and the NTN and there is no overlap of the PHY cell ID between the TN and the NTN. In some aspects, the PHY cell ID may be grouped between the TN and the NTN. The PHY cell ID of the UE may indicate which network the UE 702 was previously connected to. For example, the PHY cell ID of the UE may indicate whether the UE was previously connected to the TN or the NTN. In some aspects, the UE may have been previously connected to a high altitude platform system (HAPS), wherein the PHY cell IDs may overlap or move apart when the UE attempts to connect to a target network entity.

[0099] Figure 8 800 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104; device 1004). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow the UE to perform an RRC reestablishment procedure between a TN and an NTN.

[0100] At 802, the UE may send an RRC connection request. For example, 802 may be performed by the request component 198 of the device 1004. The UE may send an RRC connection request for establishing a connection with a second network associated with one of the NTN or TN. The UE may be on a first network associated with one of the TN or NTN. The UE may send an RRC connection request to a network entity associated with the second network. In some aspects, the RRC connection request may include at least one of an RRC reestablishment request or an RRC recovery request. In some aspects, the RRC reconnect message may include one or more downlink NAS packet data units. In some aspects, the RRC connection request includes a PHY cell ID for one of the NTN or TN of the first network and a PHY cell ID for one of the NTN or TN of the second network. For example, the PHY cell ID may include an integer value identifying the NTN and / or an integer value identifying the TN. In some aspects, the system information may indicate whether a cell associated with the network supports PHY cell IDs for TN and NTN. In some aspects, the RRC connection request may include a network field indicating that the UE was previously connected to a TN or NTN associated with the first network. The network field may include a one-bit field. A one-bit field may indicate that the UE is reestablishing a connection from a different network. For example, if the request is transmitted to the NTN network, the UE was previously connected to the TN. In some aspects, a spare bit may be used for the network field. In some aspects, if the network entity does not support the reconstruction between the TN and the NTN, the network entity may transmit a rejection message or an RRC connection establishment message. In some aspects, a dedicated or PRACH partition may be used to distinguish from the RRC connection request. In some cases, a dedicated or PRACH partition may be used to distinguish from Msg1. In some aspects, the NTN may include at least one of LEO NTN, MEO NTN, or GEO NTN. In some aspects, the first network and the second network are associated with different RAT networks. For example, the UE may be on a first network associated with the TN, and the network entity may be on a second network associated with the NTN. In some aspects, a timer associated with at least one of the PDCP, RLC, or MAC may be adjusted or restarted for unconfirmed data or undelivered data from the first network during the reconstruction process in the second network. A timer associated with at least one of the PDCP, RLC, or MAC may be adjusted based on the new configuration of the second network. For example, in the case of unconfirmed data, when the DRB is reconfigured and the DRB is reestablished, a timer (such as but not limited to PDCP DiscardTimer) may be adjusted or restarted. In addition, the QoS and radio configuration from the second network may be applied to any pending, unconfirmed and / or undelivered data from the first network.

[0101] At 804, the UE may receive an RRC reconnect message. For example, 804 may be performed by the request component 198 of the device 1004. The UE may receive the RRC reconnect message from a network entity associated with the second network. In some aspects, the RRC reconnect message may include at least one of an RRC reestablishment message, an RRC resume message, an RRC setup message, or an RRC reject message.

[0102] At 806, the UE may send an RRC reconnection complete message. For example, 806 may be performed by the request component 198 of the device 1004. The UE may send an RRC reconnection complete message to a network entity associated with one of the NTN or TN of the second network. For example, in the case where the UE is on a first network associated with the TN, the UE may send an RRC reconnection complete message to a network entity on a second network associated with the NTN. In the case where the UE is on a first network associated with the NTN, the UE may send an RRC reconnection complete message to a network entity on a second network associated with the TN. In some aspects, the RRC reconnection complete message may include at least one of an RRC reconstruction complete message, an RRC recovery complete message, or an RRC establishment complete message. In some aspects, the RRC reconnection complete message may be configured to confirm the receipt of the RRC reconnection message. The RRC reconnection complete message may include a registration update request.

[0103] Fig. 9 900 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104; device 1004). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow the UE to perform an RRC reestablishment procedure between a TN and an NTN.

[0104] At 902, the UE may send an RRC connection request. For example, 902 may be performed by the request component 198 of the device 1004. The UE may send an RRC connection request for establishing a connection with a second network associated with one of the NTN or TN. The UE may be on a first network associated with one of the TN or NTN. The UE may send an RRC connection request to a network entity associated with the second network. In some aspects, the RRC connection request may include at least one of an RRC reestablishment request or an RRC recovery request. In some aspects, the RRC reconnect message may include one or more downlink NAS packet data units. In some aspects, the RRC connection request includes a PHY cell ID for one of the NTN or TN of the first network and a PHY cell ID for one of the NTN or TN of the second network. For example, the PHY cell ID may include an integer value identifying the NTN and / or an integer value identifying the TN. In some aspects, the system information may indicate whether a cell associated with the network supports PHY cell IDs for TN and NTN. In some aspects, the RRC connection request may include a network field indicating that the UE was previously connected to a TN or NTN associated with the first network. The network field may include a one-bit field. A one-bit field may indicate that the UE is reestablishing a connection from a different network. For example, if the request is transmitted to the NTN network, the UE was previously connected to the TN. In some aspects, a spare bit may be used for the network field. In some aspects, if the network entity does not support the reconstruction between the TN and the NTN, the network entity may transmit a rejection message or an RRC connection establishment message. In some aspects, a dedicated or PRACH partition may be used to distinguish from the RRC connection request. In some cases, a dedicated or PRACH partition may be used to distinguish from Msg1. In some aspects, the NTN may include at least one of LEO NTN, MEO NTN, or GEO NTN. In some aspects, the first network and the second network are associated with different RAT networks. For example, the UE may be on a first network associated with the TN, and the network entity may be on a second network associated with the NTN. In some aspects, a timer associated with at least one of the PDCP, RLC, or MAC may be adjusted or restarted for unconfirmed data or undelivered data from the first network during the reconstruction process in the second network. A timer associated with at least one of the PDCP, RLC, or MAC may be adjusted based on the new configuration of the second network. For example, in the case of unconfirmed data, when the DRB is reconfigured and the DRB is reestablished, a timer (such as but not limited to PDCP DiscardTimer) may be adjusted or restarted. In addition, the QoS and radio configuration from the second network may be applied to any pending, unconfirmed and / or undelivered data from the first network.

[0105] At 904, the UE may receive an RRC reconnect message. For example, 904 may be performed by the request component 198 of the device 1004. The UE may receive the RRC reconnect message from a network entity associated with the second network. In some aspects, the RRC reconnect message may include at least one of an RRC reestablishment message, an RRC resume message, an RRC setup message, or an RRC reject message.

[0106] At 906, the UE may send an RRC reconnection complete message. For example, 906 may be performed by the request component 198 of the device 1004. The UE may send an RRC reconnection complete message to a network entity associated with one of the NTN or TN of the second network. For example, in the case where the UE is on a first network associated with the TN, the UE may send an RRC reconnection complete message to a network entity on a second network associated with the NTN. In the case where the UE is on a first network associated with the NTN, the UE may send an RRC reconnection complete message to a network entity on a second network associated with the TN. In some aspects, the RRC reconnection complete message may include at least one of an RRC reconstruction complete message, an RRC recovery complete message, or an RRC establishment complete message. In some aspects, the RRC reconnection complete message may be configured to confirm the receipt of the RRC reconnection message. The RRC reconnection complete message may include a registration update request.

[0107] At 908, the UE may send a registration update request. For example, 908 may be performed by the request component 198 of the device 1004. The UE may send a registration update request to a network entity associated with one of the NTN or TN of the second network. The UE sends a registration update request in response to selecting a cell associated with a different network. For example, a UE selecting a cell from a TN to an NTN indicates to the UE that the UE has moved outside its registration area. In some cases, the network may indicate in system information whether a selected cell associated with a different network supports or allows reconstruction between different networks. For example, a UE on a TN may select a cell associated with an NTN of the second network. The NTN may indicate in system information provided to the UE whether the cell allows reconstruction between the TN and the NTN. In some aspects, the indication indicating whether the selected cell supports or allows reconstruction between different networks (e.g., between the TN and the NTN) may be for each PLMN.

[0108] At 910, the UE may refrain from sending a registration update request. For example, 910 may be performed by request component 198 of device 1004. In some aspects, the second network may configure a new registration area for the UE when establishing a connection with one of the TN or NTN associated with the second network so that the UE may refrain from sending a registration update request. For example, the second network may detect that the UE is on a new network and has changed the tracking area configuration, and may configure a new registration area for the second network for the UE when the UE is connected (e.g., RRC_CONNECTED) with the second network.

[0109] At 912, the UE may abort the RRC connection procedure. For example, 912 may be performed by the request component 198 of the device 1004. The UE may abort the RRC connection procedure (e.g., a reestablishment or recovery procedure) and enter an idle mode (e.g., RRC_IDLE). In the case where the UE switches networks, the UE may abort the RRC connection procedure. For example, in the case where the UE switches from a TN to an NTN, the UE may abort the RRC connection procedure. The UE may switch from a TN to an NTN in the process of discovering a new cell, and the UE discovers a cell associated with the NTN.

[0110] At 914, the UE may select a new cell to establish a new connection. For example, 914 may be performed by the request component 198 of the device 1004. The UE may select a new cell to establish a new connection in response to suspending the RRC connection process. The new cell may be associated with the first network or the second network. The first network or the second network may be associated with one of the TN or the NTN.

[0111] Fig.101000 is a diagram illustrating an example of a hardware implementation for an apparatus 1004. The apparatus 1004 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1004 may include a cellular baseband processor 1024 (also referred to as a modem) coupled to one or more transceivers 1022 (e.g., a cellular RF transceiver). The cellular baseband processor 1024 may include on-chip memory 1024'. In some aspects, the apparatus 1004 may also include one or more subscriber identity module (SIM) cards 1020 and an application processor 1006 coupled to a secure digital (SD) card 1008 and a screen 1010. The application processor 1006 may include on-chip memory 1006'. In some aspects, the device 1004 may also include a Bluetooth module 1012, a WLAN module 1014, an SPS module 1016 (e.g., a GNSS module), one or more sensor modules 1018 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1026, a power source 1030, and / or a camera 1032. The Bluetooth module 1012, the WLAN module 1014, and the SPS module 1016 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1012, the WLAN module 1014, and the SPS module 1016 may include their own dedicated antennas and / or utilize an antenna 1080 for communication. The cellular baseband processor 1024 communicates with the UE 104 and / or with the RU associated with the network entity 1002 through the transceiver 1022 via one or more antennas 1080. The cellular baseband processor 1024 and the application processor 1006 may each include a computer-readable medium / memory 1024', 1006', respectively. The additional memory module 1026 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1024', 1006', 1026 may be non-transitory. The cellular baseband processor 1024 and the application processor 1006 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software causes the cellular baseband processor 1024 / application processor 1006 to perform the various functions described above when executed by the cellular baseband processor 1024 / application processor 1006. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1024 / application processor 1006 when executing the software.The cellular baseband processor 1024 / application processor 1006 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1004 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1024 and / or the application processor 1006, and in another configuration, the device 1004 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1004.

[0112] As discussed above, component 198 is configured to: send an RRC connection request for establishing a connection with a second network associated with one of the NTN or TN; receive an RRC reconnect message from a network entity associated with the second network; and send an RRC reconnection completion message to a network entity associated with one of the NTN or TN of the second network. Component 198 may be within the cellular baseband processor 1024, the application processor 1006, or both the cellular baseband processor 1024 and the application processor 1006. Component 198 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1004 may include a variety of components configured for various functions. In one configuration, the device 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes a component for sending an RRC connection request for establishing a connection with a second network associated with one of the NTN or TN. The device includes a component for receiving an RRC reconnection message from a network entity associated with a second network. The device includes a component for sending an RRC reconnection completion message to a network entity associated with one of the NTN or TN of the second network. The device also includes a component for sending a registration update request to a network entity associated with one of the NTN or TN of the second network. The device also includes a component for suppressing the sending of the registration update request. The second network configures a new registration area for the UE when establishing a connection with one of the TN or NTN associated with the second network. The device also includes a component for terminating the RRC connection process. The device also includes a component for selecting a new cell to establish a new connection. The new cell is associated with the first network or the second network. The first network or the second network is associated with one of the TN or NTN. The component can be a component 198 of the device 1004 configured to perform the function recorded by the component. As described above, the device 1004 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0113] Fig.11 1100 is a flow chart of a method of wireless communication. The method may be performed by a network entity (e.g., base station 102; network entity 1002). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow the network entity to participate in an RRC reestablishment process with a UE so that the UE can switch cells between a TN and an NTN.

[0114] At 1102, the network entity may receive an RRC connection request. For example, 1102 may be performed by the connection component 199 of the network entity 1302. The network entity may receive an RRC connection request from a UE on a first network associated with one of the TN or NTN. The network entity may be on a second network associated with one of the NTN or TN. The network entity may receive an RRC connection request from the UE to establish a connection with the second network. In some aspects, the RRC connection request may include at least one of an RRC reestablishment request or an RRC recovery request. In some aspects, the RRC reconnect message may include one or more downlink NAS packet data units. In some aspects, the RRC connection request includes a PHY cell ID for one of the NTN or TN of the first network and a PHY cell ID for one of the NTN or TN of the second network. For example, the PHY cell ID may include an integer value identifying the NTN and / or an integer value identifying the TN. In some aspects, the system information may indicate whether the cell associated with the network supports PHY cell IDs for TN and NTN. In some aspects, the RRC connection request may include a network field indicating that the UE was previously connected to a TN or NTN associated with the first network. The network field may include a one-bit field. A one-bit field may indicate that the UE is reestablishing a connection from a different network. For example, if the request is transmitted to the NTN, the UE was previously connected to the TN. If the request is transmitted to the TN, the UE was previously connected to the TN. In some aspects, a spare bit may be used for the network field. In some aspects, if the network entity does not support the reconstruction between the TN and the NTN, the network entity may transmit a rejection message or an RRC connection establishment message. In some aspects, a dedicated or PRACH partition may be used to distinguish from the RRC connection request. In some cases, a dedicated or PRACH partition may be used to distinguish from Msg1. In some aspects, an RRC connection request for a set of allowed PLMNs may be received. In the case of establishing a connection with the second network from the first network, an RRC connection request for a set of allowed PLMNs may be received. For example, for allowed PLMNs, when moving between TN and NTN, the UE may be allowed to perform RRC reconstruction, or vice versa. The UE may be configured as to whether to allow reestablishment between the TN and the NTN. The UE may be configured via RRC signaling or system information. In some aspects, the NTN may include at least one of a LEO NTN, a MEO NTN, or a GEO NTN. In some aspects, the first network and the second network are associated with different RAT networks. For example, the UE may be on a first network associated with the TN, while the network entity is on a second network associated with the NTN. In another example, the UE may be on a first network associated with the NTN, while the network entity is on a second network associated with the TN.

[0115] At 1104, the network entity may send an RRC reconnect message. For example, 1104 may be performed by connection component 199 of network entity 1302. The network entity may send the RRC reconnect message in response to receiving the RRC connection request. The network entity may send the RRC reconnect message to the UE. In some aspects, the RRC reconnect message may include at least one of an RRC reestablishment message, an RRC resume message, an RRC establishment message, or an RRC rejection message.

[0116] At 1106, the network entity may receive an RRC reconnection complete message. For example, 1106 may be performed by the connection component 199 of the network entity 1302. The network entity may receive an RRC reconnection complete message from a UE previously associated with the first network. In some aspects, the RRC reconnection complete message may include at least one of an RRC reconstruction complete message, an RRC recovery complete message, or an RRC establishment complete message. The RRC establishment complete may include a confirmation of the RRC reconnection request message based at least on the failure of the second network to communicate with the first network. In some aspects, for example, in the case where the UE is on a first network associated with a TN, the UE may send an RRC reconnection complete message to a network entity on a second network associated with an NTN. In the case where the UE is on a first network associated with an NTN, the UE may send an RRC reconnection complete message to a network entity on a second network associated with a TN.

[0117] Fig.12 1200 is a flow chart of a method of wireless communication. The method may be performed by a base station (e.g., base station 102; network entity 1002). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow the network entity to participate in an RRC reestablishment process with a UE so that the UE can switch cells between a TN and an NTN.

[0118] At 1202, the network entity may receive an RRC connection request. For example, 1202 may be performed by the connection component 199 of the network entity 1302. The network entity may receive an RRC connection request from a UE on a first network associated with one of the TN or NTN. The network entity may be on a second network associated with one of the NTN or TN. The network entity may receive an RRC connection request from the UE to establish a connection with the second network. In some aspects, the RRC connection request may include at least one of an RRC reestablishment request or an RRC recovery request. In some aspects, the RRC reconnect message may include one or more downlink NAS packet data units. In some aspects, the RRC connection request includes a PHY cell ID for one of the NTN or TN of the first network and a PHY cell ID for one of the NTN or TN of the second network. For example, the PHY cell ID may include an integer value identifying the NTN and / or an integer value identifying the TN. In some aspects, the system information may indicate whether the cell associated with the network supports PHY cell IDs for TN and NTN. In some aspects, the RRC connection request may include a network field indicating that the UE was previously connected to a TN or NTN associated with the first network. The network field may include a one-bit field. A one-bit field may indicate that the UE is reestablishing a connection from a different network. For example, if the request is transmitted to the NTN, the UE was previously connected to the TN. If the request is transmitted to the TN, the UE was previously connected to the TN. In some aspects, a spare bit may be used for the network field. In some aspects, if the network entity does not support the reconstruction between the TN and the NTN, the network entity may transmit a rejection message or an RRC connection establishment message. In some aspects, a dedicated or PRACH partition may be used to distinguish from the RRC connection request. In some cases, a dedicated or PRACH partition may be used to distinguish from Msg1. In some aspects, an RRC connection request for a set of allowed PLMNs may be received. In the case of establishing a connection with the second network from the first network, an RRC connection request for a set of allowed PLMNs may be received. For example, for allowed PLMNs, when moving between TN and NTN, the UE may be allowed to perform RRC reconstruction, or vice versa. The UE may be configured as to whether to allow reestablishment between the TN and the NTN. The UE may be configured via RRC signaling or system information. In some aspects, the NTN may include at least one of a LEO NTN, a MEO NTN, or a GEO NTN. In some aspects, the first network and the second network are associated with different RAT networks. For example, the UE may be on a first network associated with the TN, while the network entity is on a second network associated with the NTN. In another example, the UE may be on a first network associated with the NTN, while the network entity is on a second network associated with the TN.

[0119] At 1204, the network entity may send an RRC reconnect message. For example, 1204 may be performed by connection component 199 of network entity 1302. The network entity may send the RRC reconnect message in response to receiving the RRC connection request. The network entity may send the RRC reconnect message to the UE. In some aspects, the RRC reconnect message may include at least one of an RRC reestablishment message, an RRC resume message, an RRC establishment message, or an RRC rejection message.

[0120] At 1206, the network entity may receive an RRC reconnection complete message. For example, 1206 may be performed by the connection component 199 of the network entity 1302. The network entity may receive an RRC reconnection complete message from a UE previously associated with the first network. In some aspects, the RRC reconnection complete message may include at least one of an RRC reconstruction complete message, an RRC recovery complete message, or an RRC establishment complete message. The RRC establishment complete may include a confirmation of the RRC reconnection request message based at least on the failure of the second network to communicate with the first network. In some aspects, for example, in the case where the UE is on a first network associated with a TN, the UE may send an RRC reconnection complete message to a network entity on a second network associated with an NTN. In the case where the UE is on a first network associated with an NTN, the UE may send an RRC reconnection complete message to a network entity on a second network associated with a TN.

[0121] At 1208, the network entity may receive a registration update request. For example, 1208 may be performed by the connection component 199 of the network entity 1302. The network entity may receive a registration update request from the UE to update the registration to one of the NTN or TN associated with the second network. The network entity may receive a registration update request from the UE in response to the UE selecting a cell associated with a different network. For example, a UE selecting a cell from a TN to an NTN indicates to the UE that the UE has moved outside its registration area. In some cases, the network may indicate in system information whether a selected cell associated with a different network supports or allows reconstruction between different networks. For example, a UE on a TN may select a cell associated with an NTN of a second network. The NTN may indicate in system information provided to the UE whether the cell allows reconstruction between the TN and the NTN. In some aspects, the indication indicating whether the selected cell supports or allows reconstruction between different networks (e.g., between the TN and the NTN) may be for each PLMN.

[0122] At 1210, the network entity may poll one or more network entities of the first network and / or the second network. For example, 1210 may be performed by the connection component 199 of the network entity 1302. The network entity may poll one or more network entities associated with one of the NTN or TN of the first network. The network entity may poll one or more network entities associated with one of the NTN or TN of the second network. In some aspects, the network entity may poll one or more network entities associated with one of the NTN or TN of the first network and one or more network entities associated with one of the NTN or TN of the second network that know the PHY cell ID and cell radio network temporary identifier (C-RNTI) of the UE. The network entity may poll one or more network entities of the first and / or second network to determine whether the same PHY cell ID and C-RNTI are being used for other UEs.

[0123] At 1212, the network entity may provide a PHY cell ID between the first network and the second network. For example, 1212 may be performed by the connection component 199 of the network entity 1302. The network entity may provide a PHY cell ID between the first network and the second network so that no overlap of the PHY cell ID occurs between the first network and the second network. For example, the first network may include a TN and the second network may include an NTN, so that the PHY cell ID may be provided to the TN and the NTN and there is no overlap of the PHY cell ID between the TN and the NTN. In some aspects, the PHY cell ID may be grouped between the TN and the NTN. The PHY cell ID of the UE may indicate which network the UE was previously connected to. For example, the PHY cell ID of the UE may indicate whether the UE was previously connected to the TN or the NTN. In some aspects, the UE may have been previously connected to a HAPS, wherein the PHY cell IDs may overlap or move apart when the UE attempts to connect to the target network entity.

[0124] Fig.131300 is a diagram illustrating an example of a hardware implementation for a network entity 1302. The network entity 1302 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1302 may include at least one of a CU 1310, a DU 1330, or a RU 1340. For example, depending on the layer functionality handled by the component 199, the network entity 1302 may include a CU 1310; both a CU 1310 and a DU 1330; each of the CU 1310, the DU 1330, and the RU 1340; the DU 1330; both a DU 1330 and a RU 1340; or a RU 1340. The CU 1310 may include a CU processor 1312. The CU processor 1312 may include an on-chip memory 1312'. In some aspects, the CU 1310 may also include an additional memory module 1314 and a communication interface 1318. CU 1310 communicates with DU 1330 via a midhaul link such as an F1 interface. DU 1330 may include a DU processor 1332. DU processor 1332 may include on-chip memory 1332'. In some aspects, DU 1330 may also include additional memory modules 1334 and communication interfaces 1338. DU 1330 communicates with RU 1340 via a fronthaul link. RU 1340 may include a RU processor 1342. RU processor 1342 may include on-chip memory 1342'. In some aspects, RU 1340 may also include additional memory modules 1344, one or more transceivers 1346, antenna 1380, and communication interface 1348. RU 1340 communicates with UE 104. On-chip memory 1312', 1332', 1342' and additional memory modules 1314, 1334, 1344 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1312, 1332, 1342 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0125] As discussed above, component 199 is configured to: receive an RRC connection request for establishing a connection with a second network from a UE on a first network associated with one of the TN or NTN; send an RRC reconnect message in response to receiving the RRC connection request; and receive an RRC reconnection completion message from a UE previously associated with the first network. Component 199 may be within one or more processors of one or more of CU 1310, DU 1330, and RU 1340. Component 199 may be one or more hardware components that are specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. Network entity 1302 may include a variety of components configured for various functions. In one configuration, network entity 1302 includes a component for receiving an RRC connection request for establishing a connection with a second network from a UE on a first network associated with one of the TN or NTN. The network entity includes a component for sending an RRC reconnect message in response to receiving the RRC connection request. The network entity includes a component for receiving an RRC reconnection completion message from a UE previously associated with the first network. The network entity also includes a component for receiving a registration update request from the UE to update the registration to one of the NTNs or TNs associated with the second network. The network entity also includes a component for polling one or more network entities associated with one of the NTNs or TNs of the first network and one or more network entities associated with one of the NTNs or TNs of the second network for understanding the PHY cell ID and C-RNTI of the UE. The network entity also includes a component for providing a PHY cell ID between the first network and the second network, wherein no overlap of physical cell IDs occurs between the first network and the second network. The component may be a component 199 of the network entity 1302 configured to perform the functions recorded by the component. As described above, the network entity 1302 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recorded by the component.

[0126] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0127] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases (such as "when ......") do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, then the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0128] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0129] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0130] Aspect 1 is a method for performing wireless communications at a UE on a first network associated with one of a TN or an NTN, comprising: sending a radio resource control (RRC) connection request for establishing a connection with a second network associated with the NTN or one of the TNs; receiving an RRC reconnection message from a network entity associated with the second network; and sending an RRC reconnection completion message to the network entity associated with the NTN or one of the TNs of the second network.

[0131] Aspect 2 is the method according to aspect 1, further comprising a transceiver coupled to the at least one processor.

[0132] Aspect 3 is a method according to any one of Aspects 1 and 2, further comprising: the RRC connection request includes at least one of an RRC reconstruction request or an RRC recovery request, wherein the RRC reconnection message includes at least one of an RRC reconstruction message or an RRC recovery message, an RRC establishment message, and an RRC rejection message, wherein the RRC reconnection completion message includes at least one of an RRC reconstruction completion message, an RRC recovery completion message, or an RRC establishment completion message.

[0133] Aspect 4 is a method according to any one of aspects 1 to 3, further comprising: the RRC reconnection message includes one or more downlink NAS packet data units.

[0134] Aspect 5 is a method according to any one of aspects 1 to 4, further comprising: sending a registration update request to the network entity associated with one of the NTN or the TN of the second network.

[0135] Aspect 6 is a method according to any one of Aspects 1 to 5, further comprising: the RRC reconnection completion message is configured to confirm the receipt of the RRC reconnection completion message, and the RRC reconnection completion message includes a registration update request.

[0136] Aspect 7 is a method according to any one of aspects 1 to 6, further comprising: suppressing sending a registration update request, wherein the second network configures a new registration area for the UE when establishing the connection with one of the TN or the NTN associated with the second network.

[0137] Aspect 8 is a method according to any one of Aspects 1 to 7, further comprising: terminating the RRC connection process; and selecting a new cell to establish a new connection, wherein the new cell is associated with the first network or the second network, wherein the first network or the second network is associated with one of the TN or the NTN.

[0138] Aspect 9 is a method according to any one of aspects 1 to 8, further comprising: the RRC connection request comprises a network field indicating that the UE was previously connected to the TN or the NTN, wherein the network field comprises a one-bit field.

[0139] Aspect 10 is a method according to any one of aspects 1 to 9, further comprising: dedicated or PRACH partitioning is used to distinguish from the RRC connection request.

[0140] Aspect 11 is a method according to any one of aspects 1 to 10, further comprising: the NTN comprises at least one of a LEO NTN, a MEONTN, or a GEO NTN.

[0141] Aspect 12 is a method according to any one of aspects 1 to 11, further comprising: the first network and the second network are associated with different RAT networks.

[0142] Aspect 13 is a method according to any one of Aspects 1 to 12, further comprising: during the reconstruction process in the second network, adjusting or restarting a timer associated with at least one of PDCP, RLC or MAC for unconfirmed data or undelivered data in the first network.

[0143] Aspect 14 is an apparatus for wireless communication at a UE on a first network associated with one of a TN or an NTN, comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor being configured to implement any one of aspects 1 to 13.

[0144] Aspect 15 is an apparatus for wireless communication at a UE on a first network associated with one of a TN or an NTN, comprising means for implementing any one of aspects 1 to 13.

[0145] Aspect 16 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 13.

[0146] Aspect 17 is a method for wireless communication at a network entity on a second network associated with one of an NTN or a TN, comprising: receiving an RRC connection request for establishing a connection with the second network from a UE on a first network associated with the TN or the NTN; sending an RRC reconnection message in response to receiving the RRC connection request; and receiving an RRC reconnection completion message from the UE previously associated with the first network.

[0147] Aspect 18 is the method of aspect 17, further comprising a transceiver coupled to the at least one processor.

[0148] Aspect 19 is a method according to any one of Aspects 17 and 18, further comprising: the RRC connection request includes at least one of an RRC reconstruction request or an RRC recovery request, wherein the RRC reconnection message includes at least one of an RRC reconstruction message, an RRC recovery message, an RRC establishment message or an RRC rejection message, wherein the RRC reconnection completion message includes at least one of an RRC reconstruction completion message, an RRC recovery completion message or an RRC establishment completion message.

[0149] Aspect 20 is a method according to any one of aspects 17 to 19, further comprising: the RRC reconnection message includes one or more downlink NAS packet data units.

[0150] Aspect 21 is a method according to any one of aspects 17 to 20, further comprising: receiving a registration update request from the UE to update registration with one of the NTN or the TN associated with the second network.

[0151] Aspect 22 is a method according to any one of Aspects 17 to 21, further comprising: the RRC reconnection completion message includes a confirmation of the RRC reconnection message, and the RRC reconnection completion message includes a registration update request.

[0152] Aspect 23 is a method according to any one of aspects 17 to 22, further comprising: the RRC establishment message includes a confirmation of the RRC reconnection request message based at least on the failure of the second network to communicate with the first network.

[0153] Aspect 24 is a method according to any one of Aspects 17 to 23, further comprising: polling one or more network entities associated with the NTN or one of the TNs of the first network and one or more network entities associated with the NTN or one of the TNs of the second network to understand the PHY cell ID and C-RNTI of the UE.

[0154] Aspect 25 is a method according to any one of aspects 17 to 24, further comprising: providing a PHY cell ID between the first network and the second network, wherein no overlap of the PHY cell ID occurs between the first network and the second network.

[0155] Aspect 26 is a method according to any one of Aspects 17 to 25, further comprising: the RRC connection request includes a PHY cell ID of one of the NTN or the TN for the first network and a PHY cell ID of one of the NTN or the TN for the second network.

[0156] Aspect 27 is a method according to any one of aspects 17 to 26, further comprising: the RRC connection request includes a network field indicating that the UE was previously connected to the TN or the NTN, wherein the network field includes a one-bit field.

[0157] Aspect 28 is a method according to any one of aspects 17 to 27, further comprising: dedicated or PRACH partitioning is used to distinguish from the RRC connection request.

[0158] Aspect 29 is a method according to any one of aspects 17 to 28, further comprising: in a case where the connection with the second network is established from the first network, receiving the RRC connection request for the set of allowed PLMNs.

[0159] Aspect 30 is a method according to any one of aspects 17 to 29, further comprising: the NTN comprises at least one of a LEO NTN, a MEO NTN, or a GEO NTN.

[0160] Aspect 31 is a method according to any one of aspects 17 to 30, further comprising: the first network and the second network are associated with different RAT networks.

[0161] Aspect 32 is an apparatus for wireless communication at a network entity on a second network associated with one of an NTN or a TN, comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor being configured to implement any one of aspects 17 to 30.

[0162] Aspect 33 is an apparatus for wireless communication at a network entity on a second network associated with one of an NTN or a TN, comprising means for implementing any one of aspects 17 to 30.

[0163] Aspect 34 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 17 to 30.

Claims

1. An apparatus for wireless communication at a user equipment (UE) on a first network associated with one of a terrestrial network (TN) or a non-terrestrial network (NTN), comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: sending a radio resource control (RRC) connection request for establishing a connection with a second network associated with one of the NTN or the TN; receiving an RRC reconnection message from a network entity associated with the second network; as well as An RRC reconnection complete message is sent to the network entity associated with one of the NTN or the TN of the second network.

2. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor.

3. The apparatus according to claim 1, wherein the RRC connection request comprises at least one of an RRC reestablishment request or an RRC recovery request, wherein the RRC reconnection message comprises at least one of an RRC reestablishment message or an RRC recovery message, an RRC establishment message, and an RRC rejection message, wherein the RRC reconnection complete message comprises at least one of an RRC reestablishment complete message, an RRC recovery complete message, or an RRC establishment complete message.

4. The apparatus of claim 1, wherein the RRC reconnect message comprises one or more downlink non-access stratum (NAS) packet data units.

5. The apparatus of claim 1 , wherein the at least one processor is further configured to: A registration update request is sent to the network entity associated with one of the NTN or the TN of the second network.

6. The apparatus of claim 1, wherein the RRC reconnection complete message is configured to confirm receipt of the RRC reconnection complete message, the RRC reconnection complete message comprising a registration update request.

7. The apparatus of claim 1, wherein the at least one processor is further configured to: refraining from sending a registration update request, wherein the second network configures a new registration area for the UE when establishing the connection with one of the TN or the NTN associated with the second network.

8. The apparatus of claim 1, wherein the at least one processor is further configured to: aborting the RRC connection procedure; and A new cell is selected to establish a new connection, wherein the new cell is associated with the first network or the second network, wherein the first network or the second network is associated with one of the TN or the NTN.

9. The apparatus of claim 1, wherein the RRC connection request comprises a network field indicating that the UE was previously connected to the TN or the NTN, wherein the network field comprises a one-bit field.

10. The apparatus of claim 1, wherein dedicated or physical random access channel (PRACH) partitioning is used to distinguish from the RRC connection request.

11. The device of claim 1, wherein the NTN comprises at least one of a low earth orbit (LEO) NTN, a medium earth orbit (MEO) NTN, or a geostationary earth orbit (GEO) NTN.

12. The apparatus of claim 1, wherein the first network and the second network are associated with different radio access technology (RAT) networks.

13. The apparatus of claim 1 , wherein during a reestablishment process in the second network, a timer associated with at least one of a packet data convergence protocol (PDCP), a radio link control (RLC), or a medium access control (MAC) is adjusted or restarted for unacknowledged data or undelivered data in the first network.

14. A method of wireless communication at a user equipment (UE) on a first network associated with one of a terrestrial network (TN) or a non-terrestrial network (NTN), comprising: sending a radio resource control (RRC) connection request for establishing a connection with a second network associated with one of the NTN or the TN; receiving an RRC reconnection message from a network entity associated with the second network; as well as An RRC reconnection complete message is sent to the network entity associated with one of the NTN or the TN of the second network.

15. An apparatus for wireless communication at a network entity on a second network associated with one of a non-terrestrial network (NTN) or a terrestrial network (TN), comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving, from a user equipment (UE) on a first network associated with one of the TN or the NTN, a radio resource control (RRC) connection request for establishing a connection with the second network; sending an RRC reconnection message in response to receiving the RRC connection request; as well as An RRC reconnection complete message is received from the UE previously associated with the first network.

16. The apparatus of claim 15, further comprising a transceiver coupled to the at least one processor.

17. The apparatus of claim 15, wherein the RRC connection request comprises at least one of an RRC reestablishment request or an RRC recovery request, wherein the RRC reconnection message comprises at least one of an RRC reestablishment message, an RRC recovery message, an RRC establishment message, or an RRC reject message, wherein the RRC reconnection complete message comprises at least one of an RRC reestablishment complete message, an RRC recovery complete message, or an RRC establishment complete message.

18. The apparatus of claim 15, wherein the RRC reconnection message comprises one or more downlink non-access stratum (NAS) packet data units.

19. The apparatus of claim 15, wherein the at least one processor is further configured to: A registration update request is received from the UE to update registration with one of the NTN or the TN associated with the second network.

20. The apparatus of claim 15, wherein the RRC reconnection complete message comprises an acknowledgement of the RRC reconnection message, the RRC reconnection complete message comprising a registration update request.

21. The apparatus of claim 15, wherein the RRC setup message comprises an acknowledgement of the RRC reconnect message based at least on a failure of the second network to communicate with the first network.

22. The apparatus of claim 15, wherein the at least one processor is further configured to: Polling one or more network entities associated with one of the NTN or the TN of the first network and one or more network entities associated with one of the NTN or the TN of the second network for knowledge of a physical (PHY) cell identifier (ID) and a cell radio network temporary identifier (C-RNTI) of the UE.

23. The apparatus of claim 15, wherein the at least one processor is further configured to: A physical (PHY) cell identifier (ID) is provided between the first network and the second network, wherein no overlap of the PHY cell ID occurs between the first network and the second network.

24. The apparatus of claim 15, wherein the RRC connection request comprises a physical (PHY) cell identifier (ID) for one of the NTN or the TN for the first network and a PHY cell ID for one of the NTN or the TN for the second network.

25. The apparatus of claim 15, wherein the RRC connection request comprises a network field indicating that the UE was previously connected to the TN or the NTN, wherein the network field comprises a one-bit field.

26. The apparatus of claim 15, wherein dedicated or physical random access channel (PRACH) partitioning is used to distinguish from the RRC connection request.

27. The apparatus of claim 15, wherein the RRC connection request is received for a set of allowed public land mobile networks (PLMNs) in a scenario where the connection with the second network is established from the first network.

28. The device of claim 15, wherein the NTN comprises at least one of a low earth orbit (LEO) NTN, a medium earth orbit (MEO) NTN, or a geostationary earth orbit (GEO) NTN.

29. The apparatus of claim 15, wherein the first network and the second network are associated with different radio access technology (RAT) networks.

30. A method of wirelessly communicating at a network entity on a second network associated with one of a non-terrestrial network (NTN) or a terrestrial network (TN), comprising: receiving, from a user equipment (UE) on a first network associated with one of the TN or the NTN, a radio resource control (RRC) connection request for establishing a connection with the second network; sending an RRC reconnection message in response to receiving the RRC connection request; as well as An RRC reconnection complete message is received from the UE previously associated with the first network.