User equipment (UE)

The UE implementation method with a first timer and detach acceptance mechanism addresses the ambiguity in S&F satellite operations, ensuring clear behavior and improved system functionality in 5G mobile communication systems.

WO2026235176A1PCT designated stage Publication Date: 2026-11-12SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2026/017526
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

The implementation details for Store and Forward (S&F) satellite operation in 5G mobile communication systems are not clearly specified, leading to ambiguity in the behavior of User Equipment (UE), satellites, and networks.

Method used

A UE implementation method is provided, involving a control unit that starts a first timer when in specific states, prevents NAS procedures on S&F satellite E-UTRAN cells, and sends detach acceptance messages upon receiving a detach request, transitioning to an EMM-DEREGISTERED state.

Benefits of technology

Clarifies the method for realizing S&F satellite operations, ensuring clear UE, satellite, and network behavior, thereby enhancing system functionality and interoperability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2026017526_12112026_PF_FP_ABST
    Figure JP2026017526_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present invention provides a technique for a UE, which is capable of communicating by means of a satellite, to execute management of a store and forward (S&F) mode and / or appropriate processing of UE behaviors in the S&F mode in order for each device to appropriately support S&F satellite operations provided by a satellite that has lost connection to the ground and / or a device mounted on the satellite.
Need to check novelty before this filing date? Find Prior Art

Description

UE (User Equipment)

[0001] The present invention relates to a UE (User Equipment). This application claims priority to Japanese Patent Application No. 2025-078663 filed in Japan on May 9, 2025, the content of which is incorporated herein by reference in its entirety.

[0002] In 3GPP (3rd Generation Partnership Project: registered trademark), the system architecture of 5GS (5G System), which is a 5th Generation (5G) mobile communication system, is being studied, and discussions for supporting new procedures and new functions are underway (see Non-Patent Document 1).

[0003] 3GPP TR 23.700-29 V19.0.0 (2024-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on integration of satellite components in the 5G architecture; Phase 3 (Release 19) pp. 15, pp. 254 - 256

[0004] In Release 19, specification of Store and Forward (also referred to as S&F) satellite operation is scheduled, but details of how to implement such operation are not disclosed (see Non-Patent Document 1).

[0005] One aspect of the present invention has been made in view of the circumstances described above, and is intended to clarify an implementation method for store and forward satellite operation, as well as to clarify the detailed behavior of the UE, and / or the satellite, and / or the network.

[0006] An UE according to one aspect of the present invention comprises a control unit and a transceiver unit, wherein the control unit starts a first timer and, while the first timer is running, controls the UE not to start a NAS procedure on an S&F satellite E-UTRAN cell, the S&F satellite E-UTRAN cell is a cell having satellite E-UTRAN access technology that broadcasts information indicating that the base station is operating in S&F mode, and while the first timer is running, if the transceiver unit receives a detach request message from the network, the control unit stops the first timer, the transceiver unit sends a detach acceptance message in response to the detach request message, and the UE enters an EMM-DEREGISTERED state.

[0007] In one aspect of the present invention, the first timer is executed when the state of the UE is in the EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH state.

[0008] In one aspect of the present invention, the first timer is executed when the state of the UE is in the EMM-REGISTERED state.

[0009] In one aspect of the present invention, if the detach procedure is initiated when the transmitting / receiving unit transmits a second detach request message while the first timer is running, the transmitting / receiving unit receives a second detach acceptance message as a response to the second detach request message, and the UE enters the EMM-DEREGISTERED state.

[0010] According to one aspect of the present invention, it is possible to clarify the method for realizing memory and transmission satellite operations, as well as clarify the detailed behavior of the UE, and / or satellite, and / or network.

[0011] This is a diagram illustrating the overview of the mobile communication system (EPS / 5GS). This is a diagram illustrating the detailed configuration of the mobile communication system (EPS / 5GS). This is a diagram illustrating the equipment configuration of the UE. This is a diagram illustrating the configuration of the access network equipment. This is a diagram illustrating the configuration of the core network equipment. This is a diagram illustrating the detailed configuration of the satellite-based mobile communication system (EPS / 5GS). This is a diagram illustrating the registration procedure, attach procedure, and TAU procedure. This is a diagram illustrating the unregistered / detach procedure initiated from the UE. This is a diagram illustrating the unregistered / detach procedure initiated from the NW.

[0012] The best mode for carrying out one aspect of the present invention will be described below with reference to the drawings. In this embodiment, an example of a mobile communication system to which one aspect of the present invention is applied will be described.

[0013] [1. System Overview] First, Figure 1 is a diagram illustrating the general structure of the mobile communication system 1 used in each embodiment, and Figure 2 is a diagram illustrating the detailed configuration of the mobile communication system 1.

[0014] Figure 1 shows that mobile communication system 1 consists of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network)_A5, access network_B120, core network_B190, and DN (Data Network)_A6.

[0015] In the following, these devices and functions may be referred to using abbreviations such as UE, Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, etc.

[0016] Figure 2 also shows devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, and N3IWF170, as well as the interfaces that connect these devices and functions to each other.

[0017] In the following, these devices and functions may be described using abbreviations such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0018] Furthermore, the 4G system, EPS (Evolved Packet System), consists of access network_A and core network_A, but may also include UE and / or PDN. Similarly, the 5G system, 5GS (5G System), consists of UE, access network_B and core network_B, but may also include DN.

[0019] A UE is a device capable of connecting to network services via 3GPP access (also known as a 3GPP access network or 3GPP AN) and / or non-3GPP access (also known as a non-3GPP access network or non-3GPP AN). A UE may be a wireless communication terminal device such as a mobile phone or smartphone, and may be a terminal device capable of connecting to EPS and / or 5GS. A UE may be equipped with a UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). Note that a UE may also be referred to as a user device or terminal device.

[0020] Furthermore, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. E-UTRAN has one or more eNBs (evolved Node B, also called eNode-B)45. Note that in the following, eNB45 may be written simply as eNB. If there are multiple eNBs, each eNB is connected to the others, for example, by an X2 interface. Furthermore, the wireless LAN access network has one or more access points.

[0021] Furthermore, access network_B corresponds to the 5G access network (5G AN). The 5G AN consists of NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs)122 are placed in the NG-RAN. Note that, below, gNB122 may be written with the symbol omitted, such as gNB. A gNB is a node that provides the NR (New Radio) user plane and control plane to the UE and is a node that connects to the 5GCN via an NG interface (including the N2 interface or N3 interface). In other words, a gNB is a base station device newly designed for 5GS and has different functions from a base station device (eNB) designed for the 4G system, EPS. Also, if there are multiple gNBs, each gNB is connected to the others, for example, by an Xn interface.

[0022] Access network A and access network B may be RANs (Radio Access Networks).

[0023] Furthermore, non-3GPP access networks may include untrusted non-3GPP access networks and trusted non-3GPP access networks. Here, an untrusted non-3GPP access network may be a non-3GPP access network that does not perform security management within the access network, such as a public wireless LAN. On the other hand, a trusted non-3GPP access network may be an access network defined by 3GPP and may include a TNAP (trusted non-3GPP access point) and a TNGF (trusted non-3GPP Gateway function).

[0024] Furthermore, in the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. Similarly, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. Additionally, nodes located in access network_B may be collectively referred to as NG-RAN nodes.

[0025] Furthermore, in the following, access network_A, access network_B, and the devices included in access network_A, and the devices included in access network_B may be referred to as the access network, access network devices, or devices within the access network.

[0026] Furthermore, core network_A may correspond to EPC (Evolved Packet Core). EPC may house, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc.

[0027] Furthermore, core network_B may support 5GCN (5G Core Network). 5GCN may include, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), and UDM (Unified Data Management). Here, 5GCN may also be expressed as 5GC.

[0028] Furthermore, in the following, Core Network A, Core Network B, and the devices included in Core Network A, and the devices included in Core Network B may be referred to as the Core Network, Core Network Devices, or Devices within the Core Network.

[0029] The core network (Core Network A and / or Core Network B) may be an IP mobile communication network operated by a Mobile Network Operator (MNO) that connects the access network (Access Network A and / or Access Network B) to the PDN and / or DN; it may be a core network for a mobile network operator that operates and manages the mobile communication system 1; or it may be a core network for a virtual mobile communication operator or virtual mobile communication service provider such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler).

[0030] Furthermore, although Figure 1 shows a case where the PDN and DN are the same, they may be different. The PDN may be a DN (Data Network) that provides communication services to the UE. The DN may be configured as a packet data service network, or it may be configured for each service. In addition, the PDN may include connected communication terminals. Therefore, connecting to a PDN may also mean connecting to communication terminals or server devices located in the PDN. Furthermore, sending and receiving user data with a PDN may also mean sending and receiving user data with communication terminals or server devices located in the PDN. Note that the PDN may be referred to as DN, and the DN may be referred to as PDN. Also, the PDN and DN may be any DN that provides communication services to the UE, and are not limited to the EPS DN and the 5GS PDN.

[0031] Furthermore, in the following, access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein may be referred to as a network or network device. In other words, when a network and / or network device sends and receives messages and / or performs procedures, it means that access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein send and receive messages and / or perform procedures.

[0032] Furthermore, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the PDN or DN via the access network and the core network. That is, the UE can send and receive (communicate with) user data to and from the PDN or DN. When sending and receiving user data, non-IP communication may be used in addition to IP (Internet Protocol) communication.

[0033] Here, IP communication refers to data communication using IP, where data is sent and received via IP packets. An IP packet consists of an IP header and a payload. The payload may include data sent and received by devices and functions included in EPS or devices and functions included in 5GS. Non-IP communication, on the other hand, refers to data communication that does not use IP, where data is sent and received in a format different from the structure of an IP packet. For example, non-IP communication may be data communication realized by sending and receiving application data without an IP header, or it may be user data sent and received by the UE with other headers such as a MAC header or an Ethernet® frame header attached.

[0034] Furthermore, access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may include devices not shown in Figure 2. For example, core network_A and / or core network_B may include an AUSF (Authentication Server Function) or an AAA (Authentication, authorization, and accounting) server (AAA-S).

[0035] Here, AUSF is a core network device equipped with authentication functions for 3GPP access and non-3GPP access. Specifically, it is a network function unit that receives authentication requests for 3GPP access and / or non-3GPP access from the UE and executes the authentication procedure.

[0036] Furthermore, the AAA server is a device equipped with authentication, authorization, and billing functions, which connects directly or indirectly to the AUSF via other network devices. The AAA server may be a network device within the core network. However, the AAA server may not be included in core network_A and / or core network_B, but may be included in PLMN. In other words, the AAA server may be a core network device or a device located outside the core network. For example, the AAA server may be a server device within PLMN managed by a third party.

[0037] Note that in Figure 2, for the sake of simplification, only one of each device / function is shown; however, multiple similar devices / functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may be configured with multiple devices / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150.

[0038] In this paper, the management of information by each device may also mean that it stores information.

