Method for performing store-and-forward

Abstract

Embodiments of the present disclosure provide a method for performing communication by a first satellite. The method includes the steps of receiving information indicating that a UE supports S&F from an AMF and storing the information in a UE context, receiving data from the UE and storing it, and maintaining the UE context.

Description

Technical Field

[0001] This manual relates to mobile communications. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology designed to enable high-speed packet communication. Numerous proposals have been put forward for LTE objectives, including those aimed at reducing costs for users and providers, improving quality of service, and expanding and improving coverage and system capacity. As upper-layer requirements, 3GPP LTE needs to reduce cost per bit, increase service availability, allow flexible use of frequency bands, have a simple architecture, open interfaces, and sufficient power consumption for terminals.

[0003] Requirements and specifications for New Radio (NR) systems have begun to be developed within the International Telecommunication Union (ITU) and 3GPP. 3GPP must identify and develop technical components that will be successfully standardized in the new RAT to meet both pressing market demands and the longer-term requirements outlined in the ITU Radiocommunication Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Furthermore, NR should be able to utilize any spectrum band within at least 100 GHz that can be used for wireless communication even in the more distant future.

[0004] The goal of NR is to address all use cases, requirements, and deployment scenarios with a single technology framework, including enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), ultra-reliable and low-latency communications (URLLC), and more. NR should be inherently backward compatible.

[0005] The method for performing S&F operations when the satellite serving the terminal changes is a problem. Summary of the Invention

[0006] Technical solution

[0007] The satellite maintains the UE context and transmits MO data when it later connects to the ground station. Attached Figure Description

[0008] Figure 1 An example of a communication system that applies the implementation of this disclosure is shown.

[0009] Figure 2 An example of a wireless device that applies an implementation of the present disclosure is shown.

[0010] Figure 3 An example of a UE that applies the implementation of this disclosure is shown.

[0011] Figure 4 This is a block diagram of the next-generation cellular network.

[0012] Figure 5An example 5G system architecture is illustrated, showing an implementation method that can be applied to this specification.

[0013] Figure 6 and Figure 7 An example of a registration process applying the implementation of this disclosure is shown.

[0014] Figure 8 Examples of basic satellite operations are shown.

[0015] Figure 9 An example of S&F satellite operation is shown.

[0016] Figure 10 An example of the process of transitioning from an RRC inactive state to an RRC connected state is shown.

[0017] Figure 11 An example of the situation at time T1 is given.

[0018] Figure 12 An example of the situation at time T2 is given.

[0019] Figure 13 An example of the situation at time T3 is given.

[0020] Figure 14 An example of the Xn setting process according to an embodiment of this specification is illustrated.

[0021] Figure 15 An example of an NG setup process according to an embodiment of this specification is illustrated.

[0022] Figure 16 An example of a registration process according to an embodiment of this specification is illustrated.

[0023] Figure 17 and Figure 18 An example of the S&F process according to an embodiment of this specification is illustrated.

[0024] Figure 19 The process of the first satellite disclosed in this specification is shown.

[0025] Figure 20 The AMF process disclosed in this specification is shown.

[0026] Figure 21 The procedure of the UE disclosed in this specification is shown. Detailed Implementation

[0027] The following technologies, devices, and systems can be applied to a variety of wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using radio technologies such as Global System for Mobile Communications (GSM), Universal Packet Radio Service (GPRS), or Enhanced Data Rate Evolution of GSM (EDGE). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of the Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in DL and SC-FDMA in UL. The evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0028] For ease of description, the implementation of this disclosure is primarily described with respect to 3GPP-based wireless communication systems. However, the technical features of this disclosure are not limited thereto. For example, although the following detailed description is given of mobile communication systems corresponding to 3GPP-based wireless communication systems, the aspects of this disclosure, which are not limited to 3GPP-based wireless communication systems, are applicable to other mobile communication systems.

[0029] For any terms and techniques used in this disclosure that are not specifically described in this disclosure, please refer to previously published wireless communication standards documents.

[0030] In this disclosure, "A or B" may mean "A only", "B only", or "both A and B". In other words, "A or B" in this disclosure may be interpreted as "A and / or B". For example, "A, B or C" in this disclosure may mean "A only", "B only", "C only", or "any combination of A, B and C".

[0031] In this disclosure, a forward slash ( / ) or a comma (,) can mean "and / or". For example, "A / B" can mean "A and / or B". Therefore, "A / B" can mean "A only", "B only", or "both A and B". For example, "A, B, C" can mean "A, B, or C".

[0032] In this disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". Furthermore, the expressions "at least one of A or B" or "at least one of A and / or B" in this disclosure may be interpreted as the same as "at least one of A and B".

[0033] Additionally, in the disclosure, "at least one of A, B, and C" may mean "A only", "B only", "C only" or "any combination of A, B, and C". Furthermore, "at least one of A, B, or C" or "at least one of A, B, and / or C" may mean "at least one of A, B, and C".

[0034] Furthermore, the brackets used in this disclosure may mean "for example". Specifically, when shown as "Control Information (PDCCH)", "PDCCH" can be cited as an example of "Control Information". In other words, "Control Information" in this disclosure is not limited to "PDCCH", and "PDCCH" can be cited as an example of "Control Information". Additionally, even when shown as "Control Information (i.e., PDCCH)", "PDCCH" can be cited as an example of "Control Information".

[0035] The technical features described individually in one of the accompanying drawings of this disclosure may be implemented individually or simultaneously.

[0036] Not limited thereto, the various descriptions, functions, processes, suggestions, methods and / or operation flowcharts disclosed herein can be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0037] In the following description, this disclosure will be described in more detail with reference to the accompanying drawings. Unless otherwise indicated, the same reference numerals in the following drawings and / or description may denote the same and / or corresponding hardware blocks, software blocks and / or functional blocks.

[0038] Figure 1 An example of a communication system that applies the implementation of this disclosure is shown.

[0039] Figure 1 The 5G use cases shown are merely illustrative, and the technical features of this disclosure can be applied to... Figure 1 Other 5G use cases not shown.

[0040] The three main requirement categories for 5G include (1) Enhanced Mobile Broadband (eMBB), (2) Massive Machine-Type Communications (mMTC), and (3) Ultra-Reliable and Low-Latency Communications (URLLC).

[0041] Reference Figure 1 The communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Although Figure 1 An example of a 5G network as a network of communication system 1 is shown, but the implementation of this disclosure is not limited to 5G systems and can be applied to future communication systems other than 5G systems.

[0042] BS 200 and network 300 can be implemented as wireless devices, and a particular wireless device can operate as a BS / network node relative to other wireless devices.

[0043] Wireless devices 100a to 100f represent devices that perform communication using radio access technology (RAT) (e.g., 5G New RAT (NR) or LTE) and may be referred to as communication / radio / 5G devices. Wireless devices 100a to 100f may include (but are not limited to) robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, IoT devices 100f, and artificial intelligence (AI) devices / servers 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices and may be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include televisions, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0044] In this disclosure, wireless devices 100a to 100f may be referred to as user equipment (UE). For example, a UE may include a cellular phone, smartphone, laptop computer, digital broadcasting terminal, personal digital assistant (PDA), portable multimedia player (PMP), navigation system, Slate PC, tablet PC, ultrabook, vehicle, vehicle with autonomous driving capability, connected car, UAV, AI module, robot, AR device, VR device, MR device, holographic device, public safety device, MTC device, IoT device, medical device, fintech device (or financial device), security device, weather / environment device, device related to 5G services, or device related to the Fourth Industrial Revolution.

[0045] For example, a UAV can be an aircraft that flies wirelessly via control signals without a crew.

[0046] For example, a VR device may include means for realizing objects or backgrounds in a virtual world. For example, an AR device may include means for connecting objects or backgrounds in a virtual world to objects or backgrounds in a real world. For example, a MR device may include means for incorporating objects or backgrounds in a virtual world into objects or backgrounds in a real world. For example, a holographic device may include means for recording and reproducing stereoscopic information using the light interference phenomenon produced when two lasers meet, known as holography, to create a 360-degree stereoscopic image.

[0047] For example, public safety devices may include image relay devices or image devices that can be worn on the user's body.

[0048] For example, MTC devices and IoT devices can be devices that do not require direct human intervention or manipulation. For example, MTC devices and IoT devices can include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.

[0049] For example, a medical device can be a device for the purpose of diagnosing, treating, alleviating, treating, or preventing disease. For example, a medical device can be a device for the purpose of diagnosing, treating, alleviating, or correcting injury or trauma. For example, a medical device can be a device for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device can be a device for regulating pregnancy. For example, a medical device may include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for surgery.

[0050] For example, a safety device can be a device installed to prevent potential dangers and maintain safety. For example, a safety device can be a camera, closed-circuit television (CCTV), a recorder, or a black box.

[0051] For example, a fintech device can be a device capable of providing financial services such as mobile payments. For instance, a fintech device may include a payment device or a point-of-sale (POS) system.

[0052] For example, weather / environment devices may include devices for monitoring or predicting weather / environment.

[0053] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using 3G, 4G (e.g., LTE), 5G (e.g., NR), and super 5G networks. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can also perform direct communication with each other without going through BS 200 / network 300 (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0054] Wireless communication / connections 150a, 150b, and 150c can be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS 200 and / or between BS200. In this document, wireless communication / connections can be established via various RATs (e.g., 5G NR), such as uplink / downlink communication 150a, sidelink communication or device-to-device (D2D) communication 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc. Wireless devices 100a to 100f and BS200 / wireless devices 100a to 100f can send / receive radio signals to each other via wireless communication / connections 150a, 150b, and 150c. For example, wireless communication / connections 150a, 150b, and 150c can send / receive signals via various physical channels. Therefore, at least a portion of the various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes used for transmitting / receiving radio signals can be performed based on various proposals of this disclosure.

