Storage and forwarding satellite access with discontinuous feeder link

Abstract

Techniques are described for enabling a user equipment (UE) to communicate with a remote endpoint by accessing the SV in a storage and forwarding (Samp; F) mode when a spacecraft (SV) does not have a feeder link to a ground-based network. The SV may include an onboard radio access network and core network capabilities, which may enable a UE to communicate with an onboard proxy of a remote endpoint. The proxy stores mobile station initiated (MO) voice and data transmitted by the UE and returns mobile station terminated (MT) voice and data transmitted by the remote endpoint. When the SV has a feeder link, the proxy forwards the MO data to the Samp; a second agent in the F-center is to forward to the remote endpoint, and MT data may be received from the second agent of the UE. The UE may access the SV without limitation and register only when accessing the SV.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit and priority of U.S. Provisional Application Serial No. 63 / 518,551, filed August 9, 2023, entitled “Store and Forward 4G and 5G Satellite Access with Discontinuous Feeder Links”, and U.S. Non-Provisional Patent Application Serial No. 18 / 477,528, filed September 28, 2023, entitled “Store and Forward Satellite Access with Discontinuous Feeder Links”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to wireless communication using satellites with discontinuous feeder links. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. 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 telecommunications standards to use common protocols that enable different wireless devices to communicate at the city, country, regional, and global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CWB) program issued by the 3rd 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. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some wireless communication networks may include non-terrestrial components. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard.

[0006] Both 5G NR and LTE can support satellite access to wireless networks. In such cases, mobile devices can access satellites that do not have access to terrestrial wireless networks. In this scenario, both the mobile device and the satellite may need to support store-and-forward operations to enable the mobile device to access remote endpoints via terrestrial wireless networks. Therefore, technologies that support store-and-forward operations can be useful. Summary of the Invention

[0007] The following is a simplified summary of one or more aspects to provide a basic understanding of such aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential 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 the more detailed descriptions that follow.

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided for wireless communication at a spacecraft (SV) in a non-terrestrial network (NTN). The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor may be configured individually or in any combination to create an endpoint agent corresponding to a user equipment (UE), the endpoint agent simulating a terminal device in the terrestrial network; as the endpoint agent, receive communications from the UE to be delivered to the terminal device in the terrestrial network; store the communications at the SV during periods when the feeder link between the SV and the terrestrial network is unavailable; and forward the communications to the terrestrial network when the feeder link becomes available.

[0009] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at a store-and-forward center (SFC) are provided. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor may be configured individually or in any combination to: receive communications for a UE from a terminal device in a terrestrial network when a feeder link to an SV in an NTN serving the UE is unavailable; create a UE proxy for the UE; store communications at the SFC during the period when the feeder link is unavailable; and forward the communications to the SV when the feeder link becomes available.

[0010] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided for wireless communication performed by a user equipment (UE). The apparatus is configured to: access the SV using a serving link when the SV does not have a feeder link to a terrestrial network and the UE has not registered with the SV; register with the SV; transmit mobile station-initiated (MO) data intended for at least one remote endpoint to the SV for storage at the SV until the SV has a feeder link to a terrestrial network to forward the MO data to at least one remote endpoint via the terrestrial network; deregister from the SV; and stop accessing the SV.

[0011] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided for wireless communication performed by an SV. The apparatus is configured to: provide wireless access to a UE via a serving link, wherein the SV does not have a feeder link to a terrestrial network, and wherein the UE is not registered with the SV; register the UE; receive MO data from the UE, the MO data intended for use with at least one remote endpoint; store the MO data; deregister the UE; stop providing wireless access to the UE; obtain a feeder link to the terrestrial network; and forward the MO data to at least one remote endpoint via the terrestrial network.

[0012] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication performed by a server are provided. The apparatus is configured to: receive MO data from an SV having a feeder link to the server, the MO data being intended for at least one remote endpoint and initiated by a user equipment (UE) when the SV does not have a feeder link to the server, wherein the MO data is received independently of registration and deregistration assistance provided for registering the UE with the SV and later deregistering the UE from the SV; and forward the MO data to the at least one remote endpoint via a network.

[0013] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided for wireless communication performed by a UE. The apparatus is configured to: acquire MO data intended for use with at least one remote endpoint; package mobile station-initiated (MO) data into a single MO dataset; access a SV using a serving link, wherein the SV does not have a feeder link to a terrestrial network; transmit the MO dataset to the SV for storage and forward the MO dataset to another entity for provision to at least one remote endpoint when the SV has a feeder link to the terrestrial network; and stop accessing the SV before the SV has a feeder link to the terrestrial network.

[0014] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided for wireless communication performed by a terrestrial server. The apparatus is configured to: receive an MO dataset from a spacecraft (SV) having a feeder link to the server, the MO dataset including MO data intended for use with at least one remote endpoint; and provide the MO dataset to another entity for unpacking the MO dataset into MO data; wherein the MO dataset is initiated by a user equipment (UE) when the terrestrial server does not have a feeder link to the SV, and the MO dataset is received independently of registration and deregistration assistance provided for registering the UE with the SV and subsequently deregistering the UE from the SV.

[0015] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided for implementing security for a UE's radio access to an SV in store-and-forward mode, performed by a first entity. The apparatus is configured to transmit a key identifier (Kid) to a second entity based on a UE master key (K) configured in the second entity, so that the second entity can determine a substitute master key (K) for the UE based on Kid and K. ); and based on K To perform authentication and encryption key determination to enable secure data transfer between the UE and at least one remote endpoint via SV, where K The Kid is configured in the first entity, where secure data transfer is performed between UEs that access the SV using a serving link when the SV does not have a feeder link, and UE registration with the SV is part of access to the SV.

[0016] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided for implementing security for a UE's radio access to an SV in store-and-forward mode, performed by a second entity. The apparatus is configured to: receive a key identifier (Kid) from a first entity; and determine a substitute master key (K) for the UE based on the Kid and the UE's master key (K). K is configured in the second entity; and based on K To perform authentication and encryption key determination to achieve secure data transfer between the UE and at least one remote endpoint via SV, where K The Kid is configured in the first entity, where secure data transfer is performed between UEs that access the SV using a serving link when the SV does not have a feeder link, and the UE's registration with the SV is part of the access to the SV.

[0017] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0018] Figure 1 This illustrates how mobile devices access the network via satellite.

[0019] Figure 2 An example of a satellite architecture that supports store-and-forward operations over discontinuous feeder links is shown.

[0020] Figure 3 The example illustrates store-and-forward operations from satellite to terrestrial networks and remote endpoints.

[0021] Figure 4 An example of a first option for accessing a terrestrial network using store-and-forward operations is shown.

[0022] Figure 5 A second option for accessing terrestrial networks using store-and-forward operations is illustrated.

[0023] Figure 6 A third option for accessing terrestrial networks using store-and-forward operations is illustrated.

[0024] Figure 7 This illustrates the initial access of a mobile device to a satellite using store-and-forward operations.

[0025] Figure 8 This illustrates access to a terrestrial network using store-and-forward operations.

[0026] Figure 9 This illustrates how mobile devices utilize store-and-forward operations for subsequent access to satellites.

[0027] Figure 10 Examples of applications that improve store-and-forward operations are shown.

[0028] Figure 11 Alternative uses for improving store-and-forward operations are illustrated.

[0029] Figure 12 This illustrates how mobile devices securely access satellites using store-and-forward operations.

[0030] Figure 13 This illustrates how mobile devices can securely access satellites via IMS using store-and-forward operations.

[0031] Figure 14A and Figure 14B This illustrates how mobile devices can leverage store-and-forward operations for more flexible and secure access to satellites.

[0032] Figure 15 It is a flowchart of a method for supporting wireless communication performed by user equipment.

[0033] Figure 16 This is a flowchart of a method that supports wireless communication performed by a spacecraft.

[0034] Figure 17 This is a flowchart of a method that supports wireless communication performed by a server.

[0035] Figure 18 It is a flowchart of a method for supporting wireless communication performed by user equipment.

[0036] Figure 19 This is a flowchart of a method that supports wireless communication performed by a server.

[0037] Figure 20 This is a flowchart of a method for ensuring secure wireless access to spacecraft by a UE in store-and-forward mode.

[0038] Figure 21 This is a flowchart of a method for ensuring secure wireless access to spacecraft by a UE in store-and-forward mode.

[0039] Figure 22 This is a diagram illustrating an example of a hardware implementation of a UE configured to access a spacecraft.

[0040] Figure 23 This is a diagram illustrating an example of a hardware implementation of a spacecraft configured to support UE access.

[0041] Figure 24 This is a diagram illustrating an example of a hardware implementation of a server configured to support UE access to a spacecraft.

[0042] Figure 25 This is a diagram illustrating an example of a hardware implementation of an entity (such as a UDM or HSS) in a PLMN.

[0043] Figure 26 This is a block diagram illustrating communication between network entities and the UE in the access network.

[0044] Figure 27 It is a flowchart of a method for supporting wireless communication performed by user equipment.

[0045] Figure 28 This is a flowchart of a method that supports wireless communication performed by a spacecraft.

[0046] Figure 29 This is a flowchart of a method that supports wireless communication performed by a server.

[0047] Figure 30 It is a flowchart of a method for supporting wireless communication performed by user equipment.

[0048] Figure 31 This is a flowchart of a method that supports wireless communication performed by a server.

[0049] Figure 32 This is a flowchart of a method for ensuring secure wireless access to spacecraft by a UE in store-and-forward mode.

[0050] Figure 33 This is a flowchart of a method for ensuring secure wireless access to spacecraft by a UE in store-and-forward mode.

[0051] Similar reference numerals and symbols in the various figures indicate similar elements according to certain specific embodiments. Additionally, multiple instances of an element may be indicated by adding a letter after the first numeral, or by adding a hyphen followed by a second numeral. For example, multiple instances of element 106 may be indicated as 106-1, 106-2, 106-3, etc. Similarly, multiple instances of element 102 may be indicated as 102a, 102b, 102c, etc. When only the first numeral is used to refer to such an element, it will be understood that any instance of the element (e.g., element 106 in the previous example would refer to any of elements 106-1, 106-2, and 106-3, and element 102 in the previous example would refer to any of elements 102a, 102b, and 102c). Detailed Implementation

[0052] Satellites (also known as spacecraft (SVs) or communications satellites) can be used in communication systems, for example, to relay communication signals between gateways (also known as earth stations or ground stations) and one or more satellites and one or more mobile devices (typically called user equipment (UEs)). For example, a UE can access a satellite (rather than a terrestrial base station), which can be connected to an earth station (ES), also referred to as a ground station or non-terrestrial network (NTN) gateway. The earth station will then connect to elements in the 5G (or 4G or future 6G) network, such as a 5G core (5GC) network (5GCN) or a modified base station (potentially without a terrestrial antenna) or network node in a 4G or future 6G core network. This element will then provide access to other elements in the 5G (or 4G or future 6G) network, and ultimately to entities outside the 5G (or 4G or future 6G) network, such as internet web servers and other user equipment.

[0053] The fundamental principle of 5G (or other cellular network) satellite access for UEs can include providing ubiquitous outdoor coverage for both users and mobile network operators (MNOs). For example, in many countries, including the United States, unavailable or poor cellular network coverage is a common problem. Furthermore, even when generally good cellular coverage exists, cellular access is not always possible. For example, cellular access can be hampered by congestion, physical obstacles, localized cellular outages caused by weather (e.g., hurricanes or tornadoes), or localized power outages. Satellite access to cellular networks can provide a new, independent access that is potentially available everywhere outdoors. Current satellite-capable phones for Low Earth Orbit (LEO) SV may have similar sizes to cellular smartphones, and therefore mobile NR support using satellite-capable phones does not require a significant increase in phone size. Furthermore, satellite-capable smartphones can help drive handset sales and potentially increase operator revenue. Potential users, for example, could include anyone with limited or no cellular access, anyone wanting a backup for those lacking cellular access, anyone involved in public safety matters, or anyone who otherwise requires (nearly) 100% reliable mobile communications. Additionally, some users may expect improved or more reliable E911 service, for example, for medical emergencies or traffic breakdowns in remote areas. Additional user scenarios may include providing wireless communication access to UEs located outdoors and associated with automated or Internet of Things (IoT) devices, such as UEs enabling communication with and potentially controlling unmanned aerial vehicles (UAVs), driverless vehicles, automated machinery used in agriculture, forestry, or mining, smart meters, and monitoring devices (e.g., for monitoring weather, traffic, crowds, hazardous conditions).

[0054] Using 5G satellite access offers other benefits. For example, 5G satellite access can reduce infrastructure costs for mobile network operators (MNOs). MNOs can use satellite access to reduce the number of terrestrial base stations (such as NR NodeBs, also known as gNBs) that need to be deployed, as well as backhaul deployments in sparsely populated areas. Furthermore, 5G satellite access can be used to overcome internet blockages, for example, in some countries. Additionally, 5G satellite access can provide diversification for spacecraft operators (SVOs). For example, 5G NR satellite access can provide an additional revenue stream for SVOs that would otherwise only offer fixed internet access.

[0055] As a term, when there is prior contextual information that “cell” is a “satellite cell”, a wireless cell supported by a satellite (or SV) is referred to herein as a “satellite cell,” “radio cell,” “NTN cell,” or simply “cell.” A satellite cell will be distinguished from a wireless cell supported by terrestrial base stations and access points, which are referred to herein as a terrestrial cell or terrestrial network (TN) cell.

[0056] It should be noted that the terms spacecraft (SV), communications satellite, and satellite can be synonymous and are therefore used interchangeably herein. In some cases, an SV (or satellite) can be a navigation SV (or satellite), such as an SV used for GPS, Galileo, GLONASS, or BeiDou. SVs that function as navigation SVs but may not function as communications SVs are marked and explicitly referred to herein to avoid confusion with communications SVs that may not support navigation.

[0057] Some wireless communications can be exchanged via non-terrestrial networks (NTNs). The aspects presented in this paper contribute to achieving efficient and consistent connectivity solutions that can adapt to changing network conditions, especially in areas with intermittent or unreliable network coverage. Data communication via NTNs can be limited by the availability of serving links and / or feeder links. The aspects presented in this paper provide a solution to address the intermittent availability of feeder links and / or serving links by providing adaptive operating modes and efficient data handling methods, ultimately improving overall communication efficiency and enhancing user experience.

[0058] The overall scope involves wireless communication. Some aspects are more specifically related to store-and-forward modes for satellite access with discontinuous feeder links.

[0059] As an example, an element, any part of an element, or any combination of elements may be implemented as a “processing system” including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0060] Therefore, 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 code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, 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 accessible by a computer.

