UE (User Equipment) and movement management devices

Abstract

It provides User Equipment (UE) and / or satellites and / or networks to enable storage and transmission satellite operations. [Solution] In a mobile communication system, if an UE capable of communicating via satellite is rejected by a first satellite for an attach or TAU (Tracking Area Update) or registration request message sent by the UE for an S&F (Store and Forward) operation, the UE performs appropriate processing while a wait timer is running and / or after the wait timer has expired to control and prohibit the retransmission / retries of the request message to the first satellite.

Description

Technical Field

[0001] The present invention relates to a UE (User Equipment) and a mobility management device.

Background Art

[0002] In 3GPP (3rd Generation Partnership Project), the system architecture of 5GS (5G System), which is a fifth-generation (5G) mobile communication system, is being studied, and discussions are being held to support new procedures and new functions (see Non-Patent Documents 1 to 3).

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

[0004] Release 19 is planned to specify the Store and Forward (S&F) satellite operation, but how this operation will be implemented has not been disclosed (see Non-Patent Document 4).

[0005] One aspect of the present invention has been made in view of the above circumstances, and aims to clarify the method for realizing memory and transmission satellite operation, as well as clarify the detailed behavior of the UE and / or satellite and / or network. [Means for solving the problem]

[0006] One aspect of the present invention is a User Equipment (UE) comprising a control unit and a transmitting / receiving unit, wherein the transmitting / receiving unit transmits a request message containing information indicating an unavailable period to a mobile management device mounted on a satellite, receives a rejection message from the mobile management device in response to the request message, and the control unit, if the rejection message does not contain a second value indicating the length of the unavailable period, uses a first value determined by the UE, and if the rejection message contains the second value, uses the first value determined by the UE, or deletes the first value determined by the UE and uses the received second value.

[0007] A mobile management device according to one aspect of the present invention is a mobile management device installed on the ground, comprising a control unit and a transmitting / receiving unit, wherein the mobile management device is connected to a second mobile management device mounted on a satellite, and when the connectivity becomes available after it has been unavailable, the transmitting / receiving unit receives a first request message and a value indicating a first time from the second mobile management device, and the control unit skips the authentication procedure based on the first request message if it has received a second request message from a mobile management device mounted on another satellite after the first time, and starts the authentication procedure if it has not received a second request message from a mobile management device mounted on another satellite after the first time. [Effects of the Invention]

[0008] 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. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram illustrating the general outline of the mobile communication system (EPS / 5GS). [Figure 2] This diagram illustrates the detailed configuration of the mobile communication system (EPS / 5GS). [Figure 3] This is a diagram illustrating the equipment configuration of the UE. [Figure 4] This diagram illustrates the configuration of an access network device. [Figure 5] This diagram illustrates the configuration of the core network device. [Figure 6] This diagram illustrates the detailed configuration of a satellite-based mobile communication system (EPS / 5GS). [Figure 7] This diagram explains the registration procedure, attachment procedure, and TAU procedure. [Modes for carrying out the invention]

[0010] 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.

[0011] [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.

[0012] 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.

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

[0014] 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.

[0015] 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.

[0016] Currently, the EPS (Evolved Packet System), which is a 4G system, is composed of an access network_A and a core network_A, and may further include a UE and / or a PDN. Also, the 5GS (5G System), which is a 5G system, is composed of a UE, an access network_B, and a core network_B, and may further include a DN.

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

[0018] Also, the access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. One or more eNBs (evolved Node B) 45 are arranged in the E-UTRAN. Note that hereinafter, the eNB 45 may sometimes be described with the symbol omitted like eNB. Also, when there are multiple eNBs, each eNB is connected to each other, for example, by an X2 interface. Also, one or more access points are arranged in the wireless LAN access network.

[0019] 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.

[0020] 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).

[0021] 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.

[0022] 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.

[0023] 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.

[0024] 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), UDM (Unified Data Management), etc. Here, 5GCN may also be expressed as 5GC.

[0025] 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.

[0026] 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).

[0027] 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.

[0028] 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 at least a portion of 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.

[0029] 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.

[0030] 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.

[0031] 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).

[0032] 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.

[0033] 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.

[0034] 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.

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

[0036] [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.

[0037] 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). Each memory unit can also 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.

