UE (user equipment)

Abstract

To solve a problem in which it is not clear what behavior UE is to have when its registration is rejected by the NPN for localized services.SOLUTION: User equipment (UE) sends a registration request message including a first identity and a second identity, the first identity is information for identifying an SNPN, and the second identity is information indicating support for a hosting network, and receives a registration rejection message including a first reason value, the first reason value is a reason value indicating that the UE is not authorized for the hosting network, and the UE stores the first identity in a prohibited hosting network list on the basis of the first reason value when the registration request message is for localized service in the SNPN.SELECTED DRAWING: Figure 6

Description

[Technical Field]

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

[0002] The 3GPP (3rd Generation Partnership Project) is studying the system architecture of 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 4). In recent years, there has been active discussion about how to use local services in NPNs (Non-Public Networks) (see Non-Patent Document 5). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 23.501 V17.5.0 (2022-06); 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.5.0 (2022-06); 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.7.1 (2022-06); 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 TS 23.122 V17.7.1 (2022-06); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode (Release 17) [Non-Patent Document 5] 3GPP TR 23.700-08 V1.0.0 (2022-05); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhanced support of Non-Public Networks; Phase 2 (Release 18) Summary of the Invention [Problem to be solved by the invention]

[0004] In 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered to provide a wide variety of services. 5GS also considers providing a private network, such as NPN (Non-Public Network), which is defined separately from PLMN (Public Land Mobile Network), which is a public network, and functions to realize a private network.

[0005] Currently, it is not clear how a UE behaves when its registration is rejected by an NPN for local services. Specifically, an NPN for local services may be an SNPN or a PNI-NPN. In the current specification, there are rejection reason values ​​corresponding to SNPNs or PNI-NPNs, but there are no rejection reason values ​​corresponding to NPNs for local services.

[0006] In view of the above, one aspect of the present invention is to clarify the behavior of a UE when registration is rejected by an NPN for localized services. [Means for solving the problem]

[0007] A User Equipment (UE) according to one embodiment of the present invention comprises a transceiver unit and a controller, wherein the transceiver unit transmits a registration request message including first identification information and second identification information, the first identification information being information for identifying an SNPN, the second identification information being information indicating support for a hosting network, and receives a registration rejection message including a first reason value, the first reason value being a reason value indicating that the UE is not authorized for the hosting network, and the controller stores the first identification information in a prohibited hosting network list based on the first reason value if the registration request message is for a local service in the SNPN.

[0008] According to one aspect of the present invention, there is provided a User Equipment (UE) comprising a transceiver unit and a controller, wherein the transceiver unit transmits a registration request message including a first identification and a second identification, wherein the first identification is information for identifying an SNPN and the second identification is information indicating that the UE supports a hosting network, and receives a registration rejection message including a first reason value or a second reason value, wherein the first reason value is a reason value indicating that the UE is temporarily not authorized for the SNPN and the second reason value is a reason value indicating that the UE is permanently not authorized for the SNPN, and based on the first reason value, the controller stores the first identification in a list of SNPNs temporarily prohibited for localized service if the registration request message is for localized service at the SNPN, and based on the second reason value, the controller stores the first identification in a list of SNPNs permanently prohibited for localized service if the registration request message is for localized service at the SNPN.

[0009] A User Equipment (UE) of one embodiment of the present invention comprises a transceiver unit and a control unit, wherein the transceiver unit transmits a registration request message including first identification information and second identification information, wherein the first identification information is information indicating whether a Closed Access Group (CAG) is supported, and the second identification information is information indicating that a hosting network is supported, and receives a registration rejection message including a first reason value and third identification information, wherein the first reason value is a reason value indicating that authorization for the hosting network has not been granted, and the third identification information is a list including CAG IDs, and the control unit replaces the third identification information stored in the UE with the received third identification information based on the first reason value if the registration request message is for a local service in a PNI-NPN. [Effects of the Invention]

[0010] According to one aspect of the present invention, a UE can specify its behavior when registration is rejected from an NPN for localized services. [Brief explanation of the drawings]

[0011] [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. [Figure 6] FIG. 10 is a diagram illustrating a registration procedure. [Figure 7] FIG. 10 is a diagram illustrating a UE-initiated deregistration procedure. [Figure 8] FIG. 1 illustrates a network-initiated unregistration procedure. [Figure 9] A diagram showing a UE-initiated NAS transport procedure. [Figure 10] FIG. 1 is a diagram illustrating a network-initiated NAS transport procedure. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

[0019] 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, and may be a terminal device that can connect to both EPS and 5GS. A UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Note that a UE may be referred to as a user device or a terminal device.

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

[0021] 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 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) used in the 4G system EPS. Furthermore, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

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

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

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

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

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

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

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

[0029] 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 referred to as the DN, and the DN may be referred to as the PDN.

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

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

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

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

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

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

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

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

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

[0039] Furthermore, the UPF 130 may be the same device as the UPF_A 235. Note that the UPF 130 and the UPF_A 235 may be written with the symbols omitted, such as UPF.

[0040] [2. Configuration of each device] Next, the configuration of each device (UE, and / or access network device, and / or core network device) used in each embodiment will be described with reference to the drawings. Each device may be configured as physical hardware, 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.

[0041] Note that each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, 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. Furthermore, each memory unit can store not only information that was originally set at the time of shipment, but also various information transmitted and received between 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). Furthermore, each memory unit can store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described below. Furthermore, each memory unit may 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 5GS and / or devices / functions included in EPS. At this time, not only those transmitted and received via the N26 interface but also those transmitted and received without going through the N26 interface can be stored.

[0042] [2.1. UE Device Configuration] 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.

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

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

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

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

[0047] [2.2. gNB device configuration] 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.

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

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

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

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

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

[0053] [2.3. AMF device configuration] 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0067] [2.4. SMF device configuration] 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 necessary.

[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 send and receive user data and / or control information between the AMF, and / or UPF, and / or PCF, and / or UDM using the network connection unit _B720.

[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] [2.5. UPF device configuration] 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.

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

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

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

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

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

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

[0080] The user plane 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 or a PDU session. Furthermore, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface, and / or the S1-U interface, and / or the S5 interface, and / or the S8 interface, and / or the SGi interface. Furthermore, in the case of 5GS, the user plane may be transmitted and received via 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.

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

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

[0083] 2.6. Description of Other Devices and / or Functions Next, other devices and / or functions will be described.

[0084] A network refers to at least a portion of an access network _B, a core network _B, and a DN. One or more devices included in at least a portion of an access network _B, a core network _B, and a DN may also 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, 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. A network may also be referred to as an NW.

[0085] Furthermore, the network may refer to a PLMN (Public Land Mobile Network) or a later-described NPN (Non-Public Network). Furthermore, network selection may refer to a PLMN selection or an SNPN selection.

[0086] An NWDAF (Network Data Analytics Function) may be an NF that has the function of collecting data from NFs and application functions (also referred to as AFs).

[0087] A PCF (Policy Control Function) may be an NF that has the function of determining policies for controlling network behavior.

[0088] An NRF (Network Repository Function) may be an NF that has a service discovery function. The NRF may be an NF that has a function to provide information about the discovered NF when it receives a discovery request for another NF from another NF.

[0089] A UDM (Unified Data Management) may be an NF that has authentication credential processing functions, user identification processing functions, access authentication functions, registration / mobility management functions, subscription management functions, etc.

[0090] An SM (Session Management) message may be a NAS message used in a procedure for SM. The SM message may also be referred to as a NAS (Non-Access-Stratum) SM message. The SM message 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.

[0091] 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 of which may be initiated by the UE or the network.

[0092] An MM (Mobility management) message may be a NAS message used in procedures for MM. The MM message may also be referred to as a NAS MM message. The MM message may be a control message transmitted and received between the UE_A10 and the AMF_A240. Furthermore, the MM message may include a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, etc.

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

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

[0095] A non-5GS service may be a service other than a 5GS service, and may include an EPS service and / or a non-EPS service.

[0096] The S1 mode is a mode in which the UE_A10 is permitted to access the EPC via the E-UTRAN. In other words, the S1 mode may be a mode in which messages are sent and received using the S1 interface. The S1 interface may be composed of an S1-MME interface and an S1-U interface.

[0097] The N1 mode is a mode in which the UE_A10 is permitted to access the 5G access network via the 5G access network. In other words, the N1 mode may be a mode in which messages are sent and received using the N1 interface.

[0098] An APN (Access Point Name) may be identification information that identifies a core network and / or an external network such as a PDN. Furthermore, the APN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 that connects the core network A_90.

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

[0100] A PDU (Protocol Data Unit) session can be defined as an association between a DN providing a PDU connectivity service and a UE, but it 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. Note that each device (UE, and / or access network device, and / or core network device) may manage one or more pieces of identification information associated with a PDU session. Note that this identification information may include one or more of a DNN, a QoS rule, a PDU session type, an application identification information, an NSI identification information, an access network identification information, and an SSC mode, or may further include other information. Furthermore, when multiple PDU sessions are established, the identification information associated with each PDU session may be the same or different.

[0101] 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 a PGW / UPF that connects the core network B190. Furthermore, the DNN may be equivalent to an APN (Access Point Name).

[0102] The PDU (Protocol 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 sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Ethernet may also indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data will be sent 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.

[0103] 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 Subscription Identity) may be a Home PLMN (HPLMN). Furthermore, the UE may store an Equivalent PLMN list in its USIM to identify one or more Equivalent PLMNs (EPLMNs). A PLMN different from the HPLMN and / or EPLMN may be a Visited PLMN (VPLMN). A PLMN to which the UE has successfully registered may be a Registered PLMN (RPLMN).

[0104] Furthermore, the registered PLMN refers to the PLMN to which the UE is registered.

[0105] An equivalent PLMN is a PLMN that is treated by the network as if it were the same PLMN as any other PLMN. For example, an equivalent PLMN may be one or more PLMNs that are treated the same as the registration PLMN.

[0106] PLMN selection may be a procedure by which a UE selects a PLMN, where the PLMN selection may be performed when the UE connects to the PLMN, where the PLMN selection may be referred to as a PLMN selection process or a PLMN selection procedure.

[0107] Here, a UE not operating in the SNPN access mode or the SNPN access operation mode may perform PLMN selection. Also, a UE operating in the SNPN access mode or the SNPN access operation mode may not perform PLMN selection. Also, PLMN selection may be performed without registration. In other words, PLMN selection may be performed when the UE has not completed registration with the network. PLMN selection may include an automatic PLMN selection mode and a manual PLMN selection mode. Here, PLMN selection may refer to either the automatic PLMN selection mode or the manual PLMN selection mode.

[0108] 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. Note that 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 may be a routing area, a location area, or anything similar. Hereinafter, a tracking area may be a TA (Tracking Area). A tracking area may be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking area code) and a PLMN.

