User equipment (UE)

Abstract

To solve the problem in which, although the standardization of communications related to the connection of UE to the 5G core network via New Radio (NR) satellite access, which provides discontinuous coverage, is being promoted, yet required information, required transmission and reception of the information, and required behavior and processing of the UE and each device are not clear in the execution of a network-led registration update procedure executed to update information such as the location of the UE when the UE returns to the coverage area of NR satellite access from an outside thereof.SOLUTION: The present invention provides: identification information with which UE and a network exchange information with each other in advance, the information being required for execution of a network-led registration update procedure that is executed when the UE returns to the coverage area of NR satellite access from an outside thereof; execution of the registration update procedure based on the identification information; control of the execution mode of the registration update procedure; and control of conditions for executing the registration update procedure.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] The present invention relates to User Equipment (UE). [Background technology]

[0002] 3GPP (3rd Generation Partnership Project: registered trademark) is considering the system architecture of 5GS (5G System), which is a fifth generation (5G) mobile communication system, and is discussing how to support new procedures and new functions (see Non-Patent Documents 1 to 4). In Release 18 of the 5G standard, the architecture for 5G communication via artificial satellites (also simply called "satellites"), procedures for communication and control, etc. are being considered (see Non-Patent Document 4). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 23.501 V18.1.0 (2023-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18) [Non-Patent Document 2] 3GPP TS 23.502 V18.1.0 (2023-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 18) [Non-Patent Document 3] 3GPP TS 24.501 V18.2.0 (2023-03); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 18) [Non-Patent Document 4] 3GPP TR 23.700-28 V18.1.0 (2023-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Integration of satellite components in the 5G architecture; Phase 2 (Release 18) Summary of the Invention [Problem to be solved by the invention]

[0004] In the 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered to provide a wide variety of services. In addition, architecture for 5G communication via satellites (also simply called "satellites") is being considered.

[0005] Currently, in such communication architectures that use satellites as a wireless technology (radio access technology) connecting user equipment (UE) and a core network, studies are underway on extending conventional procedures, messages, or parameters to take into account the characteristics of wireless connections via satellite.

[0006] On the other hand, in communications via satellites that provide discontinuous coverage, the information required to execute a network-initiated registration and update procedure, which is performed to update information such as the UE's location when the UE connects to a network via NR (New Radio) satellite access and returns to coverage from outside the coverage area, as well as the transmission and reception of information, and the behavior and processing of the UE and each device, have not been clearly defined.

[0007] One aspect of the present invention has been made in consideration of the above circumstances, and its purpose is to provide a method for appropriately controlling the execution and execution mode of a network initiated registration update procedure when a UE returns to coverage from outside of NR satellite access coverage. [Means for solving the problem]

[0008] A UE (User Equipment) of one embodiment of the present invention is a UE having a transceiver unit and a control unit, wherein the transceiver unit receives a configuration update command message or a registration acceptance message including first identification information from a network via satellite access, the first identification information being identification information indicating that when the UE returns to within the satellite access range from outside the satellite access range, the network requests that the UE initiate a registration update procedure with the network via the satellite access, and further, the first identification information is associated with a PLMN (Public Land Mobile Network), and / or a RAT (Radio Access Technology) type, and / or an access type, and / or an area, and the control unit is characterized in that when the UE returns to within the satellite access range from outside the satellite access range, the control unit initiates the registration update procedure with the network via the satellite access based on the first identification information. Effect of the Invention

[0009] According to one aspect of the present invention, a means is provided for transmitting and receiving parameters between the UE and the network related to a network-initiated registration update procedure and appropriately controlling the same based on the parameters when a UE connected to a 5G network via an NR satellite access providing discontinuous coverage returns to the coverage area of ​​the NR satellite access from outside the coverage area. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an overview of a mobile communication system (EPS / 5GS). [Diagram 2] A diagram explaining the detailed configuration of a mobile communication system (EPS / 5GS). [Diagram 3] A diagram explaining the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Diagram 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 1 is a diagram illustrating a registration procedure. [Figure 7] FIG. 1 is a diagram illustrating a network-initiated mobility management procedure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0012] [1. System Overview] First, FIG. 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment, and FIG. 2 is a diagram for explaining a detailed configuration of the mobile communication system 1. As shown in FIG.

[0013] FIG. 1 shows that the mobile communication system 1 is composed 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.

[0014] In the following, these devices and functions may be described with abbreviated symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0015] 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 interfaces that connect these devices and functions to each other.

[0016] In the following, these devices and functions may be referred to by abbreviated symbols, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0017] In addition, the 4G system EPS (Evolved Packet System) is configured to include an access network _A and a core network _A, but may further include a UE and / or a PDN. In addition, the 5G system 5GS (5G System) is configured to include a UE, an access network _B, and a core network _B, but may further include a DN.

[0018] The UE is a device that can connect to a network service via 3GPP access (also referred to as a 3GPP access network, 3GPP AN) and / or non-3GPP access (also referred to as a non-3GPP access network, 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 that can connect to both EPS and 5GS. The UE may include a Universal Integrated Circuit Card (UICC) or an Embedded UICC (eUICC). The UE may be expressed as a user device or a terminal device.

[0019] Moreover, the access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. In the E-UTRAN, one or more eNBs (evolved Node B) 45 are arranged. In the following, the eNB 45 may be written with the symbol omitted, such as eNB. In addition, when there are multiple eNBs, the eNBs are connected to each other, for example, by an X2 interface. In addition, one or more access points are arranged in the wireless LAN access network.

[0020] Moreover, the access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are arranged in the NG-RAN. In the following, the gNB 122 may be written with the symbol omitted, such as gNB. The 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 an N2 interface or an N3 interface). That is, the gNB is a base station device newly designed for the 5GS, and has a different function from the base station device (eNB) used in the EPS, which is a 4G system. In addition, when there are multiple gNBs, each gNB is connected to each other, for example, by an Xn interface.

[0021] Furthermore, the non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the 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, the trusted non-3GPP access network may be an access network defined by 3GPP, and may include a trusted non-3GPP access point (TNAP) and a trusted non-3GPP Gateway function (TNGF).

[0022] In the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. In addition, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. In addition, nodes arranged in the access network_B may be collectively referred to as NG-RAN nodes.

[0023] In addition, in the following, access network _A, and / or access network _B, and / or devices included in access network _A, and / or devices included in access network _B may be referred to as access networks or access network devices.

[0024] Moreover, the core network_A corresponds to an EPC (Evolved Packet Core). In the EPC, for example, an MME (Mobility Management Entity), an SGW (Serving Gateway), a PGW (Packet Data Network Gateway)-U, a PGW-C, a PCRF (Policy and Charging Rules Function), an HSS (Home Subscriber Server), etc. are arranged.

[0025] Moreover, the core network_B corresponds to a 5G Core Network (5GCN). For example, an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), and a Unified Data Management (UDM) are arranged in the 5GCN. Here, the 5GCN may be expressed as a 5GC.

[0026] In addition, in the following, core network _A and / or core network _B, devices included in core network _A, and / or devices included in core network _B may be referred to as core networks, core network devices, or devices within a core network.

[0027] 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, or 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 such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler) or a virtual mobile communication service provider.

[0028] Also, in FIG. 1, the PDN and the DN are the same, but they may be different. The PDN may be a DN (Data Network) that provides a communication service to the UE. The DN may be configured as a packet data service network, or may be configured for each service. Furthermore, the PDN may include a communication terminal connected thereto. Therefore, connecting to the PDN may be connecting to a communication terminal or a server device arranged in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may be transmitting and receiving user data to and from a communication terminal or a server device arranged in the PDN. The PDN may be expressed as the DN, and the DN may be expressed as the PDN.

[0029] In addition, in the following, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device transmits or receives a message and / or executes a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein transmits or receives a message and / or executes a procedure.

[0030] The UE can also connect to an access network. The UE can also connect to a core network via the access network. The UE can also connect to a PDN or DN via the access network and the core network. That is, the UE can transmit and receive (communicate) user data between the PDN or DN. When transmitting and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication may be used.

[0031] Here, IP communication refers to data communication using IP, and data is transmitted and received by IP packets. The IP packet is composed of an IP header and a payload section. The payload section may include data transmitted and received by devices and functions included in EPS and devices and functions included in 5GS. In addition, non-IP communication refers to data communication that does not use IP, and data is transmitted and received in a format different from the structure of an IP packet. For example, non-IP communication may be data communication realized by transmitting and receiving application data to which an IP header is not attached, or may be user data transmitted and received by a UE with another header such as a MAC header or an Ethernet (registered trademark) frame header attached.

[0032] In addition, the access network_A, the core network_A, the access network_B, the core network_B, the PDN_A, and the DN_A may be configured with devices not shown in Fig. 2. For example, the core network_A and / or the core network_B may include an AUSF (Authentication Server Function) and an AAA (Authentication, authorization, and accounting) server (AAA-S).

[0033] Here, the AUSF is a core network device having an authentication function for 3GPP access and non-3GPP access, specifically, a network function unit that receives an authentication request for 3GPP access and / or non-3GPP access from a UE and executes an authentication procedure.

[0034] The AAA server is a device that is connected to the AUSF directly or indirectly via another network device and has authentication, authorization, and accounting functions. The AAA server may be a network device in the core network. The AAA server may not be included in the core network_A and / or the core network_B, but may be included in the PLMN. In other words, the AAA server may be a core network device or a device outside the core network. For example, the AAA server may be a server device in the PLMN managed by a third party.

[0035] 2, for the sake of simplicity, one of each device and function is shown, but a plurality of similar devices and functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may be configured with a plurality of devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150.

[0036] The UPF_A235 is connected to the DN, the SMF, other UPFs, and the access network. The UPF_A235 may perform roles such as an anchor for intra-RAT mobility or inter-RAT mobility, packet routing & forwarding, a UL CL (Uplink Classifier) ​​function supporting routing of multiple traffic flows for one DN, a branching point function supporting a multi-homed PDU session, QoS processing for the user plane, verification of uplink traffic, buffering of downlink packets, and a trigger function for downlink data notification. The UPF_A235 may also be a relay device that forwards user data as a gateway between the DN and the core network_B190. The UPF_A235 may also be a gateway for IP communication and / or non-IP communication. The UPF_A235 may also have a function of forwarding IP communication and a function of converting non-IP communication to IP communication. Furthermore, multiple gateways may be deployed, and may be gateways that connect the core network_B190 to a single DN. Note that the UPF_A235 may have connectivity with other NFs and may be connected to each device via other NFs.

[0037] In addition, UPF_C239 (also called a branching point or uplink classifier), which is a UPF different from UPF_A235, may exist as a device or NF between UPF_A235 and the access network. When UPF_C239 exists, a PDU session between the UE and the DN is established via the access network, UPF_C239, and UPF_A235.

[0038] Moreover, the UPF 130 may be the same device as the UPF_A 235. Note that the UPF 130 and the UPF_A 235 may be described with the symbol omitted, such as UPF.

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