[0038] [2.1. UE Equipment Configuration] First, an example of the UE (User 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, transceiver unit_A320, and storage unit_A340 are connected via a bus. The transceiver unit_A320 is connected to the antenna 310.

[0039] The control unit A300 is a functional unit that controls the operation and functions of the entire UE. The control unit A300 realizes various processes in the UE by reading and executing various programs stored in the memory unit A340 as needed.

[0040] The transceiver unit A320 is a functional unit for wireless communication with base station equipment (eNB or gNB) within the access network via an antenna. In other words, the UE can use the transceiver unit A320 to send and receive user data and / or control information between the access network equipment and / or core network equipment and / or PDN and / or DN.

[0041] Referring to Figure 2, the UE can communicate with the base station equipment (eNB) in E-UTRAN via the LTE-Uu interface using the transceiver unit A320. The UE can also communicate with the base station equipment (gNB) in 5G AN using the transceiver unit A320. Furthermore, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface using the transceiver unit A320. However, since the N1 interface is logical, actual communication between the UE and the AMF takes place via the 5G AN.

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

[0043] [2.2. Base Station Equipment Configuration] Next, an example of the base station equipment configuration will be explained using Figure 4. The base station equipment may be a gNB, an eNB, an en-gNB, or an ng-eNB. Here, we will explain using the case of a gNB as the base station equipment. That is, in the following explanation, gNB may be read as eNB, en-gNB, or ng-eNB. The gNB consists 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, network connection unit_B520, transceiver unit_B530, and storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0044] The control unit B500 is a functional unit that controls the operation and functions of the entire gNB. The control unit B500 implements various processes in the gNB by reading and executing various programs stored in the memory unit B540 as needed.

[0045] The network connection unit B520 is a functional unit that allows the gNB to communicate with the AMF and / or UPF. In other words, the gNB can use the network connection unit B520 to send and receive user data and / or control information with the AMF and / or UPF.

[0046] The transceiver unit B530 is a functional unit for wireless communication with the UE via the antenna 510. In other words, the gNB can send and receive user data and / or control information to and from the UE using the transceiver unit B530.

[0047] Referring to Figure 2, the gNB within the 5G AN can communicate with the AMF via the N2 interface and with the UPF via the N3 interface by using the network connection unit B520. Furthermore, the gNB can communicate with the UE by using the transceiver unit B530.

[0048] 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.

[0049] [2.3. AMF / MME Equipment Configuration] Next, we will describe an example of the device configuration of the AMF and MME, which are part of the core network device or core network function. Here, we will explain the example of the AMF device configuration using Figure 5. Here, we will explain using the AMF as an example, but it may be interpreted as 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.

[0050] 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.

[0051] 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.

[0052] 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.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

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

[0064] [2.4. SMF / PGW Equipment 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.

[0065] 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.

[0066] 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.

[0067] 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.

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

[0069] 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.

[0070] 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.

[0071] 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.

[0072] [2.5. UPF / PGW Equipment 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.

[0073] 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.

[0074] 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.

[0075] 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.

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

[0077] 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.

[0078] 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.

[0079] 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.

[0080] 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.

[0081] [2.6. Description of other devices and / or functions and identification information in this embodiment] Next, we will describe the other devices and / or functions, and the identification information.

[0082] 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.

[0083] 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.

[0084] Furthermore, the control plane (also called CP) refers to control messages sent and received for communication control 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 (Non-Access-Stratum) 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 the control plane or the C-Plane.

[0085] 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.

[0086] Furthermore, MM (Mobility Management) messages may be control messages sent and received between the UE and the AMF or MME during the MM procedure, and may also be NAS messages (also referred to as NAS MM messages).

[0087] 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 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).

[0088] 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.

[0089] In addition, in a deregistration procedure initiated by a UE, the UE may send a De-registration Request message to the AMF and receive a De-registration Accept message from the AMF that has received it.

[0090] In addition, during 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 the message.

[0091] 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.

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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).

[0096] 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.

[0097] 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.

[0098] 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.

[0099] 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.

[0100] 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).

[0101] 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).

[0102] 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.

[0103] 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.

[0104] 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.

[0105] 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.

[0106] 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.

[0107] 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.

[0108] 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.

[0109] 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.

[0110] 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.

[0111] 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.

[0112] 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.

[0113] 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.

[0114] 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.

[0115] 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.

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

[0117] 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.