[0055] AI refers to the field of studying artificial intelligence or the methods that can create it, while machine learning refers to the field that defines the various problems solved within AI and the methods for solving them. Machine learning is also defined as algorithms that improve the performance of a task through stable experience with that task.

[0056] A robot is a machine that automatically processes or operates a given task through its own capabilities. In particular, robots capable of recognizing their environment and autonomously determining the actions they must perform can be called intelligent robots. Depending on their purpose or field of use, robots can be classified as industrial, medical, domestic, military, etc. Robots can perform various physical operations, such as moving their joints using actuators or motors. Mobile robots also include driven wheels, brakes, propellers, etc., allowing them to move on the ground or fly in the air.

[0057] Autonomous driving refers to the technology of driving itself, and autonomous vehicles refer to vehicles driven without user control or with minimal user control. For example, autonomous driving can include maintaining a lane while in motion, automatically adjusting speed (e.g., adaptive cruise control), driving automatically along a set route, and automatically setting a route when a destination is set. Vehicles encompass vehicles equipped with internal combustion engines, hybrid vehicles equipped with both internal combustion engines and electric motors, and electric vehicles equipped with electric motors, and can include trains, motorcycles, and automobiles. Autonomous vehicles can be considered as robots with autonomous driving capabilities.

[0058] Extended reality is collectively referred to as VR, AR, and MR. VR technology provides real-world objects and backgrounds solely through computer graphics (CG) images. AR technology provides virtual CG images on top of real-world object images. MR technology is a CG technique that combines virtual objects into the real world. MR technology is similar to AR technology in that it displays real and virtual objects together. However, the difference lies in that in AR technology, virtual objects serve as a supplementary form to real objects, while in MR technology, virtual and real objects are treated as equal entities.

[0059] NR supports multiple parameter sets (and / or multiple subcarrier spacings (SCS)) to support a variety of 5G services. For example, a 15kHz SCS can support wide areas in traditional cellular bands, while a 30kHz / 60kHz SCS can support dense urban areas, lower latency, and wider carrier bandwidth. A 60kHz or higher SCS can support bandwidths greater than 24.25GHz to overcome phase noise.

[0060] NR bands can be defined as two types of frequency ranges, namely FR1 and FR2. The numerical values ​​of the frequency ranges can vary. For example, the two types of frequency ranges (FR1 and FR2) can be shown in Table 1 below. For ease of explanation, in the frequency ranges used in NR systems, FR1 can mean "the range below 6 GHz" and FR2 can mean "the range above 6 GHz" and can be referred to as millimeter wave (mmW).

[0061] [Table 1]

[0062] As mentioned above, the frequency range of the NR system can be varied. For example, as shown in Table 2 below, FR1 may include a frequency band from 410MHz to 7125MHz. That is, FR1 may include a frequency band of 6GHz (or 5850MHz, 5900MHz, 5925MHz, etc.) or higher. For example, the 6GHz (or 5850MHz, 5900MHz, 5925MHz, etc.) or higher frequency band included in FR1 may include unlicensed frequency bands. Unlicensed frequency bands can be used for various purposes, such as for vehicle communications (e.g., autonomous driving).

[0063] [Table 2]

[0064] Here, the radio communication technologies implemented in the wireless devices of this disclosure may include narrowband Internet of Things (NB-IoT) technologies for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology, implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the names mentioned above. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices of this disclosure may be based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and referred to by various names such as enhanced machine-type communication (eMTC). For example, LTE-M technology may be implemented in at least one of various specifications such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices of this disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN, which take into account low-power communication, and may not be limited to the names mentioned above. For example, ZigBee technology may generate personal area networks (PANs) associated with small / low-power digital communication based on various specifications such as IEEE 802.15.4, and may be referred to by various names.

[0065] Figure 2 An example of a wireless device that applies an implementation of the present disclosure is shown.

[0066] exist Figure 2 In this context, the first wireless device 100 and / or the second wireless device 200 may be implemented in various forms depending on the usage / service. For example, {the first wireless device 100 and the second wireless device 200} may correspond to... Figure 1At least one of {wireless devices 100a to 100f and BS 200}, {wireless devices 100a to 100f and wireless devices 100a to 100f} and / or {BS 200 and BS 200}. The first wireless device 100 and / or the second wireless device 200 may be configured from various elements, devices / components and / or modules.

[0067] The first wireless device 100 may include at least one transceiver (e.g., transceiver 106), at least one processing chip (e.g., processing chip 101), and / or one or more antennas 108.

[0068] The processing chip 101 may include at least one processor (e.g., processor 102) and at least one memory (e.g., memory 104). Additionally and / or alternatively, the memory 104 may be located outside the processing chip 101.

[0069] Processor 102 can control memory 104 and / or transceiver 106, and can be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, processor 102 can process information in memory 104 to generate first information / signal, and then transmit a radio signal including the first information / signal via transceiver 106. Processor 102 can receive a radio signal including a second information / signal via transceiver 106, and then store the information obtained by processing the second information / signal in memory 104.

[0070] Memory 104 may be operatively connected to processor 102. Memory 104 may store various types of information and / or instructions. Memory 104 may store firmware and / or software code 105 that implements code, commands, and / or command sets, which, when executed by processor 102, perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 105 may implement instructions that, when executed by processor 102, perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 105 may control processor 102 to execute one or more protocols. For example, firmware and / or software code 105 may control processor 102 to execute one or more layers of a radio interface protocol.

[0071] In this document, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used interchangeably with radio frequency (RF) units. In this disclosure, first wireless device 100 may represent a communication modem / circuit / chip.

[0072] The second wireless device 200 may include at least one transceiver (e.g., transceiver 206), at least one processing chip (e.g., processing chip 201), and / or one or more antennas 208.

[0073] The processing chip 201 may include at least one processor (e.g., processor 202) and at least one memory (e.g., memory 204). Additionally and / or alternatively, the memory 204 may be located outside the processing chip 201.

[0074] Processor 202 can control memory 204 and / or transceiver 206, and can be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, processor 202 can process information in memory 204 to generate third information / signal, and then transmit a radio signal including the third information / signal via transceiver 206. Processor 202 can receive a radio signal including a fourth information / signal via transceiver 106, and then store the information obtained by processing the fourth information / signal in memory 204.

[0075] Memory 204 may be operatively connected to processor 202. Memory 204 may store various types of information and / or instructions. Memory 204 may store firmware and / or software code 205 that implements code, commands, and / or command sets, which, when executed by processor 202, perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 205 may implement instructions that, when executed by processor 202, perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 205 may control processor 202 to execute one or more protocols. For example, firmware and / or software code 205 may control processor 202 to execute one or more layers of a radio interface protocol.

[0076] In this document, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used interchangeably with an RF unit. In this disclosure, second wireless device 200 may represent a communication modem / circuit / chip.

[0077] The hardware elements of wireless devices 100 and 200 will be described in more detail below. One or more protocol layers may be implemented by one or more processors 102 and 202, but are not limited thereto. For example, these one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as the Physical (PHY) layer, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Service Data Adaptation Protocol (SDAP) layer). These one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs), one or more Service Data Units (SDUs), messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information, according to the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure, and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive signals (e.g., baseband signals) from the one or more transceivers 106 and 206, and acquire PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure.

[0078] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. These one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field-programmable gate arrays (FPGAs) may be included in these one or more processors 102 and 202. For example, these one or more processors 102 and 202 may be configured as a collection of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphics processing units (GPUs), and memory control processors.

[0079] One or more memories 104, 204 may be associated with one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. These memories 104, 204 may include random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. These memories 104, 204 may be located internally and / or externally to one or more processors 102, 202. Furthermore, these memories 104, 204 may be coupled to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0080] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as described herein, to one or more other devices. The one or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as described herein, from one or more other devices. For example, the one or more transceivers 106, 206 may be associated with the one or more processors 102, 202 and may transmit and receive wireless signals. For example, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to transmit user data, control information, wireless signals, etc., to one or more other devices. Furthermore, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to receive user data, control information, wireless signals, etc., from one or more other devices.

[0081] One or more transceivers 106, 206 may be associated with one or more antennas 108, 208. Additionally and / or alternatively, the one or more transceivers 106, 206 may include one or more antennas 108, 208. The one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, features, processes, suggestions, methods, and / or operation flowcharts disclosed herein via the one or more antennas 108, 208. As used herein, the one or more antennas 108, 208 may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0082] One or more transceivers 106, 206 can convert received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals so that the received user data, control information, radio signals / channels, etc., can be processed by the one or more processors 102, 202. The one or more transceivers 106, 206 can use the one or more processors 102, 202 to convert the processed user data, control information, radio signals / channels, etc., from baseband signals to RF band signals. For this purpose, the one or more transceivers 106, 206 may include (analog) oscillators and / or filters. For example, the one or more transceivers 106, 206 can, under the control of the one or more processors 102, 202, upconvert OFDM baseband signals to OFDM signals via (analog) oscillators and / or filters, and transmit the upconverted OFDM signals at a carrier frequency. One or more transceivers 106, 206 can receive OFDM signals at a carrier frequency and, under the control of one or more processors 102, 202, down-convert the OFDM signals to OFDM baseband signals via (analog) oscillators and / or filters.

[0083] although Figure 2 As not shown, wireless devices 100 and 200 may also include additional components. Additional component 140 may be configured differently depending on the type of wireless devices 100 and 200. For example, additional component 140 may include at least one of a power unit / battery, input / output (I / O) devices (e.g., audio I / O ports, video I / O ports), drive devices, and computing devices. Additional component 140 may be coupled to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0084] In the implementation of this disclosure, the UE can operate as a transmitting device in the uplink (UL) and as a receiving device in the downlink (DL). In the implementation of this disclosure, the BS can operate as a receiving device in the UL and as a transmitting device in the DL. For ease of description, it is primarily assumed below that the first wireless device 100 acts as the UE and the second wireless device 200 acts as the BS. For example, a processor 102 connected to, installed on, or started in the first wireless device 100 may be adapted to perform UE behavior according to the implementation of this disclosure or to control the transceiver 106 to perform UE behavior according to the implementation of this disclosure. A processor 202 connected to, installed on, or started in the second wireless device 200 may be adapted to perform BS behavior according to the implementation of this disclosure or to control the transceiver 206 to perform BS behavior according to the implementation of this disclosure.

