UE(User Equipment)

Abstract

To clarify mobility management when satellite coverage areas are discontinuous (discontinuous satellite coverage) and to provide user equipment (UE) that improves power consumption.SOLUTION: In a mobile communication system, UE capable of communicating via satellite receives a wait range from a first PLMN via a first satellite. When communication via the first satellite becomes impossible and then communication via a second satellite connecting to the first PLMN becomes possible, the UE selects the first PLMN, generates a wait timer based on the wait range, and starts a timer using the wait timer. If the UE makes an emergency call while the timer is running, the UE stops the timer and executes a registration procedure for the emergency call. If the UE does not make an emergency call while the timer is running, the UE executes the registration procedure after the timer expires.SELECTED DRAWING: Figure 3

Description

[Technical Field]

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

[0002] The 3GPP (3rd Generation Partnership Project: registered trademark) is studying the system architecture of the 5GS (5G System), a fifth-generation (5G) mobile communication system, and is discussing how to support new procedures and new functions (see Non-Patent Documents 1 to 3). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 23.501 V17.6.0 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17) [Non-patent document 2] 3GPP TS 23.502 V17.6.0 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17) [Non-patent document 3] 3GPP TS 24.501 V17.8.0 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 17) [Non-patent document 4] 3GPP TR 23.700-28 V1.1.1 (2022-10); 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] Release 17 introduced satellite communication functionality in 3GPP, and Release 18 discusses expanding that functionality. Specifically, it discusses mobility management in cases of discontinuous satellite coverage and power saving enhancements in UEs. However, the detailed behavior of UEs and networks has not been clarified (see Non-Patent Document 4).

[0005] In view of the above, one aspect of the present invention is to clarify the detailed behavior of UEs and networks in terms of mobility management in cases of discontinuous satellite coverage and power saving enhancements in UEs. [Means for solving the problem]

[0006] A UE according to one embodiment of the present invention is a UE having a transceiver unit and a control unit, the UE being capable of communicating via a satellite, the transceiver unit receiving a wait range from a network during a registration procedure, and / or a configuration update procedure, and / or a service request procedure, and / or a de-registration procedure performed in a first PLMN via a first satellite, the UE being configured to select the first PLMN when communication via a second satellite connected to the first PLMN becomes possible after communication via the first satellite becomes impossible, the control unit generating a wait timer based on the wait range, the control unit starting a timer using the wait timer, the control unit stopping the timer and performing a registration procedure for an emergency call if an emergency call is to be made while the timer is running, and the control unit performing a registration procedure after the timer expires if an emergency call is not to be made while the timer is running. [Effects of the Invention]

[0007] According to one aspect of the present invention, detailed UE and network behavior can be clarified for mobility management in the case of discontinuous satellite coverage and power saving enhancements in the UE. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an outline of a mobile communication system (EPS / 5GS). [Figure 2] FIG. 1 is a diagram illustrating the detailed configuration of a mobile communication system (EPS / 5GS). [Figure 3] FIG. 1 is a diagram illustrating the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Figure 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. DETAILED DESCRIPTION OF THE INVENTION

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

[0010] [1. System Overview]

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

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

[0013] In the following, these devices and functions may be referred to by abbreviating the symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

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

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

[0016] The 4G system EPS (Evolved Packet System) includes an access network A and a core network A, but may further include a UE and / or a PDN. The 5G system 5GS (5G System) includes a UE, an access network B, and a core network B, but may further include a DN.

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

[0018] Furthermore, access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are deployed in the E-UTRAN. Note that, hereinafter, the eNB 45 may be referred to by abbreviating the symbol eNB. If there are multiple eNBs, the eNBs are connected to each other, for example, via an X2 interface. Furthermore, one or more access points are deployed in the wireless LAN access network.

[0019] Furthermore, 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 deployed in the NG-RAN. Note that, hereinafter, the symbol for gNB 122 may be abbreviated, such as gNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to UEs, and is a node that connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). In other words, the gNB is a base station device newly designed for 5GS, and has different functions from the base station device (eNB) designed for the 4G system EPS. Furthermore, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

[0020] Furthermore, the non-3GPP access network may include an untrusted non-3GPP access network and 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 specified by 3GPP, and may include a trusted non-3GPP access point (TNAP) and a trusted non-3GPP gateway function (TNGF).

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

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

[0023] The core network_A corresponds to an EPC (Evolved Packet Core), which includes, 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), and an HSS (Home Subscriber Server).

[0024] Furthermore, the core network_B corresponds to a 5G Core Network (5GCN). In the 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), a Unified Data Management (UDM), etc. are arranged. Here, the 5GCN may be expressed as a 5GC.

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

[0026] The core network (core network _A and / or core network _B) may be an IP mobile communication network operated by a mobile network operator (MNO) that connects the access network (access network _A and / or access network _B) to the PDN and / or DN, 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 or virtual mobile communication service provider such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler).

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

[0028] In addition, hereinafter, 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 sends or receives a message and / or performs 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 send or receive a message and / or perform a procedure.

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

[0030] Here, IP communication refers to data communication using IP, and data is transmitted and received using IP packets. An IP packet consists of an IP header and a payload. The payload may include data transmitted and received by devices and functions included in EPS or devices and functions included in 5GS. Non-IP communication refers to data communication that does not use IP, and data is transmitted and received in a format different from the IP packet structure. For example, non-IP communication may be data communication achieved by transmitting and receiving application data without an IP header, or may be user data transmitted and received by a UE with a different header, such as a MAC header or an Ethernet (registered trademark) frame header, added.

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

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

[0033] The AAA server is a device that has authentication, authorization, and accounting functions and is connected to the AUSF directly or indirectly via another network device. The AAA server may be a network device within the core network. The AAA server may not be included in the core network _A and / or 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 within the PLMN managed by a third party.

[0034] 2, for the sake of simplicity, each device and function is shown one by one, but multiple similar devices and functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may be configured with multiple 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.

[0035] [2. Configuration of each device]

[0036] 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, as logical (virtual) hardware configured on general-purpose hardware, or 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.

[0037] Note that each memory unit (memory unit_A340, memory unit_B540, memory unit_B740) in each device / function mentioned below is configured with, for example, a semiconductor memory, a solid state drive (SSD), a hard disk drive (HDD), etc. Each memory unit can store not only information originally configured at the time of shipment, but also various information transmitted and received between devices / functions other than the device / function itself (e.g., UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Each memory unit can also store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described below. Each memory unit may also store this information for each UE. Furthermore, when interworking between 5GS and EPS is performed, each memory unit can store control messages and user data transmitted and received between devices / functions included in 5GS and / or EPS. In this case, not only those transmitted and received via the N26 interface but also those transmitted and received without via the N26 interface can be stored.

[0038] [2.1. UE Device Configuration]

[0039] First, an example of the device configuration of UE (User Equipment) will be explained using Figure 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.

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

[0041] The transceiver unit _A320 is a functional unit for wireless communication with a base station device (eNB or gNB) in the 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.

[0042] Explaining in detail with reference to Figure 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.

[0043] The memory unit _A340 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UE. The memory unit _340 may also have the function of storing control information transmitted and received between an access network device, a core network device, and a DN.

[0044] [2.2. gNB device configuration]

[0045] Next, an example of the gNB device configuration will be described using Figure 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.

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

[0047] 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 send and receive user data and / or control information between the AMF and / or UPF using the network connection unit _B520.

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

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

[0050] The memory unit _B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB. The memory unit _540 may also have the function of storing control information transmitted and received between the UE, other access network devices (base station devices), core network devices, and DNs.

[0051] [2.3. AMF device configuration]

[0052] Next, an example of the AMF device configuration will be explained using Figure 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.

[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 SMF, and / or PCF, and / or UDM, and / or SCEF, and / or NSACF in a 5G AN. In other words, the AMF can use the network connection unit _B720 to send and receive user data and / or control information between a base station device (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF in a 5G AN.

[0055] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with a gNB via the N2 interface by using the network connection unit _A620, can communicate with a UDM via the N8 interface, can communicate with an SMF via the N11 interface, and can communicate with a PCF via the N15 interface. The AMF can also send and receive NAS messages with a UE via the N1 interface by using the network connection unit _A620. However, since the N1 interface is logical, communication between the UE and the AMF is actually performed via a 5G AN. Furthermore, if the AMF supports the N26 interface, it can communicate with an 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. required for each operation of the AMF. The memory unit _740 may also have the function of storing control information transmitted and received between the UE, access network devices, other core network devices, and DN.

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

[0058] In addition, registration management manages the RM state for each UE. The RM state may be synchronized between the UE and the AMF. The RM state includes an unregistered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered with 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 with the network, and therefore the UE can receive services that require registration with the network. Note that the RM state may also 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 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 perform registration procedures other than the registration procedure for initial registration, and / or service request procedures.

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

[0061] In addition, connection management manages the CM state for each UE. 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 an N2 interface connection or an N3 interface connection. On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. In the CM-CONNECTED state, the UE may have an N2 interface connection and / or an N3 interface connection.

[0062] Furthermore, in connection management, the CM state in 3GPP access and the CM state in non-3GPP access may be managed separately. In this case, the CM state in 3GPP access may include 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 include 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). Note that 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-IDLE 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-IDLE mode over 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 among 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]

[0067] Next, an example of the SMF device configuration 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.

[0068] 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 needed.

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

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

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

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

[0073] In addition, the memory unit _740 may have the function of storing control information transmitted and received between the UE, access network devices, other core network devices, and DN.

[0074] [2.5. UPF device configuration]

[0075] Next, an example of the device configuration of the UPF will be explained using Figure 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.

[0076] The control unit _B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit _B700 realizes various processes in the UPF by reading and executing various programs stored in the memory unit _B740 as needed.

[0077] 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 within the 5G AN. In other words, the UPF can use the network connection unit _B720 to transmit and receive user data and / or control information between the base station device (gNB), and / or SMF, and / or DN within the 5G AN.

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

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

[0080] 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 gateway between DNs and core network_B that forwards user data), packet routing and forwarding, an UL CL (Uplink Classifier) ​​function that supports routing of multiple traffic flows to 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 to trigger downlink data notifications.