[0061] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features 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 involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0062] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)), or one or more units (or components) performing base station functionality can be implemented in aggregated or decomposed architectures. For example, a BS (such as a node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or one or more components of a decomposed base station. A decomposed base station can be configured to utilize a protocol stack that is physically or logically distributed across two or more units (such as one or more central or centralized units (CU), one or more distributed units (DU), or one or more radio units (RU)).

[0063] Figure 1 An example communication system 100 is illustrated, in which UE 102 accesses a terrestrial public land mobile network (PLMN) 108 via SV 104 and NTN gateway 106. The terrestrial PLMN 108 provides UE 102 with access to a remote endpoint 116 via the Internet 112, PSTN 114, and other networks 110. Figure 1 Examples of possible endpoints are illustrated, such as remote endpoints 116a, 116b, 116c, 116c, and 116d. Remote endpoint 116 may include application functions (AF), external clients, and other UEs 102, and may be physically supported by internet servers, computers, Internet of Things (IoT) devices, and other mobile devices. The radio communication link between UE 102 and SV 104 is called a service link (SL) 101 and may be based on 5G NR, 4G LTE, future 6G standards, or some other wireless standard. The radio communication link between SV 104 and NTN gateway 106 is called a feeder link (FL) 103. In normal operation, when UE 102 has a service link 101 to SV 104, SV 104 will also have a feeder link 103 to NTN gateway 106. In the case of a discontinuous feeder link (DFL), SV 104 can provide service link 101 to UE 102 while there is no availability of feeder link 103 to NTN gateway 106.

[0064] DFL can be applied to Low Earth Orbit (LEO) and Medium Earth Orbit (MEO) SV 104, but generally not to Geostationary Earth Orbit (GEO) SV 104. Without FL availability, the spacecraft (SV) 104 in the UE 102's field of view may not have a feeder link. With partial FL availability, the SV in the UE 102's field of view may sometimes have a feeder link for a portion of its overall accessibility time to the UE 102. With continuous SL availability, the SV 104 with SL can be continuously available to the UE 102. With discontinuous SL availability, the SV 104 with SL may sometimes be unavailable to the UE 102. When the SV 104 has a feeder link, the SV 104 can operate in real-time mode while providing access to any UE 102. In real-time mode, the SV 104 can transmit voice, data, and control information between the UE 102 and the ground PLMN 108 in real time without needing to store and later forward information. The real-time mode may include transparent operations, in which SV 104 transmits voice, data, and control information between UE 102 and PLMN 108 without interpretation or modification. The real-time mode may also include regeneration operations, in which SV 104 performs some interpretation and possible protocol and format conversions on the information transmitted between UE 102 and PLMN 108.

[0065] In the absence of FL availability, for example, when the FL is unavailable, SV 104 can operate in Store & Forward (S&F) mode, where SV 104 stores information received from UE 102 when the serving link is available and forwards that information to PLMN 108 when the feeder link is available, and similarly stores information received from PLMN 108 when the feeder link is available and forwards that information to UE 102 when the serving link is available. S&F mode can support continuous SL availability, discontinuous SL availability, no FL availability, and / or partial FL availability.

[0066] One type of solution for supporting S&F mode for UEs using SV 104 could be to include PLMN functionality within SV 104, which includes RAN and core network (CN) functionality, and wherein SV 104 could include full or partial CN functionality, and store-and-forward could be performed at the application level within SV 104 using endpoint agents simulating the behavior of remote endpoints and UE agents in separate terrestrial store-and-forward centers using either terrestrial PLMN 108 or simulating the behavior of UE 102. This type of solution is described in this document at a high level, and then in more detail. It avoids store-and-forward at lower protocol levels (e.g., transport or NAS protocol levels), which could complicate S&F and delay the transmission of MO data by UE 102 and MT data by remote endpoint 116. Instead, using this type of solution described herein, UE 102 can access SV 104 and begin transmitting MO data in S&F mode almost immediately, without any additional delay.

[0067] As mentioned in this article, transmitting or receiving data at the application level can mean transmitting or receiving data at the top application protocol layer. When component E1 transmits data to another component E2 in a communication system, a layered set of communication protocols (e.g., the ISO 7 layer set) is typically used to pass the data. Lower layers support transmission, error detection and correction, session management, and other functions well-known in the industry. The top application protocol layer typically defines and supports data formatting and decoding, and in some cases can provide additional control information to identify various aspects of the data as well as source and destination addresses. Transmitting or receiving data at the application level means supporting all protocol layers used for transmission. This excludes relaying or forwarding data at lower protocol layers (e.g., the transport layer) that do not require support for higher protocol layers.

[0068] For UEs subscribing to an SVO, the SVO can support S&F mode. The subscription can represent the UE's home PLMN (HPLMN), where the SVO acts as the equivalent HPLMMN (EHPLMN). Due to regulations, the SVO may only instruct support for the serving PLMN in countries where SV 104 currently provides coverage. This could result in the UE obtaining S&F access via a VPLMN—for example, AT&T in northern Canada. ™ SVO access for subscribers and subscriptions indicates support for Telus. ™ As a service PLMN, not AT&T ™ As an alternative, SVO can support all UEs with S&F capabilities, with or without an SVO subscription.

[0069] Figure 2An example communication system 200 is illustrated, in which SV 104 provides store-and-forward support to enable UE 102 to transmit and receive information to and from remote endpoint 116, while SV 104 provides a service link 101 to UE 102 but does not have a feeder link 103 to a terrestrial PLMN. Communication system 200 may be part of communication system 100, where the same labels are used to indicate similar entities. In communication system 200, SV 104 supports 5G NR access for UE 102 and includes NR Radio Access Network (NG-RAN) functions (e.g., 205) and 5G Core (5GC) network functions (e.g., 210), endpoint proxy 240, and a satellite-to-ground communication interface 242 for communicating with NTN gateway 106. The NG-RAN functions (e.g., 205) support the ability of terrestrial NG-RAN to enable UE 102 to use NR access SV 104. 5GC function 210 supports the ability of terrestrial 5GC to support all network capabilities to enable UE 102 to access 5G on SV 104. NG-RAN function 205 may include the functions of base stations (such as gNBs), as described later for terrestrial PLMN 108. 5GC function 210 may include the functions of terrestrial 5GC as described later, and may include multiple 5GC functional elements, such as AUSF 212, AMF 214, SMF 216, UPF 218, NEF 220, UDM 222, PCF 224, SMSF / SMSC 226, IMS 230, and MGW 232. The functional elements of NG-RAN 205 and 5GC 210 may not be separate physical elements as in terrestrial NG-RAN and terrestrial 5GC, but may be different logical functions or different processes running on a single computing system in SV 104. However, from the perspective of UE 102, the functional elements of SV 104 can perform the same functions as those performed by the elements of terrestrial 5G-RAN and terrestrial 5GC, and the communication and signaling between UE 102 and SV 104 can completely or almost completely correspond to the signaling between UE 102 and terrestrial NG-RAN and terrestrial 5GC. Therefore, the functions performed by each of AUSF 212, AMF214, SMF 216, UPF 218, NEF 220, UDM 222, PCF 224, SMSF / SMSC 226, IMS 230, and MGW 232 can correspond to those referenced later. Figure 4The functions described in AUSF 412, AMF 414, SMF 416, UPF 418, NEF420, UDM 422, PCF 424, SMSF / SMSC 426, IMS 430, and MGW 432 are for similarly named elements (e.g., AUSF 212 and AUSF 412) that perform the same or similar functions.

[0070] From the perspective of UE 102, endpoint proxy 240 can mimic or emulate the communication behavior of remote endpoint 116. Therefore, UE 102 can communicate with endpoint proxy 240 in exactly the same way that UE 102 can communicate with remote endpoint 116. Endpoint proxy 240 substitutes for remote endpoint 116 and receives any data and service information initiated by mobile station transmitted by UE 102, and returns any responses to UE 102 at a lower protocol level (e.g., transport protocol level) to enable communication initiated by mobile station from UE 102. This means that UE 102 can initiate communication to remote endpoint 116, which is intercepted and stored by endpoint proxy 240 in the same way that UE 102 would initiate communication to remote endpoint 116 via a terrestrial PLMN or using SV 104 in real-time mode. Endpoint proxy 240 can be referred to as an endpoint proxy function because it can be software, rather than a physical (e.g., hardware) component of SV 104, that is, the firmware functionality of SV 104. It should be understood that since endpoint agent 240 is part of SV104, the actions of endpoint agent 240 are also the actions of SV 104. See later. Figure 3 and Figures 7 to 9 The interaction between UE 102 and endpoint agent 240 is described in more detail.

[0071] The satellite-to-ground communication interface 242 supports communication between SV 104 and NTN gateway 106, as well as the associated terrestrial storage and forwarding center (SFC) 202. The satellite-to-ground communication interface 242 is used to support feeder link 103, and the signaling and procedures used between the satellite-to-ground communication interface 242 and the storage and forwarding center (SFC) 202 may not be standardized and may be proprietary to the satellite spacecraft operator.

[0072] Figure 3 An example communication system 300 is shown for supporting end-to-end communication in S&F mode between UE 102 and one or more remote endpoints 116 using SV 104, SFC 202, and terrestrial PLMN 108. Communication system 300 may include all of communication system 200 and may correspond to communication system 100; common elements in these communication systems are indicated by the same labels. Communication system 300 includes... Figure 2The SFC 202 is shown. The SFC 202 includes or is connected to an NTN gateway 106 to communicate with the satellite-to-ground communication interface 242 in the SV 104. The SFC 202 includes a UE agent 340. The UE agent 340 may resemble the endpoint agent 240 in the communication system 200, but instead of mimicking the behavior of the remote endpoint 116, it mimics the behavior of the UE 102 from the perspective of the remote endpoint 116. The UE agent 340 stores mobile station-initiated data and service information transmitted by the UE 102. This mobile station-initiated data and service information is initially stored by the endpoint agent 240 in the SV 104, but is subsequently passed from the SV 104 to the SFC 202 when the feeder link 103 becomes available between the SV 104 and the SFC 202. The UE agent 340 transmits the mobile station-initiated data and service information to the remote endpoint 116 via the terrestrial PLMN 108. UE agent 340 mimics the behavior of UE 102 when accessing terrestrial PLMN 108 and subsequently transmitting mobile station-initiated data and service information to remote endpoint 116. If subsequent mobile station termination data and service information is transmitted to UE 102 from remote endpoint 116, this termination data and service information is initially stored in UE agent 340 and later transmitted to endpoint agent 240 in SV 104 when feeder link 103 becomes available for service link 101 to UE 102 later. UE agent 340 can be referred to as a UE agent function because it can be software of the firmware function of SFC 202, rather than a physical (e.g., hardware) component of SFC 202. It is understood that since UE agent 340 is part of SFC 202, the actions of UE agent 340 are also the actions of SFC 202. It should be noted that SFC 202 can be any enhanced ground-based server that provides such functionality, and therefore can be called by other names or simply "server" or "store-and-forward center"—these are the terms used here to illustrate the concept.

[0073] although Figure 2The diagram shows that SV 104 supports 5G NR access for UE 102. However, alternative internal architectures of SV 104 can support 4G LTE access, future 6G access, or other access types. For example, when SV supports 4G LTE access, NG-RAN205 can be replaced with Evolved Universal Terrestrial Radio Access Network (E-UTRAN), 5GC 210 can be replaced with Enhanced Packet Core (EPC), and AMF 214, UPF 218, and UDM 222 plus AUSF 212 can be replaced with Mobility Management Entity (MME), Serving Gateway (SGW) plus Packet Data Network Gateway (PGW), and Home Subscriber Server (HSS), respectively, which can support similar or identical functionality to AMF 214, UPF 218, and UDM 222 plus AUSF 212.

[0074] Figure 3 Two times, T1 and T2, are shown. At time T1, SV 104 has no feeder link and is providing service link 101 to UE 102, enabling UE 102 to transmit mobile station-initiated data and service information to SV 104, and enabling SV 104 to transmit mobile station-terminating data and service information to UE 102. At time T2, SV 104 has no service link to UE 102 but has feeder link 103 to SFC 202, enabling SV 104 to transmit mobile station-initiated data and service information stored in endpoint agent 240 to UE agent 340 in SFC 202, and enabling UE agent 340 in SFC 202 to transmit mobile station-terminating data and service information back to endpoint agent 240 in SV 104. In cases where discontinuous feeder links are supported, times T1 and T2 may differ. In one example, time T1 initially occurs when UE 102 first begins accessing SV 104 in S&F mode; then, time T2 occurs later when SV 104 moves away from UE 102 and becomes able to access SFC 202 associated with ground PLMN 108. However, in another example, time T2 may occur first when SV 104 transmits mobile station-initiated data and service information to UE agent 340 and SFC 202 returns mobile station-terminating data and service information to endpoint agent 240 in SV 104. In this case, SV 104 can move away from SFC 202 and can later provide service link 101 to UE 102, and the mobile station-terminating data and service information received from SFC 202 at time T1 will be transmitted to UE 102 at time T2. The detailed procedures for these operations are described below.

[0075] like Figure 3As shown, Mobile Station Initiated (MO) and Mobile Station Termination (MT) services and media data can be transferred between UE 102 and endpoint 116 via endpoint agent 240 in SV104 and UE agent 340 in store and forward center (SFC) 202 operated by SVO, which acts as a Uu-level NTN gateway 106 connected to a terrestrial PLMN 108 (referred to here as option (a)), or as a gNB or Trusted Non-3GPP Gateway Function (TNGF) at the N2 level (referred to here as option (b)), or supports terrestrial PLMN capabilities itself (referred to here as option (c)).

[0076] Each SV 104 internally supports all functions of the terrestrial NG-RAN and 5GC regarding interaction with UE 102. Therefore, each SV 104 supports functions such as gNB, AMF, SMF, UPF, UDM, etc., and supports the Uu and N1 interfaces to UE 102. These SV functions can interact internally according to the 5GS interface and SBI, but can also bypass 3GPP protocols and procedures with proprietary equivalents. The UDM 222 function can be pre-configured with the identifiers, subscription information, and security credentials of all UE 102s that have subscribed to S&F mode to the SVO and its SV 104. When no FL is available, the SV 104 can broadcast an indication of support for PLMNs that are permitted to provide S&F coverage at locations covered by the SV 104 and with which the SVO has a commercial relationship, and can indicate the S&F mode in System Information Block (SIB) 1 (SIB1). The PLMN Mobile Country Code (MCC) and Mobile Network Code (MNC) broadcast in SIB1 can be the same as those broadcast for real-time mode. A UE with an S&F subscription to an SVO and permitted access to a broadcast PLMN can then access the SV according to the 3GPP solution in version 17 or 18. If the S&F mode is recognized, a UE without an S&F subscription or that supports or is not permitted access to any broadcast PLMN may not attempt to access SV 104, or may otherwise be rejected when attempting to access.

[0077] For UE 102's initial access to SV 104 operating in S&F mode (where SV 104 does not use or support inter-satellite links (ISL)), UE 102 can perform a standard RRC connection establishment with SV 104 (e.g., with NG-RAN 205 element in SV 104) and an initial NAS registration to SV 104 (e.g., to AMF 214 element in SV 104). UE 102 can then establish a PDU session to SV 104 (e.g., to UPF 218 element in SV 104) and perform IMS registration (e.g., to IMS 230 element in SV 104). From UE 102's perspective, SV 104 can support UE 102's initial access and these operations by acting as UE 102's home PLMN (HPLMN) or equivalent HPLMN (EHPLMN). This will mean that one or more identifiers of UE 102 and its security credentials may need to be pre-configured in SV 104 (e.g., in the UDM 222 element within SV 104). UE 102 will also select and register with a PLMN advertised as being supported by SV 104.

[0078] The user of UE 102 can then initiate "MO transactions" to transmit MO data and MO SMS, initiate outgoing IMS voice or other media calls, request internet access, or perform email access. SV 104 can emulate remote endpoint 116 for each case via endpoint agent 240 in SV 104, which can be created specifically for UE 102 after UE 102's initial NAS registration with SV 104. Endpoint agent 240 can replace remote endpoint 116 and can accept and store any media and service data transmitted by UE 102, as well as any associated metadata (e.g., data network (DN) and IP address of the PDU session, remote endpoint 116 address, transport protocol details), and can provide any responses at lower protocol levels (e.g., for TCP, NAS, SIP, and HTTP) to avoid UE 102 timeouts. Endpoint agent 240 can receive data from UE 102 or data related to UE 102 via integration with certain network functions (NFs) in SV 104 5GC 210, or via a Standard Service-Based Interface (SBI) or other interfaces from certain NFs (e.g., AMF 214, IMS 230, UPF 218). Endpoint agent 240 can also store the location and time of UE access information—e.g., the geodetic latitude and longitude of UE 102 and NAS registration time. For example, an NG-RAN element (e.g., 205) of SV 104 can determine or obtain the location of UE 102 and pass it to the AMF 214 element, which in turn passes it to endpoint agent 240.

[0079] Endpoint agent 240 can provide responses to UE 102 and its user, indicating that S&F mode is in operation and when MO communication from UE 102 can reach remote endpoint 116 and / or when a response from remote endpoint 116 can be received back by UE 102 later. For example, for MO voice media transmitted by UE 102, after UE 102 establishes an MO voice call with endpoint agent 240, a pre-configured voice recording can be returned by endpoint agent 240 to UE 102 and its user (e.g., at the application level), stating: “Communication is now in store-and-forward mode. Please record a message and hang up or press '0' for more options when finished. Your message will be delivered in approximately X minutes, and you can receive a response in approximately X+Y minutes.” For email access, endpoint agent 240 can prompt for login / password and the date or sender of interest. For MO data, simplex operation (e.g., using non-Internet Protocol (non-IP), Internet Protocol (IP), User Datagram Protocol (UDP) plus IP (UDP / IP)) or duplex operation (e.g., using Transmit Control Protocol (TCP) plus IP (TCP / IP)) can be supported, where the endpoint agent returns a response at the transport level (e.g., returning an acceptance response to a request for a new TCP connection from UE 102) to allow UE 102 to transmit MO data in the absence of transport protocol failures. Emergency voice calls can also be supported—but with some delay upon arrival at the Public Safety Answering Point (PSAP) remote endpoint 116.

[0080] For Internet access by UE 102, endpoint agent 240 can return a pre-configured SV webpage in response to each Internet access, and later only return the correct webpage as part of the MT data. For example, if UE 102 (or a user of UE 102) enters "www.msn.com", endpoint agent 240 can return an internal webpage stating "Your query for www.msn.com will be answered in approximately X minutes. Please try your query again later." Sometime after UE agent 340 has accessed the website via terrestrial PLMN 108 and the website response has been received and uploaded to another SV 104 (see below) and the other SV 104 becomes accessible to UE 102, UE 102 or a user of UE 102 can retrieve the website response by re-entering the query "www.msn.com".

[0081] UE 102 or its user can continue the session with SV 104 in S&F mode to initiate further MO transactions, after which UE 102 will be deregistered by SV 104 (e.g., by UDM 222 element) before UE 102's access to SV 104 is lost (due to orbital movement of SV 104). This avoids maintaining the 5GC UE 102 registration status across different SV 104s, which can be complex, error-prone, and unnecessary. SV 104 may not hand over UE 102 to another SV 104, and UE 102 may not attempt handover or cell change to another SV 104, which will be unaware of UE 102's registration status in the previous SV 104 (without ISL). For example, if each SV 104 broadcasts support for a single TA that is different from the tracking area (TA) supported (and broadcast) by other SV 104s, and if all TAs except the current TA of the currently accessing SV 104 are considered prohibited TAs for UE 102 by both UE 102 and the currently accessing SV 104, then cell change and handover for UE 102 can be avoided. SV 104 may also, or alternatively, notify UE 102 that cell change is prohibited during UE 102's NAS registration with SV 104.

[0082] After UE 102 is deregistered and due to orbital movement, SV 104 will typically move to a location where feeder link access is available for a suitable terrestrial PLMN 108. This may not happen immediately, and in some cases, SV 104 may need to orbit the Earth several times before feeder link access is available for a terrestrial PLMN 108 with permitted services for UE 102. For example, national regulations may require the terrestrial PLMN 108 serving UE 102 to be in the same country. All MO media and service data, as well as metadata, previously transmitted by UE 102 and stored by SV 104 endpoint agent 240, can then be copied (downloaded) (e.g., via satellite-to-ground communication interface 242 in SV 104 and NTN gateway 106 connected to or part of SFC 202) to SFC 202, and UE agent 340 can be created to manage this data on behalf of the real UE 102 and deliver it to remote endpoint 116. If UE 102 registers in SV 104 but does not initiate any MO transactions, the mere existence of UE 102 can be transmitted to SFC 202, which can still lead to the creation of UE agent 340. SFC 202 and UE agent 340 then forward all MO media and service data to remote endpoint 116 via the serving terrestrial PLMN 108, and can subsequently or later receive back MT media and service data, which is later returned to UE 102.

[0083] With SV 104 supporting and using ISL, UE 102's initial access to SV 104 with S&F mode can be more flexible than in the case without ISL, as just described. In the ISL case, UE 102 can access multiple SV 104s (e.g., with consecutive SL availability), and SV 104 can use ISL to support UE 102's mobility to a new SV 104 via handover or cell change. To manage this, each SV 104 can broadcast support for different TAs to force NAS registration updates from UE 102 when a cell change to a new SV 104 is performed. If UE 102 can be handed over to another SV 104 or a cell change to another SV 104 can be performed before losing access to the current SV 104, the current SV 104 does not deregister UE 102. If access to UE 102 is lost and if no handover or cell change occurs to another SV 104 for UE 102, SV 104 may simply deregister UE 102. For a handover or cell change of UE 102 to another SV 104, the complete UE 102 connection state (e.g., for NAS, PDU sessions, IMS) and the endpoint agent 240 state of all ongoing MO transactions for UE 102 to the current SV 104 are passed from the current SV 104 to the new SV 104 using ISL (e.g., using a proprietary ISL procedure). If the new SV 104 will arrive at the feeder link with access to the ground PLMN 108 before the current SV 104 will have feeder link access, the endpoint agent 240 state of completed MO transactions for UE 102 may be passed from the current SV 104 to the new SV 104 only. This could result in a series of SV 104s (at different times) receiving MO media and service data from UE 102 and later accessing SFC 202 with different (e.g., consecutive) endpoint agent 240 states of UE 102. Each of these SV 104s then passes its own endpoint agent 240 state (including the stored MO data from UE 102) to SFC 202. Tags or markers can be assigned to different portions of the MO data to avoid passing information for MO transactions more than once—for example, SFC 202 can log the passed MO transactions and can only accept new MO transactions.

[0084] As previously described, the Storage and Forwarding Center (SFC) 202 can connect to the terrestrial PLMN 108 in three different ways: as a Uu-level NTN gateway 106 (option (a)), as an N2-level gNB or TNGF (option (b)), or support terrestrial PLMN capabilities itself (option (c)).

[0085] For option (a), the interaction between SFC 202 and the terrestrial PLMN 108 can simulate real-time access of UE 102 to the terrestrial PLMN 108 (e.g., where UE 102 accesses the terrestrial PLMN 108 in real-time mode using SV 104). SFC 202 and UE agent 340 then simulate the presence of UE 102 by interacting with the terrestrial serving PLMN 108 as if UE 102 were accessing LEO or MEO SV 104 in real-time. This can be accomplished by simulating the presence of a virtual “fixed” SV 104 in SFC 202 that provides coverage to all UEs 102 subscribing to S&F mode in the area where the terrestrial serving PLMN 108 provides S&F mode coverage via SV 104. SFC 202 can be part of an SVO-owned NTN gateway 106 used for both real-time and S&F modes, or it can be dedicated solely to S&F mode. SFC 202 can act as NTN gateway 106 to interface with the terrestrial serving PLMN 108, and can support all protocols (from the physical layer up) of the existing NG-RAN and 5GC Uu and N1 interfaces to the gNB of the terrestrial serving PLMN 108. It can also reproduce the UE 102 signaling and interactions required to transmit MO media and service data to the remote endpoint 116 via the terrestrial serving PLMN 108. SFC 202 and UE agent 340 can first register UE 102 with the terrestrial serving PLMN 108, and then establish any PDU session and perform any IMS registration, as previously performed by the real UE 102 to SV 104.

[0086] For option (b), SFC 202 connects as a base station (gNB in ​​this example) to the 5GC in the terrestrial serving PLMN 108, and can therefore support the 5GC N2 and N3 interfaces, which will avoid supporting the physical layer Uu interface. UE agent 340 can also remain permanently in CM connected state to avoid unnecessary paging and service requests from the terrestrial serving PLMN 108 5GC. Alternatively, SFC 202 can connect to the terrestrial serving PLMN 108 5GC as a Trusted Non-3GPP Gateway Function (TNGF) for 5G Non-3GPP Access, although this may not allow the provision of NR cell and NR TA information to the terrestrial serving PLMN 108 5GC.

[0087] For option (c), SFC 202 may include or be part of a terrestrial serving PLMN 108. For example, SFC 202 may be a server that supports interaction with other networks (e.g., Internet 112, PSTN 114, other PLMNs, and network 110) for S&F mode, but may not support real-time access for UE 102. Alternatively, the terrestrial serving PLMN 108 may support real-time access for UE 102 via SV 104 and / or terrestrial access for UE 102. SFC 202 then forwards UE 102's MO media and service data to remote endpoint 116 and can receive MT media and service data responses using N6, Mm, and other external PLMN interfaces.

[0088] SFC 202 and UE agent 340 can interact with the serving terrestrial PLMN 108 in a manner similar to options (a) and (b). For example, SFC 202 and UE agent 340 can indicate the current serving TA Identifier (TAI) and serving cell global identifier (CGI) of UE 102 to gNB 406 (option (a)) or AMF 414 (option (b)), based on (e.g., mapped from) the latest known ground location of UE 102. For example, the ground location of UE 102 can be mapped to the corresponding terrestrial PLMN 108 serving TAI and serving CGI. The serving TAI and serving CGI of UE 102 can be identifiers defined for the terrestrial PLMN 108, and therefore the actual last known location of UE 102 can be indicated to the terrestrial PLMN 108 (e.g., AMF 414 or gNB 406). Similarly, any IP address assigned to UE 102 by SV 104 (e.g., SMF 216 in SV 104) can be mapped to other IP addresses of UE 102 assigned by the terrestrial PLMN 108 (e.g., SMF 416 in 5GC 310-1).

[0089] When UE 102 subscribes to S&F mode services from SV 104, which belongs to an SVO, the SFC 202 of that SVO and SV 104 can be pre-configured with UE 102's identity and security credentials. SFC 202 (or UE agent 340) can then treat the terrestrial PLMN 108 as a serving PLMN (unless the terrestrial PLMN 108 also belongs to the SVO when it can act as an HPLMN or EHPLMN for UE 102), and can perform NAS registration and IMS registration of UE 102 to the terrestrial PLMN 108. UE agent 340 can then forward the MO data and service information previously received from endpoint agent 240 in SV 104 to remote endpoint 116.

[0090] In the case of MO voice media, UE agent 340 can play a pre-configured voice message to remote endpoint 116 before transmitting the voice media data of UE 102 to remote endpoint 116. For example, the pre-configured voice message could be: "This is a message transmitted by user ABC at time XYZ. After you hear the message, you will be prompted to repeat the message, reply to the message, or end the call." Remote endpoint 116 (e.g., the user) can then provide a reply, which is regarded by UE agent 340 as a new MT voice message to be returned to UE 102.

[0091] In the case of Internet access, UE agent 340 may provide login when needed (and if provided earlier by UE 102), transmit Internet (e.g., HTTP) queries received earlier from UE 102, and store any returned Internet (e.g., HTTP) web pages for later transmission to UE 102.

[0092] For email access, UE agent 340 may provide login as needed (and if provided earlier by UE 102), query emails, store any returned web pages, and retrieve specific emails based on earlier UE 102 preferences. For this purpose, SFC 202 may need to support specific email systems (e.g., Gmail).

[0093] When the MO media and service data transfer is complete, UE agent 340 may remain in CM connected state indefinitely (or at least until S&F support for UE 102 is no longer needed) to avoid later paging (e.g., via AMF 414 or gNB 406), although transitioning to idle state is also permitted.

[0094] Next, in Figure 4 , Figure 5 and Figure 6 More detailed examples of options (a), (b), and (c) are provided in the document.

[0095] Figure 4 An example network architecture 400 capable of supporting satellite access for both real-time and S&F modes is illustrated, for example, using 5G NR. Network architecture 400 can be an example of communication system 100 and may include communication systems 200 and 300. Although the examples using 5G NR describe aspects of network architecture 400, the concepts presented herein can also be applied to other types of core networks. Figure 4 A network architecture 400 with a transparent SV 104 in real-time mode is illustrated. The transparent SV 104 can implement frequency conversion and radio frequency (RF) amplification in both the uplink (UL) and downlink (DL) directions and can correspond to an analog RF repeater. For example, the transparent SV 104 can receive uplink (UL) signals from the served UE 102 and can redirect the combined signal DL to an earth station (e.g., 106) without demodulating or decoding the signal. Similarly, the transparent SV 104 can receive UL signals from an earth station (e.g., 106) and redirect the signal downlink to the served UE 102 without demodulating or decoding the signal. However, the SV 104 can perform frequency conversion on the received signals and can amplify and / or filter the received signals before transmitting them.

[0096] Network architecture 400 may include multiple UEs 102, multiple SVs 104-1, 104-2, and 104-3 (collectively referred to herein as SV104), multiple NTN gateways 106-1 to 106-3 (collectively referred to herein as NTN gateway 106), and multiple NR NodeBs (gNBs) 406-1 to 406-3 (collectively referred to herein as gNB 406) capable of communicating with UEs 102 via SV 104 and with SFC 202 in S&F mode and being part of NG-RAN 305. Network architecture 400 is illustrated to also include components of multiple 5G networks, including 5G core networks (5GCN or 5GC) 310-1 and 310-2 (collectively referred to herein as 5GCN or 5GC 310) Figure 4 Examples of various components within 5GC1 310-1 that can operate with NG-RAN 305 are shown. 5GC2 310-2 and other 5GCs may include the same, similar, or different components and associated NG-RAN; to avoid unnecessary confusion, Figure 4 Not shown in the example.

[0097] UE 102 may include and / or be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Location Enabled (SUPL) terminal (SET), or some other name. Furthermore, UE 102 may correspond to a cellular phone, smartphone, laptop computer, tablet computer, PDA, tracking device, navigation device, Internet of Things (IoT) device, or some other portable or mobile device.

[0098] UE 102 is configured to communicate with 5GC 310 in real-time mode via SV 104, an earth station (e.g., NTN gateway 106-3), and gNB 406-3. Real-time mode access to the 5G network is provided to UE 102 via wireless communication between each UE 102 and the serving gNB 406-3, through SV 104 and the earth station (e.g., NTN gateway 106-3). gNB 406-3 can provide wireless communication access to 5GC 310 on behalf of each UE 102 using 5G NR.

[0099] The gNB 406 in NG-RAN 305 can communicate with the AMF 414 in 5GC 310-1. For example, the gNB 406 can provide an N2 interface to the AMF 414. The N2 interface between the gNB 406 and 5GC 310 can be the same as or similar to the N2 interface supported between the terrestrial gNB and 5GC 310 for UE 102 to perform terrestrial NR access, and the Next Generation Application Protocol (NGAP) can be used between the gNB 406 and AMF 414. The AMF 414 can support UE 102's mobility in real-time mode, including radio cell changes and handover, and can participate in supporting signaling connections to UE 102 and possibly data and voice bearers for UE 102.

[0100] Network Open Function (NEF) 420 may be included in 5GC 310-1, for example, connected to AMF 414. In some specific implementations, NEF 420 may be connected to communicate directly with remote endpoint 116. NEF 420 may support the secure opening of capabilities and events concerning 5GC 310-1 and UE 102 to remote endpoint 116, and may enable the secure provision of information from remote endpoint 116 to 5GC 310-1.

[0101] User plane function (UPF) 418 supports voice and data bearers for UE 102 and enables UE 102 to access other networks, such as the Internet 112, for voice and data. UPF 418 can be connected to gNB 406. UPF 419 functions may include: external protocol data unit (PDU) session interconnection points to data networks, packet (e.g., Internet Protocol (IP)) routing and forwarding, user plane portion of packet inspection and policy rule enforcement, user plane quality of service (QoS) handling, downlink packet buffering, and downlink data notification triggering.

[0102] As illustrated, the Session Management Function (SMF) 416 is connected to the AMF 414 and the UPF 418. The SMF 416 may have the ability to control local and central UPFs within a PDU session. The SMF 416 can manage the establishment, modification, and release of PDU sessions for UE 102, perform IP address allocation and management for UE 102, act as a Dynamic Host Configuration Protocol (DHCP) server for UE 102, and select and control the UPF 418 on behalf of UE 102.

[0103] AMF 414 typically supports UE 102's network access and registration in real-time mode, UE 102's mobility (including radio cell changes and handover), and can participate in supporting signaling connections to UE 102 and possibly data and voice bearers for UE 102. The role of AMF 414 can be to register the UE during the registration process, as discussed herein. AMF 414 can page UE 102, for example, by transmitting paging messages via one or more radio cells in the tracking area where UE 102 is located.

[0104] The Policy Control Function (PCF) 424 supports a unified policy framework for managing network behavior, provides policy rules to other NFs for enforcement, accesses subscription information related to policy decisions in the Unified Data Repository (UDR), and supports PDU set processing.

[0105] Unified Data Management (UDM) 422 supports the generation of 3GPP AKA authentication credentials, user identification processing (e.g., storage and management of subscription permanent identifiers (SUPI) for each subscriber in a 5G system), unhiding of privacy-preserving subscription hidden identifiers (SUCI), access authorization based on subscription data, MT-SMS delivery, and subscription management.

[0106] The Authentication Server Function (AUSF) 412 supports authentication of UE 102 for 3GPP access and untrusted non-3GPP access, as well as authentication of UE 102 for disaster roaming services.

[0107] The Short Message Service Function (SMSF) supports SMS delivery, SMS management subscription data inspection, and SMS delivery on the Non-Access Stratum (NAS). The SMSF can interact with the SMS Center (SMSC) via the SMS Interoperability Mobile Switching Center Server (MSC) or Gateway MSC to deliver MT SMS messages from remote endpoint 116 to UE 102 or MO SMS messages from UE 102 to remote endpoint 116. In such cases (and others), the SMSC can act as the primary relay point for SMS delivery and is typically located within the HPLMN of any UE that initiates the SMS message. Figure 4 The SMSF / SMSC 426 is shown, which means SMSF, SMSC, or SMSF in combination with SMSC.

[0108] The IP Multimedia Subsystem (IMS) 430 uses the Session Initiation Protocol (SIP) to support sessions between UE 102 and remote endpoint 116. IMS 430 typically includes several SIP-enabled servers known as Call Session Control Functions (CSCFs), including the Proxy CSCF (P-CSCF), Interrogation CSCF (I-CSCF), Serving CSCF (S-CSCF), and Media Gateway Control Function (MGCF). The P-CSCF is typically the entry point for SIP messages exchanged between UE 102 and IMS 430 to reach IMS 430. Functions performed by the P-CSCF may include forwarding SIP registration requests received from UE 102 to an entry point in the IMS of UE 102's HPLMN (e.g., I-CSCF), forwarding SIP messages received from UE 102 to another SIP server (e.g., S-CSCF), forwarding SIP requests and responses to UE 102, and maintaining its own security association with each UE 102, for example, as defined in 3GPP Technical Specification (TS) 33.203.

[0109] The I-CSCF can be the contact point within IMS 430 for all SIP connections of UE 102 destined for Access Ground PLMN 108. After UE 102 transmits a SIP registration message to the P-CSCF, the P-CSCF can typically forward the SIP registration message to the I-CSCF in the IMS of UE 102's HPLMN. The I-CSCF can then determine the S-CSCF for UE 102 in the HPLMN IMS and forward the SIP registration message to that S-CSCF.

[0110] The S-CSCF performs session control services for UE 102 and other UEs in the HPLMN 108. It maintains session state to support the service. For SIP registration, the S-CSCF can act as a SIP registrar as defined in IETF RFC 3261. The S-CSCF can also act as a proxy server as defined in IETF RFC 3261 or a user agent as defined in IETF RFC 3261. The S-CSCF can be used to route SIP calls terminated by a mobile station to the destination UE 102. In this case, the SIP call terminated by the mobile station will initially be routed to the S-CSCF in the HPLMN of the destination UE 102, and then the S-CSCF will use the previous SIP registration of the destination UE 102 to route the SIP call terminated by the mobile station to the P-CSCF in the network serving the destination UE 102.

[0111] The MGCF can control the functionality of the media gateway MGW 432. For example, if UE 102 initiates a voice call via NR that requires passage through PSTN 114, or when an incoming circuit-switched voice call from PSTN 114 arrives at PLMN 108 to be delivered to UE 102 via NR, the MGW 432 can support the conversion of packet-based media (e.g., VoIP) to the corresponding circuit-switched media, such as conversion to circuit-switched voice.

[0112] As described above, while network architecture 400 is described in relation to 5G technology, network architecture 400 can be implemented to support other communication technologies (such as GSM, WCDMA, LTE, 6G, etc.) for supporting mobile devices such as UE 102 and interacting with them (e.g., to enable voice, data, location and other functionalities).

[0113] So far, the communication system illustrated in network architecture 400 has been described in terms of its support for real-time access of UE 102 to terrestrial PLMN 108 via SV 104, which then accesses NTN gateway 106-3, which in turn accesses terrestrial PLMN 108 via gNB 406-3. The communication system illustrated in network architecture 400 can also support UE 102 accessing terrestrial PLMN 108 via SV 104 in store-and-forward mode. In this case, when SV 104 does not have feeder link access to terrestrial PLMN 108, UE 102 communicates with SV 104 in store-and-forward mode as previously described. Later, SV 104 obtains feeder link access to terrestrial PLMN 108 by accessing SFC 202 via NTN gateway 106. Figure 4The two SFCs 202 shown supporting this are SFC 202-1 and SFC 202-2 accessing gNB 406-1 and gNB 402-2. For option (a), SFCs 202-1 and 202-2 access gNB 406-1 and 406-2 by mimicking the communication signaling of NTN gateway 106. gNB 406-1 and 406-2 may not need to know that they are communicating with SFC 202, rather than communicating with SV 104 in real-time mode via NTN gateway 106-1 or 106-2. From the perspective of the terrestrial PLMN 108 including gNB 406 and 5GC 310-1, it can be seen that UE agent 340 and SFC-202-1 or 202-2 are UEs 102 accessing SV 104 in real-time mode via NTN gateway 106. SFC 202's access to gNB 406 distinguishes option (a) from two other options. Both gNB 406 and 5GC 310-1 components can treat signaling from UE agent 340 as if it were initiated by UE 102, which means there may be no new impact on gNBs 406 or 5GC 310-1 components.

[0114] Figure 5 A diagram illustrating an example network architecture 500 supporting NTN access, such as using 5G NR, as presented herein. While network architecture 500 is described in relation to 5G technology as an illustrative concept, network architecture 500 can also be implemented to support other communication technologies. Figure 5 The network architecture 500 shown is similar to Figure 4 The network architecture shown here uses similar or identical specified components. However, Figure 5 The network architecture supporting option (b) is illustrated, where SFCs 202-1 and 202-2 connect to 5GC 310-1 in the terrestrial PLMN 108 instead of NG-RAN 305. This means that SFCs 202-1 and 202-2 can emulate the behavior of gNB 406 and connect to AMF 414 and UPF418 in 5GC 310-1 in the same manner as gNB 406. For example, SFCs 202-1 and 202-2 can support the NGAP protocol when accessing AMF 414. SFC 202 and UE agent 340 can emulate the signaling and procedures that will be performed by gNB 406 for UE 102, which accesses the terrestrial PLMN 108 in real-time mode via SV 104 and gNB 406.

[0115] Figure 6A diagram illustrating an example network architecture 600 supporting NTN access, such as using 5G NR, as presented herein. While network architecture 600 is described in relation to 5G technology as an illustrative concept, network architecture 600 can also be implemented to support other communication technologies. Figure 6 The network architecture 600 shown is similar to Figure 4 and Figure 5 The network architecture shown here uses similar or identical specified components. However, Figure 6 The network architecture supporting option (c) is illustrated, where SFC 202-1 and 202-2 are part of a terrestrial PLMN 108. Two alternative types of support are possible here. In the case of SFC 202-1, SFC 202-1 can be part of a terrestrial PLMN 108, which also includes 5GC310-1 and possibly NG-RAN 305 (…). Figure 6 (Not shown in the diagram). SFC 202-1 can then connect to elements in 5GC 310-1, such as AMF 414 and UPF 418, and possibly other elements. The signaling and procedures used on the link between SFC 202-1 and other elements in the terrestrial PLMN 108 (such as AMF 414 and UPF 418) may not be standardized, but may be proprietary to the terrestrial PLMN 108. However, SFC 202-1, the UE agent 340 contained therein, and other elements in the terrestrial PLMN 108 enable UE agent 340 to communicate with remote endpoint 116 via other networks 110, the Internet 112, and PSTN 114 in the same manner as UE 102 communicates with remote endpoint 116 when accessing the terrestrial PLMN 108 in real-time mode using SV 104. SFC 202-2 corresponds to and supports a complete terrestrial PLMN 108, and may not include 5GC 310 or NG-RAN 305. SFC 202-2 can use proprietary signaling and procedures internally and communicate with any other components in the terrestrial PLMN 108, and may not necessarily support real-time access for UE 102. SFC 202-2 can connect to other networks 110, the Internet 112, and PSTN 114 as if it were a terrestrial PLMN 108 supporting real-time access for UE 102.

[0116] although Figure 4 , Figure 5 and Figure 6The diagram shows that the terrestrial PLMN 108 supports 5G NR, but alternative architectures for the terrestrial PLMN 108 can support 4G LTE access, future 6G access, or other access types. For example, when the terrestrial PLMN 108 supports 4G LTE access, NG-RAN 305 can be replaced with E-UTRAN, 5GC 310 can be replaced with EPC, and AMF 414, UPF418, and UDM 422 plus AUSF 412 can be replaced with MME, SGW plus PGW, and HSS, respectively, which can support similar or identical functions to AMF414, UPF 418, and UDM 422 plus AUSF 412.

[0117] The following describes the return of MT data from remote endpoint 116 to UE 102 in S&F mode. For options (a), (b), and (c), the MT data may be provided to SFC 202 and stored in UE agent 340 of UE 102, which simulates the continuous availability of UE 102. For options (a) and (b), SFC 202 may need to recognize and respond to paging messages from the serving terrestrial PLMN 108 unless UE agent 340 remains in CM connected state. Periodically, SFC 202 uploads (e.g., via proprietary means) UE 102's MT media and service data to one or more SVs 104, which will later provide coverage at the location of UE 102. If regulations permit, and if different SFCs 202 can access the appropriate SV 104 before SFC 202, SFC 202 may upload itself or multiple times via different SFCs 202.

[0118] The SV 104 endpoint agent 240, previously used by UE 102 to transmit MO data from UE 102, can be reused by SFC 202 to transmit MT data to UE 102. Alternatively, the endpoint agent 240 in SV 104 can be specifically created to transmit MO data from UE 102 or to UE 102, and can be erased from SV 104 when it is no longer necessary to transmit MO data or MT data to UE 102.

[0119] UE 102 can access available SV 104 at any time to transmit MO data and / or receive any available MT data, but can (e.g., via endpoint agent 240) advise the user when they expect an MT data response to any transmitted MO data.

[0120] When UE 102 accesses another SV 104 in S&F mode, UE 102 can register with SV 104 as previously described. SV 104 can then check if there is any new MT data to be transmitted to UE 102. If so, an endpoint agent 240 for UE 102 may already exist in SV 104; otherwise, SV 104 can create an endpoint agent 240 for UE 102. If there is no MT data for UE 102 to switch UE 102 to another accessible SV 104, SV 104 can use ISL (if supported) if MT data for UE 102 exists in that SV 104; or if the other SV 104 does not provide access to UE 102 or provides poor access, ISL can be used to retrieve UE 102's MT data from the other SV 104. To transfer MT data from SV 104 to UE 102, and in the case of MT voice, SV 104 or endpoint agent 240 can establish an MT SIP call from endpoint agent 240 to UE 102. This endpoint agent can play back voice messages to the user of UE 102 one at a time and may have some type of menu control—for example, to allow the user of UE 102 to repeat and / or respond to MT voice messages.

[0121] For MT SMS, all MT SMS messages can be delivered to UE 102 using existing standards (e.g., using SMS on NAS or SMS on IMS).

[0122] For internet and email access, the user of UE 102 can re-enter the original internet address (e.g., Uniform Resource Identifier (URI)) and / or internet (e.g., HTTP) query, after which the webpage previously received from remote endpoint 116 and forwarded to SV 104 by SFC 202 can be provided to UE 102.

[0123] For email access, if the UE agent 340 in SFC 202 is able to access and retrieve emails from a remote endpoint 116 (e.g., an email server) based on the original email query of UE 102, then the user of UE 102 can also retrieve a specific email by repeating the previous MO email query.

[0124] For simplex MT data (e.g., UDP / IP), any MT data response from remote endpoint 116 can be provided to UE 102 using any PDU session established by UE 102 (which matches any PDU session previously established by UE 102 to initially deliver any MT data) and any new IP address now assigned to UE 102.

[0125] The session between SV 104 and UE 102 can end when all MT data to UE 102 and any new MO data from UE 102 have been transferred. As previously described, UE 102 can also be deregistered or transferred from UE 102 to a new SV 104.

[0126] SV 104 can later update SFC 202 with the delivery status of MT data to UE 102, and can provide any new MO data received from UE 102. SFC 202 can then remove the delivered MT data from all SVs 104, which was previously provided to all SVs for delivery to UE 102. ISL can also be used (if supported) to remove the delivered MT data from SV 104.

[0127] In some respects, aside from MT data related to internet and email access, the process described above for returning MT data to UE 102 can be performed without any special user action. However, the user of UE 102 may subsequently lack control over when MT data can be returned, and there is a risk of receiving the same MT data multiple times from different SV 104s. In the improved delivery method, SV 104 (e.g., endpoint agent 240) first transmits to UE 102 an indication that MT data is available for delivery to UE 102. This indication may be included in an SMS message or UDP / IP message indicating different types of MT media and service data available to UE 102 in SV 104, and having the tag and time originally received by the serving terrestrial PLMN 108. The user can then use an application (sometimes referred to as an "App") to inspect SMS messages (or UDP / IP messages), and then, if the MT data is new (and has not yet been delivered to UE 102), the user can access the application on SV 104 (e.g., which may be part of endpoint agent 240) to initiate and control the delivery of the MT data—for example, by playing voice messages one at a time, triggering the delivery of all undelivered SMS and UDP / IP messages, and viewing any returned internet web pages and emails. Alternatively, the application on UE 102 (which may be accessible to the user of UE 102) can autonomously inspect the MT SMS or UDP / IP messages and verify that at least some of the MT data is new, and then only alert the user if at least some of the MT data is new.

[0128] To support the transmission of additional MO data from and to UE 102, UE 102 may transmit additional MO data at any time to an available SV 104, as previously described, wherein the MO data is then transmitted to SFC 202 and forwarded to remote endpoint 116, also as previously described. Similarly, additional MT data from UE 102 may arrive at UE agent 340 in SFC 202 at any time from one or more remote endpoints 116. The new MT data may then be uploaded by SFC 202 to the appropriate SV 104, which will later provide coverage of UE 102’s last known location or UE 102’s expected new location. New MT data may be added to any previously undelivered MT data of UE 102 already in SV 104. UE 102 then retrieves the new MT data, as previously described, but may optionally retrieve only MT data that has not previously been received by UE 102.

[0129] To support the sequential delivery of MO data to remote endpoint 116 and the sequential delivery of MT data to UE 102, additional procedures can be used. For example, UE 102 may access SV 104 in a specific order (e.g., SV1, SV2, SV3, SV4, etc.). Due to track differences, SV 104 accessed earlier by UE 102 may arrive and obtain the feeder link to SFC 202 later than other SV 104 accessed later by UE 102. For example, the order in which SV 104 arrives at SFC 202 and accesses the feeder link to that SFC could be (in this example) SV3, SV1, SV4, SV2, where SV3 and SV4 have arrived earlier. This could result in MO-related data being delivered to remote endpoint 116 in a different order than that delivered by UE 102 and remote endpoint 116, and MT-related data being received by UE 102 in a different order. UE agent 340 or SFC 202 can correctly order MO data received from SVx (e.g., in this example, x=1, 2, 3, or 4) in such a way that MO data is forwarded to remote endpoint 116 only after all SVs 104 that were accessible at UE 102 earlier than SVx have been accessed, and any MO data from these SVs 104 is forwarded first. In the previous example, this might mean that when SV3 arrives at SFC 202, UE agent 340 or SFC 202 delays forwarding any MO data from UE 102 provided by SV3 until both SV1 and SV2 have arrived at SFC 202. Similarly, when SV4 arrives at SFC 202, UE agent 340 or SFC 202 may delay forwarding any MO data from UE 102 provided by SV4 until SV2 has arrived at SFC 202. SFC 202 can determine the order in which SV 104 will arrive at SFC 202 and the order in which the SV is visible at the known last location or expected new location of UE 102 from the orbit-related data of SV 104 (which can be pre-configured by SVO in SFC 202). Alternatively, in some aspects, UE 102 can indicate to SV 104 the identifier of a previous SV 104 to which UE 102 has previously transmitted MO data, and when SV 104 is accessed by SFC 202, SFC 202 can verify whether these previous SV 104s have already been accessed by SFC 202 or will only be accessed by SFC 202 later. This variant also avoids SFC 202 waiting for the arrival of SV 104 to which UE 102 has not transmitted any MO data.

[0130] Similarly, UE agent 340 or SFC 202 can correctly order the MT data received from remote endpoint 116 from UE 102 by uploading MT data to any SVx, such that (i) the MT data includes all MT data previously uploaded to all SVs 104, which will only become accessible to UE 102 after SVx, unless (ii) the MT data is uploaded to another SV 104 that will become available to UE 102 before SVx. As an example, assume that SFC 202 accesses SV 104 in the order SV1, SV2, SV3, SV4. Also assume that SVs will later become accessible to UE 102 in the order SV3, SV1, SV4, SV2. SFC 202 can then upload the currently available MT data to SV3, such that the MT data includes all data previously uploaded to SV1 and SV2. Similarly, SFC 202 can upload currently available MT data to SV4, but it does not need to include data previously uploaded to SV2, as that data was also uploaded to SV3 and became available to UE 102 before SV4. If UE 102 later receives MT data from SV3 first, it can treat the MT data received later from SV1 and SV2 as copies and not provide that MT data to the user. And if UE 102 does not access SV3 first, the data from SV1 and SV2 will be delivered in the correct order (although SV3 data will be missed).

[0131] Since UE 102 may miss access to some SV 104s (e.g., if UE 102 is not powered on or cannot see these SV 104s), SFC 202 can support some redundancy in MT data delivery by including MT data already uploaded to some SV 104s that can be accessed earlier by UE 102 to other SV 104s that can be accessed later by UE 102, in order to avoid UE 102 not receiving the MT data. For the previous example, where SVs become accessible to the UE in the order SV3, SV1, SV4, SV2, if the UE misses access to SV1 (and SV3), the MT data uploaded to SV1 can also be uploaded to SV2, and if the UE misses access to SV1 and SV3, the MT data uploaded to SV1, SV2, and SV3 can also be uploaded to SV4.

[0132] As just described, supporting sequential delivery of MO and MT data may introduce some additional latency during delivery, which may not be preferred in some situations. Therefore, UE 102 can be given the option to minimize latency by performing MO and MT data delivery out of order, or to perform MO and MT data delivery sequentially with some additional latency. This option can be part of UE 102's SVO subscription and pre-configured in SFC 202, or it can be indicated by UE 102 when registering with SV 104 and then passed to SFC 202. This option can apply to both MO and MT data, or the delivery of MO and MT data can differ.

[0133] Some SV 104s can support UE 102 access in both real-time and S&F modes. The transition between real-time and S&F modes can then occur as follows: When SV 104 loses all feeder links, it can switch from providing real-time access to UE 102 to providing S&F access to that UE. All UE 102s previously registered for real-time access can then remain registered to their current serving PLMN and can be switched to another SV 104 with feeder links, or enter a coverage gap where real-time access is impossible. SV 104 can then stop indicating support for PLMNs in real-time mode and begin indicating support for the same or other PLMNs that are permitted and capable of providing S&F mode coverage at the current SV location. SV 104 may also include indications for S&F mode in SIB1. UE 102s not subscribed to S&F mode can then remain in real-time mode and may not access SV 104. However, another UE 102 subscribing to S&F mode can choose to remain in real-time mode (and not access SV 104) or switch to S&F mode and access SV 104 in S&F mode. When switching to S&F mode, UE 102 can deregister from real-time mode locally and then perform a new initial registration with SV in S&F mode.

[0134] On the terrestrial PLMN 108 side, UE 102 may have previously registered for real-time mode access from SV 104 in the terrestrial PLMN 108. If SV 104, accessed by one of these UEs 102, switches to S&F mode and UE 102 remains in real-time mode (and therefore in a coverage gap), the terrestrial PLMN 108 can treat UE 102 as outside coverage and in an idle state. However, if UE 102 registers for S&F mode with SV 104, the new registration may affect the previous real-time mode registration in the terrestrial PLMN 108. Utilizing the interaction between SFC 202 and the terrestrial PLMN 108 according to option (c) described previously, SV 104 can indicate to SFC 202 and the terrestrial PLMN 108 (if the PLMN is the same for both real-time and S&F modes) that the previous real-time mode registration is no longer valid, and can provide UE 102 with new registration information for S&F mode.

[0135] Utilizing the interaction between SFC 202 and the terrestrial PLMN 108 according to option (a) or (b) as previously described, when UE agent 340 is first created for UE 102 in SFC 202, UE agent 340 typically performs the initial registration of UE 102 to the serving terrestrial PLMN 108 (e.g., as previously described and referred to later). Figure 8 (As shown). Then, the initial registration continues, and when the UDM in the HPLMN of UE 102 is notified, the UDM can implicitly deregister UE 102's previous real-time access. To avoid potential errors, initial registration of UE 102 for S&F mode can be performed (e.g., as shown). Figure 8 The diagram includes a new instruction that indicates initial registration is for S&F mode, where the instruction is forwarded to the UDM. When the UDM receives this instruction, it can perform implicit deregistration of UE 102 for real-time mode.

[0136] It may also be necessary to support the transition of SV 104 and UE 102 from S&F mode to real-time mode. The transition from S&F mode back to real-time mode can be the reverse of the transition to S&F mode. Therefore, when SV 104 regains the feeder link, it can transition from providing S&F access to UE 102 to providing real-time access to that UE. Before making this transition, SV 104 can indicate to UE 102, which is accessing SV 104 in S&F mode, that the current SV 104 radio cell will become unavailable—for example, some time in advance to allow UE 102 to complete any MO and MT transactions in S&F mode. SV 104 can then deregister all registered UE 102's S&F mode before exiting S&F mode. When the SV transitions to real-time mode, any S&F indications in SIB1 can be removed. UE 102 using S&F mode can then remain in S&F mode and access other SVs providing S&F mode or switch to real-time mode. When switching to real-time mode, UE 102 can perform a new initial NAS registration (e.g., with real-time indication) to SV 104, which can allow the UDM in UE 102's HPLMN to implicitly deregister the UE's S&F mode.

[0137] It should be noted that some UEs 102 may be located in geographical locations where visible SV 104 does not have access to the feeder link. These UEs 102 will therefore not see the transition between real-time mode and S&F mode, as visible SV 104 will remain continuously in S&F mode. The same applies to UEs 102 located in geographical locations where visible SV 104 has continuous access to the feeder link. These UEs 102 will similarly not see the transition between real-time mode and S&F mode, as visible SV 104 will remain continuously in real-time mode. Only UEs 102 located in locations where SV 104 only has access to the feeder link will see the transition between real-time mode and S&F mode.

[0138] It should also be noted that although SV 104 may support both real-time mode and S&F mode simultaneously (when the feeder link is available), this could complicate the implementation of SV 104 and reduce the performance of real-time mode if SV 104 first checks all UL transmissions, removes any signaling and messages associated with S&F mode, and then transparently forwards the remaining signaling using the feeder link.

[0139] In some cases, dual registration of UE 102 for both S&F and real-time modes can be supported. UE 102 in areas of SV 104 with feeder links for only a portion of the total accessibility time may benefit from being able to use both S&F and real-time modes without having to deregister from real-time mode while using S&F mode or vice versa. This could result in UE 102 dual registration in the same terrestrial PLMN 108 service, and in some cases, dual registration in the same AMF 414, resulting in two sets of PDU sessions and IMS registrations. This may involve some new implications, but could include aspects similar to simultaneous dual NAS registration on different radio access technologies (RATs) such as 3GPP NR and non-3GPP or 3GPP NR and 3GPP LTE.

[0140] SV 104 can also support local communication between UEs 102 in S&F mode. This allows UEs 102 that can simultaneously access the same SV 104 in S&F mode to communicate directly through SV 104 without needing to communicate via the serving terrestrial PLMN 108 and SFC 202. Real-time communication can be supported by first verifying whether the destination address of an MO transaction initiated by a UE 102 in S&F mode corresponds to another UE 102 currently registered in SV 104. If so, SV 104 (e.g., NG-RAN305 and 5GC 310) acting as the serving PLMN, serving HPLMN, or serving EHPLMN of both UEs 102 can support real-time communication.

[0141] It should be noted that the terms "MO data" and "MO service data" can generally be used here to refer to any type of mobile station-initiated data transmitted by UE 102 in S&F mode to SV 104 for later delivery to remote endpoint 116. Similarly, the terms "MT data" and "MT service data" can generally be used to refer to any type of mobile station-terminated data transmitted by SV 104 in S&F mode to UE 102, where the MT data was initially transmitted by remote endpoint 116. Types of MO data and MT data can include SMS, SIP media (e.g., voice, text, or video), email, Internet (e.g., HTTP) queries and responses, and general MO data and MT data such as UDP / IP, TCP / IP, or IP packet or non-IP data.

[0142] Next about Figure 7 , Figure 8 and Figure 9The technology used to support store-and-forward mode by UE 102, SV104, endpoint agent 240, SFC 202, and UE agent 340 is described and detailed as previously described. Note that... Figures 7 to 9 Various aspects and examples of technologies used to support store-and-forward modes are shown. However, many other examples of these technologies may exist, with some details and aspects differing.

[0143] Figure 7 Example signaling flow 700 is shown, which illustrates in more detail how UE 102 can register initial access with SV 104 and enable the creation of endpoint agent 240 in store-and-forward mode. Signaling flow 700 is executed by UE 102 and SV 104, where SV 104 contains, as for Figure 2 and Figure 3 The NG-RAN 205, 5GC 210, and endpoint agent 240 are described. Figure 7 It is assumed that UE 102 can have an SVO subscription to access SV 104 in store-and-forward mode, and therefore SV 104 can be pre-configured with the identity and security credentials of UE 102 in 5GC 210 (e.g., in UDM 222).

[0144] exist Figure 7 In Phase 1, SV 104 becomes visible at the location of UE 102 and begins to provide radio coverage at that location. SIBs can be broadcast over the coverage area of ​​SV 104, where SIB1 can indicate that SV 104 is operating in store-and-forward mode and can indicate the PLMN supported by SV 104, such as terrestrial PLMN 108.

[0145] At Phase 2, UE 102 detects radio coverage from SV 104 and decides to select SV 104 and access SV 104 using one of the PLMNs indicated by SV 104 in SIB1 at Phase 1. For example, UE 102 may decide to access SV 104 based on an indication that SV 104 is operating in store-and-forward mode, for example, if UE 102 supports store-and-forward mode.

[0146] exist Figure 7 In this scenario, SV 104 may indicate a ground-based PLMN 108 at phase 1, and UE 102 may select the ground-based PLMN 108. Alternatively, SV 104 may indicate a PLMN corresponding to an SVO at phase 1, in which case UE 102 may select the PLMN based on its knowledge of UE 102's subscription to the SVO.

[0147] At Phase 3, UE 102 registers with SV 104 by sending a NAS registration request to SV 104, and the NAS registration request includes UE 102's SUPI or SUCI. The SUCI can be UE 102's SUPI, which is encrypted using a public key provided by one of the SIBs broadcast by SV 104 at Phase 1, or it can be pre-configured in UE 102 because UE 102 subscribes to SV 104's SVO.

[0148] At Phase 4, SV 104 (e.g., AMF 214 and / or UDM 222) authenticates UE 102 based on the SUPI or SUCI provided at Phase 3. Authentication can be an exact copy of the authentication of UE 102 registered in the terrestrial HPLMN, and existing standard NAS procedures can be used for this. In this case, UE 102's identity and its security credentials, already pre-configured in SV 104, can be used to perform authentication. Authentication can be performed by SV 104 as if SV 104 (specifically 5GC 310) were the home PLMN of UE 102. From UE 102's perspective, authentication can be performed exactly as if UE 102 were accessing the terrestrial HPLMN of UE 102.

[0149] Assuming authentication at stage 4 is successful, 5GC 210 (e.g., AMF 214) returns NAS registration acceptance to UE 102 at stage 5 to complete UE 102's registration in SV 104.

[0150] At stage 6, 5GC 210 (e.g., AMF 214 or UDM 222) transmits a trigger event to the UE's endpoint agent 240 (if it has already been created), or to some other element in SV 104 (if it has not yet been created), to indicate that UE 102 has successfully registered in SV 104. If endpoint agent 240 has not yet been created for UE 102, SV 104 then creates endpoint agent 240 at stage 7 using the indication that UE 102 is currently registered in SV 104.

[0151] At phase 8, UE 102 may establish one or more PDU sessions to SV 104 (e.g., to UPF 218), which can then be used to transmit mobile station-initiated data. At phase 9, UE 102 may perform IMS registration with SV 104 (e.g., with IMS 230), which enables UE 102 to initiate mobile station-initiated SIP calls to endpoint agent 240 operating on behalf of remote endpoint 116.

[0152] At Phase 10, a user of UE 102 can interact with endpoint agent 240, for example, via application 701 (which may be referred to as the "App") on UE 102, to support out-of-band authentication of the user and agree to have certain services provided to UE 102 by SV 104. For example, in some scenarios, if SV 104 is not pre-configured with the identity and security credentials of UE 102, SV 104 may be unable to authenticate UE 102 at Phase 4. In this case, SV 104 may decide to abandon the authentication of UE 102 and allow UE 102 to successfully register at Phases 3 and 5 without authentication. This would be similar to allowing a UE to access a Wi-Fi access point (AP) without initial login to or authentication by the Wi-Fi AP, where the Wi-Fi AP authenticates the UE or the user of the UE out of band and may receive some prepayment via credit card. In the case of UE 102 and SV 104, endpoint agent 240 may prompt UE 102 with some kind of identifier of the user (e.g., via application 701) and accept some type of prepayment from the user, such as credit card prepayment. It may also reach some agreement regarding the services to be provided by SV 104 to UE 102. If this occurs, the user or UE 102 (e.g., application 701) may still need to provide SV 104 with the UE identifier (e.g., SUPI or SUCI) and the security credentials of UE 102 later used by UE agent 340 in SFC 202 to authenticate UE 102's HPLMN. Figure 7 In this context, it is assumed that stage 10 may not occur, but this stage includes... Figure 7 This could be a possible extension of the access process from UE 102 to SV 104.

[0153] Figure 7 Phases 11 through 24 illustrate how UE 102 can initiate different types of mobile station-initiated data transmissions to remote endpoint 116, where the MO data being transmitted is intercepted and stored by endpoint agent 240 in SV 104. Here, endpoint agent 240 simulates the behavior of remote endpoint 116 from the perspective of UE 102 by returning a pre-configured response to the UE at the application level (e.g., as part of SIP media data or using HTTP) and / or by returning a response to the UE at the transport level (e.g., TCP or NAS level).

[0154] At stage 11, UE 102 can transmit MO SMS on NAS or IMS. For example, MO SMS transmission on NAS can reach SMSF / SMSC 226, and at stage 12, MO SMS is transmitted from that SMSF / SMSC to endpoint agent 240. Then, at stage 13, the SMS message is stored by endpoint agent 240.

[0155] At phase 14, UE 102 may establish one or more SIP sessions to remote endpoint 116. The SIP session establishment message transmitted at phase 14 is received by 5GC 210 (e.g., by IMS 230) and subsequently forwarded to endpoint agent 240, which emulates the behavior of remote endpoint 116 by accepting the SIP session establishment request and enabling the SIP session to be established at phases 14 and 15. After the SIP sessions to endpoint agent 240 are established at phases 14 and 15, a user plane connection can be established between UE 102 and endpoint agent 240 to enable the delivery of different types of SIP-supported media data (such as voice, text, or video) for the SIP session at phase 16. This media (or media data) will be transmitted by UE 102 at phase 16 and received and stored by endpoint agent 240 at phase 17. Endpoint agent 240 may return some pre-configured media responses to UE 102 at stage 18, such as confirming the reception and storage of media at stage 17, and advising the user of UE 102 when to deliver it to remote endpoint 116 and when a response from remote endpoint 116 can be received at UE 102. In some cases, endpoint agent 240 may send some pre-configured media messages to the user of UE 102 before media delivery occurs at stage 16, instructing the user of UE 102 that any media delivered in stage 16 will be stored by endpoint agent 240 and later delivered to remote endpoint 116. After all media has been delivered at stage 16, UE 102 may initiate the release of the SIP session at stage 19 by sending a SIP release message to SV 104 (e.g., to IMS 230), which in turn may instruct endpoint agent 240 to release the SIP session at stage 20.

[0156] In the case of internet access (e.g., which may include email access) or mobile station-initiated data transmission (e.g., using non-IP, IP, UDP / IP, or TCP / IP transmission), at stage 21, UE 102 may transmit internet queries (or email queries) (e.g., HTTP queries) to SV 104, and / or may transmit mobile station-initiated data (e.g., IP, UDP / IP, or TCP / IP packets) to SV 104. This data can be transmitted to UPF 218 using the PDU session established at stage 8, where UPF 218 forwards the data to endpoint agent 240 at stage 22. Endpoint agent 240 may then store data packets, such as HTTP, non-IP, IP, UDP / IP, and / or TCP / IP packets, at stage 23, and also store details of the PDU session and the protocols and parameters used to transmit the data. At phase 24, endpoint agent 240 may optionally return a response (e.g., an HTTP response) to UE 102 in the event of an internet query (or email query) to indicate to the user of UE 102 that the internet query (or email query) transmitted at phase 21 has been stored by endpoint agent 240 and will later be forwarded to remote internet endpoint 116. Endpoint agent 240 may also return a response to UE 102 at the transport level (e.g., TCP level) when needed to allow UE 102 to transmit MO data in the absence of transport protocol failures.

[0157] After UE 102 has initiated and completed all MO data transfers from phases 11 to 24, and when UE 102 is about to lose access to SV 104, SV 104 can deregister UE 102, or UE 102 can deregister from SV 104. For example, AMF 214 and / or UDM 222 can perform NAS deregistration of UE 102 at phase 25, or UE 102 may initiate NAS deregistration itself.

[0158] At stage 26, an indication that NAS deregistration has occurred is transmitted to endpoint agent 240, for example, by AMF 214 or UDM 222. The endpoint agent can then be deactivated (e.g., shut down) at stage 27, where all MO data transmitted from UE 102 and stored by endpoint agent 240 is saved by SV 104. Finally, at stage 28, it is assumed that SV 104 moves away from UE 102 and ceases providing coverage to UE 102.

[0159] Figure 8Example signaling flow 800 is shown, which illustrates in more detail how UE agent 340 in SFC 202 can register initial access with terrestrial-based service PLMN 108 on behalf of UE 102, pass MO data previously transmitted by UE 102 in S&F mode to remote endpoint 116, and receive back and store any MT data intended for use by UE 102 from remote endpoint 116. Signaling flow 800 is configured as follows... Figures 3 to 6 The described SFC 202, UE agent 340, terrestrial PLMN 108 including NG-RAN 305 and 5GC 310, and remote endpoint 116 are executed. Figure 8 The assumption, such as regarding Figures 3 to 7 As described: (i) has occurred with Figure 7 The process is the same as or similar to that in the process in which UE 102 transmits MO data to endpoint agent 240 in SV 104; (ii) SV 104 has obtained feeder link access to SFC 202, such as Figure 8 As shown; and (iii) all MO data transmitted by UE102, along with associated protocol and addressing information, has been transferred from SV 104 to SFC 202. Figure 7 As shown, UE 102 may have an SVO subscription to access SV 104 in store-and-forward mode, and therefore SFC 202 may have been pre-configured with UE 102's subscription information, including UE 102's identity and security credentials, which can be provided to UE agent 340.

[0160] exist Figure 8 In Phase 1, SFC 202 creates UE agent 340 and provides UE agent 340 with all MO data received from SV 104, along with associated protocol and addressing information. If UE agent 340 has already been created in SFC 202, SFC 202 will instead update UE agent 340 only with the new MO data received from SV 104 and associated protocol and addressing information.

[0161] At Phase 2, if UE Agent 340 has not yet registered UE 102 in terrestrial PLMN 108, UE Agent 340 registers UE 102 in terrestrial PLMN 108 by transmitting a NAS registration request to terrestrial PLMN 108, as previously described for options (a), (b), and (c). For option (a), the NAS registration request will be transmitted to NG-RAN 305 and forwarded to 5GC 310. For option (b), the NAS registration request will be transmitted directly to 5GC 310. For option (c), SFC 202 may already include 5GC 310 capabilities or may have some dedicated links to 5GC 310 for transmitting the NAS registration request. The NAS registration request may include UE 102's SUPI or SUCI. If terrestrial PLMN 108 is UE 102's HPLMN or EHPLMN, the NAS registration initiated at Phase 2 may be performed only to that terrestrial PLMN. Otherwise, the NAS registration at stage 2 could also involve Figure 8 HPLMN of UE 102, not shown in the figure.

[0162] At phase 3, authentication of UE agent 340 occurs by either the terrestrial PLMN 108 or the HPLMN of UE 102 (if different). If the terrestrial PLMN 108 acts as the HPLMN or EHPLMN of UE 102, authentication can use the identity and security credentials of UE 102 pre-configured in the terrestrial PLMN 108 (e.g., in UDM 422).

[0163] If authentication is successful, 5GC 310 (e.g., AMF 414) returns NAS registration acceptance to UE agent 340 at stage 4, which completes the registration of UE 102 in terrestrial PLMN 108.

[0164] At phase 5, UE agent 340 establishes any PDU session to 5GC 310, which corresponds to, for example: Figure 7 The PDU session established earlier by UE 102 to SV 104, as described in [the previous section]. Similarly, at phase 6, if UE 102 has already [established a PDU session earlier than SV 104], [the PDU session will be established earlier]. Figure 7 If IMS registration to SV 104 is performed as described above, then UE agent 340 performs IMS registration to 5GC 310 (e.g., to IMS 430) and to the HPLMN of UE 102 (if different from the terrestrial PLMN 108).

[0165] It should be noted that for options (a) and (b), the terrestrial PLMN 108, including 5GC 310, can treat UE agent 340 as UE 102 itself and access the terrestrial PLMN 108 via SV 104 in real-time mode, as previously stated for... Figures 3 to 7 As described. In this case, UE agent 340 can simulate the behavior of UE 102 from the perspective of ground PLMN 108 by performing NAS registration of UE 102 to ground PLMN 108 and optionally IMS registration of UE 102 (which can be applied to options (a) and (b)).

[0166] Figure 8 Phases 7 to 22 illustrate how UE agent 340 can transmit MO data previously received from SV 104 to remote endpoint 116. If UE 102 has already... Figure 7 Sending MO SMS to SV 104 as described above, then in Figure 8 At stage 7, UE agent 340 initiates the delivery of an SMS initiated by a mobile station on the NAS or IMS, corresponding to any content previously transmitted by UE 102 to SV 104. This MO SMS can be received by SMSF / SMSC 426 and subsequently forwarded to remote endpoint 116 at stage 8. If the HPLMN is not a terrestrial PLMN 108, the delivery can be made via the SMSC in UE 102's HPLMN (…). Figure 8 (Not shown in the diagram) If the remote endpoint 116 has any SMS replies, these SMS replies can be transmitted by the remote endpoint 116 at stage 9 and can be received by the SMSF / SMSC 426 and forwarded to the UE agent 340 at stage 10. The UE agent 340 will then store these mobile station termination (MT) SMS messages at stage 11.

[0167] If UE 102 has already been... Figure 7 If a SIP session is initiated to SV 104 as described above, then UE agent 340 can initiate a corresponding SIP session to remote endpoint 116 via 5GC 310 (e.g., IMS 430) at stages 12 and 13. Remote endpoint 116 can then accept the SIP session to be established after stage 13. After the SIP session is established, a user plane connection will be established between UE agent 340 and remote endpoint 116, for example, via UPF 418. Figure 7The SIP media (or SIP media data) previously transmitted by UE 102 can then be passed from UE agent 340 to remote endpoint 116 over these user plane connections, and may include voice, text, or video media. At phase 15, remote endpoint 116 can transmit a media response back to UE 102, which will be passed to UE agent 340 over the user plane connection. UE agent 340 may also optionally transmit a pre-configured media response or message to remote endpoint 116 at the application level at phase 16 and / or before phase 14, indicating, for example, that the media data transmitted at phase 14 is being forwarded on behalf of UE 102 and / or that the media response at phase 15 is being stored and will later be transmitted to UE 102. UE agent 340 also stores all media responses and SIP session details received at phase 15 for transmission. Once all media transmitted by UE 102 has been delivered to remote endpoint 116, and all media responses from remote endpoint 116 have been received and stored, UE agent 340 may request the release of the SIP session from 5GC 310 (e.g., IMS 430) at stage 18, whereby the release request is forwarded by 5GC 310 to remote endpoint 116 at stage 19. UE agent 340 and remote endpoint 116 can then release the SIP session.

[0168] In such Figure 7 In the case of an Internet query, email query, or MO data transmitted by UE 102 over a PDU session, UE agent 340 can forward the Internet query and email query (e.g., HTTP query) and / or MO data (e.g., non-IP, IP, UDP / IP, and / or TCP / IP packets) to 5GC310 (e.g., UPF 418) at stage 20 via the PDU session established at stage 5, to be delivered to remote endpoint 116. Remote endpoint 116 can then return an Internet query response (e.g., HTTP response, email) and / or MT data response to UE agent 340 at stage 21. At stage 22, UE agent 340 stores the Internet query response, email, and / or MT data response.

[0169] At stage 23, additional unsolicited MT service data may be transmitted from remote endpoint 116 to UE agent 340. This could include, for example, SMS, SIP media, Internet data, or MT data (e.g., non-IP, IP, UDP / IP, or TCP / IP packets) terminated by the mobile station. In this case, UE agent 340 may transmit lower protocol-level (e.g., transport protocol-level) responses (e.g., acknowledgments) that may be required. UE agent 340 also stores the MT service data along with associated protocol and addressing data at stage 24. It should be noted that UE agent 340 can simulate the behavior of UE 102 from the perspective of remote endpoint 116 by: (i) transmitting MO data at stages 7, 14, and 20, receiving MT data at stages 10, 15, and 21, and / or transmitting pre-configured messages to remote endpoint 116 at the application level at stage 16 and / or prior to stage 14; and / or (ii) transmitting responses to remote endpoint 116 at the transport layer at stage 23.

[0170] At phase 25, UE agent 340 or SFC 202 periodically delivers all MT service data, related protocols, and addressing data stored by UE agent 340 to available SV 104, which is expected to later provide coverage to UE 102. The delivery at phase 25 may be performed to more than one SV 104, as any particular SV 104 may sometimes be unaccessible or unaccessible by UE 102. Furthermore, SFC 202 and UE agent 340 may continue to store all MT data, related protocols, and addressing data previously stored at phase 22 until later, upon receiving confirmation from SV 104 that the MT data has been delivered to UE 102, as previously described. SFC 202 may employ additional techniques to ensure that MT data returned to UE 102 is returned to UE 102 in the correct order, and that MO data transmitted to remote endpoint 116 is transmitted in the correct order, as previously described.

[0171] Figure 9 An example signaling flow 900 is shown, which illustrates in more detail how SV 104 can return MT data from remote endpoint 116 to UE 102 in S&F mode, and how UE 102 can transmit more MO data to SV 104 in S&F mode. Signaling flow 900 can be executed by UE 102, application (App) 901 in UE 102, and SV 104, where SV 104 includes NG-RAN 205, 5GC 210, and endpoint agent 240. Figure 9 Assumptions: (i) UE 102 has previously registered with SV 104 and transmitted MO data to SV 104, such as Figure 7As described in the document; (ii) SV 104 has passed MO data to SFC 202 and UE agent 340, which in turn have passed MO data to remote endpoint 116, as described in the document. Figure 8 As described in [the document]; and (iii) remote endpoint 116 has been [as described in the document] Figure 8 The description states that MT data is returned to SFC 202 and UE agent 340, which have already passed the MT data to... Figure 9 The SV 104 shown is for later delivery to UE 102. It is also assumed that UE 102 can have an SVO subscription to access SV 104 in store-and-forward mode, and therefore... Figure 9 The SV 104 shown can be pre-configured with the identity and security credentials of UE 102 in 5GC 210 (e.g., in UDM 222).

[0172] exist Figure 9 In Phase 1, SV 104 becomes visible at the location of UE 102 and begins to provide radio coverage at that location. SIBs can be broadcast over the coverage area of ​​SV 104, where SIB1 can indicate the use of PLMNs supported by SV 104, such as terrestrial PLMN 108 and S&F mode.

[0173] At Phase 2, UE 102 detects radio coverage from SV 104 and decides to select SV 104 and access SV 104 using one of the PLMNs indicated by SV 104 in SIB1 at Phase 1. Figure 9 In this scenario, SV 104 may indicate a ground-based PLMN 108 at phase 1, and UE 102 may select the ground-based PLMN 108. Alternatively, SV 104 may indicate a PLMN corresponding to the SVO at phase 1, in which case UE 102 may select the PLMN based on its knowledge of the SVO subscription.

[0174] At Phase 3, UE 102 registers with SV 104 by sending a NAS registration request to SV 104, and the NAS registration request includes UE 102's SUPI or SUCI. The SUCI can be UE 102's SUPI, which is encrypted using a public key provided by one of the SIBs broadcast by SV 104 at Phase 1, or it can be pre-configured in UE 102 because UE 102 subscribes to SV 104's SVO.

[0175] At Phase 4, SV 104 (e.g., AMF 214 and / or UDM 222) certifies UE 102 based on the SUPI or SUCI provided at Phase 3. Certification can be performed as follows: Figure 7 The fourth stage is described in the text.

[0176] Assuming authentication at stage 4 is successful, 5GC 210 (e.g., AMF 214) returns NAS registration acceptance to UE 102 at stage 5 to complete UE 102's registration in SV 104.

[0177] At phase 6, 5GC 210 (e.g., AMF 214 or UDM 222) transmits a trigger event to the UE's endpoint agent 240 (if already created), or to some other element in SV 104 (if not yet created), to indicate that UE 102 has successfully registered in SV 104. If endpoint agent 240 has not yet been created for UE 102, SV 104 creates endpoint agent 240 at phase 7 using the indication that UE 102 is currently registered in SV 104. If endpoint agent 240 has already been created for UE 102, SV 104 activates endpoint agent 240 at phase 7 using the indication that UE 102 is currently registered in SV 104. In either case, endpoint agent 240 is given access to all MT data of UE 102 previously passed to SV 104 by SFC 202 and UE agent 340.

[0178] At phase 8, UE 102 may establish one or more PDU sessions to SV 104 (e.g., to UPF 218), which can then be used to transmit MO and MT data. At phase 9, UE 102 may perform IMS registration with SV 104 (e.g., to IMS 230), which enables UE 102 to initiate mobile station-initiated SIP calls to endpoint agent 240 operating on behalf of remote endpoint 116, and enables endpoint agent 240 to initiate mobile station-terminated SIP calls to UE 102 to deliver MT SIP media.

[0179] At stage 10, endpoint agent 240 may notify UE 102 (e.g., application 901) that MT data stored for UE 102 exists in SV 104 and should be delivered to UE 102. A user of UE 102 can interact with application 901 and determine which types of MT data UE 102 needs to receive and which types it does not need to receive. For example, if UE 102 previously received MT data from another SV 104, where the MT data is tagged or described in some way, the user can choose not to receive the same MT data if endpoint agent 240 indicates that some or all of that same MT data is stored in SV 104. Alternatively, if all the MT data stored in SV 104 appears to be new, the user can indicate to endpoint agent 240 that all MT data can be delivered to UE 102. In some respects, stage 10 may not be performed, but this stage helps avoid duplicate delivery of the same MT data to UE 102.

[0180] At stages 11 through 24, endpoint agent 240 acquires the stored MT data (e.g., as agreed with the user at stage 10) and passes it to UE 102.

[0181] At phase 11, and in the case of SMS messages, endpoint agent 240 retrieves the stored MT SMS messages, and at phases 12 and 13 delivers these messages to UE 102 using SMS on NAS or SMS on IMS, wherein the MT SMS messages may be delivered to UE 102 via 5GC 310 (e.g., via SMSF / SMSC 226).

[0182] At phase 14, endpoint agent 240 acquires any stored SIP media (or SIP media data), and at phases 15 and 16, establishes one or more mobile station-terminated IMS sessions with UE 102 via 5GC 210 (e.g., via IMS 230). UE 102 then accepts these IMS sessions normally, which are established as part of phases 15 and 16. Also as part of phases 15 and 16, a user plane connection is established between endpoint agent 240 and UE 102 to deliver SIP media. These user plane connections may override the PDU sessions established at phase 5. At phase 17, endpoint agent 240 delivers stored SIP media (e.g., voice, text, or video) to UE 102 via the user plane connection. At phase 18, UE 102 (e.g., a user of UE 102) may return optional media responses to endpoint agent 240 on the user plane connection for later return to remote endpoint 116. In this scenario, endpoint agent 240 stores the returned media response for later transmission to remote endpoint 116 by SFC202 and point agent 340, such as... Figure 8 As described. After all MT SIP media data has been delivered to UE 102 at stage 17 and after UE 102 has provided any media response at stage 18, endpoint agent 240 may initiate the release of the SIP session via 5GC 210 (e.g., IMS 230) at stages 19 and 20.

[0183] At stage 21, endpoint agent 240 can retrieve any stored Internet query responses, emails, and / or MT data stored in SV 104, and at stage 22, deliver any MT data (e.g., non-IP, IP, UDP / IP, or TCP / IP packets) to UE 102. In the case of Internet query responses and / or emails, UE 102 or its user may first need to trigger the receipt of the Internet query response and / or email, or even at stage 23, transmit the original Internet query and / or email query (e.g., an HTTP request) to endpoint agent 240. Endpoint agent 240 can then return any corresponding Internet query response and / or email, such as an HTTP reply, stored in SV 104 to UE 102 at stage 24.

[0184] UE 102 can also initiate a new mobile station-initiated data transfer to SV 104 at phase 25, such as Figure 7 As described in [the document]. Endpoint agent 240 will then store all the new MO data that has been passed.

[0185] After SV 104 has transferred all stored MT data to UE 102 and UE 102 has sent any new MO data to SV 104, and when UE 102 is about to lose access to SV 104, SV 104 can deregister UE 102, or UE 102 can deregister from SV 104. For example, SV 104 (e.g., AMF 214 and / or UDM 222) can perform NAS deregistration of UE 102 at phase 26, or UE 102 may initiate NAS deregistration itself.

[0186] At stage 27, an indication that NAS deregistration has occurred is transmitted to endpoint agent 240, for example, by AMF 214 or UDM 222. Endpoint agent 240 can then be deactivated (e.g., shut down) at stage 28, where all new MO data transmitted from UE 102 and stored by endpoint agent 240 is saved by SV 104. Finally, at stage 29, it is assumed that SV 104 moves away from UE 102 and ceases providing coverage to UE 102. SV 104 can then later have feeder links to SFC 202 and the terrestrial PLMN 108, and can forward any new MO data to remote endpoint 116 via SFC 202 and the terrestrial PLMN 108, for example, as... Figure 8 As described.

[0187] To improve the efficiency and reduce latency of SV 104 access in S&F mode for UE 102, an S&F application can be used in UE 102. The S&F application can be an application-level program or procedure within UE 102, similar to other applications in its interaction with the user of UE 102 and with other components within UE 102. The S&F application enables the user of UE 102 to initiate and transmit MO data (e.g., MO SMS, voice calls, MO data, email, and internet queries) internally and locally within UE 102. Here, the user can interact with the S&F application without interacting with endpoint agent 240 in SV 104, and can still initiate and transmit MO data as if interacting with endpoint agent 240. However, the MO data (e.g., MO media and service data) is instead intercepted by the S&F application and stored in UE 102. Later, when SV 104 with S&F mode access becomes available to UE 102, the S&F application can autonomously initiate UE 102's NAS registration with SV 104, establish a PDU session, perform IMS registration, and then transfer all MO media and service data to endpoint agent 240 in SV 104. This transfer can simulate a transfer from the user, as previously... Figure 7 As described in the text.

[0188] The S&F application can also support a faster and more efficient delivery mode, in which all MO media and service data is first packaged (also called “packed”) into a single dataset by the S&F application and then transmitted to endpoint agent 240 in SV 104, for example, to a pre-configured address (e.g., IP, UDP, or TCP address) assigned to or associated with SV application as part of or associated with endpoint agent 240 in SV 104. The SV application then stores the dataset without alteration or interpretation. When SV 104 later has feeder link access to SFC 202, the dataset is delivered (unaltered) to the SFC application associated with UE agent 340 in SFC 202. The SFC application in SFC 202 can then unpack (also called “unpack”) the dataset to separate the different MO transactions and transmit the MO media and service data to remote endpoint 116.

[0189] The same type of process can be used to return MT media and service data to UE 102, where the SFC application in SFC 202 can package different types of MT service and media data received from remote endpoint 116 into a single dataset, which can be passed to endpoint agent 240 in SV 104 and then transmitted to the S&F application in UE 102, where the dataset is unpacked into individual MT transactions and provided to the user.

[0190] Because the high bandwidth is available for data transfer between UE 102 and SV 104, the transfer can be very fast, allowing UE 102 to access only one SV 104 for short periods (e.g., less than 1 minute) and avoiding the use of ISL support. Users can then utilize S&F mode at any time (by interacting with the UE 102 S&F application, regardless of whether SV 104 is accessible by UE 102) and are no longer restricted to accessing only when SV 104 is accessible.

[0191] In a variant that simplifies support for SV 104 and SFC 202, S&F applications in UE 102 are also supported at remote endpoint 116, without SV or SFC application support. The dataset created by the S&F application in UE 102 is then transparently transmitted (as MO data) to SV 104 endpoint agent 240, then to SFC 202 UE agent 340, and finally to remote endpoint 116 without any interpretation or alteration along the way—treated as data-only by SV 104 and SFC 202. The dataset is then unpacked by the S&F application at remote endpoint 116 to separate the different MO transactions, and the original MO media and service data is provided to remote endpoint 116 (e.g., to the user of remote endpoint 116). While the dataset can contain various media (e.g., voice, video, text), SV 104 and SFC 202 only need to support the transmission of unstructured data (e.g., octet strings) using transport protocols such as IP, UDP / IP, or TCP / IP. The S&F application in remote endpoint 116 will similarly package any MT data to be returned to UE 102 into a single MT dataset containing different types of MT data (e.g., MT SMS, voice media, MT data, email, and internet replies), which will be transparently passed back to the S&F application in UE 102 via SFC 202 and SV104.

[0192] This delivery can also be used in real-time mode to reduce SV 104 access time and access costs when SV 104 availability is very short (e.g., with discontinuous SL coverage) or even when SV 104 and terrestrial PLMN 108 coverage are continuous.

[0193] Data sets can be transmitted end-to-end in an encrypted manner, and media (e.g., voice, text, video) can be compressed. The S&F application in the UE can also manage the transmission of different data sets to and from different remote endpoints 116.

[0194] If both UEs support S&F applications, local communication between two UEs 102 simultaneously accessing the same SV 104 can also be supported using S&F applications. In this case, the S&F application in the first UE 102 can transmit a dataset to the SV 104, which identifies the destination remote endpoint 116 used for this as the second UE 102 also registered in the SV 104, and forwards the dataset to a similar S&F application in the second UE 102. The second UE then unpacks the dataset into the original MO media and service data transmitted by the first UE 102 and alerts the user of the second UE. Responses from the second UE using the S&F application can also be returned to the first UE in the same manner. Using S&F applications to support local communication between the two UEs 102 allows communication to be exchanged between the two UEs 102, which may significantly exceed the accessibility time of the SV 104 for both UEs 102 when transmitted at normal speeds (e.g., normal voice speed, normal video speed, or normal text typing speed).

[0195] Next about Figure 10 and Figure 11 The description and details are as previously described, using the S&F application to improve store-and-forward mode communication between UE102 and remote endpoint 116.

[0196] Figure 10 Example signaling flow 1000 is shown, which illustrates in more detail how UE 102 can transmit MO data to remote endpoint 116 using an S&F application. Signaling flow 1000 is performed by UE 102 and S&F application 1001 within UE 102, user 1090 of UE 102, SV 104 containing NG-RAN 205, 5GC 210, endpoint agent 240, and SV application 1002, SFC 202 containing UE agent 340 and SFC application 1003, terrestrial PLMN 108, and remote endpoint 116. It should be noted that SV application 1002 may be part of endpoint agent 240 or SV 104, and / or SFC application 1003 may be part of UE agent 340 or SFC 202.

[0197] exist Figure 10In Phase 1 of the process, user 1090 of UE 102 provides mobile station-initiated data to S&F application 1001 in UE 102. For example, MO data may include MO SMS messages, SIP media data (e.g., voice, video, or text), internet queries, email queries, and / or general MO data (e.g., data transmitted using non-IP, IP, UDP / IP, or TCP / IP). Phase 1 can be performed at any time convenient for user 1090, and in particular, it can occur when UE 102 is not accessible to SV 104. Providing MO data at step 1 may appear to user 1090 similar to providing MO data to remote endpoint 116, or similar to... Figure 7 In S&F mode, MO data is provided to SV 104.

[0198] At Phase 2, S&F application 1001 packages the MO data received at Phase 1 into a single MO dataset. A single MO dataset may include bit strings or octet strings, and for other entities, may be represented as bit strings or octet strings. However, it may contain internal structuring (e.g., as defined by some data structure standard such as ASN.1 or XML) that preserves the individual types of MO data and their formatting as provided by user 1090 at Phase 1. For example, S&F application 1001 may package MO data into a single MO dataset by combining different types of MO data (e.g., MO SMS, MO SIP media data, Internet queries, email queries, MO IP, non-IP, UDP / IP, or TCP / IP data) into a single MO dataset, and by including control information within the MO dataset that identifies the different types of MO data and their location within the MO dataset. When the MO data is intended for more than one remote endpoint 116, the S&F application 1001 can create a single MO dataset containing MO data for all intended remote endpoints 116, wherein the packaged MO data may also include the address or identifier of each intended remote endpoint 116 for each type or per MO data entry. Alternatively, the S&F application 1001 can create a separate MO dataset for each intended remote endpoint 116, containing MO data only for that remote endpoint 116. In this case, the separate MO datasets will be delivered in the stages described below, instead of just a single MO dataset.

[0199] At stage 3, which may occur later, UE 102 becomes able to access SV 104 and access SV 104, for example, as Figure 7 The process described includes registering with SV 104 (by performing NAS registration), establishing a PDU session, and performing IMS registration.

[0200] At phase 4, SV 104 creates or activates endpoint agent 240 for UE 102, for example... Figure 7 As described in the text.

[0201] At phase 5, UE 102 transmits a trigger or notification to S&F application 1001, indicating that SV 104 has been accessed by UE 102, wherein UE 102 is capable of transmitting MO data to SV 104 in S&F mode. The trigger may also indicate that SV 104 or SFC 202 has the SV application capability to receive the MO dataset packaged by S&F application 1001 at phase 2, or S&F application 1001 may query SV 104 (e.g., endpoint agent 240) to determine whether SV 104 supports SV applications, or S&F application 1001 may configure information about SVOs that support packaged MO datasets (e.g., SVO MCC-MNC).

[0202] Based on the triggering at stage 5 and the determination of support for the packaged MO dataset at stage 5, S&F application 1001 transmits the packaged MO dataset to SV 104 at stage 6. At this stage, the packaged MO dataset is received by endpoint agent 240 and can be passed to SV application 1002, where it will be stored. The MO dataset may not be entirely transparent to SV 104, which may need to know that the MO dataset contains packaged MO data. However, SV 104 and SV application 1002 may not view the MO data or may not necessarily support the packaging and / or unpacking of MO data. Optionally, however, SV application 1002 can repackage the MO data in the MO dataset—for example, to reduce the dataset size, or if SFC application 1003 in SFC 202 supports a different MO data packaging method than S&F application 1001 in UE 102. For example, SV application 1002 can repackage the MO data by unpacking the MO dataset into MO data and then packaging the MO data into a new MO dataset using a different (e.g., more efficient) packaging technique. On the other hand, the packaged MO dataset can be completely transparent to SV 104, and SV Application 1002 is not supported in SV 104. Instead, the packaged MO dataset can be received and stored by the endpoint agent at stage 6 and treated as unstructured MO data (e.g., bit strings or octet strings).

[0203] At a slightly later point in phase 7, after SV 104 has moved away from the location of UE 102, SV 104 obtains the feeder link and is able to access UE 102's SFC 202 and UE agent 340, as follows. Figure 8As described in [the document]. At stage 8, SV104, endpoint agent 240, or SV application 1002 passes the packaged MO dataset to UE agent 340, which then passes the MO dataset to SFC application 1003. SV104 or SV application 1002 may also provide an indication that the MO dataset contains packaged MO data (if this is known).

[0204] At stage 9, SFC application 1003 unpacks (also called "unpacking" or "unpacking") the MO dataset received in stage 8 back into the original MO data type provided by user 1090 at stage 1. For example, SFC application 1003 can unpack the MO dataset into MO data by identifying different types of MO data in the MO dataset (e.g., MO SMS, MO SIP media data, Internet query, email query, MO IP, non-IP, UDP / IP, or TCP / IP data) and their location within the MO dataset and separating the different types of MO data. If no indication is received at stage 8 that the MO dataset contains packaged MO data (e.g., if SV 104 or endpoint agent 240 does not know that the MO data is a packaged MO dataset), SFC application 1003 can first determine that the MO data received at stage 8 is a packaged MO dataset, for example, by examining the contents of the MO data and verifying that it has the structure of a packaged MO dataset, or by using configuration data for UE 102 stored in SFC 202 that instructs UE 102 to transmit a packaged MO dataset. After this determination, SFC application 1003 can unpack the packaged MO dataset.

[0205] Then, SFC application 1003 or UE agent 340 passes each of the original MO data types to the intended remote endpoint 116 at stage 10, and may as follows: Figure 8 As described.

[0206] At phase 11, remote endpoint 116 can transmit various MT data types (e.g., MT SMS messages, SIP media data, Internet query responses, emails, or plain MT data in non-IP, IP, UDP / IP, or TCP / IP data formats) in their raw format to UE agent 340, which can then pass these to SFC application 1003. At phase 12, SFC application 1003 then packages the received MT data types into a single MT dataset, similar to the MO dataset created by the S&F application in UE 102 at phase 2, and stores the MT dataset.

[0207] At stage 13 (which may occur at a later time), UE agent 340 is able to access SV 104 (which may be different from SV 104 in stages 3 through 8), which will later provide coverage of the last known location of UE 102, and then create or activate endpoint agent 240 for UE 102 in SV 104. At stage 14, SFC application 1003 or UE agent 340 then passes the packaged MT dataset to endpoint agent 240 in SV 104.

[0208] At a later time, SV 104 moves away from SFC 202 and provides coverage to UE 102, where UE 102 accesses SV 104 at phase 15 (e.g., registers with SV 104), for example as... Figure 7 As described in [the document]. Following this and at stage 16, SV 104 (e.g., 5GC 310) transmits a trigger to endpoint agent 240, which can forward it to SV application 1002, indicating that SV 104 is now able to access UE 102. Based on the trigger at stage 16, SV application 1002 transmits the packaged MT dataset to UE 102 at stage 17, which then provides the MT dataset to S&F application 1001. At stage 18, S&F application 1001 unpacks the MT dataset received at stage 17 into the original MT data type transmitted by remote endpoint 116 at stage 11. S&F application 1001 then provides the original MT data type to user 1090 at this time or at a later time convenient for user 1090 (e.g., when UE 102 cannot access SV 104).

[0209] At stage 20, stages 1, 2, and 6 through 10 may be repeated to transfer more packaged MO data from UE 102 to remote endpoint 116 using SV 104, which is used in stages 13 through 17. Alternatively, at stage 20, stages 1 through 10 may be repeated to transfer more packaged MO data from UE 102 to remote endpoint 116 using SV 104, which is different from the SV 104 used in stages 13 through 17.

[0210] Figure 11Example signaling flow 1100 is shown, which illustrates in more detail how UE 102 can use an S&F application to transmit MO data to a remote endpoint 116. The MO data is packaged into a single MO dataset by the S&F application in UE 102 and transparently transmitted to a similar S&F application in remote endpoint 116 via SV 104 and SFC 202. Signaling flow 1100 is executed by UE 102 and its S&F application 1101, user 1090 of UE 102, SV 104 containing NG-RAN 205, 5GC 210, and endpoint agent 240, SFC 202 containing UE agent 340, terrestrial PLMN 108, and remote endpoint 116 containing S&F application 1102.

[0211] exist Figure 11 At stage 1, user 1090 of UE 102 provides data initiated by a mobile station for a single remote endpoint 116 to S&F application 1101 in UE 102. For example, MO data may include MO SMS messages, SIP media data (e.g., voice, video, or text), internet queries, email queries, and / or general MO data (e.g., data transmitted using non-IP, IP, UDP / IP, or TCP / IP). Stage 1 can be performed at any time convenient for user 1090, and in particular, it can occur when UE 102 is not accessible to SV 104. Providing MO data at step 1 may appear to user 1090 as similar to providing MO data to remote endpoint 116, or similar to... Figure 7 In S&F mode, MO data is provided to SV 104. User 1090 can also indicate to S&F application 1101 at stage 1 that the remote endpoint 116 transmitting MO data at stage 1 has S&F application capability. Alternatively, S&F application 1101 can be configured with an indication of this capability.

[0212] At Phase 2, based on the knowledge that the remote endpoint 116, which transmitted the MO data at Phase 1, has S&F application capabilities, the S&F application 1101 packages the MO data received at Phase 1 into a single MO dataset. A single MO dataset may include a bit string or an octet, and for other entities, may be represented as a bit string or an octet. However, it may contain internal structuring (e.g., as defined by some data structure standard such as ASN.1 or XML) that preserves the individual types of MO data and their formatting as provided by user 1090 at Phase 1. For example, the S&F application 1101 can package MO data into a single MO dataset by combining different types of MO data (e.g., MO SMS, MO SIP media data, Internet queries, email queries, MO IP, non-IP, UDP / IP, or TCP / IP data) into a single MO dataset, and including control information identifying the different types of MO data and their location within the MO dataset.

[0213] At stage 3, which may occur later, UE 102 becomes able to access SV 104 and access SV 104, for example, as Figure 7 The process described includes registering with SV 104 (by performing NAS registration), establishing a PDU session, and performing IMS registration.

[0214] At phase 4, SV 104 creates or activates endpoint agent 240 for UE 102, for example... Figure 7 As described in the text.

[0215] At stage 5, UE 102 transmits a trigger or notification to S&F application 1101, which indicates that SV 104 has been accessed by UE 102, wherein UE 102 is able to transmit MO data to SV 104 in S&F mode.

[0216] Based on the trigger at stage 5, S&F application 1101 transmits the packaged MO dataset as a single unstructured data piece (e.g., an octet or bit string) to SV 104 at stage 6, where it is received and stored by endpoint agent 240. The MO dataset can be transparent to SV 104 and endpoint agent 240, which may not know that the MO dataset contains packaged MO data and may instead treat the MO dataset as a single unstructured data piece (e.g., an octet or bit string).

[0217] At a slightly later point in phase 7, after SV 104 has moved away from the location of UE 102, SV 104 obtains the feeder link and is able to access UE 102's SFC 202 and UE agent 340, as follows. Figure 8As described in [the document]. At stage 8, SV104 or SV application 1002 passes the packaged MO dataset to UE agent 340.

[0218] At stage 9, UE agent 340 transmits the packaged MO dataset to remote endpoint 116 without alteration or interpretation, and may, as follows: Figure 8 As described in [the document]. Then, remote endpoint 116 passes the packaged MO dataset to S&F application 1102 in remote endpoint 116.

[0219] At stage 10, the S&F application 1102 in remote endpoint 116 unpacks the MO dataset received at stage 9 into the original MO data type provided by user 1090 at stage 1, and makes these available to the user of remote endpoint 116. For example, S&F application 1102 can unpack the MO dataset into MO data by identifying different types (and locations) of MO data in the MO dataset (e.g., MO SMS, MO SIP media data, Internet queries, email queries, MO IP, non-IP, UDP / IP, or TCP / IP data) and separating the different types of MO data.

[0220] Remote endpoint 116 or its user can determine the various MT data types to be passed back to UE 102. For example, MT data may include MO SMS messages (which become MT SMS messages when passed to UE 102), SIP media data (e.g., voice, video, or text), internet query responses, email, and / or general MO data (e.g., data transmitted using non-IP, IP, UDP / IP, or TCP / IP methods, which become MT data when passed to UE 102). In this case, at phase 11, the MT data is first provided to S&F application 1102, which packages the MT data types into a single MT dataset, similar to the MO dataset created by the S&F application in UE 102 at phase 2. At phase 12, S&F application 1102 passes the single MT dataset to UE agent 340, which stores the MT dataset.

[0221] At stage 13 (which may occur at a later time), UE agent 340 is able to access SV 104 (which may be different from SV 104 in stages 3 through 8), which will later provide coverage of the last known location of UE 102, and then create or activate endpoint agent 240 for UE 102 in SV 104. At stage 14, UE agent 340 passes the packaged MT dataset to endpoint agent 240 in SV 104.

[0222] At a later time, SV 104 moves away from SFC 202 and provides coverage to UE 102, where UE 102 accesses SV 104 at phase 15 (e.g., registers with SV 104), for example as... Figure 7 As described in [the document]. Following this and at stage 16, SV 104 (e.g., 5GC 310) transmits a trigger to endpoint agent 240 indicating that SV 104 is now able to access UE 102. Based on the trigger at stage 16, endpoint agent 240 transmits the packaged MT dataset to UE 102 at stage 17 without alteration or interpretation, and the UE provides the MT dataset to S&F application 1101. At stage 18, S&F application 1101 unpacks the MT dataset received at stage 17 into the original MT data type provided at remote endpoint 116. S&F application 1101 then provides the original MT data type to user 1090 at this time or at a later time convenient for user 1090 (e.g., when UE 102 cannot access SV 104).

[0223] At stage 20, stages 1, 2, and 6 through 10 may be repeated to transfer more packaged MO data from UE 102 to remote endpoint 116 using SV 104, which is used in stages 13 through 17. Alternatively, at stage 20, stages 1 through 10 may be repeated to transfer more packaged MO data from UE 102 to remote endpoint 116 using SV 104, which is different from the SV 104 used in stages 13 through 17.

[0224] So far, it has been assumed that UE 102 can have an SVO subscription, and that the UE 102 identity and security credentials can be stored as a result in SV 104 and SFC 202. In some cases, this may mean that the UE 102 master security key K (which is typically stored only in the UE 102 Universal Subscriber Identity Module (USIM) and HPLMN UDM) needs to be provided to the SVO and stored in multiple SV 104 and SFC 202, which may pose a later security risk to the UE 102. To support UE 102 in SVO subscription with reduced security risk, a technique that enhances the existing security process can be used, referred to here as "SVO subscription with enhanced security," in which the UE 102 master key K is not exposed. Using this technique, the HPLMN operator can perform a process from master key K to an alternative master key K. Irreversible transformation, replacing the master key K The value is indicated by the key ID Kid. For example, K can be determined based on Kid and K by encrypting Kid using the UE's K. As an example, Kid may include a random component (e.g., pseudo-random or random bits or octets), a timestamp (e.g., date and / or time), and / or an SVO identifier, where, for example: K =Hash (encrypts Kid using K) (Equation 1) The encryption in Equation 1 can be, for example, Advanced Encryption Standard (AES) encryption.

[0225] HPLMN operators can (securely) provide Kid and K to SVO The value of SVO will be Kid and K The values ​​are stored in SV104 and SFC 202. Then, the authentication and encryption operations between UE 102 and SV 104 for S&F mode can follow the normal process, but the following differences exist.

[0226] (A)SV 104 provides the value of Kid to UE 102 at the start of any security procedure that requires the use of key K.

[0227] (B) The UE uses the value of Kid to determine the key K. .

[0228] Then, the security process is performed normally by both parties, but using K Replace K.

[0229] For the security procedures between UE agent 340 in SFC 202 and HPLMN of UE 102, UE agent 340 similarly provides the stored Kid value to HPLMN (e.g., UDM / AUSF), and HPLMN determines the K to be used in place of K. Values—this avoids storing Kid and K in HPLMN. Value required.

[0230] So far (for example, for) Figures 7 to 11 It is also assumed that UE 102 can have at least an SVO subscription to access SV104 in S&F mode using existing security procedures or an SVO subscription with the enhanced security technologies described above. However, this assumption is limiting, as it means that the UE 102 user may need to know in advance that SV 104 access in S&F mode will be required and arrange such a subscription before accessing SV 104 in S&F mode.

[0231] To avoid these limitations, a technique referred to herein as "SVO non-subscription" can be used to support UE 102's access to SV 104 without UE 102 subscribing to an SVO. Using this technique, UE 102's security and subscription information are not pre-stored in SV 104 and SFC 202. Instead, authentication and encryption between UE 102 and SV 104 can utilize a public-private key pair, where SV 104, UE 102, or both provide a public key and certificate (e.g., in the case of SV 104, provided in the authentication request) upon discovering that UE 102 is not subscribed to an SVO. The public key provided by SV 104 to UE 102 allows UE 102 to authenticate SV 104. Similarly, the public key provided by UE 102 to SV 104 allows SV 104 to authenticate UE 102's identity. SV 104 then provides UE 102 with all or some of the same limited S&F services as a subscribed UE 102. SV104 can restrict the initial service of UE 102 until UE 102 has been verified by UE 102 HPLMN (as described later).

[0232] UE 102 also provides an alternative master key K to SV 104 upon request. And the associated Kid (after encryption begins), as described above for SVO subscriptions with enhanced security. SV 104 will later provide the Kid to SFC 202. The SFC uses the values ​​of Kid and UE Agent 340 to enable UE Agent 340 to be authenticated by UE 102's HPLMN, similar to how UE 102's HPLMN authenticates UE Agent 340 with an SVO subscription featuring the enhanced security technologies described above. If UE Agent 340 is successfully authenticated by UE 102's HPLMN, then Kid... The value of Kid can be uploaded to other SVs 104 along with any MT data. Other SVs can use this MT data to authenticate UE 102 for any further access by UE 102 to other SVs 104. Simultaneously, UE 102 can wait for a device with the value of Kid. The uploaded values ​​of the satellite SV 104 and Kid become available for further access to SV 104 in S&F mode.

[0233] Figure 12 and Figure 13 Additional example aspects of SVO subscriptions with enhanced security technologies are illustrated and provided. Figure 12Example signaling flow 1200 is shown, illustrating in more detail how UE 102 can register with SV 104 and be authenticated by that SV for an SVO subscription with enhanced security technologies. Signaling flow 1200 is executed by UE 102, SV 104 containing NG-RAN 205, 5GC 210 containing AMF 214, AUSF 212, and UDM 222, and Operation and Maintenance (O&M) server 1210, which may be, for example, an SVO belonging to SV 104 or an HPLMN belonging to UE 102. Phases 3 to 20 of signaling flow 1200 can be... Figure 7 The signal flow 700 in stages 3 to 5 and Figure 9 The signal stream 900 is used in stages 3 to 5 to perform NAS registration authentication and encryption key determination, and to help enable secure transfer of MO data and MT data between UE 102 and at least one remote endpoint 116.

[0234] Suppose a user of UE 102 contacts the HPLMN operator of UE 102 and, possibly, the SVO of SV 104, and instructs UE 102 that it will need to receive store-and-forward mode services from SV 104, which belongs to the SVO. As a result, the HPLMN operator and / or SVO in Figure 12 In Phase 1, the O&M server 1210 configures the subscription, identification, and security information of UE 102 for SV 104 (e.g., UDM 222 in each SV 104). The identification information may include the UE 102's SUPI and, possibly, the General Public Subscription Identifier (GPSI). The security information may include the alternate master key K. The key identifier Kid will be determined by the HPLMN operator of UE 102, as previously described for SVO subscriptions with enhanced security technologies.

[0235] In Phase 2, UE 102 discovers and accesses SV 104 in S&F mode. In Phase 3, UE 102 registers with SV 104 by sending a NAS registration request to AMF 214 in SV 104. This NAS registration request may include UE 102's SUPI or SUCI. Phases 2 and 3 can be configured as follows: Figure 7 It occurs as described in the corresponding stage.

[0236] At phase 4, AMF 214 transmits the UE authentication request to AUSF 212 in SV 104, including the SUPI or SUCI received at phase 3.

[0237] At phase 5, AMF 212 transmits a UE authentication request to UDM 222 in SV 104, which requests authentication information from UE 102. Phases 4 and 5 can follow the existing procedures for UE authentication in HPLMN. Although AMF 214 may not know whether UE 102 is subscribed to SVO and SV 104, AMF 214 can transmit authentication requests to AMF and UDM at phases 4 and 5 in all cases.

[0238] At phase 6, UDM 222 can, for example, convert any SUCI received at phase 5 into SUPI of UE 102 based on known encryption of the SUCI using the public key known to SV 104.

[0239] At phase 7, UDM 222 uses the alternative master key K configured at phase 1. To generate authentication vectors (AVs).

[0240] At stage 8, UDM 222 returns a UE authentication acquisition response to AUSF 212, which may include the authentication vector, SUPI (if determined at stage 6), and the key identifier Kid configured at stage 1.

[0241] At stage 9, AUSF 212 returns a UE authentication response to AMF 214, which includes the key identifier Kid and authentication challenge data derived from AV by AUSF 212.

[0242] At stage 10, AMF 214 transmits a NAS authentication request to UE 102, including authentication challenge data and key identifier Kid.

[0243] At phase 11 and based on the key identifier Kid included at phase 10, UE 102 determines the alternative master key K according to the known master key K and key identifier Kid (e.g., using Equation 1) stored (i.e. configured) in the USIM of UE 102 and as previously described for SVO subscriptions with enhanced security technologies. .

[0244] At phase 12, UE 102 uses the alternative master key K calculated at phase 11. This is used to calculate the authentication response data in response to the authentication challenge received at phase 10. UE 102 also uses the alternative master key K. The authentication-related data is used to determine the encryption key used later for signaling with SV 104.

[0245] At stage 13, UE 102 returns a NAS authentication response to AMF 214, including the authentication response data calculated at stage 12. Then, at stage 14, AMF 214 returns a UE authentication request to AMF 212, including the authentication response data received from UE 102.

[0246] At stage 15, AUSF 212 verifies the authenticity of the authentication response data received at stage 14 based on the authentication vector received from UDM at stage 8. Assuming the authentication response data is successfully verified, AUSF 212 transmits the UE authentication response to AMF 214 at stage 16, including the SUPI (if the SUPI was received from UDM 222 at stage 8) and the encryption key to be used by AMF 214.

[0247] Then, at stage 17, AMF 214 returns a NAS registration acceptance indicating successful authentication to UE 102, completing UE 102's registration in SV 104. AUSF 212 also transmits a UE authentication result confirmation request to UDM 222 at stage 18, indicating successful authentication of UE 102, and UDM 222 then stores the successful UE authentication status at stage 19. At stage 20, UDM 222 also returns a UE authentication result confirmation response to AMF 212.

[0248] Aside from some minor differences added by SVO subscriptions with enhanced security technology, such as Figure 12 Phases 3 to 20 of the example signaling flow 1200 shown and described above can be similar to or the same as the phases performed by the UE and HPLMN when the UE registers in and is authenticated by the HPLMN. Differences from normal NAS registration and authentication in signaling flow 1200 may include: (i) adding and including the key identifier Kid at phases 8 to 10; and (ii) at phase 11, the UE 102 determining the alternative master key K based on the master key K and the key identifier Kid. (iii) UE 102 uses K at stage 12. Instead of K, the authentication response is calculated; and (iv) UE 102 uses an alternative master key K at phase 12. The encryption key is determined using authentication-related data.

[0249] In such a case Figure 12 Following the authentication of UE 102 as described, and in order to support the later authentication of UE agent 340, for example, as in Figure 8 In phase 3, SFC 202 or UE agent 340 can be configured with an alternative master key K. (For example, by O&M servers such as Figure 12 The O&M server 1210 is configured in the system and is authenticated by the HPLMN of UE 102. When the VPLMN of UE 102 corresponds to the terrestrial PLMN 108, it also uses the alternative master key K. Perform UE 102 authentication. Alternatively, SFC 202 or UE Agent 340 can be configured with an alternative master key K. Both and the key ID Kid (e.g., by the O&M server such as Figure 12 (Configuration of O&M server 1210 in the middle), where execution Figure 14B Phases 2 through 19 (as described later) are based on the alternative master key K by the HPLMN of UE 102. Use the key ID Kid to authenticate UE 102.

[0250] Figure 13 Example signaling flow 1300 is shown, illustrating in more detail how UE 102 can perform IMS registration with SV 104 and be able to be authenticated by SV 104 at the IMS level for an SVO subscription with enhanced security technology. The differences in authentication aspects, and particularly those added by the SVO subscription with enhanced security technology in signaling flow 1300, are similar to those in signaling flow 1200, and SV 104 can support both signaling flows 1200 and 1300 as part of an SVO subscription with enhanced security technology. Signaling flow 1300 is performed by UE 102, SV 104 containing NG-RAN 205, 5GC 210 containing P-CSCF 1310, I-CSCF 1320, S-CSCF 1330 and UDM 222, and Operation and Maintenance (O&M) server 1340, which can be, for example, an SVO belonging to SV 104 or an HPLMN belonging to UE 102. P-CSCF 1310, I-CSCF 1320, and S-CSCF 1330 can be part of the IMS 230 of SV 104 and can perform operations in conjunction with previously combined Figure 4 The P-CSCF, I-CSCF 1320, and S-CSCF described in IMS 430 have the same or similar functionality. The (O&M) server 1340 can be used with... Figure 12 The O&M server 1210 is the same. Phases 4 to 24 of signal flow 1300 can be... Figure 7 The signal flow 700 at stage 9 and Figure 9 The signal stream 900 is used at stage 9 to perform authentication and encryption key determination for IMS registration and to help achieve secure transfer of MO data and MT data (e.g., SIP media data) between UE 102 and at least one remote endpoint 116.

[0251] for Figure 12 Suppose that a user of UE 102 can contact the HPLMN operator of UE 102 and, possibly, the SVO of SV 104, and instruct UE 102 that it will need to receive store-and-forward mode services from SV 104, which belongs to the SVO. As a result, the HPLMN operator and / or SVO in Figure 13 In Phase 1, the O&M server 1340 configures the subscription, identification, and security information of UE 102 for SV 104 (e.g., UDM 222 in each SV 104). IMS-related identification information may include the UE 102's IMS Private Identifier (IMPI) and one or more IMS Public Identifiers (IMPU). Security information may include the alternate master key K. The key identifier Kid will be determined by the HPLMN operator of UE 102, as previously described for SVO subscriptions with enhanced security technologies.

[0252] In Phase 2, UE 102 discovers and accesses SV 104 in S&F mode. In Phase 3, UE 102 registers with SV 104 at the NAS level and establishes one or more PDU sessions. Phases 2 and 3 can be configured as follows: Figure 7 This occurs as described in the corresponding phase. Additionally, registration at the NAS level in phase 3 can use an SVO subscription with enhanced security technologies to authenticate UE102, for example, as for... Figure 12 As described.

[0253] At phase 4, UE 102 begins IMS registration with SV 104 by transmitting a SIP registration message to P-CSCF 1310 in SV 104 via NG-RAN 205 and UPF 218 in SV 104. The SIP registration message includes UE 102's IMPI and the IMPU to be registered.

[0254] At phase 5, P-CSCF 1310 forwards the SIP registration message with IMPI and IMPU to I-CSCF 1320.

[0255] At stage 6, I-CSCF 1320 sends a query to UDM 222 to find the identifier of S-CSCF 1330, which is then returned by UDM 222.

[0256] At phase 7, I-CSCF 1320 forwards the SIP registration message with IMPI and IMPU to S-CSCF 1330 as instructed at phase 6.

[0257] At stage 8, S-CSCF 1330 sends a Cx push message with IMPI and IMPU to UDM 222, indicating a registration attempt for IMPU.

[0258] At stage 9, S-CSCF 1330 transmits a request for the authentication vector (AV) to UDM 222, including IMPI.

[0259] At phase 10, UDM 222 uses the alternative master key K configured at phase 1. To calculate one or more AVs of UE 102.

[0260] At phase 11, UDM 222 returns a response to S-CSCF 1330, which includes IMPI, one or more AVs calculated at phase 10, and the key identifier Kid configured at phase 1.

[0261] At phase 12, S-CSCF 1330 transmits a SIP 401 authentication challenge to P-CSCF 1310 via I-CSCF 1320, and the SIP 401 message includes IMPI, UE 102's challenge data, IMS security key, and key identifier Kid.

[0262] At stage 13, P-CSCF 1310 stores the IMS security key received from S-CSCF 1330.

[0263] At phase 14, P-CSCF 1310 transmits a SIP 401 authentication challenge message to UE 102, which includes IMPI, challenge data, and key identifier Kid.

[0264] Based on the inclusion of the key identifier Kid at phase 14, at phase 15, UE 102 determines the alternative master key K based on the master key K stored (i.e., configured) in UE 102's USIM and the key identifier Kid received at phase 14. As previously described—for example, using equation (1).

[0265] At phase 16, UE 102 uses the alternative master key K. This is used to determine the response to the challenge data received at phase 14 (referred to as the challenge response). UE 102 also uses an alternative master key K. To determine the IMS security key that will be used later for signaling with SV 104 at the IMS level.

[0266] At phase 17, UE 102 transmits a second SIP registration message to P-CSCF 1310, which forwards the message to I-CSCF 1320. The second SIP registration message includes an IMPI and the challenge response determined at phase 16.

[0267] At stage 18, I-CSCF 1320 queries UDM 222 and receives the S-CSCF 1330 identifier from UDM.

[0268] At phase 19, I-CSCF 1320 forwards a second SIP registration message with IMPI and a challenge response to S-CSCF 1330.

[0269] At phase 20, the S-CSCF 1330 verifies the challenge response received at phase 19.

[0270] Assuming successful verification at stage 20, then at stage 21, the S-CSCF 1330 stores information indicating that UE 102's IMPU has been registered.

[0271] At phase 22, S-CSCF 1330 sends a Cx push message to UDM 222, indicating that UE 102's IMPU is now registered.

[0272] At stage 23, UDM 222 stores the information about the IMPU being registered.

[0273] At stage 24, S-CSCF 1330 returns a SIP 200 authentication OK message to UE 102 via I-CSCF 1320 and P-CSCF 1310. Then, UE 102 completes its IMS registration with SV 104.

[0274] Aside from some minor differences added by SVO subscriptions with enhanced security technology, such as Figure 13 Phases 4 through 24 of the signaling flow 1300 shown and described above can be similar to or the same as the phases performed by the UE and HPLMN when the UE performs IMS registration to the HPLMN using existing procedures—for example, for SV 104 access by UE 102 in real-time mode or for terrestrial access by UE 102 to the HPLMN. Differences from normal IMS registration in signaling flow 1300 may include: (i) adding and including a key identifier Kid at phases 11, 12, and 14; and (ii) at phase 15, the UE 102 determining an alternative master key K based on the master key K and the key identifier Kid. (iii) UE 102 uses K at stage 16. Instead of K, the challenge response is computed; and (iv) UE 102 uses an alternative master key K at phase 16. To determine the IMS security key.

[0275] In such a case Figure 13 Following the authentication process for IMS registration of UE 102, and in order to support subsequent authentication for IMS registration of UE agent 340, for example as... Figure 8 As part of Phase 6, SFC 202 or UE Agent 340 can be configured with an alternative master key K. (For example, by O&M servers such as Figure 13 The O&M server 1340 is configured in the system, and IMS registration authentication is performed by the HPLMN of UE102. When the VPLMN of UE102 corresponds to the terrestrial PLMN 108, it also uses the alternative master key K. Perform UE 102 authentication. Alternatively, SFC 202 or UE Agent 340 can be configured with an alternative master key K. and key ID Kid (e.g., by the O&M server such as Figure 13 The O&M server 1340 configuration in the system includes a change to normal operation whereby the authentication of IMS registration by the HPLMN of UE 102 to the HPLMN of UE 102 involves: (i) the UE agent 340 including the key ID Kid in the initial SIP registration message transmitted to the HPLMN of UE 102 via the terrestrial PLMN 108; and (ii) based on the inclusion of the key ID Kid in the initial SIP registration message, the HPLMN of UE 102 determines an alternative master key K according to the key ID Kid and the known master key K of UE 102. (For example, using equation (1)), and using K Instead of using K to perform IMS registration and authentication for UE Agent 340.

[0276] Figure 14A and Figure 14B Additional example aspects of the previously described SVO non-subscription technology are illustrated and provided. Figure 14A Example signal flow 1400 is shown, which illustrates in more detail how UE 102 can register with SV 104 and be authenticated by that SV for SVO non-subscription. Figure 14B continue Figure 14AFurthermore, example signal flow 1450 illustrates how UE agent 340 in SFC 202 can register with HPLMN of UE 102 after UE 102 has registered with SV 104 using signal flow 1400 and been authenticated by that SV. Signal flows 1400 and 1450 are performed by the following components: UE 102; SV 104 containing 5GC 210, which includes AMF 214, AUSF 212, and UDM 222, and endpoint agent 240; SFC 202 containing UE agent 340; terrestrial-based PLMN 108 containing AMF 414; and HPLMN 1408 of UE 102, which includes AUSF 1412 and UDM 1422. AUSF 1412 and UDM 1422 can perform the same actions as previously targeted... Figure 4 The functions described in AUSF 412 and UDM 422 are similar or identical.

[0277] Phases 2 to 21 of signal flow 1400 can be Figure 7 The signal flow 700 in stages 3 to 5 and Figure 9 Phases 3 to 5 of signal stream 900 are used to perform NAS registration authentication and encryption key determination, and to facilitate the secure transfer of MO and MT data between UE 102 and at least one remote endpoint 116. Phases 2 to 19 of signal stream 1450 can be used... Figure 8 The signal stream 800 is used in phases 2 to 4 to perform authentication and encryption key determination for NAS registration for UE agent 340, and to help enable secure transfer of MO data and MT data between UE 102 and at least one remote endpoint 116.

[0278] from Figure 14A Initially, it is assumed that UE 102 has discovered SV 104, which provides access in store-and-forward mode, and has determined to access SV 104. Figure 14A In stage 1, SV 104 (e.g., NG-RAN 205) Figure 14A (Not shown in the text) The public encryption key Kpsv can be broadcast in the system information block. Phase 1 is optional and, in some respects, may not occur.

[0279] At phase 2, UE 102 registers with SV104 by sending a NAS registration request to SV 104 and specifically to AMF 214. The NAS registration request includes UE 102's SUPI or SUCI and the alternate master key K. And the associated key ID Kid. K The values ​​of K and Kid can be determined by UE 102 using techniques previously described for SVO subscription modes with enhanced security, such as using Equation 1 to determine K. UE 102 vs K The determination of Kid can be based on UE 102 knowing that it has not subscribed to the SVO of SV104. UE 102 can use the public key Kpsv to determine the Kid transmitted at phase 2. The value of Kid is encrypted, and a SUCI is created based on the SUPI. UE 102 may also include the public key Kph belonging to the HPLMN of UE 102 (e.g., and configured on the USIM of UE 102).

[0280] In Phase 3, which is optional, AMF 214 in SV 104 can transmit a NAS request message to UE 102, including a request for more information from UE 102, and may also include the public encryption key Kpsv of SV 104. If the key Kpsv is included in Phase 3, Phase 1 does not need to occur, and vice versa.

[0281] At stage 4, and if stage 3 occurs, in response to the request at stage 3, UE 102 returns a NAS response to AMF 214 in SV 104, and includes SUCI if requested at stage 3 and not transmitted at stage 2, and also includes the substitute master key K if not included at stage 2. And the associated key ID Kid. If requested at phase 3 and / or Kph, UE 102 may also include UE 102's public encryption key Kpue at phase 4. For example, the public encryption key Kpue may have already been obtained by UE 102 to support V2X.

[0282] At phase 5, AMF 214 transmits the UE authentication request service operation to AMF 212, and this operation includes the SUPI or SUCI received at phase 2 or phase 4, as well as the substitute master key K. And the associated key ID Kid (if received at phase 2 or phase 4) and public key Kpue and / or Kph (if received at phase 2 or phase 4).

[0283] At stage 6, AUSF 212 transmits a UE authentication acquisition request service operation to UDM 222, including SUPI or SUCI, K And the Kid value and the Kpue and / or Kph encryption keys (if any of these are received at stage 5).

[0284] At stage 7, when the SUCI is encrypted using the Kpsv key, UDM 222 uses the private key corresponding to the public encryption key Kpsv to convert the SUCI received at stage 6 into the SUPI of UE 102.

[0285] At stage 8, if UE 102 transmits the alternative master key K at stage 2 or stage 4... And the associated key IDKid, and encrypted with the public encryption key Kpsv, then UDM 222 uses the private key pair K corresponding to the public encryption key Kpsv. Decrypt the value of Kid to obtain K And the unencrypted value of Kid.

[0286] At Phase 9, messages can be exchanged between UE 102, AUSF 212, and UDM 222 (e.g., via AMF 214) to authenticate UE 102 using the public encryption key Kpue (if this public encryption key was transmitted by UE 102 at Phase 4 or as part of Phase 9). Additionally, as part of Phase 9, UE 102 can authenticate SV 104 using the public key Kpsv received at Phase 1, Phase 4, or as part of Phase 9. The public keys Kpue and Kpsv can be provided together with certificates proving that these public keys belong to UE 102 (e.g., identified by SUPI) and SV 104 (e.g., identified by Mobile Country Code (MCC) and Mobile Network Code (MNC) respectively). In some respects, as part of phase 9 instead of phases 1, 2, and 4, UDM 222 or AUSF 212 may provide UE 102 with the SV public key Kpsv and / or receive UE 102's public key Kpue from UE 102. Similarly, UE 102 may provide an alternative master key K to AUSF 212 and UDM 222 at phase 9 instead of at phases 2 or 4. And the associated key ID Kid.

[0287] At phase 10, UDM 222 may transmit the UE authentication acquisition response service operation to AUSF 212, and if determined at phase 7, may include the UE 102's authentication vector (AV) and SUPI. The AV is generated by UDM 222 based on the alternative master key K received at phase 7 and decrypted at phase 8. To calculate.

[0288] At stage 11, AUSF 212 transmits the UE authentication authentication response service operation to AMF 214, and includes data of the authentication challenge determined by AUSF 212 based on the AV received at stage 10.

[0289] At phase 12, AMF 214 transmits a NAS authentication request to UE 102, including the authentication challenge data received at phase 11.

[0290] At phase 13, UE 102 uses the alternative master key K previously transmitted to AMF 214. To calculate the authentication response data for the authentication challenge data received at stage 12.

[0291] At phase 14, UE 102 returns a NAS authentication response message to AMF 214, including the authentication response data calculated at phase 13.

[0292] At phase 15, AMF 214 transmits the UE authentication authentication request service operation to AUSF 212, and includes authentication response data from phase 13.

[0293] At phase 16, AUSF 212 verifies the authentication response data based on the AV received from UDM 222 at phase 10.

[0294] In some respects, some or all of phases 11 through 16 may be omitted. This is because the authentication vector, authentication challenge data, and authentication response data in phases 11 through 16 are determined by UDM 222, AUSF 212, and UE 102 based on the substitute master key K, respectively. To calculate, the alternative master key K In the previous phase, the transition from UE 102 to UDM 222 was explicitly made. This means that authentication will be successful and therefore no new information is provided. However, phases 11 through 16 can also be used to reduce implementation changes to UE 102, AMF 214, and / or AMF 212 by preserving procedures that are already supported and intended for use.

[0295] At stage 17, AUSF 212 transmits a UE authentication response reply to AMF 214, which includes a SUPI (if received at stage 10) and an encryption key determined by AUSF 212 based on the AV received at stage 10.

[0296] At stage 18, AMF 214 sends a NAS registration acceptance message to UE 102 and indicates successful authentication, which completes UE 102's registration in SV 104.

[0297] At stage 19, AUSF 212 sends a UE authentication result confirmation request to UDM 222 indicating that UE 102 has been successfully authenticated.

[0298] At stage 20, UDM 222 stores an indication of successful UE 102 authentication.

[0299] At stage 21, UDM 222 transmits a UE authentication result confirmation response to AUSF 212.

[0300] At phase 22, UDM 222 transmits a NAS registration trigger indication to endpoint agent 240, indicating that UE 102 has successfully registered with SV 104. If endpoint agent 240 has not yet been created, its creation can also be part of this phase. The NAS registration trigger indication includes UE 102's SUPI and the previously received alternative master key K from UE 102. The associated key ID Kid and Kph (if received) are then stored by endpoint agent 240.

[0301] After phase 22, UE 102 can transmit mobile station-initiated data (e.g., SMS messages, MO data, IMS media data, internet queries, and / or email queries) to SV 104 and specifically to endpoint agent 240, whereby the mobile station-initiated data can be stored, for example, as... Figure 7 As described in [the document]. Because SV 104 does not yet know whether UE 102 provided legitimate identity (SUPI) and security information (K) at stages 2 through 9. (and Kid), so SV 104 can restrict the services provided to UE 102, and therefore restrict the type and amount of MO data that UE 102 is allowed to transmit. For example, in some cases, SV 104 may not allow UE 102 to transmit any MO data until Figure 14B After signal flow 1450 is completed.

[0302] Figure 14B continue Figure 14A The process that begins in the middle. Specifically, assuming that when the signal stream starts at 1450, Figure 14A Phases 1 through 22 have already occurred.

[0303] exist Figure 14B In phase 1, SV 104 obtains feeder link access to SFC 202 and creates UE agent 340 in SFC 202, for example, as... Figure 8 As described in [the text]. Figure 14BAs part of Phase 1, Endpoint Agent 240 transmits Endpoint Agent State Information to UE Agent 340, including UE 102's SUPI and Substitute Master Key K. and the associated key identifier Kid and any Kph obtained by endpoint agent 240, such as for Figure 14A As described.

[0304] At Phase 2, UE Agent 340 registers UE 102 in PLMN 108 by sending a NAS registration request message to AMF 414 in PLMN 108, including UE 102's SUPI or SUCI containing an encrypted value of SUPI and key identifier Kid. If SUCI was received at Phase 1, SUCI can be SUPI encrypted using public key Kph.

[0305] At optional Phase 3, AMF 414 may transmit a NAS request to UE Agent 340, and may include the public encryption key Kp of the terrestrial PLMN 108. If Phase 3 occurs, in response, at Phase 4, if SUPI or SUCI was not transmitted at Phase 2, UE Agent 340 transmits a NAS response containing SUCI, and / or if key identifier Kid was not included at Phase 2, transmits a NAS response containing key identifier Kid. SUCI and Kid can then be encrypted using the public encryption key Kp. In this case, AMF 214 decrypts SUCI and / or Kid.

[0306] At phase 5, AMF 414 transmits the UE Authentication Request Service Operation to AMF 1412 in the HPLMN of UE 102. AMF 214 includes the SUPI or SUCI received from UE Agent 340 and the key identifier Kid. AMF 414 may determine the HPLMN of UE 102 based on the SUPI (if received at phase 2) or based on the MCC-MNC of the HPLMN included by UE 102 at phase 2 or phase 4. In some respects, the HPLMN 1408 of UE 102 may be the same as the terrestrial-based PLMN 108, which may not affect the signaling described herein.

[0307] At phase 6, AUSF 1412 transmits a UE authentication acquisition request service operation to UDM 1422 in HPLMN 1408 of UE 102, and includes the SUPI or SUCI and key identifier Kid received at phase 6.

[0308] At stage 7, UDM 1422 uses the private key for HPLM1408 corresponding to the public key Kph for HPLM1408, and assumes that UE agent 340 uses the public key Kph for HPLM1408 to encrypt the SUPI into the SUCI, to determine the SUPI of UE 102 based on the SUCI (if received at stage 6). Furthermore, as part of stage 7 and based on the key identifier Kid received at stage 6, UDM 222 determines the alternative master key K based on the key identifier Kid and the master key K of UE 102 known to UDM 1422 (i.e., configured therein) (e.g., using Equation 1). UDM 1422 also uses an alternative master key K. The authentication vector (AV) of UE 102 is determined, and optionally a new key identifier K2id is determined, and a new alternative master key K2 is determined based on the new key ID K2id and using techniques for SVO subscription models with enhanced security (e.g., Equation 1). .

[0309] At phase 8, UDM 1422 transmits the UE authentication acquisition response service operation to AUSF 1412, including SUPI (if determined at phase 7), AV, and the new replacement master key K2. And the associated key ID K2id (if determined at stage 7).

[0310] At phase 9, AUSF 1412 transmits the UE authentication response to AMF 414 in the terrestrial PLMN 108, and includes authentication challenge data determined by AUSF 1412 based on the AV received at phase 8.

[0311] At phase 10, AMF 414 transmits a NAS authentication request to UE agent 340, including the authentication challenge data received at phase 9.

[0312] At phase 11, UE agent 340 uses the alternative master key K. To calculate the authentication response data in response to authentication challenge data.

[0313] At phase 12, UE agent 340 transmits a NAS authentication response message to AMF 414, including the authentication response data determined at phase 11.

[0314] At stage 13, AMF 414 transmits the UE authentication authentication request service operation to AUSF 1412, including the authentication response data received at stage 12.

[0315] At stage 14, AUSF 1412 uses the AV received from UDM 1422 to verify the authentication response data.

[0316] At phase 15, AUSF 1412 transmits the UE authentication response to AMF 414, including the SUPI (if received at phase 8), the encryption key, and the new replacement master key K2. And the associated new key ID K2id (if received from UDM 1422 at stage 8).

[0317] At phase 16, AMF 414 stores the encryption key from phase 15 and transmits NAS registration acceptance to UE agent 340, including an indication of successful authentication and the new replacement master key K2. And the associated new key ID K2id (if received at stage 15). This stage completes the registration of UE 102 by UE agent 340 in terrestrial PLMN 108.

[0318] At stage 17, AUSF 1412 sends a UE authentication result confirmation request to UDM 1422 indicating that UE agent 340 has successfully authenticated.

[0319] At stage 18, UDM 1422 stores an indication that UE agent 340 has been successfully authenticated. It should be noted that UDM 1422 may not be aware that it is UE agent 340 that has been authenticated, and may instead consider it as authentication of UE 102.

[0320] At stage 19, UDM 1422 transmits a UE authentication result confirmation response to AUSF 1412.

[0321] At stage 20 (which may occur sometime after SV 104 becomes capable of accessing via the feeder link to SFC 202), and when it is anticipated that SV 104 will later provide coverage to UE 102, UE agent 340 transmits UE agent state data to endpoint agent 240 in SV 104, including UE 102's SUPI and the alternate master key K received at stage 1. And the associated key ID Kid, or if received at stage 16, a new replacement master key K2. And the associated new key ID K2id. Endpoint agent 240 can then at stage 21 send SUPI and K and Kid or K2 And K2id is transmitted to UDM 222. In some respects, phases 20 and 21 can be combined, where UE agent 340 will send SUPI and K and Kid or K2 And K2id is sent to UDM 222 (or sent to SV 104 which sends it to UDM 222).

[0322] At a later time, UE 102 may begin accessing SV 104 in store-and-forward mode (which may differ from SV 104 for signaling flow 1400), for example, as for... Figure 7 and Figure 9 As described. In this scenario, UE 102 can perform NAS registration with SV104, and SV 104 can use the alternative master key K. Or a new alternative master key K2 To authenticate UE 102. NAS registration and authentication can be performed as follows: Figure 12 Phases 3 through 20 describe the SVO subscription model with enhanced security. Specifically, SV 104 can now provide UE 102 with either key ID Kid or a new key ID K2id (in... Figure 12 (in stages 8 to 10), and UE 102 can use key ID Kid or a new key ID K2id respectively according to the... Figure 12 In stage 11 of the process, the master key K configured in UE 102 is used to determine the alternative master key K. Or a new alternative master key K2 Alternate master key K Or a new alternative master key K2 Then UE 102 is used in Figure 12 The authentication response data is determined at stage 12. For any subsequent authentication of UE 102 by SV 104, both UE 102 and SV 104 (e.g., UDM 222) can use the alternative master key K. Or a new alternative master key K2 This does not require using the key ID Kid or the new key ID K2id separately to indicate this.

[0323] Other SV 104s can also be configured with K by UE agent 340. and Kid value or K2 The K2id value, and the authentication of these other SV 104 to UE 102 can be as described for phase 22. At this point, SV 104 and UE 102 can use an SVO subscription model with enhanced security to support UE 102's access to SV 104.

[0324] It should be noted that, for Figure 14A The described signal flow 1400 is divided into stages 2 to 21 and is targeted at Figure 14BThe described signal flow 1450, stages 2 to 19, can each be similar to when the UE is in the HPLMN ( Figure 14A ) or VPLMN ( Figure 14B When UE and HPLMN (in) register and are authenticated for normal terrestrial network access, they are both registered in the terrestrial network and the HPLMN (in) Figure 14A In the case of) or by UE, the interviewed PLMN (VPLMN) and HPLMN (in) Figure 14B In the case of (the situation where), the phase is executed. The differences from normal NAS registration and authentication in signal flow 1400 may include: (i) the key identifier Kid and the substitute master key K of phase 2 are determined by UE 102. (ii) At stage 2 or 4 and stages 5 to 6, UE 102 transmits key identifier Kid and substitute master key K to UDM 222. (iii) An optional additional authentication phase at phase 9 based on the public key Kpue and / or Kpsv; and (iv) Kpue and / or Kpsv by UDM 222 at phase 10 and by UE 102 at phase 13 respectively. Instead of using the master UE 102 key K to calculate authentication challenge data and authentication response data or to enable the calculation of authentication challenge data and authentication response data.

[0325] Differences from normal NAS registration and authentication in signal flow 1450 may include: (i) at phase 1, the endpoint agent 240 provides the key identifier Kid and the alternative master key K to the UE agent 340. (ii) At stage 2 or 4 and stages 5 to 6, the UE agent 340 transmits the key identifier Kid to the UDM 1422 in HPLMN 1408; (iii) at stage 7, the UDM 1422 determines the replacement master key K. (iv) K is used by UDM 222 at stage 7 and by UE agent 340 at stage 11 respectively. Instead of using the master UE 102 key K to calculate the authentication challenge data and authentication response data or enabling the calculation of the authentication challenge data and authentication response data; and (v) at stage 7, the new key identifier K2id and the new alternative master key K2 are optionally determined by UDM 1422. And it is provided to UE agent 340 by UDM 1422 at stages 8, 15 and 16.

[0326] The previously described SVO non-subscription technology can also be used for IMS registration—for example, in Figure 7 Stage 9 Figure 8 Phase 6 and Figure 9 Stage 9 in the middle. This usage can be similar to targeting Figure 14A and Figure 14B The use of UE authentication described for NAS registration, but the messages used for UE authentication for IMS registration (e.g., such as...) Figure 13 (As shown) Replace the UE authentication message used for NAS registration (e.g., as shown) Figure 14A and Figure 14B As shown in the figure, some changes were made to the network entities involved.

[0327] It should be noted that Figures 7 to 14B Assume that SV 104 provides 5G NR access to UE 102 in S&F mode, and terrestrial PLMN 108 provides 5G NR access to UE agent 340 in SFC 202 for interconnection with SFC 202 via options (a) and (b), and that the HPLMN of UE 102 supports 5G access. However, as previously described, either or both of SV 104 and terrestrial PLMN 108 (and the HPLMN of UE 102) can support different types of radio access, such as 4G LTE or future 6G standards. In this case, the implementation... Figures 7 to 14B The 5G entities (e.g., NG-RAN, 5GC, AMF, UPF, UDM, AUSF) can be replaced by corresponding entities for different types of radio access. For example, when the different types of radio access are 4G LTE, NG-RAN, 5GC, AMF, UPF, and UDM plus AUSF can be replaced by E-UTRAN, EPC, MME, SGW plus PGW, and HSS, respectively. Similarly, Figures 7 to 14B The phase in which messages (or multiple messages) for 5G NR are transmitted between a pair of components supporting 5G NR can be replaced by an equivalent phase in which messages (or multiple messages) for 5G NR are replaced by corresponding messages (or multiple corresponding messages) for 4G LTE transmitted between a pair of corresponding components supporting 4G LTE.

[0328] As an example, in Figure 7 In phases 3 and 5, UE 102 transmits a NAS registration request to 5GC 210 (e.g., AMF 214) at phase 3 and receives a NAS registration acceptance from 5GC 210 (e.g., AMF 214) at phase 5 to register UE 102 with 5GC 210. In the case of 4G LTE access to SV 104, UE 102 may alternatively transmit a NAS attach request to EPC (e.g., MME) at phase 3 and receive a NAS attach acceptance from EPC (e.g., MME) at phase 5 to register UE 102 with EPC (or attach it to EPC). When the terrestrial PLMN 108 supports 4G LTE access for UE agent 340 but does not support 5G NR access, for Figure 9 Phases 3 and 5 in the middle, for Figure 12 Stages 3 and 17 in the middle, for Figure 14A Phases 2 and 18 in the middle, for Figure 8 Phases 2 and 4 in the middle and Figure 14B The same changes may also occur in stages 2 and 16. As another example, in Figure 7 Phase 25 and Figure 9 In stage 26, UE 102 performs NAS deregistration to SV 104. When SV 204 supports UE 102's 4G LTE access, UE 102 can alternatively perform NAS decoupling from SV 104. As another example, when 4G LTE access is provided... Figure 7 Stage 8 Figure 8 Phase 5 Figure 9 Phase 8 and Figure 13 The PDU session establishment at Phase 3 can be replaced by the establishment of a Packet Data Network (PDN) connection. However, it should be noted that SIP signaling actions involving IMS entities (e.g., the P-CSCF, I-CSCF, or S-CSCF in IMS 230 or IMS 430, or the HPLMN of UE 102) can be the same for 5G NR and 4G LTE access, and possibly for future 6G access.

[0329] The following is a brief description of some additional enhancements that can support UE 102 accessing SV 104 in S&F mode, as previously described for... Figures 1 to 14B As described. To support Radio Emergency Alerts (WEA) to UE 102 in S&F mode, terrestrial PLMN 108 can receive emergency alerts from a terrestrial source (e.g., a government or local government agency) and transmit them, along with the time or duration and applicable location area, to SFC 202. SFC 202 can then utilize its feeder link to pass the emergency alerts to SV 104, allowing SV 104 to receive emergency alerts for applicable locations within its future coverage area. SV 104 can later broadcast emergency alerts to UE 102 at locations with coverage from SV 104 (e.g., in SIB messages) and at these locations, broadcast emergency alerts applicable to the current coverage area of ​​SV 104.

[0330] To support lawful interception (LI) for some UE 102s, SFC 202 and / or terrestrial PLMN 108 can be configured with the identifier (e.g., SUPI) of the UE 102 to which LI is applied. When MO and / or MT data of LI-enabled UE 102s are transferred between SV 104 and SFC 202 and / or between SFC 202 and terrestrial PLMN 108, LI-related information for the UE 102 and its MO and / or MT data can be provided to the LI authorizing authority by SFC 202 or by terrestrial PLMN 108. If existing LI capabilities in terrestrial PLMN 108 are reused, the LI-related impact may be minimal or zero.

[0331] To support service provision and to provide service only to UE 102, which is in the same country as terrestrial PLMN 108, SV 104 can obtain location-related information of UE 102 accessing SV 104 in S&F mode. This location-related information can be based on the coverage area of ​​SV 104 serving the radio cell of UE 102 and / or on location measurements obtained by SV 104 and possibly by UE 102 (e.g., angle of arrival, time of arrival, or round-trip time). SV 104 can then determine the location and country of UE 102 based on the location-related information, and if (i) UE 102 is not in the same country as terrestrial PLMN 108, SV 104 will later establish a feeder link with that terrestrial PLMN to support UE 102 at its current location, or (ii) if UE has already selected terrestrial PLMN 108 as its serving PLMN upon initial access to SV 104, service to UE 102 can be suppressed.

[0332] To support emergency (e.g., E911) calls from UE 102 accessing SV 104 in S&F mode, SV 104 can allow UE 102 to establish an emergency IMS call to endpoint agent 240, where endpoint agent 240 then provides a pre-configured voice announcement to UE 102 or its user indicating that an emergency call is being delivered in S&F mode. The user of UE 102 can then leave an emergency-related voice message using SIP voice media, which can be preferentially delivered to SFC 202 when SV 104 later has a feeder link to SFC 202. UE agent 340 in SFC 202 can then establish an emergency call preferentially to PSAP remote endpoint 116 and can forward the emergency voice message from UE 102 and other information about UE 102, such as the time of the emergency call from UE 102 and UE 102's last known location. Even when UE 102 is not subscribed to access SV 104 to obtain other services, SV 104 and SFC 202 can still support emergency calls.

[0333] Figure 15 This is a flowchart of an example method 1500 supporting wireless communication performed by user equipment (e.g., UE 102, device 2204). The following section discusses... Figure 22 Example components of the UE are provided. This method can improve UE coverage by enabling the UE to transmit and / or receive communications via the SV when the SV may have intermittent feeder link connections to a terrestrial network.

[0334] At box 1510, the UE uses a serving link to access a spacecraft (e.g., SV 104), where the SV does not have a feeder link to a terrestrial network (e.g., PLMN 108), and where the UE is not registered with the SV. For example, for Figure 7 Phases 2 to 9 and Figure 9 Phases 2 through 9 of the document illustrate example aspects of UE access to the SV. As an example, access may be performed, for instance, by the communication component 2298, transceiver 2222, and / or antenna 2280 of device 2204.

[0335] At box 1520, the UE registers with the SV. For example, Figure 7 Phases 3 to 5 and Figure 9 Phases 3 to 5 illustrate example aspects of the UE registering with the SV. As an example, registration can be performed, for instance, by the communication component 2298, transceiver 2222, and / or antenna 2280 of device 2204.

[0336] At box 1530, the UE transmits mobile station-initiated (MO) data intended for at least one remote endpoint (e.g., remote endpoint 116) to the SV, where the SV stores the MO data. Figure 7 An example is illustrated whereby the UE sends MO data to the SV at stages 11 to 23. As an example, the data may be transmitted or sent, for example, by the communication component 2298, transceiver 2222, and / or antenna 2280 of device 2204.

[0337] At box 1540, the UE is deregistered from the SV. Figure 7 An example of cancellation at stage 25 is shown, and Figure 9 An example of deregistration at stage 26 is illustrated. As an example, deregistration can be performed, for instance, by the communication component 2298, transceiver 2222, and / or antenna 2280 of device 2204.

[0338] At box 1550, the UE stops accessing the SV, which later has a feeder link to a terrestrial network, and which forwards MO data to at least one remote endpoint via the network. Figure 7 An example of stopping at stage 28 is shown, and Figure 8 and Figure 9 An example of stopping at stage 29 is illustrated. For example, the stop can be performed by the communication component 2298 of device 2204.

[0339] In some aspects, the service link supports radio access to SV using 4G LTE, 5G NR, or future 6G standards, where SV includes RAN and CN, for example, as for... Figure 2 As described. The serving link may support 5G NR, in which case registration to the SV may include performing NAS registration with the SV, and deregistration from the SV may include performing NAS deregistration with the SV. The serving link may optionally or additionally support 4G LTE, in which case registration to the SV may include performing NAS attachment with the SV, and deregistration from the SV may include performing NAS detachment from the SV. In some aspects, registration / deregistration and / or attachment / detachment may be performed by the communication component 2298 of device 2204.

[0340] In some aspects, the SV includes an endpoint proxy function (e.g., an endpoint proxy function (e.g., 240)) for at least one remote endpoint, wherein the endpoint proxy function can simulate the behavior of at least one remote endpoint from the perspective of the UE, and wherein the endpoint proxy function can receive and store MO data, for example, as for Figure 7 As described. Simulating the behavior of at least one remote endpoint from the UE's perspective may include the remote endpoint proxy function returning at least one of the following: a pre-configured response to the UE at the application level; a response to the UE at the transport level; or both, for example, as described for Figure 7 As described.

[0341] In some respects, MO data includes at least one of the following: MO Short Message Service (SMS) messages; media data of Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing, for example, as for... Figure 7 As described.

[0342] In some aspects, SV forwards MO data over a network to at least one remote endpoint by forwarding MO data to a terrestrial server (e.g., SFC 202), wherein the server forwards MO data over a network to at least one remote endpoint, for example, as for... Figure 8 As described. The server can access the network using option (a), option (b), or option (c), wherein: for option (a), the server attaches to the network as an NTN gateway, and the network includes a RAN and a CN for radio access type; for option (b), the server attaches to the network as a base station, and the network includes a CN for radio access type; and for option (c), the server includes the network or is part of the network, for example, as described for... Figures 3 to 5 and Figure 8 As described. The server may include a UE proxy function (e.g., UE proxy 340) for the UE, wherein the UE proxy function simulates the behavior of the UE from the perspective of at least one remote endpoint and the network, wherein the UE proxy function receives MO data from the SV, and wherein the UE proxy function forwards the MO data to at least one remote endpoint, for example, as for... Figure 8 As described. Simulating UE behavior from the perspective of at least one remote endpoint may include transmitting at least one of the following by the UE proxy function: a pre-configured message at the application level to at least one remote endpoint; a response at the transport level to at least one remote endpoint; or both, for example, as described for Figure 8 As described. Simulating UE behavior from the network's perspective may include actions performed by the UE proxy function: for option (a) or option (b) when the radio access type is 5G NR, the UE registers with the network's NAS; or for option (a) or option (b) when the radio access type is 4G LTE, the UE attaches to the network's NAS. Simulating UE behavior from the network's perspective may also include keeping the UE in a persistent connection state from the network's perspective using the UE proxy function.

[0343] In some respects, the SV can be a first SV, the feeder link for the first SV can be a first feeder link, and the serving link to the first SV can be a first serving link. The UE can later access the second SV (e.g., another SV 104) using a second serving link, wherein the second SV does not have a second feeder link to the terrestrial network, and wherein the UE is not registered to the second SV, for example, as for... Figure 9 As described. The UE can then: register with the second SV; receive mobile station termination (MT) data from the second SV, wherein the MT data is initiated by at least one remote endpoint and wherein the MT data is stored by the second SV; deregister from the second SV; and stop accessing the second SV, for example, as for Figure 9 As described. MT data may include at least one of the following: MT SMS messages; media data of the Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; email; or some combination of the foregoing, for example, as described for... Figure 9 As described. The second SV can receive MT data from a ground-based server (e.g., SFC 202), wherein the server receives MT data from at least one remote endpoint via a network, for example, as described for Figure 9 As described. The UE can transmit second MO data intended for at least one remote endpoint (e.g., remote endpoint 116) to a second SV, wherein the second SV stores the second MO data, wherein the second SV later has a feeder link to a terrestrial network, and wherein the second SV forwards the second MO data to at least one remote endpoint via the network, for example, as for... Figure 9 As described.

[0344] In some aspects, the UE can receive an indication broadcast by the SV that the SV is operating in store-and-forward mode. Then, at block 1510, the UE can access the SV using a serving link based on the indication broadcast by the SV that the SV is operating in store-and-forward mode. When the SV is operating in store-and-forward mode, the UE can have a subscription to access the SV, for example, as for... Figure 7 As described.

[0345] The method may also include any aspect performed by the UE, such as combining Figures 1 to 14B Described by any of them.

[0346] Figure 16 This is a flowchart of a method 1600 that supports wireless communication performed by a spacecraft (e.g., SV 104; network entity 2302). The following section discusses... Figure 23Example components for the SV are provided. This method can improve coverage provided to the UE by enabling the SV to receive and store communications when the SV does not have a feeder link connection to the terrestrial network, so that communications can be provided to the terrestrial network at a later time when the SV has a feeder link to the network.

[0347] At box 1610, the SV provides radio access to the UE (e.g., UE 102) via a serving link, wherein the SV does not have a feeder link to a terrestrial network (e.g., PLMN 108) and wherein the UE is not registered with the SV. Figure 7 and Figure 9 Examples of providing this type of access are given, for example, as for... Figure 7 Phases 1 to 9 and Figure 9 Phases 1 through 9 are described in the text. Access can be provided, for example, by... Figure 23 The network entity 2302 in the network uses the storage and forwarding components 2399, communication interface 2348, transceiver 2346 and / or antenna 2380 to perform this function.

[0348] At box 1620, SV registers UE. Figure 7 and Figure 9 Examples of registration are illustrated, such as those for... Figure 7 Phases 3 to 5 and Figure 9 Phases 3 through 5 are described in the text. Registration can, for example, be performed by... Figure 23 The network entity 2302 in the network uses the storage and forwarding components 2399, communication interface 2348, transceiver 2346 and / or antenna 2380 to perform this function.

[0349] At box 1630, the SV receives mobile station-initiated (MO) data from the UE, wherein the MO data is intended for use with at least one remote endpoint (e.g., remote endpoint 116). Figure 7 An example of receiving MO data from a UE is shown, for example, such as Figure 7 Stages 11 to 22 are described in the text. Reception can, for example, be provided by... Figure 23 The network entity 2302 in the network uses the storage and forwarding components 2399, communication interface 2348, transceiver 2346 and / or antenna 2380 to perform this function.

[0350] At box 1640, SV stores MO data. Figure 7 An example of storing MO data at the SV is shown, for example, as for... Figure 7 The storage is described in stages 13, 17, and 23. Storage can be, for example, by... Figure 23 The storage and forwarding component 2399 of the network entity 2302 in the network is used to perform this.

[0351] At box 1650, SV cancels UE. Figure 7 and Figure 9 Examples of deregistration are illustrated, such as those for... Figure 7 Phase 25 and Figure 9 As described in stage 26 of the document. Cancellation can, for example, be performed by... Figure 23 The network entity 2302 in the network uses the storage and forwarding components 2399, communication interface 2348, transceiver 2346 and / or antenna 2380 to perform this function.

[0352] At box 1660, SV stops providing radio access to UE. Figure 7 and Figure 9 Example aspects of SV stopping UE's radio access are illustrated, for example, as for... Figure 7 Phase 28 and Figure 9 The termination of access can be, for example, by stage 29 described in the text. Figure 23 The storage and forwarding components 2399 and / or communication interface 2348 of the network entity 2302 are used to perform this function.

[0353] At box 1670, SV obtains the feeder link to the terrestrial network. Figure 8 An example aspect of SV obtaining a feeder link is illustrated. The feeder link can be obtained, for example, by... Figure 23 The network entity 2302 in the network uses the storage and forwarding components 2399, communication interface 2348, transceiver 2346 and / or antenna 2380 to perform this function.

[0354] At box 1680, the SV forwards MO data to at least one remote endpoint via a terrestrial network, for example, as in combination with Figure 8 As described in the example below. Forwarding can, for example, be performed by... Figure 23 The network entity 2302 in the network uses the storage and forwarding components 2399, communication interface 2348, transceiver 2346 and / or antenna 2380 to perform this function.

[0355] In some aspects, the service link supports radio access using 4G LTE, 5G NR, or future 6G standards, where SV includes RAN and CN, for example, as for... Figure 2 and Figures 7 to 9 As described. When the serving link supports 5G NR, registering a UE may include performing NAS registration for the UE, and deregistering a UE may include performing NAS deregistration for the UE, for example, as for... Figure 7 and Figure 9 As described above. When the serving link supports 4G LTE, registering a UE may include performing a NAS attach to the UE, and deregistering a UE may include performing a NAS detach, for example, as described above. Figure 14B The description that follows the description.

[0356] In some aspects, the SV includes an endpoint proxy function (e.g., endpoint proxy 240) for at least one remote endpoint, wherein the endpoint proxy function simulates the behavior of at least one remote endpoint from the perspective of the UE, and wherein the endpoint proxy function receives and stores MO data. Simulating the behavior of at least one remote endpoint from the perspective of the UE may include returning at least one of the following: a pre-configured response to the UE at the application level; a response to the UE at the transport level; or both, for example, as for Figure 7 As described.

[0357] In some respects, MO data includes at least one of the following: MO SMS messages; media data of the Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing, for example, as for... Figure 7 As described.

[0358] In some aspects, forwarding MO data to at least one remote endpoint via a terrestrial network may include forwarding MO data to a terrestrial server (e.g., SFC 202), wherein the server forwards MO data to at least one remote endpoint via a terrestrial network, for example, as for... Figure 8 As described. The server can access the network using option (a), option (b), or option (c), wherein: for option (a), the server attaches to the network as an NTN gateway, and the network includes a RAN and a CN for radio access type; for option (b), the server attaches to the network as a base station, and the network includes a CN for radio access type; and for option (c), the server includes the network or is part of the network, for example, as described for... Figures 4 to 6 As described. The server may include a UE proxy function (e.g., UE proxy 340) for the UE, wherein the UE proxy function simulates the behavior of the UE from the perspective of at least one remote endpoint and from the perspective of the network, and the SV can transmit MO data to the UE proxy function, wherein the UE proxy function can forward MO data to at least one remote endpoint, for example, as for... Figure 8 As described. Simulating UE behavior from the perspective of at least one remote endpoint may include transmitting at least one of the following by the UE proxy function: a pre-configured message at the application level to at least one remote endpoint; a response at the transport level to at least one remote endpoint; or both, for example, as described for Figure 8 As described. Simulating UE behavior from a network perspective may include actions performed by the UE agent function: for option (a) or option (b) when the radio access type is 5G NR, the UE registers with the network's NAS, for example, as for... Figure 8As described; or for option (a) or option (b) when the radio access type is 4G LTE, the UE's NAS attachment to the network, for example, as described above. Figure 14B The description follows. Simulating UE behavior from a network perspective may also include keeping the UE in a persistent connection state by UE proxy functions from a network perspective, for example, as described for... Figure 8 As described.

[0359] In some respects, the SV can: receive terminated (MT) data from a mobile station via a network, wherein the MT data is initiated by at least one remote endpoint; store the MT data; and transmit the MT data to the UE at a later time using a serving link, for example, as for... Figure 8 and Figure 9 As described. MT data may include at least one of the following: MT SMS messages; media data using a Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; email; or some combination of the foregoing. SV may receive MT data from a terrestrial server (e.g., SFC 202), wherein the server receives MT data from at least one remote endpoint via a terrestrial network, for example, as for... Figure 8 As described.

[0360] In some respects, the SV broadcasts an indication to the UE that the SV is operating in store-and-forward mode, whereby the UE accesses the SV using a serving link and then, based on the indication broadcast by the SV that the SV is operating in store-and-forward mode, for example, as for Figure 7 As described. The SV may have subscription information for the UE, wherein the subscription information for the UE allows the UE to access the SV when the SV is operating in store-and-forward mode, for example, as for... Figure 7 As described.

[0361] Figure 17 This is a flowchart of a method 1700 that supports wireless communication performed by a server (e.g., SFC 202; network entity 2402). The following section discusses... Figure 24 Example components for the server are provided. This method improves communication between the SV and the UE via an intermittent feeder link connected to a terrestrial network.

[0362] At box 1710, the server receives mobile station-initiated (MO) data from a spacecraft (e.g., SV 104) having a feeder link to the server, wherein the MO data is intended for use with at least one remote endpoint (e.g., remote endpoint 116), wherein when the SV does not have a feeder link, a user equipment (e.g., UE 102) uses a serving link to transmit the MO data to the SV, and wherein the UE registers with the SV without assistance from the server and later deregisters from the SV. Figure 7 and Figure 8 This illustrates an example aspect of a server receiving MO data from an SV. Reception can, for example, be performed by... Figure 24 The network entity 2402 uses the store and forward component 2499, communication interface 2448, transceiver 2446 and / or antenna 2480 to perform this function.

[0363] At box 1720, the server forwards MO data to at least one remote endpoint via a network (e.g., PLMN 108), for example, as for... Figure 8 As described. Forwarding can, for example, be by Figure 24 The network entity 2402 uses the store and forward component 2499, communication interface 2448, transceiver 2446 and / or antenna 2480 to perform this function.

[0364] In some aspects, the service link supports radio access using 4G LTE, 5G NR, or future 6G standards, and the SV includes RAN and CN, for example, as for... Figure 2 and Figures 7 to 9 As described. When the serving link supports 5G NR, UE registration with the SV may include UE performing NAS registration with the SV before transmitting MO data to the SV, and deregistration with the SV may include UE performing NAS deregistration with the SV after transmitting MO data to the SV, for example, as for... Figure 7 As described above. When the serving link supports 4G LTE, UE registration with the SV may include the UE performing a NAS attach with the SV before transmitting MO data to the SV, and UE deregistration from the SV may include the UE performing a NAS detach from the SV, for example, as described above. Figure 14B The description that follows the description.

[0365] In some aspects, the SV includes an endpoint proxy function (e.g., endpoint proxy 240) for at least one remote endpoint, wherein the endpoint proxy function simulates the behavior of at least one remote endpoint from the perspective of the UE, and wherein MO data is received by the server from the endpoint proxy function, for example, as for Figure 7 and Figure 8As described. Simulating the behavior of at least one remote endpoint from the UE's perspective may include the endpoint proxy function returning at least one of the following: a pre-configured response to the UE at the application level; a response to the UE at the transport level; or both, for example, as described for Figure 7 As described.

[0366] In some respects, MO data includes at least one of the following: MO SMS messages; media data of the Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing, for example, as for... Figure 7 As described.

[0367] In some aspects, the server uses option (a), option (b), or option (c) to access the network, wherein: for option (a), the server attaches to the network as an NTN gateway, and the network includes a RAN and a CN for radio access type; for option (b), the server attaches to the network as a base station, and the network includes a CN for radio access type; and for option (c), the server includes the network or is part of the network, for example, as for... Figures 4 to 6 As described. The server may include a UE proxy function (e.g., UE proxy 340) for the UE, wherein the UE proxy function simulates the behavior of the UE from a first perspective of at least one remote endpoint and a second perspective of the network, wherein MO data is received by the UE proxy function from the SV, and wherein forwarding MO data to at least one remote endpoint includes forwarding MO data from the UE proxy function, for example, as for... Figure 8 As described. Simulating the behavior of a UE from the perspective of at least one remote endpoint may include transmitting at least one of the following: a pre-configured message at the application level to at least one remote endpoint; a response at the transport level to at least one remote endpoint; or both, for example, as described for Figure 8 As described. Simulating UE behavior from the network's perspective may include performing: for option (a) or option (b) when the radio access type is 5G NR, the UE registers with the network's NAS, for example, as for... Figure 8 As described; or for option (a) or option (b) when the radio access type is 4G LTE, the UE's NAS attachment to the network, for example, as described above. Figure 14B The description follows. Simulating UE behavior from a network perspective may also include keeping the UE in a persistent connection state from a network perspective, for example, as described for Figure 8 As described.

[0368] In some aspects, the server: receives terminated (MT) data from a mobile station via a network, wherein the MT data is initiated by at least one remote endpoint; stores the MT data; and transmits the MT data to a second SV (e.g., another SV 104) using a second feeder link, wherein the SV later forwards the MT data to the UE using a second serving link, for example, as for... Figure 8 and Figure 9 As described. MT data may include at least one of the following: MT SMS messages; media data of the Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; email; or some combination of the foregoing, for example, as described for... Figure 8 As described.

[0369] In some respects, the SV and server have subscription information for the UE, wherein the subscription information for the UE allows the UE to transmit MO data to at least one remote endpoint via the SV and server, for example, as for... Figure 7 and Figure 8 As described.

[0370] Figure 18 This is a flowchart of a method 1800 supporting wireless communication performed by user equipment (e.g., UE 102, device 2204). The following section discusses... Figure 22 Example components of the UE are provided. This method can improve UE coverage by enabling the UE to transmit and / or receive communications via the SV when the SV may have intermittent feeder link connections to a terrestrial network.

[0371] At box 1810, the UE obtains mobile station-initiated (MO) data intended for use with at least one remote endpoint (e.g., remote endpoint 116). As an example, Figure 10 and Figure 11 This illustrates various aspects of a UE acquiring MO data intended for use at a remote endpoint. As an example, acquisition is performed, for instance, by the communication component 2298, transceiver 2222, and / or antenna 2280 of device 2204.

[0372] At box 1820, the UE packages the mobile station-initiated (MO) data into a single MO dataset, for example, as for... Figure 10 and Figure 11 As described. As an example, packaging can be performed, for instance, by the communication component 2298 of device 2204.

[0373] At box 1830, the UE uses a serving link to access the spacecraft (e.g., SV 104), where the SV does not have a feeder link to a terrestrial network (e.g., PLMN 108), for example, as for... Figure 10 and Figure 11 As described. As an example, access may be performed, for instance, by the communication component 2298, transceiver 2222, and / or antenna 2280 of device 2204.

[0374] At box 1840, the UE transmits the MO dataset to the SV, where the SV stores the MO dataset. Figure 10 and Figure 11 An example aspect of the UE transmitting an MO set to an SV is illustrated. As an example, the transmission is performed, for example, by the communication component 2298, transceiver 2222, and / or antenna 2280 of device 2204.

[0375] At box 1850, the UE stops accessing the SV, where the SV later has a feeder link to a terrestrial network, where the SV uses the feeder link to forward the MO dataset to another entity, where the other entity unpacks the MO dataset into MO data, and where the other entity provides the MO data to at least one remote endpoint, for example, as for... Figure 10 and Figure 11 As described. As an example, a stop can be performed, for instance, by the communication component 2298 of device 2204.

[0376] In some respects, the service link supports radio access to the SV using 4G LTE, 5G NR, or future 6G standards, and the SV includes both RAN and CN, for example, as for... Figure 2 , Figure 10 and Figure 11 As described. When the serving link supports 5G NR, accessing the SV may include performing NAS registration with the SV, and stopping access to the SV may include performing NAS deregistration with the SV, for example, as for... Figure 10 and Figure 11 As described above. When the serving link supports 4G LTE, accessing the SV may include performing NAS attachment to the SV, and stopping access to the SV may include performing NAS decoupling from the SV, for example, as described above. Figure 14B The description that follows the description.

[0377] In some respects, MO data includes at least one of the following: MO SMS messages; media data of the Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing, for example, as for... Figure 10 and Figure 11 As described.

[0378] In some respects, a single MO dataset comprises bit sequences or octet sequences, for example, as for... Figure 10 and Figure 11 As described.

[0379] In some respects, packaging MO data into a single MO dataset includes: combining different types of MO data into a single MO dataset; and including control information within the MO dataset that identifies different types of MO data, for example, such as for... Figure 10 and Figure 11 As described. Unpacking a single MO dataset into MO data by another entity may then include: the other entity identifying different types of MO data within the single MO dataset based on control information; and the other entity separating different types of MO data, for example, as for... Figure 10 and Figure 11 As described.

[0380] In some aspects, another entity is a terrestrial server (e.g., SFC 202), wherein the terrestrial server provides MO data to at least one remote endpoint by transmitting MO data to at least one remote endpoint via a network, for example, as for... Figure 10 As described. The server can access the network using option (a), option (b), or option (c), wherein: for option (a), the server attaches to the network as an NTN gateway, and the network includes a RAN and a CN for radio access type; for option (b), the server attaches to the network as a base station, and the network includes a CN for radio access type; and for option (c), the server includes the network or is part of the network, for example, as described for... Figures 4 to 6 As described.

[0381] In some aspects, a single MO dataset is transparent to the SV, and the other entity includes at least one remote endpoint. In some aspects, at least one remote endpoint includes a single remote endpoint, where the SV uses a feeder link to forward the MO dataset to a terrestrial server (e.g., SFC 202), and where the terrestrial server forwards the MO dataset to the single endpoint via the network, for example, as for... Figure 11 As described.

[0382] In some respects, the SV can be the first SV, the feeder link can be the first feeder link, and the serving link can be the first serving link. In such respects, the UE can later use the second serving link to access the second SV (e.g., another SV 104), where the second SV does not have a second feeder link to the terrestrial network. The UE can then receive a mobile station termination (MT) dataset from the second SV, where the MT dataset contains MT data initiated by at least one remote endpoint (e.g., where the MT data is stored by the second SV), for example, as for... Figure 10 and Figure 11As described. The UE can then obtain MT data by unpacking the MT dataset. MT data may include at least one of the following: MT SMS messages; media data using Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; emails; or some combination of the above, for example, as described for... Figure 10 and Figure 11 As described. The second SV can receive MT datasets from a ground-based server (e.g., SFC 202), wherein the server receives MT data from at least one remote endpoint via a network, and wherein the server packages the MT data into an MT dataset, for example, as described for... Figure 10 As described. Alternatively, the second SV may receive MT datasets from a ground-based server (e.g., SFC 202), wherein the server receives MT datasets via a network from at least one remote endpoint, wherein the at least one remote endpoint comprises a single remote endpoint, and wherein the single remote endpoint packages MT data into an MT dataset, for example, as described for Figure 11 As described. The UE may also: obtain second MO data intended for use with at least one remote endpoint; package the second MO data into a second single MO dataset; and transmit the second single MO dataset to a second SV, wherein the second SV stores the second single MO dataset, wherein the second SV later has a second feeder link to a terrestrial network, wherein the SV uses the feeder link to forward the second single MO dataset to another entity, wherein the other entity unpacks the second single MO dataset into second MO data, and wherein the other entity provides the second MO data to at least one remote endpoint, for example, as for Figure 10 and Figure 11 As described.

[0383] In some respects, the packaging of MO data into a single MO dataset and / or the unpacking of the MT dataset into MT data at box 1820 can be performed by an application on the UE, for example, as targeted at Figure 10 and Figure 11 As described. When the UE does not have access to the SV, the UE's user can provide MO data to the application and obtain MT data from the application.

[0384] Figure 19 This is a flowchart of method 1900 that supports wireless communication performed by a server (e.g., SFC 202; network entity 2402). The following section discusses... Figure 24 Example components for the server are provided. This method improves communication between the SV and the UE via an intermittent feeder link connected to a terrestrial network.

[0385] At box 1910, the server receives an MO dataset from a spacecraft (e.g., SV 104), where the SV has a feeder link to the server, and where the MO dataset includes MO data intended for use by at least one remote endpoint (e.g., remote endpoint 116). Figure 10 and Figure 11 Various example aspects of a server receiving an MO dataset from an SV are illustrated. Reception can, for example, be performed by... Figure 24 The network entity 2402 uses the store and forward component 2499, communication interface 2448, transceiver 2446 and / or antenna 2480 to perform this function.

[0386] At box 1920, the server provides the MO dataset to another entity, which unpacks the MO dataset into MO data, and provides the MO data to at least one remote endpoint. When the SV does not have a feeder link, the user equipment (e.g., UE 102) uses a serving link to transmit the MO dataset to the SV, and the UE registers with the SV and later deregisters from it without assistance from the server, for example, as for... Figure 10 and Figure 11 As described. Provided, for example, by Figure 24 The network entity 2402 uses the store and forward component 2499, communication interface 2448, transceiver 2446 and / or antenna 2480 to perform this function.

[0387] In some aspects, the serving link supports UE radio access to the SV using 4G LTE, 5G NR, or future 6G standards, and the SV includes RAN and CN, for example, as for... Figure 2 , Figure 10 and Figure 11 As described. When the serving link supports 5G NR, UE registration with the SV may include UE performing NAS registration with the SV before transmitting the MO dataset to the SV, and deregistration with the SV may include UE performing NAS deregistration with the SV after transmitting the MO dataset to the SV, for example, as for... Figure 10 and Figure 11 As described above. When the serving link supports 4G LTE, UE registration with the SV may include the UE performing a NAS attach with the SV before transmitting the MO dataset to the SV, and UE deregistration from the SV may include the UE performing a NAS detach from the SV, for example, as described above. Figure 14B The description that follows the description.

[0388] In some aspects, the UE obtains MO data and packages the MO data into an MO dataset, for example, as for... Figure 10 and Figure 11As described. Packaging MO data into a single MO dataset by the UE may include: combining different types of MO data into an MO dataset; and including control information in the MO dataset that identifies the different types of MO data, for example, such as for... Figure 10 and Figure 11 As described. Unpacking a single MO dataset into MO data by another entity may include: the other entity identifying different types of MO data within the single MO dataset based on control information; and the other entity separating different types of MO data, for example, as for... Figure 10 and Figure 11 As described.

[0389] In some respects, MO data includes at least one of the following: MO SMS messages; media data of the Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing, for example, as for... Figure 10 and Figure 11 As described.

[0390] In some respects, the MO dataset may include bit sequences or octet sequences, for example, as for... Figure 10 and Figure 11 As described.

[0391] In some respects, another entity is a ground-based server, and the server can then provide MO data to at least one remote endpoint by transmitting MO data over a network, for example, as for... Figure 10 As described. The server can access the network using option (a), option (b), or option (c), wherein: for option (a), the server attaches to the network as an NTN gateway, and the network includes a RAN and a CN for radio access type; for option (b), the server attaches to the network as a base station, and the network includes a CN for radio access type; and for option (c), the server includes the network or is part of the network, for example, as described for... Figures 4 to 6 As described.

[0392] In some aspects, the other entity includes at least one remote endpoint, wherein the at least one remote endpoint includes a single remote endpoint, for example, as for... Figure 11 As described. In this respect, the server can forward the MO dataset to a single endpoint over the network, for example, as described for Figure 11 As described.

[0393] In some aspects, the server obtains a mobile station termination (MT) dataset, wherein the MT dataset includes MT data, and wherein the MT data is initiated by at least one remote endpoint, for example, as for Figure 10 and Figure 11 As described. The server can then store the MT dataset and transmit it to a second SV (e.g., another SV 104) using a second feeder link, wherein the second SV later forwards the MT dataset to the UE using a second service link, and wherein the UE obtains the MT data by unpacking the MT dataset, for example, as described for Figure 10 and Figure 11 As described. MT data may include at least one of the following: MTSMS messages; media data of the Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; email; or some combination of the foregoing, for example, as described for Figure 10 and Figure 11 As described. The server can receive MT data from at least one remote endpoint via a terrestrial network, and the server can then package the MT data into an MT dataset, for example, as for... Figure 10 As described. Alternatively, the server may receive the MT dataset via a network from at least one remote endpoint, wherein the at least one remote endpoint comprises a single remote endpoint, and wherein the single remote endpoint packages the MT data into the MT dataset, for example, as described for Figure 11 As described. The server can also receive a second MO dataset from a second SV (e.g., another SV 104), wherein the second SV has a second feeder link to the server, and wherein the second MO dataset includes second MO data intended for use with at least one remote endpoint, e.g., as for... Figure 10 and Figure 11 As described. The server can then provide a second MO dataset to another entity, which unpacks the second MO dataset into second MO data, which provides the second MO data to at least one remote endpoint, where the UE uses a second serving link to transmit the second MO dataset to the second SV when the SV does not have a feeder link, and where the UE registers with the second SV and later deregisters from the second SV without assistance from the server, for example, as for Figure 10 and Figure 11 As described.

[0394] In some respects, packaging MO data into MO datasets and unpacking MT datasets into MT data can be performed by applications on the UE, for example, as for... Figure 10 and Figure 11As described. When the UE does not have access to the SV, the UE's user can subsequently provide MO data to the application and obtain MT data from the application.

[0395] Figure 20 This is a flowchart of a method 2000 for securing radio access from a UE (e.g., UE 102) to a spacecraft (e.g., SV 104) in store-and-forward mode, executed by a first entity. The first entity can be an SV, a UE proxy function in a server, or a server itself. The following section discusses... Figure 23 Sample components for SV are provided. The following section discusses... Figure 24 Sample server components are provided.

[0396] At box 2010, the first entity transmits a key identifier (Kid) to the second entity, whereby the second entity determines the UE's alternate master key (K) based on the Kid and the UE's master key (K). ), where K is configured in the second entity, for example, as for Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described.

[0397] At box 2020, the first entity is based on K. To perform authentication and encryption key determination, where K The UE and Kid are configured in the first entity, wherein the UE accesses the SV using a serving link, wherein the SV does not have a feeder link when accessed by the UE, wherein the UE registers with the SV as part of accessing the SV, and wherein authentication and encryption key determination help enable secure data transfer via the SV between the UE and at least one remote endpoint (e.g., remote endpoint 116), for example, as for Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described.

[0398] In some respects, the second entity determines K based on Kid and K by encrypting Kid with K of the UE (e.g., using Equation 1). For example, such as for Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described. Kid may include one or more of the following: pseudo-random or random bits or octets; date; and time.

[0399] In some aspects, the service link supports radio access to SV using 4G LTE, 5G NR, or future 6G standards, where SV includes RAN and CN, for example, as for... Figure 2 , Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described. When the serving link supports 5G NR, UE registration with the SV may include the UE performing NAS registration with the SV, for example, as for... Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described above. When the serving link supports 4G LTE, UE registration with the SV may include the UE performing a NAS attach to the SV, for example, as described above. Figure 14B The description follows. The SV may also include an IMS, wherein registration by the UE to the SV includes performing IMS registration by the UE to the SV, for example, as for... Figure 13 As described.

[0400] In some respects, the first entity is the SV, and the second entity is the UE, and the SV (i.e., the first entity) can then transmit the Kid to the UE and perform authentication and encryption key determination as part of the UE's registration with the SV, for example, as for Figure 12 and Figure 13 As described. SV (i.e., the first entity) can also obtain Kid and K from one of the following: O&M server, where the O&M server is configured with Kid and K in SV. ; or UE, where UE will use Kid and K The data is transmitted to the SV as part of the UE's registration with the SV, for example, as for... Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described.

[0401] In some aspects, the UE transmits mobile station-initiated (MO) data intended for at least one remote endpoint to the SV, wherein the SV stores the MO data, wherein the SV later has a feeder link to a terrestrial network (e.g., PLMN 108), wherein the SV uses the feeder link to forward the MO data to a server (e.g., SFC 202), wherein the server registers the UE with the network, and wherein the server forwards the MO data via the network to at least one remote endpoint, for example, as for Figure 7 and Figure 8 As described. MO data may include at least one of the following: MO SMS messages; media data using Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the above, for example, as described for Figure 7As described. The server can access the network using option (a), option (b), or option (c), wherein: for option (a), the server attaches to the network as an NTN gateway, and the network includes a RAN and a CN for radio access type; for option (b), the server attaches to the network as a base station, and the network includes a CN for radio access type; and for option (c), the server includes the network or is part of the network, for example, as described for... Figures 4 to 6 As described. The server may include a UE proxy function (e.g., UE proxy 340) for the UE, wherein the UE proxy function simulates the behavior of the UE from the perspective of at least one remote endpoint and the network, wherein the UE proxy function receives MO data from the SV, and wherein the UE proxy function forwards the MO data to at least one remote endpoint via the network, for example, as for... Figure 7 and Figure 8 As described. Simulating UE behavior from the perspective of at least one remote endpoint by the UE proxy function may include transmitting at least one of the following by the UE proxy function: a pre-configured message at the application level to at least one remote endpoint; a response at the transport level to at least one remote endpoint; or both, for example, as described for Figure 8 As described. The UE proxy function simulating UE behavior from the network's perspective may include registering the UE with the network, wherein registering the UE with the network includes the UE proxy function performing one of the following operations: when the radio access type is 5G NR, the UE registers with the network's NAS; when the radio access type is 4G LTE, the UE attaches to the network's NAS; or the UE registers with the network's IMS, for example, as for... Figure 8 As described. The first entity can be a UE agent function, and the second entity can be a UDM or HSS in the UE's HPLMN. The first entity (i.e., the UE agent function) can then perform authentication and encryption key determination as part of registering the UE with the network, for example, as for... Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described. The first entity (i.e., the UE agent function) can also obtain Kid and K from one of the following: O&M server, where the O&M server is configured with Kid and K in the UE agent function or in the server. ;SV, where when SV has a feeder link to a terrestrial network, SV will have Kid and K The data is transmitted to the UE agent function; or to the UDM or HSS in the UE's HPLMMN, where the UDM or HSS transmits Kid and K to the UE agent function via a terrestrial network. As part of registering a UE with a terrestrial network, for example, as for... Figure 12 , Figure 13 and Figure 14B As described.

[0402] In some aspects, the UE receives Mobile Station Termination (MT) data from the SV, wherein the MT data is stored by the SV, wherein the SV receives the MT data from a server (e.g., SFC 202), wherein the server registers the UE with the network, and wherein the server receives the MT data from at least one remote endpoint via a terrestrial network (e.g., PLMN 108), for example, as for Figure 8 and Figure 9 As described. MT data may include at least one of the following: MT SMS messages; media data of the Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; email; or some combination of the foregoing, for example, as described for... Figure 8 As described. The first entity can be the SV, and the second entity can be the UE, and the SV (i.e., the first entity) can then perform authentication and encryption key determination as part of the UE's registration with the SV, for example, as for... Figure 12 , Figure 13 , Figure 14A and Figure 14B As described. SV (i.e., the first entity) can also obtain Kid and K from the server. The server receives Kid and K from the UE's HPLMN. As part of the server's registration of the UE with the network, for example, as for... Figure 14B As described.

[0403] Figure 21 This is a flowchart of method 2100, executed by a second entity, to secure radio access from a UE (e.g., UE 102) to a spacecraft (e.g., SV 104) in store-and-forward mode. The second entity can be the UE or an entity in the UE's HPLMN (e.g., UDM or HSS). The following section discusses... Figure 22 Sample components for the UE are provided. The following section discusses... Figure 25 Sample components for UDM and HSS are provided.

[0404] At box 2110, the second entity receives a key identifier (Kid) from the first entity, for example, as for... Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described.

[0405] At box 2120, the second entity determines the UE's alternate master key (K) based on Kid and the UE's master key (K). ), where K is configured in the second entity, for example, as for Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described.

[0406] At box 2130, the second entity is based on K. To perform authentication and encryption key determination, where K The UE and Kid are configured in the first entity, wherein the UE accesses the SV using a serving link, wherein the SV does not have a feeder link when accessed by the UE, wherein the UE registers with the SV as part of accessing the SV, and wherein authentication and encryption key determination help enable secure data transfer via the SV between the UE and at least one remote endpoint (e.g., remote endpoint 116), for example, as for Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described.

[0407] In some respects, the second entity determines K based on Kid and K by encrypting Kid with K of the UE (e.g., using Equation 1). For example, such as for Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described. Kid may include one or more of the following: pseudo-random or random bits or octets; date; and time.

[0408] In some respects, the service link supports radio access to the SV using 4G LTE, 5G NR, or future 6G standards, and the SV includes both RAN and CN, for example, as for... Figure 2 , Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described. When the serving link supports 5G NR, UE registration with the SV may include the UE performing NAS registration with the SV, for example, as for... Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described above. When the serving link supports 4G LTE, UE registration with the SV may include the UE performing a NAS attach to the SV, for example, as described above. Figure 14B The description follows. The SV may also include an IMS, wherein registration by the UE to the SV includes performing IMS registration by the UE to the SV, for example, as for... Figure 13 As described.

[0409] In some respects, the first entity is the SV, and the second entity is the UE, and the UE (i.e., the second entity) can then receive the Kid from the SV and perform authentication and encryption key determination as part of registration with the SV, for example, as for Figure 12 and Figure 13 As described. SV (i.e., the first entity) can also obtain Kid and K from one of the following: O&M server, where the O&M server is configured with Kid and K in SV. ; or UE, where UE will use Kid and K The data is transmitted to the SV as part of the UE's registration with the SV, for example, as for... Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described.

[0410] In some aspects, the UE transmits mobile station-initiated (MO) data intended for at least one remote endpoint to the SV, wherein the SV stores the MO data, wherein the SV later has a feeder link to a terrestrial network (e.g., PLMN 108), wherein the SV uses the feeder link to forward the MO data to a server (e.g., SFC 202), wherein the server registers the UE with the network, and wherein the server forwards the MO data via the network to at least one remote endpoint, for example, as for Figure 7 and Figure 8 As described. MO data may include at least one of the following: MO SMS messages; media data using Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the above, for example, as described for Figure 7 As described. The server can access the network using option (a), option (b), or option (c), wherein: for option (a), the server attaches to the network as an NTN gateway, and the network includes a RAN and a CN for radio access type; for option (b), the server attaches to the network as a base station, and the network includes a CN for radio access type; and for option (c), the server includes the network or is part of the network, for example, as described for... Figures 4 to 6 As described. The server may include a UE proxy function (e.g., UE proxy 340) for the UE, wherein the UE proxy function simulates the behavior of the UE from the perspective of at least one remote endpoint and the network, wherein the UE proxy function receives MO data from the SV, and wherein the UE proxy function forwards the MO data to at least one remote endpoint via the network, for example, as for... Figure 8As described. Simulating UE behavior from the perspective of at least one remote endpoint by the UE proxy function may include transmitting at least one of the following by the UE proxy function: a pre-configured message at the application level to at least one remote endpoint; a response at the transport level to at least one remote endpoint; or both, for example, as described for Figure 8 As described. The UE proxy function simulating UE behavior from the network's perspective may include registering the UE with the network, wherein registering the UE with the network includes the UE proxy function performing one of the following operations: when the radio access type is 5G NR, the UE registers with the network's NAS; when the radio access type is 4G LTE, the UE attaches to the network's NAS; or the UE registers with the network's IMS, for example, as for... Figure 8 As described. The first entity can be a UE agent function, and the second entity can be a UDM or HSS in the UE's HPLMN, and the second entity (i.e., UDM or HSS) can then perform authentication and encryption key determination as part of the UE's registration with the network by the server, for example, as for... Figure 14B As described. The first entity (i.e., the UE agent function) can obtain Kid and K from one of the following: O&M server, where the O&M server is configured with Kid and K in the UE agent function or in the server. ;SV, where when SV has a feeder link to a terrestrial network, SV will have Kid and K The data is passed to the UE agent function; or to the UDM or HSS in the UE's HPLMMN, wherein the UDM or HSS transmits Kid and K to the UE agent function via a terrestrial network. As part of the server registering the UE with the terrestrial network, for example, as for... Figure 12 , Figure 13 , Figure 14A and / or Figure 14B As described.

[0411] In some aspects, the UE receives Mobile Station Termination (MT) data from the SV, wherein the MT data is stored by the SV, wherein the SV receives the MT data from a server (e.g., SFC 202), wherein the server registers the UE with the network, and wherein the server receives the MT data from at least one remote endpoint via a terrestrial network, for example, as for Figure 8 and Figure 9 As described. MT data may include at least one of the following: MT SMS messages; media data of the Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; email; or some combination of the foregoing, for example, as described for... Figure 8 As described. The first entity can be the SV, and the second entity can be the UE, and the UE (i.e., the second entity) can then perform authentication and encryption key determination as part of registration with the SV, for example, as for... Figure 12 , Figure 13 , Figure 14A And / or as described in 14B. SV (i.e., the first entity) can also obtain Kid and K from the server. The server receives Kid and K from the UE's HPLMN. As part of the server's registration of the UE with the network, for example, as for... Figure 14B As described.

[0412] Figure 22 Figure 2200 illustrates an example of a hardware implementation of device 2204. Device 2204 may be a UE, a component of a UE, or may implement UE functionality. For example, the device may correspond to UE 102, a component of UE 102, or may implement the functionality of UE 102, such as by UE 102 in... Figures 1 to 14B In any of them or Figure 15 , Figure 18 , Figure 21 , Figure 27 , Figure 30 or Figure 33Any aspect of the process described in the flowchart of any of the following. In some aspects, device 2204 may include at least one cellular baseband processor 2224 (also referred to as a modem) coupled to one or more transceivers 2222 (e.g., cellular RF transceivers). Cellular baseband processor 2224 may include at least one on-chip memory 2224'. In some aspects, device 2204 may also include one or more subscriber identity module (SIM) cards 2220 and at least one application processor 2206 coupled to a secure digital card (SD) card 2208 and a screen 2210. Application processor 2206 may include on-chip memory 2206'. In some aspects, device 2204 may also include a Bluetooth module 2212, a WLAN module 2214, an SPS module 2216 (e.g., a GNSS module), one or more sensor modules 2218 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 2226, a power supply 2230, and / or a camera 2232. Bluetooth module 2212, WLAN module 2214, and SPS module 2216 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). Bluetooth module 2212, WLAN module 2214, and SPS module 2216 may include their own dedicated antennas and / or communicate using antenna 2280. Cellular baseband processor 2224 communicates with UE 102, SV 104, and / or RU associated with network entity 2202 via transceiver 2222 through one or more antennas 2280. Network entity 2202 may correspond to a terrestrial wireless communication network. As described herein, device 2204 may communicate with a terrestrial network via SV 104. Cellular baseband processor 2224 and application processor 2206 may each include computer-readable media / memory 2224', 2206', respectively. Additional memory module 2226 may also be considered as computer-readable media / memory. Each computer-readable media / memory (e.g., 2224', 2206', 2226) may be non-transitory. Cellular baseband processor 2224 and application processor 2206 are each responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by the cellular baseband processor 2224 / application processor 2206, the software causes the cellular baseband processor 2224 / application processor 2206 to perform the various functions described above. The cellular baseband processor 2224 and application processor 2206 are configured to perform the various functions described above based at least in part on information stored in memory.In other words, the cellular baseband processor 2224 and application processor 2206 can be configured to perform a first subset of the various functions described above without information stored in memory, and can be configured to perform a second subset of the various functions described above based on information stored in memory. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 2224 / application processor 2206 during software execution. The cellular baseband processor 2224 / application processor 2206 can be a component of the UE 2650 and can include at least one of a memory 2660, and / or a TX processor 2668, an RX processor 2656, and a controller / processor 2659. In one configuration, the device 2204 can be at least one processor chip (modem and / or application) and includes only the cellular baseband processor 2224 and / or the application processor 2206, while in another configuration, the device 2204 can be the entire UE (e.g., see UE 102 or...). Figure 26 (UE2650) and includes an additional module of device 2204.

[0413] As discussed above, in some aspects, component 2298 can be configured to: access the SV using the serving link when the SV does not have a feeder link to the terrestrial network and the UE has not registered with the SV; register with the SV; transmit MO data intended for at least one remote endpoint to the SV for storage at the SV until the SV has a feeder link to the terrestrial network to forward the MO data to at least one remote endpoint via the terrestrial network; deregister from the SV; and stop accessing the SV. In some aspects, the serving link supports radio access to the SV using 4G LTE, 5G NR, or future 6G standards, where the SV includes a RAN and a CN. In some aspects, when the serving link supports 5G NR, the device can be configured to perform NAS registration with the SV in order to register with the SV, and to perform NAS deregistration with the SV in order to deregister from the SV. When the serving link supports 4G LTE, the device can be configured to perform NAS attachment with the SV in order to register with the SV, and to perform NAS detachment from the SV in order to deregister from the SV. The device 2204 may also be configured to receive a response from an endpoint proxy function at the SV for at least one remote endpoint, the response simulating the behavior of at least one remote endpoint from the UE's perspective, the response instructing the endpoint proxy function to receive and store MO data. The response may simulate the behavior of at least one remote endpoint from the UE's perspective and includes at least one of the following: a pre-configured response at the application level to the UE; a transport-level response to the UE; or both. The MO data may include at least one of the following: MO SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; internet queries; email queries; or some combination of the foregoing. In some aspects, the SV can be a first SV, the feeder link for the first SV can be a first feeder link, and the serving link to the first SV can be a first serving link. The apparatus can also be configured to: access a second SV later using a second serving link, wherein the second SV does not have a second feeder link to a terrestrial network, and wherein the UE is not registered with the second SV; register with the second SV; receive MT data from the second SV, wherein the MT data includes SV storage data initiated by at least one remote endpoint; deregister from the second SV; and stop accessing the second SV. In some aspects, the apparatus can also be configured to: transmit second MO data intended for at least one second remote endpoint to the second SV for storage at that SV and forward it to the at least one second remote endpoint when the second SV later has a second feeder link to a terrestrial network.In some aspects, the device may also be configured to: receive an indication in a broadcast received from the SV, wherein the indication indicates that the SV is operating in store-and-forward mode; and access the SV using a serving link based on the indication received from the SV that the SV is operating in store-and-forward mode. In some aspects, when the SV is operating in store-and-forward mode, the UE may have a subscription to access the SV.

[0414] In some aspects, apparatus 2204, and specifically cellular baseband processor 2224 and / or application processor (e.g., including communication component 2298), may be configured to: acquire MO data intended for use by at least one remote endpoint; include components for packaging the MO data into a single MO dataset; access an SV using a serving link, wherein the SV does not have a feeder link to a terrestrial network; transmit the MO dataset to the SV for storage and forward it to another entity for provision to at least one remote endpoint when the SV has a feeder link to a terrestrial network; and stop access to the SV before the SV has a feeder link to a terrestrial network. In some aspects, the serving link supports radio access to the SV using 4G LTE, 5G NR, or future 6G standards, wherein the SV includes a RAN and a CN. In some aspects, for accessing the SV, device 2204 is configured to perform NAS registration with the SV, and for stopping access to the SV, the device is configured to perform NAS deregistration with the SV. When the serving link supports 5G NR, for accessing the SV, the device may be configured to perform NAS attachment to the SV, and when the serving link supports 4G LTE, for stopping access to the SV, the device may be configured to perform NAS decoupling from the SV. MO data may include at least one of the following: MO SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing. In some aspects, a single MO dataset may include a bit sequence or an octet sequence. In some aspects, for packaging MO data into a single MO dataset, device 2204 may be configured to combine different types of MO data into a single MO dataset, and include control information identifying the different types of MO data in the MO dataset. In some aspects, another entity is a terrestrial server. In some aspects, a single MO dataset is transparent to the SV, wherein the other entity includes at least one remote endpoint, wherein the at least one remote endpoint includes a single remote endpoint. In some aspects, the SV is a first SV, the feeder link for the first SV is a first feeder link, and the service link to the first SV is a first service link, and the apparatus can also be configured to: access a second SV at a later time using a second service link, wherein the second SV does not have a second feeder link to the terrestrial network; receive an MT dataset from the second SV, wherein the MT dataset contains MT data initiated by at least one remote endpoint; and obtain the MT data by unpacking the MT dataset.MT data may include at least one of the following: MTSMS messages, SIP media data, wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP methods; Internet query responses; email; or some combination of the foregoing. In some aspects, apparatus 2204 may also be configured to: obtain second MO data intended for use with at least one remote endpoint; package the second MO data into a second single MO dataset; and transmit the second single MO dataset to a second SV for storage and forwarding when the second SV later has a second feeder link to a terrestrial network. In some aspects, one or more of the actions of packaging MO data into a single MO dataset or unpacking MT datasets into MT data are performed by an application on the UE. In some aspects, when the UE does not have access to the SV, a user of the UE may provide MO data to an application and obtain MT data from the application.

[0415] In some respects, another component of communication component 2298 or device 2204 may be configured to determine K based on Kid and K by encrypting Kid using K of the UE. In some aspects, Kid includes one or more of the following: pseudo-random or random bits or octets; date and / or time (e.g., the date and / or time when Kid is determined); and duration or a second date and / or time (e.g., indicating when Kid is no longer valid). In some aspects, the serving link supports radio access to the SV using 4G LTE, 5G NR, or future 6G standards, where the SV includes a RAN and a CN. When the serving link supports 5G NR, UE registration to the SV may include UE NAS registration to the SV, and when the serving link supports 4G LTE, UE registration to the SV may include UE NAS attachment to the SV. In some aspects, the SV also includes IMS, where UE registration includes UE IMS registration to the SV. For example, the enabled secure delivery of data may be directed to a UE that transmits MO data intended for at least one remote endpoint to the SV for storage and forwards it to the terrestrial network via a server when the SV later has a feeder link to the terrestrial network, where the UE registers with the terrestrial network via the server. MO data may include at least one of the following: MO SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing. In some aspects, secure transmission of data may include MT data from at least one remote endpoint via a terrestrial network and an SV. MT data may include at least one of the following: MT SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; email; or some combination of the foregoing. In some aspects, the second entity may be a UE, and the first entity may be an SV, wherein communication component 2298 or another component of device 2204 is configured to perform authentication and encryption key determination as part of registering the UE with the SV. In some aspects, Kid and K It can come from one of the following: an O&M server; or a UE, where the UE will have Kid and K It is transmitted to the SV as part of the UE's registration with the SV.

[0416] Communication component 2298 or another component of the device may also be configured to perform or cause the device to perform [operations]. Figures 1 to 14B UE 102 in any of the above performs and / or combines Figure 15 , Figure 18 , Figure 21 , Figure 27 , Figure 30 or Figure 33Any aspect described in the flowchart of any of the above. Component 2298 may be located within cellular baseband processor 2224, application processor 2206, or both cellular baseband processor 2224 and application processor 2206. Component 2298 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination.

[0417] As shown in the figure, apparatus 2204 may include a variety of components configured for various functions. In some configurations, apparatus 2204, and specifically cellular baseband processor 2224 and / or application processor 2206, may include: components for accessing the SV using a serving link when the SV does not have a feeder link to a terrestrial network and the UE is not registered with the SV; components for registering with the SV; components for transmitting MO data intended for at least one remote endpoint to the SV for storage at the SV until the SV has a feeder link to a terrestrial network for forwarding the MO data to at least one remote endpoint via the terrestrial network; components for deregistering from the SV; and components for stopping access to the SV. In some aspects, the serving link supports radio access to the SV using 4G LTE, 5G NR, or future 6G standards, wherein the SV includes a RAN and a CN. In some aspects, when the serving link supports 5G NR, the component for registering with the SV is configured to perform NAS registration with the SV, and the component for deregistering from the SV is configured to perform NAS deregistration with the SV. When the serving link supports 4G LTE, the component for registering with the SV is configured to perform NAS attachment with the SV, and the component for deregistering from the SV is configured to perform NAS detachment from the SV. In some aspects, the apparatus may further include a component for receiving a response at the SV from an endpoint proxy function for at least one remote endpoint, the response simulating the behavior of at least one remote endpoint from the perspective of the UE, the response instructing the endpoint proxy function to receive and store MO data. In some aspects, the SV is a first SV, the feeder link for the first SV is a first feeder link, and the serving link to the first SV is a first serving link. The apparatus may further include: components for accessing the second SV later using a second serving link, wherein the second SV does not have a second feeder link to a terrestrial network, and wherein the UE is not registered to the second SV; components for registering with the second SV; components for receiving MT data from the second SV, wherein the MT data includes SV storage data initiated by at least one remote endpoint; components for deregistering from the second SV; and components for stopping access to the second SV. In some aspects, the apparatus may further include components for transmitting second MO data intended for at least one second remote endpoint to the second SV for storage at the SV and forwarding it to the at least one second remote endpoint when the second SV later has a second feeder link to a terrestrial network. In some aspects, the apparatus may further include: components for receiving an indication in a broadcast received from the SV, wherein the indication indicates that the SV is operating in store-and-forward mode; and components for accessing the SV using a serving link based on the indication received from the SV that the SV is operating in store-and-forward mode.

[0418] In some configurations, apparatus 2204, and specifically cellular baseband processor 2224 and / or application processor 2206, may include: components for acquiring MO data intended for use with at least one remote endpoint; components for packaging the MO data into a single MO dataset; components for accessing an SV using a serving link, wherein the SV does not have a feeder link to a terrestrial network; components for transmitting the MO dataset to the SV to store the MO dataset and forwarding it to another entity for provision to at least one remote endpoint when the SV has a feeder link to a terrestrial network; and components for stopping access to the SV before the SV has a feeder link to a terrestrial network. In some aspects, the serving link supports radio access to the SV using 4G LTE, 5G NR, or future 6G standards, wherein the SV includes a RAN and a CN. In some aspects, when the serving link supports 5G NR, the component for accessing the SV is configured to perform NAS registration with the SV, and the component for stopping access to the SV is configured to perform NAS deregistration with the SV. When the serving link supports 4G LTE, the component for accessing the SV is configured to perform NAS attachment with the SV, and the component for stopping access to the SV is configured to perform NAS decoupling from the SV. MO data may include at least one of the following: MO SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing. In some aspects, a single MO dataset may include a bit sequence or an octet sequence. In some aspects, the component for packaging MO data into a single MO dataset may be configured to combine different types of MO data into a single MO dataset, and include control information identifying the different types of MO data in the MO dataset. In some aspects, another entity is a terrestrial server. In some aspects, a single MO dataset is transparent to the SV, wherein the other entity includes at least one remote endpoint, wherein the at least one remote endpoint includes a single remote endpoint. In some aspects, the SV is a first SV, the feeder link for the first SV is a first feeder link, and the service link to the first SV is a first service link, and the apparatus further includes: components for accessing a second SV at a later time using a second service link, wherein the second SV does not have a second feeder link to the terrestrial network; components for receiving an MT dataset from the second SV, wherein the MT dataset contains MT data initiated by at least one remote endpoint; and components for obtaining MT data by unpacking the MT dataset.MT data may include at least one of the following: MT SMS messages, SIP media data, wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP methods; Internet query responses; email; or some combination thereof. In some aspects, apparatus 2204 may further include: components for obtaining second MO data intended for at least one remote endpoint; components for packaging the second MO data into a second single MO dataset; and components for transmitting the second single MO dataset to a second SV for storage and forwarding it when the second SV later has a second feeder link to a terrestrial network. In some aspects, one or more of packaging MO data into a single MO dataset or unpacking MT datasets into MT data is performed by an application on the UE. In some aspects, when the UE does not have access to the SV, a user of the UE can provide MO data to an application and obtain MT data from the application.

[0419] In some respects, device 2204 may correspond to a combination Figure 21 The second entity described. Apparatus 2204 may include components for implementing security measures performed by the second entity for UE radio access to the SV in store-and-forward mode. Apparatus 2204 may include: components for receiving a key identifier (Kid) from the first entity; and components for determining a substitute master key (K) for the UE based on the Kid and the UE's master key (K). The component K is configured in the second entity; and the component for using K The component that performs authentication and encryption key determination to enable secure data transfer between the UE and at least one remote endpoint via SV, wherein K The Kid is configured in the first entity, where secure data transmission occurs between UEs accessing the SV using a serving link when the SV does not have a feeder link, and UE registration with the SV is part of access to the SV. In some aspects, the component for determination is configured to determine K based on Kid and K by encrypting Kid using the UE's K. In some aspects, Kid includes one or more of the following: pseudo-random or random bits or octets; date and / or time; and duration or a second date and / or time. In some aspects, the serving link supports radio access to the SV using 4G LTE, 5G NR, or future 6G standards, where the SV includes a RAN and a CN. When the serving link supports 5G NR, UE registration to the SV may include UE NAS registration to the SV, and when the serving link supports 4G LTE, UE registration to the SV may include UE NAS attachment to the SV. In some aspects, the SV also includes IMS, where UE registration includes UE IMS registration to the SV. For example, the enabled secure delivery of data may be directed to a UE that transmits MO data intended for at least one remote endpoint to the SV for storage and forwards it to the terrestrial network via a server when the SV later has a feeder link to the terrestrial network, where the UE registers with the terrestrial network via the server. MO data may include at least one of the following: MO SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing. In some aspects, secure transmission of data may include MT data from at least one remote endpoint via a terrestrial network and an SV. MT data may include at least one of the following: MT SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; email; or some combination of the foregoing. In some aspects, the second entity may be a UE, and the first entity may be an SV, wherein the UE includes components for performing authentication and encryption key determination as part of registering the UE with the SV. In some aspects, Kid and K It can come from one of the following: an O&M server; or a UE, where the UE will have Kid and K It is transmitted to the SV as part of the UE's registration with the SV.

[0420] The device may also include features for performing the operation by Figures 1 to 14B UE execution and / or combination in any of them Figure 15 , Figure 18 , Figure 21 , Figure 27 , Figure 30 or Figure 33The components may be any aspect of the aspects described in the flowcharts of any of the components. These components may be components 2298 of device 2204 configured to perform the functions described by these components. As described above, device 2204 may include a TX processor 2668, an RX processor 2656, and a controller / processor 2659. Thus, in one configuration, these components may be the TX processor 2668, the RX processor 2656, and / or the controller / processor 2659 configured to perform the functions described by these components.

[0421] Figure 23 Figure 2300 illustrates an example of a hardware implementation for network entity 2302. The network entity may correspond to an SV, a component of an SV, or may implement, for example, a hardware implementation for... Figures 1 to 14B The SV functionality and / or combination described in any of the SV 104 Figure 16 , Figure 20 , Figure 21 , Figure 28 , Figure 32 and / or Figure 33 The method described in the flowchart of any of the above. Network entity 2302 may include at least one processor 2342, which may include on-chip memory 2342'. In some aspects, network entity 2302 may also include an additional memory module 2344 and a communication interface 2348, one or more transceivers 2346, an antenna 2380 and a communication interface 2348. Network entity 2302 may be configured to communicate with UE 102, for example, via a serving link, and with terrestrial network entity 2202, for example, via a feeder link, as in combination Figures 1 to 14B Any of the descriptions and / or combinations thereof Figure 16 , Figure 20 , Figure 21 , Figure 28 , Figure 32 and / or Figure 33 The method described in the flowchart of either of the above. On-chip memory 2342' and additional memory module 2344 can each be considered as computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Processor 2342 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 can also be used to store data manipulated by the processor when executing the software.

[0422] As discussed above, the store and forward component 2399 can be configured to: provide radio access to the UE via a serving link, wherein the SV does not have a feeder link to a terrestrial network, and wherein the UE is not registered with the SV; register the UE; receive MO data from the UE, the MO data being intended for use with at least one remote endpoint; store the MO data; deregister the UE; stop providing radio access to the UE; obtain a feeder link to the terrestrial network; and forward the MO data to at least one remote endpoint via the terrestrial network. In some aspects, the serving link supports radio access to the SV using 4G LTE, 5G NR, or future 6G standards, wherein the SV includes a RAN and a CN. When the serving link supports 5G NR, the network entity can be configured to perform NAS registration for the UE in order to register the UE, and to perform NAS deregistration for the UE in order to deregister the UE. When the serving link supports 4G LTE, the network entity can be configured to perform NAS attachment for the UE in order to register the UE, and to perform NAS detachment for the UE in order to deregister the UE. In some aspects, the SV may include an endpoint proxy function for at least one remote endpoint (e.g., it may be an aspect of the store and forward component 2399), which may be configured to simulate the behavior of at least one remote endpoint from the UE's perspective, receive and store MO data. In some aspects, to simulate the behavior of at least one remote endpoint from the UE's perspective, network entity 2302 may also be configured to return at least one of the following: a pre-configured response to the UE at the application level; a response to the UE at the transport level; or both. In some aspects, MO data may include at least one of the following: MO SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing. To forward MO data to at least one remote endpoint via a terrestrial network, network entity 2302 may be configured to forward the MO data to a terrestrial server for forwarding to at least one remote endpoint via the terrestrial network. In some aspects, network entity 2302 may also be configured to: receive MT data via a terrestrial network, the MT data being initiated by at least one remote endpoint; store the MT data; and transmit the MT data to the UE at a later time using a serving link. MT data may include at least one of the following: MT SMS messages, SIP media data, wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP methods; Internet query responses; email; or some combination of the foregoing.In some aspects, to receive MT data, network entity 2302 may be configured to receive MT data from a terrestrial server, wherein the MT data is initiated by at least one remote endpoint via a terrestrial network. In some aspects, network entity 2302 may also be configured to broadcast an indication to the UE that the SV is operating in store-and-forward mode, wherein based on the indication broadcast by the SV that the SV is operating in store-and-forward mode, access to the SV is provided to the UE using a serving link. In some aspects, the SV may have subscription information for the UE, which allows the UE to access the SV when the SV is operating in store-and-forward mode.

[0423] In some respects, the store-and-forward component 2399 and / or another component of the network entity 2302 may be configured to implement security measures performed by the first entity for the UE's radio access to the SV in store-and-forward mode. For example, the network entity may be configured to transmit a key identifier (Kid) to the second entity based on the UE's master key (K) configured in the second entity, so that the second entity can determine the UE's alternative master key (K) based on Kid and K. ); and based on K To perform authentication and encryption key determination to enable secure data transfer between the UE and at least one remote endpoint via SV, where K The Kid is configured in the first entity, where secure data transfer occurs between UEs accessing the SV using a serving link when the SV does not have a feeder link, and UE registration with the SV is part of access to the SV. In some aspects, the network entity (e.g., component 2399) can be configured to transmit the Kid so that the second entity can determine the K based on the Kid and K by encrypting the Kid using the UE's K. In some aspects, Kid includes one or more of the following: pseudo-random or random bits or octets; date and / or time; and duration or a second date and / or time. In some aspects, secure data transfer may be via a serving link supporting radio access to the SV using 4G LTE, 5G NR, or future 6G standards, wherein the SV includes a RAN and a CN. In some aspects, when the serving link supports 5G NR, UE registration to the SV includes UE NAS registration to the SV, wherein when the serving link supports 4G LTE, UE registration to the SV includes UE NAS attachment to the SV. In some aspects, the SV may also include an IMS, wherein UE registration to the SV includes UE IMS registration to the SV. In some aspects, the first entity may be the SV, the second entity may be the UE, and a network entity (e.g., component 2399) may be configured to transmit Kid from the SV to the UE and perform authentication and encryption key determination as part of the UE registration to the SV. In some aspects, the network entity (e.g., component 2399) may be configured to obtain Kid and K from one of the following: : O&M server, as the source of information from the O&M server to the SV, indicating Kid and K The configuration; or the UE, where the SV receives Kid and K from the UE. As part of the UE's registration with the SV, in some aspects, network entities (e.g., component 2399) can be configured based on the Kid and K from the UE's HPLMN. Get Kid and K from the server As part of the UE's registration with the terrestrial network. In some aspects, secure data delivery may include MO data from the UE intended for at least one remote endpoint being forwarded via SV at a later time when the SV later has a feeder link to the terrestrial network, wherein secure data delivery also includes a server that registers the UE with the terrestrial network. MO data may include at least one of the following: MO SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing. In some aspects, secure data delivery may include MT data from at least one remote endpoint via the terrestrial network and SV. MT data may include at least one of the following: MT SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; email; or some combination of the foregoing.

[0424] Another component of store and forward component 2399 or network entity 2302 may also be configured to perform or cause the network entity to perform by combination Figures 1 to 14B Any aspect and / or combination of any of the aspects of SV 104 execution described in any of the above. Figure 16 , Figure 20 , Figure 21 , Figure 28 , Figure 32 and / or Figure 33 The method described in the flowchart of any of the above. The store-and-forward component 2399 may be within one or more processors of the network entity 2302. The store-and-forward component 2399 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination.

[0425] Network entity 2302 may include a variety of components configured for various functions. In some configurations, network entity 2302 may include: components for providing radio access to a UE via a serving link, wherein the SV does not have a feeder link to a terrestrial network, and wherein the UE is not registered with the SV; components for registering the UE; components for receiving MO data from the UE, the MO data being intended for use with at least one remote endpoint; components for storing the MO data; components for deregistering the UE; components for stopping the provision of radio access to the UE; components for obtaining a feeder link to the terrestrial network; and components for forwarding the MO data to at least one remote endpoint via the terrestrial network. In some aspects, the serving link supports radio access to the SV using 4G LTE, 5G NR, or future 6G standards, wherein the SV includes a RAN and a CN. When the serving link supports 5G NR, the components for registering the UE may be configured to perform NAS registration of the UE, and the components for deregistration may be configured to perform NAS deregistration of the UE. When the serving link supports 4G LTE, the component for registering the UE can be configured to perform NAS attachment of the UE, and the component for deregistering the UE can be configured to perform NAS detachment of the UE. In some aspects, the SV may include an endpoint proxy function for at least one remote endpoint, which can be configured to simulate the behavior of at least one remote endpoint from the perspective of the UE, receive and store MO data. In some aspects, to simulate the behavior of at least one remote endpoint from the perspective of the UE, network entity 2302 may include a component for returning at least one of the following: a pre-configured response to the UE at the application level; a response to the UE at the transport level; or both. In some aspects, MO data may include at least one of the following: MO SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing. The component for forwarding MO data to at least one remote endpoint via a terrestrial network may be configured to forward the MO data to a terrestrial server for forwarding to at least one remote endpoint via the terrestrial network. In some aspects, network entity 2302 may further include: components for receiving MT data via a terrestrial network, the MT data being initiated by at least one remote endpoint; components for storing the MT data; and components for transmitting the MT data to the UE at a later time using a serving link. MT data may include at least one of the following: MT SMS messages, SIP media data, wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP methods; Internet query responses; email; or some combination of the foregoing.In some aspects, the components for receiving MT data may be configured to receive MT data from a terrestrial server, wherein the MT data is initiated by at least one remote endpoint via a terrestrial network. In some aspects, network entity 2302 may also include components for broadcasting to the UE an indication that the SV is operating in store-and-forward mode, wherein based on the indication broadcast by the SV that the SV is operating in store-and-forward mode, access to the SV is provided to the UE using a serving link. In some aspects, the SV may have subscription information for the UE, which allows the UE to access the SV when the SV is operating in store-and-forward mode.

[0426] In some configurations, the network entity may include components for implementing security measures performed by the first entity for UE radio access to the SV in store-and-forward mode. For example, the network entity may include: transmitting a key identifier (Kid) to the second entity based on the UE's master key (K) configured in the second entity, so that the second entity can determine the UE's alternative master key (K) based on Kid and K. ) components; and for K-based The component that performs authentication and encryption key determination to enable secure data transfer between the UE and at least one remote endpoint via SV, wherein K The Kid is configured in the first entity, where secure data transfer occurs between UEs accessing the SV using a serving link when the SV does not have a feeder link, and UE registration with the SV is part of access to the SV. In some aspects, the components for transmission can be configured to transmit the Kid so that the second entity can determine the K based on the Kid and the K by encrypting the Kid using the UE's K. In some aspects, Kid includes one or more of the following: pseudo-random or random bits or octets; date and / or time; and duration or a second date and / or time. In some aspects, secure data transfer may be via a serving link supporting radio access to the SV using 4G LTE, 5G NR, or future 6G standards, wherein the SV includes a RAN and a CN. In some aspects, when the serving link supports 5G NR, UE registration to the SV includes UE NAS registration to the SV, wherein when the serving link supports 4G LTE, UE registration to the SV includes UE NAS attachment to the SV. In some aspects, the SV may also include an IMS, wherein UE registration to the SV includes UE IMS registration to the SV. In some aspects, the first entity may be the SV, the second entity may be the UE, and the transmission component may be configured to transmit the Kid from the SV to the UE, and the execution component may be configured to perform authentication and encryption key determination as part of the UE registration to the SV. The network entity may also include components for obtaining the Kid and K from one of the following: Components: O&M server, as the server that directs Kid and K from the O&M server to the SV The configuration; or the UE, where the SV receives Kid and K from the UE. As part of the UE's registration with the SV, network entities may also include Kid and K for use with the HPLMN from the UE. Get Kid and K from the server As part of the UE's registration with the terrestrial network, secure data delivery may, in some aspects, include MO data from the UE intended for at least one remote endpoint, which may be forwarded via SV at a later time when SV later has a feeder link to the terrestrial network, wherein secure data delivery may also be via a server that registers the UE with the terrestrial network. MO data may include at least one of the following: MO SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing. In some aspects, secure data delivery may include MT data from at least one remote endpoint via the terrestrial network and SV. MT data may include at least one of the following: MT SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; email; or some combination of the foregoing.

[0427] Network entity 2302 may also include components for performing the combination Figures 1 to 14B Any aspect and / or combination of any of the aspects of SV 104 execution described in any of the above. Figure 16 , Figure 20 , Figure 21 , Figure 28 , Figure 32 and / or Figure 33 The component is a part of the method described in the flowchart of any of the components. This component may be a store-and-forward component 2399 of network entity 2302 configured to perform the functions described therein. As described above, network entity 2302 may include a TX processor 2616, an RX processor 2670, and a controller / processor 2675. Therefore, in one configuration, these components may be the TX processor 2616, the RX processor 2670, and / or the controller / processor 2675 configured to perform the functions described therein.

[0428] Figure 24Figure 2400 illustrates an example of a hardware implementation for network entity 2402. Network entity 2402 may be a server, a component of a server, or something that implements server functionality. For example, network entity 2402 may be configured to implement... Figures 2 to 14B Any of the descriptions in and / or the combination of the server Figure 17 , Figure 19 , Figure 20 , Figure 21 , Figure 29 , Figure 31 , Figure 32 and / or Figure 33 The flowchart in any of the above describes any aspect of the terrestrial SFC 202. Network entity 2402 may include at least one processor 2442, which may include on-chip memory 2442'. In some aspects, network entity 2402 may also include an additional memory module 2444 and a communication interface 2448 for exchanging communication with one or more SV104s and with one or more endpoints 116. In some aspects, communication interface 2448 may include one or more transceivers 2446 and an antenna 2480. Network entity 2402 may be configured to communicate with SV 104, for example, via a feeder link, and with one or more endpoints 116, as in combination. Figures 2 to 14B any of and / or Figure 17 , Figure 19 , Figure 20 , Figure 21 , Figure 29 , Figure 31 , Figure 32 and / or Figure 33 As described in either of the above. On-chip memory 2442' and additional memory module 2444 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Processor 2442 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 can also be used to store data manipulated by the processor when executing the software.

[0429] As discussed above, in some aspects, the store-and-forward component 2499 may be configured to receive MO data from an SV having a feeder link to a server, the MO data being intended for at least one remote endpoint and initiated by a UE when the SV does not have a feeder link to the server, wherein the network entity 2402 is configured to: receive MO data independently of registration and deregistration assistance used to register the UE with the SV and later deregister the UE from the SV; and forward the MO data via the network to at least one remote endpoint. In some aspects, the MO data may include at least one of the following: MO SMS messages; SIP media data, wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet queries; email queries; or some combination of the foregoing. In some aspects, network entity 2402 may be configured to access the network using option (a), option (b), or option (c), wherein: for option (a), the server is configured to attach to the network as an NTN gateway, and the network includes a RAN and a CN for radio access type; for option (b), the server is configured to attach to the network as a base station, and the network includes a CN for radio access type; and for option (c), the server includes the network or is part of the network. In some aspects, network entity 2402 may include a UE proxy function for a UE, wherein the UE proxy function is configured to simulate UE behavior from a first perspective of at least one remote endpoint and a second perspective of the network, wherein MO data is received from the SV by the UE proxy function, and wherein the network entity is configured to forward the MO data to the at least one remote endpoint, the at least one remote endpoint being configured to forward the MO data from the UE proxy function. In some aspects, to simulate UE behavior from the perspective of at least one remote endpoint, network entity 2402 may be configured to transmit at least one of the following: a pre-configured message at the application level to at least one remote endpoint; a response at the transport level to at least one remote endpoint; or both. In some aspects, to simulate UE behavior from a network perspective, network entity 2402 may be configured to: register the UE with the network's NAS when the radio access type is 5G NR for option (a) or option (b); or attach the UE to the network's NAS when the radio access type is 4G LTE for option (a) or option (b). In some aspects, to simulate UE behavior from a network perspective, network entity 2402 may also be configured to keep the UE in a persistently connected state from a network perspective. In some aspects, network entity 2402 may also be configured to: receive MT data via the network, the MT data being initiated by at least one remote endpoint; store the MT data; and transmit the MT data to a second SV using a second feeder link for later forwarding to the UE using a second serving link.MT data may include at least one of the following: MTSMS messages, SIP media data, wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-IP, IP, UDP / IP, or TCP / IP; Internet query responses; email; or some combination of the above.

[0430] In some aspects, network entity 2402 (e.g., store-and-forward component 2499) may be configured to: receive an MO dataset from an SV having a feeder link to a server, the MO dataset including MO data intended for use with at least one remote endpoint; and provide the MO dataset to another entity to unpack the MO dataset into MO data; wherein the MO dataset is initiated by the UE when the terrestrial server does not have a feeder link to the SV, and the MO dataset is received independently of registration and deregistration assistance provided for registering the UE with the SV and later deregistering the UE from the SV. In some aspects, the MO dataset may be based on 4G LTE, 5G NR, or future 6G standards. In some aspects, the MO dataset may include a single MO dataset comprising different types of MO data and control information identifying the different types of MO data, wherein, in order for the single MO dataset to be unpacked into MO data by another entity, netw...

Claims

1. An apparatus for wireless communication performed by a user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to cause the UE to: When the spacecraft (SV) does not have a feeder link to the ground-based network and the UE is not registered with the SV, a service link is used to access the SV; Register with the SV; Mobile station-initiated (MO) data intended for use at at least one remote endpoint is transmitted to the SV for storage at the SV until the SV has the feeder link to the terrestrial network for forwarding the MO data to the at least one remote endpoint via the terrestrial network; Cancel from the SV; as well as Stop accessing the SV.

2. The apparatus of claim 1, wherein the service link supports radio access to the SV using 4G LTE, 5G NR or future 6G standards, wherein the SV includes a radio access network (RAN) and a core network (CN).

3. The apparatus of claim 2, wherein when the serving link supports the 5G NR, in order to register with the SV, the at least one processor is configured to cause the UE to perform Non-Access Stratum (NAS) registration with the SV, and in order to deregister from the SV, the at least one processor is configured to cause the UE to perform NAS deregistration with the SV, wherein when the serving link supports the 4G LTE, in order to register with the SV, the at least one processor is configured to cause the UE to perform NAS attachment with the SV, and in order to deregister from the SV, the at least one processor is configured to cause the UE to perform NAS detachment from the SV.

4. The apparatus of claim 1, wherein the at least one processor is further configured to cause the UE to: At the SV, a response is received from the endpoint proxy function for the at least one remote endpoint, the response simulating the behavior of the at least one remote endpoint from the perspective of the UE, the response indicating that the endpoint proxy function is capable of receiving and storing the MO data.

5. The apparatus of claim 4, wherein the response simulating the behavior of the at least one remote endpoint from the perspective of the UE comprises at least one of the following: The application-level response to the pre-configured UE; The transmission level response to the UE; or It has both.

6. The apparatus of claim 1, wherein the MO data comprises at least one of the following: MO Short Message Service (SMS) messages; Media data of Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-Internet Protocol (non-IP), Internet Protocol (IP), User Datagram Protocol (UDP) / IP, or Transmission Control Protocol (TCP) / IP; Internet search; Email inquiry; or A combination of the above items.

7. The apparatus of claim 1, wherein the SV is a first SV, the feeder link for the first SV is a first feeder link, and the service link to the first SV is a first service link, and wherein the at least one processor is further configured to cause the UE to: At a later time, a second service link is used to access the second SV, wherein the second SV does not have a second feeder link to the terrestrial network, and wherein the UE is not registered with the second SV; Register with the second SV; Receive mobile station termination (MT) data from the second SV, wherein the MT data includes SV storage data initiated by the at least one remote endpoint; Cancel from the second SV; as well as Stop accessing the second SV.

8. The apparatus of claim 7, wherein the MT data comprises at least one of the following: MT Short Message Service (SMS) messages; Media data of Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-Internet Protocol (non-IP), Internet Protocol (IP), User Datagram Protocol (UDP) / IP, or Transmission Control Protocol (TCP) / IP; Internet query response; email; or A combination of the above items.

9. The apparatus of claim 7, wherein the at least one processor is further configured to cause the UE to transmit second MO data intended for use with the at least one remote endpoint to the second SV for storage at the second SV and to forward it to the at least one remote endpoint when the second SV later has a second feeder link to the terrestrial network.

10. The apparatus of claim 1, wherein the at least one processor is further configured to cause the UE to: Receive an indication in a broadcast received from the SV, wherein the indication indicates that the SV is operating in store-and-forward mode; and Based on the indication received from the SV that the SV is operating in the store and forward mode, the service link is used to access the SV.

11. The apparatus of claim 10, wherein the UE has a subscription to access the SV when the SV is operating in the store-and-forward mode.

12. An apparatus for wireless communication performed by a spacecraft (SV), the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to cause the SV: Radio access is provided to user equipment (UE) via a serving link, wherein the SV does not have a feeder link to a terrestrial network, and wherein the UE is not registered to the SV; Register the UE; The UE receives mobile station-initiated (MO) data, which is intended for use with at least one remote endpoint; Store the MO data; Cancel the UE; Stop providing the radio access to the UE; Obtain the feeder link of the terrestrial network; as well as The MO data is forwarded to the at least one remote endpoint via the terrestrial network.

13. The apparatus of claim 12, wherein the service link supports the radio access using 4G LTE, 5G NR or a future 6G standard, wherein the SV includes a radio access network (RAN) and a core network (CN).

14. The apparatus of claim 13, wherein when the serving link supports the 5G NR, in order to register the UE, the at least one processor is configured to cause the SV to perform non-access stratum (NAS) registration of the UE, and in order to deregister the UE, the at least one processor is configured to cause the SV to perform NAS deregistration of the UE, wherein when the serving link supports the 4G LTE, in order to register the UE, the at least one processor is configured to cause the SV to perform NAS attachment of the UE, and in order to deregister the UE, the at least one processor is configured to cause the SV to perform NAS detachment of the UE.

15. The apparatus of claim 12, wherein the SV includes an endpoint proxy function for the at least one remote endpoint, and the at least one processor is configured to cause the endpoint proxy function to simulate the behavior of the at least one remote endpoint from the perspective of the UE, the endpoint proxy function receiving and storing the MO data.

16. The apparatus of claim 15, wherein, in order to simulate the behavior of the at least one remote endpoint from the perspective of the UE, the at least one processor is configured to cause the SV to return at least one of the following: The application-level response to the pre-configured UE; In the response from the transmission level to the UE; or It has both.

17. The apparatus of claim 12, wherein the MO data comprises at least one of the following: MO Short Message Service (SMS) messages; Media data of Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-Internet Protocol (non-IP), Internet Protocol (IP), User Datagram Protocol (UDP) / IP, or Transmission Control Protocol (TCP) / IP; Internet search; Email inquiry; or A combination of the above items.

18. The apparatus of claim 12, wherein, in order to forward the MO data to the at least one remote endpoint via the terrestrial network, the at least one processor is configured to cause the SV to forward the MO data to a terrestrial server for forwarding to the at least one remote endpoint via the terrestrial network.

19. The apparatus of claim 12, wherein the at least one processor is further configured to cause the SV: The mobile station terminates (MT) data via the terrestrial network, the MT data being initiated by the at least one remote endpoint; Store the MT data; as well as The MT data will be transmitted to the UE at a later time using the service link.

20. The apparatus of claim 19, wherein the MT data comprises at least one of the following: MT Short Message Service (SMS) messages; Media data of Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-Internet Protocol (non-IP), Internet Protocol (IP), User Datagram Protocol (UDP) / IP, or Transmission Control Protocol (TCP) / IP; Internet query response; email; or A combination of the above items.

21. The apparatus of claim 19, wherein the at least one processor is configured to cause the SV to receive the MT data from a ground-based server, wherein the MT data is initiated by the at least one remote endpoint.

22. The apparatus of claim 12, wherein the at least one processor is further configured to cause the SV to broadcast to the UE an indication that the SV is operating in store-and-forward mode, wherein the indication enables the UE to access the SV using the serving link.

23. The apparatus of claim 22, wherein the SV has subscription information for the UE, and the subscription information for the UE allows the UE to access the SV when the SV is operating in the store-and-forward mode.

24. An apparatus for wireless communication performed by a server, the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to enable the server to: Mobile station initiated (MO) data is received from a spacecraft (SV) having a feeder link to the server, the MO data being intended for at least one remote endpoint, wherein the MO data is transmitted by a user equipment (UE) to the SV using a serving link when the SV does not have the feeder link to the server, wherein the UE registers with the SV without assistance from the server and subsequently deregisters from the SV. The MO data is forwarded to the at least one remote endpoint via the network.

25. The apparatus of claim 24, wherein the MO data comprises at least one of the following: MO Short Message Service (SMS) messages; Media data of Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MO data transmitted using non-Internet Protocol (non-IP), Internet Protocol (IP), User Datagram Protocol (UDP) / IP, or Transmission Control Protocol (TCP) / IP; Internet search; Email inquiry; or A combination of the above items.

26. The apparatus of claim 24, wherein the at least one processor is configured to cause the server to access the network using a first option, a second option, or a third option, wherein: For the first option, the at least one processor is configured to attach the server to the network as an NTN gateway, and the network includes a RAN and a CN for radio access types; For the second option, the at least one processor is configured to attach the server as a base station to the network, and the network includes the CN for the wireless access type; and For the third option, the server includes the network or a part of the network, wherein the server includes a UE proxy function for the UE, wherein the at least one processor is configured to cause the UE proxy function to simulate the behavior of the UE from a first angle of the at least one remote endpoint and a second angle of the network, wherein the MO data is received by the UE proxy function from the SV, and wherein the at least one processor is configured to cause the server to forward the MO data from the UE proxy function to the at least one remote endpoint.

27. The apparatus of claim 26, wherein, in order to simulate the behavior of the UE from the first angle of the at least one remote endpoint, the at least one processor is configured to cause the server to transmit at least one of the following: Pre-configured messages at the application level to the at least one remote endpoint; In the response at the transmission level to the at least one remote endpoint; or It has both.

28. The apparatus of claim 26, wherein, in order to simulate the behavior of the UE from the second perspective of the network, the at least one processor is configured to cause the server to perform: For either the first or second option, when the radio access type is 5G NR, the UE registers with the network's NAS; or For either the first or second option, when the wireless access type is 4G LTE, the UE is attached to the NAS of the network.

29. The apparatus of claim 28, wherein, in order to simulate the behavior of the UE from the second perspective of the network, the at least one processor is configured to cause the server to keep the UE in a persistent connection state from the second perspective of the network.

30. The apparatus of claim 24, wherein the at least one processor is further configured to cause the server to: Receive mobile station terminated (MT) data via the network, the MT data being initiated by the at least one remote endpoint; Store the MT data; as well as The MT data is transmitted to the second SV using a second feeder link, and then forwarded to the UE using a second serving link at a later time, wherein the MT data includes at least one of the following: MT Short Message Service (SMS) messages; Media data of Session Initiation Protocol (SIP), wherein the media data includes at least one of voice, text, or video; MT data transmitted using non-Internet Protocol (non-IP), Internet Protocol (IP), User Datagram Protocol (UDP) / IP, or Transmission Control Protocol (TCP) / IP; Internet query response; Email; or A combination of the above items.

Images