[0109] A registration area is a collection 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.

[0110] The UE ID is information for identifying a UE. For example, the UE ID may be SUCI, SUPI, IMSI, GUTI, 5G-GUTI, IMEI, IMEISV, TMSI, or 5G-S-TMSI. 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.

[0111] A Subscription Concealed Identifier (SUCI) may be a privacy preserving identifier including a concealed SUPI. The SUCI may be composed of a SUPI Type, a Home Network Identifier, a Routing Indicator, a Protection Scheme Id, a Home Network Public Key Identifier, and a Scheme Output.

[0112] A SUPI (Subscription Permanent Identifier) ​​may be a globally unique identifier assigned to each subscriber in a 5G system. The SUPI may be defined as a SUPI type and an IMSI, NSI, GCI (Global Cable Identifier), or GLI (Global Line Identifier). The SUPI type may indicate an IMSI, an NSI, a GCI, or a GLI. That is, when the SUPI type indicates an IMSI, the SUPI may be composed of a SUPI type indicating the IMSI and the IMSI. Similarly, when the SUPI type indicates an NSI, the SUPI may be composed of a SUPI type indicating the NSI and the NSI. When the SUPI type indicates a GCI, the SUPI may be composed of a SUPI type indicating the GCI and the GCI. When the SUPI type indicates a GLI, the SUPI may be composed of a SUPI type indicating the GLI and the GLI.

[0113] An International Mobile Subscription Identity (IMSI) may be composed of a Mobile Country Code (MCC), a Mobile Network Code (MNC), and a Mobile Subscriber Identification Number (MSIN).

[0114] 5G-GUTI (5G Globally Unique Temporary Identifier) ​​may be information for providing an unambiguous UE identifier that does not reveal the UE or the user's permanent identity. 5G-GUTI may also be information that can identify the AMF and the network. 5G-GUTI may also be information used by the network and the UE to establish the UE's identity. 5G-GUTI may be composed of two elements: one that identifies the AMF that assigned the 5G-GUTI, and one that uniquely identifies the UE within the AMF that assigned the 5G-GUTI. The former may be GUAMI (Globally Unique AMF Identifier), and the latter may be 5G-TMSI (5G-Temporary Mobile Subscriber Identity). That is, 5G-GUTI may be composed of GUAMI and 5G-TMSI.

[0115] The IMEI (International Mobile station Equipment Identity) may be composed of a TAC (Type Allocation Code), an SNR (Serial Number), and a CD (Check Digit) / SD (Spare Digit).

[0116] The IMEISV (International Mobile station Equipment Identity and Software Version number) may be composed of a TAC (Type Allocation Code), an SNR (Serial Number), and an SVN (Software Version Number).

[0117] The 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​may be an abbreviation of the 5G-GUTI. The 5G-S-TMSI may enable more efficient radio signaling procedures, such as paging (also referred to as a paging procedure) and service requests (also referred to as a service request procedure). For paging, the UE may be paged using the 5G-S-TMSI. The 5G-S-TMSI may consist of an AMF Set ID, an AMF Pointer, and the 5G-TMSI.

[0118] The MAC address (Media Access Control address) may be a hardware address of a device connected to the shared media, or may be a unique identification number assigned to a UE or a network device.

[0119] An EUI-64 (IEEE Extended Unique Identifier) ​​may be a 64-bit identifier standardized by the IEEE, and may be used when automatically generating IPv6 addresses.

[0120] A PEI (Permanent Equipment Identifier) ​​may be information for identifying a UE. The PEI may be defined as a PEI type and an IMEI, IMEISV, a MAC address, or an EUI-64. Here, the PEI type may indicate an IMEI, IMEISV, a MAC address, or an EUI-64. That is, when the PEI type indicates an IMEI, the PEI may be composed of a PEI type indicating an IMEI and an IMEISV. Similarly, when the PEI type indicates an IMEISV, the PEI may be composed of a PEI type indicating an IMEISV and an IMEISV. When the PEI type indicates a MAC address, the PEI may be composed of a PEI type indicating a MAC address and an IMEISV. When the PEI type indicates an EUI-64, the PEI may be composed of a PEI type indicating an EUI-64 and an EUI-64.

[0121] The 5GS mobile identity may be an IE for providing the SUCI, 5G-GUTI, IMEI, IMEISV, 5G-S-TMSI, MAC address, or EUI-64, and may also be referred to as a 5GS mobile identity information element (IE).

[0122] An NPN (Non-Public Network) is a private network used by specific users for specific purposes. There are two types of NPNs: SNPN (Stand-alone Non-Public Network) and PNI-NPN (Public Network Integrated NPN). Note that the term NPN may refer to either an SNPN or a PNI-NPN, or both.

[0123] An SNPN is a network operated by an NPN operator and is not affected by functions provided by a PLMN. In other words, an SNPN is a dedicated network for NPNs, independent of publicly available PLMNs. An SNPN may be a network identified by an SNPN identity (SNPN ID). The SNPN ID may be a combination of a PLMN ID and a Network Identifier (NID). The PLMN ID used in the SNPN ID may be information reserved for private networks. For example, the MCC included in the PLMN ID may be 999. When a UE is registered with an SNPN, the registered SNPN may be referred to as a registered SNPN or an RSNPN (registered SNPN).

[0124] The NID is information that identifies a network. The SNPN may be identified by a combination of the PLMN ID and the NID. The NID may be unique within the SNPN or may be unique worldwide.

[0125] The PNI-NPN is a network realized using the functional units of a PLMN. In other words, the PNI-NPN is an NPN virtually realized within a PLMN. Furthermore, the PNI-NPN is an NPN that can be created via a PLMN. The PNI-NPN may be realized using the function of a network slice. Specifically, the PNI-NPN may be a network that can be realized by using a network slice allocated for the NPN. In this case, the PNI-NPN may be identified by an S-NSSAI or by a combination of the S-NSSAI and a CAG ID. Furthermore, the PNI-NPN may be realized using a DN. Specifically, the PNI-NPN may be a network that can be realized by using a DN for the NPN. In this case, the PNI-NPN may be identified by a DNN or by a combination of the DNN and a CAG ID.

[0126] A CAG (Closed Access Group) is a group used to realize PNI-NPN. A CAG may be a group identified by a CAG ID. A CAG may be used to prevent unauthorized UEs from attempting to access a network slice allocated for an NPN.

[0127] The CAG ID is information that identifies a CAG within a PLMN, and is a unique identifier within the PLMN.

[0128] An SNPN-enabled UE may be a UE that can use an SNPN. The SNPN-enabled UE may store at least one piece of information related to the SNPN. In other words, the configuration information of the SNPN-enabled UE may include information indicating that the SNPN is available. Furthermore, the SNPN-enabled UE may support an SNPN access mode or an SNPN access operation mode. In other words, the SNPN-enabled UE may operate in the SNPN access mode or the SNPN access operation mode.

[0129] The SNPN access mode may be a mode in which a UE selects an SNPN. The SNPN access mode may also be a mode in which a UE is registered with an SNPN. Furthermore, the SNPN access mode may also be a mode in which a UE is connected to an SNPN. In other words, a UE operating in the SNPN access mode may select only an SNPN during network selection. More specifically, a UE operating in the SNPN access mode may select only an SNPN via the Uu interface during network selection. In other words, a UE operating in the SNPN access mode may select an SNPN without selecting a PLMN during network selection. Here, a UE operating in the SNPN access mode may be referred to as a UE in SNPN access mode. Furthermore, a UE in the SNPN access mode may be an SNPN-enabled UE.

[0130] The SNPN access operation mode is a mode of connecting to the SNPN via the SNPN access mode or non-3GPP access. Here, "non-3GPP access" in the SNPN may refer to a case where the UE is connected to the SNPN via a PLMN. Furthermore, when the UE operates in the SNPN access mode, it may operate in the SNPN access operation mode. Furthermore, when the UE does not operate in the SNPN access mode, it does not have to operate in the SNPN access operation mode. Furthermore, a UE in the SNPN access mode may be a UE in the SNPN access operation mode. Note that the SNPN access operation mode may be read as the SNPN access mode.

[0131] SNPN selection may be a procedure by which a UE selects an SNPN. SNPN selection may also be a procedure performed when a UE connects to an SNPN. SNPN selection may also be referred to as an SNPN selection process or an SNPN selection procedure. SNPN selection may also be a process by which a UE selects an SNPN. SNPN selection may also be a process performed when a UE connects to an SNPN.

[0132] Here, a UE operating in an SNPN access mode or an SNPN access operation mode may perform SNPN selection. A UE not operating in an SNPN access mode or an SNPN access operation mode may not perform SNPN selection. Also, SNPN selection may include an automatic SNPN selection mode and a manual SNPN selection mode. Also, SNPN selection may be performed without registration. In other words, SNPN selection may be performed when the UE has not completed registration with the network. Here, SNPN selection may refer to either the automatic SNPN selection mode or the manual SNPN selection mode.

[0133] An equivalent SNPN (equivalent PLMN) may be an SNPN that is treated as if it were the same SNPN as any SNPN. For example, an equivalent SNPN may be one or more SNPNs that are treated as if it were the same SNPN as the registration SNPN. Furthermore, an equivalent SNPN may be a PLMN that is treated as if it were the same SNPN as any SNPN. For example, an equivalent SNPN may be one or more PLMNs that are treated as if it were the same SNPN as the registration SNPN.

[0134] Furthermore, the equivalent SNPN may be one or more SNPNs or PLMNs identified by the same PLMN ID as any SNPN. For example, the equivalent SNPN may be one or more SNPNs or PLMNs identified by the same PLMN ID as the registration SNPN. Furthermore, the equivalent SNPN may be a PLMN identified by the same PLMN ID as the registration SNPN, and an equivalent PLMN of said PLMN.