[0081] 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 a function for converting non-IP communication and IP communication. Furthermore, 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.

[0082] In addition, the memory unit _740 may have the function of storing control information transmitted and received between the UE, access network devices, other core network devices, and DN.

[0083] The user plane (also referred to as UP) refers to user data transmitted and received between a UE and a network. The user plane may be transmitted and received using a PDN connection in the case of 4G, or a PDU session in the case of 5G. 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 the 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 referred to as the U-Plane.

[0084] Furthermore, the control plane (also referred to as CP) refers to control messages transmitted and received to control UE communications, etc. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the MME. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the AMF. 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 referred to as the control plane or the C-Plane.

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

[0086] [2.6. Description of other devices and / or functions and identification information in this embodiment]

[0087] Next, other devices and / or functions and identification information will be described.

[0088] A network refers to at least a portion of an access network _B, a core network _B, and a DN. Furthermore, one or more devices included in at least a portion of an access network _B, a core network _B, and a 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 devices within the network (network devices and / or control devices) transmit, receive, receive, and / or process messages. Conversely, when a device within the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, receives, and / or processes messages.

[0089] In addition, an NSSF (Network Slice Selection Function) may be a network function (also referred to as an NF) that has the function of selecting a network slice that serves a UE.

[0090] Furthermore, an NWDAF (Network Data Analytics Function) may be an NF that has the function of collecting data from an NF or an application function (also referred to as an AF).

[0091] Furthermore, a PCF (Policy Control Function) may be an NF having a function of determining a policy for controlling the behavior of a network.

[0092] Furthermore, an NRF (Network Repository Function) may be an NF having a service discovery function, which may have a function of providing information about the discovered NF when receiving a discovery request for another NF from another NF.

[0093] A Network Slice Admission Control Function (NSAC) may also monitor and control the number of registered UEs per NS and / or the number of PDU sessions per NS for network slices (NSs) associated with the Network Slice Admission Control (NSAC). The NSACF may also be configured with a maximum number of allowed UEs per NS and / or a maximum number of allowed PDU sessions per NS for each NS associated with the NSAC. The NSACF may also be capable of increasing or decreasing the number of UEs registered with an NS so as not to exceed the maximum number of UEs allowed to register with that NS. The NSACF may also maintain a list of UE IDs registered with an NS associated with the NSAC. When the number of UEs registered with an NS increases (e.g., when a UE sends a new registration request message to the NS), the NSACF may also be capable of checking whether the ID of the UE is already included in the list of UE IDs registered with the NS. If the ID of the UE is not included in the list, the NSACF may further check with the NS whether the maximum number of UEs per NS has been reached. Furthermore, when the registration status of a UE for an NS associated with an NSAC changes during a registration procedure, a deregistration procedure, and / or an NSSAA procedure, the AMF may request the NSACF regarding the maximum number of UEs per NS. The NSACF may also have a function to increase or decrease the number of PDU sessions for an NS so as not to exceed the maximum number of PDU sessions permitted by that NS. When the number of PDU sessions using an NS increases (e.g., when a UE sends a PDU session establishment request message to that NS), the NSACF may also have a function to check for that NS whether the maximum number of UEs per NS has been reached. The SMF may also request the NSACF regarding the maximum number of PDU sessions per NS during a PDU session establishment procedure and / or a PDU session release procedure.

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

[0095] The SM procedure (also referred to as a procedure for SM) 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 the NW.