[0040] Each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) in each device / function described below is composed of, for example, a semiconductor memory, a solid state drive (SSD), a hard disk drive (HDD), etc. Each memory unit can store not only information that was originally set at the time of shipment, but also various information transmitted and received between the device / function other than the device / function itself (for example, UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Each memory unit can store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described later. Each memory unit may store this information for each UE. Each memory unit can store control messages and user data transmitted and received between the device / function included in the 5GS and / or EPS when interworking is performed between the 5GS and EPS. At this time, not only those transmitted and received via the N26 interface but also those transmitted and received without passing through the N26 interface can be stored.

[0041] [2.1. UE device configuration] First, an example of the device configuration of UE (User Equipment) will be described with reference to Fig. 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

[0042] The control unit _A300 is a functional unit that controls the operation and functions of the entire UE. The control unit _A300 realizes various processing in the UE by reading and executing various programs stored in the memory unit _A340 as necessary.

[0043] The transceiver unit _A320 is a functional unit for wirelessly communicating with a base station device (eNB or gNB) in an access network via an antenna. That is, the UE can use the transceiver unit _A320 to transmit and receive user data and / or control information between an access network device, and / or a core network device, and / or a PDN, and / or a DN.

[0044] Explaining in detail with reference to FIG. 2, the UE can communicate with a base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver unit _A320. The UE can also communicate with a base station device (gNB) in the 5G AN by using the transceiver unit _A320. The UE can also transmit and receive AMF and NAS (Non-Access-Stratum) messages via the N1 interface by using the transceiver unit _A320. However, since the N1 interface is logical, in reality, communication between the UE and the AMF is performed via the 5G AN.

[0045] The memory unit _A340 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UE.

[0046] [2.2. gNB device configuration] Next, an example of the device configuration of the gNB will be described with reference to Fig. 4. The gNB is composed of a control unit _B500, an antenna 510, a network connection unit _B520, a transceiver unit _B530, and a memory unit _B540. The control unit _B500, the network connection unit _B520, the transceiver unit _B530, and the memory unit _B540 are connected via a bus. The transceiver unit _B530 is connected to the antenna 510.

[0047] The control unit _B500 is a functional unit that controls the operation and functions of the entire gNB. The control unit _B500 realizes various processes in the gNB by reading and executing various programs stored in the memory unit _B540 as necessary.

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

[0049] The transceiver unit _B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information between the UE and the transceiver unit _B530.

[0050] 2, the gNB in ​​the 5G AN can communicate with the AMF via the N2 interface by using the network connection unit _B 520, and can communicate with the UPF via the N3 interface. The gNB can also communicate with the UE by using the transceiver unit _B 530.

[0051] The memory unit _B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB.

[0052] [2.3. AMF device configuration] Next, an example of the device configuration of the AMF will be described with reference to FIG. 5. The AMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The AMF may be a node that handles the control plane. The AMF may also be a network device. In other words, for example, in this specification, the network device may mean the AMF.

[0053] The control unit _B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit _B700 realizes various processing in the AMF by reading and executing various programs stored in the memory unit _B740 as necessary.

[0054] The network connection unit _B720 is a functional unit for the AMF to connect to a base station device (gNB), and / or an SMF, and / or a PCF, and / or an UDM, and / or an SCEF in a 5G AN. That is, the AMF can transmit and receive user data and / or control information between a base station device (gNB), and / or an SMF, and / or a PCF, and / or an UDM, and / or an SCEF in a 5G AN using the network connection unit _B720. In other words, for example, the network connection unit may be a transceiver unit.

[0055] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with the gNB via the N2 interface by using the network connection unit_A620, can communicate with the UDM via the N8 interface, can communicate with the SMF via the N11 interface, and can communicate with the PCF via the N15 interface. In addition, the AMF can transmit and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, in reality, communication between the UE and the AMF is performed via the 5G AN. In addition, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit_A620.

[0056] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of AMF.

[0057] In addition, the AMF has a function of exchanging control messages with the RAN using the N2 interface, a function of exchanging NAS messages with the UE using the N1 interface, a function of encrypting and protecting the integrity of NAS messages, a registration management (RM) function, a connection management (CM) function, a reachability management function, a mobility management function for UEs, etc., a function of transferring SM (Session Management) messages between the UE and the SMF, an access authentication (access authorization) function, a security anchor functionality (SEA), a security context management (SCM) function, a function of supporting the N2 interface for the N3IWF (Non-3GPP Interworking Function), a function of supporting the transmission and reception of NAS signals with the UE via the N3IWF, and a function of authenticating UEs connected via the N3IWF.

[0058] In addition, in the registration management, the RM state of each UE is managed. The RM state may be synchronized between the UE and the AMF. The RM state includes a non-registered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered in the network, and therefore the UE context in the AMF does not have valid location information or routing information for the UE, and therefore the AMF cannot reach the UE. In the RM-REGISTERED state, the UE is registered in the network, and therefore the UE can receive services that require registration with the network. The RM state may be expressed as a 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as a 5GMM-REGISTERED state.

[0059] In other words, 5GMM-REGISTERED may be a state in which each device has established a 5GMM context, or may be a state in which each device has established a PDU session context. When each device is 5GMM-REGISTERED, UE_A10 may start transmitting and receiving user data and control messages, or may respond to paging. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may execute a registration procedure other than the registration procedure for initial registration, and / or a service request procedure.

[0060] Furthermore, 5GMM-DEREGISTERED may be a state in which each device has not established a 5GMM context, a state in which the location information of UE_A10 is not known to the network, or a state in which the network cannot reach UE_A10. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or establish a 5GMM context by executing the registration procedure.

[0061] In addition, in the connection management, the CM state of each UE is managed. The CM state may be synchronized between the UE and the AMF. The CM state includes a non-connected state (CM-IDLE state) and a 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. In the CM-IDLE state, the UE does not have a connection (N2 connection) of the N2 interface and a connection (N3 connection) of the N3 interface. On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. In the CM-CONNECTED state, the UE may have a connection (N2 connection) of the N2 interface and / or a connection (N3 connection) of the N3 interface.

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

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

[0064] In addition, one or more AMFs may be placed in the core network_B. In addition, the AMF may be a network function (NF) that manages one or more network slice instances (NSIs). In addition, the AMF may be a common control plane network function (CCNF) shared between multiple NSIs.

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

[0066] [2.4. SMF device configuration] Next, an example of the device configuration of the SMF will be explained using Figure 5. The SMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The SMF may be a node that handles the control plane.

[0067] The control unit _B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit _B700 realizes various processing in the SMF by reading and executing various programs stored in the memory unit _B740 as necessary.

[0068] The network connection unit _B720 is a functional unit for connecting the SMF to the AMF, and / or the UPF, and / or the PCF, and / or the UDM. In other words, the SMF can use the network connection unit _B720 to transmit and receive user data and / or control information between the AMF, and / or the UPF, and / or the PCF, and / or the UDM.

[0069] Explaining in detail with reference to Figure 2, the SMF in the 5GCN can communicate with the AMF via the N11 interface, can communicate with the UPF via the N4 interface, can communicate with the PCF via the N7 interface, and can communicate with the UDM via the N10 interface, by using the network connection unit _A620.

[0070] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the SMF.

[0071] The SMF has a session management function such as establishing, modifying, and releasing PDU sessions, an IP address allocation for UEs and its management function, a UPF selection and control function, a UPF setting function for routing traffic to the appropriate destination (destination), a function for sending and receiving the SM part of NAS messages, a function for notifying that downlink data has arrived (Downlink Data Notification), a function for providing AN-specific (for each AN) SM information to be sent to the AN via the N2 interface via the AMF, a function for determining the SSC mode (Session and Service Continuity mode) for the session, and a roaming function.

[0072] [2.5. UPF device configuration] Next, an example of the device configuration of the UPF will be described with reference to Fig. 5. The UPF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory 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 realizes various processing in the UPF by reading and executing various programs stored in the memory unit _B740 as necessary.

[0074] The network connection unit _B720 is a functional unit for the UPF to connect to a base station device (gNB), and / or SMF, and / or DN in the 5G AN. In other words, the UPF can transmit and receive user data and / or control information between the base station device (gNB), and / or SMF, and / or DN in the 5G AN using the network connection unit _B720.

[0075] Explaining in detail with reference to Figure 2, by using network connection unit _A620, the UPF in the 5GCN can communicate with a gNB via an N3 interface, can communicate with an SMF via an N4 interface, can communicate with a DN via an N6 interface, and can communicate with other UPFs via an N9 interface.

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

[0077] The UPF has functions such as an anchor point for intra-RAT mobility or inter-RAT mobility, an external PDU session point for interconnecting to DNs (i.e., a function for forwarding user data as a gateway between DN and core network_B), a packet routing and forwarding function, a UL CL (Uplink Classifier) ​​function that supports routing of multiple traffic flows for one 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 for triggering downlink data notification.

[0078] The UPF may also be a gateway for IP communication and / or non-IP communication. The UPF may also have a function for forwarding IP communication, and may also have a function for converting non-IP communication and IP communication. Furthermore, the multiple gateways may be gateways that connect the core network_B to a single DN. The UPF may also have connectivity with other NFs, and may be connected to each device via other NFs.

[0079] The user plane refers to user data transmitted and received between the UE and the network. The user plane may be transmitted and received using a PDN connection or a PDU session. Furthermore, in the case of EPS, the user plane 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. Furthermore, in the case of 5GS, the user plane may be transmitted and received via an interface between the UE and the NG RAN, and / or the N3 interface, and / or the N9 interface, and / or the N6 interface. Hereinafter, the user plane may be expressed as U-Plane.

[0080] Furthermore, the control plane refers to a control message transmitted and received to control communication of the UE. The control plane may be transmitted and received using a Non-Access-Stratum (NAS) signaling connection between the UE and the MME. Furthermore, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Furthermore, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and the NG RAN and the N2 interface. Hereinafter, the control plane may be expressed as the control plane or the C-Plane.

[0081] Furthermore, the U-Plane (User Plane; UP) may be a communication path for transmitting and receiving user data and may be composed of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may be a communication path for transmitting and receiving control messages and may be composed of multiple bearers.

[0082] [2.6. Description of other equipment and / or functions] Next, other devices and / or functions will be described.

[0083] The PCF has a function of providing policy rules.

[0084] The UDM also has an authentication credential processing function, a user identification processing function, an access authentication function, a registration / mobility management function, a subscription management function, and the like.

[0085] The PCRF is connected to the PGW and / or the PDN and has a function of managing QoS for data delivery. For example, the PCRF manages the QoS of the communication path between the UE_A10 and the PDN. The PCRF may also be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used by each device when transmitting and receiving user data.

[0086] The HSS is connected to the MME and / or the SCEF and has a function of managing subscriber information. The subscriber information of the HSS is referred to, for example, when controlling access to the MME. Furthermore, the HSS may be connected to a location management device different from the MME.

[0087] [3. Explanation of terms and identification information used in each embodiment] Next, terms and identification information used in each embodiment will be explained in advance.

[0088] [3.1. Explanation of terms used in each embodiment] Next, highly specialized terms used in each embodiment and identification information used in the procedures will be described.

[0089] The network refers to at least a part of the access network _B, the core network _B, and the DN. Furthermore, one or more devices included in at least a part of the access network _B, the core network _B, and the DN may be referred to as a network or a network device. In other words, when a network transmits, receives, and / or processes messages, it may mean that a device in the network (a network device and / or a control device) transmits, receives, and / or processes messages. Conversely, when a device in the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, and / or processes messages.

[0090] The SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a NAS message used in procedures for SM, and may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240. Furthermore, the SM message may include a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message, a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, etc. Furthermore, the procedure for SM or the SM procedure may include a PDU session establishment procedure, a PDU session modification procedure, and a UE-requested PDU session release procedure.Each procedure may be initiated by the UE or may be initiated by the NW.

[0091] An MM (Mobility management) message (also referred to as a NAS MM message) may be a NAS message used in a procedure for MM, and may be a control message transmitted and received between UE_A10 and AMF_A240. Furthermore, the MM message may include a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, and the like. Furthermore, the procedures for MM or MM procedures may include a Registration procedure, a De-registration procedure, a Generic UE configuration update procedure (also simply referred to as a UE configuration update procedure), an Authentication and / or Authorization procedure, a Service request procedure, a Paging procedure, and a Notification procedure.

[0092] The 5GS (5G System) service is a connection service provided using the core network_B190. Furthermore, the 5GS service may be a service different from the EPS service or may be a service similar to the EPS service.

[0093] Non-5GS services may be services other than 5GS services and may include EPS services and / or non-EPS services.

[0094] PDN (Packet Data Network) type indicates the type of PDN connection, and can be IPv4, IPv6, IPv4v6, or non-IP. 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 IPv4v6 is specified, it indicates that data will be sent and received using either IPv4 or IPv6. If non-IP is specified, it indicates that communication will not be via IP, but rather via a communication method other than IP.

[0095] A PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between a DN providing a PDU connectivity service and a UE, but may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data between a DN and a DN by establishing a PDU session via an access network_B and a core network_B. Here, the external gateway may be a UPF, a SCEF, or the like. A UE can transmit and receive user data to and from a device such as an application server located in a DN by using a PDU session. Each device (UE, and / or an access network device, and / or a core network device) may manage one or more pieces of identification information in association with a PDU session. These pieces of identification information may include one or more of a DNN, a QoS rule, a PDU session type, an application identification information, an NSI identification information, an access network identification information, and an SSC mode, or may further include other information. Furthermore, when a plurality of PDU sessions are established, each piece of identification information associated with a PDU session may be the same or different.

[0096] The DNN (Data Network Name) may be identification information for identifying a core network and / or an external network such as a DN. Furthermore, the DNN may be used as information for selecting a gateway such as a PGW / UPF that connects the core network B190. Furthermore, the DNN may be equivalent to an APN (Access Point Name).

[0097] The PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of the PDU session, and can be IPv4, IPv6, Ethernet, or Unstructured. If IPv4 is specified, it indicates that data is transmitted and received using IPv4. If IPv6 is specified, it indicates that data is transmitted and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames are transmitted and received. Ethernet may also indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data is transmitted and received to an application server or the like in a DN using Point-to-Point (P2P) tunneling technology. As the P2P tunneling technology, for example, UDP / IP encapsulation technology may be used. In addition to the above, the PDU session type may also include IP. IP can be specified when the UE is capable of using both IPv4 and IPv6.

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

[0099] A tracking area is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. The tracking area may be composed of multiple cells. Furthermore, the tracking area may be a range in which control messages such as paging are broadcast, or a range in which UE_A10 can move without performing a handover procedure. Furthermore, the tracking area may be a routing area, a location area, or anything similar to these. Hereinafter, the tracking area may be a TA (Tracking Area). The tracking area may be identified by a TAI (Tracking Area Identity) composed of a TAC (Tracking area code) and a PLMN.

[0100] A registration area is a collection of one or more TAs that the AMF assigns to a UE. Note that while UE_A10 is moving within one or more TAs included in the registration area, it may be able to move without sending or receiving a signal for tracking area update. In other words, a registration area may be a group of information indicating an area in which UE_A10 can move without performing a tracking area update procedure. A registration area may be identified by a TAI list consisting of one or more TAIs.

[0101] The Current TAI is the TAI broadcast by the selected PLMN in the cell where the UE is located or camped, or if the cell is a satellite NG-RAN cell that broadcasts multiple TACs in the selected PLMN, the UE NAS layer may select the current TAI from multiple Tracking Area Codes (TACs) in the selected PLMN.

[0102] The Lists of 5GS forbidden tracking areas may be a list of 5GS forbidden tracking areas for roaming and / or a list of 5GS forbidden tracking areas for regional provision of service stored by a UE not operating in an SNPN access operation mode. In other words, a UE not operating in an SNPN access operation mode must store a list of 5GS forbidden tracking areas for roaming and / or a list of 5GS forbidden tracking areas for regional provision of service. Furthermore, the UE needs to search for a suitable cell in the same PLMN that belongs to a TA that is not included in the list of 5GS forbidden tracking areas.

[0103] Furthermore, the UE is not permitted to request 5GS services other than emergency services if it is located in a cell of a TA that belongs to the list of 5GS forbidden tracking areas for regional provision of service.

[0104] The UE may also store the forbidden tracking area ID (TAI) in a list of 5GS forbidden tracking areas for regional service provision to prevent repeated access attempts to cells in the forbidden tracking area. Furthermore, the list of 5GS forbidden tracking areas for regional service provision may be deleted when the UE is powered off, when the SIM is removed, or periodically (for a period ranging from 12 to 24 hours).

[0105] In addition, information indicating the 5GS forbidden tracking areas for roaming may be included in an information element (Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE (Information Element)) included in a message sent by the network and transmitted to the UE.

[0106] In addition, the 5GS forbidden tracking areas for regional provision of service may be included in an information element (Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE (Information Element)) included in a message sent by the network and transmitted to the UE.

[0107] The UE ID is information for identifying a UE. For example, the UE ID may be a SUCI (Subscription Concealed Identifier), or a SUPI (Subscription Permanent Identifier), or a GUTI (Globally Unique Temporary Identifier), or an IMEI (International Mobile Subscriber Identity), or an IMEISV (IMEI Software Version), or a TMSI (Temporary Mobile Subscriber Identity). Alternatively, the UE ID may be other information set in an application or a network. Furthermore, the UE ID may be information for identifying a user.

[0108] An NTN (Non-terrestrial network) may be an NG-RAN consisting of multiple gNBs, which provides non-terrestrial NR access to UEs via NTN payloads and NTN gateways mounted on NTN transmission means such as satellites, aircraft, etc. installed in space or in the air.

[0109] Here, the NTN payload is a network node mounted on a satellite or a high altitude platform station and provides a connection function between a service link and a feeder link. Furthermore, the NTN payload may be a TNL (Transport Network Layer) node.

[0110] An NTN Gateway is an earth station installed on the Earth's surface that provides connectivity to an NTN payload using a feeder link, and may be a Transport Network Layer (TNL) node.

[0111] In other words, for example, a "NR connection via satellite" (NR satellite access) by a UE may be an NR connection via a satellite (also referred to simply as a satellite in this specification) carrying an NTN payload and a gNB consisting of an NTN gateway. Furthermore, the UE may perform procedures for registering with the network and / or establishing a PDU session via the NR connection, and may further perform communication using the established PDU session after completion of these procedures.

[0112] Herein, communication via an NTN is also referred to as communication via NR satellite access, or communication via satellite access, or communication via an NTN, or NTN communication, or 5GSAT communication, or satellite communication, etc. Also, an NR connection via a satellite (i.e., an NTN) is also referred to as NR satellite access, or connection via satellite, or access via satellite, or satellite radio access, or satellite access, etc. Also, the NR satellite access may be a 3GPP access.

[0113] A TN (terrestrial network) may provide terrestrial radio access to UEs through an access network configured by base stations installed on the ground. In contrast to an NTN, which is a non-terrestrial network using satellites, a TN may be a terrestrial network. In addition, an access network installed and configured on the ground may be, for example, an NG-RAN configured by multiple gNBs, or an E-UTRAN configured by multiple eNBs, but is not limited to these.

[0114] Herein, communication via a TN is also referred to as communication via NR terrestrial access, or communication via a TN, TN communication, or non-satellite communication, etc. Also, an NR connection via a TN is also referred to as NR terrestrial access, or connection or access via a non-satellite, or non-satellite access, etc.

[0115] The satellite NG-RAN Radio Access Technology (RAT) type may be information used to identify or distinguish different types of satellite NG-RAN access in satellite NG-RAN access. The satellite NG-RAN RAT type may be, for example, "NR (LEO)", "NR (MEO)", "NR (GEO)", and "NR (OTHERSAT)". Here, "LEO" may mean a low earth orbit satellite, "MEO" may mean a middle earth orbit satellite, "GEO" may mean a geostationary earth orbit satellite, and "OTHERSAT" may mean other satellites.

[0116] Here, the access technology may be associated with a PLMN or an SNPN, and further, the PLMN or SNPN may be capable of supporting multiple access technologies, where the UE may use the access technology information to determine the type of wireless carrier when selecting a particular PLMN or SNPN.

[0117] The AMF may also determine the RAT type of the NR satellite access, and if the UE is accessing the NR using the satellite access, an indication indicating the type of the NR satellite access may be provided on the N2 interface. In addition, for the serving PLMN to implement efficient mobility restrictions for NR access, the TA in which the cell of each NR satellite RAT type is deployed must be different from the TAs of other different satellite RAT types and the TAs of the terrestrial access RAT types. Furthermore, the AMF may initiate deregistration of the UE when it receives an N2 UE Context Release Request with a cause value indicating that the UE is not in the PLMN serving area.

[0118] In addition, for example, the coverage of NR satellite access provided by MEO and LEO satellites or satellite constellations is discontinuous, and such coverage is also called discontinuous network coverage. Here, discontinuous coverage is caused by, for example, MEO and LEO satellites or satellite constellations moving in time series with respect to a specific location on the earth, and therefore the coverage that these satellites or satellite constellations can provide is discontinuous. Note that geostationary satellites (GEO) can provide coverage to a specific time and location on the earth, so the problem of discontinuous network coverage does not basically occur.

[0119] In addition, a UE connected to a network via NR satellite access providing such discontinuous network coverage moves between out of coverage and in coverage in a time series. For this reason, each device of the UE and / or the network may support part or all of one or more functions including controls, parameters, or procedures for supporting the discontinuous network coverage provided by the NR satellite access. In this case, in coverage may mean a coverage (area) where the UE can communicate with a satellite, or a coverage (area) where the UE can communicate via a satellite. In addition, out of coverage may mean a coverage (area) where the UE cannot communicate with a satellite, or a coverage (area) where the UE cannot communicate via a satellite.

[0120] More specifically, the one or more functions including the control, parameters, or procedures for supporting discontinuous network coverage provided by the NR satellite access may include satellite coverage availability information, and / or mobility pattern, and / or UE out-of-coverage period (Unreachable period), and / or Unreachability period, and / or overload control (which may also be referred to as congestion control) in the discontinuous coverage provided by the NR satellite access, and / or a maximum waiting time for overload control in the discontinuous coverage, and / or a discontinuous coverage wait timer value for overload control in the discontinuous coverage, and / or a back-off timer in the discontinuous coverage provided by the NR satellite access, and / or timer offset information in the NR satellite access providing discontinuous coverage. These are described below.

[0121] Satellite coverage availability information is location and time information related to the expected availability of coverage of a satellite or a satellite constellation that provides discontinuous coverage. In other words, satellite coverage availability information may be information of a location or time when satellite access provided by a satellite or a satellite constellation is expected to be available for use by a UE. That is, satellite coverage availability information may be information indicating the expected in- or out-of-range of a UE at the location and time indicated by the information. In this specification, satellite coverage availability information is also simply referred to as satellite coverage information.

[0122] The UE may also use the satellite coverage availability information to support operation in discontinuous coverage in a satellite access or connection. Furthermore, the satellite coverage availability information may be provided to the UE from an external server via a PDU session or a Short Message Service (SMS).

[0123] Furthermore, the AMF may use satellite coverage availability information to support satellite access or connectivity for UEs in discontinuous coverage, where the satellite coverage availability information may be provided by O&M (Operation and Maintenance) or AF, and the satellite coverage availability information provided to the AMF describes when and where satellite coverage is expected to be available in an area. Furthermore, the satellite coverage availability information is not UE specific, but may be applied by the AMF to any UE in the affected area.

[0124] Here, in particular, low Earth orbit (LEO) and medium Earth orbit (MEO) satellites may provide discontinuous coverage and may be able to provide NR satellite access to terrestrial UEs at specific times and locations, i.e., discontinuously.

[0125] The satellite coverage availability information may include information indicating the time and location at which each satellite is expected to be able to provide NR satellite access to terrestrial UEs. Alternatively, the satellite coverage availability information may include information indicating the time and location at which each satellite is able to provide NR satellite access to terrestrial UEs, and the time and location at which each satellite is unable to provide NR satellite access to terrestrial UEs. It goes without saying that terrestrial UEs do not only refer to UEs that are strictly adjacent to the Earth's surface, but also include UEs that are not adjacent to the Earth's surface.

[0126] A mobility pattern is a concept that the AMF can use to characterize and optimize the mobility of a UE, and is also referred to as a UE mobility pattern. Here, the AMF may determine or update the mobility pattern of a UE based on UE subscription information, UE mobility statistics, network local policies, and UE assistance information, or any combination thereof. Here, the statistics of the UE mobility may be a past or predicted trajectory of the UE's movement. Also, if an NWDAF is deployed in the network, the statistics of the UE mobility may be an analysis (i.e., statistics or predictions) provided by the NWDAF.

[0127] Furthermore, the mobility pattern may be capable of being used by the AMF for optimization of the mobility support provided to the UE, such as, for example, allocation of a registration area.

[0128] In addition, the UE may be able to receive the mobility pattern determined by the AMF via the C-Plane or U-plane using various procedures, and may store the received mobility pattern.

[0129] In addition, the mobility pattern in this specification may be a conventional mobility pattern or a mobility pattern that takes into account the discontinuous coverage provided by the NR satellite access. In addition to the AMF, the UE may determine or update the mobility pattern.

[0130] The UE out-of-coverage period may be a period or time during which a UE is expected or assumed to be out of coverage (i.e., out of coverage) in NR satellite access providing discontinuous coverage. Here, the UE out-of-coverage period may be determined based on satellite coverage information and UE mobility patterns. Furthermore, the UE out-of-coverage period may be determined by the UE, or by the network or each network device. More specifically, for example, the UE may transmit the determined UE out-of-coverage period to the network, and the network or each network device may receive and store it. Also, for example, the network or any network device (e.g., AMF) may transmit the determined UE out-of-coverage period to the UE, network, or other network device, and the UE, network, or other network device may receive and store it. The UE out-of-coverage period is also referred to as a period during which the UE is out of coverage.

[0131] Here, the UE out-of-service period may be a period during which the UE is out of service, or a timer or timer value corresponding to the period during which the UE is out of service. Also, the UE out-of-service period may be an unreachability period, or a period indicated by the unreachability period or a corresponding timer or timer value. Furthermore, for example, the unreachability period may be a timer or timer value included in the "Unreachability period duration IE". Also, if the UE out-of-service period is a timer or timer value corresponding to the period during which the UE is out of service, the timer may be started when the UE transitions to an out-of-service state or an idle state (idle mode).

[0132] Also, for example, the UE may use an existing timer or a timer value corresponding to the UE out-of-coverage period, or may use a new timer different from the existing timer. More specifically, for example, the UE out-of-coverage period may be a timer or a timer value included in a "UE out-of-coverage period duration Information Element (IE)". Furthermore, the "UE out-of-coverage period duration IE" may be an existing timer or a timer value (for example, GPRS Timer 3 IE), or may be information indicating a new timer or a new timer value for 5GSAT communication. Note that, for example, when the UE out-of-coverage period is an unreachability period, a timer or a timer value indicating a period corresponding to the UE out-of-coverage period may be included in the "UE out-of-coverage period duration IE" and / or the "Unreachability period duration IE".

[0133] In addition, when the UE determines the UE out-of-service period, the determination may be based on satellite coverage availability information and a UE mobility pattern provided by the network, or on satellite coverage availability information and a UE mobility pattern held by the UE. For example, the UE may determine the UE out-of-service period based on satellite coverage availability information provided by the network and a UE mobility pattern provided by the network. Alternatively, for example, the UE may determine the UE out-of-service period based on satellite coverage availability information provided by the network and a UE mobility pattern held by the UE. Alternatively, for example, the UE may determine the UE out-of-service period based on satellite coverage availability information held by the UE and a UE mobility pattern held by the UE, but is not limited thereto.

[0134] Furthermore, for example, if the UE can determine a "UE out of coverage period" and the UE decides to remain out of service during the period indicated by the UE out of coverage period, it may perform a Mobility Registration Update procedure before the start of the Unreachability period. Furthermore, the UE may request a MICO (Mobile Initiated Connection Only) mode parameter, eDRX (extended DRX) parameter in CM-IDLE, or other NAS timer using a related procedure that takes into account the UE out of coverage period, and in this case, not include the UE out of coverage period if the UE requests to use MICO mode or eDRX. Alternatively, the UE may inform the network of the UE out of coverage period when it is about to leave the satellite coverage, and further perform a Mobility Registration Update procedure when it returns to coverage via any access type.

[0135] Overload control in discontinuous coverage provided by NR satellite access is a control and / or function for avoiding excessive signal load on the network when a large number of UEs return from outside the range of the NR satellite access to the range again. Furthermore, overload control in discontinuous coverage may be a control using a maximum waiting time. Also, the maximum waiting time may be a time determined by the AMF until the UE, which has returned to the range of the satellite access, is allowed to start NAS signaling with the network. In other words, for overload control, the AMF may determine a maximum waiting time until the UE is allowed to start NAS signaling with the network. Here, the maximum waiting time may be referred to as, for example, Disco wait range.

[0136] More specifically, in the overload control in discontinuous coverage using the maximum latency, the AMF first determines the maximum latency based on the network configuration, or the priority user, or the priority service, and transmits the maximum latency to the UE during the registration procedure or the UE configuration update procedure. Then, if the UE that receives the maximum latency has already received the maximum latency of the same RAT type and PLMN, the UE may replace the stored maximum latency. Furthermore, A UE that receives the maximum waiting time may select a random value that caps the maximum waiting time and determine a discontinuous coverage wait timer value.

[0137] Wherein, the discontinuous coverage waiting timer may be a timer that restricts the UE from connecting to the network via the satellite access, and further, the UE may execute the discontinuous coverage waiting timer based on a discontinuous coverage waiting timer value determined by the UE.

[0138] In addition, when the UE returns to the coverage area of ​​the NR satellite access from outside the coverage area with the same RAT (Radio Access Technology) type and PLMN, the UE starts a discontinuous coverage wait timer. Note that the UE that is running the discontinuous coverage wait timer must not start NAS signaling for the RAT type and PLMN. Through the above procedures and processing, multiple UEs that return to the coverage area each run the discontinuous coverage wait timer with a different random value, which makes it possible to control and reduce excessive signal load on the network.

[0139] Here, the maximum waiting time determined by the AMF may be included in an MM message transmitted and received during an MM (Mobility Management) procedure and transmitted to the UE. More specifically, for example, the MM procedure in which the AMF transmits the maximum waiting time to the UE may be a registration procedure or a UE configuration update procedure. Furthermore, for example, the MM message in which the AMF includes the maximum waiting time may be, for example, a registration acceptance message, a registration rejection message, or a configuration update command message. In other words, the maximum waiting time may be included in an MM message and transmitted from the AMF to the UE in an MM procedure such as a registration procedure or a UE configuration update procedure.

[0140] Furthermore, if the UE receives a paging message and there is an emergency service pending, or if the UE enters a TAI outside the registration area, the UE may stop the discontinuous coverage waiting time timer and initiate NAS signaling.

[0141] Also, the UE or the network or each device using the function related to the maximum latency may support the maximum latency. In other words, if the UE or the network or each device supports the maximum latency, for example, the AMF may have the capability to determine the maximum latency, or the UE may have the capability to select or determine the waiting timer for discontinuous coverage from the maximum latency received. In other words, the UE or the network or each device supporting communication via NR satellite access may support the maximum latency as a function for discontinuous coverage.

[0142] The back-off timer in discontinuous coverage provided by NR satellite access may be a timer provided by the AMF to the UE to prevent the initiation of Mobile Originated (MO) data transmission or signaling before the UE is about to go out of coverage.

[0143] In other words, the back-off timer in the discontinuous satellite coverage provided to the UE by the AMF may be a back-off timer that is started to end when the UE is in range (i.e., the coverage period of the NR satellite access) based on the satellite coverage availability information, and the UE may be prohibited from starting MO data transmission or signaling while the timer is running. Also, if the UE is still in the same satellite communication area after the timer expires, it may start MO data transmission or signaling, or if it finds a cell of another TN or NTN, it may stop the timer and register through a new access network and transmit MO data.

[0144] In addition, the AMF that provided the back-off timer to the UE may initiate an AN release procedure. In addition, the back-off timer in the discontinuous satellite coverage may use an existing timer or may be defined and used as a new timer.

[0145] The timer offset information in NR satellite access providing discontinuous coverage may be information indicating a timer offset value that corresponds to a timer executed while the UE is in range or a timer executed while the UE is out of range, taking into account the coverage recognized by the UE or the network from the satellite coverage availability information and a physical coverage gap due to the movement of the UE or the orbit of the satellite, etc. In this specification, the timer offset information in NR satellite access providing discontinuous coverage is also referred to as timer offset information indicating a time or period, or timer offset information, or timer offset, or offset information, or simply offset, etc.

[0146] Here, the offset information may be information or parameters preconfigured in the UE, determined by the UE, or determined by the network. More specifically, for example, the offset information may be information or parameters preconfigured in the UE. Or, the offset information may be information or parameters determined by the network, transmitted to the UE, and stored by the received UE. Or, the offset information may be information or parameters determined by the UE, transmitted to the network, and stored by the network or each device.

[0147] The timer offset information may be associated with one or more timers. That is, the timer offset information may be associated with the same number of offset information for one or more timers, or one offset information may be associated with one or more timers. Here, the timer to which the offset information is associated may be information associated with a period or timer indicating a time during which the UE corresponding to the satellite coverage availability information is in range, and / or information associated with a UE out-of-range period. More specifically, for example, the offset information may be an offset value of a timer used to specify a time to advance or delay the start or end of a timer corresponding to a period during which the UE is out of range or in range, taking into account discontinuous coverage in NR satellite access. In other words, for example, when the offset information is information indicating that the expiration time of a timer corresponding to a UE out-of-range period is extended, the UE may start the timer based on a value obtained by adding the value of the offset information to the timer value.

[0148] [3.2. Description of Identification Information in Each Embodiment] The first identification information in the present invention may be identification information indicating that when the UE returns from outside the satellite access range to within the range, the network requests the UE to start a registration procedure via satellite access. In other words, the first identification information may be identification information indicating that the network requests or is requesting the UE to start a registration procedure via satellite access when the UE returns from outside the satellite access range to within the range. Here, the registration procedure that the UE starts with the network via satellite access when the UE returns from outside the satellite access range to within the range may be a registration update procedure.

[0149] The first identification information may be associated with or related to one or more of the RAT type, and / or PLMN, and / or access type, and / or area, and / or type of core network or system. Here, the area to which the first identification information is associated may be, for example, a registration area or a tracking area. The core network / system to which the first identification information is associated may be, for example, 5GCN (5G Core Network) or 5GS (5G System), or EPC (Evolved Packet Core) or EPS (Evolved Packet System). Here, the first identification information may be identification information including information on association or association with one or more of the RAT type, and / or PLMN, and / or access type, and / or area, and / or type of core network or system. Alternatively, the UE may store association or association with one or more of the RAT type, and / or PLMN, and / or access type, and / or area, and / or type of core network or system together with the first identification information.

[0150] Alternatively, the first identification information may be an identification information including information indicating that the first identification information is common to any one of the RAT type, and / or the PLMN, and / or the access type, and / or the area, and / or the type of the core network or system. More specifically, for example, the first identification information may be an identification information including information indicating that the first identification information is common to a specific PLMN. In other words, for example, when the first identification information includes information indicating that the first identification information is common to a specific PLMN, the UE may perform a behavior based on the first identification information in the PLMN regardless of the RAT type, and / or the access type, and / or the area, and / or the type of the core network or system.

[0151] Here, the UE may receive the first identification information via a satellite access or a terrestrial access, and based on the information included in the first identification information that corresponds or corresponds to a RAT type, and / or a PLMN, and / or an access type, and / or an area, and / or a type of core network or system, or information indicating common to any of them, recognize that the first identification information is valid in the corresponding access and / or network, and perform a behavior based on the identification information.

[0152] Also, the first identity may be included in any message in the registration procedure or the network initiated mobility management procedure and transmitted to the UE from the network via satellite access. More specifically, the first identity may be included in a registration accept message, and / or a configuration update command message, and / or a notification message, or a NAS transport message and transmitted from the network to the UE via satellite access. Here, the registration accept message including the first identity may be transmitted during the initial registration procedure or the registration update procedure.

[0153] From the above, the first identification information is, for example, an identification information indicating that when a UE returns to a satellite access range from outside the satellite access range, the UE requests the network to start a registration update procedure via the satellite access, and further, the first identification information may be an identification information associated with a PLMN, and / or a RAT type, and / or an access type, and / or an area.

[0154] In addition, when the UE that has received the first identification information returns to the satellite access range after being out of the satellite access range in the discontinuous satellite coverage, the UE may execute the registration update procedure based on the first identification information after the expiration of the waiting timer for the discontinuous coverage. In other words, the UE that has received the first identification information from the network and returned to the satellite access range after being out of the satellite coverage range may not start or execute the registration update procedure based on the first identification information while the waiting timer for the discontinuous coverage is running.

[0155] In addition, the UE that receives the first identification information may perform a registration update procedure every time the UE that receives the first identification information passes outside of satellite access range in discontinuous satellite coverage and returns to range.

[0156] Here, for example, when the UE returns from outside the satellite coverage to within the coverage, if any one or more of the RAT type, and / or PLMN, and / or access type, and / or area, and / or type of core network or system in the connection during the period in which the UE was in coverage immediately before are different, the UE may stop the behavior based on the first identification information. In other words, for example, if the connection is changed to a combination different from the RAT type, and / or PLMN, and / or access type, and / or area, and / or core network or system associated with the first identification information #1, the UE may not perform the registration update procedure. In other words, if the UE is in the coverage of the RAT type, and / or PLMN, and / or access type, and / or area, and / or core network or system associated with the first identification information #1, the UE may recognize that the first identification information is valid and activate it. In addition, if the device is within the range of a network different from the RAT type, and / or PLMN, and / or access type, and / or area, and / or core network or system associated with the first identification information #1, the first identification information may be recognized as invalid and may be invalidated.

[0157] More specifically, for example, if the network to which the UE is connected via satellite access is a 5G Core Network (5GC) or a 5G System (5GS) during the period in which the UE was in range before going out of range, and the network to which the UE is connected when it returns to range has switched to an Evolved Packet Core Network (EPC) or an Evolved Packet System (EPS), the registration update procedure based on the first identification information does not need to be started or executed. And / or, for example, if the network to which the UE is connected via satellite access has switched RAT types before and after the UE goes out of range, the registration update procedure based on the first identification information does not need to be started or executed. And / or, for example, if the network to which the UE is connected via satellite access has switched PLMNs before and after the UE goes out of range, the registration update procedure based on the first identification information does not need to be started or executed. And / or, for example, when the access type of the network to which the UE is connected via satellite access is changed before and after the UE goes out of service, or when the PLMN is changed before and after the UE goes out of service, the registration update procedure based on the first identification information may not be started or executed. And / or, for example, when the area of ​​the network to which the UE is connected via satellite access is changed before and after the UE goes out of service, the registration update procedure based on the first identification information may not be started or executed. Furthermore, for example, when the UE returns from outside the satellite coverage to within the coverage, if the RAT type, and / or PLMN, and / or access type, and / or area, and / or core network or system are associated with the first identification information #1, the registration update procedure may be executed based on the first identification information #1. In other words, the UE that has received the first identification information may execute the registration update procedure every time the UE returns from outside the satellite coverage to within the coverage.

[0158] Furthermore, the behavior based on the first identification information may be activated when the UE receives the first identification information, goes out of satellite access range, and returns to satellite access range. That is, the UE that receives the first identification information may be activated from the time when the UE goes out of satellite access range and returns to satellite access range due to discontinuous satellite coverage, and a registration update procedure may be performed. And / or, if the first identification information includes and indicates conditions such as the timing, number of times, and / or period for activating the first identification information by the network, the UE may recognize the first identification information as valid and perform the behavior based on the first identification information according to the information. And / or, if the UE transitions to a non-registered state, or if the conditions included in the first identification information by the network, such as the timing, number of times, and / or period for activating the first identification information, end or expire, the UE may recognize the first identification information as invalidated.

[0159] Details of the behavior of the UE and the network based on the first identity are also described in Chapter 5. In this specification, the UE behavior based on the first identity (also simply referred to as the behavior based on the first identity) may be the behavior of the UE that receives the first identity from the network, and as already described, may be the behavior of the UE that returns to the satellite access range after being out of the satellite access range, and performs the registration update procedure or the registration procedure through the satellite access based on the first identity. Furthermore, the behavior based on the first identity in this specification may be configured by a combination of multiple behaviors including the UE receiving the first identity from the network, and / or the UE returning to the satellite access range after being out of the satellite access range, and / or the UE activating the first identity, and / or the UE performing the registration update procedure or the registration procedure through the satellite access based on the first identity. In this specification, the behavior based on the first identity may indicate, for example, that the combination of these behaviors is performed once. Furthermore, the first identity-based behavior in this specification may be executed one or more times by the UE, for example, taking into consideration a condition of the first identity-based behavior indicated by the network as information further included in the first identity or transmitted together with the first identity in association with the first identity. In this specification, in this case, the first identity-based behavior may be executed one or more times, or one or more combinations of each behavior constituting the first identity-based behavior multiple times may be executed among the first identity-based behavior.

[0160] The second identification information in the present invention may be identification information indicating that the network requests the UE not to perform a registration update procedure via the satellite access when the UE transitions or returns from outside the satellite access coverage to within the coverage, and may be identification information further transmitted from the network when the UE has received the first identification information from the network.

[0161] The second identification information may be associated with or related to one or more of the RAT type, and / or PLMN, and / or access type, and / or area, and / or type of core network or system. Here, the area to which the second identification information is associated may be, for example, a registration area or a tracking area. The core network / system to which the first identification information is associated may be, for example, 5GCN (5G Core Network) or 5GS (5G System), or EPC (Evolved Packet Core) or EPS (Evolved Packet System). Here, the second identification information may be identification information including information on association or association with one or more of the RAT type, and / or PLMN, and / or access type, and / or area, and / or type of core network or system. Alternatively, the UE may store association or association with one or more of the RAT type, and / or PLMN, and / or access type, and / or area, and / or type of core network or system together with the second identification information.

[0162] Alternatively, the second identity may be identity including information indicating that the second identity is common to any one of the RAT type, and / or the PLMN, and / or the access type, and / or the area, and / or the type of the core network or system. More specifically, for example, the second identity may be identity including information indicating that the second identity is common to a specific PLMN. In other words, for example, when the second identity includes information indicating that the second identity is common to a specific PLMN, the UE may perform a behavior based on the second identity in the PLMN regardless of the RAT type, and / or the access type, and / or the area, and / or the type of the core network or system.

[0163] Here, the UE may receive the second identity via a satellite access or a terrestrial access, and based on the information included in the second identity that corresponds or corresponds to the RAT type, and / or the PLMN, and / or the access type, and / or the area, and / or the type of core network or system, or information indicating common to any of them, recognize that the second identity is valid in the corresponding access and / or network, and may perform a behavior based on the identity.

[0164] Also, the second identity may be included in any message in the registration procedure or the network initiated mobility management procedure and transmitted to the UE from the network via satellite access. More specifically, the second identity may be included in a registration accept message, and / or a configuration update command message, and / or a notification message, or a NAS transport message and transmitted from the network to the UE via satellite access. Here, the registration accept message including the second identity may be transmitted during the initial registration procedure or the registration update procedure.

[0165] More specifically, for example, the UE may not need to perform a registration update procedure every time the UE returns from outside the satellite access range based on the reception of the first identification after receiving the second identification. In other words, the second identification may be an identification for deactivating the UE's operation based on the first identification that the UE has already received. Note that the second identification for deactivating the first identification needs to be associated with any one or more combinations of the same RAT type, and / or PLMN, and / or access type, and / or area, and / or type of core network or system as the first identification.

[0166] Further details of the UE and network behavior based on the second identity are provided in Chapter 5.

[0167] The third identification information in the present invention is identification information indicating that the network to which the UE is registered and / or connected via satellite access requests the UE to start a registration update procedure. Here, the UE that receives the third identification information may, for example, immediately execute the registration update procedure based on the third identification information. Alternatively, the UE may execute the registration update procedure based on the third identification information after the UE finishes the procedure that is being executed when the UE receives the third identification information. Alternatively, the UE may execute the registration update procedure at a timing based on information further indicated by the network together with the third identification information.

[0168] The third identification information may be associated with or related to one or more of a RAT type, and / or a PLMN, and / or an access type, and / or an area, and / or a type of a core network or system. Here, the area to which the third identification information is associated may be, for example, a registration area or a tracking area. The core network / system to which the third identification information is associated may be, for example, a 5G Core Network (5GCN), a 5G System (5GS), an Evolved Packet Core (EPC), or an Evolved Packet System (EPS).

[0169] Here, the third identity may be identity including information of association or mapping with one or more of the RAT type, and / or PLMN, and / or access type, and / or area, and / or type of core network or system, or the UE may store association or mapping with one or more of the RAT type, and / or PLMN, and / or access type, and / or area, and / or type of core network or system together with the third identity.

[0170] Alternatively, the third identity may be an identity including information indicating that the third identity is common to any one of the RAT type, and / or the PLMN, and / or the access type, and / or the area, and / or the type of the core network or system. More specifically, for example, the third identity may be an identity including information indicating that the third identity is common to a specific PLMN. In other words, for example, when the third identity includes information indicating that the third identity is common to a specific PLMN, the UE may perform a behavior based on the third identity in the PLMN regardless of the RAT type, and / or the access type, and / or the area, and / or the type of the core network or system.

[0171] Here, the UE may receive the third identity via a satellite access or a terrestrial access, and based on the information included in the third identity that corresponds or corresponds to the RAT type, and / or the PLMN, and / or the access type, and / or the area, and / or the type of core network or system, or information indicating common to any of them, recognize that the third identity is valid in the corresponding access and / or network, and may perform a behavior based on the identity.

[0172] In other words, for example, a UE that has received the third identity may initiate a registration update procedure with a network that has transmitted the third identity via a satellite access through which the third identity has been received. More specifically, for example, the UE may perform a registration procedure via a connection of one or more combinations of a RAT type, and / or a PLMN, and / or an access type, and / or an area, and / or a type of a core network or system through which the third identity has been received. Conversely, for example, the UE may not perform a registration update procedure based on the third identity via a connection of one or more combinations of a RAT type, and / or a PLMN, and / or an access type, and / or an area, and / or a type of a core network or system through which the third identity has been received.

[0173] Also, the third identity may be included in any message in the registration procedure or the network-initiated mobility management procedure and transmitted to the UE from the network via satellite access. More specifically, the third identity may be included in a registration accept message, and / or a configuration update command message, and / or a notification message, or a NAS transport message and transmitted from the network to the UE via satellite access. Here, the registration accept message including the third identity may be transmitted from the network to the UE during the initial registration procedure or the registration update procedure.

[0174] In addition, when or during the period when the UE is within the range of satellite access used to connect to the network, the network may at any time transmit a message including a third identification information to the UE, or initiate or execute a procedure for transmitting such a message.

[0175] Furthermore, the third identification information may be identification information that is transmitted and received independently of the transmission and reception of the first and / or second identification information. In other words, for example, the third identification information may be identification information that the network can transmit to the UE at any timing, regardless of whether the first and / or second identification information has been transmitted from the network to the UE.

[0176] Details of the UE and network behavior based on one or a combination of the above first to third identification information are not limited to those described in this chapter, but are also described in Chapter 5.

[0177] [4. Description of procedures used in each embodiment] Next, procedures used in each embodiment will be described, which may include a registration procedure and a network-initiated mobility management procedure.

[0178] In each embodiment, as shown in FIG. 2, the case where the HSS and UDM, the PCF and PCRF, the SMF and PGW-C, and the UPF and PGW-U are configured as the same device (i.e., the same physical hardware, or the same logical hardware, or the same software) will be described as an example. However, the contents described in this embodiment are also applicable to the case where these are configured as different devices (i.e., different physical hardware, or different logical hardware, or different software). For example, data may be transmitted and received directly between these, 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.

[0179] The details of each procedure are explained below.

[0180] [4.1. Registration Procedure] First, the registration procedure will be described with reference to FIG. 6. The registration procedure is a procedure in 5GS. In the following of this section, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering to the access network_B and / or the core network_B and / or the DN. If the UE is not registered to the network, it can execute this procedure at any time, such as when the power is turned on. In other words, if the UE is in a deregistered state (RM-DEREGISTERED state), it can start this procedure at any time. In addition, each device (especially the UE and the AMF) can transition to a registered state (RM-REGISTERED state) based on the completion of the registration procedure.

[0181] The registration procedure may also be an initial registration initiated by the UE, the registration procedure may also be a mobility and periodic registration, or the registration procedure may also be an MM procedure.

[0182] Furthermore, the registration procedure may 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 certain parameters related to the UE in the network.

[0183] This procedure may also be a procedure for registration by the UE via NR satellite access. Furthermore, the PDU session established after completion of this procedure may be a PDU session via the satellite NG-RAN or NR satellite access. In other words, for example, a PDU session established by a PDU session establishment procedure performed after completion of the registration procedure via NR satellite access may be a PDU session via NR satellite access. Or, for example, a PDU session via NR satellite access may be established based on the completion of this procedure.

[0184] The UE may initiate a registration procedure when mobility across TAs is performed. More specifically, the UE may initiate a mobility registration update procedure for re-registration when the UE moves to a TA different from the TA indicated in the TA list held by the UE. Furthermore, the UE may initiate this procedure when a running timer expires. Furthermore, the UE may initiate a registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may initiate a registration procedure when a change occurs in capability information and / or preferences regarding the establishment of a PDU session of the UE. Furthermore, the UE may initiate a registration procedure periodically. Furthermore, the UE may initiate a registration procedure based on the completion of a UE configuration update procedure. It should be noted that the UE may execute the registration procedure at any timing, not limited to the above.

[0185] Furthermore, even if the UE is in a registered state, the UE may initiate a registration procedure periodically. In other words, the UE may initiate a registration procedure based on the expiration of a timer. In other words, the registration procedure performed periodically may be a Periodic Registration Update procedure.

[0186] In addition, the registration procedure performed based on the mobility of the UE and the registration procedure performed periodically may be expressed as a registration procedure for mobility and registration update. In other words, the registration procedure for mobility and registration update may be a registration procedure performed based on the mobility of the UE, or may be a registration procedure performed periodically. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed based on a setting update of the UE. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed to establish a communication path for transmitting and receiving user data. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed based on a request from the network. Furthermore, in other words, the registration procedure for mobility and registration update may be a registration procedure other than the initial registration procedure. Hereinafter, the registration procedure for mobility and registration update may be expressed as this procedure. Furthermore, in this specification, the registration update procedure initiated or executed by the UE may be a registration procedure, in other words, for example, the registration update procedure in this specification may be read as a registration procedure.

[0187] Next, each step of the registration procedure will be described. Note that the registration procedure described below may be an initial registration procedure, or a registration procedure for mobility and registration renewal.

[0188] First, the UE starts the registration procedure by transmitting a registration request message to the AMF (S600) (S602) (S604). Specifically, the UE transmits an RRC message including a registration request message to the 5G AN (or gNB) (S600). The registration request message is a NAS message. The RRC message may be a control message transmitted and received between the UE and the 5G AN (or gNB). The NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.

[0189] Here, the UE may transmit identification information indicating that the UE supports the functions for communication via NR satellite access in the registration request message. Here, the identification information indicating that the UE supports the functions for communication via NR satellite access may be information included in a 5GMM capability information element indicating that the UE supports the functions for communication via NR satellite access.

[0190] The UE may also initiate a PDU session establishment procedure during the registration procedure by sending a SM message in or together with a registration request message, where the SM message may be a PDU session establishment request message.

[0191] When the 5G AN (or gNB) receives an RRC message including a registration request message, it selects an AMF to which the registration request message is to be transferred (S602). The 5G AN (or gNB) can select an AMF based on information included in the registration request message and / or the RRC message. The 5G AN (or gNB) extracts the registration request message from the received RRC message and transfers the registration request message to the selected AMF (S604).

[0192] When the AMF receives the registration request message, the AMF can execute a first condition determination. The first condition determination is for determining whether the network (or the AMF) accepts the request of the UE. When the first condition determination is true, the AMF starts the procedure of (A) in Fig. 6, whereas when the first condition determination is false, the AMF starts the procedure of (B) in Fig. 6.

[0193] The first condition determination may be performed based on the reception of a registration request message, and / or each identification information included in the registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or a context held by the AMF. For example, if the network permits the request of the UE, the first condition determination may be true, and if the network does not permit the request of the UE, the first condition determination may be false. In addition, if the network to which the UE is registered and / or a device in the network supports a function requested by the UE, the first condition determination may be true, and if the network does not support the function requested by the UE, the first condition determination may be false. Furthermore, if the identification information to be transmitted and received is permitted, the first condition determination may be true, and if the identification information to be transmitted and received is not permitted, the first condition determination may be false. In addition, the conditions for determining whether the first condition determination is true or false may not be limited to the above-mentioned conditions.

[0194] First, a case where the first condition determination is true will be described. In the procedure of (A) in Fig. 6, the AMF can first execute the fourth condition determination. The fourth condition determination is for determining whether the AMF transmits and receives an SM message between the AMF and the SMF.

[0195] In addition, the fourth condition determination may be performed based on whether the AMF has received an SM message. In addition, the fourth condition determination may be performed based on whether the registration request message includes an SM message. For example, if the AMF has received an SM message and / or if the registration request message includes an SM message, the fourth condition determination may be true, and if the AMF has not received an SM message and / or if the registration request message does not include an SM message, the fourth condition determination may be false. In addition, the conditions that determine the truth or falsehood of the fourth condition determination may not be limited to the above-mentioned conditions.

[0196] Next, the AMF transmits a registration accept message to the UE via the 5G AN (or gNB) as a response message to the registration request message based on the reception of the registration request message and / or the completion of the transmission and reception of the SM message with the SMF (S608). For example, when the fourth condition determination is false, the AMF may transmit a registration accept message based on the reception of the registration request message from the UE. Also, when the fourth condition determination is true, the AMF may transmit a registration accept message based on the completion of the transmission and reception of the SM message with the SMF. Note that the registration accept message is a NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) in an RRC message.