[0135] SOR is an abbreviation for Steering of Roaming, and refers to a method or technology for encouraging a UE to roam to a network that is a preferred roaming destination (or a recommended roaming destination) indicated by an HPLMN.

[0136] SOR-CMCI (Steering of roaming connected mode control information) is HPLMN information for controlling the timing of transition from 5GMM connected mode to 5GMM disconnected mode in order for the UE to perform SOR. SOR-CMCI may be included in SOR information and / or an SOR transparent container, or may be included in other information elements and transmitted / received.

[0137] Furthermore, the SOR-CMCI may be information that enables a network such as an HPLMN to control the timing at which a UE in connected mode transitions to disconnected mode for SOR. The SOR-CMCI may be information based on an operator policy and / or a HPLMN policy. The SOR-CMCI may be information set in each device or may be information notified from the NW to the UE.

[0138] In addition, the SOR-CMCI may be information provided by a Steering of Roaming application function (SOR-AF). In addition, the SOR-CMCI may be information provided to the UE by the SOR-AF via the UDM and the AMF.

[0139] Alternatively, the SOR-CMCI may be included in a secured packet, or may be included in the SOR information.

[0140] Additionally, the SOR-CMCI may be configured with one or more SOR-CMCI rules.

[0141] The SOR-CMCI rule may be configured with one piece of criteria information and one first timer value. Furthermore, the criteria information and the first timer value may be associated with each other. Here, the criteria information may be referred to as a criterion.

[0142] Here, the criterion information may be configured as a criterion belonging to a PDU session (PDU session attribute type criterion), and / or a criterion relating to a service type (service type criterion), and / or a SOR security check criterion, and / or a criterion belonging to all types (match all type criterion). The criterion information may also be configured as a criterion relating to a local service.

[0143] Here, the criteria for the local service may be the criteria when the local service is used, or may be the criteria used when connecting to the hosting network, or may simply be referred to as the local service.

[0144] Furthermore, the criteria belonging to a PDU session may be criteria information for identifying the corresponding PDU session. Specifically, the criteria belonging to a PDU session may be configured as the DNN of the PDU session, or the S-NSSAI STT of the PDU session, or the S-NSSAI STT and SD of the PDU session. Furthermore, the criteria belonging to a PDU session may be configured as criteria related to local services.

[0145] Furthermore, the criteria regarding the service type may be criteria information for identifying a corresponding service. Specifically, the criteria regarding the service type may be IMS registration related signaling, MMTEL voice call, MMTEL video call, SMS over NAS or SMSoIP. The criteria regarding the service type may also be criteria regarding a local service.

[0146] Additionally, the SOR security validation criteria may include SOR security check not successful. Also, the SOR security validation criteria may include criteria related to local services.

[0147] Furthermore, the criteria belonging to all types may be criteria information that matches in any state, and may also be composed of criteria related to local services.

[0148] Also, if multiple PDU sessions are established, the SOR-CMCI may contain multiple SOR-CMCI rules. Furthermore, if multiple services are running, the SOR-CMCI may contain multiple SOR-CMCI rules.

[0149] The SOR information (Steering of roaming information) may be information of the SOR configured with information protected by the HPLMN. The SOR information may include information indicating whether to request an acknowledgement (Ack), which is a response indicating successful reception of the Steering of roaming information from the UE.

[0150] The SOR information may include a list of recommended (or preferred) PLMN and access technology combinations and information indicating that (the list) is included, or information indicating that (the packet) is a secured packet, or information indicating that the SOR information does not include information indicating a list of recommended PLMN and access technology combinations because there is no need to change the list of recommended PLMN and access technology combinations stored in the UE.

[0151] The SOR information and an Ack, which is a response indicating that the UE has successfully received the SOR information, may be transmitted and received within an SOR transparent container information element included in the NAS message.

[0152] Each device may manage and / or store multiple SOR-CMCIs for the UE, or may manage and / or store one SOR-CMCI.

[0153] The first timer is a timer for determining the timing at which a UE in connected mode transitions to disconnected mode for SOR. The first timer may be the 3GPP Tsor-cm timer. The first timer may be managed by the UE and / or the NW. The first timer may be managed for each PDU session, for each access type, for each combination of a PDU session and an access type, for each service type, for each PLMN, or for each UE. In addition, the timer value set in the first timer may be referred to as the first timer value.

[0154] In other words, one UE may manage one or more first timers, or one UE may manage one first timer. The first timer managed by the UE may be stored in association with a PDU session ID, information indicating an access type, information indicating a combination of a PDU session and an access type, a service type, and / or a PLMN ID.

[0155] A first timer value may be associated with each criterion, and the first timer value may indicate the time the UE waits before releasing the PDU session or service and entering an idle state, and the first timer value may be a value for the Tsor-cm timer.

[0156] Based on the SOR-CMCI used when selecting the timer value to be set in the first timer, the criteria to which the selected timer value is associated, and / or information belonging to the PDU session included in the criteria, and / or information indicating the service type included in the criteria, and / or information indicating the priority to which the criteria is associated may be managed in association with the first timer and / or the first timer value.

[0157] A PDU session identified by information associated with these first timers, or a PDU session using information associated with the first timers, may be referred to as a PDU session associated with the first timer, and a service identified by information associated with the first timer may be referred to as a service associated with the first timer.

[0158] Here, "managing the first timer" means that the first timer is started and / or stopped and / or expired and / or executed. In other words, "the UE and / or NW managing the first timer" means that the UE and / or NW starts and / or stops and / or expires and / or executes the first timer, and "the state in which the UE and / or NW manages the first timer" means that the UE and / or NW is executing the first timer.

[0159] For example, when the UE and / or NW has established multiple PDU sessions, the UE and / or NW may manage a first timer for each PDU session, or may manage only one first timer.

[0160] Furthermore, for example, when the UE and / or NW establishes a first PDU session and a second PDU session on a 3GPP access and a third PDU session and a fourth PDU session on a non-3GPP access, the UE and / or NW may manage a first timer associated with the 3GPP access and a first timer associated with the non-3GPP access, or may simultaneously manage multiple first timers associated with each of the first to fourth PDU sessions.

[0161] Furthermore, for example, when the UE and / or NW establishes an MA PDU session that establishes user plane resources over both 3GPP access and non-3GPP access, the UE and / or NW may manage a first timer associated with the MA PDU session, or may simultaneously manage a first timer associated with the 3GPP access and a first timer associated with the non-3GPP access.

[0162] The temporarily forbidden SNPNs list may be managed independently for each access type. That is, the temporarily forbidden SNPNs list may be managed for each 3GPP access or non-3GPP access. The temporarily forbidden SNPNs list may be a list of SNPNs to which the UE cannot temporarily connect. In addition, if the UE supports onboarding services in an SNPN, an additional "temporarily forbidden SNPNs" list for onboarding services may be managed.

[0163] Also, if the UE supports localized services, a temporarily barred SNPN list may be maintained for additional localized services.

[0164] The permanently forbidden SNPNs list may be managed independently for each access type. That is, the permanently forbidden SNPNs list may be managed for each 3GPP access or non-3GPP access. The permanently forbidden SNPNs list may be a list of SNPNs to which the UE cannot permanently connect. In addition, if the UE supports onboarding services in the SNPN, an additional "permanently forbidden SNPNs" list for onboarding services may be managed.

[0165] Also, if the UE supports localized services, a permanently barred SNPN list may be maintained for additional localized services.

[0166] Additionally, the UE may not be able to initiate a registration procedure for an SNPN in the temporarily barred SNPN list or the permanently barred SNPN list.

[0167] The list of SNPNs temporarily prohibited for local services may be used when the UE supports local services. The list of SNPNs temporarily prohibited for local services may be an additional list of SNPNs temporarily prohibited for local services. The list of SNPNs temporarily prohibited for local services may be a list of SNPNs that provide local services to which the UE cannot temporarily connect.

[0168] In addition, the list of SNPNs temporarily prohibited for localized services may be managed independently for each access type, i.e., the list of SNPNs temporarily prohibited for localized services may be managed for each 3GPP access or non-3GPP access.

[0169] The list of SNPNs permanently barred for local services may be used when the UE supports local services. The list of SNPNs permanently barred for local services may be an additional list of SNPNs permanently barred for local services. The list of SNPNs permanently barred for local services may be a list of SNPNs that provide local services to which the UE cannot permanently connect.

[0170] In addition, the list of SNPNs permanently barred for localized services may be managed independently for each access type, i.e., the list of SNPNs permanently barred for localized services may be managed for each 3GPP access or non-3GPP access.

[0171] The list of prohibited hosting networks may be used when the UE supports localized services. The list of prohibited hosting networks may be a list of hosting networks to which the UE cannot connect.

[0172] Alternatively, the list of prohibited hosting networks may be managed independently for each access type, i.e., the list of prohibited hosting networks may be managed for each 3GPP access or non-3GPP access.

[0173] Additionally, the list of prohibited hosting networks may be maintained as a list of temporarily prohibited hosting networks and / or a list of permanently prohibited hosting networks.

[0174] Localized services may be services provided in a specific / restricted area. Localized services may also be time-restricted. Localized services may also be referred to as local services. Localized services may also be realized via applications such as live or on-demand voice or video streams, video games, or IMS. Localized services may also be realized via connectivity such as UE-to-UE or UE-to-DN.

[0175] Furthermore, a local service may be read as a hosting network, a local service may be provided by a hosting network, and a local service is supported may be read as a hosting network is supported.

[0176] A localized service provider may be an application provider or a network operator that localizes services and provides them to end users through a hosting network. A localized service provider may also be an application provider or a network operator that provides localized services. A localized service provider may also be a DN. A localized service provider may also be a core network.

[0177] A hosting network may be a network that provides connectivity to local services. The hosting network may also be an NPN, which may be an SNPN or a PNI-NPN.

[0178] Also, a hosting network may be read as a local service, and a supported hosting network may be read as a local service.

[0179] A home network may be a network that owns the subscription or credentials of a UE that is currently in use, and may be a PLMN or an NPN, where the NPN may be an SNPN or a PNI-NPN.

[0180] A home network service may be a service provided to a UE based on a subscription agreed with a home network operator, or may be a service provided by a home network.