[0096] Furthermore, an MM (Mobility management) message (also referred to as an NAS MM message) may be an NAS message used in procedures 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 (also referred to as a non-registration request) message, a de-registration accept (also referred to as a non-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, etc.

[0097] In addition, the MM procedure (also referred to as a procedure for MM) may include a registration procedure, a de-registration procedure (also referred to as a non-registration procedure), a generic UE configuration update procedure, an authentication and authorization procedure, a service request procedure, a paging procedure, and a notification procedure.

[0098] In addition, the 5GS (5G System) service may be 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.

[0099] In addition, non-5GS services may be services other than 5GS services, and may include EPS services and / or non-EPS services.

[0100] Furthermore, the 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 via a communication method other than IP.

[0101] Furthermore, a PDU (Protocol Data Unit) session can be defined as an association between a DN that provides 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 to and from a DN by establishing a PDU session via an access network _B and a core network _B. Here, this external gateway may be a UPF, SCEF, or the like. The UE can transmit and receive user data to and from a device such as an application server located in the DN using the PDU session.

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

[0103] Each device (UE, and / or access network device, and / or core network device) may associate one or more pieces of identification information with a PDU session and manage them. These pieces of identification information may include one or more of the DNN, QoS rule, PDU session type, application identification information, NSI identification information, and access network identification information, or may further include other information. Furthermore, when multiple PDU sessions are established, the identification information associated with the PDU sessions may be the same or different.

[0104] Furthermore, 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 can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 that connects the core network B190. Furthermore, the DNN may be equivalent to an APN (Access Point Name).

[0105] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and can be IPv4, IPv6, Ethernet, or Unstructured. If IPv4 is specified, it indicates that data will be transmitted and received using IPv4. If IPv6 is specified, it indicates that data will be transmitted and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be transmitted and received. Furthermore, Ethernet may indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data will be transmitted and received to an application server or the like in the 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 if the UE is capable of using both IPv4 and IPv6.

[0106] 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 communications 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 store an Equivalent HPLMN list in its 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 a UE has successfully registered may be a Registered PLMN (RPLMN). Note that a service provided by a PLMN may be referred to as a PLMN service, and a service provided by an SNPN may be referred to as an SNPN service.

[0107] A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. UEs and / or networks can support network slices (NW slices; NS) in 5GS. A network slice may also be simply referred to as a slice.

[0108] A network slice instance (NSI) is composed of an instance (entity) of a network function (NF) and a set of required resources, forming a deployed network slice. Here, an NF is a processing function in a network, adopted or defined by 3GPP. An NSI is an entity of one or more NSs configured within a core network _B. An NSI may also be composed of virtual network functions (NFs) generated using a network slice template (NST). Here, an NST is associated with resource requirements for providing required communication services and capabilities, and is a logical representation of one or more NFs. In other words, an NSI may be a collection of multiple NFs within the core network _B 190. An NSI may also be a logical network configured to separate user data delivered by services, etc. One or more NFs may be configured within an NS. The NFs configured in an NS may or may not be devices shared with other NSs. A UE and / or a device in the network can be assigned to one or more NSs based on registration information such as an NSSAI, an S-NSSAI, an UE usage type, an NSI ID, or one or more APNs. The UE usage type is a parameter value included in the UE registration information and used to identify the NSI. The UE usage type may be stored in the HSS. The AMF may select an SMF and a UPF based on the UE usage type.

[0109] Furthermore, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying an NS. The S-NSSAI may consist of only an SST (Slice / Service type), or may consist of an SST and an SD (Slice Differentiator). Here, the SST is information indicating the expected behavior of the NS in terms of functions and services. The SD may be information that interpolates the SST when selecting one NSI from multiple NSIs indicated by the SST. The S-NSSAI may be information specific to each PLMN, or may be standard information common among PLMNs. The network may store one or more S-NSSAIs in the registration information of the UE as default S-NSSAIs. Note that when the S-NSSAI is the default S-NSSAI, if the UE does not send a valid S-NSSAI to the network in a registration request message, the network may provide an NS related to the UE.

[0110] Also, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAIs. Each S-NSSAI included in the NSSAI is information that assists the access network or core network in selecting an NSI. The UE may store the NSSAI authorized by the network for each PLMN. Also, the NSSAI may be information used to select an AMF.

[0111] Furthermore, a configured NSSAI (also referred to as a configured NSSAI) is an NSSAI applicable to one or more PLMNs or SNPNs, and is provided to and stored in a UE. The UE may store a configured NSSAI for each PLMN, or may store a configured NSSAI for each NPN (hereinafter, SNPNs and / or PNI-NPNs may be collectively referred to as NPNs). The configured NSSAI may be information configured by the network (PLMN or SNPN). The S-NSSAI included in the configured NSSAI may be expressed as a configured S-NSSAI. The configured S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI. The configured NSSAI may include a configured NSSAI stored in the UE and a configured NSSAI transmitted from the network to the UE.

[0112] Furthermore, the requested NSSAI (also referred to as Requested NSSAI) is an NSSAI provided from the UE to the network (current PLMN (serving PLMN, also referred to as current PLMN) or NPN (serving NPN, also referred to as current NPN)) during the registration procedure. The S-NSSAI included in the requested NSSAI may be an S-NSSAI selected from one or more S-NSSAIs included in the configured NSSAI and / or allowed NSSAI associated with the current PLMN or NPN. Furthermore, the S-NSSAI included in the requested NSSAI may be an S-NSSAI selected so as not to include one or more S-NSSAIs included in the pending NSSAI and / or rejected NSSAI. Furthermore, the requested NSSAI may be information indicating the network slice to which the UE wishes to register or access. Furthermore, the S-NSSAI included in the requested NSSAI may be expressed as requested S-NSSAI. The requested NSSAI may be included in an NAS message, such as a registration request message, transmitted from the UE to the network (PLMN or SNPN), and / or a Radio Resource Control (RRC) message including a Non-Access-Stratum (NAS) message. The requested NSSAI may include a requested NSSAI stored in the UE and a requested NSSAI transmitted from the UE to the network (PLMN or SNPN).

[0113] The allowed NSSAI (also referred to as Allowed NSSAI) is information indicating one or more network slices to which a UE is permitted. In other words, the allowed NSSAI may be information identifying a network slice to which the network has permitted the UE to connect. The allowed NSSAI may also be information indicating one or more S-NSSAIs that can be used in the current PLMN or SNPN in the current registration area. The UE and the network each store and manage the allowed NSSAI for each access (3GPP access or non-3GPP access) as information for the UE. The S-NSSAI included in the allowed NSSAI may be expressed as the allowed S-NSSAI. The allowed S-NSSAI may be configured to include the S-NSSAI and the mapped S-NSSAI. The allowed NSSAI may include the allowed NSSAI stored in the UE and the allowed NSSAI transmitted from the network to the UE.

[0114] Furthermore, the mapped S-NSSAI (also referred to as Mapped S-NSSAI) may be the S-NSSAI of the HPLMN mapped to the S-NSSAI of the registered PLMN in a roaming scenario. The mapped S-NSSAI may basically be the S-NSSAI used when the UE is roaming, or may be the S-NSSAI not used when the UE is not roaming (also referred to as non-roaming). The UE may store one or more mapped S-NSSAIs mapped to the configured NSSAI and the S-NSSAI included in the Allowed NSSAI for each access type. The UE may also store one or more mapped S-NSSAIs included in the rejected NSSAI or mapped S-NSSAIs corresponding to the S-NSSAI included in the rejected NSSAI. The mapped NSSAI may include a mapped NSSAI stored in the UE and a mapped NSSAI transmitted from the network to the UE.

[0115] Furthermore, a rejected NSSAI (also referred to as Rejected NSSAI) is information indicating one or more network slices to which a UE is not permitted to connect. In other words, a rejected NSSAI is information identifying a network slice to which a network does not permit a UE to connect. A rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value (hereinafter also referred to as a reason value or rejection reason). Here, a rejection reason value is information indicating a reason why a network rejects a corresponding S-NSSAI. The UE and the network may store and manage the rejected NSSAI appropriately based on the rejection reason value associated with each S-NSSAI. Furthermore, the rejected NSSAI may be included in an NAS message transmitted from the network to a UE, such as a registration accept message, a configuration update command, or a registration reject message, or in an RRC message including an NAS message. An S-NSSAI included in a rejected NSSAI may be expressed as a rejected S-NSSAI. Here, the rejected NSSAI may mean any of the first to fourth rejected NSSAIs. Furthermore, the rejected S-NSSAI may mean a rejected S-NSSAI included in any of the first to fourth rejected NSSAIs. Furthermore, the rejected NSSAI may be any of the first to fourth rejected NSSAIs and a pending NSSAI, or a combination of these. An S-NSSAI included in a rejected NSSAI may be expressed as a rejected S-NSSAI. The rejected S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0116] Here, the first rejected NSSAI may be a rejected NSSAI for the current PLMN or SNPN. In other words, the first rejected NSSAI may be an NSSAI that cannot be used in the current PLMN or SNPN. Alternatively, the first rejected NSSAI may be a set of one or more S-NSSAIs that the UE included in the requested NSSAI are not available in the current PLMN or SNPN. The first rejected NSSAI may be a 5GS rejected NSSAI for the current PLMN or SNPN. Alternatively, the first rejected S-NSSAI may be a rejected S-NSSAI for the current PLMN or SNPN, or may be an S-NSSAI included in the rejected NSSAI for the current PLMN or SNPN. Alternatively, the first rejected NSSAI may be a rejected NSSAI stored by the UE and / or the NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the first rejected NSSAI is a rejected NSSAI transmitted from a NW to a UE, the first rejected NSSAI may be information including one or more combinations of an S-NSSAI and a reason value. The rejection reason value may indicate "S-NSSAI not available in the current PLMN or SNPN," which may mean that the S-NSSAI associated with the rejection reason value is not available in the current PLMN or SNPN.

[0117] Furthermore, the first rejected NSSAI may be valid for the entire registered PLMN or registered SNPN. In other words, the UE and / or NW may treat the first rejected NSSAI and the S-NSSAI included in the first rejected NSSAI as information independent of the access type. That is, the first rejected NSSAI may be information valid for both 3GPP access and non-3GPP access.

[0118] The UE may delete the first rejected NSSAI from its memory if it transitions to an unregistered state in both 3GPP access and non-3GPP access for the current PLMN or SNPN. In other words, if the UE transitions to an unregistered state for the current PLMN or SNPN via an access, or if the UE successfully registers to a new PLMN or SNPN via an access, or if the UE fails to register to the new PLMN via an access and transitions to an unregistered state, and if the UE is not registered via the other access (unregistered state), the UE may delete the first rejected NSSAI.

[0119] Furthermore, the S-NSSAI included in the first rejected NSSAI in the memory unit of the UE may be treated as unusable in the current PLMN or the entire SNPN, i.e., the UE may be in a state where MM procedures and / or SM procedures using the S-NSSAI are prohibited in the current PLMN or the entire SNPN.

[0120] The second rejected NSSAI may be a rejected NSSAI for the current registration area (also referred to as a registration area). In other words, the second rejected NSSAI may be an NSSAI that cannot be used in the current registration area. The second rejected NSSAI may be a set of one or more S-NSSAIs that the UE included in the requested NSSAI and that are not available in the current registration area. The second rejected NSSAI may be a rejected NSSAI of 5GS for the current registration area. The second rejected NSSAI may be a rejected NSSAI stored by the UE and / or the NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the second rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the second rejected NSSAI may be information including one or more combinations of an S-NSSAI and a reason value. This reason value may indicate "S-NSSAI not available in the current registration area," which may mean that the S-NSSAI associated with the reason value is not available in the current registration area.

[0121] Furthermore, the second rejected NSSAI may be valid within the current registration area. That is, the UE and / or NW may treat the second rejected NSSAI and the S-NSSAI included in the second rejected NSSAI as information for each access type. That is, the second rejected NSSAI may be information valid for each of 3GPP access and non-3GPP access. That is, once the UE transitions to an unregistered state for a certain access, the UE may delete the second rejected NSSAI from its memory.

[0122] Furthermore, the S-NSSAI included in the second rejected NSSAI in the memory unit of the UE may be treated as unusable in the current registration area, i.e., the UE may be in a state where the MM procedure and / or SM procedure using the S-NSSAI is prohibited in the current registration area.

[0123] Furthermore, the third rejected NSSAI is a set of one or more S-NSSAIs that require an NSSAA and for which the NSSAA for that S-NSSAI has failed or been revoked. The third rejected NSSAI may be an NSSAI stored by the UE and / or the NW, or may be transmitted from the NW to the UE. When the third rejected NSSAI is transmitted from the NW to the UE, the third rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value. In this case, the rejection reason value may be "S-NSSAI is not available due to the failed or revoked network slice-specific authorization and authentication" or may be information indicating that the NSSAA for the S-NSSAI associated with the rejection reason value has failed or been revoked.