[0197] The AMF may include the first and / or second identification information in the registration accept message and transmit it. More specifically, for example, when the first and / or second identification information are associated with the same combination of any one or more of RAT type, and / or PLMN, and / or access type, and / or area, and / or core network or system type, the AMF may include one of the first or second identification information in the registration accept message and receive it at the UE. More specifically, for example, the AMF may not include the first identification information associated with the combination of {RAT type #1, PLMN #1} and the second identification information associated with the combination of {RAT type #1, PLMN #1} in the same registration accept message.

[0198] Conversely, for example, when the first and / or second identification information is associated with one or more different combinations of RAT type, and / or PLMN, and / or access type, and / or area, and / or core network or system type, the AMF may include the first or second identification information in the same registration accept message and transmit it to the UE. More specifically, for example, the AMF may include the first identification information associated with the combination of {RAT type #1, PLMN #2} and the first identification information associated with the combination of {RAT type #2, PLMN #1} in the same registration accept message and transmit it to the UE.

[0199] In addition, the AMF may indicate the contents of the first and / or second identification information to the UE by transmitting the first and / or second identification information. Furthermore, the UE that receives the first and / or second identification information may store the received identification information, or may behave based on the content information of the received identification information. Detailed behavior of the UE that receives the first and / or second identification information is described in Chapter 5.

[0200] Furthermore, when multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request for use of the function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0201] Furthermore, the AMF may select and determine whether to include the first and / or second identification information in the registration acceptance message based on each identification information received by the AMF from the UE or each device, 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.

[0202] Furthermore, the AMF may include and send the SM message in a registration accept message, or may send the SM message together with the registration accept message. However, this sending method may be executed when the SM message is included in the registration request message and the fourth condition determination is true. Also, this sending method may be executed when the SM message is included together with the registration request message and the fourth condition determination is true. By performing such a sending method, the AMF can indicate that the procedure for SM has been accepted in the registration procedure. Here, the SM message may be a PDU session establishment request message or a PDU session establishment acceptance message.

[0203] The AMF may also indicate that the UE's request has been accepted by sending a registration acceptance message based on the received identification information, and / or subscription information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0204] Furthermore, the AMF may include information indicating that some of the UE's requests have been rejected in the registration acceptance message and transmit it, or may indicate the reason why some of the UE's requests have been rejected by transmitting information indicating that some of the UE's requests have been rejected. Furthermore, the UE may recognize the reason why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. In addition, the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0205] The UE receives a registration acceptance message from the AMF via the 5G AN (gNB) (S608). By receiving the registration acceptance message, the UE can recognize that the UE's request by the registration request message has been accepted and the contents of various identification information included in the registration acceptance message.