[0181] [2.7. Description of Identification Information in This Embodiment] Next, the identification information transmitted, received, stored, and / or managed by each device in this embodiment will be described.

[0182] First, the first identification information is information for identifying an SNPN. The first identification information may be an SNPN ID. Furthermore, the first identification information may be information combining a PLMN ID and an NID. Here, the PLMN ID may be composed of an MCC and an MNC. Furthermore, the PLMN ID may be information within a 5GS mobile identity.

[0183] Next, the second identification information may be information indicating whether or not a Closed Access Group (CAG) is supported. The second identification information may be information indicating that a CAG is supported. Alternatively, the second identification information may be information indicating that a CAG is not supported. Alternatively, the second identification information may be 5GMM capability. Alternatively, the second identification information may be information included in the 5GMM capability.

[0184] Next, the third identification information may be information indicating whether or not a hosting network is supported. The third identification information may be information indicating that a hosting network is supported. Alternatively, the third identification information may be information indicating that a hosting network is not supported. Alternatively, the third identification information may be 5GMM capability. Alternatively, the third identification information may be information included in the 5GMM capability.

[0185] Furthermore, the third identification information may be information indicating whether or not a local service is supported. The third identification information may be information indicating that a local service is supported. The third identification information may be information indicating that a local service is not supported.

[0186] The third identification information may also be information indicating a request for use of a hosting network. In other words, the third identification information may be information indicating a request for connection to a hosting network. The third identification information may also be information indicating a request for use of a local service. In other words, the third identification information may be information indicating a request for connection to a local service.

[0187] The third identification information may also be information indicating that authentication and / or authorization is requested from the hosting network, or may be information indicating that authentication and / or authorization is requested from a local service.

[0188] Next, the tenth identification information is SOR-CMCI. The tenth identification information may be composed of one or more of the eleventh identification information, the twelfth identification information, and / or the thirteenth identification information.

[0189] Next, the eleventh identification information is the SOR-CMCI rule. The eleventh identification information may be composed of one twelfth identification information and one thirteenth identification information. The eleventh identification information may also be information included in the tenth identification information.

[0190] Next, the twelfth identification information is a criterion. The twelfth identification information may be information included in the tenth identification information and / or the eleventh identification information.

[0191] The twelfth identification information may also be configured with a PDU session attribute type criterion, and / or a service type criterion, and / or a SOR security check criterion, and / or a match all type criterion. The criterion information may also be configured with a local service criterion.

[0192] Here, the criteria for a local service may be criteria when the local service is used. Alternatively, the criteria for a local service may be criteria used when connecting to a hosting network. Alternatively, the criteria for a local service may be referred to as criteria indicating a local service. Alternatively, the criteria for a local service may simply be referred to as a local service.

[0193] Furthermore, the criteria belonging to a PDU session may be criteria information for identifying the corresponding PDU session. Specifically, the criteria belonging to a PDU session may be configured as the DNN of the PDU session, or the S-NSSAI STT of the PDU session, or the S-NSSAI STT and SD of the PDU session. Furthermore, the criteria belonging to a PDU session may be configured as criteria related to local services.

[0194] Furthermore, the criteria regarding the service type may be criteria information for identifying a corresponding service. Specifically, the criteria regarding the service type may be IMS registration related signaling, MMTEL voice call, MMTEL video call, SMS over NAS or SMSoIP. The criteria regarding the service type may also be criteria regarding a local service.

[0195] Additionally, the SOR security validation criteria may include SOR security check not successful. Also, the SOR security validation criteria may include criteria related to local services.

[0196] Furthermore, the criteria belonging to all types may be criteria information that matches in any state, and may also be composed of criteria related to local services.

[0197] Next, the thirteenth identification information is the first timer value. The thirteenth identification information may be information included in the tenth identification information and / or the eleventh identification information.

[0198] In other words, the thirteenth identity may be a timer value of the Tsor-cm timer, and may be associated with the twelfth identity, and may indicate a time period that the UE should wait before releasing the PDU session or service and entering the idle state.

[0199] Furthermore, the thirteenth identification information may be a different value for each UE.

[0200] Furthermore, the 13th identification information may have a different value for each group of multiple UEs. In other words, the 13th identification information may have a different value for each UE group including one or more UEs. For example, if UE1, UE2, UE3, and UE4 exist, and UE1 and UE2 belong to UE group 1, and UE3 and UE4 belong to UE group 2, the 13th identification information for UE1 and UE2 (or UE group 1) may be timer value 1, and the 13th identification information for UE3 and UE4 (or UE group 2) may be timer value 2. That is, the 13th identification information may be information including multiple timer values.

[0201] Next, the fourteenth identification information may be a cause value indicating that the local service has been terminated. In other words, the fourteenth identification information may be a cause value indicating that the local service has become unavailable. The fourteenth identification information may be a 5GMM cause value. Furthermore, the fourteenth identification information may be information included in the 5GMM cause value.

[0202] The fourteenth identification information may also be a reason value indicating that the hosting network has been shut down, i.e., that the hosting network has become unavailable.

[0203] Next, the fifteenth identification information may be information indicating a range of a registration wait time. The fifteenth identification information may be a registration wait range. Here, the fifteenth identification information may include a minimum registration wait time and a maximum registration wait time.

[0204] The fifteenth identification information may also be information indicating a range of waiting time until returning to the home network, and may include a minimum value and a maximum value.

[0205] The UE may also generate a random number within the range of the minimum and maximum values ​​of the 15th identification information. The number generated using the 15th identification information may also be used as a timer value. That is, the UE may start a timer using the timer value, which is the number generated using the 15th identification information.

[0206] Next, the 16th identification information is a timer value. The 16th identification information may be a timer value indicating a time during which an MM procedure, including a registration procedure, is not to be initiated. For example, while a timer using the timer value indicated by the 16th identification information is running, the UE may not be able to initiate an MM procedure, including a registration procedure. Furthermore, the UE may initiate an MM procedure, including a registration procedure, based on expiration of the timer using the timer value indicated by the 16th identification information.

[0207] Furthermore, the 16th identification information may indicate a time. Specifically, the 16th identification information may indicate a time at which the MM procedure should not be started. For example, the UE may not be able to start the MM procedure until the time indicated by the 16th identification information, or the UE may be able to start the MM procedure after the time indicated by the 16th identification information.

[0208] Next, the 17th identification information may be a reason value indicating to the hosting network that the authorization was not granted. The 17th identification information may be a 5GMM cause value. Furthermore, the 17th identification information may be information included in the 5GMM cause value.

[0209] The seventeenth identification information may also be a reason value indicating that local service is not permitted, i.e., that connection to the hosting network is not permitted.

[0210] Next, the 18th identification information may be a reason value indicating that the SNPN is temporarily not authorized. The 18th identification information may be #74 (Temporarily not authorized for this SNPN). Furthermore, the 18th identification information may be a 5GMM cause value. Furthermore, the 18th identification information may be information included in the 5GMM cause value.

[0211] Next, the 19th identification information may be a reason value indicating that the SNPN has been permanently not authorized. The 19th identification information may be #75 (Permanently not authorized for this SNPN). The 19th identification information may also be a 5GMM cause value. The 19th identification information may also be information included in the 5GMM cause value.

[0212] Next, the 20th identification information may be a list including one or more CAG IDs. The 20th identification information may be a CAG information list. Furthermore, the 20th identification information may be an extended CAG information list.

[0213] The 20th identification information may also be a list including one or more CAG IDs for the local service. The 20th identification information may also be a CAG information list for the local service. The 20th identification information may also be an extended CAG information list for the local service.

[0214] The 20th identification information may be a list including one or more CAG IDs for the hosting network. The 20th identification information may be a CAG information list for the hosting network. The 20th identification information may be an extended CAG information list for the hosting network.

[0215] Next, the 21st identification information may be a reason value indicating that the CAG was not authorized or that the CAG cell was authorized only. The 21st identification information may be #76 (Not authorized for this CAG or authorized for CAG cells only). Furthermore, the 21st identification information may be a 5GMM cause value. Furthermore, the 21st identification information may be information included in the 5GMM cause value.

[0216] Next, the 22nd identification information may be a list containing identifiers of available hosting networks. The 22nd identification information may be a list containing SNPN IDs and / or CAG IDs. Here, the hosting network may be an NPN. In other words, the hosting network may be an SNPN or a PNI-NPN.

[0217] Next, the 23rd identification information may be a list containing identifiers of unavailable hosting networks. The 23rd identification information may be a list containing SNPN IDs and / or CAG IDs. Here, the hosting network may be an NPN. In other words, the hosting network may be an SNPN or a PNI-NPN.

[0218] [3. Description of procedures used in each embodiment] Next, procedures used in each embodiment will be described. The procedures used in each embodiment include a registration procedure, a UE-initiated de-registration procedure, a network-initiated de-registration procedure, a UE-initiated NAS transport procedure, and a network-initiated NAS transport procedure. Each procedure will be described below.

[0219] In each embodiment, as shown in FIG. 2, the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are each configured as the same device (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 where these are configured as different devices (i.e., different physical hardware, different logical hardware, or different software). For example, data may be transmitted and received directly between these devices, or data may be transmitted and received via the N26 interface between the AMF and MME, or data may be transmitted and received via the UE.

[0220] 3.1. Registration Procedure First, the registration procedure will be described with reference to FIG. 6. The registration procedure is a procedure in 5GS. In this chapter, this procedure refers to the registration procedure. The registration procedure is a procedure initiated by the UE to register with the access network _B and / or the core network _B and / or the DN. If the UE is not registered with the network, it can execute this procedure at any time, for example, when it is powered on. In other words, if the UE is in the deregistered state (RM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and the AMF) can transition to the registered state (RM-REGISTERED state) based on the completion of the registration procedure. Note that the registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state (registered state or deregistered state) for 3GPP access and the registration state for non-3GPP access.

[0221] The registration procedure may also be a registration procedure for initial registration, or a registration procedure for mobility and periodic registration update.

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

[0223] This procedure may also be a registration procedure for a local service or a registration procedure for a hosting network.

[0224] The UE may initiate the registration procedure when performing mobility across TAs. In other words, the UE may initiate the registration procedure when it moves to a TA different from the TA indicated in the TA list it holds. Furthermore, the UE may initiate the registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may initiate the registration procedure when there is a change in the capability information and / or preferences related to the establishment of the UE's PDU session. Furthermore, the UE may initiate the registration procedure periodically. Furthermore, the UE may initiate the registration procedure based on the completion of a UE configuration update procedure. However, the UE is not limited to these, and may perform the registration procedure at any timing.

[0225] Additionally, the UE may periodically initiate a registration procedure even when in a registered state.

[0226] Note that a registration procedure performed based on the mobility of the UE and a registration procedure performed periodically may be referred to as a registration procedure for mobility and registration update. In other words, the registration procedure for mobility and registration update may be a registration procedure performed based on the mobility of the UE, or may be a registration procedure performed periodically. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed based on a configuration update of the UE. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed to establish a communication path for transmitting and receiving user data. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed based on a request from the network. Furthermore, in other words, the registration procedure for mobility and registration update may be a registration procedure other than the registration procedure for initial registration.

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

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

[0229] Here, the UE may transmit one or more of the first to third identification information by including them in a registration request message and / or an RRC message. More specifically, the UE may transmit one or more of the first to third identification information by including them in a registration request message and / or an RRC message, or may transmit one or more of the first to third identification information by including them in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, a MAC layer, an RLC layer, or a PDCP layer).