[0118] 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.

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

[0120] 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.

[0121] 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).

[0122] 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.

[0123] 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.

[0124] 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.

[0125] 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).

[0126] 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.

[0127] 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.

[0128] Furthermore, Store and Forward (S&F) satellite operation (also known as Store and Forward satellite operation 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).

[0129] 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.

[0130] 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.

[0131] 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.

[0132] 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.

[0133] 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.

[0134] 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.

[0135] Furthermore, the UE, and / or satellite, and / or NW 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."

[0136] 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.

[0137] 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 (not operating in standard mode)," etc. Similarly, when the UE and / or satellite and / or NW operate in normal mode, for simplicity, it will be expressed as "when operating in normal mode (not operating in S&F mode)," etc.

[0138] 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 NW 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.

[0139] Next, a system configuration when an access network and a portion of the MME and / or AMF are mounted on or installed on a satellite 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.

[0140] 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.

[0141] 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.

[0142] 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.

[0143] 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.

[0144] 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.

[0145] 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 regarding the unavailability period may be synonymous with determining the unavailability period itself.

[0146] 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.

[0147] 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.

[0148] 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.

[0149] 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.

[0150] 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.

[0151] The first identification information is information indicating whether the UE supports the S&F operation mode. The first identification information may also be information indicating that the UE supports the S&F operation mode.

[0152] The second identification information may be information indicating that the information transmitted by the UE is a retransmission of a request message that was rejected for S&F operation mode and / or a retry of sending the request message. Alternatively, the second identification information may be information indicating whether or not the information transmitted by the UE is a retransmission of a request message that was rejected for S&F operation mode.

[0153] The second identification information indicates that the request message sent by the UE is a retransmission of a request message that was rejected for S&F. The UE may include the second identification information in the request message if it retries sending the request message after the Wait timer count expires when the request for S&F is rejected from the network and / or satellite.

[0154] The second identification information may be information indicating that the request message rejected for S&F and the request message sent together with and / or included with the second identification information are the same information.

[0155] The third identifier may be information about the period of unavailability that the UE notifies the network of. The third identifier may also be Unavailability information IE. The third identifier may include information indicating the type of unavailability and / or the duration of the unavailability period and / or the start of the unavailability period.

[0156] The Unavailability Type is information indicating the associated reason and / or type of unavailability, and may be information indicating unavailability due to UE reasons and / or unavailability due to discontinuous coverage.

[0157] The length of the unavailability period may be information that the UE notifies the network of, indicating the expected length of the unavailability period, and may be expressed in seconds. Similarly, the start of the unavailability period may be information that the UE notifies the network of, indicating the expected start of the unavailability period. The start of the unavailability period may include information that indicates the time until the start of the next unavailability period, and may be expressed in seconds.

[0158] 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.

[0159] 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.

[0160] 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 MME or AMF on the satellite and that the information will be forwarded to the ground network after the feeder link is established.

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

[0162] The eleventh piece of identification information may be information indicating the value of the Wait timer. The Wait timer may be information indicating the amount of time the UE waits before retrying the attach procedure, TAU procedure, or registration procedure for the same PLMN satellite. In other words, while the Wait timer is running, the UE may be controlled to prohibit and / or control and / or wait to send request messages for the attach procedure, TAU procedure, or registration procedure to the current PLMN and / or satellite.

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

[0164] The 12th identification information may be information indicating one or more satellites on which the UE can retry the attach, TAU, or registration procedure after the Wait timer has expired. The 12th identification information may be a list of Satellite IDs, and may be referred to as a list of Satellite IDs. The 12th identification information may include at least one Satellite ID indicating the satellite from which the 12th identification information was transmitted. The 12th identification information may also be information indicating satellites on which the UE is prohibited from retrying the registration procedure (e.g., the attach procedure, TAU procedure, or registration procedure) while the Wait timer is running.

[0165] The 13th identification information may be information about an unavailability period determined and / or set and / or stored by the NW. The 13th identification information may also be an Unavailability configuration IE. The 13th identification information may include at least one of the identification information items 14 to 16.

[0166] The 14th identifying information may include information indicating whether the UE is required to notify the end of the unavailability period. In other words, the 14th identifying information may indicate that the UE is required to notify the end of the unavailability period, or it may indicate that the UE is not required to notify the end of the unavailability period.