[0206] Here, the UE that receives the registration accept message may recognize and store that the network has some or all of the 5G SAT communication capabilities based on the received one or more second identification information.

[0207] Furthermore, the UE may transmit a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S610). Here, the registration completion message is a NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) in an RRC message.

[0208] The AMF receives a registration completion message via the 5G AN (gNB) (S610). In addition, each device completes the procedure of (A) in FIG. 6 based on the transmission and reception of the registration acceptance message and / or the registration completion message.

[0209] Next, a case where the first condition determination is false will be described. In the procedure of (B) of Fig. 6, the AMF transmits a registration reject message to the UE via the 5G AN (gNB) as a response message to the registration request message (S612). Here, the registration reject message is a NAS message transmitted and received on the N1 interface, but is included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

[0210] Here, the AMF may include one or more second identification information in the registration rejection message and transmit it. In addition, by transmitting these identification information, the AMF may indicate to the UE that the network does not have some or all of the 5GSAT communication capabilities. Furthermore, the AMF may include a rejection reason value indicating that the network does not have some or all of the 5GSAT communication capabilities, or a rejection reason value corresponding to a 5GSAT communication function that the network does not support.

[0211] Furthermore, when multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request for use of the function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0212] Furthermore, the AMF may select and determine whether to include the second identification information in the registration rejection message based on each identification information received by the AMF, 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.