[0230] By transmitting these pieces of identification information, the UE may indicate to the network that the UE supports each function, or may indicate a request from the UE. Furthermore, when multiple pieces of identification information are transmitted and received, two or more pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0231] Furthermore, the UE may indicate to the network the contents indicated by the identification information included in the registration request message by including one or more of the first to third identification information in the registration request message and sending it.

[0232] In addition, the UE may select and decide whether to include one or more of the first to third identification information in the registration request message based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0233] The UE may also transmit identification information other than the first to third identification information in the registration request message.

[0234] When a 5G AN (or gNB) receives an RRC message including a registration request message, it selects an AMF to which to forward the registration request message (S802). The 5G AN (or gNB) can select an AMF based on information included in the registration request message and / or the RRC message. The 5G AN (or gNB) extracts the registration request message from the received RRC message and forwards the registration request message to the selected AMF (S804).

[0235] When the AMF receives the registration request message, the AMF can perform a first condition determination. The first condition determination is for determining whether the network (or the AMF) accepts the UE's request. If the first condition determination is true, the AMF starts the procedure of (A) in Figure 6, while if the first condition determination is false, the AMF starts the procedure of (B) in Figure 6.

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

[0237] First, a case where the first condition determination is true will be described. In the procedure of (A) in Fig. 6, the AMF transmits a registration accept message to the UE via the 5G AN (or gNB) as a response message to the registration request message (S806). Note that the registration accept message is an NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) as part of an RRC message.

[0238] The AMF may include one or more of the identification information items 10 to 23 in the registration accept message and transmit it. By transmitting these identification information items, the AMF may indicate that the network supports each function, or may indicate that the UE's request has been accepted. Furthermore, when multiple identification information items are transmitted and received, two or more of these identification information items may be configured as one or more identification information items. Furthermore, the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0239] Furthermore, the AMF may indicate to the UE the contents indicated by one or more of the 10th to 23rd identification information by including them in a registration accept message and sending them. The AMF may also indicate to the UE the contents of these identification information by sending a registration accept message.

[0240] Furthermore, the AMF may select and decide whether to include one or more of the identification information from the 10th to 23rd identification information in the registration acceptance message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0241] In addition, the AMF may also include identification information other than identification information 10 to 23 in the registration acceptance message.

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

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

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

[0245] Next, the UE may or may not send a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S808). Here, the registration completion message is an NAS message transmitted and received on the N1 interface, but is included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

[0246] Next, the AMF may or may not receive a registration completion message via the 5G AN (gNB) (S808).

[0247] Each device completes the procedure in FIG. 6(A) based on the transmission and reception of the registration acceptance message and / or the registration completion message.

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

[0249] Here, the AMF may include one or more of the identification information items 10 to 23 in the registration rejection message and send it. Furthermore, the AMF may send these identification information items to indicate that the UE request has been rejected, or may indicate the reason why the UE request has been rejected.

[0250] Furthermore, the AMF may indicate to the UE the contents indicated by the identification information included in the registration rejection message by including one or more of the identification information from the 10th to 23rd identification information in the registration rejection message. The AMF may also indicate to the UE the contents of these identification information by sending a registration rejection message.

[0251] Furthermore, the AMF may select and decide whether to include one or more of the identification information from the 10th to 23rd identification information in the registration rejection message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

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

[0253] Next, the UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S810). By receiving the registration rejection message, the UE can recognize that the UE's request via the registration request message has been rejected and the contents of various identification information included in the registration rejection message.

[0254] Furthermore, if the UE does not receive a registration rejection message within a predetermined period of time after sending the registration request message, the UE may recognize that the UE's request has been rejected.

[0255] Based on the sending and receiving of the registration rejection message, each device completes step (B) of this procedure.

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

[0257] Each device completes the registration procedure based on the completion of the procedure of (A) or (B) in Figure 6. Note that each device may transition to a state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure of (A) in Figure 6. Also, each device may maintain a state in which the UE is not registered in the network (RM_DEREGISTERED state) based on the completion of the procedure of (B) in Figure 6, or may transition to a state in which the UE is not registered in the network.

[0258] Furthermore, each device may perform processing based on the information transmitted and received during the registration procedure based on the completion of the registration procedure. For example, if the device transmits or receives information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's requests have been rejected, or may perform the registration procedure for the core network_B or another cell.

[0259] Furthermore, the UE may store the identification information received with the registration accept message or registration reject message and may recognize the network's decision based on the completion of the registration procedure.

[0260] 3.2. Non-Registration Procedures Next, the de-registration procedure will be described. In this chapter, this procedure refers to the de-registration procedure. The de-registration procedure is a procedure initiated by the UE or the network to deregister the UE. The de-registration procedure may also be a procedure to change the state of the UE to the unregistered state.

[0261] The UE and the network can execute this procedure at any time as long as the UE is registered with the network. In other words, the UE and the network can start this procedure at any time as long as the UE is registered. Furthermore, each device (especially the UE and the AMF) can transition to the unregistered state based on the completion of the unregistration procedure.

[0262] Furthermore, a device in the core network, such as the AMF, may initiate this procedure based on an update to the network configuration and / or an update to the operator policy. The trigger for this procedure may be detection of UE mobility, detection of a change in the status of the UE, the access network, and / or the core network, or a change in the status of a network slice. The trigger for this procedure may be reception of a request from the DN and / or an application server of the DN, a change in the network configuration, or a change in the operator policy. The triggers for the device in the core network to initiate this procedure are not limited to these.

[0263] Furthermore, this procedure may be performed at any time when each device has established a 5GMM context and / or when each device is in 5GMM connected mode.

[0264] During this procedure, each device may also send and receive messages containing identification information indicating the reason for the UE deregistration and / or indicating that network reselection is required. Furthermore, each device may delete the UE context or initiate network-directed behavior based on the completion of this procedure.

[0265] The UE may recognize the reason for deregistration based on the control information transmitted and received in this procedure. Furthermore, upon recognizing the reason for deregistration, the UE may delete the UE context or initiate network reselection. In other words, a device in the core network may initiate this procedure and send the control messages and control information of this procedure to the UE, thereby causing the UE to recognize the reason for deregistration. Furthermore, upon recognizing the reason for deregistration, the device in the core network may delete the UE context or initiate network reselection.

[0266] The non-registration procedure is classified into a UE-initiated non-registration procedure and a network-initiated non-registration procedure. The UE-initiated non-registration procedure and the network-initiated non-registration procedure will be described below.

[0267] 3.2.1. UE-initiated de-registration procedure First, the UE-initiated de-registration procedure will be explained using Figure 7. In this chapter, this procedure refers to the UE-initiated de-registration procedure. The UE-initiated de-registration procedure is a de-registration procedure initiated by the UE. Each step of this procedure will be explained below.

[0268] First, the UE initiates the deregistration procedure by sending a deregistration request message to the AMF via the 5G AN (or gNB) (S900).

[0269] Here, the UE may transmit the deregistration request message including one or more of the first to third identification information. By transmitting this identification information, the UE may indicate the reason for deregistration of the UE or may indicate the need for network reselection. Furthermore, two or more of these identification information may be configured as one or more identification information. Note that the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0270] Furthermore, the UE may indicate to the AMF the contents indicated by the identification information included in the non-registration request message by including one or more of the first to third identification information in the non-registration request message and sending it.

[0271] In addition, the UE may select and decide whether to include one or more of the first to third identification information in the non-registration request message based on the received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0272] The UE may also request deletion of the UE's context by sending a deregistration request message based on the received identification information, and / or subscription information, and / or UE capability information, and / or UE status, and / or user registration information, and / or context held by the UE, etc.

[0273] Next, the AMF receives a non-registration request message via the 5G AN (gNB) (S900). The AMF may recognize the reason for deregistration of the UE based on the non-registration request message and / or the identification information included in the non-registration request message.

[0274] Furthermore, the AMF may send a deregistration accept message to the UE via the 5G AN (gNB) as a response message to the deregistration request message based on the identification information included in the deregistration request message (S902).

[0275] Next, the UE may receive a non-registration acceptance message via the 5G AN (gNB) (S902).

[0276] Each device completes this procedure based on sending and receiving a non-registration request message and / or a non-registration acceptance message.

[0277] Furthermore, each device may perform processing based on the information transmitted and received in this procedure upon completion of this procedure. For example, each device may delete the UE context when it transmits or receives update information for the configuration information.

[0278] Furthermore, if the UE transmits or receives information indicating that a network reselection and / or registration procedure needs to be performed, the UE may initiate the network reselection and / or registration procedure based on the completion of this procedure.

[0279] 3.2.2. Network-Initiated Deregistration Procedures Next, the network-initiated de-registration procedure will be explained using Figure 8. In this chapter, this procedure refers to the network-initiated de-registration procedure. The network-initiated de-registration procedure is a de-registration procedure that is initiated by the network. Each step of this procedure will be explained below.

[0280] First, the AMF initiates the deregistration procedure by sending a deregistration request message to the UE via the 5G AN (or gNB) (S1000).