[0085] In this disclosure, BS is also referred to as Node B (NB), eNode B (eNB), or gNB.

[0086] Figure 3 An example of a UE that applies the implementation of this disclosure is shown.

[0087] Reference Figure 3 UE 100 can correspond to Figure 2 The first wireless device 100.

[0088] The UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 141, a battery 142, a display 143, a keypad 144, a subscriber identification module (SIM) card 145, a speaker 146, and a microphone 147.

[0089] Processor 102 may be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. Processor 102 may be adapted to control one or more other components of UE 100 to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. A layer of the radio interface protocol may be implemented in processor 102. Processor 102 may include an ASIC, other chipsets, logic circuitry, and / or data processing means. Processor 102 may be an application processor. Processor 102 may include at least one of a DSP, CPU, GPU, and modem (modulator and demodulator). Examples of processor 102 can be found in the SNAPDRAGON manufactured by Qualcomm®. TM Series processors, Samsung® manufactured EXYNOS TMSeries processors, a range of processors manufactured by Apple®, and HELIO manufactured by MediaTek® TM Series processors, Intel® manufactured ATOM TM This series of processors or the corresponding next-generation processors.

[0090] Memory 104 is operatively coupled to processor 102 and stores various information to operate processor 102. Memory 104 may include ROM, RAM, flash memory, memory card, storage medium, and / or other storage devices. When the implementation is software-based, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein. Modules may be stored in memory 104 and executed by processor 102. Memory 104 may be implemented within or outside processor 102, in which case it may be communicatively coupled to processor 102 via various means known in the art.

[0091] Transceiver 106 is operatively coupled to processor 102 and transmits and / or receives radio signals. Transceiver 106 includes a transmitter and a receiver. Transceiver 106 may include baseband circuitry for processing radio frequency signals. Transceiver 106 controls one or more antennas 108 to transmit and / or receive radio signals.

[0092] The power management module 141 manages the power of the processor 102 and / or transceiver 106. The battery 142 supplies power to the power management module 141.

[0093] Display 143 outputs the results processed by processor 102. Keypad 144 receives inputs to be used by processor 102. Keypad 144 can be displayed on display 143.

[0094] The SIM card 145 is an integrated circuit designed to securely store the International Mobile Subscriber Identity (IMSI) number and its associated key used for identifying and authenticating subscribers on mobile devices such as mobile phones and computers. Contact information can also be stored on many SIM cards.

[0095] Speaker 146 outputs the sound-related results processed by processor 102. Microphone 147 receives the sound-related input to be used by processor 102.

[0096] Figure 4 This is a block diagram of the next-generation cellular network.

[0097] The 5G core (5GC) can include various components, some of which are in Figure 5The diagram shows functions such as Access and Mobility Management Function (AMF) (410), Session Management Function (SMF) (420), Policy Control Function (PCF) (430), User Plane Function (UPF) (440), Application Function (AF) (450), Unified Data Management (UDM) (460) and Non-3GPP Interoperability Function (N3IWF) (490).

[0098] UE 100 connects to the data network via UPF 440 through a next-generation radio access network (NG-RAN) including gNB 20.

[0099] Data services can also be provided to UE 100 via untrusted non-3GPP access (such as wireless local area network (WLAN)). To connect the aforementioned non-3GPP access to the core network, an N3IWF 490 can be deployed.

[0100] The N3IWF 490 shown performs the function of managing interoperability between non-3GPP access and 5G systems. When UE 100 is associated with a non-3GPP access (e.g., WiFi, also known as IEEE 801.11), UE 100 can associate with a 5G system via the N3IWF 490. The N3IWF 490 communicates with the AMF 410 for control signaling and with the UPF 440 via the N3 interface for data transmission.

[0101] The AMF 410 shown can manage access and mobility in 5G systems. The AMF 410 can perform functions for managing Non-Access Stratum (NAS) security. The AMF 410 can perform functions for handling mobility in idle states.

[0102] The UPF 440 shown is a gateway through which user data is sent and received. The UPF node 440 can perform all or part of the user plane functions of a Serving Gateway (S-GW) and Packet Data Network Gateway (P-GW) for fourth-generation mobile communications.

[0103] The UPF 440 acts as a boundary between the Next Generation Radio Access Network (NG-RAN) and the core network, and is an element that maintains the data path between gNB 20 and SMF 420. Additionally, the UPF 440 acts as a mobility anchor when the UE 100 moves across the area served by gNB 20. The UPF 440 can perform PDU processing functions. For mobility within the NG-RAN (Next Generation Radio Access Network as defined in 3GPP Release 15 and later), the UPF can route packets. The UPF 440 can also be used as an anchor for mobility with other 3GPP networks (RANs defined prior to 3GPP Release 15, such as UTRAN, E-UTRAN (Evolved UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network) or GERAN (Global System for Mobile Communications (GSM) / EDGE (Global Evolution Enhanced Data Rate) Radio Access Network). The UPF 440 can correspond to the termination point of the data interface to the data network.

[0104] The PCF 430 shown is a node that controls the operator's policies.

[0105] The AF 450 shown is a server used to provide multiple services to UE 100.

[0106] The UDM 460 shown is a type of server that manages subscriber information, such as the Home Subscriber Server (HSS) in fourth-generation mobile communications. The UDM 460 stores and manages subscriber information in a unified data repository (UDR).

[0107] The SMF 420 shown can perform the function of assigning Internet Protocol (IP) addresses to UEs. The SMF 420 can also control Protocol Data Unit (PDU) sessions.

[0108] For reference purposes, the reference numerals for AMF 410, SMF 420, PCF 430, UPF 440, AF 450, UDM460, N3IWF 490, gNB 20, or UE 100 may be omitted in this document.

[0109] Fifth-generation mobile communication supports multiple parameter sets or subcarrier spacings (SCS) to support a variety of 5G services. For example, a 15kHz SCS supports wide-area coverage in traditional cellular bands; a 30kHz / 60kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidth; and a 60kHz or higher SCS supports bandwidths greater than 24.25GHz to overcome phase noise.

[0110] Figure 5 An example 5G system architecture is illustrated, showing an implementation method that can be applied to this specification.

[0111] The architecture of a 5G system (5GS; 5G system) consists of the following network functions (NFs).

[0112] -AUSF (Authentication Server Functionality)

[0113] -AMF (Access and Mobility Management Function)

[0114] -DN (Data Network), such as carrier services, internet access, or third-party services.

[0115] -USDF (Unstructured Data Storage Function)

[0116] -NEF (Network Open Functionality)

[0117] -I-NEF (middle NEF)

[0118] -NRF (Network Storage Function)

[0119] -NSSF (Network Slice Selection Function)

[0120] -PCF (Policy Control Function)

[0121] -SMF (Session Management Function)

[0122] -UDM (Unified Data Management)

[0123] -UDR (Unified Data Repository)

[0124] -UPF (User Plane Function)

[0125] -UCMF (UE Radio Capability Management Function)

[0126] -AF (Application Function)

[0127] -UE (User Equipment)

[0128] - (R)AN (Radio Access Network)

[0129] -5G-EIR (5G Device Identifier Register)

[0130] -NWDAF (Network Data Analysis Function)

[0131] -CHF (Billing Function)

[0132] In addition, the following network functions can be considered.

[0133] -N3IWF (Non-3GPP interoperability function)

[0134] -TNGF (Trusted Non-3GPP Gateway Function)

[0135] -W-AGF (Wired Access Gateway Function)

[0136] Figure 5 The architecture of a 5G system in a non-roaming scenario is shown using reference points that illustrate how various network functions interact with each other.

[0137] exist Figure 5 For clarity of the point-to-point diagram, UDSF, NEF, and NRF are not described. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0138] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in [the original text]. Figure 5 As shown in the image. For clarity, Figure 5 The connection between NWDAF and other NFs (e.g., PCF) is not shown.

[0139] The 5G system architecture includes the following reference points.

[0140] -N1: Reference point between UE and AMF.

[0141] -N2: (R) Reference point between AN and AMF.

[0142] -N3: (R) Reference point between AN and UPF.

[0143] -N4: Reference point between SMF and UPF.

[0144] -N6: Reference point between UPF and data network.

[0145] -N9: Reference point between two UPFs.

[0146] The following reference points illustrate the interactions that exist between NF services.

[0147] -N5: Reference point between PCF and AF.

[0148] -N7: Reference point between SMF and PCF.

[0149] -N8: Reference point between UDM and AMF.

[0150] -N10: Reference point between UDM and SMF.

[0151] -N11: Reference point between AMF and SMF.

[0152] -N12: Reference point between AMF and AUSF.

[0153] -N13: Reference point between UDM and AUSF.

[0154] -N14: Reference point between the two AMFs.

[0155] -N15: The reference point between the PCF and AMF in non-roaming scenarios, and the reference point between the PCF and AMF of the visited network in roaming scenarios.

[0156] -N16: Reference point between two SMFs (in the case of roaming, between the visiting SMF and the home SMF).

[0157] -N22: Reference point between AMF and NSSF.

[0158] In some cases, it may be necessary to connect two NFs to each other to serve the UE.

[0159] <Registration Process>

[0160] Describe the registration process. Refer to Section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0161] Figure 6 and Figure 7 An example of a registration process applying the implementation of this disclosure is shown.

[0162] The UE needs to register with the network to obtain authorization to receive services, enabling mobility tracking and reachability. The UE initiates the registration process using one of the following registration types: - To the initial registration of 5GS; or - Mobility registration update; or - Periodic registration and updates; or - Urgent registration.

[0163] Figure 6 and Figure 7 The general registration process applies to all of these registration processes, but periodic registration updates do not need to include all the parameters used in other registration cases.