[0213] Furthermore, the AMF may indicate that the UE's request by the registration request message has been rejected by sending a registration rejection message. Furthermore, the AMF may include information indicating the reason for the rejection in the registration rejection message and transmit it, or may indicate the reason for the rejection by sending the reason for the rejection. Furthermore, the UE may recognize the reason for the rejection of the UE's request by receiving information indicating the reason for the rejection of the UE's request. In addition, the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0214] The UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S612). By receiving the registration rejection message, the UE can recognize that the UE's request by the registration request message has been rejected and the contents of various identification information included in the registration rejection message. In addition, if the UE does not receive a registration rejection message even after a predetermined period has elapsed after transmitting the registration request message, the UE may recognize that the UE's request has been rejected. Each device completes the procedure (B) in this procedure based on the transmission and reception of the registration rejection message.

[0215] Here, the UE that receives the registration rejection message may recognize and store, based on the received second identification information, that the network does not have some or all of the 5G SAT communication capability.

[0216] The procedure in FIG. 6(B) may be started when the procedure in FIG. 6(A) is stopped.

[0217] Each device completes the registration procedure based on the completion of the procedure of (A) or (B) in Fig. 6. Each device may transition to a state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure of (A) in Fig. 6, and may maintain a state in which the UE is not registered in the network (RM_DEREGISTERED state) or transition to a state in which the UE is not registered in the network based on the completion of the procedure of (B) in Fig. 6. Furthermore, the transition of each device to each state may be performed based on the completion of the registration procedure or the establishment of a PDU session.