[0281] Here, the AMF may transmit one or more identification information items among the tenth to twenty-third identification information items in the deregistration request message. By transmitting these identification information items, the AMF may indicate the reason for deregistration of the UE or may indicate the need for network reselection. Furthermore, two or more of these identification information items may be configured as one or more identification information items. Furthermore, the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information or as different identification information.

[0282] Furthermore, the AMF may indicate to the UE the contents indicated by the identification information included in the non-registration request message by including one or more of the identification information from the 10th to 23rd identification information in the non-registration request message and sending it.

[0283] Furthermore, the AMF may select and decide whether to include one or more of the identification information from the 10th to 23rd identification information in the non-registration request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0284] The AMF may also request deletion of the UE's context by sending a deregistration request message based on the received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0285] Next, the UE receives a deregistration request message via the 5G AN (gNB) (S1000). The UE may recognize the reason for deregistration of the UE based on the deregistration request message and / or the identification information included in the deregistration request message, and may perform network reselection.

[0286] Furthermore, the UE may send a deregistration accept message to the AMF via the 5G AN (gNB) as a response message to the deregistration request message based on the identification information included in the deregistration request message (S1002).

[0287] Next, the AMF may receive a non-registration acceptance message via the 5G AN (gNB) (S1002). In addition, each device completes this procedure based on the transmission and reception of the non-registration request message and / or the non-registration acceptance message.

[0288] Furthermore, each device may perform processing based on the information transmitted and received in this procedure upon completion of this procedure. For example, each device may delete the UE context when it transmits or receives update information for the configuration information.

[0289] Furthermore, if the UE transmits or receives information indicating that a network reselection and / or registration procedure needs to be performed, the UE may initiate the network reselection and / or registration procedure based on the completion of this procedure.

[0290] In the above procedure, by sending and receiving a non-registration request message, a device in the core network can instruct the UE to delete configuration information already applied by the UE, or to stop or change functions currently being executed by the UE.

[0291] 3.3. NAS Transport Procedures Next, the NAS transport procedure will be described. In this chapter, this procedure refers to the NAS transport procedure. The NAS transport procedure is a procedure initiated by the UE or the network to provide payload transfer between the UE and the AMF.

[0292] This procedure may be performed at any time when each device has established a 5GMM context and / or when each device is in 5GMM connected mode.

[0293] Furthermore, a device in the core network, such as the AMF, may initiate this procedure based on an update to the network configuration and / or an update to the operator policy. The trigger for this procedure may be detection of UE mobility, detection of a change in the status of the UE, the access network, and / or the core network, or a change in the status of a network slice. The trigger for this procedure may be reception of a request from the DN and / or an application server of the DN, a change in the network configuration, or a change in the operator policy. The triggers for the device in the core network to initiate this procedure are not limited to these.

[0294] Furthermore, each device may initiate network-directed behavior based on the completion of this procedure.

[0295] The NAS transport procedure includes a UE-initiated NAS transport procedure and a network-initiated NAS transport procedure. The UE-initiated NAS transport procedure and the network-initiated NAS transport procedure will be described below.

[0296] 3.3.1. UE-initiated NAS transport procedures First, the UE-initiated NAS transport procedure will be explained using Figure 9. In this chapter, this procedure refers to the UE-initiated NAS transport procedure. The UE-initiated NAS transport procedure is a NAS transport procedure that is initiated by the UE. Each step of this procedure will be explained below.

[0297] First, the UE initiates a NAS transport procedure by sending a UL NAS TRANSPORT message to the AMF (S1100). The UL NAS TRANSPORT message may be referred to as an Uplink Non-Access-Stratum TRANSPORT message.

[0298] Here, the UE may transmit the UL NAS transport message including one or more of the first to third identification information. Note that two or more of these identification information may be configured as one or more identification information. Note that the information indicating support of each function and the information indicating a request for use of each function may be transmitted and received as the same identification information or as different identification information.

[0299] Furthermore, the UE may indicate to the AMF the contents indicated by the identification information included in the UL NAS transport message by including one or more of the first to third identification information in the UL NAS transport message and transmitting the same.

[0300] The UE may select and decide whether to include one or more of the first to third identification information in the UL NAS transport message based on the received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0301] Next, the AMF receives the UL NAS transport message (S1100).

[0302] Each device completes this procedure based on sending and receiving UL NAS transport messages.

[0303] Furthermore, each device may perform processing based on the information transmitted and received in this procedure upon completion of this procedure.

[0304] 3.3.2. Network-Initiated NAS Transport Procedures Next, the network-initiated NAS transport procedure will be explained using Figure 10. In this chapter, this procedure refers to the network-initiated NAS transport procedure. The network-initiated NAS transport procedure is a NAS transport procedure that is initiated by the network. Each step of this procedure will be explained below.

[0305] First, the AMF initiates the NAS transport procedure by sending a DL NAS TRANSPORT message to the UE (S1200). The DL NAS TRANSPORT message may be referred to as a Downlink Non-Access-Stratum TRANSPORT message.

[0306] Here, the AMF may transmit one or more of the identification information items 10 to 23 in the DL NAS transport message. Note that two or more of these identification information items may be configured as one or more identification information items. Note that the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information or as different identification information.

[0307] Furthermore, the AMF may indicate to the UE the contents indicated by the identification information included in the DL NAS transport message by including one or more of the identification information 10 to 23 in the DL NAS transport message and sending it.

[0308] Furthermore, the AMF may select and decide whether to include one or more of the identification information from the 10th to 23rd identification information in the DL NAS transport message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0309] Next, the UE receives a DL NAS transport message (S1200).

[0310] Each device completes this procedure based on sending and receiving DL NAS transport messages.

[0311] Furthermore, each device may perform processing based on the information transmitted and received in this procedure upon completion of this procedure.

[0312] 4. Embodiment Next, each embodiment will be described.

[0313] [4.1. First embodiment] First, a first embodiment will be described. In this chapter, the first embodiment may be referred to as the present embodiment.

[0314] In this embodiment, the network may be a hosting network, where the hosting network may be an SNPN or a PNI-NPN.

[0315] In addition, in this embodiment, a registration procedure, and / or a UE-initiated NAS transport procedure, and / or a network-initiated NAS transport procedure may be performed.

[0316] In this embodiment, the first control message may be a registration acceptance message or a DL NAS transport message.

[0317] Each step of this procedure will be explained below.

[0318] First, the network sends a first control message to the UE, where the network may include one or more of the tenth to thirteenth identification information in the first control message.

[0319] Here, the network may indicate to the UE the contents indicated by the identification information included in the first control message by including one or more of the identification information from the tenth to thirteenth identification information in the first control message and transmitting the same.

[0320] Specifically, the network may indicate the SOR-CMCI to the UE by transmitting tenth identification information. Also, the network may indicate the content of each identification information to the UE by transmitting the tenth identification information consisting of one or more identification information among the eleventh to thirteenth identification information. Specifically, the network may indicate the SOR-CMCI and / or the SOR-CMCI rule and / or the criterion and / or the first timer value to the UE by transmitting the tenth identification information consisting of one or more identification information among the eleventh to thirteenth identification information.

[0321] Furthermore, the network may indicate the SOR-CMCI rule to the UE by transmitting eleventh identification information. Here, the network may transmit the eleventh identification information to the UE by including it in the tenth identification information. Furthermore, the network may indicate the content of each identification information to the UE by transmitting the eleventh identification information consisting of one or more identification information from the twelfth to thirteenth identification information. Specifically, the network may indicate the SOR-CMCI rule, the criterion, and / or the first timer value to the UE by transmitting the eleventh identification information consisting of one or more identification information from the twelfth to thirteenth identification information.

[0322] The network may also indicate the criteria to the UE by transmitting a twelfth identification, where the network may transmit the twelfth identification to the UE by including it in the tenth and / or eleventh identification.

[0323] Here, the network may set the 12th identification information to a reference related to the DNN of the PDU session or a local service.

[0324] The network may also indicate the first timer value to the UE by transmitting a thirteenth identification, where the network may transmit the thirteenth identification to the UE by including it in the tenth and / or eleventh identifications.

[0325] Furthermore, the network may transmit the first control message to indicate to the UE the content of each piece of identification information included in the first control message. Furthermore, the network may transmit the each piece of identification information to indicate to the UE the content of each piece of identification information.

[0326] In addition, the network may select and decide whether to include one or more of the tenth to thirteenth identification information in the first control message based on the state of the UE, and / or information received from a local service provider, and / or information received from the UDM, and / or information received from the AUSF, etc.

[0327] The network may also determine whether to transmit the first control message and / or the respective identification information based on the state of the UE, and / or information received from the local service provider, and / or information received from the UDM, and / or information received from the AUSF, etc. The network may also transmit the first control message and / or the respective identification information based on information received from the local service provider and / or the UDM. The network may also transmit the first control message and / or the respective identification information based on information received from the AUSF indicating that the local service is to be terminated.

[0328] Next, the UE receives a first control message. The UE may also receive a first control message from the network, the first control message including one or more of the tenth to thirteenth identification information.

[0329] Furthermore, the UE may store the identification information received with the first control message or recognize the network's decision based on receiving the first control message, and may recognize the content of the identification information received with the first control message based on receiving the first control message.

[0330] Specifically, when the UE receives the tenth identification information, the UE may recognize the SOR-CMCI. Also, when the UE receives the tenth identification information, the UE may apply the SOR-CMCI. Specifically, when the UE receives the tenth identification information, the UE may perform a process for applying the SOR-CMCI.

[0331] Furthermore, when the UE receives a tenth identification consisting of one or more of the eleventh to thirteenth identifications, the UE may recognize each identification. Specifically, when the UE receives a tenth identification consisting of one or more of the eleventh to thirteenth identifications, the UE may recognize the SOR-CMCI, and / or the SOR-CMCI rule, and / or the criterion, and / or the first timer value.

[0332] Furthermore, when the UE receives a tenth identification consisting of one or more identifications among the eleventh to thirteenth identifications, the UE may perform processing for each identification. Specifically, when the UE receives a tenth identification consisting of one or more identifications among the eleventh to thirteenth identifications, the UE may perform processing for the SOR-CMCI, and / or the SOR-CMCI rule, and / or the criterion, and / or the first timer value.