[0164] Figure 6 and Figure 7 The general registration process is also used for 3GPP access when the UE has already registered in a non-3GPP access scenario, and vice versa. Registration in 3GPP access when the UE has already registered in a non-3GPP access scenario may require an AMF change.

[0165] First, description Figure 6 The process.

[0166] (1) Step 1: The UE sends a registration request message to the (R)AN. The registration request message corresponds to the AN message.

[0167] The registration request message may include AN parameters. In the case of NG-RAN, AN parameters include, for example, the 5G SAE Temporary Mobile Subscriber Identity (5G-S-TMSI) or Globally Unique AMF ID (GUAMI), the selected Public Land Mobile Network (PLMN) ID (or PLMN ID and Network Identifier (NID)), and the requested Network Slice Selection Auxiliary Information (NSSAI). AN parameters also include the establishment reason. The establishment reason provides the reason for requesting to establish an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the Access Layer Connection Establishment NSSAI Include Mode parameter.

[0168] The registration request message may include a registration type. The registration type indicates whether the UE wants to perform an initial registration (i.e., the UE is in the RM-DEREGISTERED state), a mobility registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process due to mobility issues or because the UE needs to update its capabilities or protocol parameters or requests a change in the set of network slices it is allowed to use), a periodic registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process because the periodic registration update timer has expired), or an emergency registration (i.e., the UE is in a restricted service state).

[0169] When the UE is performing initial registration, the UE should indicate its UE identifier in the registration request message, as shown below, listed in descending order of preference: i) If the UE has a valid Evolved Packet System (EPS) GUTI, then the 5G Globally Unique Temporary Identifier (5G-GUTI) is mapped from the EPS GUTI.

[0170] ii) The native 5G-GUTI assigned by the PLMN to which the UE is attempting to register (if available); iii) The native 5G-GUTI assigned by the equivalent PLMN to the PLMN the UE is trying to register to (if available); iv) Native 5G-GUTI assigned by any other PLMN (if available); v) Otherwise, the UE should include its Subscriber Hidden Identifier (SUCI) in the registration request message.

[0171] When a UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE should also indicate the native 5G-GUTI as an additional GUTI. If more than one native 5G-GUTI is available, the UE should select the 5G-GUTI from items (ii) to (iv) in the list above in descending order of preference.

[0172] When a UE is performing initial registration using native 5G-GUTI, the UE should indicate the relevant GUAMI information in the AN parameters. When a UE is performing initial registration using its SUCI, the UE should not indicate any GUAMI information in the AN parameters.

[0173] For emergency registration, if the UE does not have a valid 5G-GUTI available, the SUCI should be included; when the UE does not have a Subscriber Permanent Identifier (SUPI) and does not have a valid 5G-GUTI, the Permanent Device Identifier (PEI) should be included. In other cases, the 5G-GUTI is included and it indicates the last serving AMF.

[0174] The registration request message may also include security parameters, PDU session status, etc. Security parameters are used for authentication and integrity protection. PDU session status indicates the previously established PDU sessions in the UE. When the UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the PDU session status indicates the established PDU sessions in the current PLMN of the UE.

[0175] (2) Step 2: (R)AN selects AMF.

[0176] If 5G-S-TMSI or GUAMI is not included, or if 5G-S-TMSI or GUAMI does not indicate a valid AMF, then (R)AN selects the AMF based on (R)AT and the requested NSSAI (if available).

[0177] If the UE is in CM-CONNECTED state, the (R)AN can forward the registration request message to the AMF based on the UE's N2 connection.

[0178] If the (R)AN cannot select an appropriate AMF, it will forward the registration request message to the AMF already configured in the (R)AN to perform AMF selection.

[0179] (3) Step 3: (R)AN sends a registration request message to the new AMF. The registration request message corresponds to the N2 message.

[0180] The registration request message may include all and / or a portion of the information included in the registration request message received from the UE as described in step 1.

[0181] The registration request message may include N2 parameters. When using NG-RAN, the N2 parameters include the selected PLMN ID (or PLMN ID and NID), location information and cell identifier associated with the cell where the UE is camped, and a UE context request indicating that a UE context including security information needs to be set up at NG-RAN. When using NG-RAN, the N2 parameters should also include the reason for registration.

[0182] If the registration type indicated by the UE is periodic registration update, steps 4 to 19 can be omitted.

[0183] (4) Step 4: If the UE’s 5G-GUTI is included in the registration request message and the service AMF has changed since the last registration process, the new AMF can invoke the Namf_Communication_UEContextTransfer service operation on the old AMF, which includes the complete registration request non-access stratum (NAS) message, to request the UE’s SUPI and UE context.

[0184] (5) Step 5: The old AMF can respond to the new AMF by including the UE's SUPI and UE context in the Namf_Communication_UEContextTransfer call.

[0185] (6) Step 6: If the SUCI is not provided by the UE or retrieved from the old AMF, the identity request process can be initiated by sending an identity request message to the UE requesting the SUCI through the new AMF.

[0186] (7) Step 7: The UE can respond with an identity response message that includes the SUCI. The UE obtains the SUCI by using the provisioning public key of the home PLMN (HPLMN).

[0187] (8) Step 8: The new AMF can decide to initiate UE authentication by calling AUSF. In this case, the new AMF selects AUSF based on SUPI or SUCI.

[0188] (9) Step 9: Authentication / security can be established by UE, new AMF, AUSF and / or UDM.

[0189] (10) Step 10: If the AMF has changed, the new AMF can notify the old AMF of the UE's registration completion in the new AMF by calling the Namf_Communication_RegistrationCompleteNotify service operation. If the authentication / security process fails, registration will be rejected, and the new AMF can call the Namf_Communication_RegistrationCompleteNotify service operation with a rejection indication reason code to the old AMF. The old AMF can continue as if it had never received the UE context delivery service operation.

[0190] (11) Step 11: If the PEI is not provided by the UE or retrieved from the old AMF, the identity request process can be initiated by sending an identity request message to the UE through the new AMF to retrieve the PEI. The PEI should be transmitted in encrypted form unless the UE performs emergency registration and cannot be authenticated.

[0191] (12) Step 12: Optionally, the new AMF can initiate an ME identity check by calling the N5g-eir_EquipmentIdentityCheck_Get service operation.

[0192] Now, the description is in Figure 6 After the process Figure 7 The process.

[0193] (13) Step 13: If you want to perform step 14 below, the new AMF can select UDM based on SUPI, and then UDM can select UDR instance.

[0194] (14) Step 14: The new AMF can register with the UDM.

[0195] (15) Step 15: The new AMF can select PCF.

[0196] (16) Step 16: The new AMF can optionally perform AM policy association establishment / modification.

[0197] (17) Step 17: The new AMF can send an update / release SM context message to the SMF (e.g., Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext).

[0198] (18) Step 18: If the new AMF and the old AMF are in the same PLMN, the new AMF can send a UE context modification request to N3IWF / TNGF / W-AGF.

[0199] (19) Step 19: N3IWF / TNGF / W-AGF can send a UE context modification response to the new AMF.

[0200] (20) Step 20: After the new AMF receives the response message from N3IWF / TNGF / W-AGF in step 19, the new AMF can register with UDM.

[0201] (21) Step 21: The new AMF sends a registration acceptance message to the UE.

[0202] The new AMF sends a registration acceptance message to the UE, indicating that the registration request has been accepted. If the new AMF allocates a new 5G-GUTI, this 5G-GUTI is included. If the UE is already in RM-REGISTERED state via another access point in the same PLMN, the UE should use the 5G-GUTI received in the registration acceptance message for both registrations. If the registration acceptance message does not include a 5G-GUTI, the UE will also use the 5G-GUTI allocated for the existing registration for the new registration. If the new AMF allocates a new registration area, it should send the registration area to the UE via the registration acceptance message. If the registration acceptance message does not include a registration area, the UE should treat the old registration area as valid. Mobility restrictions are included if they apply to the UE and the registration type is not emergency registration. The new AMF indicates the established PDU session to the UE in the PDU session state. The UE locally removes any internal resources associated with a PDU session not marked as established in the received PDU session state. When a UE connects to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the UE locally removes any internal resources associated with the current PLMN's PDU session that are not marked as established in the received PDU session state. If the PDU session state information is in the registration request message, the new AMF should indicate the PDU session state to the UE.

[0203] The allowed NSSAIs provided in the registration acceptance message are valid within the registered region, and it applies to all PLMNs whose tracking regions are included within the registered region. The mapping of allowed NSSAIs is a mapping from each S-NSSAI of the allowed NSSAIs to the HPLMN S-NSSAIs. The mapping of configured NSSAIs is a mapping from each S-NSSAI of the configured NSSAIs used to serve the PLMN to the HPLMN S-NSSAIs.

[0204] In addition, optionally, the new AMF performs UE policy association establishment.

[0205] (22) Step 22: When the UE successfully updates itself, the UE can send a registration completion message to the new AMF.

[0206] The UE can send a registration completion message to the new AMF to confirm whether a new 5G-GUTI has been allocated.

[0207] (23) Step 23: For registration via 3GPP access, if the new AMF does not release the signaling connection, the new AMF can send the RRC inactivity auxiliary information to the NG-RAN. For registration via non-3GPP access, if the UE is also in the CM-CONNECTED state on 3GPP access, the new AMF can send the RRC inactivity auxiliary information to the NG-RAN.

[0208] (24) Step 24: The new AMF can perform information updates toward the UDM.

[0209] (25) Step 25: The UE can perform network slice-specific authentication and authorization procedures.

[0210] Non-terrestrial networks

[0211] NTN (Non-Terrestrial Network) refers to a network or network segment that uses RF resources installed on a satellite (or UAS platform).

[0212] There are generally two scenarios where NTN provides access to user equipment: transparent payload and regenerative payload.

[0213] NTN is typically characterized by the following elements: - Connect NTN to one or more satellite gateways (sat-gateways) in a public data network.