[0218] The UE may also complete the registration procedure based on receiving the registration accept message or the registration reject message.

[0219] Furthermore, each device may perform processing based on the information transmitted and received in the registration procedure based on the completion of the registration procedure. For example, when transmitting and receiving information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's request has been rejected, or may perform the registration procedure for the core network_B or another cell.

[0220] Further, the UE may store the identification information received with the registration accept message and / or the registration reject message and may recognize the network's decision upon completion of the registration procedure.

[0221] The UE may recognize the content of the above identification information by receiving a registration acceptance message or a registration rejection message.

[0222] In addition, the behavior to be performed when each piece of identification information is received may be executed based on the received identification information.

[0223] [4.2. Network-initiated mobility management procedures] Next, the network-initiated mobility management procedure will be described with reference to FIG. 7. In the following, in this section, the network-initiated mobility management procedure will also be referred to as this procedure. Here, the network-initiated mobility management procedure will also be referred to as the network-initiated mobility management procedure, the NW-init MM procedure, etc.

[0224] The network-initiated mobility management procedure described in this chapter may be a generic UE configuration update procedure (also simply referred to as a UE configuration update procedure), a notification procedure, a network-initiated NAS transport procedure, or a paging procedure. Here, the paging procedure may be a procedure for transferring paging information to a UE in RRC_IDLE or RRC_INACTIVE. In other words, it may be a procedure executed when the UE is in RRC_IDLE or RRC_INACTIVE.