[0333] In addition, the UE may recognize the SOR-CMCI rule when receiving the eleventh identification information, and may perform processing for the SOR-CMCI rule when receiving the eleventh identification information.

[0334] Furthermore, when the UE receives eleventh identification information consisting of one or more of the twelfth to thirteenth identification information, the UE may recognize each identification information. Specifically, when the UE receives eleventh identification information consisting of one or more of the twelfth to thirteenth identification information, the UE may recognize the SOR-CMCI rule, the criterion, and / or the first timer value.

[0335] Furthermore, when the UE receives eleventh identification information consisting of one or more identification information among the twelfth to thirteenth identification information, the UE may perform processing for each identification information. Specifically, when the UE receives eleventh identification information consisting of one or more identification information among the twelfth to thirteenth identification information, the UE may perform processing for the SOR-CMCI rule, and / or the criterion, and / or the first timer value.

[0336] In addition, the UE may recognize the criterion when receiving the twelfth identification information, and may perform processing for the criterion when receiving the twelfth identification information.

[0337] Furthermore, the UE may recognize the first timer value when receiving the thirteenth identification information. Furthermore, the UE may perform processing for the first timer value when receiving the thirteenth identification information.

[0338] Wherein, if the twelfth identification information is a criterion indicating a local service, the UE may check whether the local service is running and start a first timer associated with the thirteenth identification information. Also, if the twelfth identification information is a criterion indicating a local service, the UE may check whether the local service is running and start a first timer associated with the twelfth identification information using the thirteenth identification information.

[0339] The UE may also start an associated first timer based on the twelfth identification information and using the thirteenth identification information.

[0340] Furthermore, when the 13th identification information is associated with the 12th identification information indicating a criterion for a local service, the 13th identification information may be a different value for each UE. Furthermore, when the 13th identification information is associated with the 12th identification information indicating a DNN of the PDU session, the 13th identification information may be a different value for each UE.

[0341] Furthermore, when the 13th identification information is associated with the 12th identification information indicating a criterion for a local service, the 13th identification information may have a different value for each group of UEs including one or more UEs. For example, when UE1, UE2, UE3, and UE4 exist, and UE1 and UE2 belong to UE group 1, and UE3 and UE4 belong to UE group 2, the 13th identification information for UE1 and UE2 (or UE group 1) may be timer value 1, and the 13th identification information for UE3 and UE4 (or UE group 2) may be timer value 2.

[0342] The UE may perform the behavior after receiving the first control message, or after receiving one or more of the tenth to thirteenth identification information.

[0343] Furthermore, when the UE receives the first control message, the UE may perform the behavior that occurs when it receives each piece of identification information included in the first control message.

[0344] [4.2. Second embodiment] Next, a second embodiment will be described. In this chapter, the second embodiment may be referred to as the present embodiment.

[0345] In this embodiment, the network may be a hosting network, where the hosting network may be an SNPN or a PNI-NPN.

[0346] In addition, in this embodiment, a network-initiated de-registration procedure may be implemented.

[0347] Each step of this procedure will be explained below.

[0348] First, the network sends a non-registration request message to the UE, where the network may include one or more of the fourteenth to sixteenth identities in the non-registration request message.

[0349] Here, the network may indicate to the UE the contents indicated by the identification information included in the non-registration request message by including one or more of the identification information from the 14th to 16th identification information in the non-registration request message and sending it.

[0350] Specifically, the network may send the fourteenth identification information to the UE to indicate a cause value indicating that the localized service has been terminated. Also, the network may send the fourteenth identification information to the UE to indicate that the localized service has been terminated.

[0351] The network may also indicate a range of registration waiting times to the UE by transmitting the fifteenth identification information, and may also indicate a minimum registration waiting time and a maximum registration waiting time to the UE by transmitting the fifteenth identification information.

[0352] The network may also indicate the timer value to the UE by sending the 16th identification information.

[0353] The network may also indicate to the UE the content of each piece of identification information included in the non-registration request message by transmitting the non-registration request message. The network may also indicate to the UE the content of each piece of identification information by transmitting the each piece of identification information.

[0354] In addition, the network may select and decide whether to include one or more of the fourteenth to sixteenth identification information in the de-registration request message based on the state of the UE, and / or information received from a local service provider, and / or information received from the UDM, and / or information received from the AUSF, etc.

[0355] The network may also determine whether to send the deregistration request message and / or each identification information based on the state of the UE, and / or information received from the local service provider, and / or information received from the UDM, and / or information received from the AUSF, etc. The network may also send the deregistration request message and / or each identification information based on information received from the local service provider and / or the UDM. The network may also send the deregistration request message and / or each identification information based on information received from the AUSF indicating that the local service is to be terminated.

[0356] The UE then receives a non-registration request message. The UE may also receive a non-registration request message from the network, the non-registration request message including one or more of the fourteenth to sixteenth identities.

[0357] Furthermore, the UE may store the identification information received with the non-registration request message or recognize the network's decision based on receiving the non-registration request message, and may recognize the content of the identification information received with the non-registration request message based on receiving the non-registration request message.

[0358] Specifically, when the UE receives the 14th identification information, the UE may recognize that the local service has ended, and when the UE receives the 14th identification information, the UE may delete the 15th or 16th identification information stored in the UE.

[0359] Furthermore, when the UE receives the 15th identification information, the UE may recognize the range of the registration waiting time. Furthermore, when the UE receives the 15th identification information, the UE may delete the 15th identification information stored in the UE and store the received 15th identification information.

[0360] Furthermore, when the UE receives the 16th identification information, the UE may recognize the registration waiting time. Furthermore, when the UE receives the 16th identification information, the UE may delete the 16th identification information stored in the UE and store the received 16th identification information.

[0361] In addition, when the UE receives the 14th identification information and also receives the 15th or 16th identification information, it may delete the 15th or 16th identification information stored in the UE and store the received 15th or 16th identification information.

[0362] Furthermore, if the UE decides to perform PLMN selection or SNPN selection and has a stored 15th identity, the UE may generate a random number within the range of the 15th identity and start a second timer using the generated number.

[0363] Also, if the UE decides to perform PLMN selection or SNPN selection and has a stored 16th identity, the UE may start a second timer using the 16th identity.

[0364] Here, the UE may not initiate the registration procedure while the second timer is running, and may perform the registration procedure when the second timer expires.

[0365] The UE may perform the above behavior after receiving a deregistration request message, or after receiving one or more of the fourteenth to sixteenth identification information.

[0366] Furthermore, when the UE receives a non-registration request message, the UE may perform the behavior when it receives each piece of identification information included in the non-registration request message.

[0367] [4.3. Third embodiment] Next, a third embodiment will be described. In this chapter, the third embodiment may be referred to as the present embodiment.

[0368] In this embodiment, the network may be a hosting network, where the hosting network may be an SNPN or a PNI-NPN.

[0369] In addition, in this embodiment, a registration procedure may be performed.

[0370] Each step of this procedure will be explained below.

[0371] First, the UE sends a registration request message to the network, where the UE may include one or more pieces of identification information among the first to third pieces of identification information in the registration request message.

[0372] Here, the UE may indicate to the network the contents indicated by the identification information included in the registration request message by including one or more of the first to third identification information in the registration request message and sending it.

[0373] Specifically, the UE may indicate the SNPN ID to the network by sending the first identification information.

[0374] The UE may also indicate to the network whether it supports CAG by transmitting the second identification information. The UE may also indicate to the network that it supports CAG by transmitting the second identification information. The UE may also indicate to the network that it does not support CAG by transmitting the second identification information.

[0375] The UE may also indicate to the network that it supports the hosting network by sending the third identification information.

[0376] Then, the network sends a registration rejection message to the UE, where the network may include one or more of the 17th to 23rd identities in the registration rejection message.

[0377] Here, the network may include one or more of the identification information items 17 to 23 in the registration rejection message and send it to indicate to the UE the contents indicated by the identification information included in the registration rejection message.

[0378] Specifically, the network may transmit the seventeenth identification to indicate to the UE that it has not been authorized for the hosting network. The network may also transmit the seventeenth identification to indicate to the UE that it has not been authorized for this hosting network.

[0379] The network may also indicate to the UE that the SNPN is temporarily not authorized by transmitting the eighteenth identification information. The network may also indicate to the UE that the SNPN indicated by the first identification information is temporarily not authorized by transmitting the eighteenth identification information. The network may also indicate to the UE that the SNPN is temporarily not authorized by transmitting the eighteenth identification information.

[0380] The network may also indicate to the UE that it has been permanently disauthorized for the SNPN by transmitting a nineteenth identity. The network may also indicate to the UE that it has been permanently disauthorized for the SNPN indicated by the first identity by transmitting a nineteenth identity. The network may also indicate to the UE that it has been permanently disauthorized for the SNPN by transmitting a nineteenth identity.

[0381] The network may also indicate to the UE the list containing the CAG ID by sending the 20th identification information.

[0382] Alternatively, the network may transmit a registration rejection message to the UE, thereby indicating the content of each piece of identification information included in the registration rejection message. Alternatively, the network may transmit each piece of identification information to the UE, thereby indicating the content of each piece of identification information.

[0383] In addition, the network may select and decide whether to include one or more of the identification information from the 17th to 23rd identification information in the registration rejection message based on the status of the UE, and / or information received from the local service provider, and / or information received from the UDM, and / or information received from the AUSF, etc.

[0384] The network may also determine whether to send the registration rejection message and / or the respective identification information based on the state of the UE, and / or information received from the local service provider, and / or information received from the UDM, and / or information received from the AUSF, etc. The network may also send the registration rejection message and / or the respective identification information based on information received from the local service provider and / or the UDM. The network may also send the registration rejection message and / or the respective identification information based on information received from the AUSF indicating that the local service is to be terminated.

[0385] The UE then receives a registration rejection message. The UE may also receive a registration rejection message from the network, the registration rejection message including one or more of the 17th to 23rd identities.

[0386] Furthermore, the UE may store the identification information received together with the registration rejection message based on the reception of the registration rejection message, or may recognize the network's decision. Also, the UE may recognize the content of the identification information received together with the registration rejection message based on the reception of the registration rejection message.

[0387] Specifically, if the UE receives the 17th identification, it may recognize that it has not been authorized for the hosting network.