[0214] - GEO satellites are provided by one or more satellite gateways deployed across satellite target ranges (e.g., regional or continental ranges). It is assumed that a UE in a cell is served by only one satellite gateway.

[0215] - Non-GEO satellites served sequentially by one or more satellite gateways. The system ensures service and feeder link continuity between continuously serving satellite gateways, with sufficient duration for mobility anchoring and handover.

[0216] - Feeder link or radio link between the satellite gateway and the satellite (or UAS platform).

[0217] - Service links or radio links between user equipment and satellites (or UAS platforms).

[0218] - The satellite (or UAS platform) is capable of implementing transparent or regenerative (including on-board processing) payloads. The satellite (or UAS platform) typically generates multiple beams for a service area specified according to the field of view. The coverage area of a beam is usually elliptical. The field of view of the satellite (or UAS platform) depends on the on-board antenna pattern and the minimum elevation angle.

[0219] - Transparent payload: RF filtering, frequency conversion, and amplification. Thus, the waveform signal repeated by the payload is not changed.

[0220] - Regenerative payload: RF filtering, frequency conversion, and amplification, demodulation / decoding, switching, and / or routing, and encoding / modulation. This is effectively equivalent to installing all or part of the base station function (e.g., gNB) on the satellite (or UAS platform).

[0221] - Optionally, an inter-satellite link (ISL) in the case of satellite deployment. This requires a regenerative payload on the satellite. The ISL can operate in the RF frequency or optical band.

[0222] - The user equipment is served by a satellite (or UAS platform) within the target service area.

[0223] In the case of a transparent satellite, the satellite amplifies the signal sent from the ground base station (gNB-NTN gateway) and sends the signal to the terminal. In the case of a regenerative satellite, in addition to signal amplification, functions of the ground base station such as routing, encoding, modulation, decoding, and demodulation are also performed. The NTN terminal has a GPS function and periodically receives position, time, and speed information for the NTN satellite.

[0224] The S&F operations related to communication via satellite are described.

[0225] <S&F (store and forward)>

[0226] In a 5G system capable of satellite access, the S&F (store and forward) satellite operation aims to provide delay-tolerant communication services to UEs belonging to the satellite range and having intermittent / temporary satellite connectivity (e.g., the case where the satellite is not connected via a feeder link or not connected to the ground network via an ISL).

[0227] Figure 8 Examples of basic satellite operations are illustrated.

[0228] Figure 9 Examples of S&F satellite operations are illustrated.

[0229] Figure 8 and Figure 9An example of "S&F satellite operation" is illustrated in contrast to the current assumption of "normal / basic satellite operation" for 5G systems capable of satellite access.

[0230] A service link is the link between the terminal and the satellite, while a feeder link can be the link between the satellite and the ground gateway.

[0231] In order to exchange signaling and data services between a UE with satellite access and a remote terrestrial network in "normal / basic satellite operation" mode, both the serving link and the feeder link must be active simultaneously. Therefore, at the point in time when the UE interacts with the satellite via the serving link, there is a continuous end-to-end connection path between the UE, the satellite, and the terrestrial network.

[0232] In contrast, in the "S&F Satellite Operation" mode, the end-to-end exchange of signaling / data services is now handled as a combination of two steps that differ in time (Step A and Step B). In Step A, signaling / data exchange between the UE and the satellite is performed. This operation can be performed even if the satellite is not simultaneously connected to the terrestrial network (e.g., the satellite can operate a serving link without an active feeder link connection). In Step B, a connection is established between the satellite and the terrestrial network, enabling communication between them. Therefore, the satellite transitions from being connected to the UE in Step A to being connected to the terrestrial network in Step B.

[0233] The concept of “S&F” services is widely used in the fields of latency-tolerant and interruption-tolerant networks. In the 3GPP context, the service that can be assimilated into S&F services is SMS, in which case an end-to-end connection between endpoints is not required (e.g., one endpoint could be a UE, and the other could be an application server). However, a connection is only needed between the endpoints and the SMSC, which acts as an intermediate node responsible for storage and dependencies.

[0234] Support for S&F satellite operations is particularly well-suited for using NGSO satellites to provide latency-tolerant / non-real-time satellite services.

[0235] The transparent payload and the regenerated payload are as follows: - Transparent payload: Electromagnetic waves transmitted from the Earth's surface are converted into electrical signals by the satellite receiving antenna, and then filtered by the channel and amplified by a low-noise amplifier (LNA). The signal is then frequency-converted. A high-power amplifier (HPA) finally transmits the signal to the transmitting antenna to generate reproduced electromagnetic waves directed toward the Earth's surface where the receiving station is located.

[0236] - Regenerated Payload: An Onboard Processor (OBP) is inserted between the LNA and HPA. This OBP translates the air interface between the uplink (from Earth to satellite) and downlink (from satellite to Earth). This allows for the correction of erroneous bits or packets before retransmission or for routing packets between beams. Ultimately, thanks to the OBP (which includes all the functions connected to the gNB CU or DU or CN), all network functions can be implemented at the expense of power and quality.

[0237] To support S&F functionality, regenerable satellites (satellites capable of acting as ground base stations) may be needed, rather than transparent satellites that simply relay signals from terminals.

[0238] When the terminal connects to 5GC via satellite and then the satellite (or the terminal) moves and leaves the satellite's coverage area, the terminal transitions to the CM-IDLE (RRC_IDLE) state. Subsequently, when the terminal enters the coverage area of ​​the same satellite or another satellite, it must transition to the CM-CONNECTED (RRC_CONNECTED) state to send and receive signaling and data from the satellite.

[0239] When only NG-RAN is installed on the satellite base station without any additional core network functions, the RRC_INACTIVE mode (RRC inactive state) can be used by the terminal to maintain the CM-CONNECTED state for communication.

[0240] While maintaining the CM-CONNECTED state with the core network, the terminal can use the RRC_INACTIVE mode, in which the base station manages the terminal's mobility. Then, when there is no data transmission / reception for the terminal, the terminal operates in the "CM-CONNECTED with RRC_INACTIVE" mode, and when there is data transmission / reception, the terminal can switch to RRC-CONNECTED (RRC connected state) and operate in the RRC-CONNECTED (RRC connected state) mode.

[0241] Figure 10 An example of the process of transitioning from an RRC inactive state to an RRC connected state is shown.

[0242] In a typical terrestrial network, when a terminal in an RRC inactive state establishes an RRC connection with a new base station, the terminal includes the Inactive Radio Network Temporary Identifier (I-RNTI) information assigned from the base station that last served the terminal when sending an RRC Resume Request.

[0243] The new base station receiving the RRCreumeRequest retrieves the UE context information from the base station that last served the corresponding terminal, based on the base station ID included in the I-RNTI.

[0244] The new base station sends a "RETRIEVE UE CONTEXT REQUEST" to request the UE context from the previous serving base station. Then, the previous serving base station sends a "RETRIEVE UE CONTEXT RESPONSE" containing the UE context to the new base station.

[0245] Based on this, the new base station sends RRCResume to the terminal, and the terminal switches to RRC connection state.

[0246] After the new base station retrieves the UE context from the previous serving base station, the new base station sends a UE context release message. Then, the previous serving base station deletes the UE context.

[0247] Figure 11 An example of the situation at time T1 is given.

[0248] Figure 12 An example of the situation at time T2 is given.

[0249] Figure 13 An example of the situation at time T3 is given.

[0250] It can perform S&F operations using the RRC inactive state.

[0251] For example, the following operations can be performed at time T1: - The terminal can establish an RRC connection with satellite A through initial registration.

[0252] - The terminal can establish a PDU session for data transmission.

[0253] - The terminal can send uplink MO (mobile station initiated) data.

[0254] - If satellite A is configured to buffer data, it can buffer data until it moves to a transmittable position using a direct feed link, instead of immediately transmitting data to the AMF. After this, the terminal can enter the RRC_INACTIVE state.

[0255] For example, the following operations can be performed at time T2: - The satellite (or terminal) can move, and the terminal can move out of the coverage area of ​​satellite A.

[0256] The terminal can connect to satellite B and perform periodic registration. To do this, the terminal can make an RRC recovery request. Based on this, satellite B can retrieve the UE context from satellite A, which stores the UE context. The terminal can then transition to the RRC_CONNECTED state and perform the registration process.

[0257] Satellite B sends a message to Satellite A to delete the UE context via a UE context release message, based on existing operations. Satellite A then deletes the UE context while it is not yet connected to the ground gateway (base station) and therefore cannot send uplink data from the terminal. The terminal transitions to the RRC_INACTIVE state. Subsequently, at time T3, Satellite A connects to the ground gateway. Because the UE context has been deleted, Satellite A cannot deliver uplink data (e.g., NAS signaling) to the AMF via the ground gateway.

[0258] For S&F operations, when satellite A connects to the ground gateway, satellite A must be able to deliver the terminal's uplink data to the ground gateway.

[0259] In order to perform S&F operations in the RRC inactive state of the terminal, a method is needed to ensure that the UE context is not deleted by satellite A even after the UE context has been sent to satellite B.

[0260] Due to time delays, S&F operations can be used in delay-tolerant data communications. Therefore, since the above method (the method that does not delete the UE context) is only required for terminals performing delay-tolerant data communications, it needs to be distinguished from general terminals.

[0261] This specification presents a method for managing the UE context of satellites used to support S&F operations for terminals and networks.

[0262] The method for managing the UE context of a base station for storage and delivery operations for the proposed satellite may consist of one or more of the following operations / configurations / steps.

[0263] These procedures and / or messages can use traditional procedures / messages, can use extended traditional procedures / messages, or can define and use new procedures / messages.

[0264] In this specification, store and forward (S&F) and store and delivery are used interchangeably.

[0265] In this specification, UE (User Equipment) and terminal are used interchangeably.

[0266] This instruction manual focuses on the content presented.

[0267] In this specification, a satellite may be a regenerated satellite.