[0124] Furthermore, the third rejected NSSAI is valid for the entire registered PLMN. In other words, the UE and / or NW may treat the third rejected NSSAI and the S-NSSAI included in the third rejected NSSAI as information independent of the access type. That is, the third rejected NSSAI may be information valid for 3GPP access and non-3GPP access. The third rejected NSSAI may be an NSSAI different from the rejected NSSAI. The third rejected NSSAI may be the first rejected NSSAI.

[0125] The third rejected NSSAI identifies a slice that the UE rejected due to an NSSAA failure or revocation from the core network. Specifically, while the UE stores the third rejected NSSAI, the UE does not initiate a registration request procedure for the S-NSSAI included in the third rejected NSSAI. The third rejected NSSAI may be identification information including one or more S-NSSAIs received from the core network in association with a rejection reason value indicating an NSSAA failure. The third rejected NSSAI is information independent of the access type. Specifically, when the UE stores the third rejected NSSAI, the UE may not attempt to send a registration request message including the S-NSSAI included in the third rejected NSSAI to both 3GPP access and non-3GPP access. Alternatively, the UE may send a registration request message including the S-NSSAI included in the third rejected NSSAI based on a UE policy. Alternatively, the UE may delete the third rejected NSSAI based on the UE policy and transition to a state in which it can transmit a registration request message including an S-NSSAI included in the third rejected NSSAI. In other words, when the UE transmits a registration request message including an S-NSSAI included in the third rejected NSSAI based on the UE policy, the UE may delete the S-NSSAI from the third rejected NSSAI.

[0126] Furthermore, the S-NSSAI included in the third rejected NSSAI in the memory unit of the UE may be treated as being unusable in the entire current PLMN or SNPN, i.e., the UE may be in a state where MM procedures and / or SM procedures using the S-NSSAI are prohibited in the current registration area.

[0127] In addition, the fourth rejected NSSAI may be a rejected NSSAI for the current tracking area. In other words, the fourth rejected NSSAI may be an NSSAI that cannot be used in the current tracking area.

[0128] The fourth rejected NSSAI may also be a rejected NSSAI for the current tracking area in the current registration area. In other words, the fourth rejected NSSAI may be an NSSAI that cannot be used in the current tracking area in the current registration area.

[0129] Furthermore, the fourth rejected NSSAI may be an NSSAI that cannot be used in the current tracking area in the current registration area, but may be an NSSAI that can be used in other tracking areas in the current registration area.

[0130] Furthermore, the fourth rejected NSSAI may be an NSSAI that cannot be used in the current tracking area in the current registration area, but may be an NSSAI that can be used in other tracking areas in the current registration area and other registration areas (different from the current registration area).

[0131] Furthermore, the fourth rejected NSSAI may be a set of S-NSSAIs included in the requested NSSAI by the UE, which may be S-NSSAIs that are not available in the current tracking area, or a set of S-NSSAIs sent by the AMF with a rejection reason indicating that the S-NSSAIs are not available in the current tracking area.

[0132] Also, in a roaming scenario (while roaming), the fourth rejected NSSAI may include one or more S-NSSAIs for the current PLMN, or may include a set of mapped S-NSSAIs if available.

[0133] Furthermore, the fourth rejected NSSAI may be a rejected NSSAI stored by the UE and / or the NW, or may be a rejected NSSAI transmitted from the NW to the UE. If the fourth rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the fourth rejected NSSAI may be information including one or more combinations of an S-NSSAI and a reason value. The reason value may be the twelfth identification information.

[0134] Furthermore, the fourth rejected NSSAI may be valid for 3GPP access and / or non-3GPP access. In other words, the UE and / or NW may treat the fourth rejected NSSAI as independent of the access type, or may treat the fourth rejected NSSAI as dependent on the access type. In other words, the UE and / or NW may manage and / or store the fourth rejected NSSAI for each access type, or may not manage and / or store the fourth rejected NSSAI for each access type.

[0135] Furthermore, a pending NSSAI (also referred to as a Pending NSSAI) is an S-NSSAI that requires network slice specific authentication by the network, and is a collection of one or more S-NSSAIs that are not usable in the current PLMN because the network slice specific authentication has not been completed. The pending NSSAI may be a 5GS Rejected NSSAI due to NSSAA or a pending NSSAI. The pending NSSAI may be an NSSAI stored by the UE or the NW, or an NSSAI transmitted from the NW to the UE. Note that the pending NSSAI is not limited to the rejected NSSAI, and may be an NSSAI independent of the rejected NSSAI. When the pending NSSAI is an NSSAI transmitted from the NW to the UE, the pending NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value. The rejection reason value at this time may be "NSSAA is pending for the S-NSSAI" and may be information indicating that the S-NSSAI associated with the rejection reason value is prohibited or pending use by the UE until the NSSAA for that S-NSSAI is completed.

[0136] Furthermore, the pending NSSAI is valid for the entire registered PLMN. In other words, the UE and / or NW may treat the third rejected NSSAI and the S-NSSAI included in the pending NSSAI as information independent of the access type. That is, the pending NSSAI may be information valid for 3GPP access and non-3GPP access. The pending NSSAI may be an NSSAI different from the rejected NSSAI. The pending NSSAI may be the first rejected NSSAI.

[0137] Furthermore, the pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that identify slices for which the UE has pending procedures. Specifically, while the UE stores the pending NSSAI, it does not initiate a registration request procedure for the S-NSSAI included in the pending NSSAI. In other words, the UE does not use the S-NSSAI included in the pending NSSAI during the registration procedure until the NSSAA for the S-NSSAI included in the pending NSSAI is completed. The pending NSSAI is identification information that includes one or more S-NSSAIs received from the core network in association with a rejection reason value indicating a pending NSSAA. The pending NSSAI is information that is independent of the access type. Specifically, when the UE stores the pending NSSAI, the UE does not attempt to send a registration request message including the S-NSSAI included in the pending NSSAI to both 3GPP access and non-3GPP access.

[0138] 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. A tracking area may be composed of multiple cells. Furthermore, a tracking area may be an area in which control messages such as paging are broadcast, or an area in which UE_A10 can move without performing a handover procedure. Furthermore, a tracking area (also referred to as a Tracking Area, TA) may be a routing area, a location area, or anything similar. A tracking area may be identified by a Tracking Area Identity (TAI) consisting of a Tracking Area Code (TAC) and a PLMN.

[0139] A registration area (also referred to as a registration area) is a set of one or more TAs assigned to a UE by the AMF. 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 signals for tracking area update. In other words, a registration area may be a group of information indicating areas 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.

[0140] The UE ID is information for identifying a UE. Specifically, for example, the UE ID may be a SUCI (Subscription Concealed Identifier), a SUPI (Subscription Permanent Identifier), a GUTI (Globally Unique Temporary Identifier), an IMEI (International Mobile Subscriber Identity), 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.

[0141] Network Slice-Specific Authentication and Authorization (NSSAA) is a function for realizing network slice-specific authentication and authorization. Network slice-specific authentication and authorization allows UE authentication and authorization to be performed outside the core network, such as by a third party. PLMNs and network devices with NSSAA functionality can perform NSSAA procedures for a certain S-NSSAI based on the UE's registration information. Furthermore, UEs with NSSAA functionality can manage and store rejected NSSAIs for pending NSSAA and / or rejected NSSAIs for failed NSSAA. In this document, NSSAA may be referred to as the network slice-specific authentication and authorization procedure or the authentication and authorization procedure.

[0142] An S-NSSAI requiring an NSSAA is an S-NSSAI requiring an NSSAA that is managed by a core network and / or a core network device. The core network and / or core network device may store an S-NSSAI requiring an NSSAA by associating the S-NSSAI with information indicating whether an NSSAA is required. The core network and / or core network device may further store an S-NSSAI requiring an NSSAA with information indicating whether an NSSAA has been completed, or information indicating that the NSSAA has been completed and is permitted or successful. The core network and / or core network device may manage an S-NSSAI requiring an NSSAA as information unrelated to the access network.

[0143] Also, a UE in single registration mode has only one active MM state. That is, a UE in single registration mode can only be active in either the RM state (5GMM state) in 5GC or the EMM state in EPC. Also, a UE in single registration mode is in 5GC NAS mode when connecting to 5GC, and is in EPC NAS mode when connecting to EPC. Also, since a UE in single registration mode can only be registered to either 5GC or EPC, when moving between EPC and 5GC, it is necessary to map EPS-GUTI (also referred to as 4G-GUTI) and 5G-GUTI.

[0144] In addition, a UE in dual registration mode may be able to independently register with 5GC and EPC. A UE in dual registration mode can independently maintain 5G-GUTI and EPS-GUTI (also referred to as 4G-GUTI).