[0039] [2. Configuration of Each Device] Next, the configuration of each device (UE, and / or access network device, and / or core network device) used in each embodiment will be described with reference to a diagram. Each device may be configured as physical hardware, as logical (virtual) hardware configured on general-purpose hardware, or as software. Furthermore, at least some (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

[0040] Furthermore, each memory unit (memory unit_A340, memory unit_B540, memory unit_B740) within each device / function described below is composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each memory unit can store not only the information originally set at the time of shipment, but also various information transmitted and received with devices / functions other than its own device / function (for example, UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). In addition, each memory unit can store identification information, control information, flags, parameters, etc., contained in control messages transmitted and received within the various communication procedures described later. Furthermore, each memory unit may store this information for each UE. In addition, when interworking between 5GS and EPS, each memory unit can store control messages and user data transmitted and received with devices / functions contained within 5GS and / or EPS. In this case, it can store not only information transmitted and received via the N26 interface, but also information transmitted and received without the N26 interface.

[0041] [2.1. UE Equipment Configuration] First, an example of the UE (User Equipment) equipment configuration will be explained using Figure 3. The UE consists of a control unit_A300, an antenna 310, a transceiver unit_A320, and a storage unit_A340. The control unit_A300, the transceiver unit_A320, and the storage unit_A340 are connected via a bus. The transceiver unit_A320 is connected to the antenna 310.

[0042] Control unit_A300 is a functional unit that controls the overall operations and functions of the UE. The control unit_A300 reads and executes various programs stored in the storage unit_A340 as needed, thereby implementing various processes in the UE.

[0043] Transceiver unit_A320 is a functional unit for performing radio communication with a base station apparatus (eNB or gNB) in an access network via an antenna. That is, the UE can transmit and receive user data and / or control information to and from the access network apparatus, and / or the core network apparatus, and / or the PDN, and / or the DN, using the transceiver unit_A320.

[0044] Describing in detail with reference to Figure 2, the UE can communicate with a base station apparatus (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver unit_A320. In addition, the UE can communicate with a base station apparatus (gNB) in the 5G AN by using the transceiver unit_A320. Further, the UE can transmit and receive NAS (Non-Access-Stratum) messages to and from the AMF via the N1 interface by using the transceiver unit_A320. However, since the N1 interface is logical, the communication between the UE and the AMF is actually performed via the 5G AN.

[0045] Storage unit_A340 is a functional unit for storing programs, user data, control information and the like required for each operation of the UE. In addition, the storage unit_A340 may have a function of storing control information transmitted and received to and from the access network apparatus, the core network apparatus, and the DN.

[0046] [2.2. Apparatus Configuration of Base Station Apparatus] Next, an example of the apparatus configuration of the base station apparatus will be described using FIG. 4. The base station apparatus may be a gNB, or an eNB, or an en-gNB, or an ng-eNB. Here, a case where the base station apparatus is a gNB will be described as an example. That is, in the following description, gNB may be read as eNB, or en-gNB, or ng-eNB. The gNB is composed of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, the network connection unit_B520, the transceiver unit_B530, and the storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0047] The control unit_B500 is a functional unit that controls the overall operations and functions of the gNB. The control unit_B500 implements various processes in the gNB by reading and executing various programs stored in the storage unit_B540 as necessary.

[0048] The network connection unit_B520 is a functional unit for the gNB to communicate with an AMF and / or a UPF. That is, the gNB can transmit and receive user data and / or control information to and from the AMF and / or the UPF using the network connection unit_B520.

[0049] The transceiver unit_B530 is a functional unit for performing wireless communication with a UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information to and from the UE using the transceiver unit_B530.

[0050] To describe in detail with reference to FIG. 2, a gNB located in the 5G AN can communicate with an AMF via the N2 interface and can communicate with a UPF via the N3 interface by using the network connection unit_B520. Further, the gNB can communicate with a UE by using the transceiver unit_B530.

[0051] Memory unit B540 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the gNB. Memory unit 540 may also have the function of storing control information transmitted and received between the UE, other access network devices (base station devices), core network devices, and DN.

[0052] [2.3. AMF / MME Device Configuration] Next, we will describe an example of the device configuration of AMF and MME, which are part of the core network device or core network function. Here, we will describe an example of the AMF device configuration using Figure 5. Here, we will explain using the AMF as an example, but it may be replaced with MME and / or movement management device. The AMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The AMF may be a node that handles the control plane.

[0053] The control unit B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit B700 realizes various processes in the AMF by reading and executing various programs stored in the memory unit B740 as needed.

[0054] The network connection unit_B720 is a functional unit for the AMF to connect to base station equipment (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF, and / or NSACF within the 5G AN. In other words, the AMF can use the network connection unit_B720 to send and receive user data and / or control information with base station equipment (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF within the 5G AN. The network connection unit_B720 can be read as a transmitting / receiving unit.

[0055] Referring to Figure 2, the AMF within 5GCN can communicate with the gNB via the N2 interface, the UDM via the N8 interface, the SMF via the N11 interface, and the PCF via the N15 interface, using the network connection unit _A620. Furthermore, the AMF can send and receive NAS messages with the UE via the N1 interface using the network connection unit _A620. However, since the N1 interface is logical, actual communication between the UE and the AMF takes place via the 5G AN. Additionally, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface using the network connection unit _A620.

[0056] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the AMF. Memory unit B740 may also have the function of storing control information transmitted and received between the UE, access network device, other core network device, and DN.

[0057] Furthermore, the AMF has functions such as exchanging control messages with the RAN using the N2 interface, exchanging NAS messages with the UE using the N1 interface, encrypting and protecting the integrity of NAS messages, registration management (RM) function, connection management (CM) function, reachability management function, mobility management function for UEs, etc., forwarding SM (Session Management) messages between the UE and the SMF, access authentication (Access Authentication, Access Authorization) function, security anchor function (SEA), security context management (SCM), support for the N2 interface to the N3IWF (Non-3GPP Interworking Function), support for sending and receiving NAS signals with the UE via the N3IWF, and authentication of UEs connected via the N3IWF.

[0058] Furthermore, registration management manages the RM state for each UE. The RM state may be synchronized between the UE and the AMF. There are two RM states: unregistered state (RM-DEREGISTERED state) and registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered with the network, so the UE context in the AMF does not have valid location or routing information for that UE, and therefore the AMF cannot reach the UE. In the RM-REGISTERED state, the UE is registered with the network, so the UE can receive services that require registration with the network. Note that the RM state may also be expressed as the 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state.

[0059] In other words, 5GMM-REGISTERED means that each device may have established a 5GMM context or a PDU session context. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may start sending and receiving user data and control messages, and may respond to paging. In addition, when each device is 5GMM-REGISTERED, UE_A10 may perform registration procedures other than the registration procedure for initial registration, and / or service request procedures.

[0060] Furthermore, 5GMM-DEREGISTERED may occur even if each device has not established a 5GMM context, or if the location information of UE_A10 is not known to the network, or if the network is unreachable to UE_A10. If each device is in a 5GMM-DEREGISTERED state, UE_A10 may initiate the registration procedure, or establish a 5GMM context by executing the registration procedure.

[0061] Furthermore, connection management manages the CM state for each UE. The CM state may be synchronized between the UE and the AMF. There are two CM states: disconnected state (CM-IDLE state) and connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-IDLE state, the UE does not have an N2 connection or an N3 connection. On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-CONNECTED state, the UE may have an N2 connection and / or an N3 connection.

[0062] Furthermore, connection management may be handled separately for CM states in 3GPP access and CM states in non-3GPP access. In this case, the CM states in 3GPP access may include an unconnected state (CM-IDLE state over 3GPP access) and a connected state (CM-CONNECTED state over 3GPP access). Furthermore, the CM states in non-3GPP access may include an unconnected state (CM-IDLE state over non-3GPP access) and a connected state (CM-CONNECTED state over non-3GPP access). Note that the unconnected state may be expressed as idle mode, and the connected state may be expressed as connected mode.

[0063] Furthermore, the CM state may be expressed as 5GMM mode. In this case, the disconnected state may be expressed as 5GMM-IDLE mode, and the connected state may be expressed as 5GMM-CONNECTED mode. Additionally, the disconnected state in 3GPP access may be expressed as 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access may be expressed as 5GMM-CONNECTED mode over 3GPP access. Furthermore, the disconnected state in non-3GPP access may be expressed as 5GMM-IDLE mode over non-3GPP access, and the connected state in non-3GPP access may be expressed as 5GMM-CONNECTED mode over non-3GPP access. Note that 5GMM-IDLE mode may also be expressed as idle mode, and 5GMM-CONNECTED mode may also be expressed as connected mode.

[0064] Furthermore, one or more AMFs may be placed within core network_B. Also, an AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). Additionally, an AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs.

[0065] Furthermore, N3IWF is a device and / or function placed between the non-3GPP access and 5GCN when the UE connects to 5GS via non-3GPP access.

[0066] Although the above explanation uses the case of AMF and / or MME as an example, any NF that has at least one function of AMF, such as the movement management function of UE, will suffice, and AMF and / or MME may be replaced with movement management device. In that case, the 5MM state can be read as the EMM state.

[0067] In addition to the unregistered state (5GMM-DEREGISTERED state or EMM-DEREGISTERED state) and registered state (5GMM-REGISTERED state or EMM-REGISTERED state), other possible 5GMM states and / or EMM states include the empty state (5GMM-NULL or EMM-NULL state), the registration initiation state (5GMM-REGISTERED-INITIATED state or EMM-REGISTERED-INITIATED state), the unregistered initiation state (5GMM-DEREGISTERED-INITIATED state or EMM-DEREGISTERED-INITIATED state), the tracking area update initiation state (EMM-TRACKING-AREA-UPDATING-INITIATED state), and the service request initiation state (5GMM-SERVICE-REQUEST-INITIATED state or EMM-SERVICE-REQUEST-INITIATED state).

[0068] [2.4. SMF / PGW Device Configuration] Next, an example of the device configuration of an SMF, which is a core network device or part of the core network function, will be explained using Figure 5. Here, the example of an SMF will be used, but it may be replaced with a PGW or PGW-C. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. The SMF may be a node that handles the control plane.

[0069] The control unit B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit B700 implements various processes in the SMF by reading and executing various programs stored in the memory unit B740 as needed.

[0070] The network connection unit B720 is a functional unit that allows the SMF to connect with the AMF, and / or UPF, and / or PCF, and / or UDM. In other words, the SMF can use the network connection unit B720 to send and receive user data and / or control information with the AMF, and / or UPF, and / or PCF, and / or UDM, and / or NSACF.

[0071] Referring to Figure 2, the SMF within 5GCN can communicate with the AMF via the N11 interface, the UPF via the N4 interface, the PCF via the N7 interface, and the UDM via the N10 interface by using the network connection unit A620.

[0072] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the SMF.

[0073] SMF has session management functions such as establishing, modifying, and releasing PDU sessions; IP address allocation and management functions for UEs; UPF selection and control functions; UPF configuration functions for routing traffic to appropriate destinations; functions for sending and receiving the SM portion of NAS messages; functions for notifying when downlink data has arrived (Downlink Data Notification); functions for providing AN-specific (AN-specific) SM information sent to ANs via the N2 interface through AMF; functions for determining the SSC mode (Session and Service Continuity mode) for sessions; and roaming functions.

[0074] Furthermore, the memory unit 740 may have a function for storing control information transmitted and received between the UE, access network device, other core network device, and DN.

[0075] Although the above explanation uses the case of SMF and / or PGW and / or PGW-C as an example, any NF that has at least one function of an SMF, such as session management functionality, will suffice, and SMF and / or PGW and / or PGW-C may be replaced with session management devices.

[0076] [2.5. UPF / PGW Device Configuration] Next, an example of the device configuration of a UPF, which is a core network device or one of the core network functions, will be explained using Figure 5. Here, the case of a UPF is used as an example, but it may be replaced with a PGW or PGW-U. A PGW may combine the functions of both a PGW-C and a PGW-U. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. The UPF may be a node that handles the control plane.

[0077] The control unit B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit B700 implements various processes in the UPF by reading and executing various programs stored in the memory unit B740 as needed.

[0078] The network connection unit B720 is a functional unit that allows the UPF to connect with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN. In other words, the UPF can use the network connection unit B720 to send and receive user data and / or control information with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN.

[0079] Referring to Figure 2, the UPF within 5GCN can communicate with the gNB via the N3 interface, the SMF via the N4 interface, the DN via the N6 interface, and other UPFs via the N9 interface by using the network connection unit A620.

[0080] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the UPF.

[0081] UPF has functions such as acting as an anchor point for intra-RAT mobility or inter-RAT mobility, acting as an external PDU session point for interconnecting to DNs (i.e., acting as a gateway between DNs and core network B to forward user data), routing and forwarding packets, an UL CL (Uplink Classifier) ​​function that supports routing multiple traffic flows to a single DN, a branching point function that supports multi-homed PDU sessions, a QoS (Quality of Service) processing function for the user plane, an uplink traffic verification function, downlink packet buffering, and a function to trigger downlink data notification.

[0082] Furthermore, the UPF may also be a gateway for IP communication and / or non-IP communication. The UPF may also have the function of forwarding IP communication, and may also have the function of converting non-IP communication to IP communication. In addition, multiple gateways may be gateways connecting the core network B to a single DN. The UPF may also have connectivity to other NFs, and may connect to each device via other NFs.

[0083] Furthermore, the memory unit 740 may have a function for storing control information transmitted and received between the UE, access network device, other core network device, and DN.

[0084] Although the above explanation uses the case of UPF and / or PGW and / or PGW-U as an example, any NF that has at least one function of UPF is acceptable, and UPF and / or PGW and / or PGW-U may be interpreted as user plane function devices.

[0085] [2.6. Description of Other Devices and / or Functions and Identification Information in This Embodiment] Next, other devices and / or functions and identification information will be described.

[0086] The term "network" refers to at least a portion of Access Network B, Core Network B, and DN. Furthermore, one or more devices included in at least a portion of Access Network B, Core Network B, and DN may be referred to as a network or network device. In other words, the statement that a network performs message transmission and / or processing may also mean that devices within the network (network devices, and / or control devices) perform message transmission and / or processing. Conversely, the statement that devices within the network perform message transmission and / or processing may also mean that the network performs message transmission and / or processing.

[0087] Furthermore, the user plane (also called UP) refers to user data transmitted and received between the UE and the network. The UP may also be a communication channel for transmitting and receiving user data, and may consist of multiple bearers. In the case of 4G, the UP may be transmitted and received using a PDN connection, or in the case of 5G, using a PDU session. In the case of EPS, the UP may be transmitted and received using the LTE-Uu interface, and / or the S1-U interface, and / or the S5 interface, and / or the S8 interface, and / or the SGi interface. In the case of 5GS, the UP may be transmitted and received via the interface between the UE and the NG RAN, and / or the N3 interface, and / or the N9 interface, and / or the N6 interface. The UP may also be expressed as U-Plane.

[0088] Furthermore, the control plane (also called CP) refers to control messages sent and received for the purpose of controlling the communication of the UE. The CP may also be a communication channel for sending and receiving control messages, and may consist of multiple bearers. The CP may be sent and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the MME. The CP may also be sent and received using a NAS signaling connection between the UE and the AMF. In the case of EPS, the CP may be sent and received using the LTE-Uu interface and the S1-MME interface. In the case of 5GS, the CP may be sent and received using the interface between the UE and the NG RAN, and the N2 interface. The CP may be referred to as either a control plane or a C-Plane.

[0089] Furthermore, the NAS signaling connection is a connection established between the UE and the core network device, and the core network device is not limited to the MME and / or AMF, but may be any other connection and / or communication path between the core network device and the UE.

[0090] Furthermore, the U-Plane (User Plane; UP) may also be a communication channel for sending and receiving user data, and may consist of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may also be a communication channel for sending and receiving control messages, and may consist of multiple bearers.

[0091] Furthermore, the UE and core network may manage the RM state (also known as the 5GMM state or EMM state) and / or CM state (5GMM mode or EMM mode) for each UE.

[0092] The main UE 5GMM states and / or EMM states may include unregistered state (5GMM-DEREGISTERED state or EMM-DEREGISTERED state), registered state (5GMM-REGISTERED state or EMM-REGISTERED state), empty state (5GMM-NULL or EMM-NULL state), registration initiation state (5GMM-REGISTERED-INITIATED state or EMM-REGISTERED-INITIATED state), unregistered initiation state (5GMM-DEREGISTERED-INITIATED state or EMM-DEREGISTERED-INITIATED state), tracking area update initiation state (EMM-TRACKING-AREA-UPDATING-INITIATED state), and service request initiation state (5GMM-SERVICE-REQUEST-INITIATED state or EMM-SERVICE-REQUEST-INITIATED state).

[0093] Furthermore, substates belonging to the unregistered state (5GMM-DEREGISTERED state or EMM-DEREGISTERED state) or the registered state (5GMM-REGISTERED state or EMM-REGISTERED state) may be managed by the UE. For example, there may be UE states such as 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION and EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH, which are the UE states when the registration procedure fails.

[0094] Furthermore, MM (Mobility Management) messages may be control messages transmitted between the UE and the AMF or MME or other core network devices in the MM procedure, and may also be NAS messages (also referred to as NAS MM messages).

[0095] Furthermore, in 5GS, MM procedures (also referred to as procedures for MM (Mobility Management)) may include a Registration procedure initiated by the UE, a De-registration procedure initiated by the UE or AMF (or network), a De-registration procedure initiated by the UE or AMF (or network), a Generic UE Configuration Update procedure initiated by the AMF (or network), a Service Request procedure initiated by the UE, a Paging procedure initiated by the AMF (or network), and a Notification procedure initiated by the AMF (or network).

[0096] In this registration process, the UE may send a Registration Request message to the AMF and receive a Registration Accept or Registration Reject message from the AMF that has received it. The AMF may send a Registration Accept message if it approves the registration request from the UE, or a Registration Reject message if it does not.

[0097] In addition, in a de-registration procedure initiated by a UE, the UE may send a de-registration request message to the AMF and receive a de-registration acceptance message from the AMF that has received it.

[0098] In addition, in a deregistration procedure initiated by the AMF (or network), the AMF may send a deregistration request message to the UE and receive a deregistration acceptance message from the UE that received it.

[0099] In addition, in the generic UE configuration update procedure, the AMF may send a Configuration Update Command message to the UE and receive a Configuration Update Complete message from the UE that received the command.

[0100] Furthermore, in the service request procedure, the UE may send a Service Request message or a Control Plane Service Request message to the AMF, and receive a Service Accept message or a Service Reject message from the AMF that has received it. Here, the AMF may send a Service Accept message if it approves the service request from the UE, or a Service Reject message if it does not approve it.

[0101] In addition, during the paging procedure, the AMF sends a Request Paging to the base station, the base station receives this and sends a Paging message to the UE, the UE receives this and sends a Service Request message, CP Service Request message, or Registration Request message to the AMF, which the AMF may receive.

[0102] In addition, during the notification procedure, the AMF may send a Notification message to the UE and receive a Notification Response message, or a Service Request message, or a CP Service Request message, or a Registration Request message from the UE that received the Notification Response message.

[0103] Furthermore, in EPS, MM procedures may include an Attach procedure initiated by the UE, a Tracking area updating procedure initiated by the UE, a Detach procedure initiated by the UE or MME (or network), a Service Request procedure initiated by the UE, a Paging procedure initiated by the MME (or network), and a Transport of NAS messages procedure initiated by the UE or MME (or network).

[0104] In the attachment procedure, the UE may send an Attach Request message to the MME and receive an Attach Accept or Attach Reject message from the MME that received it. The MME may send an Attach Accept message if it permits the UE's attach request, or an Attach Reject message if it does not permit it.

[0105] Furthermore, in the tracking area update procedure, the UE may send a Tracking Area Update Request message to the MME and receive either an Attach Accept message or a Tracking Area Update Reject message from the MME that received it. Here, the MME may send a Tracking Area Accept message if it permits the Tracking Area Update Request from the UE, or a Tracking Area Reject message if it does not permit it.

[0106] In addition, during a detach procedure initiated by the UE, the UE may send a Detach Request message to the MME and receive a Detach Accept message from the MME that received it.

[0107] Furthermore, in a detach procedure initiated by the MME (or network), the MME may send a detach request message to the UE and receive a detach acceptance message from the UE that received it.

[0108] Furthermore, an SM (Session Management) message (also called a NAS (Non-Access-Stratum) SM message) may be a control message sent and received between the UE and the SMF via the AMF during an SM procedure, and may also be a NAS message (also called a NAS SM message).

[0109] Alternatively, an SM message may be a control message sent and received between the UE and the network in the SM procedure of the EPS, and may be a NAS message (also referred to as a NAS SM message). Furthermore, in 5GS, the SM procedure (also referred to as a procedure for SM) may include a PDU session establishment procedure initiated by the UE, a PDU session modification procedure initiated by the UE or SMF (or network), and a UE-requested PDU session release procedure initiated by the UE or SMF (or network).

[0110] In the PDU session establishment procedure, the UE may send a PDU Session Establishment Request message to the SMF and receive a PDU Session Establishment Accept message or a PDU Session Establishment Reject message from the SMF that received it. The SMF may send a PDU Session Establishment Accept message if it permits the UE's request to establish a PDU session, or a PDU Session Establishment Reject message if it does not permit it.

[0111] Furthermore, in a PDU session modification procedure initiated by the UE, the UE sends a PDU session modification request message to the SMF, and upon receiving this, the SMF may either execute the PDU session modification procedure initiated by the SMF, or send a PDU session modification reject message to the UE, which the UE may receive. Here, if the SMF approves the PDU session modification request from the UE, it may execute the PDU session modification procedure initiated by the SMF, or if it does not approve, it may send a PDU session modification reject message.

[0112] Furthermore, in a PDU session modification procedure initiated by the SMF (or network), the SMF may send a PDU Session Modification Command message to the UE, and may receive a PDU Session Modification Complete message or a PDU Session Modification Command Reject message from the UE that received it. Here, the UE may send a PDU Session Modification Complete message if it permits the PDU session modification instruction from the SMF, or a PDU Session Modification Command Reject message if it does not permit it.

[0113] Furthermore, in the PDU session release procedure initiated by the UE, the UE sends a PDU session release request message to the SMF, and upon receiving this, the SMF may either execute the PDU session release procedure initiated by the SMF, or send a PDU session release reject message to the UE, which the UE may receive. Here, if the SMF approves the PDU session release request from the UE, it may execute the PDU session release procedure initiated by the SMF, or if it does not approve, it may send a PDU session release reject message.

[0114] Additionally, in a PDU session release procedure initiated by the SMF (or network), the SMF may send a PDU Session Release Command message to the UE and receive a PDU Session Release Complete message from the UE that received the command.

[0115] Furthermore, in the PDN connection procedure, the UE may send a PDN Connectivity Request message to the MME, and may receive an Activate Default EPS Bearer Context Request message or a PDN Connectivity Reject message from the MME that received the request. Here, the MME may send an Activate Default EPS Bearer Context Request message if it permits the request from the UE, or a PDN Connectivity Reject message if it does not permit it.

[0116] Furthermore, in the PDN disconnection procedure, the UE may send a PDN Disconnect Request message to the MME, and may receive a Deactivate EPS Bearer Context Request message or a PDN Disconnect Reject message from the MME that received it. Here, the MME may send a Deactivate EPS Bearer Context Request message if it permits the request from the UE, or a PDN Disconnect Reject message if it does not permit it.

[0117] Furthermore, in the bearer resource allocation procedure, the UE may send a Bearer Resource Allocation Request message to the MME, and may receive an Activate Dedicated EPS Bearer Context Request message, a Modify EPS Bearer Context Request message, or a Bearer Resource Allocation Reject message from the MME that received the request. Here, the MME may send an Activate Dedicated EPS Bearer Context Request message or a Modify EPS Bearer Context Request message if it permits the request from the UE, or it may send a Bearer Resource Allocation Reject message if it does not permit the request.

[0118] Furthermore, in the bearer resource modification procedure, the UE may send a Bearer Resource Modification Request message to the MME, and may receive an Activate Dedicated EPS Bearer Context Request message, a Modify EPS Bearer Context Request message, a Deactivate EPS Bearer Context Request message, or a Bearer Resource Modification Reject message from the MME that has received this message. Here, the MME may send an Activate Dedicated EPS Bearer Context Request message, a Modify EPS Bearer Context Request message, or a Deactivate EPS Bearer Context Request message if it permits the request from the UE, or it may send a Bearer Resource Modification Reject message if it does not permit the request.

[0119] Furthermore, in the default EPS bearer context activation procedure, the MME may send an Activate Default EPS Bearer Context Request message to the UE, and may receive an Activate Default EPS Bearer Context Accept message or an Activate Default EPS Bearer Context Reject message from the UE that received the request. Here, the UE may send an Activate Default EPS Bearer Context Accept message if it approves the request from the MME, or an Activate Default EPS Bearer Context Reject message if it does not approve it.

[0120] Furthermore, in the dedicated EPS bearer context activation procedure, the MME may send an Activate Dedicated EPS Bearer Context Request message to the UE, and may receive an Activate Dedicated EPS Bearer Context Accept message or an Activate Dedicated EPS Bearer Context Reject message from the UE that received the request. Here, the UE may send an Activate Dedicated EPS Bearer Context Accept message if it permits the request from the MME, or an Activate Dedicated EPS Bearer Context Reject message if it does not permit the request.

[0121] Furthermore, in the EPS bearer context modification procedure, the MME may send a Modify EPS Bearer Context Request message to the UE, and may receive a Modify EPS Bearer Context Accept message or a Modify EPS Bearer Context Reject message from the UE that received the request. Here, the UE may send a Modify EPS Bearer Context Accept message if it approves the request from the MME, or a Modify EPS Bearer Context Reject message if it does not approve it.

[0122] In addition, during the EPS bearer context deactivation procedure, the MME may send a Deactivate EPS Bearer Context Request message to the UE and receive a Deactivate EPS Bearer Context Accept message from the UE that received it.

[0123] Note that MM procedures and SM procedures may be NAS procedures.

[0124] Furthermore, the 5GS (5G System) service may be a connectivity service provided using the core network_B190. In addition, the 5GS service may be a different service from the EPS service, or it may be a service similar to the EPS service.

[0125] Furthermore, non-5GS services may be any service other than 5GS services, and may include EPS services and / or non-EPS services.

[0126] Furthermore, the PDN (Packet Data Network) type indicates the type of PDN connection, and includes IPv4, IPv6, IPv4v6, and non-IP. If IPv4 is specified, it means that data will be sent and received using IPv4. If IPv6 is specified, it means that data will be sent and received using IPv6. If IPv4v6 is specified, it means that data will be sent and received using either IPv4 or IPv6. If non-IP is specified, it means that communication will be conducted using a communication method other than IP, rather than IP-based communication.

[0127] Furthermore, a PDU (Protocol Data Unit) session can be defined as the relationship between a DN and an UE that provides PDU connectivity services, but it may also be connectivity established between the UE and an external gateway. In 5GS, the UE can send and receive user data to and from the DN using the PDU session by establishing a PDU session via access network_B and core network_B. Here, this external gateway may be UPF, SCEF, etc. The UE can use the PDU session to send and receive user data with devices such as application servers located on the DN.

[0128] Furthermore, an MA PDU session may be a PDU session that provides PDU connectivity services using 3GPP access and / or non-3GPP access.

[0129] Furthermore, each device (UE, and / or access network device, and / or core network device) may manage one or more pieces of identification information associated with each PDU session. These pieces of identification information may include one or more of the following: DNN, QoS rules, PDU session type, application identification information, NSI identification information, and access network identification information, or they may include other information as well. In addition, if multiple PDU sessions are established, the pieces of identification information associated with each PDU session may be the same or different.

[0130] Furthermore, the DNN (Data Network Name) may be any identification information that identifies the core network and / or external networks such as DNs. In addition, the DNN can be used as information to select gateways such as PGW_A30 / UPF_A235 to which the core network B190 is connected. Furthermore, the DNN may be equivalent to the APN (Access Point Name).

[0131] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet, and Unstructured. If IPv4 is specified, it indicates that data will be sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Ethernet may also indicate that communication using IP will not be performed. If Unstructured is specified, it indicates that data will be sent and received to application servers, etc., on the DN using Point-to-Point (P2P) tunneling technology. As a P2P tunneling technology, for example, UDP / IP encapsulation technology may be used. In addition to the above, IP may also be included as a PDU session type. IP can be specified when the UE can use both IPv4 and IPv6.

[0132] Furthermore, a PDN connection can be defined as the relationship between a PDN represented by an APN and a UE, but it may also be a connectivity established between a UE and an external gateway. In the EPS, the UE can send and receive user data to and from the PDN using the PDN connection by establishing a PDN connection via access network_A and core network_A. Here, this external gateway may be a PGW, SCEF, etc. The UE can use the PDN connection to send and receive user data with devices such as application servers located in the PDN.

[0133] Furthermore, a PLMN (Public Land Mobile Network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by a telecommunications operator, and the operator can be identified by the PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN). In addition, the UE may maintain an Equivalent HPLMN list in the USIM to identify one or more EPLMNs (Equivalent HPLMNs). A PLMN that is different from the HPLMN and / or EPLMN may be a VPLMN (Visited PLMN). A PLMN that the UE has successfully registered may be an RPLMN (Registered PLMN; also called a Registered PLMN). Services provided by a PLMN may be called PLMN services, and services provided by an SNPN may be called SNPN services.

[0134] A tracking area is one or more ranges managed by the core network that can be represented by the location information of UE_A10. A tracking area may consist of multiple cells. Furthermore, a tracking area may be the range to which control messages such as paging are broadcast, or the range to which UE_A10 can move without handover procedures. In addition, a tracking area (also called a Tracking Area or TA) may be a routing area, a location area, or something similar. A tracking area may be identified by a Tracking Area Identity (TAI), which consists of a Tracking Area Code (TAC) and a Tracking Area Name Code (PLMN).

[0135] A registration area (also called a registration area) is a set of one or more TAs assigned by the AMF to a UE. UE_A10 may move within one or more TAs included in the registration area without sending or receiving signals for tracking area updates. In other words, a registration area may be a set of information indicating an area that UE_A10 can move within without performing the tracking area update procedure. A registration area may be identified by a TAI list consisting of one or more TAIs.

[0136] A UE ID is information used to identify a UE (User Account). Specifically, for example, a UE ID may be a SUCI (Subscription Concealed Identifier), SUPI (Subscription Permanent Identifier), GUTI (Globally Unique Temporary Identifier), IMEI (International Mobile Subscriber Identity), IMEISV (IMEI Software Version), or TMSI (Temporary Mobile Subscriber Identity). Alternatively, a UE ID may be other information configured within an application or network. Furthermore, a UE ID may be information used to identify a user.

[0137] Furthermore, a periodic update timer is a timer used to manage the update interval for periodically updating the registration status and / or registered information of a UE. The periodic update timer may be a periodic update timer, a periodic registration update timer, or a periodic tracking area update timer.

[0138] An implicit de-registration timer is a timer used to implicitly (unintentionally) manage that a UE is in an unregistered state when the NW loses connectivity to the UE for a certain period of time. It may be an implicit detachment timer or an implicit de-registration timer.

[0139] The mobile reachable timer is a timer used by the network to manage the maximum time until a UE managed by the network initiates the next MM procedure. If the network does not receive an MM message from the UE via the MM procedure before the mobile reachable timer expires, it may execute an implicit unregistered timer. If the network still does not receive an MM message before the implicit unregistered timer expires, it may implicitly manage the UE as unregistered.

[0140] Furthermore, Store and Forward (S&F) satellite operation (also referred to as Store and Forward (S&F) mode) may be an operation mode in which a serving satellite provides communication services to a UE for a period and / or geographic area in which it does not simultaneously connect to a terrestrial network via a feeder link or inter-satellite link (ISL).

[0141] In other words, S&F satellite operation may be an operating mode that enables a serving satellite to provide communication services to the UE even when discontinuous connectivity to the ground network is unavailable. In this case, the serving satellite may refer to the satellite that is interacting with the UE.

[0142] Furthermore, S&F mode is a mode in which the UE and / or RAN and / or core network equipment and / or functional units and / or entities and / or satellites perform S&F satellite operations. S&F mode may be a mode managed by each equipment and / or each functional unit and / or each entity, or a mode managed by any of the equipment and / or functional units and / or entities.

[0143] In the case of an uplink (also called UL), "store" may mean storing UL information from the UE on the satellite, and "forward" may mean transferring the stored UL information to the ground network. Similarly, in the case of a downlink (also called DL), "store" may mean storing DL information from the ground network on the satellite, and "forward" may mean transferring the stored UL information to the UE. In this specification, the storage and transfer satellite operations may be referred to as S&F, S&F function, S&F mode, or S&F operation mode. Supporting the S&F operation mode may be referred to as supporting the first function.

[0144] Furthermore, normal satellite operation (also referred to as normal satellite operation mode) may be a different operating mode from S&F satellite operation mode. Normal satellite operation may also be a mode with service link connectivity and feeder link connectivity. Furthermore, normal satellite operation may be a mode that does not perform the aforementioned store and forward operations. Normal satellite operation may also be an operating mode that provides communication services to UEs over a period and / or geographical area in which the satellites in service are simultaneously connected to the ground network via feeder links or inter-satellite links. Normal satellite operation may also be referred to as default satellite operation (also referred to as default satellite operation mode). In this specification, normal satellite operation may also be referred to as normal mode or normal operating mode.

[0145] A service link is the link, connection, or connectivity between a UE and a satellite. A broken service link means that communication between the UE and the satellite becomes impossible, or is in an impossible state. In other words, a broken service link can also be described as a state of no service link connectivity and / or a service link being unavailable. Conversely, a state where the service link is not broken, and / or a service link is established, and / or a service link is connected, can be described as a state of service link connectivity and / or a service link being available.

[0146] A feeder link is the link, connection, or connectivity between a satellite and a ground network. A broken feeder link means that communication between the satellite and the ground network becomes impossible. In other words, a broken feeder link can be described as a state of no feeder link connectivity and / or a feeder link being unavailable. Conversely, a state where the feeder link is not broken, and / or where the feeder link is established, and / or where the feeder link is connected, can be described as a state of feeder link connectivity and / or a feeder link being available.

[0147] Furthermore, a serving satellite may be a satellite that provides satellite connectivity to a UE (for example, provides a serving cell). Depending on the orbit, a serving satellite may cover a certain geographical area for a limited period of time. In other words, a UE with a serving satellite may be able to communicate via satellite, while a UE without a serving satellite may not be able to communicate via satellite. Also, a serving satellite operating in S&F mode may not have feeder link connectivity.

[0148] An S&F satellite E-UTRAN cell may be a cell with satellite E-UTRAN access technology that broadcasts information indicating that a base station (e.g., eNB) is operating in S&F mode. In other words, an S&F satellite E-UTRAN cell may be a type of satellite E-UTRAN cell. To put it another way, an S&F satellite E-UTRAN cell may be a satellite E-UTRAN cell. Note that E-UTRAN can be read as NG-RAN, and in this case, eNB may be gNB.

[0149] Furthermore, the UE and / or base station and / or network (e.g., MME, SGW, PGW, AMF, SMF, UPF, etc., hereinafter the same) may store information in advance and generate new information as needed. Also, when such information is transmitted and received between them, the receiving side may store the received information and act based on that information.

[0150] Furthermore, the UE, and / or satellite, and / or core network may operate in S&F mode or in normal mode. Note that when each device operates in S&F mode, this may be expressed as "S&F mode is active." When the device does not operate in S&F mode, this may be expressed as "operating in normal mode."

[0151] Furthermore, the ability to operate in S&F mode and normal mode may depend on whether only the UE (Underground Equipment), only the satellite, or only the NW (Network). For example, if only the satellite can operate in S&F mode and normal mode, then other components (in this case, the UE and NW) may not operate in either S&F mode or normal mode, and instead behave according to the mode in which the satellite operates. Similarly, if only the UE can operate in S&F mode and normal mode, then other components (in this case, the satellite and NW) may not operate in either S&F mode or normal mode, and instead behave according to the mode in which the UE operates. Similarly, if only the NW can operate in S&F mode and normal mode, then other components (in this case, the UE and satellite) may not operate in either S&F mode or normal mode, and instead behave according to the mode in which the NW operates.

[0152] Furthermore, for simplicity, when the UE and / or satellite and / or NW operate in S&F mode, it will be expressed as "when operating in S&F mode (when not operating in normal mode)," etc.

[0153] Furthermore, the UE, and / or satellite, and / or NW may switch between S&F mode and normal mode. For example, when the UE, and / or satellite, and / or NW are operating in normal mode, they may switch from normal mode to S&F mode while a procedure is being initiated and that procedure is in progress. Also, when the UE, and / or satellite, and / or core network are operating in S&F mode, they may switch from S&F mode to normal mode while a procedure is being initiated and that procedure is in progress.

[0154] Furthermore, there may be two configurations for a network capable of performing Store and Forward Satellite operations: a split mobile management system configuration that includes an access network to the satellite and some of the functions of the mobile management system, and a Full core network configuration that includes an access network to the satellite and all core network functions. The split mobile management system may also be expressed as split MME in the case of EPS and split AMF in the case of 5GS. Similarly, the Full core network may be expressed as Full CN, and further as Full EPC in the case of EPS and Full 5GC in the case of 5GS.

[0155] First, the system configuration of the split mobile management device will be explained using Figure 6. As shown in Figure 6, in satellite-based communication, the functions of the MME and AMF may be divided between the satellite and the ground network. In that case, the AMF and MME mounted on the satellite may be referred to as AMF-onboard141 and MME-onboard41, and the AMF and MME on the ground network may be referred to as AMF-ground142 and MME-ground42.

[0156] AMF-onboard141 and AMF-ground142 may be considered a single AMF140, and when referred to as AMF140, it may mean AMF-onboard141 and / or AMF-ground142. Similarly, MME-onboard41 and MME-ground42 may be considered a single MME40, and when referred to as MME40, it may mean MME-onboard41 and / or MME-ground42.

[0157] Furthermore, AMF-ground142 and MME-ground42 may be AMF and MME capable of normal connectivity via ground base stations without satellite. In other words, AMF-ground142 may be AMF140, and MME-ground42 may be MME40. In other words, AMF-ground142 and MME-ground42 may be functional units indistinguishable from conventional AMF and MME.

[0158] Furthermore, the UE, and / or base stations, and / or AMF, and / or SMF, and / or other core network devices or network functions may store information in advance and generate new information as needed. Also, when such information is sent and received between them, the receiving side may store the received information and act based on that information.

[0159] The Satellite ID may be information used to identify a satellite, broadcast from the access network using a System Information Block (SIB). The SIB is a message transmitted at the RRC layer. Here, the SIB may be system information or broadcast information.

[0160] An unavailable period is a period during which the UE is unavailable. Unavailability periods can be initiated by the UE or by the UE entering the satellite discontinuity. Entering the satellite discontinuity may also mean that the UE leaves the satellite's range. Furthermore, support for unavailable periods by the UE and / or network may also mean support for enhanced discontinuous coverage.

[0161] Each device (UE and / or network device) that supports the unavailability period and / or extended discontinuity range can anticipate, / or determine, and / or store the unavailability period. Furthermore, each device can send and receive information indicating the determined unavailability period. This information may also be expressed as information regarding the unavailability period, and may be the duration of the unavailability period and / or the start of the unavailability period. Determining the information indicating the unavailability period may be synonymous with determining the unavailability period.

[0162] Furthermore, information regarding the unavailability period may include the type of unavailability and / or whether the UE needs to notify the end of the unavailability period.

[0163] Discontinuous coverage refers to the range where the service link between the UE and the satellite is inactive. Specifically, when deploying connectivity services to a satellite-based network (such as E-UTRAN and / or NGRAN), there may be a gap between the range where the UE can be connected via satellite and the range where the next satellite connection can be provided; this gap is called a coverage gap. During a coverage gap, the access layer may be inactive, and this range may be considered a discontinuous coverage. The range where the UE can be connected via satellite may also be called coverage.

[0164] The discontinuous coverage maximum time offset is a value used to randomly set the transmission timing so that simultaneous transmission and reception from multiple UEs to the network does not occur when multiple UEs that have moved out of coverage due to satellite movement return from the discontinuous area.

[0165] Specifically, a UE with a maximum time offset for a discontinuity range may, if it has moved outside the coverage due to the discontinuity range and then returned to the coverage, and / or if it has received information from the network in a previous MM procedure indicating that the UE needs to report the end of the unavailability period, set a random value with the maximum time offset for the discontinuity range as its maximum value, start the maximum time offset timer for the discontinuity range, and after the offset timer expires, send an MM message to the network and execute the MM procedure.

[0166] The above MM procedure may be, for example, a registration procedure initiated by the UE and / or a tracking area update procedure initiated by the UE, and the MM message may be, for example, a registration request message and / or a TAU request message.

[0167] Access types may be classified as either 3GPP access types or non-3GPP access types.

[0168] RAT type refers to the transmission technology used in access networks for both 3GPP and non-3GPP access. RAT types may include, for example, NR, NB-IOT, Untrusted Non-3GPP, Trusted Non-3GPP, Trusted IEEE 802.11 Non-3GPP access, Wireline, Wireline-Cable, and Wireline-BBF.

[0169] Furthermore, in satellite connections, a RAT type may be used to distinguish it from other types of satellite connections. In the case of E-UTRAN satellite connections, the RAT type may be, for example, "WB-E-UTRAN(LEO)", "WB-E-UTRAN(MEO)", "WB-E-UTRAN(GEO)", "WB-E-UTRAN(OTHERSAT)", "NB-IoT(LEO)", "NB-IoT(MEO)", "NB-IoT(GEO)", "NB-IoT(OTHERSAT)", "LTE-M(LEO)", "LTE-M(MEO)", "LTE-M(GEO)", or "LTE-M(OTHERSAT)". In the case of NG-RAN satellite connections, the RAT type may be, for example, "NR(LEO)", "NR(MEO)", or "NR(GEO)".

[0170] The first identification information is information indicating whether or not the UE supports S&F mode. The first identification information may be information indicating that the UE supports S&F mode, or information indicating that the UE does not support S&F mode. The first identification information may be information included in the UE's capability information, or it may be the UE's capability information itself. The first identification information may be information requesting the network to provide communication services via S&F satellite operation. The first identification information may be included in the UE's capability information and transmitted or received.

[0171] The second identification information may be information indicating the configurations supported by the UE. Specifically, the second identification information may be information indicating whether or not the UE supports S&F satellite operation with a split mobile management device configuration. In other words, the second identification information may be information indicating that the UE supports S&F satellite operation with a split mobile management device configuration, or it may be information indicating that it does not support it.

[0172] Furthermore, the second identification information may indicate whether the UE supports S&F satellite operations using satellites equipped with a Full Core Network. In other words, the second identification information may indicate that the UE supports S&F satellite operations using satellites equipped with a Full Core Network, or it may indicate that it does not.

[0173] Furthermore, the information indicated by the second identification information may be indicated by a single identification information, or it may be divided into multiple identification information and transmitted / received separately. In other words, the second identification information may consist of identification information indicating whether or not the UE supports S&F satellite operation using a split mobile management device configuration, and identification information indicating whether or not the UE supports S&F satellite operation using a satellite equipped with a full core network. The second identification information may also be information included in the UE's capability information.

[0174] The sixth identification information is information indicating the time when the mobile management device-onboard sent a rejection message to reject the request from the UE for S&F when the feeder link is unavailable. The sixth identification information may also be Request time. Ground core network equipment may check whether a location update has arrived from another mobile management device after the time indicated in the sixth identification information. The sixth identification information may also be seventh identification information.

[0175] The seventh identification information may also be information indicating the time when the mobile management device-onboard receives an MM message and / or information contained in the MM message from the UE while operating in S&F mode, and then forwards that MM message to the mobile management device-ground when the feeder link becomes active. The ground core network device may check whether a location update has arrived from another mobile management device-onboard after the time indicated in the seventh identification information. The seventh identification information may also be the sixth identification information.

[0176] The tenth identification information is information indicating that a procedure initiated by a request message sent by the UE cannot be completed due to an S&F operation. The tenth identification information may be information indicating that the request indicated in the request message sent by the UE was rejected due to an S&F operation. The tenth identification information may be information indicating that the attach or TAU or registration procedure can be retried for the same PLMN on the next satellite path. Furthermore, the tenth identification information may be information indicating that the information contained in the UE's request message has been stored in the mobile management device on the satellite and that the information will be forwarded to the ground network after the feeder link is established.

[0177] The tenth identification information may be a reason value, for example, the EMM cause of EPS or the 5GMM cause of 5GS.

[0178] The tenth identification information, if it is an EMM cause for EPS, may indicate that "Procedure cannot be completed due to unavailable feeder link while MME is operating in S&F mode." The tenth identification information, if it is a 5GMM cause for 5GS, may indicate that "Procedure cannot be completed due to unavailable feeder link while AMF is operating in S&F mode."

[0179] The eleventh identification piece may be information indicating the value of the S&F Wait timer. The S&F Wait timer may be information indicating the amount of time the UE waits before attempting or retrying a NAS procedure (e.g., an attach procedure, a TAU procedure, or a registration procedure). In other words, while the S&F Wait timer is running, the UE may be controlled to prohibit and / or control and / or wait to send control messages and / or request messages to initiate a NAS procedure to the current PLMN and / or satellites belonging to the same PLMN, and / or to attempt and / or retry the NAS procedure. In other words, after the S&F Wait timer has expired, the UE may attempt or retry the NAS procedure to satellites belonging to the same PLMN. At this time, the satellite may be operating in S&F mode.

[0180] In other words, while the S&F Wait timer is running, the UE may be controlled to refrain from sending control messages and / or request messages to initiate NAS procedures on the S&F satellite E-UTRAN cell and / or satellite E-UTRAN cell, and / or to wait for attempts and / or retries of NAS procedures. In other words, after the S&F Wait timer expires, the UE may attempt or retry NAS procedures on the S&F satellite E-UTRAN cell and / or satellite E-UTRAN cell.

[0181] The UE may control the execution of the S&F Wait timer so that NAS procedures are not attempted or retried within the S&F satellite E-UTRAN cell and / or satellite E-UTRAN cell. In other words, the UE may, upon the expiration or termination of the S&F Wait timer, be in a state where the execution of NAS procedures within the S&F satellite E-UTRAN cell and / or satellite E-UTRAN cell is not restricted.

[0182] Furthermore, the NAS procedure to be retried may be, for example, a NAS procedure previously rejected by the 10th identification information, and may be, for example, a registration procedure and / or an attachment procedure and / or a tracking area update (TAU procedure).

[0183] Here, the S&F Wait timer may also be expressed as the Wait timer. The value of the S&F Wait timer may be a value indicating the duration of the S&F Wait timer, or a value indicating the duration of the S&F Wait time.

[0184] The S&F Wait timer may also be expressed as S&F wait time or wait time. The duration of the S&F Wait timer may be interpreted as the duration of the S&F wait time, and vice versa. The S&F Wait timer may also be T3451 in EPS.

[0185] In other words, the value of S&F wait time may be a value indicating the duration of the S&F wait time. The 11th identifying information may include a value indicating the S&F wait time duration, or the 11th identifying information may be the S&F wait time duration.

[0186] The S&F wait timer may be started or executed when the UE is in the registered state and / or the registration start state. Alternatively, the S&F wait timer may be started or executed when the UE is in the unregistered state and / or the registration failed state (5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH state).

[0187] The 11th piece of identification information may also indicate the upper and / or lower limits of the S&F Wait timer value. Furthermore, the satellites targeted by the S&F Wait timer indicated by the 11th piece of identification information are not limited to these, but may be one or more satellites indicated by the 12th piece of identification information described later. Note that the upper limit may mean the maximum value.

[0188] The 12th identification information may be information comprising one or more satellite IDs. Satellites indicated by one or more satellite IDs included in the 12th identification information may belong to the same PLMN. The 12th identification information may also be information indicating one or more satellites from which the UE attempts or retries NAS procedures (MM procedures and / or SM procedures). The 12th identification information may also be information indicating one or more satellites from which the UE transmits MT data, in other words, from which the UE receives MT data.

[0189] For example, the 12th identification information may be information indicating one or more satellites on which the UE can attempt or retry the attach or TAU or registration procedure after the S&F Wait timer has expired. The 12th identification information may be a list of Satellite IDs, which may be referred to as a list of Satellite IDs, a satellite IDs list, a monitoring list, or an S&F monitoring list.

[0190] The 12th identification information may include at least a Satellite ID indicating the satellite that transmitted the 12th identification information. The 12th identification information may also be information indicating a satellite that the UE prohibits from attempting or retrying registration procedures (e.g., attach procedures, TAU procedures, or registration procedures) while the S&F Wait timer is running.

[0191] The 13th identifying information is information indicating the estimated and / or expected time required from the time data is transmitted from the UE until it is delivered to the ground network function unit and / or network element, and may be the Uplink S&F estimated delivery time. The Uplink S&F estimated delivery time may also be expressed as estimated delivery time, estimated time, Estimated UL Delivery Time, Estimated S&F UL Delivery Time, etc. The 13th identifying information may be information indicating a time value.

[0192] Furthermore, items 11 to 13 may be configured within a single IE; for example, at least one of the identification information items 11 to 13 may be configured and transmitted within the S&F satellite operation parameters IE.

[0193] In other words, the transmission or reception of at least one of the identification information items 11 through 13 may be considered equivalent to the transmission or reception of S&F satellite operation parameters IE.

[0194] The S&F satellite operation parameters IE may include presence indications for each of the 11th to 13th identification pieces, indicating whether or not each piece of information is included in the IE. In other words, the S&F satellite operation parameters IE may include information indicating whether or not the 11th identification piece is included, information indicating whether or not the 12th identification piece is included, and information indicating whether or not the 13th identification piece is included.

[0195] The S&F satellite operation parameters IE may include information indicating and / or requesting whether to delete the 11th through 13th identification information stored by the UE. In other words, the S&F satellite operation parameters IE may include information indicating whether to delete the 11th identification information stored by the UE, information indicating whether to delete the 12th identification information stored by the UE, and information indicating whether to delete the 13th identification information stored by the UE.

[0196] The information indicating and / or requesting whether to delete the 11th to 13th identification information stored by the aforementioned UE may be the same as the information indicating whether each of the 11th to 13th identification information is included in the IE. For example, the S&F satellite operation parameters IE may include information indicating one of the following: first information indicating that the 11th identification information is not included, second information indicating that the 11th identification information is not included and that the UE is requesting the deletion of the 11th identification information stored by the UE, or third information indicating that the 11th identification information is included. The same may apply to the 12th and 13th identification information.

[0197] The 14th identifier may be information indicating that the running S&F wait timer should not be stopped. The 14th identifier may be a reason value, for example, an EMM cause for EPS or a 5GMM cause for 5GS. The 14th identifier may also be included in the S&F satellite operation parameters IE.

[0198] [3. Description of Each Procedure] Next, the procedures used in the embodiments of this application will be described. The procedures used in the embodiments include at least one of the following: a registration procedure, an attachment procedure, a tracking area update procedure, a non-registration procedure, and / or a detachment procedure. In other words, multiple procedures may be performed in combination within the embodiments.

[0199] For example, the UE may perform a registration or attach procedure, and after the UE transitions to the registered state, the registration or TAU procedure may be performed at any time. Furthermore, if the UE is in a registered state, the unregistration procedure and / or detach procedure may be performed at any time.

[0200] Each procedure may be executed multiple times during the embodiment. For example, the registration procedure and / or the TAU procedure and / or the non-registration procedure and / or the detach procedure may be executed periodically, regardless of whether other procedures are being executed.

[0201] In each embodiment, the explanation will be based on the example where the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are configured as the same device (i.e., the same physical hardware, the same logical hardware, or the same software), as shown in Figure 2. However, the contents described in this embodiment are also applicable when these are configured as different devices (i.e., different physical hardware, different logical hardware, or different software). For example, data may be transmitted and received directly between them, or data may be transmitted and received via the N26 interface between the AMF and MME, or data may be transmitted and received via the UE. The following describes each procedure.

[0202] [3.1. Registration Procedure / Attachment Procedure / Tracking Area Update Procedure (TAU Procedure)] First, the procedures for a UE to register with and / or attach to a system (e.g., 5GS or EPS) and / or to notify and / or update the status of the UE will be explained using Figure 7. Hereinafter, "this procedure" refers to the procedure for a UE to register with and / or attach to a system and / or to notify and / or update the status of the UE, and may also be expressed as an MM procedure. For example, this procedure may be a registration procedure, an attach procedure, a tracking area update procedure (TAU), or any other procedure. Note that the tracking area update procedure is also called a TAU procedure.

[0203] Figure 7 shows a procedure performed via a satellite that constitutes a split mobile management system, in which part of the mobile management system is mounted on the satellite. However, the configuration of this procedure is not limited to this; it may also be a procedure performed via a satellite that constitutes a Full CN (core network), or data may be sent and received with the ground core network without using a satellite.

[0204] The registration procedure is a process initiated by the UE to register with Access Network B and / or Core Network B and / or DN. The UE can perform this procedure at any time, for example, when powered on, if it is not already registered with the network. In other words, the UE can start this procedure at any time as long as it is in the unregistered state (5GMM-DEREGISTERED state). Furthermore, each device (especially the UE and AMF) can transition to the registered state (5GMM-REGISTEDED state) upon completion of the registration procedure.

[0205] The attach procedure is a procedure initiated by the UE to register with access network_A and / or core network_A and / or DN. The UE can perform this procedure at any time, for example, when powered on, if it is not registered with the network. In other words, the UE can start this procedure at any time as long as it is in the unregistered state (EMM-DEREGISTERED state). Furthermore, each device (especially the UE and MME) can transition to the registered state (EMM-REGISTEDED state) based on the completion of the attach procedure.

[0206] Furthermore, each registration status may be stored and / or managed by each device for each access. Specifically, each device may independently store and / or manage the registration status for 3GPP access (registered or unregistered) and the registration status for non-3GPP access.

[0207] Furthermore, the registration procedure and TAU procedure may also be a procedure for updating the location registration information of the UE in the network, and / or for the UE to periodically notify the network of the status of the UE, and / or for updating specific parameters related to the UE in the network.

[0208] A UE may initiate the registration process when it moves across a registered Tracking Area (TA). In other words, a UE may initiate the registration process when it moves to a TA different from the TA indicated in its TA list (TAI list or registered area). Furthermore, a UE may initiate this process when a running backoff timer or other timer expires.

[0209] In 5GS, the procedure for a UE to transition from a state where it is not registered with the network to a state where it is registered may be called the initial registration procedure or the registration procedure for initial registration. Furthermore, the registration procedure performed when the UE is registered with the network may be called the registration procedure for mobility and periodic registration update or the mobility and periodic registration procedure.

[0210] Furthermore, the registration procedures for mobility registration update and the registration procedure for periodic registration update may be separate procedures.

[0211] On the other hand, in EPS, the procedure for transitioning a UE from a state where it is not registered with the network to a state where it is registered may be called an attach procedure, and the procedure for updating location information and / or registration information of the UE, which is performed when the UE is registered with the network, may be called a standard or periodic TAU procedure (Normal and periodic tracking area updating procedure).

[0212] Furthermore, if a TAU procedure is performed for the purpose of movement, it may be called a normal tracking area updating procedure, and if it is performed periodically, it may be called a periodic tracking area updating procedure.

[0213] In Figure 7, the base station equipment may be base station equipment such as eNB and / or gNB, and may be a base station equipment installed on the ground or a base station equipment mounted on a satellite. The mobile management equipment may be AMF140 and / or MME40, and may be a mobile management equipment installed on the ground, a mobile management equipment mounted on a satellite, or a combination of a mobile management equipment installed on the ground and a mobile management equipment mounted on a satellite.

[0214] The mobile management device-onboard may be AMF-onboard141 and / or MME-onboard41, and may be any mobile management device mounted on a satellite. The mobile management device-ground may be AMF-ground142 and / or MME-ground42, and may be any mobile management device installed on the ground. The subscriber / approval management device may be HSS50 and / or UDM150 and / or AUSF, and may be any network device installed on the ground for managing subscribers and / or approvals.

[0215] Furthermore, when referring to a mobile management device for a terrestrial network, it may mean the mobile management device and / or mobile management device-ground. Also, the mobile management device may include mobile management device-onboard and / or mobile management device-ground.

[0216] The mobile management device-onboard and the mobile management device-ground may be connected by a feeder link. In other words, the mobile management device-onboard has connectivity with the mobile management device-ground. Similarly, the mobile management device-ground has connectivity with the mobile management device-onboard.

[0217] First, UE_A10 initiates this procedure by sending a request message to the movement management device (S600)(S602)(S604). For example, UE_A10 may initiate a registration procedure, an attachment procedure, or a TAU procedure by sending a registration request message to AMF140, or an attach request message or a tracking area update request message (TAU request message) to MME40.

[0218] Specifically, in 5GS, the UE sends an RRC message containing a registration request message to the 5G AN120 (or gNB) (S600). Alternatively, in EPS, the UE sends an RRC message containing an attach request message or a TAU request message to the E-UTRAN80 (or eNB) (S600). The 5G AN120 (or gNB) and / or E-UTRAN80 (or eNB) may send or forward the received NAS message to the AMF140 and / or MME40.

[0219] Note that registration request messages are NAS messages sent and received over the N1 interface. On the other hand, attach request messages and TAU request messages are NAS messages sent and received using the LTE-Uu interface and the S1-MME interface.

[0220] Furthermore, RRC messages may be control messages transmitted between the UE and the access network or base station. Also, NAS messages are processed at the NAS layer, and RRC messages are processed at the RRC layer. Note that the NAS layer is a higher layer than the RRC layer.

[0221] Hereinafter, registration request messages, attach request messages, and TAU request messages will be referred to as request messages. In other words, unless otherwise specified, request messages refer to registration request messages and / or attach request messages and / or TAU request messages sent from the UE. Here, UE_A10 may include at least one of the identification information from the first to the second identification information when sending request messages and / or RRC messages.

[0222] UE_A10 may include UE capability information in its request message to inform the network of the capabilities that UE_A10 supports. Here, the UE capability information may be the 5G MM capability IE for 5GS or the UE network capability IE for EPS. The first and / or second identification information may be the information contained in the 5G MM capability IE for 5GS and / or the UE network capability IE for EPS.

[0223] In other words, if the UE supports the first function and / or if the UE has the first function available, the UE may set the first identification information to indicate that it supports the first function (S&F satellite operation supported) and transmit it; if the UE does not support the first function, the UE may set the first identification information to indicate that it does not support the first function (S&F satellite operation not supported).

[0224] If the UE supports S&F satellite operation with a split mobile management device configuration, it may set information indicating that it supports S&F satellite operation with a split mobile management device configuration in the second identification information and transmit it; if the UE does not support S&F satellite operation with a split mobile management device configuration, it may set information indicating that it does not support S&F satellite operation with a split mobile management device configuration in the second identification information and transmit it.

[0225] If the UE supports S&F satellite operation using a satellite equipped with a Full Core Network, it may set and transmit information in the second identification information indicating that it supports S&F satellite operation using a satellite equipped with a Full Core Network. If the UE does not support S&F satellite operation using a satellite equipped with a Full Core Network, it may set and transmit information in the second identification information indicating that it does not support S&F satellite operation using a satellite equipped with a Full Core Network.

[0226] If the UE does not support S&F satellite operation using a split mobile management device configuration or S&F satellite operation using a satellite equipped with a full core network, it may set and transmit information indicating that it does not support S&F satellite operation in the second identification information, or it may not transmit the second identification information.

[0227] Furthermore, the UE capability information may include one or more capability information, and may indicate whether or not capabilities other than the first function are supported. For example, the UE capability information may include information indicating whether or not unavailability periods are supported, and / or whether or not extended discontinuous ranges are supported.

[0228] Specifically, if the UE supports downtime, it may set information in its capability information indicating that the UE supports downtime; if the UE does not support downtime, it may set information indicating that the UE does not support downtime.

[0229] Similarly, if the UE supports extended discontinuous ranges, the UE may set information in its capability information indicating that the UE supports extended discontinuous ranges, and if the UE does not support extended discontinuous ranges, the UE may set information indicating that the UE does not support extended discontinuous ranges.

[0230] UE_A10 may include a second identifier in the request message if the request message to be sent is a retransmission of a request message that was rejected due to the S&F operation mode. Alternatively, UE_A10 may set the second identifier to information indicating that it is a retransmission of a request message that was rejected due to the S&F operation mode, and then send it.

[0231] UE_A10 may include the SM message in an SM message container IE and combine it with the request message. Here, the SM message container IE may be the ESM message container IE of the EPS or something else. The SM message to be included in the SM message container IE may be, for example, a PDU session establishment request message and / or a PDN connectivity request message.

[0232] For example, in EPS, if the UE or MME does not support a registration state without a PDN connection (EMM-REGISTERD), or if the UE wants to request a PDN connection in this procedure (e.g., the attach procedure), the UE may send a request message for this procedure along with an SM message container IE that includes a PDN connectivity request message.

[0233] For example, in EPS, if the UE and MME support a registration state without a PDN connection (EMM-REGISTERD), and the UE does not want to request a PDN connection in this procedure (e.g., the attach procedure), the UE may send a request message for this procedure along with an SM message container IE that includes a dummy message. Alternatively, the UE may send a request message for this procedure that does not include an SM message container IE.

[0234] UE_A10 may also transmit these identifiers and / or IEs in a different control message, such as a control message at a lower layer than the RRC layer (e.g., MAC layer, RLC layer, PDCP layer). Furthermore, by transmitting these identifiers, UE_A10 may indicate that UE_A10 supports each function, indicate a request from the UE, or both. Additionally, if multiple identifiers are transmitted and received, two or more of these identifiers may be combined into one or more identifiers. The information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identifier, or as different identifiers.

[0235] UE_A10 may include other identification information in the request message and / or the RRC message containing the request message, such as the UE ID and / or PLMN ID.

[0236] Furthermore, UE_A10 may select and decide whether or not to transmit this identification information to the network based on the UE's capability information, and / or UE policies, and / or the UE's status, and / or the user's registration information, and / or the context held by the UE, etc.

[0237] When the access network (5G AN120 (or gNB) or E-UTRAN (or eNB)) receives an RRC message containing a request message, it selects a mobility management device (e.g., AMF, MME) to forward the request message (S602). The access network may select a mobility management device based on one or more pieces of identification information contained in the request message and / or the RRC message containing the request message.

[0238] For example, the access network may select a mobility management device based on the PLMN ID. Specifically, the access network may select a mobility management device for the requested PLMN based on the PLMN ID that indicates the PLMN requested by the UE.

[0239] The method for selecting a mobile management device is not limited to this, and the access network may select a mobile management device based on other conditions. The access network extracts the request message from the received RRC message and forwards the request message to the selected mobile management device (S604). The access network may also forward identification information included in the RRC message but not in the request message to the selected mobile management device along with the request message (S604).

[0240] Here, if this procedure is performed using a UE and / or satellite and / or core network equipped with the capability to operate in S&F mode, the access network and / or base station equipment may be located on the satellite, and the mobility management equipment selected by the access network may be a mobility management equipment-onboard (e.g., MME-onboard41 or AMF-onboard141).

[0241] The mobile management device-onboard may transmit information received from the UE via the access network to the mobile management device on the ground network when the UE and / or satellite and / or core network are operating in normal mode (S605). Specifically, for example, the MME-onboard41 may transmit or forward information received from the UE via the E-UTRAN80 (or eNB) to the MME-ground142 or MME140 on the ground network. Similarly, the AMF-onboard141 may transmit or forward information received from the UE via the 5G AN120 (or gNB) to the AMF-ground142 or AMF140 on the ground network.

[0242] Here, the information received from the UE may be a request message or an RRC message containing a request message, and the request message may contain at least one of the first to second identification information.

[0243] The mobile management device-onboard may transmit to the mobile management device-ground the information received from the UE via the access network and / or the sixth identification information and / or the seventh identification information if the feeder link becomes available after being unavailable, and if the UE and / or the satellite and / or core network also support S&F mode (S605). In other words, the mobile management device-ground may receive the information received from the UE and / or the sixth identification information and / or the seventh identification information from the mobile management device-onboard after the feeder link becomes available after being unavailable.

[0244] The mobile management device-ground may decide to initiate the UE authentication procedure and / or the procedure for obtaining UE registration information based on the information received from the UE via the mobile management device-onboard (S606). The specific behavior of the mobile management device-ground is described below. Note that the following MM messages may be request messages.

[0245] If the mobile management device-ground receives an MM message and sixth identification information from the UE, it may check whether it has received an MM message from another mobile management device on another satellite (another mobile management device-onboard) after the time indicated in the sixth identification information, and whether it has performed the UE authentication procedure and / or the procedure for obtaining UE registration information based on the receipt of an MM message from another mobile management device-onboard.

[0246] If the mobile management device-ground has received an MM message from another mobile management device-onboard after the time indicated in the sixth identification information, or has performed the UE authentication procedure and / or UE registration information acquisition procedure in conjunction with the receipt of the MM message, it may skip the MM message from the UE received via the mobile management device-onboard in S605 and / or the UE authentication procedure (S607) and / or UE registration information acquisition procedure (S608) based on the information contained in the MM message.

[0247] On the other hand, if the mobile management device-ground has not received an MM message from another mobile management device-onboard after the time indicated in the sixth identification information, or has not performed the UE authentication procedure and / or the UE registration information acquisition procedure in conjunction with the receipt of the MM message, it may decide in S605 to start the UE authentication procedure (S607) and / or the UE registration information acquisition procedure (S608) based on the MM message from the UE and / or the information contained in the MM message received via the mobile management device-onboard.

[0248] Examples of specific UE authentication procedures (S607) and UE registration information acquisition procedures (S608) are described below. For example, if AMF-ground142 or AMF140 decides to initiate the UE authentication procedure, it may select an AUSF based on the UE's SUPI or SUCI. AMF-ground142 or AMF140 may send the UE's SUPI or SUCI to the selected AUSF and request the authentication procedure.

[0249] AUSF selects UDM, and UDM may obtain the authentication data. Once the UE is authenticated, AUSF sends security-related information about the UE to AMF-ground142 or AMF140. If AUSF received SUCI from AMF-ground142 or AMF140 during the authentication process, AUSF may provide SUPI to AMF-ground142 or AMF140 only after successful authentication.

[0250] Furthermore, if MME-ground142 or MME140 decides to initiate the UE authentication process, the UE selects the HSS and obtains security information from the HSS. Upon successful authentication, all NAS messages become protected by NAS security.

[0251] After the authentication procedure is successful, if the terrestrial network mobile management device does not have a UE context, it may perform a procedure to obtain the UE context and / or UE registration information from the subscriber management device (e.g., HSS50 or UDM150) (S608).

[0252] Specifically, AMF-ground142 or AMF140 may register with the UDM if the AMF has changed since the previous registration procedure, or if this registration procedure is an initial registration procedure or a registration procedure for emergency services, or if the UE has included a SUPI in the request message that does not refer to a valid context within AMF-ground142 or AMF140, or if the UE is registering with the same AMF that it has already registered with for non-3GPP access.

[0253] If AMF-ground142 or AMF140 has successfully registered with UDM and does not have the UE registration information and / or the information contained in the UE registration information, it may obtain the UE registration information and / or the information contained in the UE registration information from UDM.

[0254] Furthermore, MME-ground142 or MME140 may send an Update Location Request to HSS if the MME has changed since the last detachment, or if there is no valid registration context for the UE within MME-ground142 or MME140, or if the UE provides a GUTI that does not refer to an IMSI or a valid context within MME-ground142 or MME140. The Update Location Request may include, for example, the MME ID and / or IMSI. HSS may send an Update Location Ack containing the UE's IMSI and registration information to MME-ground142 or MME140 and return an Ack to the Update Location Request (also known as an Update Location message).

[0255] If this procedure is performed via satellite, and if the UE and / or satellite and / or core network are operating in normal mode and / or if feeder link connectivity is available, the mobile management device of the ground network may transmit and / or transfer the UE authentication results and / or UE registration information obtained in S607 and S608 to the mobile management device-onboard (S609).

[0256] The mobile management device may decide whether to accept or reject a request from a UE based on the authentication procedure and / or the acquisition of the UE's registration information. The information used to decide whether to accept or reject a request from a UE is not limited to the above, and the mobile management device may decide whether to accept or reject a request from a UE based on one or more pieces of information acquired by the mobile management device of the terrestrial network during this procedure. Based on the decision to accept or reject a request from a UE, the mobile management device may generate a control message (acceptance message or rejection message) which is a response message to the request from the UE. Specifically, the mobile management device may generate an acceptance message when accepting a request from a UE, and a rejection message when rejecting a request.

[0257] If this procedure is performed via satellite, and further if the UE and / or satellite and / or core network are operating in normal mode and / or feeder link connectivity is available and / or S&F mode is inactive, the ground network mobility management device may send the generated control message to mobility management device-onboard (S609).

[0258] If this procedure is performed via satellite, and the UE and / or satellite and / or core network are operating in S&F mode and / or feeder link connectivity is unavailable, the mobile management device of the ground network may store the UE authentication results and / or UE registration information obtained in S607 and S608, and transmit and / or forward them after feeder link connectivity becomes available (S609).

[0259] The movement management device may send an RRC message to the UE as a response to the request message, including an acceptance message or a rejection message (S610). The movement management device may send an acceptance message if it accepts the request from the UE, and a rejection message if it rejects it.

[0260] The movement management device-onboard may forward control messages received from the movement management device-ground, or it may generate a control message to send to the UE based on the control message and / or information received from the movement management device-ground, and send it to the UE. For example, the movement management device-onboard may generate a new control message by adding information to the control message received from the movement management device-ground, or it may decide whether or not to accept a request from the UE based on the control message and / or information received from the movement management device-ground, and generate a control message.

[0261] Acceptance messages may be messages indicating acceptance of a request message from the UE, and may include registration accept messages, attach accept messages, and tracking area update accept messages. Rejection messages may be messages indicating rejection of a request message from the UE, and may include registration reject messages, attach reject messages, and tracking area update reject messages.

[0262] When the mobile management device-onboard receives a request message from the UE in S604, if the UE and / or satellite and / or core network are operating in S&F mode, the mobile management device-onboard and / or each device in the network may reject the request from the UE without performing the procedures from S605 to S609. In this case, the mobile management device-onboard may send an RRC message containing a rejection message to the UE (S610). In this case, the mobile management device-onboard may be rejecting the request from the UE because it is in S&F mode.

[0263] Alternatively, when the mobile management device-onboard receives a request message from the UE in S604, if the UE and / or satellite and / or core network are operating in S&F mode but the feeder link connectivity is about to become active, the mobile management device-onboard and / or each device in the network may not skip the procedures from S605 to S609, but wait for the feeder link connectivity to become active and then execute the procedures from S605 to S609, or send an acceptance message in S610 (it may not send a rejection message).

[0264] The time the movement management device-onboard waits for the feeder link connectivity to become active may be, for example, 15 seconds or less, which is the value of T3510 in 5GS; 15 seconds or less, which is the value of T3410 and / or T3430 in EPS; 6 seconds or 11 seconds or less, which is the value of T3550 in 5GS; or 6 seconds or 18 seconds or less, which is the value of T3450 in EPS.

[0265] Alternatively, if the UE and / or satellite and / or RAN and / or core network support S&F mode, and / or the UE and / or satellite and / or RAN and / or core network operate in S&F mode, and / or the mobile management device-onboard receives a request message from the UE in S604, and / or it is expected that the feeder link connectivity will soon become active, and / or it is expected that the mobile management device-onboard and / or each device in the network will be able to successfully complete this procedure even if they wait for the feeder link connectivity to become active before performing steps S605 through S609, the mobile management device-onboard and / or each device in the network may wait for the feeder link connectivity to become active before performing steps S605 through S609, or send an acceptance message in S610 (they do not need to send a rejection message).

[0266] The mobile management device-onboard may determine the value of the S&F Wait timer and / or the value of the uplink S&F estimated delivery time if the UE and / or satellite and / or RAN and / or core network support S&F mode, and / or if the UE and / or satellite and / or RAN and / or core network operate in S&F mode.

[0267] The mobile management device-onboard may further determine the value of the periodic update timer, and / or the value of an unspecified unregistered timer, and / or the value of the mobile reachable timer, based on the determined value of the S&F Wait timer and / or the value of the uplink S&F estimated delivery time.

[0268] The movement management device may include at least one of the identification information items 10 to 13 in the control message (acceptance message or rejection message) and / or RRC message sent to the UE. The control message may also include an SM message container IE.

[0269] If the movement management device-onboard rejects a request from the UE in S&F mode, it may store the information contained in the request message from the UE, and after the feeder link connection becomes possible and the feeder link is available, it may execute S605 to S609 which were not executed (skipped). In that case, the movement management device-onboard may send and / or forward the request message from the UE to the movement management device-ground, adding information indicating that the movement management device-onboard has already responded to the UE (S605).

[0270] If the movement management device-ground receives information indicating that the movement management device-onboard has already responded to the UE in response to the request message from the UE, it does not need to decide whether to accept or reject the request indicated in the request message from the UE, and / or does not need to send a control message to the movement management device-onboard (S609).

[0271] Registration acceptance messages and registration rejection messages are NAS messages sent and received over the N1 interface. On the other hand, attach acceptance messages, attach rejection messages, TAU acceptance messages, and TAU rejection messages are NAS messages sent and received using the LTE-Uu interface and the S1-MME interface.

[0272] If the mobile management device-onboard rejects a request from the UE for S&F operations, it may include at least one of the 10th to 13 identification information in the rejection message or the RRC message containing the rejection message. The mobile management device-onboard may decide whether or not to transmit at least one of the 10th to 13 identification information based on information received from the UE and / or the access network and / or the first identification information.

[0273] For example, if the movement management device-onboard receives a first identification information which is information indicating that the UE supports the S&F operation mode, it may transmit at least one of the 10th to 13th identification information.

[0274] On the other hand, if the mobile management device-onboard receives a first identification information indicating that the UE does not support S&F operation mode, or does not receive a first identification information indicating that the UE supports S&F operation mode, it does not need to transmit the 10th to 13th identification information. In that case, the mobile management device-onboard may include a reason value indicating congestion (EMM cause or 5GMM cause) and a backoff timer value (T3346) in the rejection message or the RRC message containing the rejection message.

[0275] UE_A10 receives a control message and / or one or more pieces of information contained in the control message from the network. Based on the reception of the control message and / or one or more pieces of information contained in the control message, UE_A10 may recognize the received information.

[0276] Specifically, a UE that receives the 10th identification information may recognize that this procedure cannot be completed due to an S&F operation. A UE that receives the 10th identification information may recognize that this procedure can be retried to attach to or TAU or register with the same PLMN on the next satellite path. A UE that receives the 10th identification information may recognize that the information contained in the request message sent in this procedure is stored in the satellite's AMF or MME, and that the stored information is forwarded to the ground network when the feeder link becomes available. A UE that receives the 10th identification information may store information about the satellite performing this procedure in the stored 12th identification information.

[0277] Based on the receipt of the 11th identification information and / or the receipt of a control message containing the 11th identification information, the UE may store the value indicated in the 11th identification information. Based on the receipt of the 11th identification information and / or the fact that the NW and / or UE are controlled in S&F mode, the UE may execute and / or start the S&F wait timer using the value indicated in the 11th identification information and / or the stored S&F wait timer value.

[0278] Upon receiving the 11th identification information contained in the acceptance message, any running S&F wait timer may be stopped, and an S&F wait timer using the value indicated by the 11th identification information may be started immediately, or the S&F wait timer may be started after the NW and / or UE are controlled in S&F mode.

[0279] If an eleventh identifier is received in the rejection message, any running S&F wait timer may be stopped, and an S&F wait timer using the value indicated by the eleventh identifier may be immediately started.

[0280] Based on the UE's receipt of the 11th Identification Information, the UE may associate and store, and / or manage and run, the PLMN ID and / or Satellite ID with the S&F wait timer. The S&F wait timer may be associated with one or more Satellite IDs, which may be satellite IDs indicating the satellite that transmitted the 11th Identification Information, or one or more satellite IDs that are included in and constitute the S&F Monitoring list indicated by the 12th Identification Information.

[0281] Based on the receipt of the 11th identification information, the UE may stop the running S&F Wait timer and / or delete the stored value of the S&F Wait Timer. Alternatively, even if the UE receives the 11th identification information, it may, based on its own decision, not delete the stored value of the S&F Wait Timer and / or stop the running S&F Wait Timer. In other words, even if the UE receives the 11th identification information, it may, based on its own decision, not update the value of the S&F Wait Timer.

[0282] In other words, even if the UE receives the 11th identification information, it may maintain the value of the S&F wait timer it stores and ignore the value indicated in the received 11th identification information.

[0283] While the S&F wait timer is running, the UE may control the satellites indicated by the PLMN ID associated with the running S&F wait timer and / or by one or more Satellite IDs to prevent the UE from retrying sending request messages, and may also control the satellites to prevent attempts to perform NAS procedures by sending other MM messages.

[0284] Upon the expiration of the S&F wait timer, the UE may retry sending a request message to the PLMN and / or satellites indicated by the PLMN ID associated with the S&F wait timer and / or one or more Satellite IDs, or may attempt NAS procedures by sending other MM messages.

[0285] Based on the receipt of the 12th identification, the UE may delete any stored S&F Monitoring Lists and store the received 12th identification. Alternatively, if the UE stores an S&F Monitoring List, the UE may, at its discretion, not delete the stored S&F Monitoring List even if it receives the 12th identification. In other words, the UE may, at its discretion, not update the S&F Monitoring List even if it receives the 12th identification. To put it another way, the UE may, even if it receives the 12th identification, maintain the stored S&F Monitoring List and ignore the value indicated in the received 12th identification.

[0286] The UE may decide whether or not to update the S&F Monitoring List based on its own judgment. For example, if the S&F Monitoring List indicated by the 12th identification information received by the UE is older than the S&F Monitoring List stored by the UE, the UE may decide not to update the stored S&F Monitoring List. In other words, if the S&F Monitoring List stored by the UE is newer than the S&F Monitoring List indicated by the 12th identification information received, the UE may decide not to update the stored S&F Monitoring List.

[0287] In other words, if the UE finds that the S&F Monitoring List indicated by the 12th identification information it receives is newer than the S&F Monitoring List it stores, it may decide to update the S&F Monitoring List it stores. In other words, if the UE finds that the S&F Monitoring List it stores is older than the S&F Monitoring List indicated by the 12th identification information it receives, it may decide to update the S&F Monitoring List it stores.

[0288] Alternatively, based on information pre-configured in the UE, such as whether the UE is an IoT device, the UE may decide not to update the S&F Monitoring List it stores. For example, the UE may be configured to store only the 12th identification information received from a specific satellite.

[0289] If the UE does not remember the received 12th identification information, it may delete the stored S&F Monitoring List or retain the memory.

[0290] Upon receiving the 13th identification information, the UE may recognize the estimated and / or expected time required from transmission until the data is delivered to the ground network function unit and / or network element. Based on the receipt of the 13th identification information, the UE may start counting a timer for the uplink S&F estimated delivery time using the value of the 13th identification information.

[0291] A UE that has received at least one of the identification pieces from the 10th to 13 may activate S&F mode based on the receipt of the information and / or a message containing the received information. At this time, S&F mode may be associated with a satellite ID indicating the satellite that sent the message, a list of Satellite ID(s) shown in the 12th identification piece, a PLMN, an access type, a registered tracking area list consisting of one or more tracking areas, a RAT type, or a combination of these pieces of information.

[0292] Furthermore, the mobility management device may select and determine the identification information to include in the control message and / or the information to be notified based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the mobility management device.

[0293] For example, the movement management device may include in the control message the determined and / or updated values ​​of the periodic update timer and / or the implicit unregistered timer, based on the determined S&F Wait timer value and / or the uplink S&F estimated delivery time value. The UE may receive the control message and / or the RRC message containing the control message, which include the values ​​of the periodic update timer and / or the implicit unregistered timer.

[0294] The UE may store the received update timer value and / or the implicit unregistered timer value. If the UE has already stored the update timer value and / or the implicit unregistered timer value, it may delete the old value before storing the newly received value. In other words, the UE may update and store the received update timer value and / or the implicit unregistered timer value.

[0295] Furthermore, the mobile management device may indicate that the UE's request has been accepted by sending a registration acceptance message based on the received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, or it may indicate that the UE's request has been rejected by sending a registration rejection message.

[0296] The UE receives a control message via the access network (S610). If the control message is an acceptance message, the UE can recognize that its request in the request message has been accepted and can also recognize the content of various identification information contained in the acceptance message.

[0297] Alternatively, if the control message is a rejection message, the UE can recognize, upon receiving the rejection message, that its request via the request message has been rejected, and can also recognize the content of various identification information contained in the rejection message. Furthermore, if the UE does not receive a control message after a predetermined period has elapsed since sending the request message, it may recognize that its request has been rejected.

[0298] Furthermore, if the control message is an acceptance message, the UE may send a completion message to the AMF or MME via the access network as a response message to the acceptance message. Here, the completion message is a NAS message sent and received on the N1 interface, or the LTE-Uu interface and S1-MME interface, but is included in the RRC message sent and received between the UE and the access network.

[0299] The completion message may be a registration completion message, an attachment completion message, or a tracking area update completion message.

[0300] The movement management device receives a completion message via the access network. Each device also completes this procedure based on the sending and receiving of control messages and / or completion messages.

[0301] Furthermore, each device may transition to or maintain a state based on the transmission and reception of control messages and / or information contained in those control messages. Alternatively, the transition of each device to a state may be based on the transmission and reception of completion messages or the completion of this procedure. Note that transitioning to a state may be synonymous with entering a state.

[0302] For example, each device may transition to or maintain a state in which the UE is registered with the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the sending and receiving of registration acceptance messages and / or registration completion messages, or may transition to or maintain a state in which the UE is not registered with the network on the access for which a registration rejection message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) or a state in which the UE is registered with the network based on the sending and receiving of registration rejection messages and / or reason values.

[0303] Alternatively, each device may transition to a state where the UE is registered with the network (EMM_REGISTERED state) based on the sending and receiving of an attach acceptance message and / or an attach completion message, or may transition to or maintain a state where the UE is not registered with the network (EMM_DEREGISTERED state) or a state where the UE is registered with the network (EMM_REGISTERED state) based on the sending and receiving of an attach rejection message and / or a reason value.

[0304] Alternatively, each device may transition to a state where the UE is registered with the network (EMM_REGISTERED state) based on the sending and receiving of a TAU acceptance message and / or a TAU completion message, or may transition to or maintain a state where the UE is not registered with the network on the access for which an attach rejection message was received for the current PLMN (EMM_DEREGISTERED state) or a state where the UE is registered with the network (EMM_REGISTERED state) based on the sending and receiving of a TAU rejection message and / or a reason value.

[0305] Furthermore, if this procedure is a registration procedure other than initial registration, each device may transition to or maintain a state in which the UE is not registered with the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of a registration rejection message and the identification information in item 10.

[0306] Alternatively, if this procedure is a registration procedure other than initial registration, if a registration rejection message is sent or received, or if the registration procedure fails, or if the 10th identification information is sent or received, each device may transition to or maintain the state in which the UE is registered with the network (EMM_REGISTERED state).

[0307] Furthermore, if this procedure is an attach procedure, each device may transition to or maintain a state in which the UE is not registered on the network (EMM_DEREGISTERED state) based on the transmission and reception of an attach rejection message and the identification information of item 10.

[0308] Furthermore, if this procedure is a TAU procedure, each device may transition to or maintain a state in which the UE is not registered with the network (EMM_DEREGISTERED state) or a state in which the UE is registered with the network (EMM_REGISTERED state) based on the transmission and reception of the TAU rejection message and the identification information of item 10.

[0309] Based on the transmission and reception of the rejection message and the identification information of the tenth device, each device may transition to or enter, or be managed in, the UE state when the registration procedure fails, such as 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH.

[0310] Furthermore, each device may determine the next procedure to perform based on its state after the completion of this procedure. For example, if the UE transitions to the registration state, the TAU procedure or the registration procedure may be performed.

[0311] Furthermore, each device may, upon completion of this procedure, perform processing based on the information transmitted and received in this procedure. For example, if it has transmitted or received information indicating that some of the UE's requests were rejected, it may recognize the reason why the UE's requests were rejected. Furthermore, based on the reason why the UE's requests were rejected, each device may retry initiating the registration procedure and / or the attach procedure and / or the TAU procedure, or it may perform the registration procedure and / or the attach procedure and / or the TAU procedure for the current satellite or another satellite, or the current PLMN or another PLMN.

[0312] Furthermore, based on the completion of this procedure, the UE may store the identification information received along with the acceptance and / or rejection messages, and may recognize the network's decision.

[0313] Furthermore, based on the completion of this procedure and / or the information received in this procedure, the UE may reset the stored information, start a timer, or stop any running timers.

[0314] Specifically, for example, upon receiving at least one of the tenth and / or eleventh pieces of identification information, the UE may start counting an S&F wait timer using the value of the S&F wait timer indicated in the eleventh piece of identification information. The S&F wait timer may be stored and run in association with a Satellite ID indicating the current PLMN and / or satellite from which the UE sent the request message.

[0315] Furthermore, if the UE receives the 12th identification information, the S&F wait timer may be stored and executed in association with information (list of satellite IDs) indicating one or more satellites indicated by the 12th identification information.

[0316] Furthermore, if the information included in the 11th identification information is neither 0 nor information indicating deactivate, the UE may start counting the S&F wait timer and / or start and / or execute control using the S&F wait timer.

[0317] Furthermore, the UE may keep the S&F mode active while the S&F wait timer is running, and may deactivate the UE's S&F mode upon the expiration of the S&F wait timer. In other words, the UE may recognize the state of the S&F mode (active or inactive) based on the execution of the S&F wait timer. In this case, the S&F mode may be associated with the S&F wait timer and may be associated with one or more Satellite IDs.

[0318] Based on the above, each device may appropriately complete the registration, attachment, or TAU procedure, update its stored information and / or status, and / or perform control based on the stored information.

[0319] [3.2. Deregistration / Detachment Procedures] Next, we will describe the deregistration / detachment procedures, which are procedures for a UE to deregister with and / or detach from a system (e.g., 5GS or EPS). Deregistration / detachment procedures may be initiated by the UE or the NW. The following describes each deregistration / detachment procedure. Hereinafter, "this procedure" refers to the procedure for a UE to deregister with and / or detach from a system, and unless otherwise specified, this procedure may be initiated by the UE or the NW.

[0320] [3.2.1. UE-Initiated De-Registration / Detachment Procedures] The following describes procedures initiated by the UE for the UE to de-register and / or detach from a system (e.g., 5GS or EPS), using Figure 8. Hereinafter, "this procedure" refers to the procedure for the UE to de-register and / or detach from a system. For example, this procedure may be a UE-initiated de-registration procedure or a UE-initiated detachment procedure, or any other procedure.

[0321] The unregistration procedure initiated by the UE is a procedure initiated by the UE to unregister with access network_B and / or core network_B and / or DN. The UE can execute this procedure before powering off, if it is registered with the network. In other words, the UE can initiate this procedure at any time if it is in the registered state (5GMM-REGISTERED state). For example, this procedure may be executed after transitioning to the registered state via the procedure for registration and / or attachment and / or notification and / or updating the UE state described in Chapter 3.1.

[0322] Furthermore, each device (especially the UE and AMF) can transition to and / or enter an unregistered state (5GMM-DEREGISTERED state) based on the completion of the deregistration procedure.

[0323] The detach procedure initiated by the UE is a procedure initiated by the UE to deregister with access network_A and / or core network_A and / or DN. The UE can execute this procedure at any time, for example, before powering off, as long as it is registered with the network. In other words, the UE can initiate this procedure at any time as long as it is in the deregistered state (EMM-DEREGISTERED state). Furthermore, each device (especially the UE and MME) can transition to the deregistered state (EMM-DEREGISTERED state) based on the completion of the detach procedure.

[0324] Furthermore, each registration status may be stored and / or managed by each device for each access. Specifically, each device may independently store and / or manage the registration status for 3GPP access (registered or unregistered) and the registration status for non-3GPP access.

[0325] In Figure 8, the base station equipment may be base station equipment such as eNB and / or gNB, the mobile management equipment may be AMF140 and / or MME40, the mobile management equipment-onboard may be AMF-onboard141 and / or MME-onboard41, the mobile management equipment-ground may be AMF-ground142 and / or MME-ground42, and the session management equipment may be SMF132 and / or SGW35 and / or PGW and / or PGW-C. Note that when referred to as the mobile management equipment of the terrestrial network, it may mean the mobile management equipment and / or mobile management equipment-onboard. Furthermore, the mobile management equipment may include the mobile management equipment-onboard and / or mobile management equipment-ground.

[0326] First, UE_A10 initiates this procedure by sending a request message to the movement management device (S800). For example, UE_A10 may initiate a deregistration procedure initiated by the UE by sending a deregistration request message to AMF140, or it may initiate a detach procedure initiated by the UE by sending a detach request message to MME40.

[0327] Specifically, in 5GS, the UE may send an RRC message containing a non-registration request message to the 5G AN120 (or gNB). Alternatively, in EPS, the UE may send an RRC message containing a detach request message to the E-UTRAN80 (or eNB). The 5G AN120 (or gNB) and / or E-UTRAN80 (or eNB) may send or forward the received NAS message to the AMF140 and / or MME40.

[0328] Note that the unregistered request message is a NAS message sent and received over the N1 interface. On the other hand, the detach request message is a NAS message sent and received using the LTE-Uu interface and the S1-MME interface.

[0329] Furthermore, RRC messages may be control messages transmitted between the UE and the access network or base station. Also, NAS messages are processed at the NAS layer, and RRC messages are processed at the RRC layer. Note that the NAS layer is a higher layer than the RRC layer.

[0330] Hereafter, unregistered request messages and detach request messages will be referred to as request messages. In other words, unless otherwise specified, request messages refer to unregistered request messages and / or detach request messages sent from the UE.

[0331] UE_A10 may include in the request message information indicating whether this procedure is performed based on the UE being powered off. This information may be included in the Deregistration type IE and / or Detach type IE.

[0332] UE_A10 may include information in the request message indicating the type of access subject to this procedure during 5GS. Specifically, this information may indicate whether the access to be transitioned to the unregistered state by this procedure is 3GPP access, non-3GPP access, or both. The information indicating the type of access subject to this procedure may be the information contained in Deregistration type IE.

[0333] UE_A10 may also transmit these identifiers and / or IEs in a different control message, such as a control message at a lower layer than the RRC layer (e.g., MAC layer, RLC layer, PDCP layer). Furthermore, UE_A10 may indicate a request from the UE by transmitting these identifiers. In addition, if multiple identifiers are transmitted and received, two or more of these identifiers may be configured as one or more identifiers.

[0334] UE_A10 may include other identification information in the request message and / or the RRC message containing the request message, such as the UE ID and / or PLMN ID.

[0335] Here, if this procedure is performed using a UE and / or satellite and / or NW that has the capability to operate in S&F mode, the access network and / or base station equipment may be located on the satellite, and the mobile management equipment on which the access network forwards request messages from the UE may be a mobile management equipment-onboard (e.g., MME-onboard41 or AMF-onboard141).

[0336] The mobile management device-onboard may transmit information received from the UE via the access network to the mobile management device on the ground network when the UE and / or satellite and / or NW are operating in normal mode (S802). Specifically, for example, the MME-onboard41 may transmit or forward information received from the UE via the E-UTRAN80 (or eNB) to the MME-ground142 or MME140 on the ground network. Similarly, the AMF-onboard141 may transmit information received from the UE via the 5G AN120 (or gNB) to the AMF-ground142 or AMF140 on the ground network.

[0337] The mobile management device on the ground network may send a session release request message to the session management device upon receiving a request message from the UE via the mobile management device-onboard and / or access network (S804). The session management device that has received the session release request message may send a session release response message to the mobile management device on the ground network (S806).

[0338] Specifically, AMF-ground142 or AMF140 may send a PDU session release request message to SMF132 for each PDU session if a PDU session is established on an access type for which the UE has requested non-registration. Upon receiving a PDU session release request message, SMF may release the PDU session in question and send a PDU session release response message to AMF-ground142 or AMF140 as a response message.

[0339] Furthermore, if MME-ground142 or MME140 has an active PDN connection, it may send a Delete Session Request to the SGW for each PDN connection. In addition, the SGW may send a Delete Session Request to the PGW for each PDN connection. The PGW and / or SGW may send a session deletion response as a response message, and MME-ground142 or MME140 may receive the session deletion response.

[0340] If this procedure is performed via satellite, and furthermore, if the UE and / or satellite and / or NW are operating in normal mode and / or feeder link connectivity is available, the mobile management device of the ground network may recognize the release and / or deletion of the session upon receiving S806 and send a control message to the mobile management device-onboard as a response to the request from the UE (S808). The control message may be an acceptance message, a deregistration accept message and / or a detach accept message, or any other acceptance message to a request from the UE.

[0341] Hereafter, the acceptance message may be a deregistration accept message and / or a detach accept message. Furthermore, a deregistration accept message may be interpreted as a detach accept message, and vice versa.

[0342] If this procedure is performed via satellite, and further if the UE and / or satellite and / or NW are operating in S&F mode and / or feeder link connectivity is unavailable, the mobile management device of the ground network may recognize the release and / or deletion of the session based on the receipt of S806, generate a control message in response to the request from the UE, store the control message in ground storage, and transmit it after feeder link connectivity becomes available (S808).

[0343] The movement management device may send an RRC message containing an acceptance message to the UE (S810). The movement management device-onboard may forward the control message received from the movement management device-ground, or it may generate a control message to send to the UE based on the control message and / or information received from the movement management device-ground, and send it to the UE. For example, the movement management device-onboard may generate a new control message by adding information to the control message received from the movement management device-ground, or it may generate a control message based on the control message and / or information received from the movement management device-ground. The control message may be an acceptance message, a deregistration accept message and / or a detach accept message, or any other acceptance message for a request from the UE.

[0344] When the mobile management device-onboard receives a request message from the UE in S800, if the UE and / or satellite and / or NW are operating in S&F mode, the mobile management device-onboard and / or each device in the network may accept the request from the UE without performing the procedures from S802 to S808. In that case, the mobile management device-onboard may send an RRC message containing an acceptance message to the UE (S810).

[0345] The mobile management device-onboard, being in S&F mode, skips S802 through S808. When accepting a request from the UE, it stores the information contained in the request message from the UE. After the feeder link connection becomes possible and the feeder link is available, it executes S802, which had not been executed, thereby allowing the mobile management device-onboard and / or each device in the network to execute S802 through S808.

[0346] In that case, the movement management device-onboard may send and / or forward the request message from the UE to the movement management device-ground, adding information indicating that the movement management device-onboard has already responded to the UE (S802). If the movement management device-ground receives information indicating that the movement management device-onboard has already responded to the UE in response to the request message from the UE, it does not need to send a control message to the movement management device-onboard (S808).

[0347] Unregistered acceptance messages are NAS messages sent and received over the N1 interface. Detachment acceptance messages, on the other hand, are NAS messages sent and received using the LTE-Uu interface and the S1-MME interface.

[0348] The mobile management device-onboard may, upon receiving a control message from the mobile management device-ground, transmit the received control message and / or the generated control message to the UE (S810). The mobile management device (mobile management device-onboard and / or mobile management device-ground) may transmit the control message including at least one of the identification information from the 11th to the 13th.

[0349] UE_A10 receives a control message and / or one or more pieces of information contained in the control message from the network. Based on the reception of the control message and / or one or more pieces of information contained in the control message, UE_A10 may recognize the received information.

[0350] The UE receives a control message from the mobility management device via the access network (S810). If the control message is an acceptance message, the UE can recognize that its request in the request message has been accepted and can also recognize the content of various identification information contained in the acceptance message.

[0351] For example, based on the receipt of the 11th identification information and / or the receipt of a control message containing the 11th identification information, the UE may store the value indicated in the 11th identification information. Based on the receipt of the 11th identification information and / or the fact that the NW and / or UE are controlled in S&F mode, the UE may execute and / or start the S&F wait timer using the value indicated in the 11th identification information and / or the stored S&F wait timer value.

[0352] The UE may associate and store, and / or manage and run, a PLMN ID and / or Satellite ID with the S&F wait timer. The S&F wait timer may be associated with one or more Satellite IDs, which may be satellite IDs indicating the satellite that transmitted the 11th identification information, or may be one or more satellite IDs that are included in the S&F Monitoring list indicated by the 12th identification information.

[0353] Based on the receipt of the 11th identification information, the UE may stop and / or delete any running and / or stored S&F wait timers. Alternatively, even if the UE receives the 11th identification information, it may, based on its own decision, not delete any stored S&F wait timer values ​​and / or stop any running S&F wait timers. In other words, even if the UE receives the 11th identification information, it may, based on its own decision, not update any S&F wait timer values.

[0354] In other words, even if the UE receives the 11th identification information, it may maintain the value of the S&F wait timer it stores and ignore the value indicated in the received 11th identification information.

[0355] While the S&F wait timer is running, the UE may control the PLMN and / or satellites indicated by the PLMN ID associated with the S&F wait timer, preventing the UE from retrying sending request messages, and may also control the UE from attempting NAS procedures by sending other MM messages.

[0356] Upon the expiration of the S&F wait timer, the UE may retry sending a request message to the PLMN and / or satellites indicated by the PLMN ID associated with the S&F wait timer and / or one or more Satellite IDs, or may attempt NAS procedures by sending other MM messages.

[0357] Based on the receipt of the 12th identification information, the UE may manage and / or store an S&F Monitoring List consisting of one or more Satellite IDs indicated in the 12th identification information, associated with the value of the S&F wait timer indicated in the 11th identification information and / or an S&F wait timer using the value of the 11th identification information. The UE may also store and / or manage the S&F Monitoring List in association with a satellite ID indicating the satellite to which the PLMN and / or the mobile management device that transmitted the 12th identification information belong.

[0358] Based on the receipt of the 12th identification, the UE may delete any stored S&F Monitoring Lists and store the received 12th identification. Alternatively, if the UE stores an S&F Monitoring List, the UE may, at its discretion, not delete the stored S&F Monitoring List even if it receives the 12th identification. In other words, the UE may, at its discretion, not update the S&F Monitoring List even if it receives the 12th identification. To put it another way, the UE may, even if it receives the 12th identification, maintain the stored S&F Monitoring List and ignore the value indicated in the received 12th identification.

[0359] Based on the UE's decision, the UE may decide whether or not to update the S&F Monitoring List it stores. For example, if the S&F Monitoring List indicated by the 12th identification information received by the UE is older than the S&F Monitoring List stored by the UE, the UE may decide not to update the stored S&F Monitoring List. In other words, if the S&F Monitoring List stored by the UE is newer than the S&F Monitoring List indicated by the 12th identification information received, the UE may decide not to update the stored S&F Monitoring List.

[0360] In other words, if the UE finds that the S&F Monitoring List indicated by the 12th identification information it receives is newer than the S&F Monitoring List it stores, it may decide to update the S&F Monitoring List it stores. In other words, if the UE finds that the S&F Monitoring List it stores is older than the S&F Monitoring List indicated by the 12th identification information it receives, it may decide to update the S&F Monitoring List it stores.

[0361] For example, based on information pre-configured in the UE, such as the UE being an IoT device, the UE may decide not to update the S&F Monitoring List it stores. For example, the UE may be configured to store only the 12th identification information received from a specific satellite, or it may be configured to store only the S&F Monitoring List that is pre-configured in the UE.

[0362] If the UE does not remember the received 12th identification information, it may delete the stored S&F Monitoring List, or it may retain the stored S&F Monitoring List without deleting it.

[0363] Upon receiving the 13th identification information, the UE may recognize the estimated and / or expected time required from transmission until the data is delivered to the ground network function unit and / or network element. Based on the receipt of the 13th identification information, the UE may start counting a timer for the uplink S&F estimated delivery time using the value of the 13th identification information.

[0364] Furthermore, each device may transition to or maintain a state based on the transmission and reception of control messages and / or information contained in those control messages. Alternatively, the transition of each device to a state may be based on the transmission and reception of completion messages or the completion of this procedure. Note that transitioning to a state may be synonymous with entering a state.

[0365] For example, each device may transition to a state where the UE is not registered with the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the sending or receiving of a request message and / or the sending or receiving of a non-registration acceptance message.

[0366] While the UE is running the S&F wait timer, the UE may stop the S&F wait timer based on the UE sending a request message and / or receiving an acceptance message.

[0367] If the UE is running the S&F wait timer, the UE may stop the S&F wait timer based on the UE receiving an unregistered acceptance message that does not include S&F satellite operation parameters IE. If the UE is running the S&F wait timer, the UE may stop the S&F wait timer based on the UE receiving an unregistered acceptance message that includes S&F satellite operation parameters IE but does not include the 11th identification information.

[0368] If the UE is running the S&F wait timer, the UE may stop the S&F wait timer based on receiving an unregistered acceptance message that includes S&F satellite operation parameters IE containing an eleventh identifier with a value of 0.

[0369] If the UE is running the S&F wait timer, the UE may stop the S&F wait timer based on receiving an unregistered acceptance message containing S&F satellite operation parameters IE that includes first information indicating that the 11th identification information is not included, or second information indicating that the 11th identification information is not included and that the UE requests the deletion of the 11th identification information it stores.

[0370] Furthermore, the UE may stop the S&F wait timer while it is running if the UE has performed a local detach and / or local deregistration. Here, local detach and / or local deregistration may mean releasing the NAS signaling connection.

[0371] Furthermore, based on the completion of this procedure, the UE may store the identification information received along with the acceptance message, or recognize the network decision. Furthermore, based on the completion of this procedure and / or the information received in this procedure, the UE may reset the stored information, start one or more timers, or stop any running timers.

[0372] Furthermore, each device may, upon completion of this procedure, perform processing based on the information transmitted and received in this procedure and / or the stored information of each device. For example, upon completion of this procedure, the UE may perform a PLMN search to find a PLMN to connect to.

[0373] Based on the above, each device may complete a deregistration / detachment procedure appropriately initiated by the UE, update stored information and / or state, and / or perform control based on the stored information.

[0374] [3.2.2. Deregistration / Detachment Procedures Initiated by the Network] Next, we will explain, using Figure 9, the procedures initiated by the network for a UE to deregister and / or detach from a system (e.g., 5GS or EPS). Hereinafter, "this procedure" refers to the procedure for deregistering and / or detaching from a system. For example, this procedure may be a network-initiated deregistration procedure, a network-initiated detachment procedure, an MME-initiated detachment procedure, or any other procedure.

[0375] The deregistration procedure initiated by the network (NW) is a procedure led by the NW to deregister with access network_B and / or core network_B and / or DN. The NW can execute this procedure if it is registered with the network. In other words, if the UE is in the registered state (5GMM-REGISTERED state), it can initiate this procedure at any time. Furthermore, each device (especially the UE and AMF) can transition to and / or enter the deregistered state (5GMM-DEREGISTERED state) based on the completion of the deregistration procedure.

[0376] Detach procedures initiated by the network (NW) and / or MME are procedures initiated by the NW and / or MME to deregister the UE with access network_A and / or core network_A and / or DN. The NW can execute this procedure at any time, provided that the UE is registered with the network. For example, this procedure may be executed after transitioning to the registered state through the registration and / or attachment and / or notification and / or update of the UE status procedures described in Chapter 3.1.

[0377] Furthermore, each device (especially the UE and MME) can transition to an unregistered state (EMM-DEREGISTERED state) based on the completion of the detach procedure.

[0378] Furthermore, each registration status may be stored and / or managed by each device for each access. Specifically, each device may independently store and / or manage the registration status for 3GPP access (registered or unregistered) and the registration status for non-3GPP access.

[0379] In Figure 9, the base station equipment may be base station equipment such as eNB and / or gNB, the mobile management equipment may be AMF140 and / or MME40, the mobile management equipment-onboard may be AMF-onboard141 and / or MME-onboard41, the mobile management equipment-ground may be AMF-ground142 and / or MME-ground42, and the session management equipment may be SMF132 and / or SGW35 and / or PGW and / or PGW-C. Note that when referred to as the mobile management equipment of the terrestrial network, it may mean the mobile management equipment and / or mobile management equipment-onboard. Furthermore, the mobile management equipment may include the mobile management equipment-onboard and / or mobile management equipment-ground.

[0380] First, the movement management device initiates this procedure by sending a request message to UE_A10 (S902). For example, AMF140 may initiate a deregistration procedure initiated by the network by sending a deregistration request message to UE_A10. Alternatively, MME40 may initiate a detach procedure initiated by the network and / or MME by sending a detach request message to UE_A10.

[0381] Specifically, the UE may transmit or forward NAS messages received from the 5G AN120 (or gNB) and / or E-UTRAN80 (or eNB) AMF140 and / or MME40. Furthermore, in 5GS, the UE may receive an RRC message containing a non-registration request message from the 5G AN120 (or gNB). Alternatively, in EPS, the UE may receive an RRC message containing a detach request message from the E-UTRAN80 (or eNB).

[0382] Note that the unregistered request message is a NAS message sent and received over the N1 interface. On the other hand, the detach request message is a NAS message sent and received using the LTE-Uu interface and the S1-MME interface.

[0383] Furthermore, RRC messages may be control messages transmitted between the UE and the access network or base station. Also, NAS messages are processed at the NAS layer, and RRC messages are processed at the RRC layer. Note that the NAS layer is a higher layer than the RRC layer.

[0384] Hereafter, unregistered request messages and detach request messages will be referred to as request messages. In other words, unless otherwise specified, the following request messages refer to unregistered request messages and / or detach request messages sent from the network.

[0385] The mobile management device may send a request message indicating whether or not it will require registration again after the completion of this procedure. Specifically, in 5GS, the AMF may set Deregistration type IE to re-registration required or re-registration not required. In EPS, the MME may set Detach type IE to re-attach required or re-attach not required.

[0386] The movement management device may indicate a request from the network by transmitting this identification information. Furthermore, if multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information.

[0387] The movement management device may include other identification information in the request message, such as the UE ID and / or PLMN ID. The movement management device may include at least one of the identification information items 11 through 14 in the request message.

[0388] Here, if this procedure is performed using a UE and / or satellite and / or NW that has the capability to operate in S&F mode, the access network and / or base station equipment may be located on the satellite, and the mobile management equipment on which the access network forwards request messages from the UE may be a mobile management equipment-onboard (e.g., MME-onboard41 or AMF-onboard141).

[0389] The mobile management device-onboard may receive a request message from the mobile management device on the ground network when the UE and / or satellite and / or NW are operating in normal mode (S900). Based on having received a request message from the mobile management device on the ground network, the mobile management device-onboard may send a request message to the UE (S902).

[0390] Alternatively, the mobile management device-onboard may send a request message to the UE at any time, without receiving a request message from the mobile management device on the ground network (S902). In this case, the UE and / or satellite and / or NW may be in normal mode or S&F mode.

[0391] UE_A10 receives a request message and / or one or more pieces of information contained in the request message from the mobility management device via the access network (S902). Based on the receipt of the request message and / or the receipt of one or more pieces of information contained in the request message, UE_A10 may recognize the content of various identification information contained in the request message and may further take actions based on that recognition.

[0392] For example, based on the receipt of the 11th identification information and / or the receipt of a request message containing the 11th identification information, the UE may store the value indicated in the 11th identification information. Based on the receipt of the 11th identification information and / or the fact that the NW and / or satellite and / or UE are controlled in S&F mode, the UE may execute and / or start the S&F wait timer using the value indicated in the 11th identification information and / or the stored S&F wait timer value.

[0393] The UE may associate and store, and / or manage and run, a PLMN ID and / or Satellite ID with the S&F wait timer. The S&F wait timer may be associated with one or more Satellite IDs, which may be satellite IDs indicating the satellite that transmitted the 11th identification information, or may be one or more satellite IDs that are included in the S&F Monitoring list indicated by the 12th identification information.

[0394] Based on the receipt of the 11th identification information, the UE may stop and / or delete any running and / or stored S&F wait timers. Alternatively, even if the UE receives the 11th identification information, it may, based on its own decision, not delete any stored S&F wait timer values ​​and / or stop any running S&F wait timers. In other words, even if the UE receives the 11th identification information, it may, based on its own decision, not update any S&F wait timer values.

[0395] In other words, even if the UE receives the 11th identification information, it may maintain the value of the S&F wait timer it stores and ignore the value indicated in the received 11th identification information.

[0396] While the S&F wait timer is running, the UE may control the PLMN and / or satellites indicated by the PLMN ID associated with the S&F wait timer, preventing the UE from retrying sending request messages, and may also control the UE from attempting NAS procedures by sending other MM messages.

[0397] Upon the expiration of the S&F wait timer, the UE may retry sending a request message to the PLMN and / or satellites indicated by the PLMN ID associated with the S&F wait timer and / or one or more Satellite IDs, or may attempt NAS procedures by sending other MM messages.

[0398] Based on the receipt of the 12th identification information, the UE may manage and / or store an S&F Monitoring List consisting of one or more Satellite IDs indicated in the 12th identification information, associated with the value of the S&F wait timer indicated in the 11th identification information and / or an S&F wait timer using the value of the 11th identification information. The UE may also store and / or manage the S&F Monitoring List in association with a satellite ID indicating the satellite to which the PLMN and / or the mobile management device that transmitted the 12th identification information belong.

[0399] Based on the receipt of the 12th identification, the UE may delete any stored S&F Monitoring Lists and store the received 12th identification. Alternatively, if the UE stores an S&F Monitoring List, the UE may, at its discretion, not delete the stored S&F Monitoring List even if it receives the 12th identification. In other words, the UE may, at its discretion, not update the S&F Monitoring List even if it receives the 12th identification. To put it another way, the UE may, even if it receives the 12th identification, maintain the stored S&F Monitoring List and ignore the value indicated in the received 12th identification.

[0400] Based on the UE's decision, the UE may decide whether or not to update the S&F Monitoring List it stores. For example, if the S&F Monitoring List indicated by the 12th identification information received by the UE is older than the S&F Monitoring List stored by the UE, the UE may decide not to update the stored S&F Monitoring List. In other words, if the S&F Monitoring List stored by the UE is newer than the S&F Monitoring List indicated by the 12th identification information received, the UE may decide not to update the stored S&F Monitoring List.

[0401] In other words, if the UE finds that the S&F Monitoring List indicated by the 12th identification information it receives is newer than the S&F Monitoring List it stores, it may decide to update the S&F Monitoring List it stores. In other words, if the UE finds that the S&F Monitoring List it stores is older than the S&F Monitoring List indicated by the 12th identification information it receives, it may decide to update the S&F Monitoring List it stores.

[0402] Alternatively, based on information pre-configured in the UE, such as the UE being an IoT device, the UE may decide not to update the S&F Monitoring List it stores. For example, the UE may be configured to store only the 12th identification information received from a specific satellite, or it may be configured to store only the S&F Monitoring List that is pre-configured in the UE.

[0403] If the UE does not remember the received 12th identification information, it may delete the stored S&F Monitoring List, or it may retain the stored S&F Monitoring List without deleting it.

[0404] Upon receiving the 13th identification information, the UE may recognize the estimated and / or expected time required from transmission until the data is delivered to the ground network function unit and / or network element. Based on the receipt of the 13th identification information, the UE may start counting a timer for the uplink S&F estimated delivery time using the value of the 13th identification information.

[0405] Upon receiving a request message from the movement management device, the UE sends a control message to the movement management device (S908). Here, the control message may be an acceptance message, a deregistration accept message and / or a detach accept message, or any other acceptance message for a request from the NW.

[0406] Hereafter, the acceptance message may be a deregistration accept message and / or a detach accept message. Furthermore, a deregistration accept message may be interpreted as a detach accept message, and vice versa.

[0407] If the 14th identification information is received, and the UE is also running the S&F wait timer, the S&F wait timer may not be stopped, and the count and control of the running S&F wait timer may be continued.

[0408] If this procedure is performed via satellite, and further if the UE and / or satellite and / or NW are operating in normal mode and / or feeder link connectivity is available, the mobile management device-onboard may forward the received control message and / or generate and transmit a message including a portion of the control message to the mobile management device on the ground network (S910).

[0409] Based on the transmission of an unregistered request message (S902 or S900) and / or the reception of a control message (S908 or S910), the mobile management device may send a session release request message to the session management device (S904). The session management device that has received the session release request message may send a session release response message to the mobile management device of the terrestrial network (S906).

[0410] Specifically, AMF-ground142 or AMF140 may send a PDU session release request message to SMF132 for each PDU session if a PDU session is established on an access type for which the UE has requested non-registration. Upon receiving a PDU session release request message, SMF may release the PDU session in question and send a PDU session release response message to AMF-ground142 or AMF140 as a response message.

[0411] Furthermore, if MME-ground142 or MME140 has an active PDN connection, it may send a Delete Session Request to the SGW for each PDN connection. In addition, the SGW may send a Delete Session Request to the PGW for each PDN connection. The PGW and / or SGW may send a session deletion response as a response message, and MME-ground142 or MME140 may receive the session deletion response.

[0412] Unregistered acceptance messages are NAS messages sent and received over the N1 interface. Detachment acceptance messages, on the other hand, are NAS messages sent and received using the LTE-Uu interface and the S1-MME interface.

[0413] UE_A10 sends a control message and / or one or more pieces of information contained in the control message to the network. The network may recognize the received information based on its receipt of the control message and / or one or more pieces of information contained in the control message.

[0414] The UE transmits a control message via the access network (S908). Each device completes this procedure based on the transmission and reception of the control message and / or completion message.

[0415] Furthermore, each device may transition to or maintain a state based on the transmission and reception of control messages and / or information contained in those control messages. Alternatively, the transition of each device to a state may be based on the transmission and reception of completion messages or the completion of this procedure. Note that transitioning to a state may be synonymous with entering a state.

[0416] For example, each device may transition to a state where the UE is not registered with the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the sending or receiving of a request message and / or the sending or receiving of an acceptance message.

[0417] If the UE does not receive the 14th identification information, the UE may stop the S&F wait timer as follows:

[0418] While the UE is running the S&F wait timer, the UE may stop the S&F wait timer based on the UE receiving a request message and / or sending an acceptance message.

[0419] If the UE is running the S&F wait timer, the UE may stop the S&F wait timer based on the UE receiving a request message that does not include S&F satellite operation parameters IE. If the UE is running the S&F wait timer, the UE may stop the S&F wait timer based on the UE receiving a request message that includes S&F satellite operation parameters IE that does not include the 11th identification information. Note that S&F satellite operation parameters IE that does not include the 11th identification information may mean S&F satellite operation parameters IE that does not have an S&F wait time duration field.

[0420] While the UE is running the S&F wait timer, the UE may stop the S&F wait timer based on receiving a request message containing S&F satellite operation parameters IE, which includes an eleventh identification piece indicated by a value of 0.

[0421] While the UE is running the S&F wait timer, the UE may stop the S&F wait timer based on receiving a request message containing S&F satellite operation parameters IE that includes first information indicating that the 11th identification information is not included, or second information indicating that the 11th identification information is not included and that the UE requests the deletion of the 11th identification information stored by the UE.

[0422] Furthermore, the UE may stop the S&F wait timer while it is running based on the UE performing a local detach.

[0423] Furthermore, based on the completion of this procedure, the UE may store the identification information received with the request message, or recognize the network decision. Furthermore, based on the completion of this procedure and / or the information received in this procedure, the UE may reset the stored information, start a timer, or stop any running timers.

[0424] Furthermore, each device may, upon completion of this procedure, perform processing based on the information transmitted and received in this procedure and / or the stored information of each device. For example, upon completion of this procedure, the UE may perform a PLMN search to find a PLMN to connect to.

[0425] Based on the above, each device may appropriately complete the unregistering / detachment procedure initiated by the NW and / or the mobile management device, update stored information and / or status, and / or perform control based on the stored information.

[0426] [4. Modifications] A program that operates in a device according to one aspect of the present invention may be a program that controls a Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of an embodiment according to one aspect of the present invention. The program or information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, a Hard Disk Drive (HDD), or other storage device system.

[0427] Furthermore, a program for realizing the functions of an embodiment relating to one aspect of the present invention may be recorded on a computer-readable recording medium. This may also be realized by loading the program recorded on this recording medium into a computer system and executing it. Here, "computer system" refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. Also, "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other computer-readable recording medium.

[0428] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, such as an integrated circuit or a combination of integrated circuits. An electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, a conventional processor, controller, microcontroller, or state machine. The aforementioned electrical circuit may consist of digital circuits or analog circuits. Also, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, one or more aspects of the present invention may also utilize new integrated circuits based on such technologies.

[0429] It should be noted that the present invention is not limited to the embodiments described above. Although one example of a device is described in the embodiments, one aspect of the present invention is not limited thereto and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0430] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, various modifications are possible within the scope of the claims for one aspect of the present invention, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included.