[0167] The 15th identification information may be information indicating the length of the unavailable period duration determined and / or set and / or stored by the NW, and may be information indicating the number of seconds. When the 15th identification information is included in the 13th identification information, the 13th identification information may include information indicating that information indicating the length of the unavailable period exists. Conversely, when the 15th identification information is not included in the 13th identification information, the 13th identification information may include information indicating that information indicating the length of the unavailable period does not exist. In other words, the 13th identification information may include information indicating whether or not information indicating the length of the unavailable period exists.

[0168] The sixteenth identification information may be information indicating the start of an unavailability period determined and / or set and / or stored by the NW. The sixteenth identification information may be information indicating the time until the next unavailability period begins, and may be information in seconds.

[0169] When the 16th identification information is included in the 13th identification information, the 13th identification information may include information indicating the existence of information indicating the start of an unavailability period. Conversely, when the 16th identification information is not included in the 13th identification information, the 13th identification information may include information indicating the absence of information indicating the start of an unavailability period. In other words, the 13th identification information may include information indicating the presence or absence of information indicating the start of an unavailability period.

[0170] [3. Description of the procedures used in each embodiment] Next, the procedures used in each embodiment will be described. Note that the procedures used in each embodiment include a registration procedure. The following describes each procedure.

[0171] 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.

[0172] [3.1. Registration Procedure / Attachment Procedure / Tracking Area Renewal Procedure (TAU Procedure)] First, the procedure for a UE to register with and / or attach to a system (e.g., 5GS or EPS) and / or 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 may also be referred to as the MM procedure. For example, this procedure may be a registration procedure, an attach procedure, a tracking area updating procedure (TAU), or any other procedure. Note that the tracking area updating procedure is also called the TAU procedure.

[0173] 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.

[0174] 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.

[0175] 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.

[0176] 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.

[0177] 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.

[0178] 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.

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

[0180] 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).

[0181] 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.

[0182] 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.

[0183] 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.

[0184] 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.

[0185] 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.

[0186] 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.

[0187] 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.

[0188] 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.

[0189] 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.

[0190] 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 first to third identification information in the request message and / or RRC message.

[0191] UE_A10 may include UE capability information in the request message to notify 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 identification information may be the information contained in the 5G MM capability IE for 5GS and / or the UE network capability IE for EPS.

[0192] In other words, if the UE supports the first function, it may set information indicating that it supports the first function in the first identification information and transmit it; if the UE does not support the first function, it may set information indicating that it does not support the first function.

[0193] 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 unavailable periods are supported, and / or whether or not extended discontinuous ranges are supported.

[0194] 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 in its capability information indicating that the UE does not support downtime.

[0195] Similarly, if the UE supports extended discontinuity, it may set information in its capability information indicating that the UE supports extended discontinuity; if the UE does not support extended discontinuity, it may set information in its capability information indicating that the UE does not support extended discontinuity.

[0196] 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.

[0197] UE_A10 may include a third identifier in the request message if the UE needs to indicate an upcoming unavailability due to discontinuous coverage in order to activate an unavailability period.

[0198] Furthermore, if the third identification information is included in the request message, the network may have already provided the UE with network functionality information indicating that it supports the unavailability period and / or extended discontinuity range. In other words, the UE may have received network functionality information from the network in the previous MM procedure indicating that it supports the unavailability period and / or extended discontinuity range.

[0199] 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.

[0200] 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.

[0201] 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.

[0202] 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.

[0203] 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.

[0204] 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).

[0205] Here, if this procedure is performed using a UE and / or satellite and / or NW 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 device selected by the access network may be a mobility management device-onboard (e.g., MME-onboard41 or AMF-onboard141).

[0206] 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 (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.

[0207] 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 third identification pieces of information.

[0208] 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 the NW 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.

[0209] 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 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.

[0210] If the mobile management device-ground receives an MM message from the UE and the sixth identification information from the mobile management device-onboard, it may check whether it has received an MM message from a 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 the other mobile management device-onboard.

[0211] 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.

[0212] 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.

[0213] 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.

[0214] 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.

[0215] 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.

[0216] 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).

[0217] 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.

[0218] 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.

[0219] 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).