[0145] An SNPN is a type of NPN that is a 5GS service deployed for non-public use. It is operated by an NPN operator and is independent of the NF provided by the PLMN. An SNPN is identified by a combination of a PLMN ID and a Network Identifier (NID). A UE capable of using an SNPN may support an SNPN access mode (also referred to as an SNPN access operation mode). A UE configured to operate in the SNPN access mode may be able to select an SNPN and register with the SNPN, but may not be able to select a PLMN. A UE configured to operate in the SNPN access mode may be able to perform an SNPN selection procedure, but may not be able to perform a PLMN selection procedure. A UE that is enabled for an SNPN but not configured to operate in the SNPN access mode may be unable to select an SNPN and register with the SNPN, but may be able to select a PLMN. A UE that is not configured to operate in the SNPN access mode may be unable to perform an SNPN selection procedure, but may be able to perform a PLMN selection procedure.

[0146] Also, a UE operating in SNPN access mode may be able to select an SNPN via Uu (3GPP access). Also, a UE operating in SNPN access mode may be able to select an SNPN via Uu or NWu established via a PDU session provided by a selected PLMN via Uu or NWu (non-3GPP access). Also, a UE not operating in SNPN access mode may be able to select a PLMN via Uu or NWu established via a PDU session provided by a selected SNPN via Uu or NWu (non-3GPP access).

[0147] The SNPN access mode may be managed and / or applied on an access basis. That is, it may be managed and / or applied separately for 3GPP access and non-3GPP access. In other words, activation or deactivation of the SNPN access mode for 3GPP access may be independent of activation or deactivation of the SNPN access mode for non-3GPP access. That is, when the SNPN access mode for 3GPP access is activated, the SNPN access mode for non-3GPP access may be activated or deactivated. Furthermore, when the SNPN access mode for 3GPP access is deactivated, the SNPN access mode for non-3GPP access may be activated or deactivated.

[0148] Here, the SNPN access mode for 3GPP access may also be referred to as the SNPN access mode over 3GPP access or the SNPN access mode via 3GPP access.

[0149] In addition, the SNPN access mode for non-3GPP access may also be referred to as the SNPN access mode over non-3GPP access or the SNPN access mode via non-3GPP access.

[0150] Furthermore, "activation" may be read as "operation" and "deactivation" may be read as "not operation." In other words, activation of the SNPN access mode for 3GPP access may mean operation in the SNPN access mode for 3GPP access. Deactivation of the SNPN access mode for 3GPP access may mean not operation in the SNPN access mode for 3GPP access. Activation of the SNPN access mode for non-3GPP access may mean operation in the SNPN access mode for non-3GPP access. Deactivation of the SNPN access mode for non-3GPP access may mean not operation in the SNPN access mode for non-3GPP access.

[0151] In addition, when a UE roams between SNPNs, the SNPN may be classified as a Home SNPN (also referred to as an HSNPN) and a Visited SNPN (also referred to as a VSNPN).In addition, when a UE does not roam between SNPNs, the SNPN may be treated as the same as the Home SNPN.

[0152] The Home SNPN may be an SNPN that the UE can register as its home. The Home SNPN may be an SNPN that the UE initially selects during SNPN selection. The Home SNPN may be an SNPN in which at least a portion of information included in the SNPN identity (also referred to as an SNPN ID) matches at least a portion of information included in the IMSI of the UE. The Home SNPN may be an SNPN in which the MCC and MNC included in the PLMN identity (also referred to as a PLMN ID) included in the SNPN identity (also referred to as an SNPN ID) match the MCC and MNC included in the IMSI of the UE.

[0153] A visited SNPN may be an SNPN that the UE can register as other than its home. A visited SNPN may be an SNPN that the UE does not register as its home. A visited SNPN may be an SNPN that the UE does not initially select during SNPN selection. A visited SNPN may be an SNPN in which at least some of the information included in the SNPN identity (also referred to as an SNPN ID) does not match at least some of the information included in the IMSI of the UE. A visited SNPN may be an SNPN in which the MCC and MNC included in the PLMN identity (also referred to as a PLMN ID) included in the SNPN identity (also referred to as an SNPN ID) do not match the MCC and MNC included in the IMSI of the UE.

[0154] Furthermore, an equivalent HSNPN (also referred to as equivalent Home SNPN, EHSNPN) may be an SNPN that is considered to be equivalent to a current SNPN (herein also referred to as Home SNPN (HSNPN)) in SNPN selection, cell selection, and / or cell reselection. Furthermore, an equivalent HSNPN may be one or more SNPNs included in the equivalent HSNPN list, or one or more SNPNs not included in the equivalent VSNPN list.

[0155] Furthermore, an equivalent VSNPN (also referred to as equivalent Visited SNPN, EVSNPN) may be an SNPN that is considered to be equivalent to a current SNPN (herein also referred to as Visited SNPN (VSNPN)) in SNPN selection, cell selection, and / or cell reselection. Furthermore, an equivalent VSNPN may be one or more SNPNs included in the equivalent VSNPN list, or one or more SNPNs not included in the equivalent HSNPN list.

[0156] Furthermore, the equivalent SNPN (also referred to as ESNPN) may be a concept that includes the equivalent HSNPN and / or the equivalent VSNPN. In other words, the ESNPN may refer to the equivalent HSNPN and / or the equivalent VSNPN.

[0157] In addition, the SNPN to which the UE has successfully registered may be an RSNPN (Registered SNPN).

[0158] Next, the identification information transmitted, received, stored and / or managed by each device in this embodiment will be described.

[0159] The UE, the base station, the AMF, the SMF, and / or other core network devices or network functions may store information in advance and generate new information as needed. When information is transmitted and received between them, the receiving party may store the received information and perform operations based on the information.

[0160] 3. First Embodiment

[0161] First, a description will be given of the procedures used in the first embodiment. The procedures used in the first embodiment may include the MM procedure and SM procedure described above.

[0162] In the first embodiment, as shown in FIG. 2, an example will be described in which 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 / function (i.e., the same physical hardware, the same logical hardware, or the same software). However, the contents described in this embodiment are also applicable to cases in which these are configured as different devices / functions (i.e., different physical hardware, different logical hardware, or different software). For example, data may be transmitted and received directly between these, or may be transmitted and received via the N26 interface between the AMF and MME, or may be transmitted and received via the UE.

[0163] The AMF may determine a RAT type for NR satellite access. Here, the NR satellite access may refer to a connection between the UE and the core network via a satellite using NR and / or 5G communication functions. In other words, when the UE connects to the network via a satellite access, the AMF may determine the RAT type. In this specification, the NR satellite access may be simply referred to as a satellite connection. The NR satellite access may also include NR (LEO), NR (MEO), NR (GEO), and NR (OTHERSAT). The NR (LEO) may refer to a connection between the UE and the core network via a LEO satellite using NR and / or 5G communication functions. The NR (MEO) may refer to a connection between the UE and the core network via a MEO satellite using NR and / or 5G communication functions. The NR (MEO) may also refer to a connection between the UE and the core network via a GEO satellite using NR and / or 5G communication functions. NR(OTHERSAT) may also mean a connection between a UE and a core network via a satellite other than LEO, MEO, or GEO using NR and / or 5G communication capabilities. RAT type values ​​such as NR(LEO), NR(MEO), NR(GEO), and NR(OTHERSAT) may also be used in 5GC to identify the type of satellite connection.

[0164] Also, when the UE is connected to an NR or network using a satellite connection (when connected using an NR satellite connection), information indicating the type of NR satellite connection (which may be a RAT type) may be provided between the AMF and the base station using the N2 interface.

[0165] Furthermore, the TA to which the cells (communication areas) of the RAT type for each satellite connection belong may be different from the TA to which the cells of other RAN types belong, or may be different from the TA to which the terrestrial RAT type belongs.

[0166] The AMF may also initiate a deregistration procedure to deregister the UE when it receives a release request for an N2 connection (e.g., an N2 UE context release request) from the base station with a cause value indicating that the UE is not in the serving area of ​​the PLMN.

[0167] Also, network selection (PLMN selection and access network selection) for satellite connections may be provided identical to terrestrial network selection.

[0168] Additionally, in a satellite connection, a UE with location capability may use information about the UE's location to select a PLMN that can operate or connect to at that location.

[0169] Additionally, moving cells for satellite connections, i.e., cells that move with the movement of the satellite, may indicate support for one or more TACs per PLMN.

[0170] Furthermore, a UE registered with a PLMN (a PLMN providing satellite connectivity) may be able to connect to a cell and may not need to perform a registration procedure (a registration procedure that is performed as the UE moves) if the TAC for the RPLMN or a PLMN that is equivalent to the RPLMN (also called EPLMN) is part of the UE's registration area.

[0171] In addition, the UE may perform a registration procedure (a registration procedure performed in conjunction with movement) if the TAC for the RPLMN or a PLMN that is equivalent to the RPLMN is not in the registration area of ​​the UE.