[0431] One aspect of the present invention can be used, for example, in communication systems, communication equipment (e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (e.g., communication chips), or programs.

[0432] 1 Mobile Communication System 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access Network_A 90 Core Network_A 120 Access Network_B 122 gNB 130 UPF 132 SMF 140 AMF 150 UDM 160 PCF 170 N3IWF 190 Core Network_B

Claims

1. User Equipment (UE) comprising a control unit and a transceiver unit, wherein the control unit starts a first timer, controls the UE not to start NAS procedures on an S&F satellite E-UTRAN cell while the first timer is running, the S&F satellite E-UTRAN cell is a cell having satellite E-UTRAN access technology that broadcasts information indicating that the base station is operating in S&F mode, and while the first timer is running, if the transceiver unit receives a detach request message from the network, the control unit stops the first timer, the transceiver unit sends a detach acceptance message in response to the detach request message, and the UE enters an EMM-DEREGISTERED state.

2. The UE according to claim 1, wherein the first timer is executed when the state of the UE is EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH state.

3. The UE according to claim 1, wherein the first timer is executed when the state of the UE is in the EMM-REGISTERED state.

4. If the detach procedure is initiated by the transmitting / receiving unit transmitting a second detach request message while the first timer is running, the transmitting / receiving unit receives a second detach acceptance message as a response to the second detach request message, and the UE enters the EMM-DEREGISTERED state, the UE according to claim 1.