[0268] In this specification, it is assumed that the NG-RAN architecture is installed on a satellite.

[0269] In this specification, connection may refer to logical connection (association) and / or physical connection.

[0270] When the satellite serving a terminal is changed, the terminal can establish an RRC connection with the new satellite by registering. This process of establishing an RRC connection can be achieved through an inter-satellite link (ISL). Depending on the implementation method, the base station can relay NAS signals by loading an Xn interface on the ISL. Alternatively, the ISL can be used as a transport layer to directly implement an N2 interface between the satellite and the AMF.

[0271] Through registration, the core network can receive the UE context of the terminal.

[0272] AMF can set a periodic registration timer based on the terminal's satellite coverage information. Based on this, the terminal can perform registration each time a satellite changes.

[0273] In this specification, it is assumed and described that the inter-satellite Xn interface is implemented via ISL, and that each satellite delivers signaling to the AMF via the Xn interface. For this purpose, it is assumed that each satellite has routing information for delivering signaling to the AMF.

[0274] Alternatively, the satellite can directly establish an N2 interface via a multi-hop ISL between the satellite and the AMF.

[0275] Assume there is no mobility of the IoT terminal for S&F operations. Alternatively, even if the terminal has mobility, assume the network (e.g., AMF) can know when the terminal enters satellite coverage based on information about the terminal's mobility.

[0276] Satellites can have inter-satellite Xn interfaces via ISL. Terminals can register and establish PDU sessions via ISL. Terminals can send data via S&F mode.

[0277] The data transmission in this specification may be data transmission via the control plane through the 5GS CIoT optimized operation of the control plane.

[0278] When a terminal delivers data via the control plane in the RRC_CONNECTED state, the satellite NG-RAN cannot know whether the user data is included in the UL NAS transmission message included in the RRC message, and therefore the terminal can include an indication to notify whether the user data is included in the RRC message.

[0279] The satellite can operate in RRC inactive mode (RRC_INACTIVE mode) for a specific terminal. In RRC inactive mode (RRC_INACTIVE mode), the satellite can retrieve the UE context from the NG-RAN that maintains the UE context for the specific terminal. Then, a transition to the RRC connected state is performed. Afterward, the terminal and satellite can send and receive data.

[0280] Figure 14 An example of the Xn setting process according to an embodiment of this specification is illustrated.

[0281] Base station node 1 can send an XN configuration request message to base station node 2. Based on this, base station node 2 can send an XN configuration response message to base station node 1. At this point, the two satellites can exchange the configuration data required for the Xn interface.

[0282] When base station node 1 (satellite) supports S&F operation, base station node 1 can include information about the ability to support S&F operation in the XN setup request message and send it to base station node 2.

[0283] Similarly, when base station node 2 (satellite) supports S&F operation, base station node 2 can include information about the ability to support S&F operation in the XN setup response message and send it to base station node 1.

[0284] Base station node 1 and base station node 2 can know whether each other supports S&F operations.

[0285] To include the above capabilities in the XN setup request (or XN setup response) message, a new IE can be defined. (For example, Serving Cell List NR IE > Serving Cell Information NR IE > Store and Forward Support IE)

[0286] Figure 15 An example of the NG setup process according to the embodiments of this specification is given.

[0287] It can perform the NG setup process between satellites (base stations) and AMF.

[0288] The satellite can send an NG setup request message to the AMF. Based on this, the AMF can send an NG setup response message to the satellite. Through this process, the configuration data required for the NG interface can be exchanged.

[0289] When a satellite supports S&F operations, it can include information about its ability to support S&F operations in the NG setup request message and send it to the AMF.

[0290] When the AMF supports S&F operations, the AMF can include information about its ability to support S&F operations in the NG setup response message and send it to the satellite.

[0291] Satellites and AMF can know whether each other supports S&F operations.

[0292] To include the above capabilities in the NG settings request (or NG settings response) message, a new IE can be defined.

[0293] When both the satellite and the AMF support S&F operation, multiple N2 connections between the satellite and the AMF can be created for terminals that support S&F operation.

[0294] For example, even if there is an N2 connection between the satellite and the AMF for a specific terminal, an additional N2 connection for a specific terminal can be created between the satellite and the AMF.

[0295] Figure 16 An example of a registration process according to an embodiment of this specification is illustrated.

[0296] For the general registration process, you can apply section 4.2.2.2.2 of TS 23.502 v18.2.0 for general registration or... Figures 6 to 7 The content.

[0297] According to the embodiments described in this specification, information indicating support for S&F operation can be sent to the base station (satellite). The base station (satellite) can then add this information to the UE context.

[0298] Step 1. The terminal can be within the coverage area of ​​satellite A.

[0299] The terminal can connect to the terrestrial network (terrestrial gateway and / or core network) via satellite A.

[0300] The terminal can register with the core network via satellite A.

[0301] The terminal can connect to the terrestrial network via ISL between satellite A and satellite B.

[0302] Step 2. The terminal can send a registration request message to the AMF via satellite A to register with the network.

[0303] The terminal can put information indicating whether operation in S&F mode is possible into the 'core network MM capability' of the registration request message and send it to the AMF via satellite A.