[0172] In addition, when the UE indicates the last visited TAI during the registration procedure, it may indicate at least some of the TAIs supported in cells where the TAC for the RPLMN or a PLMN that is equivalent to the RPLMN, to which the UE was connected before the registration procedure, is part of the UE's registration area.

[0173] Furthermore, even when a cell is moving on the surface of the Earth, the base station may change the TAC value and broadcast the changed TAC value in the system information of the cell.

[0174] Also, the base station may broadcast one TAC per PLMN in a cell and may change the TAC value as the cell moves, or the base station may broadcast more than one TAC per PLMN in a cell and may add or remove TAC values ​​as the cell moves.

[0175] The base station may also send the TAI for the selected PLMN to the AMF.

[0176] The base station may also indicate to the AMF the TAI in which the UE is located. The AMF may generate a registration area suitable for the UE, taking into account the TAI in which the UE is located received from the base station.

[0177] The AMF and the UE may also receive one or more TAIs broadcast from the base station. The AMF may also consider the UE to be in a forbidden area if some or all of the received TAIs are forbidden based on the UE's subscription data. The UE may also consider the UE to be in a forbidden area if some or all of the received TAIs are forbidden. The UE may also consider the UE to be not in a forbidden area if at least one of the received TAIs is not forbidden.

[0178] The AMF may also receive one or more TAIs broadcast from the base station, and may provide service area restrictions consisting of allowed areas or non-allowed areas.

[0179] Also, when changing to a suitable cell that indicates multiple TAs to the RPLMN, and all of those multiple TAs are outside the registration area of ​​the UE in the CM-CONNECTED and CM-IDLE states, the registration procedure may be initiated.

[0180] The UE may also send the last visited TAI to the AMF to help the AMF create a registration area for the UE.

[0181] The AMF may also verify the location of the UE during the registration procedure or service request procedure and determine whether a PLMN is operational at the UE's location.

[0182] The UE may also perform PLMN selection to select another PLMN when it receives a registration rejection message or a service rejection message that includes a cause value indicating that the PLMN is not permitted to operate at the UE's current location.

[0183] The AMF may also initiate a network-initiated de-registration procedure when it detects that the PLMN to which the UE is registered is not authorized to operate at the current UE location, in which case the AMF may send a de-registration request message to the UE, the de-registration request message including a cause value indicating that the PLMN is not authorized to operate at the current UE location.

[0184] In addition, when a UE connected to a satellite moves out of the serving area of ​​the PLMN (the area where communication is possible in the PLMN), it may initiate an Access Network (AN) release procedure. Here, the AN release procedure may be a procedure executed to release the connection between the AN and the AMF, the N3 user plane connection (the connection between the AN and the UPF), the connection between the UE and the AN, the AN resources, etc., for the UE.

[0185] Also, during the AN release procedure, if the cause value included in the N2 UE context release request sent from the AN to the AMF indicates that the release is requested because the UE with a satellite connection has moved outside the serving area of ​​the PLMN, the AMF may initiate a deregistration procedure to deregister the UE without continuing the AN release procedure.

[0186] The AMF may also verify the location of the UE during the PDU session establishment procedure.

[0187] The UE may store a list of PLMNs not allowed to operate at the present UE location. Each piece of information (also referred to as an entry) included in the list may include a PLMN ID, UE location information, and UE distance information. Here, the PLMN ID may be the PLMN ID of a PLMN that has sent a message including a 5GMM cause value indicating that operation is not allowed at the present UE location. The UE location information may be the location information of a UE that has received a message including a 5GMM cause value indicating that operation is not allowed at the present UE location. The UE distance information may be, for example, information regarding the distance between a satellite and the UE.

[0188] The UE may also delete an existing entry with the same PLMN ID before storing a new entry in the list of PLMNs that are not allowed to operate at the UE's current location. When storing a new entry in the list of PLMNs that are not allowed to operate at the UE's current location, the UE may also start a timer associated with the entry. If a lower bound timer value has been received from the network, the UE may start the timer using a timer value that is equal to or greater than the timer value. The lower bound timer value may be received by the UE from a core network (e.g., AMF or SMF) and included in a control message such as a registration reject message, a DL NAS TRANSPORT message, a non-registration request message, or a service rejection message. If the UE has not received a lower bound timer value from the network, the UE may start the timer using a timer value set based on implementation.

[0189] In addition, if the current UE location is known, the UE location information is stored in the entry for that PLMN, and the distance to the current UE location is greater than a predetermined value, the UE may connect to a PLMN that is included in the list of PLMNs that are not allowed to operate at the current UE location.

[0190] Additionally, the UE may connect to a PLMN that is included in the list of PLMNs that are not allowed to operate at the UE's current location if the timer associated with that PLMN's entry expires.

[0191] Additionally, if the connection is for emergency services, the UE may connect to a PLMN that is included in the list of PLMNs that are not allowed to operate at the UE's current location.

[0192] Additionally, the list of PLMNs that are not allowed to operate at the current UE location may contain more than two entries, and if the list of PLMNs that are not allowed to operate at the current UE location is full and a new entry is to be added, the UE may delete the oldest entry.

[0193] Additionally, the UE may delete an entry in the list of PLMNs that are not permitted to operate at the UE's current location upon successful registration or registration procedure for the PLMN stored in the entry, except in the case of registration for emergency services.

[0194] The UE may also delete an entry in the list of PLMNs that are not allowed to operate at the UE's current location if the timer associated with the entry expires.

[0195] Additionally, if the current UE location is known, the entry for that PLMN stores the UE's location information, and the distance to the current UE location is greater than a predetermined value, the UE may delete the entry in the list of PLMNs that are not allowed to operate at the current UE location.

[0196] The UE may also perform PLMN selection if it is in 5GMM-DEREGISTERED.LIMITED-SERVICE state and removes entries from the list of PLMNs that are not allowed to operate at the UE's current location.

[0197] Additionally, when the UE is powered down, the UE may maintain in non-volatile memory a list of PLMNs that are not permitted to operate in the UE's current location.

[0198] The UE may also delete the list of PLMNs that are not allowed to operate in the UE's current location if the USIM is removed.

[0199] The AMF may also have a function of determining a waiting range (also referred to as a wait range, a wait range, or a wait range) based on a network configuration. The AMF may also transmit information about and / or the wait range to the UE via a registration procedure, a configuration update procedure, a service request procedure, and / or a non-registration procedure. For example, the AMF may transmit information about and / or the wait range to the UE in a registration accept message, a registration reject message, a configuration update command, a non-registration request message, a service accept message, a service reject message, and / or a NAS message.

[0200] Furthermore, the UE may calculate a wait timer (also referred to as a wait timer) based on the wait range and / or information related to the wait range and / or information including the wait range received from the network. In other words, the wait range may indicate a range used to determine the wait timer. The wait timer may also refer to a wait timer value or a timer value to be set in a timer used in the UE. Furthermore, the network may generate a wait timer from the wait range on behalf of the UE, and transmit the wait range and / or information related to the wait range and / or information including the wait range to the UE in the control message, in which case the UE may use the received wait timer.

[0201] Furthermore, the UE may start a timer using a wait timer after communication via a satellite becomes possible after the UE has lost communication via a satellite (this is also referred to as returning to coverage from discontinuous coverage). Furthermore, the UE may not transmit control messages (e.g., NAS messages and / or RRC messages) until this timer expires. In other words, the timer using a wait timer is started after communication via a satellite becomes possible after communication via a satellite has become impossible, and may be a timer for setting a period during which the UE cannot transmit control messages.