[0225] This procedure may be started by the AMF sending a message to the UE (S700) based on the decision of the AMF or the core network device. Here, the message that the AMF sends to the UE via the NR satellite access may be a NAS message or a paging message. Note that if this procedure is started based on the decision of a core network device other than the AMF or the sending of a message, the message sent by the core network device may be sent to the UE via the AMF and the NR satellite access.

[0226] Here, the message that the AMF sends to the UE (S700) may be, but is not limited to, a configuration update command message, and / or a notification message, and / or a DL NAS TRANSPORT message, and / or a paging message.

[0227] Furthermore, the AMF may include one or more of the first to third identification information in the message sent in S700 and send it to the UE.

[0228] Next, the UE that receives the message sent by the AMF (S700) may or may not send a response message to the received message to the AMF via NR satellite access (S702).

[0229] Here, the message sent by the UE to the AMF (S702) may be a configuration update complete message, or a notification response message, or a service request message, or a registration request message. Furthermore, the message sent by the UE in S702 is not limited to these, and may be a response message corresponding to a message received by the UE, or a response message based on identification information included in the message received by the UE.

[0230] In addition, this procedure may be completed based on the UE receiving a message sent by the AMF via the NR satellite access (S700), and / or the UE transmitting a response message to the AMF via the NR satellite access based on the UE's reception of the message at S700 (S702).

[0231] In addition, this procedure may be a procedure used by the network to transmit one or more of the first to third identities to the UE connecting via satellite access. Furthermore, this procedure may be a procedure executed when the AMF or the core network decides to transmit one or more of the first to third identities to the UE connecting via satellite access.

[0232] [5. Embodiment] Next, each embodiment of the present invention will be described. Note that each embodiment described in this chapter is based on the term definitions, various identification information, or each behavior described in Chapter 3, and each procedure or each behavior described in Chapter 4.

[0233] Also, each embodiment may be an embodiment that is started in a state where the UE connects to the network via NR satellite access and registration is completed. Also, in each embodiment or this specification, the registration update procedure that is started or executed by the UE may be a registration procedure. In other words, for example, the registration update procedure that is started or executed by the UE in each embodiment or this specification may be read as a registration procedure.

[0234] Furthermore, unless otherwise specified, the embodiments of the present invention are not limited to being implemented individually and independently as described in each section of this chapter, but may be implemented as a combination of one or more embodiments described in each section, or one or more embodiments described in each section may be implemented in any order.

[0235] Each embodiment will be described below.

[0236] [5.1. First embodiment] A first embodiment of the present invention will be described. Hereinafter, in this section, the first embodiment will also be referred to as the present embodiment.

[0237] The UE of the first embodiment first receives a message including first identification information from the network via satellite access.

[0238] More specifically, for example, the UE of the first embodiment receives a message including the first identity from the network via satellite access during a network-initiated mobility management procedure or a registration procedure. Here, the first identity may be included in a configuration update command message or a registration accept message and transmitted from the network to the UE via satellite access. More specifically, for example, the UE may receive a configuration update command message including the first identity or a registration accept message including the first identity from the AMF via satellite access.

[0239] In other words, the network or AMF may send a message including the first identity via satellite access during a network-initiated mobility management procedure or during a registration procedure. Here, the network or AMF may include the first identity in a configuration update command message or a registration accept message and send the message from the network to the UE. More specifically, for example, the network or AMF may send a configuration update command message including the first identity or a registration accept message including the first identity to the UE via satellite access.

[0240] Furthermore, the UE that receives the first identification information from the network via the satellite access may store the received first identification information, and when the UE receives new first identification information, the UE may replace the first identification information that has already been received and stored with the newly received first identification information.

[0241] Next, the UE having received the first identification information from the network may, when it falls out of satellite access range in the discontinuous satellite coverage and subsequently returns to range, initiate or perform a registration update procedure with the network via the satellite access based on the first identification information.

[0242] Wherein, the access and network from which the UE performs the registration update procedure may be the satellite access and network from which the UE received the first identity, and wherein the network from which the UE sent the message including the first identity may be the network in which the UE initially registered, and further, the first identity received by the UE may be associated with, for example, the PLMN of the source network and the RAT type of the satellite access.

[0243] Furthermore, when the UE returns to the satellite access range, if the waiting timer for discontinuous coverage is running, the UE does not need to perform the registration update procedure. In other words, for example, when the UE returns to the satellite access range, if the waiting timer for discontinuous coverage is running, the UE may wait for the timer to expire and perform the registration update procedure after the timer expires.

[0244] Here, the UE that has received the first identification information may repeat the execution of the registration update procedure each time it returns from outside the satellite access range to within range. For example, in a network in which the UE is registered, the UE may repeatedly execute the registration update procedure based on the first identification information and perform the operation until the UE transitions to an unregistered state.

[0245] Alternatively, the UE that has received the first identification information may repeat the execution of the registration update procedure each time it returns from outside the satellite access range to within the range, and if one or more of the RAT type, and / or PLMN, and / or access type, and / or area, and / or core network or system type are changed, the UE may stop executing the registration update procedure based on the first identification information and stopping the repetition of the operation.

[0246] Alternatively, a UE that has received the first identification information may repeat the execution of the registration update procedure each time it returns from outside the satellite access range to within range, and if any one or more of the RAT type, and / or PLMN, and / or access type, and / or area, and / or core network or system type is changed, the UE may stop executing the registration update procedure based on the first identification information and repeating the operation, but if the UE returns to range in the RAT type, and / or PLMN, and / or access type, and / or area, and / or core network or system type, and / or access and / or network associated with the first identification information, it may again execute the registration update procedure based on the first identification information and repeat the operation.

[0247] In addition, when the UE returns to satellite access coverage from outside the coverage area, the change in core network or system may be from 5GCN (5G Core Network) or 5GS (5G System) to EPC (Evolved Packet Core) or EPS (Evolved Packet System), and when the core network or system is changed, the UE does not need to initiate or execute a registration update procedure based on the first identification information.

[0248] Furthermore, the behavior based on the first identity may be enabled when the UE receives the first identity, goes out of satellite access range, and then returns to satellite access range. That is, the first identity may be enabled from the time when the UE that has received the first identity goes out of satellite access range and then returns to satellite access range, and a registration update procedure may be performed by the UE to the network via the satellite access based on the first device-specific information.

[0249] Furthermore, the network may further include information indicating a condition under which the UE executes a UE behavior based on the first identification information, or a request from the network, or a condition for enabling or disabling the first identification information, in the first identification information and transmit the information to the UE, or may transmit the information to the UE as information different from the first identification information. More specifically, the condition under which the UE executes a UE behavior based on the first information or the request from the network may be, for example, the timing to enable the first identification information, and / or the number of times the UE behavior based on the first identification information is executed when the first identification information is enabled, and / or the period during which the UE behavior based on the first identification information is executed when the first identification information is enabled, etc.