[0388] The UE may also store the first identity in a list of prohibited hosting networks based on the seventeenth identity. The UE may also store the first identity in a list of prohibited hosting networks based on the seventeenth identity if the registration request message is for a localized service. Here, the list of prohibited hosting networks may be the same as the twenty-third identity.

[0389] The UE may also not store the first identity in the temporarily banned SNPN list and / or the permanently banned SNPN list based on the seventeenth identity. The UE may also not store the first identity in the temporarily banned SNPN list and / or the permanently banned SNPN list based on the seventeenth identity if the registration request message is for a localized service.

[0390] The UE may also replace the twentieth, and / or twenty-second, and / or twenty-third identities stored in the UE with the received twentieth, and / or twenty-second, and / or twenty-third identities based on the seventeenth or twenty-first identity. The UE may also replace the twentieth, and / or twenty-second, and / or twenty-third identities stored in the UE with the received twentieth, and / or twenty-second, and / or twenty-third identities based on the seventeenth or twenty-first identity if the registration request message is for a localized service in the PNI-NPN. In other words, the UE may replace the twentieth, and / or twenty-second, and / or twenty-third identities stored in the UE with the received twentieth, and / or twenty-second, and / or twenty-third identities based on the seventeenth or twenty-first identity if the registration request message is for a hosting network as the PNI-NPN.

[0391] Furthermore, the UE may replace the 20th, and / or the 22nd, and / or the 23rd identities stored in the UE with the received 20th, and / or the 22nd, and / or the 23rd identities based on the 17th or the 21st identity if the UE supports a hosting network. In other words, the UE may replace the 20th, and / or the 22nd, and / or the 23rd identities stored in the UE with the received 20th, and / or the 22nd, and / or the 23rd identities based on the 17th or the 21st identity if the UE supports a localized service.

[0392] Furthermore, the UE may replace entries for serving VPLMNs having the 20th and / or 22nd and / or 23rd identities stored in the UE with entries for serving VPLMNs having the received 20th and / or 22nd and / or 23rd identities based on the 17th or 21st identity. Furthermore, the UE may replace entries for serving VPLMNs having the 20th and / or 22nd and / or 23rd identities stored in the UE with entries for serving VPLMNs having the received 20th and / or 22nd and / or 23rd identities based on the 17th or 21st identity if the registration request message is for localized service in the PNI-NPN. In other words, based on the 17th or 21st identity, if the registration request message is for a hosting network as a PNI-NPN, the UE may replace the serving VPLMN entry for the 20th, and / or 22nd, and / or 23rd identity stored in the UE with the serving VPLMN entry for the received 20th, and / or 22nd, and / or 23rd identity.

[0393] Furthermore, if the UE supports a hosting network based on the 17th or 21st identity, the UE may replace entries for serving VPLMNs with the 20th, 22nd, and / or 23rd identities stored in the UE with entries for serving VPLMNs with the received 20th, 22nd, and / or 23rd identities. In other words, if the UE supports localized services based on the 17th or 21st identity, the UE may replace entries for serving VPLMNs with the 20th, 22nd, and / or 23rd identities stored in the UE with entries for serving VPLMNs with the received 20th, 22nd, and / or 23rd identities.

[0394] The UE may also delete the 20th, 22nd, and / or 23rd identities stored in the UE based on the 17th or 21st identity. The UE may also delete the 20th, 22nd, and / or 23rd identities stored in the UE based on the 17th or 21st identity if the registration request message is for a local service in the PNI-NPN. In other words, the UE may delete the 20th, 22nd, and / or 23rd identities stored in the UE based on the 17th or 21st identity if the registration request message is for a hosting network as the PNI-NPN.

[0395] Furthermore, the UE may delete the 20th, 22nd, and / or 23rd identities stored in the UE if the UE supports a hosting network based on the 17th or 21st identity. In other words, the UE may delete the 20th, 22nd, and / or 23rd identities stored in the UE if the UE supports a localized service based on the 17th or 21st identity.

[0396] Furthermore, when the UE receives the 18th identification information, it may recognize that it has been temporarily not authorized for the SNPN. Furthermore, when the UE receives the 18th identification information, it may recognize that it has been temporarily not authorized for the SNPN indicated by the first identification information. Furthermore, when the UE receives the 18th identification information, it may recognize that it has been temporarily not authorized for this SNPN.

[0397] The UE may also store the first identity in a list of SNPNs that are temporarily prohibited for localized service based on the eighteenth identity. The UE may also store the first identity in a list of SNPNs that are temporarily prohibited for localized service based on the eighteenth identity, if the registration request message is for localized service at the SNPN. In other words, the UE may store the first identity in a list of SNPNs that are temporarily prohibited for localized service based on the eighteenth identity, if the registration request message is for a hosting network as the SNPN.

[0398] Furthermore, the UE may store the first identity in a list of SNPNs that are temporarily prohibited for localized services based on the eighteenth identity, if the UE supports a hosting network. In other words, the UE may store the first identity in a list of SNPNs that are temporarily prohibited for localized services based on the eighteenth identity, if the UE supports localized services.

[0399] Furthermore, when the UE receives the 19th identification information, the UE may recognize that it has not been permanently authorized for the SNPN. Furthermore, when the UE receives the 19th identification information, the UE may recognize that it has not been permanently authorized for the SNPN indicated by the first identification information. Furthermore, when the UE receives the 19th identification information, the UE may recognize that it has not been permanently authorized for this SNPN.

[0400] The UE may also store the first identity in a list of SNPNs that are permanently barred for localized service based on the nineteenth identity. The UE may also store the first identity in a list of SNPNs that are permanently barred for localized service based on the nineteenth identity, if the registration request message is for localized service at the SNPN. In other words, the UE may store the first identity in a list of SNPNs that are permanently barred for localized service based on the nineteenth identity, if the registration request message is for a hosting network as the SNPN.

[0401] The UE may also store the first identity in a list of SNPNs that are permanently prohibited for localized services based on the nineteenth identity and if the UE supports a hosting network. In other words, the UE may store the first identity in a list of SNPNs that are permanently prohibited for localized services based on the nineteenth identity and if the UE supports localized services.

[0402] Furthermore, when the UE receives the 20th identification information, the UE may replace the 20th identification information stored in the UE with the received 20th identification information. Furthermore, when the UE receives the 20th identification information, the UE may replace the 20th identification information stored in the UE with the received 20th identification information based on the 17th or 21st identification information.

[0403] Furthermore, when the UE receives the 21st identification information, the UE may recognize that it has not been authorized for the CAG. Furthermore, when the UE receives the 21st identification information, the UE may recognize that it has been authorized for only the CAG cell.

[0404] Furthermore, when the UE receives the 22nd identification information, the UE may replace the 22nd identification information stored in the UE with the received 22nd identification information. Furthermore, when the UE receives the 22nd identification information, the UE may replace the 22nd identification information stored in the UE with the received 22nd identification information based on the 17th or 21st identification information.

[0405] Furthermore, when the UE receives the 23rd identification information, the UE may replace the 23rd identification information stored in the UE with the received 23rd identification information. Furthermore, when the UE receives the 23rd identification information, the UE may replace the 23rd identification information stored in the UE with the received 23rd identification information based on the 17th or 21st identification information.

[0406] Furthermore, when the UE receives a registration rejection message, the UE may recognize the content of each piece of identification information included in the registration rejection message. Furthermore, when the UE receives each piece of identification information, the UE may recognize the content of each piece of identification information.

[0407] The UE may perform the above behavior after receiving a registration reject message, or after receiving one or more of the 17th to 23rd identities.

[0408] Furthermore, when the UE receives a registration rejection message, the UE may perform the behavior it performs when it receives each piece of identification information included in the registration rejection message.

[0409] 5. Variations 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 one aspect of the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a random access memory (RAM), a non-volatile memory such as a flash memory, a hard disk drive (HDD), or another storage device system.

[0410] 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 loaded 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 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.

[0411] 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 circuit technologies that replace current integrated circuits.

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

[0413] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications 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]

[0414] 1. Mobile communication systems 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access Network_A (E-UTRAN) 90 Core Network_A 120 Access Network_B (5G AN) 122 gNB 130 UPF 132 SMF 140 AMF 150 UDM 160 PCF 190 Core Network_B 235 UPF_A 239 UPF_C

Claims

1. User Equipment (UE), The UE includes a transceiver unit and a control unit; The transmitting / receiving unit Sending a registration request message including the first identification information and the second identification information; the first identification information is information for identifying an SNPN, the second identification information is information indicating that a hosting network is supported; receiving a registration reject message including a first cause value; the first reason value is a reason value indicating that the hosting network was not authorized; The control unit stores the first identification information in a prohibited hosting network list if the registration request message is for a local service in an SNPN based on the first reason value.

2. 2. The UE of claim 1, wherein the controller is configured to not store the first identity in a temporarily prohibited SNPN list and / or a permanently prohibited SNPN list if the registration request message is for a local service in an SNPN based on the first reason value.

3. User Equipment (UE), The UE includes a transceiver unit and a control unit; The transmitting / receiving unit Sending a registration request message including the first identification information and the second identification information; the first identification information is information for identifying an SNPN, the second identification information is information indicating that a hosting network is supported; receiving a registration reject message including a first cause value or a second cause value; the first reason value is a reason value indicating that the SNPN is temporarily not authorized; the second reason value is a reason value indicating that the SNPN has been permanently disapproved; based on the first reason value, the control unit stores the first identity in a list of SNPNs temporarily prohibited for local service if the registration request message is for local service at the SNPN; Based on the second reason value, the control unit stores the first identity in a list of SNPNs permanently prohibited for local services if the registration request message is for local services in an SNPN.

4. User Equipment (UE), The UE includes a transceiver and a controller; The transmitting / receiving unit Sending a registration request message including the first identification information and the second identification information; the first identification information is information indicating whether a Closed Access Group (CAG) is supported; the second identification information is information indicating that a hosting network is supported; receiving a registration reject message including a first cause value and third identification information; the first reason value is a reason value indicating that authorization was denied to the hosting network; The third identification information is a list including CAG IDs, The UE is characterized in that, based on the first reason value, if the registration request message is for a local service in a PNI-NPN, the control unit replaces the third identification information stored in the UE with the received third identification information.

Images