[0202] Furthermore, a UE capable of communicating via a satellite may receive a wait range from the network during a registration procedure, a configuration update procedure, a service request procedure, and / or a deregistration procedure performed in a first PLMN via a first satellite. The UE may transmit UE capability information indicating its capability to calculate / generate a wait timer based on the wait range to the network during the same or an earlier procedure as the procedure for receiving the wait range. In other words, to determine whether the NW side is allowed to transmit the wait range, the UE may transmit UE capability information indicating whether it supports a wait range, a wait timer, and / or a timer using the wait timer. The network may then transmit the wait range only to UEs that have the capability based on the received UE capability information. After communication via the first satellite becomes unavailable, the UE may select the first PLMN when communication via a second satellite connected to the first PLMN becomes available. If the first PLMN has already been selected, the UE does not need to reselect the first PLMN. The UE may then generate a wait timer based on the wait range. The UE may start the timer using the wait timer immediately after generating the wait timer, or may start the timer using the wait timer when a predetermined time has elapsed or a predetermined condition is met. If the UE makes an emergency call while the timer is running, the UE may stop the timer and perform a registration procedure, an MM procedure, and / or an SM procedure for the emergency call. If the UE does not make an emergency call while the timer is running, the UE may perform a registration procedure, an MM procedure, and / or an SM procedure in the first PLMN after the timer expires. The above PLMN may also be read as PLMN and / or RAT. The first PLMN may be a HPLMN or a VPLMN.Furthermore, if the UE again becomes unable to communicate via a second satellite connecting to the first PLMN before the timer using the wait timer expires, the UE may stop the timer and perform PLMN selection to select another PLMN connectable via a satellite (e.g., the second PLMN or the third PLMN) and / or another PLMN connectable without a satellite (e.g., the fourth PLMN). Furthermore, if the UE again becomes unable to communicate via a satellite with the second PLMN before the timer using the wait timer expires, the UE may perform PLMN selection to select another PLMN connectable via a satellite and / or another PLMN connectable without a satellite without stopping the timer. Furthermore, if the UE again becomes unable to communicate via a satellite with the second PLMN before the timer using the wait timer expires, the UE may perform PLMN selection to select another PLMN connectable via a satellite and / or another PLMN connectable without a satellite, and then stop the timer. Furthermore, after the network transmits a wait range to the UE in a registration procedure performed in a certain PLMN, the network may transmit the updated wait range to the UE in a registration procedure and / or configuration update procedure performed in the same PLMN, thereby updating the wait range and / or the wait timer and / or the timer using the wait timer. In other words, after the UE receives a wait range from the network in a registration procedure performed in a certain PLMN, the UE may receive the updated wait range from the network in a registration procedure and / or configuration update procedure performed in the same PLMN, thereby updating the wait range and / or the wait timer and / or the timer using the wait timer.

[0203] Furthermore, a UE capable of communicating via a satellite may receive a wait range from the network during a registration procedure, a configuration update procedure, a service request procedure, and / or a non-registration procedure performed in a first PLMN via a first satellite. The UE may transmit UE capability information indicating its capability to calculate / generate a wait timer based on the wait range to the network during the same or an earlier procedure as the procedure for receiving the wait range. In other words, to determine whether the NW side is allowed to transmit the wait range, the UE may transmit UE capability information indicating whether it supports a wait range, a wait timer, and / or a timer using the wait timer. The network may then transmit the wait range only to UEs with that capability based on the received UE capability information. After communication via the first satellite becomes unavailable, if communication via a second satellite connected to the second PLMN becomes available, the UE may select the second PLMN. The UE may then generate a wait timer based on the wait range. The UE may generate the wait timer and immediately start the timer using the wait timer, or may start the timer using the wait timer after a predetermined time or when a predetermined condition is met. If the UE makes an emergency call while the timer is running, the UE may stop the timer and perform a registration procedure, an MM procedure, and / or an SM procedure for the emergency call. If the UE does not make an emergency call while the timer is running, the UE may perform a registration procedure, an MM procedure, and / or an SM procedure in the second PLMN after the timer expires. Here, the first PLMN may be a HPLMN or a VPLMN. The second PLMN may be a PLMN different from the first PLMN. The second PLMN may be an equivalent PLMN. The second PLMN may be a PLMN included in a forbidden PLMN list.Furthermore, the above-mentioned PLMN may be read as PLMN and / or RAT. Furthermore, if the UE again becomes unable to communicate with the second PLMN via a second satellite before the timer using the wait timer expires, the UE may stop the timer and perform PLMN selection to select another PLMN connectable via a satellite (e.g., the first PLMN or the third PLMN) and / or another PLMN connectable without a satellite (e.g., the fourth PLMN). Furthermore, if the UE again becomes unable to communicate with the second PLMN via a satellite before the timer using the wait timer expires, the UE may perform PLMN selection to select another PLMN connectable via a satellite and / or another PLMN connectable without a satellite without stopping the timer. Furthermore, if the UE again becomes unable to communicate with the second PLMN via a satellite before the timer using the wait timer expires, the UE may perform PLMN selection to select another PLMN connectable via a satellite and / or another PLMN connectable without a satellite, and then stop the timer. Furthermore, after the network transmits a wait range to the UE in a registration procedure performed in a certain PLMN, the network may transmit the updated wait range to the UE in a registration procedure and / or configuration update procedure performed in the same PLMN, thereby updating the wait range and / or the wait timer and / or the timer using the wait timer. In other words, after the UE receives a wait range from the network in a registration procedure performed in a certain PLMN, the UE may receive the updated wait range from the network in a registration procedure and / or configuration update procedure performed in the same PLMN, thereby updating the wait range and / or the wait timer and / or the timer using the wait timer.Furthermore, after the network transmits a wait range to the UE in a registration procedure performed in a PLMN, the network may transmit the updated wait range to the UE in a registration procedure and / or configuration update procedure performed in a different PLMN, thereby updating the wait range and / or the wait timer and / or the timer using the wait timer. In other words, after the UE receives a wait range from the network in a registration procedure performed in a PLMN, the UE may receive the updated wait range from the network in a registration procedure and / or configuration update procedure performed in a different PLMN, thereby updating the wait range and / or the wait timer and / or the timer using the wait timer.

[0204] Furthermore, when the UE waits until coverage of the same RAT and / or PLMN that was previously used for satellite-based communication is restored (i.e., satellite-based communication using the same RAT and / or PLMN becomes possible) because satellite-based communication has been unavailable (this is also referred to as discontinuous coverage), the UE may calculate the wait timer based on the wait range and / or information related to the wait range and / or information including the wait range received from the network. This wait timer calculation may be performed after satellite-based communication has been unavailable and before satellite-based communication becomes possible. Furthermore, the timer using the wait timer may be started after satellite-based communication has been unavailable and before satellite-based communication becomes possible, or may be started after satellite-based communication has been unavailable and after satellite-based communication becomes possible. In other words, if the timer using the wait timer is started after satellite-based communication for the same RAT and / or PLMN becomes possible after satellite-based communication has been unavailable, the timer using the wait timer may be a timer for setting a period during which the UE cannot transmit a control message. In addition, if the timer using the wait timer is a timer that is started after communication via a satellite is no longer possible and before communication via a satellite for the same RAT and / or PLMN is again possible, the timer using the wait timer may have the function of a timer for setting a period during which the UE cannot transmit control messages, and / or the function of a timer for specifying a period during which coverage for the same RAN and / or PLMN is restored.

[0205] Furthermore, the calculation of this wait timer may be performed after communication via a satellite becomes unavailable and after communication via a satellite becomes available. Furthermore, the start of the timer using this wait timer may be performed after communication via a satellite becomes unavailable and after communication via a satellite becomes available. In other words, the timer using the wait timer may be a timer that is started after communication via a satellite for the same RAT and / or PLMN becomes available after communication via a satellite becomes unavailable, and may be a timer for setting a period during which the UE cannot transmit a control message.

[0206] Furthermore, when a UE is communicating with a core network via a satellite using a certain PLMN (here, PLMN A) and a certain RAT (e.g., a radio access technology such as 3G, 4G, or 5G, here, RAT A), the core network may generate a wait range and notify the UE, and the UE may receive and understand the wait range. The UE may then start a timer using the wait timer after it becomes able to communicate via a satellite using the same RAT (RAT A) and the same PLMN (PLMN A) after it loses communication via a satellite (this is also referred to as returning to coverage from discontinuous coverage). In other words, the wait range, the wait timer, and the timer using the wait timer may apply to the same RAT and the same PLMN. In other words, the wait range, the wait timer, and the timer using the wait timer may only apply to the same PLMN. Here, the UE may generate a wait timer from the wait range after coverage is restored or immediately after receiving the wait range (i.e., before it loses communication via a satellite).

[0207] Furthermore, when a UE is communicating with a core network via a satellite using a certain PLMN (here, PLMN A) and a certain RAT (here, RAN A), the core network may generate a wait range and notify the UE, and the UE may receive and understand the wait range. After the UE subsequently loses communication via the satellite, it may start a timer using the wait timer after it becomes able to communicate via the satellite using a different RAT (RAT B) and the same PLMN (PLMN A) (this is also referred to as returning to coverage from discontinuous coverage). In other words, the wait range, the wait timer, and the timer using the wait timer may be applied to different RATs and the same PLMN. In yet another way, the wait range, the wait timer, and the timer using the wait timer may be applied to the same or different RATs and the same PLMN. In yet another way, the wait range, the wait timer, and the timer using the wait timer may be applied to the same PLMN and may be independent of the RAT. Here, the UE may generate a wait timer from the wait range after coverage is restored, or may generate a wait timer immediately after receiving the wait range (i.e., before communication via the satellite becomes impossible).