[0220] Furthermore, in S606, the mobile management device of the terrestrial network may determine the length of the unavailability period and / or the start of the unavailability period based on the information received from the mobile management device-onboard and / or the UE. In other words, if the information received from the mobile management device-onboard includes a third identification information and / or a seventh identification information, the mobile management device of the terrestrial network may determine and / or store the length of the unavailability period and / or the start of the unavailability period, taking into consideration the third identification information and / or the seventh identification information.

[0221] Specifically, the mobile management device-ground may determine the start and / or length of the unavailability period based on the start of the unavailability period included in the third identification information and the seventh identification information. More specifically, the mobile management device of the terrestrial network may set the length and / or start of the unavailability period based on the unavailability period indicated by the UE indicated by the third identification information, taking into account the difference between the time the UE indicated by the seventh identification information transmitted the third identification information and the time the mobile management device of the terrestrial network actually received the third identification information.

[0222] Alternatively, the determination of information regarding the period of unavailability may be performed by the onboard mobile management device while S&F mode is active. In this case, the mobile management device may transmit a rejection message including at least one of the identification information items 13 to 16.

[0223] If this procedure is performed via satellite, and if the UE and / or satellite and / or NW 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).

[0224] 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 UE 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.

[0225] 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 ground network mobility management device may send the generated control message to mobility management device-onboard (S609).

[0226] If this procedure is performed via satellite, and the UE and / or satellite and / or NW are operating in S&F mode and / or the 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 the feeder link connectivity becomes available (S609).

[0227] The movement management device may send an RRC message to the UE that includes 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.

[0228] 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.

[0229] 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.

[0230] If the request message contains a third identification piece, the movement management device may include a thirteenth identification piece and / or at least one of the fourteenth through sixteenth identification pieces in the control message. In other words, the movement management device may include a thirteenth identification piece and / or at least one of the fourteenth through sixteenth identification pieces in the acceptance message and / or rejection message.

[0231] The mobile management device may determine the length of the unavailability period and / or the start of availability based on satellite coverage availability information stored in the mobile management device and / or received third identification information, and may store and / or provide this information to the UE.

[0232] If the UE receives at least one of the identification information from 13 to 16, and / or if the UE receives a control message containing at least one of the identification information from 13 to 16, the UE may perform the following actions:

[0233] If the UE receives a 13th identification information containing the value of the 15th identification information, it may delete the value of the unavailability period length it has stored and use the value contained in the received 15th identification information to determine the length of the unavailability period, or it may use the value determined by the UE to determine the length of the unavailability period. Otherwise, if the UE receives a 13th identification information that does not contain the value of the 15th identification information, or if the UE receives a control message that does not contain the value of the 15th identification information, the UE may use the value determined by the UE to determine the length of the unavailability period.

[0234] If the UE receives a 13th identification information containing the value of the 16th identification information, it may delete the stored value for the start of the unavailable period and use the value contained in the received 16th identification information to determine the start of the unavailable period, or it may use the value determined by the UE to determine the start of the unavailable period. Otherwise, if the UE receives a 13th identification information that does not contain the value of the 16th identification information, or if the UE receives a control message that does not contain the value of the 16th identification information, it may delete the stored value for the start of the unavailable period and use the value contained in the received 16th identification information to determine the start of the unavailable period, or it may use the value determined by the UE to determine the start of the unavailable period.

[0235] If the UE receives a 13th identification that does not include either the 15th or 16th identification, or if it receives a control message that does not include the 13th identification, the UE may use the value it has determined to determine the length of the unavailability period and / or the start of the unavailability period.

[0236] Alternatively, a UE that has sent a request message containing third identification information may use a value determined by the UE based on the receipt of a rejection message in response to the request message to determine the length of the unavailability period and / or the start of the unavailability period.

[0237] If a UE that has sent a request message containing a third identifier receives a control message (acceptance message and / or rejection message) that does not contain any of the identifiers from the 13th to 16, the UE may use a value determined by the UE to determine the length of the unavailability period and / or the start of the unavailability period.

[0238] When a UE downtime becomes active, all NAS timers are stopped, and procedures associated with stopped NAS timers may be canceled. However, one or more wait timers are exempt from this rule and do not need to be stopped when a UE downtime becomes active.

[0239] When the mobile management device-onboard receives a request message from the UE in S604, 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 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.

[0240] Alternatively, when the mobile management device-onboard receives a request message from the UE in S604, even if the UE and / or satellite and / or NW are operating in S&F mode, if 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 (without sending a rejection message).