[0304] Step 3. You can execute TS 23.502 v18.2.0 (or Figures 6 to 7 Steps 2 to 9 of the general registration process are as follows: 4.2.2.2.2.

[0305] Step 4. In TS 23.502 v18.2.0 (or Figures 6 to 7 In step 9 of the general registration process (4.2.2.2.2), the AMF performs the initial context setup procedure with the NG-RAN. At this time, the AMF can send information indicating that the terminal supports S&F operations to the NG-RAN (Satellite A and Satellite B).

[0306] Step 5. Satellite A can store information in the UE context that it is a terminal that supports S&F operation (operating in S&F mode). This information is sent to the new satellite (or base station) even when the satellite (or base station) is changed.

[0307] Step 6. You can execute TS 23.502 v18.2.0 (or Figures 6 to 7 Steps 10 to 25 of the general registration process (4.2.2.2.2) are as follows. In step 21, the AMF may include information supporting S&F operations in the registration acceptance message and send it to the terminal.

[0308] In the case of S&F, MO (Mobile Station Initiated) data (uplink data) can be delivered using the 'UPF-anchored Mobile Station Initiated Data Transmission in Control Plane CIoT 5GS Optimization' method in TS 23.502v18.2.0 4.24.1, or it can be sent via the general user plane.

[0309] The data buffering described in this specification can be performed by a satellite base station (NG-RAN).

[0310] Satellite A, Satellite B, and AMF can all support S&F operations.

[0311] The implementation method using control plane CIoT 5G optimization is as follows: Terminals that have registered with the network and created a PDU session can send MO data to satellite B. Here, satellite B can be a satellite that is not directly connected to the ground network via a feeder link.

[0312] Satellite B can store MO data from the terminal.

[0313] - Subsequently, when the feeder link between Satellite B and the ground network is established, Satellite B can transmit MO data to the ground network.

[0314] Satellite C can retrieve the UE context for the terminal from Satellite B.

[0315] - All satellites A, B, and C can maintain the UE context without deleting it.

[0316] Even if the satellite serving the terminal is changed, the terminal can still send MO data by connecting to the changed satellite.

[0317] Figure 17 and Figure 18 Examples of S&F processes according to embodiments of this specification are provided.

[0318] Steps 1 to 5, which will be described later, can correspond to Figure 11 T1.

[0319] Steps 6 to 12, which will be described later, can correspond to Figure 12 T2.

[0320] Step 13, which will be described later, can correspond to Figure 13 T3.

[0321] Steps 1 to 2. With Figure 16 Steps 1 through 6 are the same. After this, the terminal can be in the CM-CONNECTED or RRC_CONNECTED state.

[0322] Step 3. The terminal can create a PDU session according to the PDU session establishment procedure in TS 23.502 v18.2.0 4.3.2.2.1. During this procedure, the AMF can determine to use the control plane CIoT 5GS optimization.

[0323] Step 4. If MO data for the terminal exists, the terminal can include the PDU session ID and MO data optimized for control plane CIoT 5GS in the NAS message (UL NAS transmission) and deliver it to satellite A.

[0324] The terminal can send MO data to satellite A. The MO data may include the PDU session ID.

[0325] Step 5. If satellite A currently has no feeder link and the terminal supports S&F operation, then satellite A can store the terminal's MO data.

[0326] Satellite A can confirm whether the terminal supports S&F operations through the UE context. The fact that the terminal supports S&F operations may mean that there is no problem even if the terminal performs communication through S&F operations. For example, this could be a case where the terminal performs latency-tolerant networking.

[0327] Step 6. The terminal can transition to the RRC_INACTIVE state.

[0328] The terminal can transition to the RRC_INACTIVE state if the data (MO data and / or MT data) for the terminal is not present.

[0329] Alternatively, when the terminal is no longer within the coverage area of ​​satellite A (due to the movement of the terminal / satellite), the terminal may switch to the RRC_INACTIVE state.

[0330] (Through movement of the terminal or satellite A) the satellite serving the terminal can be changed from satellite A to satellite B. For example, (through movement of the terminal or satellite A) the terminal can be located within the coverage area of ​​satellite B instead of satellite A.

[0331] The terminal can be in RRC connected state within the coverage area of ​​satellite A. Afterwards, the terminal can be in RRC inactive state. Afterwards, the terminal can be in RRC connected state within the coverage area of ​​satellite B.

[0332] Step 7. Based on the periodic registration cycle, the terminal can send an RRC ResumeRequest (TS38.300 v17.5.0 9.2.2.4.1) message to satellite A to trigger the registration process. Based on this, the RRC recovery process can be executed.

[0333] Step 8. Satellite B can confirm the base station ID (corresponding to the ID of satellite A) through the UE's I-RNTI information and retrieve the UE context from satellite A.

[0334] Satellite B can retrieve the UE context via ISL with Satellite A.

[0335] Satellite B can send a UE context retrieval request message to Satellite A. Based on this, Satellite A can send a UE context retrieval response message to Satellite B.

[0336] Retrieving the UE context response message can include the UE context. The UE context can include information about the terminal's support for S&F operations.

[0337] Step 9. RRC recovery is complete, and the terminal can be in the RRC_CONNECTED state.

[0338] Satellite B can send RRCResume to the terminal. Then, the terminal can be in the RRC_CONNECTED state.

[0339] Step 10. The terminal can send an RRRCResumeComplete message to satellite B.

[0340] At this point, the RRCResumeComplete message may include a registration request for the periodic registration of the terminal.

[0341] The terminal can be in CM-CONNECTED or RRC_CONNECTED state.

[0342] Step 11. Satellite B may determine not to send a UE CONTEXT RELEASE message to Satellite A. This determination may be based on the fact that Satellite A and the terminal support S&F operation.

[0343] Traditionally, after the RRRCResumeComplete procedure, satellite B delivers a UE context release message to satellite A. Then, the procedure for deleting the UE context from satellite A is performed.

[0344] Based on the following, satellite B can determine not to send a UE context release message to satellite A: Based on the acquired UE context information (retrieved from satellite A), satellite B can know that the terminal supports S&F operations.

[0345] - When satellite B and satellite A perform Xn settings ( Figure 14 Satellite B can know that Satellite A supports S&F operations.

[0346] Since no UE context release message was received from satellite B, satellite A can maintain the UE context and buffered terminal data without deleting them.

[0347] Step 12. The terminal can perform a periodic registration process via satellite B.

[0348] Periodic registration processes can be performed via the service link between the terminal and satellite B, and the feeder link between satellite B and the ground gateway.

[0349] The terminal can perform a periodic registration process via i) the service link between the terminal and satellite B, ii) the ISL between satellite B and another satellite (e.g., satellite C), and iii) the feeder link between the other satellite and the ground gateway.

[0350] The AMF can determine if a terminal supports S&F operations through the UE context (the AMF's UE context) (information received from the terminal during the registration process in step 2, indicating that the terminal supports S&F operations). Based on this, the AMF can identify multiple N2 connections.

[0351] For example, the AMF can additionally create an N2 connection with satellite B while maintaining an N2 connection with satellite A.

[0352] Step 13. When connected to a terrestrial network, satellite A can determine to transmit buffered data via the feeder link.

[0353] When satellite A is able to connect to the ground gateway, satellite A can use the UE context to connect to the core network (e.g., AMF) through the ground gateway (feeder link). For example, satellite A can use the maintained N2 connection to connect to the AMF (e.g., without having to perform the NG setup procedure).

[0354] Satellite A can use the maintained UE context to connect to the UE's AMF.

[0355] Step 14. Satellite A can deliver the NAS message (UL NAS transmission) received from the terminal to the AMF. The NAS message may include the terminal's MO data and PDU session ID from Step 4.

[0356] Using the N2 connection maintained in step 12 (e.g., without having to perform the NG setup procedure) and the UE context, satellite A can send the buffered data to the AMF via the feeder link when connected to the terrestrial network. The buffered data may include the PDU session ID.

[0357] Step 15. The AMF can determine the SMF handling the PDU session based on the PDU session ID included in the NAS message. Based on this, the AMF can deliver the PDU session ID and data to the determined SMF through the Nsmf_PDUSession_SendMOData service operation.

[0358] Step 16. The SMF can deliver the data received from the AMF to the UPF.

[0359] Even if there is no uplink data (MO data) or downlink data (MT data) in the satellite, the satellite can maintain its UE context without deleting it. When the corresponding satellite serves the terminal again (e.g., when it serves the terminal again after it has been in orbit for a period of time), the maintained UE context can be used.

[0360] The UE context can be deleted after a certain period of time using a timer. The timer can be set by the terminal, satellite, base station, or core network.

[0361] If control plane CIoT 5GS optimization is not used, then in Figure 17 In step 4, instead of the terminal sending user data via a NAS message (UL NAS transfer) including the PDU session ID and data, the terminal can send MO data to satellite A through the user plane. Satellite A can store the MO data.

[0362] In this case, Figure 17 After step 10, Satellite B can send a path switching request message to the AMF. Satellite B can include an indication that it supports S&F operations in the path switching request.

[0363] Based on the indication and / or fact that the terminal supports S&F operations, the AMF may maintain the N2 connection with satellite A for the terminal without deleting it.

[0364] After this, satellite A can connect to the ground gateway (feed link). Figure 17 (Step 13). Then, Satellite A can use the maintained N2 connection (e.g., without having to perform the NG setup procedure) and UE context to connect with the AMF. Satellite A can send a path switching request message to the AMF. Then, Satellite A can create user plane resources with the UPF through the SMF and forward the stored MO data to the UPF.

[0365] During the registration process, a satellite (equipped with base station functionality) can receive information from the AMF instructing the terminal to support S&F operations and store it in the UE context. When the satellite serving the terminal is changed, the UE context, including the corresponding information, can be delivered to the changed serving satellite (the satellite currently serving the terminal). Prior to the change in UE context, the changed serving satellite may not send a UE context release message to the serving satellite. Therefore, the previous serving satellite does not delete the UE context, and the UE context can subsequently be used to connect to the terminal's AMF when connecting to a terrestrial gateway. Based on this, the previous serving satellite can forward buffered MO data to the AMF.

[0366] S&F operations are supported in RRC inactive state (RRC_INACTIVE mode).

[0367] The operations described in this specification can be applied by the NG-RAN and AMF installed on the satellite to the terminal performing the satellite's S&F operations.

[0368] NG-RAN can be installed on a satellite. There may be no mobility of the terminal supporting S&F operations. Alternatively, even if the terminal has mobility, the network (e.g., AMF) can determine when the terminal enters satellite coverage based on information about the terminal's mobility.

[0369] Satellites can perform inter-satellite Xn interface communication via ISL. Signaling messages (e.g., terminal registration with the network or creation of a PDU session) can be sent to the gateway (base station) via ISL. Data transmission from the terminal can be handled by S&F.

[0370] The proposed operation can be used even when using a general user plane, and it can also be used when sending data as a NAS message via 'Control Plane CIoT 5GS Optimization'. The terminal may include an indication notifying whether user data is included in an RRC message.

[0371] The satellite can be a LEO or MEO satellite.

[0372] 1) Satellites can determine whether they support S&F operations by exchanging capability information regarding support for S&F operations during the Xn setup process. Satellites can also determine whether AMFs support S&F operations by exchanging capability information regarding support for S&F operations between them during the NG setup process. When both the satellite and AMF support the corresponding functionality, multiple N2 connections can be created and maintained between the AMF and the satellite base station for a single UE that supports S&F functionality.

[0373] 2) During network registration, the terminal notifies itself that it supports S&F operation, and the satellite's AMF also accepts S&F operation. When creating the initial context with the satellite NG-RAN, the AMF can provide indications in the UE context to instruct the UE to operate in S&F, or it can include the UE's operation in S&F in the UE context. The RAN can store the UE's operation in S&F mode in the UE context. This information can be sent to the new satellite (or base station) even if the satellite (or base station) is changed.

[0374] 3) If there is no data to be sent, the terminal switches to the RRC_INACTIVE state, and the satellite NG-RAN can maintain the UE context of the terminal.

[0375] 4) When a satellite moves and the satellite covering the terminal is changed to allow the terminal to perform an RRC recovery procedure, the new satellite's NG-RAN can retrieve the UE context from the satellite that previously held the terminal's UE context. The new satellite can confirm that the corresponding UE supports S&F functionality from the UE context retrieved in the UE context response message. The new satellite can confirm that it is a satellite supporting S&F operation during the Xn setup procedure with the satellite that delivered the UE context. Based on the fact that the existing satellite and the UE support S&F operation, the new satellite can determine not to deliver the UE context release message to the existing satellite.

[0376] 5) When the satellite serving the terminal is changed, even if the satellite before the change delivers the UE context to the satellite after the change, the satellite before the change can still maintain the UE context. Based on this, when the satellite before the change connects to the ground gateway, it can use the stored UE context to connect to the UE's AMF. Furthermore, if the satellite before the change stores the UE's MO data, it can send the UE's MO data to the UE's AMF.

[0377] The following figures are created to illustrate specific examples of this specification. Since the specific names of the devices or signals / messages / fields described in the figures are presented as examples, the technical features of this specification are not limited to the specific names used in the following figures.

[0378] Figure 19 The process of the first satellite disclosed in this specification is shown.

[0379] 1. The first satellite can receive registration request messages from the user equipment (UE).

[0380] The registration request message may include UE capability information indicating that the UE supports store and forward (S&F).

[0381] 2. The first satellite can send a registration request message to the Access and Mobility Management Function (AMF).

[0382] 3. The first satellite can receive the initial context setting message from the AMF.

[0383] The initial context setting message may include UE capability information.

[0384] 4. The first satellite can store UE capability information as a UE context for the UE based on the initial context setting message.

[0385] 5. The first satellite can receive data from the UE.

[0386] 6. The first satellite may store data based on i) the first satellite not having a connection with a ground gateway and ii) UE capability information.

[0387] 7. The first satellite can send satellite support information, indicating that the first satellite supports S&F, to the second satellite through the Xn setup process with the second satellite.

[0388] 8. Based on the change of the satellite serving the UE from the first satellite to the second satellite, the first satellite can receive requests for the UE context from the second satellite.

[0389] 9. The first satellite may send the UE context to the second satellite based on this request.

[0390] 10. Based on the UE context being transmitted, the first satellite can receive the UE context release message from the second satellite.

[0391] 11. The first satellite can delete the UE context based on the UE context release message.

[0392] Based on i) sending satellite support information and ii) UE capability information, the first satellite can skip receiving UE context release messages and deleting UE contexts.

[0393] The first satellite can connect to a specific ground gateway.

[0394] Based on skipping the deletion of the UE context, the first satellite can use the UE context to send data to the AMF through a specific ground gateway.