[0250] Here, the UE may recognize that the first identification information is valid or has been activated based on the information, and may execute a behavior based on the first identification information. More specifically, for example, if the network includes information on the timing to activate the first identification information in the first identification information, the UE may recognize the first identification information as valid at the timing indicated by the information, and execute the UE behavior based on the first identification information. And / or, for example, if information on the number of times the UE behavior based on the first identification information is executed is included, the UE may activate the first identification information until the behavior based on the first identification information is completed a number of times based on the information. And / or, for example, if information on the period during which the UE behavior based on the first identification information is executed is included, the UE may execute the behavior based on the first identification information that is activated during the period based on the information. More specifically, for example, when the network specifies "1" as information indicating the number of times the UE behavior based on the first identification information is executed, and specifies the timing when the UE goes out of service and then comes back into service as the timing when the first identification information is enabled, the UE may enable the first identification information based on the information, execute a registration update procedure once as the behavior based on the first identification information when the UE next comes back into service, and further invalidate the first identification information. Alternatively, for example, when the network specifies "1 or more" as information indicating the number of times the UE behavior based on the first identification information is executed, and specifies the timing when the UE goes out of service and then comes back into service as the timing when the first identification information is enabled, the UE may enable the first identification information based on the information when the UE next comes back into service, execute a registration update procedure as the behavior based on the first identification information each time the UE comes into service for the number of times indicated by the network, and further invalidate the first identification information after repeating the behavior based on the first identification information the number of times indicated by the network.

[0251] In addition, the information indicating the conditions for executing the UE's behavior based on the first identification information or requests from the network, etc., which is indicated by the network and included in the first identification information or sent to the UE together with the first identification information as information different from the first identification information, may be associated with one or more combinations of RAT type, and / or PLMN, and / or access type, and / or area, and / or core network or system type, and / or access and / or network, similar to the first identification information, and if the UE returns to the coverage area and is connected to a different combination, the first identification information may be invalidated.

[0252] From the above, the first embodiment may be, for example, an embodiment in which a UE receives a UE configuration update command message or a registration accept message as an MM message including a first identification from a network via a satellite access, and when the UE returns to the range of an NR satellite access from outside the range, in a discontinuous satellite coverage, the UE executes a registration update procedure to the network via the satellite access based on the first identification received by the UE. Here, the first identification is identification indicating that the UE requests the network to start a registration update procedure via the satellite access when the UE returns to the range of the satellite access from outside the range of the satellite access, and further, the first identification may be identification associated with a PLMN, and / or a RAT type, and / or an access type, and / or an area. Furthermore, when the correspondence of one or more of the RAT type, and / or the PLMN, and / or the access type, and / or the area, and / or the type of the core network or system included in the first information becomes the range of a different access and / or network, the operation based on the first identification may be temporarily stopped or until the UE becomes unregistered in the access and / or network.

[0253] [5.2. Second embodiment] A second embodiment of the present invention will be described below. In this section, the second embodiment will also be referred to as the present embodiment.

[0254] The second embodiment may be an embodiment executed after each behavior of the first embodiment is executed. Alternatively, the second embodiment may be an embodiment executed independently of the first embodiment. Alternatively, the second embodiment may be an embodiment executed without any relation to the first embodiment. More specifically, the second embodiment may be, for example, an embodiment after the UE of the first embodiment receives the first identification information and executes a behavior based on the first identification information. The behavior of the second embodiment described below overlaps with some behaviors of the first embodiment described in Chapter 5.1.

[0255] The UE of the first embodiment first receives a message including first identification information from the network via satellite access.

[0256] More specifically, for example, the UE of the second embodiment receives a message including the first identity from the network via satellite access during a network-initiated mobility management procedure or a registration procedure. Here, the first identity may be included in a configuration update command message or a registration accept message and transmitted from the network to the UE. More specifically, for example, the UE may receive a configuration update command message including the first identity or a registration accept message including the first identity from the AMF via satellite access.

[0257] Furthermore, the UE that receives the first identification information from the network may store the received first identification information, and when the UE receives new first identification information, the UE may replace the first identification information that has already been received and stored with the newly received first identification information.

[0258] Next, the UE having received the first identification information from the network may, when it falls out of satellite access range in the discontinuous satellite coverage and subsequently returns to range, initiate or perform a registration update procedure with the network via the satellite access based on the first identification information.

[0259] Wherein, the access and network from which the UE performs the registration update procedure may be the satellite access and network from which the UE received the first identity, and wherein the network from which the UE sent the message including the first identity may be the network in which the UE initially registered, and further, the first identity received by the UE may be associated with, for example, the PLMN of the source network and the RAT type of the satellite access.

[0260] Furthermore, when the UE returns to the satellite access range, if the waiting timer for discontinuous coverage is running, the UE does not need to perform the registration update procedure. In other words, for example, when the UE returns to the satellite access range, if the waiting timer for discontinuous coverage is running, the UE may wait for the timer to expire and perform the registration update procedure after the timer expires.

[0261] Here, the UE that has received the first identification information may repeat the execution of the registration update procedure each time it returns from outside the satellite access range to within range. For example, in a network in which the UE is registered, the UE may repeatedly execute the registration update procedure based on the first identification information and perform the operation until the UE transitions to an unregistered state.

[0262] Next, after the UE receives the first identification information, or while the UE has received the first identification information and is performing an operation based on the first identification information, the UE further receives a message including the second identification information from the network via satellite access during a network initiated mobility management procedure or during a registration procedure.

[0263] Here, the second identification information may be included in a configuration update command message or a registration accept message sent from the network to the UE. Here, for example, the registration accept message may be a message sent from the network to the UE and received by the UE during a registration update procedure initiated or performed by the UE based on the first identification information. Or, for example, the registration accept message may be a message sent from the network to the UE and received by the UE during a registration update procedure initiated or performed by the UE that is not based on the first identification information.

[0264] A UE that has received a second identification from the network may not start or may stop repeatedly executing a registration update procedure based on the first identification each time the UE returns from outside the satellite access range to within range based on the second identification.

[0265] In other words, for example, the UE of the second embodiment, after receiving first identification information from the network via satellite access, further receives second identification information from the network via satellite access, thereby stopping the initiation of a registration update procedure based on the first identification information when the UE returns from outside the satellite access range to within range, i.e., does not need to perform the registration update procedure.

[0266] Here, the second identification information may invalidate an operation based on the first identification information that is associated with the same combination of any one or more of a RAT type, and / or a PLMN, and / or an access type, and / or an area, and / or a type of a core network or system, and that is enabled. In other words, it is not necessary to invalidate the first identification information that is associated with a different combination of any one or more of a RAT type, and / or a PLMN, and / or an access type, and / or an area, and / or a type of a core network or system.

[0267] In addition, when the UE returns to satellite access coverage from outside the coverage area, the change in the core network or system may be from 5GCN (5G Core Network) or 5GS (5G System) to EPC (Evolved Packet Core) or EPS (Evolved Packet System), and when the core network or system is changed, the UE does not need to perform a registration update procedure based on the first identification information.

[0268] From the above, the second embodiment may be, for example, an embodiment in which, when a UE performing a behavior based on the first identification information described in the first embodiment further receives second identification information, the UE invalidates the behavior based on the first identification information being performed. Here, the behavior based on the first identification information that is invalidated by the second identification information may be a registration update procedure performed by the UE when it returns from within the satellite access range to outside the range, or a repetition of the registration procedure performed by the UE every time it returns from within the satellite access range to outside the range.

[0269] [5.3. Third embodiment] A third embodiment of the present invention will be described below. In this section, the third embodiment will also be referred to as the present embodiment.

[0270] The UE of the third embodiment receives a message including a third identity from the network via satellite access, where the message including the third identity may be any of the network initiated mobility management procedures mentioned in Chapter 4. Furthermore, the message including the third identity may be an MM message or a paging message, where the MM message may be, for example, a configuration update command message, or a notification message, or a DL NAS transport message.

[0271] The UE that receives the third identity from the network may initiate a registration update procedure with the network via satellite access based on receipt of the third identity.

[0272] Here, for example, if the UE receives a message including a third identification while the discontinuous coverage waiting timer is running, or based on the third identification received by the UE, the UE may stop the timer and initiate a registration update procedure to the network via satellite access.

[0273] Or, conversely, when the UE receives a message including the third identification information while the discontinuous coverage waiting timer is running, the UE may stop the timer and not start the registration update procedure. In other words, the UE that receives the third identification information in this case may wait for the discontinuous coverage waiting timer to expire, and perform the registration update procedure after the discontinuous coverage waiting timer expires.

[0274] From the above, the UE of the third embodiment may receive a message including the third identification information from the network, for example, via satellite access, and perform a registration update procedure via satellite access based on the reception of the third identification information.

[0275] Also, the third identification information may be an identification information that is transmitted only to UEs connecting via satellite access and not to UEs connecting via non-satellite access, or the third identification information may be an identification information that is transmitted to UEs connecting via either satellite access or non-satellite access.

[0276] Also, the third identification information may be an identification information that is transmitted from the network to the UE via satellite access and is not transmitted from the network to the UE via non-satellite access, or the third identification information may be an identification information that is transmitted to the UE via either satellite access or non-satellite access.

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

[0278] A program for implementing the functions of the embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. The program may be implemented by loading the program recorded on the recording medium into a computer system and executing it. The term "computer system" as used herein refers to a computer system built into an apparatus, and includes hardware such as an operating system and peripheral devices. The term "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 recording medium that can be read by a computer.

[0279] In addition, each functional block or feature of the device used in the above-mentioned embodiment may be implemented or performed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. The electric 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, or a conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. In addition, when a technology for integrated circuitization that replaces current integrated circuits appears due to the progress of semiconductor technology, one or more aspects of the present invention may use a new integrated circuit based on that technology.

[0280] The present invention is not limited to the above-mentioned embodiment. In the embodiment, one example of the device is described, but the present invention is not limited to this and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices of AV equipment, kitchen equipment, cleaning / washing equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0281] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within the scope of the gist of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are replaced with elements that have the same effect are also included. [Explanation of symbols]

[0282] 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 (E-UTRAN) 90 Core Network_A 120 Access Network_B (5G AN) 122 gNB 130 UPF 132 SMF 140 AMF 150 UDM 160 PCF 190 Core Network_B 235 UPF_A 239 UPF_C

Claims

1. A UE (User Equipment) comprising a transmitting / receiving unit and a control unit, The aforementioned transmitting and receiving unit receives a registration acceptance message containing the first information from the network. The control unit, If the first information indicates that the UE needs to perform the registration procedure at the end of the first period, When the aforementioned UE returns to coverage from outside the discontinuous coverage area, the timer starts. When the aforementioned timer expires, the registration procedure will be executed. A UE characterized by the following features.

2. The first period is the period during which the UE is outside the coverage due to discontinuous coverage by satellite access. The UE according to feature 1.

3. The transmitting and receiving unit, before the first period, receives the first information from the network in the registration acceptance message, The UE according to feature 1 or 2.

4. The registration procedure is a procedure for renewing mobility registration. The UE according to feature 1.

5. When the control unit receives a paging message, it stops the timer and starts NAS (Non-Access-Stratum) signaling. The UE according to feature 1.

Images