[0241] 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.

[0242] Alternatively, if the UE and / or satellite and / or NW support S&F mode, and / or the UE and / or satellite and / or NW 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 the procedure even if they wait for the feeder link connectivity to become active before performing the remaining steps of this procedure (for example, steps S605 to S609 or S605 to S610), 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 to S609, or send an acceptance message in S610 (they do not need to send a rejection message).

[0243] 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).

[0244] 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).

[0245] 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.

[0246] 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 12 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 12 identification information based on information received from the UE and / or the access network and / or the first identification information.

[0247] For example, if the mobile 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 tenth to twelve identification information.

[0248] On the other hand, if the movement 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 send the 10th to 12th identification information. In that case, the movement 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.

[0249] 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.

[0250] 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.

[0251] Upon receiving the 11th identification information, the UE may execute a Wait timer using the value indicated in the 11th identification information. The UE may associate the PLMN ID and / or Satellite ID with the Wait timer, store, and / or manage and execute it. The UE may also stop and / or delete any running Wait timers based on the receipt of the 11th identification information.

[0252] While the Wait timer is running, the UE may control the system so that it does not retry sending the request message to the PLMN and / or satellite indicated by the PLMN ID associated with the Wait timer.

[0253] Upon receiving the 12th identification information, the UE may manage and / or store a list of Satellite ID(s) consisting of one or more Satellite IDs indicated by the 12th identification information, associated with the Wait timer value indicated by the 11th identification information and / or a Wait timer using the value of the 11th identification information.

[0254] 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 AMF, etc.

[0255] 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.

[0256] 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.

[0257] 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.

[0258] 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.

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

[0260] 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.

[0261] 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.

[0262] 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.

[0263] 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.

[0264] 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.

[0265] 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.

[0266] 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).

[0267] 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.

[0268] 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.

[0269] 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.

[0270] 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.

[0271] 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.

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

[0273] Furthermore, if the UE receives the 12th identification information, the 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.

[0274] Furthermore, if the information contained in the 11th identification information is neither 0 nor information indicating deactivate, the UE may start counting the Wait timer and / or start and / or execute control using the Wait timer.

[0275] 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.

[0276] [4. Description of Embodiments] The procedures used in the first and second embodiments may include the MM procedure described above.