[0395] The first satellite can perform the process of establishing a PDU session with the UE and AMF.

[0396] This data can be related to PDU sessions.

[0397] This data may include the ID of the PDU session.

[0398] The first satellite can be a regenerated satellite.

[0399] The following figures are created to illustrate specific examples of this specification. Since the specific names of the devices or signals / messages / fields described in the figures are presented as examples, the technical features of this specification are not limited to the specific names used in the following figures.

[0400] Figure 20 The AMF process disclosed in this specification is shown.

[0401] 1. The AMF can receive the first registration request message from the UE via the first satellite.

[0402] The registration request message may include UE capability information indicating that the UE supports S&F.

[0403] 2. The AMF can send an initial context setting message to the first satellite.

[0404] The initial context setting message may include UE capability information.

[0405] 3. The AMF can send a first registration request acceptance message to the UE based on the first registration request message.

[0406] The first registration request acceptance message may include information instructing AMF to support S&F.

[0407] 4. The AMF can receive a second registration request message from the UE via the second satellite based on the change of the satellite serving the UE from the first satellite to the second satellite.

[0408] 5. The AMF can be based on i) the first satellite supporting S&F, ii) the first satellite being connected to the ground gateway, iii) the first satellite having received and stored data from the UE before the change, and iv) UE capability information, receiving data from the first satellite through the ground gateway.

[0409] AMF can perform the process for establishing a PDU session with the UE and the first satellite; This data can be related to PDU sessions.

[0410] This data may include the ID of the PDU session.

[0411] AMF can send data to SMF based on the PDU session ID.

[0412] The first satellite can be a regenerated satellite.

[0413] The following figures are created to illustrate specific examples of this specification. Since the specific names of the devices or signals / messages / fields described in the figures are presented as examples, the technical features of this specification are not limited to the specific names used in the following figures.

[0414] Figure 21 The procedure of the UE disclosed in this specification is shown.

[0415] 1. The UE can send a first registration request message to the first satellite.

[0416] The first satellite may not have a connection to a ground gateway.

[0417] The registration request message may include UE capability information indicating that the UE supports S&F.

[0418] 2. The UE can receive registration acceptance messages from the AMF.

[0419] 3. The UE can execute the procedure for establishing a PDU session with the first satellite and the AMF.

[0420] 4. The UE can send data to the first satellite via a PDU session; and

[0421] 5. Based on the change of the satellite serving the UE from the first satellite to the second satellite, send a second registration request message to the second satellite.

[0422] The first satellite can be a regenerated satellite.

[0423] In the following sections, devices for performing communication according to some embodiments of this specification will be described.

[0424] For example, a device may include a processor, a transceiver, and memory.

[0425] For example, the processor can be configured to be operationally coupled to memory and processor.

[0426] The processor can perform the following: sending a first registration request message to the first satellite; Wherein, the first satellite has no connection with the ground gateway, and the registration request message includes UE capability information indicating that the UE supports S&F, receiving a registration acceptance message from the AMF; performing a process for establishing a PDU session with the first satellite and the AMF; sending data to the first satellite through the PDU session; and sending a second registration request message to the second satellite based on the change of the satellite serving the UE from the first satellite to the second satellite.

[0427] In the following sections, a processor for providing communication according to some embodiments of this specification will be described.

[0428] The processor is configured to: send a first registration request message to a first satellite; wherein the first satellite has no connection to a ground gateway, wherein the registration request message includes UE capability information indicating that the UE supports S&F; receive a registration acceptance message from the AMF; perform a process for establishing a PDU session with the first satellite and the AMF; send data to the first satellite through the PDU session; and send a second registration request message to a second satellite based on a change in the satellite serving the UE from the first satellite to the second satellite.

[0429] In the following, a non-volatile computer-readable medium storing one or more instructions for providing multicast services in wireless communication will be described according to some embodiments of this specification.

[0430] According to some embodiments of this disclosure, the technical features of this disclosure can be directly implemented as hardware, software executed by a processor, or a combination of both. For example, in wireless communication, a method executed by a wireless device can be implemented in hardware, software, firmware, or any combination thereof. For example, software can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or other storage media.

[0431] Some examples of storage media are coupled to a processor, allowing the processor to read information from the storage media. Alternatively, the storage media can be integrated into the processor. The processor and storage media can reside in an ASIC. Yet another example is that the processor and storage media can reside as separate components.

[0432] Computer-readable media can include tangible and non-volatile computer-readable storage media.

[0433] For example, non-volatile computer-readable media may include random access memory (RAM), such as synchronous dynamic random access memory (SDRAM), read-only memory (ROM), or non-volatile random access memory (NVRAM). Read-only memory (EEPROM), flash memory, magnetic or optical data storage media, or other media that can be used to store instructions or data structures, or non-volatile computer-readable media may also include combinations of the above.

[0434] Furthermore, the methods described herein can be implemented at least in part through a computer-readable communication medium that carries or transmits code in the form of instructions or data structures and can be accessed, read, and / or executed by a computer.

[0435] According to some embodiments of this disclosure, a non-transitory computer-readable medium has one or more instructions stored thereon. The stored one or more instructions can be executed by a processor of a base station.

[0436] One or more stored instructions cause the processor to perform the following operations: send a first registration request message to the first satellite; Wherein, the first satellite has no connection with the ground gateway, and the registration request message includes UE capability information indicating that the UE supports S&F, receiving a registration acceptance message from the AMF; performing a process for establishing a PDU session with the first satellite and the AMF; sending data to the first satellite through the PDU session; and sending a second registration request message to the second satellite based on the change of the satellite serving the UE from the first satellite to the second satellite.

[0437] This instruction manual can have various effects.

[0438] For example, S&F operations can be performed when the serving satellite changes.

[0439] The effects achievable through the specific examples in this specification are not limited to those listed above. For instance, there may be various technical effects that a person skilled in the art can understand or derive from this specification. Therefore, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0440] The claims described herein can be combined in various ways. For example, the technical features of the method claims of this specification can be combined and implemented as a device, and the technical features of the device claims of this specification can be combined and implemented as a method. Furthermore, the technical features of the method claims and the device claims of this specification can be combined and implemented as a device, and the technical features of the method claims and the device claims of this specification can be combined and implemented as a method. Other embodiments are within the scope of the appended claims.

Claims

1. A method for performing communication by a first satellite, the method comprising: Receive a registration request message from the user equipment (UE); The registration request message includes UE capability information indicating that the UE supports store and forward S&F. Send the registration request message to the Access and Mobility Management Function (AMF); Receive the initial context setting message from the AMF; The initial context setting message includes the UE capability information. Based on the initial context setting message, the UE capability information is stored as a UE context for the UE; Receive data from the UE; Based on i) the fact that the first satellite has no connection with the ground gateway and ii) the UE capability information, the data is stored; Satellite support information indicating that the first satellite supports S&F is sent to the second satellite through the Xn setup process with the second satellite; Based on the change of the satellite serving the UE from the first satellite to the second satellite, a request for the UE context is received from the second satellite; Based on the request, the UE context is sent to the second satellite; Based on the transmitted UE context, a UE context release message is received from the second satellite; and The UE context is deleted based on the UE context release message. Wherein, the first satellite, based on i) sending the satellite support information and ii) the UE capability information, skips receiving the UE context release message and deleting the UE context from the second satellite.

2. The method according to claim 1, further comprising: Connect to a specific ground gateway; as well as Based on skipping the deletion of the UE context, the data is sent to the AMF through the specific terrestrial gateway using the UE context.

3. The method according to claim 2, further comprising: Perform the procedure for establishing a PDU session with the UE and the AMF. The data is related to the PDU session, and The data includes the ID of the PDU session.

4. The method according to any one of claims 1 to 3, in, The first satellite is a regenerated satellite.

5. A method for performing communication by an Access and Mobility Management Function (AMF), the method comprising: Receive the first registration request message from the user equipment (UE) via the first satellite; The registration request message includes UE capability information indicating that the UE supports S&F. Send an initial context setting message to the first satellite; The initial context setting message includes the UE capability information. A first registration request acceptance message is sent to the UE based on the first registration request message; The first registration request acceptance message includes information indicating that the AMF supports S&F. Based on the change of the satellite serving the UE from the first satellite to the second satellite, a second registration request message is received from the UE via the second satellite; and Based on i) the first satellite supports S&F, ii) the first satellite is connected to a ground gateway, iii) the first satellite has received and stored data from the UE before the change, and iv) the UE capability information, the data is received from the first satellite through the ground gateway.

6. The method according to claim 5, further comprising: Perform the procedure for establishing a PDU session with the UE and the first satellite; The data is related to the PDU session. The data includes the ID of the PDU session, and The data is sent to the SMF based on the ID of the PDU session.

7. The method according to claim 5 or claim 6, in, The first satellite is a regenerated satellite.

8. A method for performing communication by a user equipment (UE), the method comprising: Send the first registration request message to the first satellite; The first satellite is not connected to the ground gateway. The registration request message includes UE capability information indicating that the UE supports S&F. Receive registration acceptance messages from the Access and Mobility Management Function (AMF); Perform the procedure for establishing a PDU session with the first satellite and the AMF; Data is sent to the first satellite via the PDU session; and Based on the change of the satellite serving the UE from the first satellite to the second satellite, a second registration request message is sent to the second satellite.

9. The method according to claim 8, in, The first satellite is a regenerated satellite.

10. A first satellite for performing communications, the first satellite comprising: At least one transceiver; as well as At least one processor, The processor performs the operation of the method according to any one of claims 1 to 4.

11. An Access and Mobility Management Function (AMF) for performing communications, the AMF comprising: At least one transceiver; as well as At least one processor, The processor performs the operation of the method according to any one of claims 5 to 7.

12. A user equipment (UE) for performing communication, the UE comprising: At least one transceiver; as well as At least one processor, The processor performs the operation according to claim 8 or 9.

Images