[0208] Also, when a UE is communicating with a core network via a satellite using a certain PLMN (here, PLMN A) and a certain RAT (here, RAN A), the core network may generate a wait range and notify the UE, and the UE may receive and understand the wait range. After the UE subsequently loses communication via the satellite, it may start a timer using the wait timer after it becomes able to communicate via the satellite using the same RAT (RAT A) and a different PLMN (PLMN B) (this is also referred to as returning from discontinuous coverage to coverage). In other words, the wait range, the wait timer, and the timer using the wait timer may apply to the same RAT and different PLMNs. In yet another way, the wait range, the wait timer, and the timer using the wait timer may apply only to different PLMNs. Alternatively, the wait range, the wait timer, and the timer using the wait timer may apply to all PLMNs. Here, the UE may generate a wait timer from the wait range after coverage is restored, or may generate a wait timer immediately after receiving the wait range (i.e., before communication via the satellite becomes impossible).

[0209] Also, when a UE is communicating with a core network via a satellite using a certain PLMN (here, PLMN A) and a certain RAT (here, RAN A), the core network may generate a wait range and notify the UE, and the UE may receive and understand the wait range. After the UE subsequently loses communication via the satellite, it may start a timer using the wait timer after it becomes able to communicate via the satellite using a different RAT (RAT B) and a different PLMN (PLMN B) (this is also referred to as returning from discontinuous coverage to coverage). In other words, the wait range, the wait timer, and the timer using the wait timer may apply to different RATs and different PLMNs. In yet another way, the wait range, the wait timer, and the timer using the wait timer may apply only to different PLMNs. Alternatively, the wait range, the wait timer, and the timer using the wait timer may apply to all PLMNs. Here, the UE may generate a wait timer from the wait range after coverage is restored, or may generate a wait timer immediately after receiving the wait range (i.e., before communication via the satellite becomes impossible).

[0210] Furthermore, when an emergency call is made while a timer using a wait timer is operating (i.e., before expiration), the UE may perform an MM procedure and / or an SM procedure with the same PLMN even before the timer expires. In other words, when an emergency call is made while a timer using a wait timer is operating (i.e., before expiration), the UE may transmit and receive control messages (e.g., NAS messages and / or RRC messages) with the same PLMN even before the timer expires. In this case, the UE may stop the timer before performing the MM procedure and / or the SM procedure. However, the UE may stop the timer while performing the MM procedure and / or the SM procedure, or may stop the timer after performing the MM procedure and / or the SM procedure. Furthermore, in the MM procedure and / or the SM procedure, the control message transmitted by the UE may include information indicating that the emergency call is via a satellite. For example, when the MM procedure is a registration procedure, the 5GS registration type IE included in the registration request message transmitted by the UE may be set to emergency registration. Also, in the MM procedure and / or SM procedure, if the control message received from the UE includes information indicating that it is an emergency call via satellite, the network (e.g., AMF and / or SMF) may send a control message to the UE including information indicating that the emergency call via satellite is allowed.

[0211] Furthermore, when an emergency call is made while a timer using a wait timer is operating (i.e., before expiration), the UE may perform an MM procedure and / or an SM procedure for the same PLMN and / or the same or a different RAT even before the timer expires. In other words, when an emergency call is made while a timer using a wait timer is operating (i.e., before expiration), the UE may transmit or receive a control message (e.g., an NAS message and / or an RRC message) for the same PLMN and / or the same or a different RAT even before the timer expires. In this case, the UE may stop the timer before performing the MM procedure and / or the SM procedure. However, the UE may stop the timer while performing the MM procedure and / or the SM procedure, or may stop the timer after performing the MM procedure and / or the SM procedure. Furthermore, in the MM procedure and / or the SM procedure, the control message transmitted by the UE may include information indicating that the emergency call is made via a satellite. For example, if the MM procedure is a registration procedure, the 5GS registration type IE included in the registration request message sent by the UE may be set to emergency registration. Also, if the control message received from the UE in the MM procedure and / or the SM procedure includes information indicating that the call is an emergency call via a satellite, the network (e.g., AMF and / or SMF) may send a control message including information indicating that the call is permitted via a satellite to the UE.

[0212] Furthermore, when an emergency call is made while a timer using a wait timer is running (i.e., before it expires), the UE may select another PLMN and perform an MM procedure and / or an SM procedure with the selected PLMN even before the timer expires. In other words, when an emergency call is made while a timer using a wait timer is running (i.e., before it expires), the UE may select another PLMN and transmit / receive a control message (e.g., an NAS message and / or an RRC message) to / from the selected PLMN even before the timer expires. Here, the other PLMN may include a PLMN included in the forbidden PLMN list or an equivalent PLMN to the HPLMN or RPLMN. This operation may also be performed, for example, when the already selected PLMN and / or the network slice in that PLMN is congested. In this case, the UE may stop the timer and then perform an MM procedure and / or an SM procedure. However, the UE may stop the timer while executing the MM procedure and / or the SM procedure, or may stop the timer after executing the MM procedure and / or the SM procedure. Furthermore, in the MM procedure and / or the SM procedure, the control message transmitted by the UE may include information indicating that the call is an emergency call via a satellite. For example, if the MM procedure is a registration procedure, the 5GS registration type IE included in the registration request message transmitted by the UE may be set to emergency registration. Furthermore, in the MM procedure and / or the SM procedure, if the control message received from the UE includes information indicating that the call is an emergency call via a satellite, the network (e.g., AMF and / or SMF) may transmit a control message to the UE including information indicating that the call is allowed via a satellite.

[0213] Furthermore, when an emergency call is made while a timer using a wait timer is operating (i.e., before expiration), the UE may select another PLMN and / or the same or a different RAT and perform an MM procedure and / or an SM procedure with the selected PLMN and RAT even before the timer expires. In other words, when an emergency call is made while a timer using a wait timer is operating (i.e., before expiration), the UE may select another PLMN and / or the same or a different RAT and transmit / receive control messages (e.g., NAS messages and / or RRC messages) with the selected PLMN and RAT even before the timer expires. Here, the other PLMN may include PLMNs included in the forbidden PLMN list and PLMNs equivalent to the HPLMN or RPLMN. This operation may also be performed, for example, when the already selected PLMN and / or the network slice in that PLMN and / or the RAT are congested. In this case, the UE may stop the timer and then perform an MM procedure and / or an SM procedure. However, the UE may stop the timer while executing the MM procedure and / or the SM procedure, or may stop the timer after executing the MM procedure and / or the SM procedure. Furthermore, in the MM procedure and / or the SM procedure, the control message transmitted by the UE may include information indicating that the call is an emergency call via a satellite. For example, if the MM procedure is a registration procedure, the 5GS registration type IE included in the registration request message transmitted by the UE may be set to emergency registration. Furthermore, in the MM procedure and / or the SM procedure, if the control message received from the UE includes information indicating that the call is an emergency call via a satellite, the network (e.g., AMF and / or SMF) may transmit a control message to the UE including information indicating that the call is allowed via a satellite.

[0214] The above may be applied to an NPN (SNPN and / or PNI-NPN). That is, the present embodiment may be applied to an NPN by replacing PLMN with SNPN.

[0215] 4. Variations

[0216] A program running on an apparatus according to one 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 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 another storage device system.

[0217] A program for implementing the functions of an embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. The program may be read into a computer system and executed. The term "computer system" as used herein refers to a computer system built into a device, including hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may also refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium.

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

[0219] The present invention is not limited to the above-described embodiment. Although one example of a device has been described in the embodiment, one aspect of the present invention is not limited to this and can be applied to terminal devices or communication devices of stationary or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0220] 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 modifications and the like are also included within the scope of the gist of the present invention. Furthermore, various modifications of one aspect of the present invention are possible 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 substituted with elements that achieve the same effect are also included. [Explanation of symbols]

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

Claims

1. A UE (User Equipment) including a transceiver unit and a control unit, The transceiver unit receives first information applicable to a first PLMN (Public Land Mobile Network) and a first RAT (Radio Access Technology) from a network in a registration accept message or a configuration update command; The first information is information indicating a range used to determine a value of a wait timer to be started in the UE when the UE returns from outside coverage of discontinuous coverage to within coverage, When the UE returns from outside the discontinuous coverage to within the coverage, the control unit starts the waiting timer based on the first information; When an emergency call is made, the control unit stops the waiting timer that is running, and the transceiver unit transmits a NAS (Non-Access-Stratum) message. A UE characterized by:

2. The transceiver does not transmit a NAS message to the first PLMN and the first RAT while the waiting timer is operating.

2. The UE of claim 1 .

3. A communication control method executed by a UE (User Equipment), comprising: receiving, from the network, first information applicable to a first Public Land Mobile Network (PLMN) and a first Radio Access Technology (RAT) in a registration accept message or a configuration update command; The first information is information indicating a range used to determine a value of a wait timer to be started in the UE when the UE returns from outside coverage of discontinuous coverage to within coverage, When the UE returns from outside the discontinuous coverage to within the coverage, starting the waiting timer based on the first information; When an emergency call is made, the waiting timer is stopped and a NAS (Non-Access-Stratum) message is transmitted. A communication control method comprising:

Images