[0277] In the embodiments of the present invention, as shown in Figure 2, the example will be described in which the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are each configured as the same device / function (i.e., the same physical hardware, or the same logical hardware, or the same software). However, the contents described in this embodiment are also applicable when these are configured as different devices / functions (i.e., different physical hardware, or 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.

[0278] Hereinafter, a satellite equipped with base station equipment and / or mobile management equipment may be simply referred to as satellite, base station equipment, or mobile management equipment. Here, base station equipment may also be called a base station, and may refer to an access point (for example, an access point used in wireless LANs) that is connected to a gNB, eNB, en-gNB, ng-eNB, or non-3GPP access. MME may be MME-onboard and / or MME-ground, and AMF may be AMF-onboard and / or AMF-ground.

[0279] Also, the UE, and / or the satellite, and / or the network may operate in the S&F mode or may operate in the normal mode. That is, the UE, and / or the satellite, and / or the network may support the function of operating in the S&F mode.

[0280] Also, the UE, and / or the satellite, and / or the network may support the function of connecting the UE to the terrestrial core network via the satellite.

[0281] Hereinafter, examples of specific embodiments of the present invention will be described.

[0282] [4.1 First Embodiment] First, the procedure used in the first embodiment will be described. In the first embodiment, when the S&F mode is active and the UE transmits the third identification information to the satellite, the behavior when the length and / or start of the inaccessibility period are determined by the mobility management device - ground will be described.

[0283] In this embodiment, the first satellite may be equipped with the first base station device and the first mobility management device - onboard, and the second satellite may be equipped with the second base station device and the second mobility management device - onboard. Further, the first mobility management device - onboard, the second mobility management device - onboard, and the mobility management device - ground may act as one mobility management device.

[0284] First, the UE transmits a first request message including the third identification information to the first satellite, and / or the first base station device and / or the first mobility management device - onboard mounted on the first satellite. Here, the request message may be a TAU request message, a registration request message, or other MM messages.

[0285] When the first mobile management device - onboard operates in the S&F mode with the first satellite and / or network, it transmits a rejection message to the UE for the first request message. At this time, the rejection message may include at least one of the identification information from the 10th to the 12th. In other words, the UE receives a rejection message including at least one of the identification information from the 10th to the 12th.

[0286] Based on the information and / or message received from the first mobile management device - onboard, the UE may determine and / or set the unavailable period using the value determined by the UE for the length and / or start of the unavailable period.

[0287] Specifically, based on the fact that the UE has received a rejection message from the first mobile management device - onboard and / or the reason value indicated by the 10th identification information, the UE may use the value determined by the UE for the length and / or start of the unavailable period. The UE may activate the unavailable period based on the information regarding the determined unavailable period and / or based on whether the service link is active. Note that the UE may set the unavailable period for each satellite, and in this case, the unavailable period for the first satellite may be activated.

[0288] Furthermore, based on the information and / or message received from the first mobile management device - onboard, the UE may start a Wait timer. Specifically, the Wait timer may be set and started based on the 10th to 12th identification information received from the first mobile management device - onboard.

[0289] Note that the 12th identification information may include the second satellite ID indicating the second satellite and the first satellite ID indicating the first satellite. In that case, during the execution of the Wait timer, the UE may be prohibited from re - transmitting the first request message to the first satellite and the second satellite.

[0290] On the other hand, when the feeder link becomes available, the first movement management device-onboard transmits the first request message and / or at least one piece of information contained in the first request message, and / or the sixth identification information and / or the seventh identification information to the movement management device-ground.

[0291] The mobile management device-ground may determine information regarding the unavailability period based on the information received from the first mobile management device-onboard, and may decide to initiate the UE authentication procedure and / or the procedure for obtaining UE registration information. In other words, the mobile management device-ground may determine the length of the unavailability period and / or the start of the unavailability period based on the receipt of the third and seventh identification information. 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 receipt of the sixth identification information.

[0292] More specifically, the movement management device-ground may recognize the unavailability period indicated by the UE from the information indicating the length of the unavailability period and / or the start of the unavailability period included in the third identification information, and / or the information indicated in the seventh identification information, and authenticate based on that.

[0293] Specifically, since the start of the unavailability period included in the third identification information indicates the time until the start of the unavailability period, the movement management device-ground may recognize that the start of the unavailability period indicated by the UE is after the time the request message from the UE indicated in the seventh identification information is received and after the value of the start of the unavailability period included in the third identification information.

[0294] Furthermore, the movement management device-ground may recognize that the end of the unavailability period indicated by the UE is after the start of the unavailability period indicated by the UE and the value indicated by the length of the unavailability period included in the third identification information.

[0295] Accordingly, the ground network mobility management device-ground may recognize the downtime indicated by the UE to the network and, taking that into consideration, determine, and / or set, and / or store information regarding the downtime (length of the downtime and / or the start of the downtime).

[0296] If the unavailability period is active after the Wait timer expires, the UE is prohibited from retransmitting the first request message to the first satellite and / or the first mobile management device-onboard, but may be permitted to send the first request message to the second satellite and / or the second mobile management device-onboard.

[0297] In other words, if the unavailability period associated with the first satellite is active after the Wait timer associated with the first and second satellites has expired, the UE may control the system to not retransmit the first request message to the first satellite, but to send the first request to the second satellite.

[0298] As a result, each device can implement control based on the period of unavailability while the S&F mode is active.

[0299] Furthermore, the above may also be applied to NPN (SNPN and / or PNI-NPN). That is, this embodiment may also be applied to NPN by replacing PLMN with SNPN.

[0300] [4.2 Second Embodiment] Next, the procedure used in the second embodiment will be described. In the second embodiment, when S&F mode is active and the UE transmits third identification information to the satellite, the behavior of the mobile management device-onboard when determining the length and start of the unavailability period will be described.

[0301] In this embodiment as well, a first satellite and a second satellite similar to those in the first embodiment may be configured. Further, the first onboard mobility management device, the second onboard mobility management device, and the ground mobility management device may act as one mobility management device.

[0302] First, the UE transmits a first request message including third identification information to the first satellite and / or the first base station device and / or the first onboard mobility management device mounted on the first satellite. Here, the request message may be a TAU request message, a registration request message, or other MM messages.

[0303] When the first satellite and / or the network operates in the S&F mode, the first onboard mobility management device transmits a rejection message to the UE for the first request message. At this time, the rejection message may include at least one identification information among the identification information from 10 to 12. Further, the rejection message may include at least one identification information among the identification information from 13 to 16.

[0304] Based on the information and / or message received from the first onboard mobility management device, the UE may delete the value determined by the UE and use the received value as the length of the inoperable period, or use the value determined by the UE as the length of the inoperable period. Similarly, based on the information and / or message received from the first onboard mobility management device, the UE may delete the value determined by the UE and use the received value as the start of the inoperable period, or use the value determined by the UE as the start of the inoperable period.

[0305] Based on the information regarding the determined inoperable period and / or based on whether the service link is active, the UE may activate the inoperable period. Note that the UE may set the inoperable period for each satellite, and in this case, the inoperable period for the first satellite may be activated.

[0306] Furthermore, the UE may start a wait timer based on information and / or messages received from the first movement management device-onboard. Specifically, the UE may set and start a wait timer based on the 10th to 12th identification pieces received from the first movement management device-onboard.

[0307] The 12th identification information may include a second satellite ID indicating the second satellite and a first satellite ID indicating the first satellite. In this case, the UE may prohibit the retransmission of the first request message to the first and second satellites while the wait timer is running.

[0308] If the feeder link becomes available after being unavailable, the first movement management device-onboard transmits the first request message and / or at least one piece of information contained in the first request message, and / or the sixth identification information, and / or information regarding the period of unavailability determined by the first movement management device-onboard, to the movement management device-ground.

[0309] In other words, if the feeder link becomes available after being unavailable, the movement management device-ground may receive the first request message and / or at least one piece of information contained in the first request message, and / or the sixth identification information, and / or information regarding the period of unavailability determined by the first movement management device-onboard.

[0310] The mobile management device-ground may recognize the period of unavailability based on the information received from the first mobile management device-onboard. Based on the receipt of the sixth identification information, the mobile management device-ground may decide to initiate the UE authentication procedure and / or the procedure for obtaining UE registration information.

[0311] Based on the above, the mobile management device-ground may recognize the downtime indicated by the UE on the network and, taking that into consideration, determine, and / or set, and / or store information regarding the downtime (length of the downtime and / or the start of the downtime).

[0312] If the unavailability period is active after the Wait timer expires, the UE is prohibited from retransmitting the first request message to the first satellite and / or the first mobile management device-onboard, but may be permitted to send the first request message to the second satellite and / or the second mobile management device-onboard.

[0313] In other words, if the unavailability period associated with the first satellite is active after the Wait timer associated with the first and second satellites has expired, the UE may control the system to not retransmit the first request message to the first satellite, but to send the first request to the second satellite.

[0314] As a result, each device can implement control based on the period of unavailability while the S&F mode is active.

[0315] Furthermore, the above may also be applied to NPN (SNPN and / or PNI-NPN). That is, this embodiment may also be applied to NPN by replacing PLMN with SNPN.

[0316] [5. Variant] A program operating 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 the embodiment according to the present invention. The program or the 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.

[0317] 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.

[0318] 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.

[0319] 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.

[0320] 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. [Explanation of Symbols]

[0321] 1. Mobile communication systems 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. A UE comprising a control unit and a transmitting / receiving unit, The aforementioned transmitting and receiving unit is A request message containing information indicating the period of unavailability is sent to the mobile management device onboard the satellite. The movement management device receives a rejection message in response to the request message. The control unit, If the rejection message does not include a second value indicating the length of the unavailability period, the UE will use the first value it has determined. If the rejection message includes the second value, the UE will use the first value determined by the UE, or delete the first value determined by the UE and use the received second value. A UE characterized by the following:

2. A mobile management device installed on the ground, It comprises a control unit and a transmitting / receiving unit, The aforementioned mobile management device is connected to a second mobile management device mounted on the satellite. If the aforementioned connectivity becomes available after it has become unavailable, The transmitting / receiving unit receives a first request message and a value indicating a first time from the second movement management device. The control unit, If, after the first time, a second request message is received from a mobile management device on another satellite, the authentication procedure based on the first request message is skipped. If, after the first time, the second request message has not been received from the mobile management device on another satellite, the authentication procedure shall be initiated. A mobile management device characterized by the following features.

Images