User equipment (UE)

Abstract

This UE is provided with a transmission / reception unit, a control unit, and a storage unit. When the UE operates in an SNPN access operation mode, the storage unit stores a first counter, which is an SNPN-specific trial counter for non-3GPP access, and which is also used when the UE is directly connected to the SNPN via the non-3GPP access, and when the UE operates in the SNPN access operation mode, the storage unit stores a second counter, which is used when the UE is directly connected to the SNPN via the non-3GPP access, which is used when the UE is connected to the SNPN via the non-3GPP access, and which is used when the UE is connected to the SNPN via the non-3GPP access. The control unit increments the first counter when the transmission / reception unit receives first control information via the non-3GPP access, the first control information being a rejection reason value indicating that an N1 mode is not allowed, or a 5GCN connection via the non-3GPP access is not allowed, or the SNPN is temporarily not allowed, or the SNPN is permanently not allowed. The first control information further comprises a login rejection message which does not guarantee integrity or a service rejection message which does not guarantee integrity.

Description

Technical Field

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

[0002] In 3GPP (3rd Generation Partnership Project), new processes and functions in the system architecture for supporting 5GS (5G System), a fifth generation (5G) mobile communication system, are being studied, discussed, and specifications are being formulated (see non-patent documents 1 to 4). For NPN (Non-Public Network), which was discussed up to Release 17, further expansion of its functions is being discussed in Release 18. Prior art literature Non-patent literature

[0003] Non-patent literature 1: 3GPP TS23.501V17.5.0 (2022-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; SystemArchitecture for the 5G System; Stage 2 (Release 17) Non-patent document 2: 3GPP TS23.502V17.5.0 (2022-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 17) Non-patent document 3: 3GPP TS24.501V17.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 TR23.700-08V1.0.0(2022-05); 3rd GenerationPartnership Project; Technical Specification Group Services and SystemAspects; Study on enhanced support of Non-Public Networks; Phase 2(Release 18) Summary of the invention Problem that the invention aims to solve

[0004] In order to provide various services in 5GS (5G System), 5GCN (5G Core Network) as a new core network is being studied. Currently, for 5GS, the functional expansion of NPN (Non-Public Network) which is a non-public network that specific users can connect to and use, which has been studied so far, is being studied (see Non-Patent Document 4).

[0005] In the past, only connection via PLMN (Public Land Mobile Network) and / or DN (Data Network) was supported for connection from UE (User Equipment) via non-3GPP (non-3GPP) access to SNPN (Stand-alone Non-Public Network) or SNPN service, which is a form of NPN. On the other hand, in the research on the expansion of NPN, as a connection to SNPN or SNPN service via non-3GPP access, in addition to the connection methods so far, direct connection to SNPN or SNPN service via non-3GPP access is also supported. However, the details of the conditions, procedures and methods related to the processing of trial counters and / or event counters when connecting to SNPN service via existing PLMN are not clear.

[0006] The present invention is made in view of the situation as described above, and provides a method and process for properly maintaining and processing trial counters and event counters in a connection from a UE via a PLMN to a SNPN and a direct connection via a non-3GPP access being studied, as well as the information and processes sent and received between the UE and the network required to execute these. Technical Solution

[0007] The UE (User Equipment) of an embodiment of the present invention includes a transceiver unit, a control unit and a storage unit, wherein, when the UE operates in an SNPN (Stand-alone Non-Public Network) access operation mode, the storage unit stores a first counter, the first counter is a trial counter specific to the SNPN for non-3GPP access, and the first counter is also used when directly connecting to the SNPN via the non-3GPP access, and the control unit increments the first counter when the transceiver unit receives first control information via the non-3GPP access, the first control information is a rejection reason value indicating that the N1 mode is not allowed or the 5GCN connection via the non-3GPP access is not allowed or the SNPN is temporarily not allowed or permanently not allowed, and the first control information is also included in a login rejection message that does not guarantee integrity or a service rejection message that does not guarantee integrity. Beneficial Effects

[0008] According to one embodiment of the present invention, a method can be provided for maintaining and / or processing trial counters and event counters corresponding to the connection form by a UE in connections classified as connections via non-3GPP access, connections to SNPN via PLMN, and direct connections via non-3GPP access. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 This is a diagram illustrating an overview of a mobile communication system. Figure 2 This is a diagram illustrating the detailed structure of a mobile communication system. Figure 3 This is a diagram illustrating the device structure of UE. Figure 4 This is a diagram illustrating the structure of the access network device (gNB) in 5GS. Figure 5 This is a diagram that illustrates the structure of the core network device (AMF / SMF / UPF / N3IWF) in 5GS. Figure 6 This is a diagram for explaining the login process. DETAILED DESCRIPTION

[0010] Hereinafter, the best mode for carrying out the present invention will be described with reference to the accompanying drawings. It should be noted that in this embodiment, an embodiment of a mobile communication system in which the present invention is applied will be described as an example. [1. System Overview]

[0011] Here, each mobile communication system is described.

[0012] first, Figure 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment. Figure 2 It is a diagram for explaining the detailed structure of the mobile communication system 1.

[0013] Figure 1 The communication system 1 composed of UE (User Equipment)_10, access network_B120, core network_B200, and DN (Data Network)_250 is recorded.

[0014] Here, and below, these symbols may be omitted for description. Figure 1 The access network_B120 can be a 3GPP access or a non-3GPP access, but in this specification, it is assumed to be a non-3GPP access unless otherwise specified. Figure 1 In the communication system 1, it is assumed that the UE is directly connected to the SNPN service (hereinafter also referred to as the service provided by the SNPN, the SNPN service or simply referred to as the SNPN) via a non-3GPP access. In other words, when the UE is directly connected to the SNPN service, in the SNPN, after the UE performs a login process on the core network _B200 via a non-3GPP access (access network_B120) and becomes logged in, it uses the PDU session established by executing the PDU session establishment process (hereinafter also referred to as the first PDU session) to become able to communicate with DN_250. At this time, it can be said that the UE is in a state of being connected to the SNPN service. In addition, it can also be said that the access network_B120 and / or the core network_B200 and / or DN_250 are networks constituting the SNPN. In addition, it can also be said that the device / network functions included in the access network_B120, the core network_B200 and the DN_250 are devices / network functions constituting the SNPN. The communication system 1 refers to such a communication system.

[0015] also, Figure 2 The device / network functions such as UE_A10, AMF_140, SMF_132, UPF_130, N3IWF_240, DN_250 and the interfaces that connect them are recorded.

[0016] Here, in the following, these symbols are sometimes omitted for description. It should be noted that AMF, SMF, UPF, and N3IWF may be included in the core network_B200. Figure 2 Although not described in the document, a base station device or access point is provided between the UE and the N3IWF. The base station device or access point may be included in the access network.

[0017] In addition, the 5GS (5G System) as a 5G system is composed of UE, access network_B and core network_B, but it can also further include DN. It should be noted that the core network_B can be a PLMN, or it can be a SNPN (Stand-aloneNon-Public Network) or a PNI-NPN (Public Network Integrated Non-Public Network). In addition, the access network_B can also be a non-3GPP access network connected to the SNPN.

[0018] UE is a device that can connect to network services via 3GPP access (also known as 3GPP access network, 3GPP AN) and / or non-3GPP access (non-3GPP access, also known as non-3GPP access network, non-3GPP AN). UE can be a terminal device that can perform wireless communication, such as a portable phone or a smart phone, or a terminal device that can connect to EPS (Evolved Packet System) and 5GS, which are 4G systems. UE can have UICC (Universal Integrated Circuit Card) and eUICC (Embedded UICC). It should be noted that UE can be expressed as a user device or as a terminal device. Moreover, UE can also be ME (Mobile Equipment).

[0019] In addition, access network_B corresponds to the 5G access network (5G AN). 5G AN is composed of NG-RAN (NG Radio Access Network: NG wireless access network) and / or non-3GPP access network. One or more gNB (NRNodeB: NR Node B) 122 are configured in NG-RAN. It should be noted that, below, the gNB122 is sometimes recorded with omitted symbols, such as eNB. The gNB is a node that provides the NR (New Radio: New Radio) user plane and control plane to the UE, and is a node connected to the 5GCN via the NG interface (including the N2 interface or the N3 interface). That is, the gNB is a base station device redesigned for 5GS, and has different functions from the base station device (eNB) used in the EPS as a 4G system. In addition, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

[0020] In addition, the non-3GPP access network can be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network can be a non-3GPP access network such as a public wireless LAN that does not perform security management within the access network. On the other hand, the trusted non-3GPP access network is also called TNAN (Trusted Non-3GPP Access Network), and may also have TNAP (trusted non-3GPP access point) and TNGF (trusted non-3GPP gateway function).

[0021] In addition, NG-RAN is referred to as 3GPP access below. In addition, wireless LAN access network and non-3GPP AN are sometimes referred to as non-3GPP access. In addition, nodes configured in access network_B are sometimes collectively referred to as NG-RAN nodes.

[0022] In addition, hereinafter, access network_B and / or the devices included in access network_B are sometimes referred to as access network or access network devices.

[0023] In addition, core network_B corresponds to 5GCN (5G Core Network). In 5GCN, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), UDM (Unified Data Management), etc. are configured. Here, 5GCN can be expressed as 5GC.

[0024] In addition, below, core network_B and the devices included in core network_B are sometimes referred to as core network or core network devices or devices within the core network.

[0025] The core network (Core Network_B) can be an IP mobile communication network operated by a mobile communication operator (Mobile Network Operator; MNO) that connects the access network (Access Network_B) with the PDN and / or DN, or it can be a core network used by a mobile communication operator that operates and manages the mobile communication system 1, or it can be a core network used by virtual mobile communication operators and virtual mobile communication service providers such as MVNO (Mobile Virtual Network Operator) and MVNE (Mobile Virtual Network Enabler).

[0026] The core network (core network_B) and the access network (access network_B) may differ for each mobile communication operator.

[0027] In addition, the DN may be configured as a packet data service network or may be configured for each service. Furthermore, the DN may include a connected communication terminal. Therefore, the connection with the DN may be the connection with a communication terminal or a server device configured in the DN. Furthermore, the sending and receiving of user data with the DN may be the sending and receiving of user data with a communication terminal or a server device configured in the DN.

[0028] In addition, hereinafter, at least a part of the access network_B, the core network_B, the DN, and / or one or more devices included therein are sometimes referred to as a network or a network device. That is, the network and / or the network device sending and receiving messages and / or executing a process means that at least a part of the access network_B, the core network_B, the DN, and / or one or more devices included therein send and receive messages and / or execute a process.

[0029] In addition, the UE can be connected to the access network. In addition, the UE can be connected to the core network via the access network. Moreover, the UE can be connected to the DN via the access network and the core network. That is, the UE can send and receive (communicate) user data between the DN. When sending and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication can be used.

[0030] Here, IP communication refers to data communication using IP, in which data is sent and received through IP packets. An IP packet consists of an IP header and a payload portion. The payload portion may include data sent and received by devices / functions included in EPS and devices / functions included in 5GS. In addition, non-IP communication refers to data communication that does not use IP, in which data is sent and received in a form different from the structure of IP packets. For example, non-IP communication may be data communication achieved by sending and receiving application data that is not assigned an IP header, or may be assigned other headers such as a MAC header, Ethernet (registered trademark) frame header, etc. to send and receive user data sent and received by the UE.

[0031] In addition, the access network_B, core network_B, and DN may have configurations not recorded in Figure 2 For example, AUSF (Authentication Server Function), AAA (Authentication, authorization, and accounting) server (AAA-S) may be included in the core network_B and / or DN. The AAA server may be configured outside the core network.

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

[0033] In addition, the AAA server is a device that is directly connected to the AUSF or indirectly connected via other network devices and has authentication, authorization and billing functions. The AAA server can be a network device within the core network. It should be noted that the AAA server can be included in the PLMN or SNPN but not in the core network_B. That is, the AAA server can be either a core network device or a device outside the core network. For example, the AAA server can be a server device within the PLMN or SNPN managed by a third party (3rd Party).

[0034] It should be noted that in Figure 2 In order to simplify the drawings, each device / function is recorded as one, but multiple similar devices / functions may be configured in the mobile communication system 1. Specifically, multiple devices / functions such as UE10, 5G AN120, AMF140, UPF130, SMF132, PCF160 and / or UDM150 may be configured in the mobile communication system 1. [2. Configuration of each device]

[0035] Next, the configuration of each device (UE and / or access network device and / or core network device) used in each embodiment is described using the accompanying drawings. It should be noted that each device can be configured as physical hardware, as logical (virtual) hardware configured on general hardware, or as software. In addition, at least part (including all) of the functions of each device can also be configured as physical hardware, logical hardware, or software.

[0036] It should be noted that each storage unit (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) in each device and each function that appears below is composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each storage unit can not only store the information originally set from the factory stage, but also store various information sent and received between devices / functions other than its own device and its own function (for example, UE and / or access network device and / or core network device and / or PDN and / or DN). In addition, each storage unit can store identification information, control information, flags, parameters, etc. included in the control messages sent and received in various communication processes described later. In addition, each storage unit can also store this information for each UE. In addition, each storage unit can store control messages and user data sent and received between the devices / functions included in 5GS and / or EPS when intercommunication between 5GS and EPS is performed. At this time, not only the data sent and received via the N26 interface can be stored, but also the data not sent and received via the N26 interface can be stored. [2.1. UE device configuration]

[0037] First, use Figure 3 An example of the configuration of a UE (User Equipment) is described. The UE is composed of a control unit_A300, an antenna 310, a transceiver_A320, and a storage unit_A340. The control unit_A300, the transceiver_A320, and the storage unit_A340 are connected via a bus. The transceiver_A320 is connected to the antenna 310.

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

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

[0040] Reference Figure 2 To explain in detail, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver_A320. In addition, the UE can communicate with the base station device (gNB) in the 5G AN by using the transceiver_A320. In addition, the UE can send and receive NAS (Non-Access-Stratum: non-access layer) messages with the AMF via the N1 interface by using the transceiver_A320. However, since the N1 interface is a logical interface, the communication between the UE and the AMF is actually carried out via the 5G AN.

[0041] The storage unit_A340 is a functional unit for storing programs, user data, control information, etc. required for various actions of the UE. [2.1.1.gNB device configuration]

[0042] Next, use Figure 4 The following describes an example of the gNB device configuration. The gNB is composed of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, the network connection unit_B520, the transceiver unit_B530, and the storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0043] The control unit_B500 is a functional unit that controls the overall actions and functions of the gNB. The control unit_B500 reads and executes various programs stored in the storage unit_B540 as needed, thereby realizing various processes in the gNB.

[0044] The network connection unit_B520 is a functional unit for gNB to communicate with AMF and / or UPF. That is, the gNB can use the network connection unit_B520 to send and receive user data and / or control information between the AMF and / or UPF.

[0045] The transceiver_B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can use the transceiver_B530 to send and receive user data and / or control information between the UE.

[0046] Reference Figure 2To explain in detail, the gNB in ​​the 5G AN can communicate with the AMF via the N2 interface by using the network connection unit_B520, and can communicate with the UPF via the N3 interface. In addition, the gNB can communicate with the UE by using the transceiver unit_B530.

[0047] Storage unit_B540 is a functional unit used to store programs, user data, control information, etc. required for various actions of gNB. [2.1.2.AMF device configuration]

[0048] Next, use Figure 5 The following describes an example of the device configuration of AMF. AMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. AMF can be a node that operates a control plane.

[0049] The control unit_B700 is a functional unit that controls the overall operation and functions of the AMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the AMF.

[0050] The network connection unit_B720 is a functional unit for connecting the AMF with the base station device (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF in the 5G AN. That is, the AMF can use the network connection unit_B720 to send and receive user data and / or control information between the base station device (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF in the 5G AN. That is, the network connection unit_B720 can be a transceiver for sending and receiving user data and / or control information.

[0051] Reference Figure 2 To explain in detail, the AMF in 5GCN can communicate with gNB via the N2 interface, can communicate with UDM via the N8 interface, can communicate with SMF via the N11 interface, and can communicate with PCF via the N15 interface by using the network connection part_A620. In addition, the AMF can send and receive NAS messages with the UE via the N1 interface by using the network connection part_A620. However, since the N1 interface is a logical interface, the communication between the UE and the AMF is actually carried out via the access network_B or non-3GPP AN or 5G AN.

[0052] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of AMF.

[0053] It should be noted that AMF has the following functions: the function of exchanging control messages with RAN using N2 interface, the function of exchanging NAS messages with UE using N1 interface, the function of encrypting and integrity protecting NAS messages, the registration management (RM) function, the connection management (CM) function, the reachability management function, the mobility management (Mobility management) function of UE, etc., the function of transmitting SM (Session Management) messages between UE and SMF, the access authentication (Access Authentication, Access Authorization) function, the security anchor function (SEA; Security Anchor Functionality), the security context management (SCM; Security Context Management) function, the function of supporting the N2 interface for N3IWF (Non-3GPP Interworking Function: non-3GPP interworking function), the function of supporting the sending and receiving of NAS signals with UE via N3IWF, the function of authenticating UE connected via N3IWF, etc.

[0054] In addition, the RM state of each UE is managed in the login management. The RM state can be synchronized between the UE and the AMF. As the RM state, there are a non-logged-in state (RM-DEREGISTERED state) and a logged-in state (RM-REGISTERED state). In the RM-DEREGISTERED state, since the UE has not logged in to the network, the UE context in the AMF does not have valid location information and routing information for the UE, so the AMF is in a state where the UE cannot be reached. In addition, in the RM-REGISTERED state, the UE has logged in to the network, so the UE can receive services that require login to the network. It should be noted that the RM state can be expressed as a 5GMM state (5GMM state). In this case, the RM-DEREGISTERED state can be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state can be expressed as a 5GMM-REGISTERED state.

[0055] In other words, 5GMM-REGISTERED can be a state where each device has established a 5GMM context, or a state where each device has established a PDU session context. It should be noted that when each device is 5GMM-REGISTERED, UE_A10 can start sending and receiving user data and control messages, and can also respond to paging. Moreover, it should be noted that when each device is 5GMM-REGISTERED, UE_A10 can perform login procedures and / or service request procedures other than the login procedure for initial login.

[0056] Moreover, 5GMM-DEREGISTERED can be a state where each device has not established a 5GMM context, a state where the location information of UE_A10 is not grasped by the network, or a state where the network cannot reach UE_A10. It should be noted that when each device is 5GMM-DEREGISTERED, UE_A10 can start the login process or establish a 5GMM context by executing the login process.

[0057] In addition, the CM state of each UE is managed in the connection management. The CM state can be synchronized between the UE and the AMF. As CM states, there are 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 (NAS signaling connection) established with the AMF via the N1 interface. In addition, in the CM-IDLE state, the UE does not have a connection (N2connection) of the N2 interface and a connection (N3connection) of the N3 interface. On the other hand, in the CM-CONNECTED state, it has a NAS signaling connection (NAS signaling connection) established with the AMF via the N1 interface. In addition, in the CM-CONNECTED state, the UE may also have a connection (N2connection) of the N2 interface and / or a connection (N3connection) of the N3 interface.

[0058] Moreover, in connection management, it can also be divided into CM state in 3GPP access and CM state in non-3GPP access for management. In this case, as the CM state in 3GPP access, there can be a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over3GPP access). Moreover, as the CM state in non-3GPP access, there can be a non-connected state in non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state in non-3GPP access (CM-CONNECTEDstate over non-3GPP access). It should be noted that the non-connected state can be expressed as an idle mode, and the connected state mode can be expressed as a connected mode.

[0059] It should be noted that the CM state can also be expressed as 5GMM mode. In this case, the non-connected state can also be expressed as 5GMM non-connected mode (5GMM-IDLE mode), and the connected state can also be expressed as 5GMM connected mode (5GMM-CONNECTED mode). Moreover, the non-connected state in 3GPP access can also be expressed as 5GMM non-connected mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access can also be expressed as 5GMM connected mode in 3GPP access (5GMM-CONNECTED mode over 3GPP access). Moreover, the non-connected state in non-3GPP access can also be expressed as 5GMM non-connected mode in non-3GPP access (5GMM-IDLE modeover non-3GPP access), and the connected state in non-3GPP access can also be expressed as 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). It should be noted that the 5GMM non-connected mode can be expressed as an idle mode, and the 5GMM connected mode can be expressed as a connected mode.

[0060] In addition, more than one AMF can be configured in the core network_B. In addition, AMF can be an NF that manages more than one NSI (Network Slice Instance). In addition, AMF can also be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among multiple NSIs.

[0061] It should be noted that N3IWF is a device and / or function configured between non-3GPP access and 5GCN when the UE is connected to 5GS via non-3GPP access. [2.1.3. SMF device configuration]

[0062] Next, use Figure 5 The following describes an example of the device configuration of SMF 132. SMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. SMF can be a node that operates a control plane.

[0063] The control unit_B700 is a functional unit that controls the entire operation and function of the SMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the SMF.

[0064] The network connection unit_B720 is a functional unit for connecting the SMF with the AMF and / or UPF and / or PCF and / or UDM. That is, the SMF can use the network connection unit_B720 to send and receive user data and / or control information between the AMF and / or UPF and / or PCF and / or UDM.

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

[0066] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of SMF.

[0067] SMF has the following functions: session management functions such as establishment, modification, and release of PDU sessions, IP address allocation and management functions for UE, UPF selection and control functions, UPF setting functions for routing services to the appropriate destination (sending destination), functions for sending and receiving the SM part of NAS messages, functions for notifying that downlink data has arrived (Downlink Data Notification), functions for providing AN-specific (each AN's) SM information sent to AN via AMF and through the N2 interface, functions for determining the SSC mode (Session and Service Continuity mode) for the session, roaming functions, etc. [2.1.4. UPF device configuration]

[0068] Next, use Figure 5 The following describes an example of the device configuration of the UPF. The UPF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. The UPF may be a node that operates the control plane.

[0069] The control unit_B700 is a functional unit that controls the overall operation and functions of the UPF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the UPF.

[0070] The network connection unit_B720 is a functional unit for connecting the UPF to the base station device (gNB) and / or SMF and / or DN in the 5G AN. That is, the UPF can use the network connection unit_B720 to send and receive user data and / or control information between the base station device (gNB) and / or SMF and / or DN in the 5G AN.

[0071] Reference Figure 2 To explain in detail, the UPF in 5GCN can communicate with gNB via the N3 interface, communicate with SMF via the N4 interface, communicate with DN via the N6 interface, and communicate with other UPFs via the N9 interface by using the network connection unit _A620.

[0072] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of UPF.

[0073] UPF has the following functions: serving as an anchor point for intra-RAT mobility or inter-RAT mobility, serving as an external PDU session point for interconnecting with DN (that is, serving as a gateway between DN and core network_B to transmit user data), routing and transmission of packets, UL CL (Uplink Classifier) ​​function that supports routing of multiple service flows for one DN, branching point function that supports multi-homed PDU sessions, QoS (Quality of Service) processing function for user plane, verification function of uplink services, triggering buffering of downlink packets, downlink data notification function, etc.

[0074] In addition, UPF can be a gateway for IP communication and / or non-IP communication. In addition, UPF can have the function of transmitting IP communication and can also have the function of converting non-IP communication and IP communication. Moreover, the configured multiple gateways can be gateways connecting the core network_B with a single DN. It should be noted that UPF can have connectivity with other NFs and can also be connected to each device via other NFs.

[0075] It should be noted that the user plane is user data sent and received between the UE and the network. The user plane can be sent and received using a PDU session. Moreover, in the case of 5GS, the user plane can also be sent 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 also be expressed as U-Plane or UP.

[0076] In addition, the control plane is a control message sent and received for communication control of the UE, etc. In 5GS, the control plane can also use the interface between the UE and the NG RAN or each device for non-3GPP access and the N2 interface for sending and receiving. In the following, the control plane can be expressed as Control Plane or C-Plane.

[0077] Furthermore, the user plane (U-Plane, User Plane; UP) can be a communication path for sending and receiving user data, and can be composed of multiple bearers. Furthermore, the control plane (C-Plane, Control Plane; CP) can be a communication path for sending and receiving control messages, and can be composed of multiple bearers. [2.1.5. Device composition of N3IWF]

[0078] Next, use Figure 5 The device / functional configuration example of N3IWF used in each embodiment is described. N3IWF is configured in the core network when the UE is connected to 5GS via an untrusted non-3GPP access. N3IWF is composed of a control unit 700, a network connection unit 720, and a storage unit 740. The control unit 700, the network connection unit 720, and the storage unit 740 are connected via a bus.

[0079] The control unit 700 is a functional unit that controls the overall actions and functions of the N3IWF. It should be noted that the control unit 700 can also process all functions that other functional units (network connection unit 720, storage unit 740) in the N3IWF do not have. The control unit 700 implements various processes in the N3IWF by reading various programs stored in the storage unit 740 as needed and executing them.

[0080] The network connection unit_720 is a functional unit for N3IWF to communicate with a base station device or an access point and / or AMF and / or UPF. That is, N3IWF can use the network connection unit_720 to send and receive control information and / or user data between the base station device or the access point. In addition, N3IWF can use the network connection unit_720 to send and receive control information and / or user data between AMF and / or UPF, etc.

[0081] That is, the N3IWF can communicate with the base station device or access point via the Y2 interface by using the network connection unit 720. In addition, the N3IWF can communicate with the AMF via the N2 interface. In addition, the N3IWF can communicate with the UPF via the N3 interface.

[0082] It should be noted that the above only records the communication between N3IWF and representative devices / functions. N3IWF can of course also communicate with devices / functions other than the above, that is, core network devices other than the above.

[0083] The storage unit 740 is a functional unit for storing programs, user data, control information, etc. required for various actions of N3IWF.

[0084] It should be noted that the N3IWF has the following functions: a function of establishing an IPsec tunnel with the UE, a function of terminating the N2 interface for the control plane, a function of terminating the N3 interface for the user plane, a function of relaying NAS signaling between the UE and the AMF, a function of processing the N2 signaling from the SMF regarding the PDU session and QoS, a function of establishing an IPsec SA (Security Association) for the service supporting the PDU session, a function of relaying user plane packets between the UE and the UPF (including a function of encapsulating / decapsulating packets for IPsec and N3 tunnels), a function of serving as a local mobility anchor point in an untrusted non-3GPP access network, a function of selecting an AMF, etc. All of these functions are controlled by the control unit 700. [2.1.6. Description of other devices and / or functions]

[0085] Next, other devices and / or functions are described.

[0086] TNAN (Trusted Non-3GPP Access Network) is an access network used to provide connections via trusted non-3GPP access to UEs, and can be composed of TNAP (Trusted Non-3GPP Access Point) and TNGF (Trusted Non-3GPP Gateway Function).

[0087] PCF has the function of providing policy rules, etc. PVF is connected to AMF and SMF, and has the function of performing QoS management for data distribution, etc. For example, QoS management of the communication path between UE_A10 and PDN can be performed. In addition, PCF can be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used by each device when sending and receiving user data.

[0088] In addition, UDM has the following functions: authentication credential processing function, user identification processing function, access authentication function, login / mobility management function, subscriber information management (subscription management) function, etc. [2.2. Description of terms used in this embodiment]

[0089] Next, highly specialized terms used in each embodiment and identification information used in the process will be described.

[0090] The network (NW) refers to at least a part of the access network_B, the core network_B, and the DN. In addition, one or more devices included in at least a part of the access network_B, the core network_B, and the DN may also be referred to as a network or a network device. That is, the network performing the sending, receiving, and / or processing of messages may mean that a device in the network (network device and / or control device) performs the sending, receiving, and / or processing of messages. Conversely, the device in the network performs the sending, receiving, and / or processing of messages may mean that the network performs the sending, receiving, and / or processing of messages.

[0091] Furthermore, the network may refer to a PLMN (Public Land Mobile Network), an NPN (Non-Public Network), or a SNPN (Stand-alone Non-Public Network). Furthermore, when the expression is that the UE performs network selection, it may refer to that the UE performs PLMN selection, or it may refer to that the UE performs SNPN selection. It should be noted that in this specification, the access network, core network, PLMN, and SNPN are also referred to as networks or NWs.

[0092] In addition, the SM (Session Management) message (also called NAS (Non-Access-Stratum: non-access layer) SM message) can be a NAS message used in the process for SM, or it can be a control message sent and received between UE_A10 and SMF_132 via AMF_140. Moreover, 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 change request message, a PDU session change command message, a PDU session change complete message, a PDU session change command reject message, a PDU session change reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, etc. Furthermore, the SM process or the SM process may include: a PDU session establishment procedure, a PDU session change procedure, and a PDU session release procedure (UE-requested PDU session release procedure: UE-requested PDU session release procedure). It should be noted that each process can be initiated by the UE or by the NW.

[0093] In addition, the MM (Mobility management) message (or also called NAS MM message) can be a NAS message used for the MM process, or a control message sent and received between UE_A10 and AMF_A140. Moreover, 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. In addition, with regard to the procedures used for MM or MM procedures, it can include: registration procedure, de-registration procedure, generic UE configuration update procedure, authentication, authorization procedure, service request procedure, paging procedure, and notification procedure.

[0094] In addition, 5GS (5G System) services may be connection services provided using the core network B200. Furthermore, 5GS services may be services different from EPS services or services similar to EPS services.

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

[0096] In addition, the PDN (Packet Data Network) type indicates the type of PDN connection, which includes IPv4, IPv6, IPv4v6, and non-IP. When IPv4 is specified, it indicates that IPv4 is used to send and receive data. When IPv6 is specified, it indicates that IPv6 is used to send and receive data. When IPv4v6 is specified, it indicates that IPv4 or IPv6 is used to send and receive data. When non-IP is specified, it indicates that communication is not using IP, but communication is carried out by a communication method other than IP.

[0097] In addition, there are two types of access types: 3GPP access and non-3GPP access. Here, the information indicating the access type can be constituted as an access type information element (Access type Information Element (IE)), for example, it can be the signaling between the UE and the core network or the identification information indicating the access type used in the transmission and reception of user data.

[0098] In addition, a PDU (Protocol Data Unit / Packet Data Unit) session may refer to an association between a DN and a UE that can be defined as providing a PDU connectivity service, but a connectivity established between the UE and an external gateway. The UE establishes a PDU session via the access network_B and the core network_B in the 5GS, thereby being able to use the PDU session to send and receive user data with the DN. Here, the external gateway may refer to a UPF, a SCEF, etc. The UE can use the PDU session to send and receive user data with a device such as an application server configured in the DN.

[0099] It should be noted that each device (UE and / or access network device and / or core network device) can also establish a correspondence between one or more identification information and the PDU session for management. It should be noted that these identification information may include one or more of DNN, QoS rules, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode (SSCmode), and may further include other information. Moreover, in the case of establishing multiple PDU sessions, each identification information corresponding to the PDU session establishment may be the same content or different content.

[0100] In addition, the PDU session can be used for sending and receiving SNPN information in the remote provisioning via the user plane during the UE loading process. It should be noted that the process related to the establishment of the PDU session for loading or loading services and the process of remote provisioning via the user plane will be described in detail later.

[0101] In addition, DNN (Data Network Name) can be identification information for identifying a core network and / or an external network such as a DN. Furthermore, DNN can also be used as information for selecting a gateway such as UPF_130 connected to the core network_B200. Furthermore, DNN can also be equivalent to APN (Access Point Name).

[0102] In addition, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, which includes IPv4, IPv6, Ethernet, and Unstructured. When IPv4 is specified, it means that IPv4 is used to send and receive data. When IPv6 is specified, it means that IPv6 is used to send and receive data. When Ethernet is specified, it means that Ethernet frames are sent and received. In addition, Ethernet can indicate that communication without using IP is performed. When Unstructured is specified, it means that Point-to-Point (P2P) tunnel technology is used to send and receive data to an application server in the DN. As a P2P tunnel technology, for example, UDP / IP encapsulation technology can also be used. It should be noted that in addition to the above, IP can also be included in the PDU session type. IP can be specified when the UE can use both IPv4 and IPv6.

[0103] In addition, PLMN (Public land mobile network) is a communication network that provides mobile wireless communication services. PLMN is a network managed by an operator as a (mobile) communication operator, and the operator can be identified by the PLMN ID. In addition, the operator can also manage more than one PLMN. It should be noted that in this article, PLMN may also refer to PLMN ID. The PLMN that is consistent with the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscriber Identity) can be the Home PLMN (Home PLMN: HPLMN).

[0104] Moreover, the UE may maintain an equivalent HPLMN list (Equivalent HPLMN list) for identifying one or more E-HPLMNs (Equivalent HPLMN) in the USIM (Universal Subscriber Identity Module). A PLMN different from the HPLMN and / or E-HPLMN may be a VPLMN (Visited PLMN or VPLMN; destination PLMN). In addition, the PLMN to which the UE successfully logs in may be an RPLMN (Registered PLMN). The current PLMN may be the PLMN requested by the UE, and / or the PLMN selected by the UE, and / or the RPLMN, and / or the PLMN allowed by the network, and / or the PLMN to which the core network device that sends and receives messages belongs. It should be noted that the services provided by the PLMN may be referred to as PLMN services, and the services provided by the SNPN may be referred to as SNPN services.

[0105] In addition, a network slice (NS) refers to a logical network that provides specific network capabilities and network characteristics. UE and / or network can support network slicing (NW slicing; NS) in 5GS. Sometimes network slicing is also referred to as slicing.

[0106] In addition, a network slice instance (NSI) refers to a network slice formed and configured by a collection of instances (entities) of network functions (NFs) and required resources. Here, NF refers to a processing function in a network, which is adopted or defined in 3GPP. NSI is an entity that constitutes one or more NSs within the core network_B. In addition, NSI can be composed of a virtual NF (Network Function) generated using NST (Network Slice Template).

[0107] Here, NST refers to a logical expression of one or more NFs associated with a resource request for providing the requested communication service or capability. That is, NSI may refer to a collection within the core network_B200 composed of multiple NFs. In addition, NSI may be a logical network configured to divide the distributed user data according to services, etc. More than one NF may be configured in NS. The NF configured in NS may be a device shared with other NSs, or may not be a device shared with other NSs.

[0108] The UE and / or the device in the network can be assigned to one or more NSs based on the login information such as NSSAI and / or S-NSSAI and / or UE usage type (UE usage type) and / or one or more NSI IDs and / or APN. It should be noted that the UE usage type is a parameter value included in the login information of the UE for identifying the NSI. The UE usage type can be stored in the AMF and / or UDM. The AMF can select SMF132 and UPF based on the UE usage type.

[0109] In addition, S-NSSAI (Single Network Slice Selection Assistance information) is information used to identify NS. S-NSSAI can be composed of only SST (Slice / Servicetype: slice / service type), or it can be composed of both SST and SD (Slice Differentiator: slice differentiator). Here, SST refers to information indicating the expected actions of NS in terms of functions and services. In addition, SD can be information that interpolates SST when selecting an NSI from multiple NSIs shown in SST. S-NSSAI can be information specific to each PLMN, or it can be standard information common among PLMNs. In addition, the network can store more than one S-NSSAI in the UE's login information as the default S-NSSAI. It should be noted that when the S-NSSAI is the default S-NSSAI, the network can provide NS related to the UE when the UE does not send a valid S-NSSAI to the network in the login request message.

[0110] In addition, the S-NSSAI sent and received between the UE and the NW can also be expressed as an S-NSSAI IE (Information element). Moreover, the S-NSSAI IE sent and received between the UE and the NW can be composed of an S-NSSAI composed of an SST and / or SD of a logged-in PLMN and / or an SST and / or SD representing an S-NSSAI of an HPLMN mapped with the S-NSSAI. One or more S-NSSAIs stored by the UE and / or the NW can be composed of an SST and / or SD, or can be composed of an S-NSSAI composed of an SST and / or SD and / or an SST and / or SD representing an S-NSSAI of an HPLMN mapped with the S-NSSAI.

[0111] In addition, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in NSSAI is information for assisting the access network or core network to select NSI. The UE can store the NSSAI allowed by the network for each PLMN. In addition, NSSAI can be information for selecting AMF. The UE can also apply each NSSAI (allowed NSSAI and / or set NSSAI and / or rejected NSSAI and / or pending NSSAI and / or first NSSAI) to PLMN and EPLMN.

[0112] The mapped S-NSSAI is the S-NSSAI of the HPLMN mapped to the S-NSSAI of the logged-in PLMN in the roaming scenario. The UE may store one or more set NSSAIs and mapped S-NSSAIs mapped to the S-NSSAI included in the allowed NSSAI of each access type. Moreover, the UE may also store one or more mapped S-NSSAIs of the S-NSSAI included in the first NSSAI and / or the rejected NSSAI and / or the pending NSSAI.

[0113] The Network Slice-Specific Authentication and Authorization (NSSAA) function refers to a function used to implement network slice-specific authentication and authorization. In network slice-specific authentication and authorization, the UE can be authenticated and authorized outside the core network such as a third party. PLMNs and network devices equipped with the NSSAA function can perform the NSSAA process on a certain S-NSSAI based on the UE's login information. Moreover, UEs equipped with the NSSAA function can manage, store, and send and receive pending NSSAI and third-party rejected NSSAI. In this article, NSSAA is sometimes referred to as a network slice-specific authentication and authorization process, an authentication and authorization process.

[0114] The S-NSSAI requiring NSSAA is an S-NSSAI requiring NSSAA managed by the core network and / or the core network device. Furthermore, the S-NSSAI requiring NSSAA may also be an S-NSSAI managed by the core network and / or the core network device and requiring NSSAA other than the HPLMN to which the S-NSSAI is mapped.

[0115] The core network and / or the core network device may store the S-NSSAI that requires NSSAA by establishing a correspondence between information indicating whether S-NSSAI and NSSAA are required. The core network and / or the core network device may also establish a correspondence between the S-NSSAI that requires NSSAA and information indicating whether NSSAA has been completed or information indicating the status of allowing or successfully completing NSSAA for storage. The core network and / or the core network device may manage the S-NSSAI that requires NSSAA as information that is not related to the access network.

[0116] In addition, the configured NSSAI is the NSSAI provided to the UE for storage. The UE can store the configured NSSAI for each PLMN. The UE can also store the configured NSSAI in association with the PLMN. It should be noted that, in this article, the configured NSSAI corresponding to the PLMN can be expressed as a configured NSSAI for the PLMN or a configured NSSAI for the PLMN or a configured NSSAI for the PLMN, and a configured NSSAI associated with the PLMN. In addition, the UE can also store a configured NSSAI that is valid for all PLMNs without establishing an association with the PLMN, and such a configured NSSAI can be set as the "default configured NSSAI".

[0117] NSSAI may not be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

[0118] The configured NSSAI may be information configured by the network (or PLMN). The S-NSSAI included in the configured NSSAI may be expressed as a configured S-NSSAI. The configured S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI. Alternatively, the S-NSSAI of the PLMN may be expressed as a "configured S-NSSAI", which may be mapped to the S-NSSAI of the HPLMN and may be expressed as a "mapped S-NSSAI for the configured NSSAI for the PLMN".

[0119] In addition, the requested NSSAI is the NSSAI provided by the UE to the network during the login process. During the login process, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI or the set NSSAI stored by the UE. During the PDU session establishment process, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI stored by the UE.

[0120] The request NSSAI may be information indicating the network slice requested by the UE. The S-NSSAI included in the request NSSAI may be expressed as the request S-NSSAI. For example, the request NSSAI is included in an RRC (Radio Resource Control) message and sent, and the RRC message includes a login request message or a PDU session establishment request message, a NAS message or a NAS (Non-Access-Stratum) message sent from the UE to the network.

[0121] In addition, allowed NSSAI is information indicating one or more network slices that the UE is allowed to connect to. In other words, allowed NSSAI is information identifying the network slices that the network is allowed to connect to the UE.

[0122] The UE and / or NW may store and manage the allowed NSSAI as UE information for each access (3GPP access or non-3GPP access). The UE and / or NW may also manage the allowed NSSAI in association with the login area.

[0123] Moreover, the UE and / or NW may store and manage the allowed NSSAI as UE information in association with the PLMN. The allowed NSSAI may be associated with multiple PLMNs, which may be EPLMNs.

[0124] It should be noted that, in this article, the allowed NSSAI corresponding to the PLMN and the access type can be expressed as the allowed NSSAI for the PLMN and the access type or the allowed NSSAI for the access type of the PLMN. The S-NSSAI included in the allowed NSSAI can be expressed as allowed S-NSSAI (allowed S-NSSAI). The allowed S-NSSAI can be composed of S-NSSAI and mapped S-NSSAI.

[0125] In addition, rejected NSSAI is information indicating one or more network slices that the UE is not allowed to connect to. In other words, rejected NSSAI is information identifying a network slice that does not allow the network to connect to the UE. Rejected NSSAI can be information including a combination of one or more S-NSSAI and a rejection reason value.

[0126] Here, the rejection reason value refers to information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and the network can appropriately store and manage the rejection of NSSAI based on establishing a corresponding rejection reason value for each S-NSSAI.

[0127] Moreover, the rejection of NSSAI may also be included in a NAS message sent from the network to the UE, such as a login acceptance message, a setting update command, a login rejection message, or an RRC message including a NAS message. The S-NSSAI included in the rejection of NSSAI may be expressed as a rejection of S-NSSAI.

[0128] The reject NSSAI may be any one of the first to third reject NSSAIs, the pending NSSAI, and the first NSSAI, or a combination thereof. The S-NSSAI included in the reject NSSAI may be expressed as a reject S-NSSAI. The reject S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0129] The UE and / or NW may store and manage the rejection of NSSAI as UE information by establishing association with the PLMN. The rejection of NSSAI may also not be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

[0130] The tracking area is one or more ranges managed by the core network that can be represented as the location information of UE_A10. The tracking area can be composed of multiple cells. Moreover, the tracking area can be either a range for broadcasting control messages such as paging, or a range where UE_A10 can move without performing a switching process. Moreover, the tracking area can be either a routing area or a positioning area, as long as it is the same area as these areas. Hereinafter, the tracking area may also be referred to as TA (Tracking Area). The tracking area can be identified by TAI (Tracking Area Identity) composed of TAC (Tracking area code) and PLMN.

[0131] The registration area (Registration area or login area) is a set of one or more TAs assigned to the UE by the AMF. It should be noted that it is better for UE_A10 to move without sending or receiving signals for tracking area update while moving within one or more TAs included in the registration area. In other words, the registration area can be an information group indicating the area where UE_A10 can move without performing the tracking area update process. The registration area can be identified by a TAI list (TAIlist) composed of one or more TAIs.

[0132] The TAIs included in the TAI list may belong to one PLMN or multiple PLMNs. In the case where multiple TAIs included in the TAI list belong to different PLMNs, these PLMNs may be EPLMNs.

[0133] UE ID refers to information used to identify UE. Specifically, for example, UE ID can be SUCI (SUbscription Concealed Identifier) ​​or SUPI (Subscription Permanent Identifier) ​​or GUTI (Globally Unique Temporary Identifier) ​​or IMEI (International Mobile Subscriber Identity) or IMEISV (IMEI Software Version) or TMSI (Temporary Mobile Subscriber Identity). Alternatively, UE ID can also be other information configured in an application or network. Moreover, UE ID can also be information used to identify a user.

[0134] N1 NAS signaling connection refers to the connection between the UE and the network (AMF), which can be independently managed and exist through a connection on a 3GPP access and a connection on a non-3GPP access.

[0135] The state in which the N1 NAS signaling connection is established may be 5GMM-connected mode. The state in which the N1 NAS signaling connection is not established may be 5GMM-idle mode.

[0136] In other words, the state in which the N1 NAS signaling connection is established over the 3GPP access can be expressed as the UE being in the 5GMM-CONNECTED mode over 3GPP access, and the state in which the N1NAS signaling connection is not established over the 3GPP access can be expressed as the UE being in the 5GMM-IDLE mode over 3GPP access.

[0137] Similarly, the state in which the N1 NAS signaling connection is established on the non-3GPP access can be expressed as the UE being in the 5GMM-CONNECTED mode over non-3GPP access, and the state in which the N1 NAS signaling connection is not established on the non-3GPP access can be expressed as the UE being in the 5GMM-IDLE mode over non-3GPP access.

[0138] In addition, SNPN (Stand-alone Non-Public Network) is a type of NPN for 5GS deployed for non-public use. It is operated by an NPN operator and is not dependent on the NF provided by the PLMN. That is, SNPN can be a network dedicated to NPN independent of PLMN. In addition, SNPN can be identified by a combination of PLMN ID and NID (Network Identifier). It should be noted that the PLMN ID used for SNPN ID can be information ensured for a private network, for example, the MCC included in the PLMN ID can be 999.

[0139] In addition, a UE that can utilize SNPN can support the SNPN access mode. In addition, a UE that is set to operate in the SNPN access mode may be able to select the SNPN and log in to the SNPN, but may not be able to select the PLMN. In addition, a UE that is set to operate in the SNPN access mode may be able to perform the SNPN selection process, but may not be able to perform the PLMN selection process. In addition, even if the UE can utilize SNPN (SNPN enabled), a UE that is not set to operate in the SNPN access mode may not be able to select the SNPN and log in to the SNPN, but may be able to select the PLMN. In addition, a UE that is not set to operate in the SNPN access mode may not be able to perform the SNPN selection process, but may be able to perform the PLMN selection process.

[0140] In addition, a UE that performs actions in SNPN access mode may select SNPN via Uu (3GPP access). In addition, a UE that performs actions in SNPN access mode may also select SNPN via Uu or NWu, wherein Uu or NWu is established via a PDU session provided by a PLMN, and the PLMN is selected via Uu or NWu (non-3GPP access). In addition, a UE that does not perform actions in SNPN access mode may also select PLMN via Uu or NWu, wherein Uu or NWu is established via a PDU session provided by a SNPN, and the SNPN is selected via Uu or NWu (non-3GPP access).

[0141] Here, as a form of UE connecting to SNPN or SNPN service (hereinafter referred to as SNPN only) via non-3GPP access, there can be two types: connection to SNPN via PLMN and direct connection to SNPN via non-3GPP access.

[0142] In addition, the connection to SNPN via PLMN can be that the UE first logs in to the PLMN, establishes a PDU session as a communication path, and then connects via the DN (data network) and the N3IWF in the SNPN. Here, the connection process to SNPN via PLMN can be achieved as follows: after the UE's login process to the PLMN and / or the PDU session establishment process, a general login process to the PLMN via non-3GPP access and / or the same process as the PDU session establishment process is performed and completed by acceptance from the SNPN. It should be noted that the UE can perform login and connection to the PLMN via 3GPP access or non-3GPP access in the SNPN connection via PLMN. Moreover, NAS messages can also be sent and received via the N1 interface between the UE connected to the SNPN via the PLMN and the AMF in the SNPN.

[0143] In addition, direct connection to SNPN via non-3GPP access may include direct connection to SNPN via untrusted non-3GPP access and direct connection to SNPN via trusted non-3GPP access. The SNPN can be logged in and the communication path established through the general login process of PLMN via non-3GPP access and / or the same process as the PDU session establishment process. It should be noted that the UE attempting to directly connect to the SNPN via non-3GPP access can operate in the SNPN access operation mode. NID (Network identifier) ​​is information that identifies the network. SNPN can be identified by the combination of PLMN ID and NID. NID can be unique information within the SNPN or unique information.

[0144] The public network integrated NPN is a network implemented using the functional part of the PLMN. In other words, the public network integrated NPN is an NPN implemented virtually within the PLMN. Moreover, the public network integrated NPN is an NPN that can be generated via the PLMN. It should be noted that the public network integrated NPN can be implemented using the function of network slicing. Specifically, the public network integrated NPN can be a network that can be implemented by using a network slice assigned to the NPN. In this case, the public network integrated NPN can be identified by the S-NSSAI or by a combination of the S-NSSAI and the CAG ID.

[0145] Moreover, the public network integrated NPN may be implemented using the DN. Specifically, the public network integrated NPN may be a network implemented by using the DN for the NPN. The public network integrated NPN may be identified by the DNN or by a combination of the DNN and the CAGID.

[0146] CAG (Closed Access Groups) ID is information that identifies a group of subscribers who are allowed to connect to one or more cells associated with the CAG. CAG can be a group identified by CAG ID. CAG is a group used when implementing public network integration NPN in network slices. CAG can be used to not attempt to access the network slice assigned to the NPN from a UE that does not allow the NPN. Moreover, the CAG ID is unique information within the PLMN.

[0147] SNPN enabled UE refers to a UE that is set to use SNPN. SNPN enabled UE can store at least one information related to SNPN. In other words, the setting information of SNPN enabled UE can include information indicating that SNPN can be used. Moreover, SNPN enabled UE can support SNPN access mode or SNPN access operation mode. In other words, SNPN enabled UE can operate in SNPN access mode or SNPN access operation mode.

[0148] In addition, the SNPN access mode is a mode in which the UE selects only SNPN. More specifically, the UE in the SNPN access mode may be a mode of the UE when the matter is for the process of logging in, connecting to the SNPN, processing, etc. Moreover, in the case of performing SNPN selection or ON-SNPN selection as a network selection, or performing a normal login process to the SNPN, or performing a login process for loading, or performing a process for remote provisioning, the UE needs to act in the SNPN access mode. Here, the UE operating in the SNPN access mode may also be expressed as a UE in the SNPN access mode. Moreover, the UE in the SNPN access mode may also be a UE in which the SNPN is valid.

[0149] In addition, the SNPN access operation mode is an SNPN access mode or a mode of connecting to the SNPN via a non-3GPP access. Here, connecting to the SNPN via "non-3GPP access" may refer to a case where the UE is connected to the SNPN via a PLMN or a case where the UE is directly connected to the SNPN via a non-3GPP access. In addition, the direct connection to the SNPN via a non-3GPP access may be a direct connection to the SNPN via a "trusted non-3GPP access" or a direct connection to the SNPN via an "untrusted non-3GPP access". In addition, when operating in the SNPN access mode, the UE may operate in the SNPN access operation mode. In addition, when not operating in the SNPN access mode, the UE may not operate in the SNPN access operation mode. Moreover, a UE in the SNPN access mode may also be a UE in the SNPN access operation mode.

[0150] The SNPN selection process may be a process for selecting the SNPN. In addition, the SNPN selection process may also be a process for the UE to select the SNPN. In addition, the SNPN selection process may also be a process implemented when the UE is connected to the SNPN. The SNPN selection process may also be referred to as SNPN selection, or as a SNPN selection procedure. SNPN selection may also be referred to as the SNPN selection process, or as a SNPN selection procedure. The SNPN selection process may also be referred to as the SNPN selection process, or as a SNPN selection.

[0151] A UE operating in SNPN access mode or SNPN access operation mode may perform the SNPN selection process. A UE not operating in SNPN access mode or SNPN access operation mode may not perform the SNPN selection process. The SNPN selection process may have an automatic SNPN selection mode and a manual SNPN selection mode. The SNPN selection process may be performed without logging in. In other words, the SNPN selection process may be performed without the UE completing the login to the network.

[0152] In addition, a UE that is not operating in SNPN access mode or SNPN access operation mode may also perform a PLMN selection process. A UE that is operating in SNPN access mode or SNPN access operation mode may also not perform a PLMN selection process. The PLMN selection process may be performed without logging in. In other words, the PLMN selection process may be performed without the UE completing the login to the network. The PLMN selection process may have an automatic PLMN selection mode and a manual PLMN selection mode.

[0153] In addition, a non-public network (NPN) is a non-public network used by specific users for specific purposes such as enterprises and other private purposes, and is not intended for general use. There are two types of NPN: stand-alone non-public network (SNPN) and public network integrated NPN (Public network integrated NPN). It should be noted that the following recorded as NPN can mean both SNPN and public network integrated NPN.

[0154] Default UE credentials are information maintained by the UE before the actual loading process. The default UE credentials may be information used to uniquely identify the UE. Furthermore, the default UE credentials may also be information used to verify the security of the UE.

[0155] The default certificate server or default certificate server (Default Credentials Server: DCS) is a server that can use the default UE certificate to authenticate the UE. The default certificate server can also be another device or a server that can provide an entity with the authentication function of the UE using the default UE certificate. It should be noted that the DCS can be configured to include an AAA server, or it can be configured to include an AUSF and an UDM. In other words, the functions of the DCS can be implemented by an AAA server, or by an AUSF and an UDM.

[0156] NPN credentials are information used for authentication by UE in order to access NPN. NPN credentials can be 3GPP credentials or non-3GPP credentials.

[0157] An onboarding network (ON) is a network that provides an initial login and / or access to a UE for onboarding. In other words, the UE may log in and / or access the onboarding network to implement onboarding.

[0158] Here, the onboarding network may be implemented by a PLMN. Moreover, the onboarding network may also be implemented by an SNPN. It should be noted that the SNPN providing access to the UE for onboarding may be an ON-SNPN (Onboarding Standalone Non-Public Network).

[0159] A Provisioning Server (PVS) is a server that provides subscription data to an authenticated and authorized UE. A Provisioning Server (PVS) can also be a server that provides subscription data and other setting information to an authenticated and authorized UE.

[0160] Furthermore, the provisioning server may also be a server existing in the loading network. Furthermore, the provisioning server may also be a server existing in the PLMN. Furthermore, the provisioning server may also be a server existing in the SNPN. Furthermore, the provisioning server may also be a server existing in the core network. Furthermore, the provisioning server may also be a server existing in an external DN.

[0161] The subscription owner (SO) is an entity that stores subscription data and / or other setting information and provides the subscription data and / or other setting information to the UE via the PS domain as a result of the UE loading process. In other words, the subscription owner is an entity that stores subscription data and / or other setting information, and may also be an entity that provides subscription data and / or other setting information to the UE during the UE loading process.

[0162] In addition, CH (Credentials Holder) may be an entity that authenticates and authorizes the connection of the SNPN separated from the CH by the UE. It should be noted that the DCS may be a form of CH. In other words, the DCS may also be replaced by the CH.

[0163] UE loading is to provide the UE and entities within the network with the information required to obtain the UE's authorized access and connectivity to the NPN.

[0164] In other words, UE loading may be providing information to the UE or an entity within the network. Here, the information may be information required for the UE to establish access and connectivity to the NPN. Moreover, the access and connectivity to the NPN may also be authorized. Moreover, the information may also be SNPN information.

[0165] In other words, when the UE attempts to establish access and connectivity to the NPN, the UE may obtain information required for establishing access and connectivity to the NPN by performing UE loading. Furthermore, the UE may perform a process for establishing access and connectivity to the NPN after performing UE loading.

[0166] It should be noted that UE loading may also be referred to as UE loading process. Moreover, UE loading may also be referred to as loading service. Moreover, UE loading may also be referred to as loading.

[0167] In other words, when it is expressed as a UE loading process, it may refer to UE loading. Moreover, when it is expressed as loading a service, it may also refer to UE loading. Moreover, when it is expressed as loading, it may also refer to UE loading.

[0168] SNPN information is information required for the UE to establish access and connectivity to the SNPN. The SNPN information may also be information used when the UE implements a process for establishing access and connectivity to the SNPN. Furthermore, the SNPN information may also be subscription data and / or other setting information. Furthermore, the SNPN information may also be an NPN certificate. Furthermore, the SNPN information may also be referred to as NPN information.

[0169] It should be noted that the UE may obtain the SNPN information from the network during UE loading. In more detail, the UE may obtain the SNPN information from the provisioning server or subscription owner during UE loading.

[0170] In other words, the network may provide the SNPN information to the UE during UE onboarding. In more detail, the provisioning server or subscription owner may provide the SNPN information to the UE during UE onboarding.

[0171] The process of providing SNPN information is a process for the network to provide SNPN information to the UE. In other words, the process of providing SNPN information is a process for the UE to obtain SNPN information from the network. Moreover, the process of providing SNPN information can also be a process for implementing UE loading. It should be noted that in this specification, the process of providing SNPN information is also referred to as UE remote provision process, UE remote provision or remote provision process or remote provision, etc.

[0172] The network may provide the SNPN information to the UE in the process of providing the SNPN information. In more detail, the provisioning server or the subscription owner may provide the SNPN information to the UE in the process of providing the SNPN information.

[0173] Moreover, the UE may acquire the SNPN information from the network during the provision of the SNPN information. In more detail, the UE may acquire the SNPN information from the provision server or the subscription owner during the provision of the SNPN information.

[0174] Here, the process of providing SNPN information via the user plane is also referred to as a remote provisioning process via the user plane, etc.

[0175] The process of providing SNPN information via the user plane is a process in which the network provides SNPN information to the UE via the user plane. In other words, the process of providing SNPN information via the user plane is a process in which the UE obtains SNPN information from the network via the user plane.

[0176] Specifically, the process of providing the SNPN information via the user plane is a process of providing the SNPN information from the network to the UE using the PDU session after a PDU session is established between the UE and the network.

[0177] Here, in the case of using the process of providing SNPN information via the user plane, the network can provide SNPN information to the UE by establishing a PDU session with the UE and sending the SNPN information to the UE on the PDU session. In other words, in the case of using the process of providing SNPN information via the user plane, the UE can obtain the SNPN information by establishing a PDU session with the network and receiving the SNPN information from the network on the PDU session.

[0178] It should be noted that the PDU session for providing SNPN information may be a PDU session for providing SNPN information. In other words, the PDU session for providing SNPN information may be a PDU session for providing SNPN information.

[0179] In addition, the PDU session for loading the service is a PDU session established for loading the service. The PDU session for loading the service may be a PDU session established for performing a provision process of the SNPN information.

[0180] Furthermore, the PDU session for loading the service may be a PDU session used in loading the service. Furthermore, the PDU session for loading the service may also be a PDU session used in the process of providing the SNPN information.

[0181] Moreover, the PDU session used for loading the service may also be a PDU session established in a network used for loading the service. Here, the network used for loading may be either a SNPN or a PLMN.

[0182] Furthermore, the PDU session for loading services may also be a PDU session established in a state where a login process for loading services is completed. Furthermore, the PDU session for loading services may also be a PDU session established in a state where a registration that can only use the loaded services is completed.

[0183] Furthermore, each device may establish a PDU session for loading services in order to perform the loading services. Furthermore, each device may also establish a PDU session for loading services in order to perform the SNPN information provision process.

[0184] Furthermore, each device may use the PDU session for loading the service to perform the loading service. Furthermore, each device may also use the PDU session for loading the service to perform the provision process of the SNPN information.

[0185] Moreover, each device may also perform remote provisioning via the user plane using a PDU session for loading services. In other words, the remote provisioning process via the user plane may be composed of a process of establishing a PDU session for loading and a process of provisioning via the PDU session for loading established. It should be noted that, here, the UE may obtain the FQDN or IP address of the provisioning server (PVS) in establishing the remote provisioning via the user plane during the process of establishing the PDU session for loading.

[0186] A UE operating in the SNPN access mode or the SNPN access operation mode may perform a loaded network selection procedure. In other words, in the case of performing a loaded network selection procedure, the UE may operate in the SNPN access mode or the SNPN access operation mode.

[0187] A list of subscription data ("list of subscription data") refers to a list stored, maintained and managed by a UE that is executing an SNPN access operation mode, also referred to as a list of subscriber data. Here, the UE may store, maintain and manage, for each entry in the list of subscription data, a SNPN-specific attempt counter for 3GPP access or a SNPN-specific attempt counter for non-3GPP access or a counter for "the entry for the current SNPN considered invalid for 3GPP access" events or a counter for "the entry for the current SNPN considered invalid for non-3GPP access" events. It should be noted that, in this specification, the SNPN-specific attempt counter for 3GPP access and the SNPN-specific attempt counter for non-3GPP access are simply referred to as "attempt counters" (attempt counter(s)), the counter for events in which the entry of the current SNPN is considered invalid for 3GPP access and the counter for events in which the entry of the current SNPN is considered invalid for non-3GPP access are simply referred to as "event counters" (event counter(s)), and the attempt counter or event counter is simply referred to as a "counter".

[0188] Here, each entry of the list of subscription data may be constructed per SNPN ID and / or per access type. In other words, the various counters included in the list of subscription data may be constructed per SNPN ID and / or per access type. In addition, the list of subscription data may be maintained regardless of the power on / off of the UE, the insertion and removal of the SIM, or the activation / deactivation of the UE's SNPN access operation mode, and the list of subscription data may be deleted.

[0189] Furthermore, the UE may store the list of subscription data and / or these counters in a non-volatile memory. Furthermore, in the event that a selected item of subscription data is updated or the USIM for the selected PLMN subscription is removed, the UE may erase the trial counter and reset the event counter. Furthermore, the UE implementation-specific maximum value of these counters may be less than 10, and different maximum values ​​may be used for different counters.

[0190] The forbidden PLMN list (forbidden PLMN list or list of "forbidden PLMN(s)") refers to a list for managing PLMNs that are prohibited from connecting (accessing) and / or logging in, and may also be a list of PLMN IDs that include more than 0. Here, the forbidden PLMN list may be a list managed by the UE inside the UE. More specifically, when the UE performs a login process, the UE may add the PLMN ID of the core network to the forbidden PLMN list based on a login rejection message received from the core network.

[0191] In addition, the prohibited PLMN list may manage multiple lists for each access type within the UE, for example, two lists, a prohibited PLMN list in 3GPP access and a prohibited PLMN list in non-3GPP access, may be managed.

[0192] In addition, the prohibited PLMN list may be stored and managed in, for example, a USIM (Universal Subscriber Identity Module) or a SIM inside the UE.

[0193] The forbidden SNPNs list refers to a list for managing SNPNs that are prohibited from connecting (accessing), and may be a list of SNPN IDs including 0 or more. Here, the forbidden SNPN list may include a permanently forbidden SNPN list ("permanently forbidden SNPNs" list) and a temporarily forbidden SNPN list ("temporarily forbidden SNPNs" list), which may be managed independently by the UE operating in the SNPN access operation mode according to each access type. It should be noted that, in this specification, the permanently forbidden SNPN list and the temporarily forbidden SNPN list are also referred to as the forbidden SNPN list. In other words, unless otherwise specified, the forbidden SNPN list means a permanently forbidden SNPN list and / or a temporarily forbidden SNPN list. It should be noted that the forbidden SNPN list is also referred to as a list of forbidden SNPNs.

[0194] Furthermore, in a case where the UE supports connection to the SNPN using a certificate from a certificate holder, a list of SNPNs that are not a prohibited PLMN list but are permanently prohibited and a list of temporarily prohibited SNPNs can be managed independently for each access type by the UE operating in the SNPN access operation mode, for each list of subscription data or entry of PLMN subscription.

[0195] Here, independently managing the permanently prohibited SNPN list and the temporarily prohibited SNPN list according to each access type may refer to independently managing four lists, namely, the permanently prohibited SNPN list for 3GPP access, the permanently prohibited SNPN list for non-3GPP access, the temporarily prohibited SNPN list for 3GPP access, and the temporarily prohibited SNPN list for non-3GPP access.

[0196] In addition, in the case where the UE supports the loading service in the SNPN, the additional permanently prohibited SNPN list for the loading service and the additional temporarily prohibited SNPN list for the loading service can also be managed by the UE operating in the SNPN access operation mode. In other words, the permanently prohibited SNPN list and the temporarily prohibited SNPN list can be set as different lists for management in the normal access to the SNPN and the SNPN access for the loading service. Moreover, the additional permanently prohibited SNPN list for the loading service and the additional temporarily prohibited SNPN list for the loading service can be managed independently for each access type. In this case, the eight lists can also be managed independently.

[0197] Here, the prohibited SNPN list may be a list managed by the UE inside the UE, or may be a list stored and managed in the UE, such as a USIM (Universal Subscriber Identity Module) or a SIM.

[0198] In addition, for example, the UE may add the SNPN ID of the core network to the prohibited SNPN list or delete it from the prohibited SNPN list based on receiving a rejection message including a rejection reason value (5GMM cause value) from the core network when the UE is performing various processes. Here, for example, the various processes may include a login process or a service request process or an authentication process, the rejection message may include a login rejection message or a service rejection message or an authentication rejection message, and the rejection reason value may include one or more of the following: illegal UE (Illegal UE; #3) or illegal ME (Illegal ME; #6) or 5GS services not allowed (5GS services not allowed; #7) or N1 mode not allowed (N1 mode not allowed; #27) or 5GCN connection via non-3GPP access is not allowed (Non-3GPP access to 5GCN not allowed; #72) or temporarily not allowing the SNPN (Temporarily not authorized for this SNPN; #74) or permanently not allowing the SNPN (Permanently not authorized for this SNPN; #75), and the details of the action will be described later.

[0199] Timer T3510 refers to the timer of 5GS mobility management, which is a timer executed in the UE. Here, timer T3510 is a timer that is started when the UE sends a login request message and stopped when the UE receives a login acceptance message or a login rejection message from the network as a response message.

[0200] Timer T3517 refers to the timer of 5GS mobility management, which is a timer executed in the UE. Here, timer T3517 is a timer that is started when the UE sends a service request message (SERVICE REQUEST message) or a control plane service request message (CONTROL PLANE SERVICE REQUEST message) and is stopped when the UE receives a service acceptance message or a service rejection message from the network as a response message.

[0201] Timer T3247 refers to the timer of 5GS mobility management, which is a timer executed in the UE. Here, timer T3247 is a timer that is started when the UE in N1 mode receives a login rejection message that does not guarantee integrity or a service rejection message that does not guarantee integrity from the network, and is stopped when the SIM / USIM is removed from the UE or the entry of the SNPN ID in the list of subscription data is updated or when the power of the UE is disconnected.

[0202] Here, when the reason value (5GMM cause value) included in the above-mentioned rejection message received by the UE is #74, the UE starts timer T3247 with a random value in the range of 15 minutes to 30 minutes; in the case of any other reason value, the UE starts timer T3247 with a random value in the range of 30 minutes to 60 minutes.

[0203] Moreover, when the UE is executing timer T3510 or timer T3517, if it receives a login rejection message or a service rejection message that does not guarantee integrity, it can stop timer T3510 or timer T3517 and start timer T3247.

[0204] It should be noted that, here, timer T3510 or timer T3517 or timer T3247 can be a timer for 5GS mobility management. Moreover, timer T3510 or timer T3517 or timer T3247 can be a timer executed in the UE under the above conditions.

[0205] In addition, the NAS messages including various rejection messages may include messages with integrity protection and messages without integrity protection. In addition, integrity checking may be performed by the NAS or on NAS signaling.

[0206] Each rejection message in this specification may be an integrity-protected NAS reject message or a non-integrity-protected NAS reject message. Furthermore, these may be synonymous with an integrity-confirmed NAS message or an integrity-unconfirmed NAS message. Furthermore, these may also be synonymous with a message whose integrity is confirmed by NAS or a message whose integrity is not guaranteed by NAS.

[0207] In addition, as the rejection reason values ​​(5GMM cause value) mainly handled in this specification, there are illegal UE (Illegal UE; #3) or illegal ME (Illegal ME; #6) or 5GS services not allowed (5GS services not allowed; #7) or N1 mode not allowed (N1 mode not allowed; #27) or 5GCN connection via non-3GPP access is not allowed (Non-3GPP access to 5GCN not allowed; #72) or temporarily not allowed for this SNPN (Temporarily not authorized for this SNPN; #74) or permanently not allowed for this SNPN (Permanently not authorized for this SNPN; #75). Hereinafter, in this specification, for example, "illegal UE (Illegal UE; #3)" is also referred to as rejection reason value #3. [2.3. Description of the counter of this embodiment]

[0208] Next, in this embodiment, various counters maintained and / or stored and / or managed in each device are described.

[0209] The trial counter #0 of this embodiment is a SNPN-specific attempt counter for 3GPP access. The trial counter #0 may be a counter used when the UE is connected to the SNPN or SNPN service via the 3GPP access.

[0210] The trial counter #1 of this embodiment is a SNPN-specific attempt counter for non-3GPP access. The trial counter #1 may be a counter used when the UE is connected to the SNPN via the PLMN. Moreover, the trial counter #1 may also be a counter used when the UE supports connection to the SNPN service via the PLMN.

[0211] The trial counter #2 of this embodiment is a SNPN-specific attempt counter for non-3GPP access, which is used in the case of connecting to the SNPN service via the PLMN and in the case of directly connecting to the SNPN service via the non-3GPP access. Trial counter #2 can be a counter used in the case where the UE is connected to the SNPN service via the PLMN and in the case of directly connecting to the SNPN service via the non-3GPP access. Moreover, trial counter #2 can also be a counter used in the case where the UE supports connection to the SNPN service via the PLMN and direct connection to the SNPN via the non-3GPP access.

[0212] Furthermore, trial counter #2 may be a counter that extends trial counter #1. More specifically, the management of trial counter #1 considers not only the case where the UE connects to the SNPN via the PLMN, but also the case where the UE directly connects to the SNPN via a non-3GPP access.

[0213] In other words, trial counter #2 is a counter used both when connecting to the SNPN service via the PLMN and when directly connecting to the SNPN service via non-3GPP access. Therefore, for example, when switching from a connection to the SNPN service via the PLMN to a direct connection to the SNPN service via the non-3GPP access, it can be a counter that inherits the value used in the connection to the SNPN service via the PLMN, or it can be a counter that is used after resetting the value once.

[0214] The trial counter #3 of this embodiment is a SNPN-specific attempt counter for non-3GPP access, which is used when directly connecting to the SNPN service via non-3GPP access. Trial counter #3 can be a counter used when the UE is directly connected to the SNPN service via non-3GPP access. Moreover, trial counter #3 can also be a counter used when the UE supports direct connection to the SNPN service via non-3GPP access.

[0215] In other words, trial counter #3 is different from trial counter #2. Although it is a counter that is also used when directly connecting to the SNPN service via non-3GPP access, it is a counter that is not used when connecting to the SNPN service via PLMN. Therefore, for example, when switching from a connection to the SNPN service via PLMN to a direct connection to the SNPN service via non-3GPP access, trial counter #1 can be used in the connection to the SNPN service via PLMN, and trial counter #3 can be used in the direct connection to the SNPN service via non-3GPP access.

[0216] Event counter #0 of this embodiment is a counter for "the entry for the current SNPN considered invalid for 3GPP access" events. Event counter #0 may be a counter used when the UE is connected to a SNPN or SNPN service via 3GPP access.

[0217] Event counter #1 of this embodiment is a counter for "the entry for the current SNPN considered invalid for non-3GPP access" events. Event counter #1 can be a counter used when the UE is connected to the SNPN service via the PLMN. Moreover, event counter #1 can also be a counter used when the UE supports connection to the SNPN service via the PLMN.

[0218] Event counter #2 of the present embodiment is a counter for “the entry for the current SNPN considered invalid for non-3GPP access” events, used in the case of connecting to the SNPN service via a PLMN and in the case of directly connecting to the SNPN service via a non-3GPP access. Event counter #2 may be a counter used in the case of the UE connecting to the SNPN service via a PLMN and in the case of directly connecting to the SNPN service via a non-3GPP access. Moreover, event counter #2 may also be a counter used in the case of the UE supporting connection to the SNPN service via a PLMN and direct connection to the SNPN via a non-3GPP access.

[0219] Furthermore, event counter #2 may be a counter extending event counter #1. More specifically, event counter #2 manages not only the case where the UE targeted by event counter #1 connects to the SNPN via the PLMN, but also the case where the UE directly connects to the SNPN via non-3GPP access.

[0220] In other words, event counter #2 is a counter used both when connecting to the SNPN service via the PLMN and when directly connecting to the SNPN service via non-3GPP access. Therefore, for example, when switching from a connection to the SNPN service via the PLMN to a direct connection to the SNPN service via the non-3GPP access, it can be a counter that inherits the value used in the connection to the SNPN service via the PLMN, or it can be a counter that is used after resetting the value once.

[0221] Event counter #3 of this embodiment is a counter for the event of "the entry of the current SNPN is considered invalid for non-3GPP access" used when the UE is directly connected to the SNPN service via non-3GPP access. Event counter #3 can be a counter used when the UE is directly connected to the SNPN service via non-3GPP access. Moreover, event counter #3 can also be a counter used when the UE supports direct connection to the SNPN service via non-3GPP access.

[0222] In other words, event counter #3 is different from event counter #2. Although it is a counter that is also used when directly connecting to the SNPN service via non-3GPP access, it is a counter that is not used when connecting to the SNPN service via the PLMN. Therefore, for example, when switching from a connection to the SNPN service via the PLMN to a direct connection to the SNPN service via the non-3GPP access, event counter #1 can be used in the connection to the SNPN service via the PLMN, and event counter #3 can be used in the direct connection to the SNPN service via the non-3GPP access.

[0223] It should be noted that any one or more of the various counters (trial counters #0 to #3 and event counters #0 to #3) described in this item may be included in the list of the above-mentioned subscription data, which is stored, maintained, and managed by the UE. In other words, the UE operating in the SNPN access operation mode may store, maintain, and manage the list of subscription data including any one or more of the various counters (trial counters #0 to #3 and event counters #0 to #3) described in this item.

[0224] In addition, the various counters (trial counters #0 to #3 and event counters #0 to #3) described in this item are different and independent counters, and each counter can be independently stored, maintained, and managed in the UE. In addition, the various counters (trial counters #0 to #3 and event counters #0 to #3) described in this item can also be stored, maintained, and managed for each SNPN ID.

[0225] In addition, the storage, maintenance, and management of the various counters (trial counters #0 to #3 and event counters #0 to #3) described in this item by the UE may also be based on the connection method to the SNPN supported by the UE. For example, when the UE supports connection to the SNPN via non-3GPP access, trial counter #1, trial counter #2, event counter #1, and event counter #2 may be included in the list of subscription data for storage, maintenance, and management. [3. Embodiments of the present invention] [3.1. Description of the process or processing used in each embodiment]

[0226] Next, the process used in each embodiment is described. It should be noted that the process or processing used in each embodiment includes a login process, a service request process, an authentication process, and the processing of a counter in each process.

[0227] It should be noted that each process may also be a process for the UE to directly connect to the SNPN via non-3GPP access or attempt a direct connection to the SNPN. Moreover, each process may also be a process performed by the UE operating in the SNPN access operation mode or the SNPN access mode.

[0228] In addition, in the description of each process in this chapter, a detailed description of each entity constituting the non-3GPP access is omitted, and the transmission and reception of NAS messages between and the core network constituting the SNPN is mainly described.

[0229] Each process is described below. [3.1.1. Login process]

[0230] use Figure 6 The registration procedure is described below. It should be noted that in this chapter, the registration procedure is also referred to as this procedure.

[0231] Here, the login process of this embodiment can be a login process to SNPN via non-3GPP access (access network_B120). Hereinafter, unless otherwise specified, the login process to SNPN via non-3GPP access will also be referred to as this process. In addition, this process can also be a process performed by a UE in SNPN access operation mode or SNPN access mode. Moreover, this process can also be a login process for a direct connection to SNPN via non-3GPP access performed by a UE.

[0232] In addition, this process can be an initial registration procedure for an initial login process or a mobile and regular login process or an initial registration process for a loading service in an SNPN, or it can be a process performed on an SNPN accessed via a non-3GPP as described above. Here, the login process for loading can be an initial registration procedure.

[0233] The login process is a process for the UE to log in to the access network_B and / or core network_B and / or DN and / or SNPN. If the UE is not logged in to the network, this process can be performed at any time, such as when the power is turned on. In other words, if the UE is in a non-logged-in state (5GMM-DEREGISTERED state), this process can be started at any time. In addition, each device (especially UE and AMF) can be transformed into a logged-in state (5GMM-REGISTEDED state) based on the completion of the login process. It should be noted that each login state can be managed by each device for each access. Specifically, each device can independently manage the login state for 3GPP access (logged-in state or non-logged-in state) and the login state for non-3GPP access.

[0234] Moreover, the registration process may be a process for updating location registration information of the UE in the network and / or periodically notifying the network of the status of the UE from the UE and / or updating specific parameters related to the UE in the network.

[0235] The UE can start the login process when moving across a TA (tracking area). In other words, the UE can start the login process when it moves to a TA different from the TA represented by the maintained TA list (TAI list or login area). Moreover, the UE can also start this process when the back-off timer or other timer being executed expires. Moreover, the UE can also start the login process when the context of each device needs to be updated due to the disconnection or disabling of the PDU session. Moreover, the UE can also start the login process when the capability information and / or preference related to the establishment of the UE's PDU session changes. Moreover, the UE can also start the login process periodically. Moreover, the UE can start the login process based on the completion of the UE configuration update process, the completion of the login process, the completion of the PDU session establishment process, the completion of the PDU session management process, or the information received from the network in each process, or the expiration or stop of the back-off timer. It should be noted that the UE can perform the login process at any timing, and is not limited to this.

[0236] It should be noted that the above-mentioned process for transitioning from a state where the UE is not logged in to the network to a logged in state may also be set as an initial registration procedure or a registration procedure for initial registration. Alternatively, the registration procedure performed when the UE is logged in to the network may be set as a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure. Alternatively, when the UE is not logged in to the network, it may be set as an initial registration procedure for onboarding services in SNPN that is performed to obtain information about the SNPN.

[0237] It should be noted that the UE may perform the above network selection before the login process or in the initial state of the login process, and select and determine the PLMN or SNPN or ON-SNPN requested by the UE.

[0238] Figure 6The new AMF (new AMF) 141 represents the AMF logged in by UE_A10 through this process, and the old AMF (old AMF) 142 represents the AMF that the UE has logged in through the process before this process. If no change of AMF occurs in this process, the interface between the old AMF142 and the new AMF141 and the process between the old AMF142 and the new AMF141 will not occur, and the new AMF141 can be the same device as the old AMF142. It should be noted that in this article, when recorded as AMF, it can refer to the new AMF141, it can also refer to the old AMF142, or it can refer to both parties. In addition, the new AMF141 and the old AMF142 can be AMF140.

[0239] First, UE_A10 starts the registration process by sending a registration request message to the new AMF141 (S600)(S602)(S604). Specifically, the UE sends the registration request message to the access network_B120 (S600). It should be noted that the registration request message can be a NAS message sent and received on the N1 interface.

[0240] Moreover, UE_A10 may include identification information indicating the type of this process in the login request message and send it. Here, the identification information indicating the type of this process may be a 5GS registration type IE (5GS registration type IE), which may be information indicating that this process is a login process for initial login, for login information update accompanying movement, for regular login information update, or for login in an emergency.

[0241] Here, the AMF identification information may refer to information that identifies the AMF or a set of AMFs, for example, it may refer to 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier).

[0242] In addition, UE_A10 can start the PDU session establishment process during the login process by including an SM message (such as a PDU session establishment request message) in the login request message, or sending an SM message (such as a PDU session establishment request message) together with the login request message.

[0243] When receiving the login request message, the access network_B120 selects an AMF to transmit the login request message (S602). It should be noted that the access network_B120 can select an AMF based on the login request message and / or one or more identification information included in the login request message. For example, the access network_B120 can select an AMF that supports the function corresponding to the UE capability information included in the message.

[0244] It should be noted that the method for selecting AMF is not limited to this, and access network_B120 may also select AMF based on other conditions. Access network_B120 extracts the login request message from the received RRC message and transmits the login request message to the selected new AMF (S604).

[0245] The new AMF 141 can perform the first condition determination upon receiving the login request message. The first condition determination is used to determine whether the network (or the new AMF 141) accepts the UE's request. When the first condition determination is true, the new AMF 141 executes the processes of S606 to S612. On the other hand, when the first condition determination is false, the new AMF 141 may not execute the processes of S606 to S608, but execute the processes of S608 and / or S610.

[0246] Here, the process of S609 may be an authentication / security process. It should be noted that, in the case where this process is executed as a login process for loading a service, AMF may receive and store the FQDN or IP address of the provisioning server (PVS) from DCS (Default Credential Server) via AUSF (Authentication Server Function) during the process of S609. Here, PVS may be a server that supplies SNPN information or a certificate (qualification information; credential) to the UE during the process for loading a service. In addition, the FQDN or IP address of the PVS sent and received in S609 may be used when the UE connects to the PVS to obtain SNPN information or a certificate (qualification information; credential) during the remote provisioning process via the user plane that is executed after completing this process that is executed as a login process for loading a service.

[0247] Alternatively, the new AMF 141 may also perform the first condition determination after requesting the UE context from the old AMF 142 and receiving the UE context from the old AMF 142 (S606, S608). In this case, the new AMF 141 may execute S610 and / or S612 if the first condition determination is true. On the other hand, the new AMF 141 may execute S610 if the first condition determination is false.

[0248] It should be noted that, here, when the first condition is judged to be true, the control message sent and received in S610 may be a registration accept message, and when the first condition is judged to be false, the control message sent and received in S610 may be a registration reject message.

[0249] It should be noted that the first condition judgment can be performed based on the reception of the login request message and / or the identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF included in the login request message.

[0250] For example, the first condition may be true when the network allows the UE's request, and false when the network does not allow the UE's request. In addition, the first condition may be true when the network of the UE's login destination and / or the device in the network supports the function requested by the UE, and false when the function requested by the UE is not supported. Furthermore, the first condition may be true when the identification information sent and received is allowed, and false when the identification information sent and received is not allowed.

[0251] When the AMF indicated by the AMF identification information included in the message received by the new AMF141 from the UE is the old AMF142, the new AMF141 performs the procedures of S606 and S608. When the AMF indicated by the AMF identification information included in the message received by the new AMF141 from the UE_A10 is the new AMF141, the procedures of S606 and S608 are not performed. In other words, when an AMF change occurs through this procedure, the procedures of S606 and S608 are performed. When no AMF change occurs, the procedures of S606 and S608 are skipped.

[0252] The UE context transmission process (S606, S608) is described. The new AMF 141 sends a UE context request message to the old AMF 142 (S606). Based on the received UE context request message, the old AMF 142 sends the UE context to the new AMF 141. The new AMF 141 generates a UE context based on the received UE context.

[0253] Here, the UE context sent from the new AMF 141 to the old AMF 142 may include UE ID and allowed NSSAI.

[0254] The new AMF 141 may send a control message (S610) to the UE based on the determination of the first condition and / or receiving the UE context from the old AMF 142. The control message may be a login acceptance message or a login rejection message. The following describes the case where the control message sent to the UE is a login acceptance message.

[0255] In addition, when the control message is a login acceptance message, the AMF can include an SM message (e.g., a PDU session establishment acceptance message) in the login acceptance message and send it, or send the SM message (e.g., a PDU session establishment acceptance message) together with the login acceptance message. However, the sending method can also be performed when the SM message (e.g., a PDU session establishment request message) is included in the login request message. In addition, the sending method can also be performed when the SM message (e.g., a PDU session establishment request message) is sent together with the login request message. The AMF can indicate that the process used for SM in the login process is accepted by performing such a sending method.

[0256] In addition, the AMF may indicate that the UE's request is accepted by sending a login acceptance message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF, or may indicate that the UE's request is rejected by sending a login rejection message.

[0257] The UE receives a control message via the access network_B120 (S610). In the case where the control message is a login acceptance message, the UE can identify that the UE's request according to the login request message is accepted and the contents of various identification information included in the login acceptance message by receiving the login acceptance message. Alternatively, in the case where the control message is a login rejection message, the UE can identify that the UE's request implemented by the login request message is rejected and the contents of various identification information included in the login rejection message by receiving the login rejection message. In addition, the UE can also identify that the UE's request is rejected if the control message is not received after a specified period of time after sending the login request message.

[0258] Here, when the UE receives a login acceptance message from the AMF via the access network_B, the trial counter #1 and / or the event counter #1 may be deleted or reset. The details will be described later (3.1.4, 3.2, 3.3).

[0259] In addition, here, the login rejection message received by the UE from the AMF may include any one or more of the following as rejection reason values ​​(5GMM cause value): illegal UE (Illegal UE; rejection reason value #3) or illegal ME (IllegalME; rejection reason value #6) or 5GS services not allowed (5GS services not allowed; rejection reason value #7) or N1 mode not allowed (N1 mode not allowed; rejection reason value #27) or 5GCN connection via non-3GPP access is not allowed (Non-3GPP access to 5GCN not allowed; rejection reason value #72) or temporarily not allowed for this SNPN (Temporarily not authorized for this SNPN; rejection reason value #74) or permanently not allowed for this SNPN (Permanently not authorized for this SNPN; rejection reason value #75).

[0260] Moreover, the login rejection message received by the UE from the AMF may also be a message that does not guarantee integrity. Conversely, the login rejection message received by the UE from the AMF may also be a message that guarantees integrity. Here, the integrity confirmation of the login rejection message may be performed by the NAS.

[0261] In addition, the UE that receives the login rejection message may stop timer T3510 or timer T3517 and execute timer T3247 when executing timer T3510 or timer T3517. Here, the UE stops timer T3510 or timer T3517 and then executes timer T3247 when the integrity of the received login rejection message is not guaranteed and / or the rejection reason value includes any one or more of rejection reason value #3, rejection reason value #6, rejection reason value #7, rejection reason value #27, rejection reason value #72, rejection reason value #74, or rejection reason value #75.

[0262] Moreover, when the control message is a login acceptance message, the UE can send a login completion message to the AMF via the access network_B120 as a response message to the login acceptance message (S610). It should be noted that the UE can include an SM message such as a PDU session establishment acceptance message in the login completion message when receiving an SM message such as a PDU session establishment acceptance message, and can also indicate that the SM process is completed by including the SM message. Here, the login completion message is a NAS message sent and received on the N1 interface.

[0263] AMF receives the login completion message via access network_B 120 (S612). In addition, each device completes this process based on the transmission and reception of the login acceptance message and / or the login completion message.

[0264] Alternatively, each device may complete the login process based on the sending and receiving of a login acceptance message or a login rejection message.

[0265] It should be noted that each device can transition or maintain the state in which the UE has logged in to the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the sending and receiving of the login acceptance message and / or the login completion message, and can also transition or maintain the state in which the UE has not logged in to the network for the current PLMN or SNPN on the access receiving the login rejection message (RM_DEREGISTERED state or 5GMM-DEREGISTEREDstate) based on the sending and receiving of the login rejection message. In addition, the transition of each device to each state can be based on the sending and receiving of the login completion message or the completion of the login process.

[0266] Furthermore, each device may perform processing based on the information sent and received during the login process based on the completion of the login process. For example, when information indicating that a request of a part of the UE is rejected is sent and received, the reason why the UE's request is rejected may be identified. Furthermore, each device may perform this process again based on the reason why the UE's request is rejected, or may perform the login process on other cells.

[0267] Furthermore, the UE may store the identification information received together with the login acceptance message and / or the login rejection message based on the completion of the login process, and may also identify the determination of the network. Furthermore, the UE may also perform processing based on the received login rejection message and various information included in the message. The specific processing performed by the UE in this embodiment is described in the following sections (3.1.4, 3.2, 3.3). [3.1.2. Service request process]

[0268] Next, the outline of the service request process is described. Hereinafter, the service request process is also referred to as this process. It should be noted that the service request process may include a network-led process and a UE-led service request process.

[0269] In addition, the service request process of the present embodiment may be a process performed by a UE that logs in to the SNPN via a non-3GPP access (access network_B120). Hereinafter, unless otherwise specified, the service request process to the SNPN via a non-3GPP access will also be referred to as this process. In addition, this process may also be a process performed by a UE in an SNPN access operation mode or a SNPN access mode. Moreover, this process may also be a process performed by a UE in the case of a direct connection to the SNPN via a non-3GPP access.

[0270] This process under the UE-led situation is a process for a UE in a non-connected state (CM-IDLE state) to establish a connection with the AMF in the core network_B via the N1 interface, and can be transformed into a connected state (CM-CONNECTED state) after executing this process. In addition, a UE in a non-connected state or a connected state is also a process for activating the U-Plane connection of an established PDU session.

[0271] First, the UE sends a Service Request message to the AMF via non-3GPP access.

[0272] When this process is successful or allowed by the network, the AMF may send a Service Accept message to the UE via access network _B, and the UE and each device complete the process.

[0273] It should be noted that, when the UE receives a service acceptance message from the AMF via access network_B, the trial counter and / or event counter may be deleted or reset. Details are described later (3.1.4, 3.2, 3.3).

[0274] On the contrary, if this process fails or is not allowed by the network, the AMF may send a Service Reject message to the UE.

[0275] Here, the service rejection message received by the UE from the AMF may include any one or more of the following as rejection reason values ​​(5GMM cause value): illegal UE (Illegal UE; rejection reason value #3) or illegal ME (Illegal ME; rejection reason value #6) or 5GS services not allowed (5GS services not allowed; rejection reason value #7) or N1 mode not allowed (N1 mode not allowed; rejection reason value #27) or 5GCN connection via non-3GPP access is not allowed (Non-3GPP access to 5GCN not allowed; rejection reason value #72) or temporarily not allowed for this SNPN (Temporarily not authorized for this SNPN; rejection reason value #74) or permanently not allowed for this SNPN (Permanently not authorized for this SNPN; rejection reason value #75).

[0276] Moreover, the service rejection message received by the UE from the AMF may also be a message without integrity guarantee. Conversely, the service rejection message received by the UE from the AMF may also be a message with guaranteed integrity. Here, the integrity confirmation of the rejection message may be performed by the NAS.

[0277] In addition, the UE that receives the service rejection message may stop timer T3510 or timer T3517 and execute timer T3247 when executing timer T3510 or timer T3517. Here, the UE stops timer T3510 or timer T3517 and then executes timer T3247 when the integrity of the received service rejection message is not guaranteed and / or the rejection reason value includes any one or more of rejection reason value #3, rejection reason value #6, rejection reason value #7, rejection reason value #27, rejection reason value #72, rejection reason value #74, or rejection reason value #75.

[0278] The UE and each device can complete this process based on the service acceptance message or service rejection message sent by the UE from the AMF. In addition, the UE can also perform processing based on various messages received and various information included in the message. The specific processing performed by the UE in this embodiment is described in the following sections (3.1.4, 3.2, 3.3). [3.1.3. One-time authentication process]

[0279] Next, the primary authentication process is described. Here, the primary authentication process of this embodiment can be a process performed by a UE that attempts to log in or connect to the SNPN via a non-3GPP access (access network_B120) or a UE that connects to the SNPN via a non-3GPP access (access network_B120). It should be noted that in this chapter, the primary authentication process is also referred to as this process.

[0280] This process can be an EAP based primary authentication and key agreement procedure, or an EAP-AKA' (Extensible Authentication Protocol Method for 3rd Generation Authentication and KeyAgreement) association process or an EAP-TLS (Extensible Authentication Protocol-Transport Layer Security) association process or an EAP-AKA' and a process associated with an EAP method other than EAP-TLS.

[0281] In addition, this process may be an authentication process performed in the login process or service request process described in this chapter (Chapter 3.1.). For example, it may be a process performed in the authentication / security (S609) in the login process described in Section 3.1.1. Alternatively, it may be a process performed by the UE and each device as a process other than these processes or as an independent process.

[0282] It should be noted that, unless otherwise specified, this process is set to perform message transmission and reception between UE and AMF via non-3GPP access (access network_B120). In addition, this process can also be a process performed by a UE operating in SNPN access operation mode or SNPN access mode.

[0283] In this process, first, the AMF sends an authentication request (Authentication Request) message including an EAP request message to the UE via access network_B. The UE that receives the authentication request (Authentication Request) message including the EAP request message from the AMF sends an authentication response (Authentication Response) including an EAP response message to the EAP request message to the AMF via access network_B. Here, the EAP request message and the EAP response message to the EAP request message can correspond one to one.

[0284] Then, the UE and the AMF receive the required number of EAP request messages and EAP response messages to the EAP request messages.

[0285] When this process is successful or allowed by the network, the AMF sends a Security Mode Command including an EAP-success message to the UE, and the UE and each device complete the process.

[0286] It should be noted that, when the UE receives an acceptance message from the AMF, the trial counter and / or event counter may be deleted or reset. Details are described later (3.1.4, 3.2, 3.3).

[0287] On the contrary, if this process fails or is not allowed by the network, the AMF may include an EAP-failure message in a Registration Reject message, a Service Reject message, a Registration Accept message, a Service Accept message, or an Authentication Reject message and send it to the UE.

[0288] Here, the login rejection message or service rejection message or authentication rejection message including the EAP failure message received by the UE from the AMF may also include any one or more of the following as rejection reason values ​​(5GMM cause value): illegal UE (Illegal UE; rejection reason value #3) or illegal ME (Illegal ME; rejection reason value #6) or 5GS services not allowed (5GSservices not allowed; rejection reason value #7) or N1 mode not allowed (N1 mode not allowed; rejection reason value #27) or 5GCN connection via non-3GPP access is not allowed (Non-3GPP access to 5GCN not allowed; rejection reason value #72) or the SNPN is temporarily not allowed (Temporarily not authorized for this SNPN; rejection reason value #74) or the SNPN is permanently not allowed (Permanently not authorized for this SNPN; rejection reason value #75).

[0289] In addition, the login rejection message, service rejection message, or authentication rejection message including the EAP failure message received by the UE from the AMF may be a message that does not guarantee integrity. Conversely, the login rejection message, service rejection message, or authentication rejection message including the EAP failure message received by the UE from the AMF may also be a message that guarantees integrity. Here, the integrity confirmation of the rejection message may be performed by the NAS.

[0290] In addition, the AMF may include either an EAP success message or an EAP failure message in the Authentication Result message.

[0291] The UE and each device may complete this process based on the UE receiving various messages including EAP success messages or EAP failure messages sent from the AMF. Moreover, the UE may also perform processing based on the various messages received and the various information included in the messages. The specific processing performed by the UE in this embodiment is described in the following sections (3.1.4, 3.2, 3.3). [3.1.4. Processing of counters, etc. in each process]

[0292] The processing of the counters in each process is described below. Note that in this chapter, the processing of the counters in each process is also referred to as the present processing.

[0293] This processing is performed when the UE receives a login rejection message, service request message or authentication rejection message including a rejection reason value (5GMM cause value) during the login process, service request process or authentication process when the UE is connected to the SNPN or SNPN service or attempts to connect via the PLMN.

[0294] Here, the rejection reason value (5GMM cause value) can be any one or more of the following: illegal UE (Illegal UE; rejection reason value #3) or illegal ME (Illegal ME; rejection reason value #6) or 5GS services not allowed (5GSservices not allowed; rejection reason value #7) or N1 mode not allowed (N1 mode not allowed; rejection reason value #27) or 5GCN connection via non-3GPP access is not allowed (Non-3GPP access to 5GCN not allowed; rejection reason value #72) or temporarily not allowing the SNPN (Temporarily not authorized for this SNPN; rejection reason value #74) or permanently not allowing the SNPN (Permanently not authorized for this SNPN; rejection reason value #75).

[0295] In this process, the counter stored, maintained, and managed by the UE may be a trial counter #1 or an event counter #1. It should be noted that, here, the UE that maintains, stores, and manages the trial counter #1 or the event counter #1 may be a UE operating in the SNPN access operation mode.

[0296] Moreover, the UE in this process may store, maintain and manage a permanently forbidden SNPN list (“permanently forbidden SNPNs” list) and / or a temporarily forbidden SNPN list (“temporarily forbidden SNPNs” list).

[0297] In addition, the login process in this process may also be an initial login process or a mobile or periodic registration update process. Furthermore, unless otherwise specified, the login process of this embodiment may be a login for loading services in SNPN or an execution of an initial login in SNPN for loading services.

[0298] On the other hand, the UE may delete or reset the trial counter #1 and / or the event counter #1 upon receiving a login accept message, a service accept message, or an authentication accept message during a login procedure, a service request procedure, or an authentication procedure.

[0299] Next, the details of the processing related to the management of various counters after the UE receives the above-mentioned rejection message from the network are described below. · Trial counter #1 increment

[0300] In a process (service request process) or a process (login process or authentication process) in which a UE operating in the SNPN access operation mode is connected to an SNPN service via a PLMN, the UE may receive a rejection message (login rejection message or service rejection message or authentication rejection message) including a rejection reason value and not guaranteeing integrity via a non-3GPP access, or based on the reception, the trial counter #1 or the trial counter #1 value may be incremented by 1. Here, the rejection reason value may be a rejection reason value #27 and / or a rejection reason value #72 and / or a rejection reason value #74 and / or a rejection reason value #75.

[0301] Furthermore, the addition of the trial counter #1 may also be performed during the execution of the timer T3247. Here, the timer T3247 may be a timer started when the UE receives a login rejection message, a service rejection message, or an authentication rejection message. Furthermore, the timer T3247 may also be a timer started when the integrity of various rejection messages (login rejection message, service rejection message, or authentication rejection message) received by the UE is not guaranteed.

[0302] The increment of the trial counter #1 may also be performed when the rejection reason value is the rejection reason value #27 and / or the rejection reason value #72. The increment of the trial counter #1 may also be performed when the rejection reason value is the rejection reason value #74 and / or the rejection reason value #75, and when the UE receives the rejection message (login rejection message, service rejection message, or authentication rejection message), and when the trial counter #1 is a value less than the maximum value specific to the UE installation.

[0303] Alternatively, when a UE operating in SNPN access operation mode receives a login rejection message with non-integrity guaranteed including illegal UE (Illegal UE; #3) and / or illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7) as a rejection reason value via non-3GPP access during the login process for loading services in SNPN or the initial login process in SNPN for loading services, the UE may increase the value of trial counter #1 or trial counter #1 by 1. Increment event counter #1

[0304] In the process (service request process) or the process (login process or authentication process) of attempting to connect to an SNPN service via a PLMN when a UE operating in the SNPN access operation mode logs in or connects to an SNPN service, the UE may receive a rejection message (login rejection message or service rejection message or authentication rejection message) including a rejection reason value via a non-3GPP access without ensuring integrity or based on the reception, and add (increment) 1 to the value of event counter #1 or event counter #1. Here, the rejection reason value may be an illegal UE (Illegal UE; #3) and / or an illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7).

[0305] Moreover, the addition of the event counter #1 may also be performed during the execution of the timer T3247. Here, the timer T3247 may be a timer started when the UE receives a login rejection message, a service rejection message, or an authentication rejection message. Moreover, the timer T3247 may also be a timer started when the integrity of various rejection messages (login rejection message, service rejection message, or authentication rejection message) received by the UE is not guaranteed.

[0306] The addition of event counter #1 may also be performed when the UE is not logged in on other accesses (3GPP access) and when event counter #1 is a value below a maximum value specific to the UE installation.

[0307] Alternatively, when a UE operating in the SNPN access operation mode is not in the process of logging in for loading services in the SNPN via non-3GPP access or the initial logging in the SNPN for loading services, and receives a login rejection message without integrity guarantee including illegal UE (Illegal UE; #3) and / or illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GSservices not allowed; #7) as the rejection reason value via non-3GPP access, the UE may add 1 to event counter #1 or the value of event counter #1. Set the UE installation-specific maximum value for trial counter #1

[0308] In the case where a UE operating in the SNPN access operation mode logs in or connects to an SNPN service via a PLMN (service request process) or attempts to connect (login process or authentication process) or is used for loading services in an SNPN (login process or authentication process) or logs in to an SNPN for loading services, the UE may receive a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity guaranteed including a rejection reason value via a non-3GPP access or based on the reception, set a maximum value specific to the UE installation for the trial counter #1, store or add the SNPN ID for performing the login process for loading services to the list of SNPNs permanently prohibited for loading services, and perform SNPN selection for loading services. Here, the rejection reason value may be an illegal UE (Illegal UE; #3) and / or an illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7).

[0309] Alternatively, in the process (service request process) or the process (login process or authentication process) of the UE operating in the SNPN access operation mode logging in or connecting to the SNPN service via the PLMN, the UE may receive a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity guaranteed including a rejection reason value via non-3GPP access or based on the reception, set the trial counter #1 to a UE installation-specific maximum value, and disable the N1 mode capability (N1 mode capability) for non-3GPP access. It should be noted that the process in which the UE receives a rejection message with integrity guaranteed may not be a process in which the UE is not logged in to the SNPN for loading services or a process (login process or authentication process) for loading services in the SNPN. Here, the rejection reason value may be that the N1 mode is not allowed (N1 mode not allowed; #27) and / or that 5GCN connection via non-3GPP access is not allowed (Non-3GPP access to 5GCN not allowed; #72).

[0310] Alternatively, in a process (service request process) or a process (login process or authentication process) in which a UE operating in the SNPN access operation mode logs in or connects to an SNPN service via a PLMN, the UE may set a UE installation-specific maximum value for the trial counter #1 when or based on receiving a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity including a rejection reason value via a non-3GPP access. Here, the rejection reason value may be temporarily not authorized for this SNPN (Temporarily not authorized for this SNPN; #74) and / or permanently not authorized for this SNPN (Permanently not authorized for this SNPN; #75). Set a UE installation-specific maximum value for event counter #1

[0311] In the process (service request process) or the process (login process or authentication process) of the UE operating in the SNPN access operation mode logging in or connecting to the SNPN service via the PLMN, the UE may set the value of event counter #1 or event counter #1 to the maximum value specific to the UE installation when or based on the reception of a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity guaranteed including a rejection reason value via non-3GPP access. Here, the rejection reason value may be an illegal UE (Illegal UE; #3) and / or an illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7). Here, the process of the UE receiving the rejection message may not be a login process for loading services in the SNPN. Action based on trial counter #1 and rejection reason value

[0312] In the process (service request process) or the process (login process or authentication process) of attempting to connect to an SNPN service via a PLMN when a UE operating in the SNPN access operation mode logs in or connects to an SNPN service, when a rejection message (login rejection message or service rejection message or authentication rejection message) that does not guarantee integrity including a rejection reason value is received via non-3GPP access, and when the trial counter #1 is one or more and less than the maximum value specific to the UE installation, the UE may delete the SNPN ID corresponding to the execution process from the permanently prohibited SNPN list for non-3GPP access or the temporarily prohibited SNPN list for non-3GPP access. Here, the rejection reason value may be any one or more of the rejection reason value #3 and / or the rejection reason value #6 and / or the rejection reason value #7 and / or the rejection reason value #27 and / or the rejection reason value #72 and / or the rejection reason value #74 and / or the rejection reason value #75. Moreover, the deletion of the above-mentioned SNPN ID may also be performed when the UE supports the use of the certificate provided by the certificate holder in the SNPN connection.

[0313] Moreover, in addition to the above conditions, the UE can re-enable the N1 mode capability for non-3GPP access when timer T3247, which is started when the UE receives a login reject message or a service reject message as a rejection message without integrity guarantee including a rejection reason value, expires, and can delete the corresponding SNPN ID of the execution process from the permanently prohibited SNPN list or the temporarily prohibited SNPN list when the trial counter #1 is one or more and less than the maximum value specific to the UE installation.

[0314] Alternatively, in addition to the above conditions, the UE may also delete the corresponding SNPN ID of the execution process from the permanently prohibited SNPN list for non-3GPP access or the temporarily prohibited SNPN list for non-3GPP access when the power is disconnected or the UICC including the USIM is removed from the UE.

[0315] Alternatively, in addition to the above conditions, the UE may also delete the corresponding SNPN ID for the execution process from the list of permanently prohibited SNPNs for non-3GPP access or the list of temporarily prohibited SNPNs for non-3GPP access when an entry in the list of subscription data is updated, the UE does not support the use of the certificate by the certificate holder in a connection to the SNPN, and the trial counter #1 corresponding to the updated entry is one or more and less than a maximum value specific to the UE installation.

[0316] Alternatively, in addition to the above conditions, the UE may also, when an entry in the list of subscription data is updated and the UE supports the use of the certificate by the certificate holder in a connection to the SNPN, delete the SNPN ID corresponding to the updated entry from the list of permanently prohibited SNPNs for non-3GPP access or the list of temporarily prohibited SNPNs for non-3GPP access when the trial counter #1 for the SNPN corresponding to the entry included in the list of permanently prohibited SNPNs for non-3GPP access or the list of temporarily prohibited SNPNs for non-3GPP access is one or more and less than a maximum value specific to the UE installation. Action based on event counter #1 and rejection reason value

[0317] In the process (service request process) or the process (login process or authentication process) of attempting to connect (login process or authentication process) when a UE operating in the SNPN access operation mode logs in or connects to an SNPN service via a PLMN, when a rejection message (login rejection message or service rejection message or authentication rejection message) without integrity guarantee including a rejection reason value is received via a non-3GPP access, and when event counter #1 is less than the maximum value specific to the UE installation, the UE can set the non-3GPP access to be valid for each entry in the list of subscription data. It should be noted that the validity of the non-3GPP access may refer to the validity of either or both of the connection from the UE to the SNPN via the PLMN or the direct connection via the non-3GPP access.

[0318] Here, the rejection reason value may be any one or more of the rejection reason value #3 and / or the rejection reason value #6 and / or the rejection reason value #7 and / or the rejection reason value #27 and / or the rejection reason value #72 and / or the rejection reason value #74 and / or the rejection reason value #75. Moreover, setting the above-mentioned non-3GPP access to be valid may also be performed when the UE supports the use of the certificate provided by the certificate holder in the SNPN connection. [3.2. First embodiment]

[0319] The first embodiment of the present invention is a case where the UE is directly connected to the SNPN or SNPN service via a non-3GPP access, and the UE receives a login rejection message or a service request message or an authentication rejection message including a rejection reason value (5GMM cause value) during a login process or a service request process or an authentication process. It should be noted that in this chapter, the first embodiment is also referred to as this embodiment.

[0320] Moreover, the present embodiment is an embodiment in which the same trial counter and / or the same event counter are used in the case where the UE is connected to the SNPN or SNPN service via the PLMN and in the case where the UE is directly connected to the SNPN or SNPN service via the non-3GPP access. More specifically, it may also be an embodiment in which the UE of the present embodiment uses the same trial counter #2 and / or the same event counter #2 in either connection form, in the case where the UE is connected to the SNPN or SNPN service via the PLMN and in the case where the UE is directly connected to the SNPN or SNPN service via the non-3GPP access.

[0321] It should be noted that, in this embodiment, the counter stored, maintained, and managed by the UE may be a trial counter #2 or an event counter #2. It should be noted that, here, the UE that maintains, stores, and manages the trial counter #2 or the event counter #2 may be a UE operating in the SNPN access operation mode.

[0322] Moreover, the UE of this embodiment may store, maintain and manage a permanently forbidden SNPN list (“permanently forbidden SNPNs” list) and / or a temporarily forbidden SNPN list (“temporarily forbidden SNPNs” list).

[0323] It should be noted that the permanently prohibited SNPN list and / or the temporarily prohibited SNPN list can be used when the UE is connected to the SNPN or SNPN service via the PLMN and when the UE is directly connected to the SNPN or SNPN service via non-3GPP access.

[0324] In addition, this embodiment is a form that is an extension of the process in Chapter 3.1.4 and further considers the case where the UE is directly connected to the SNPN via a non-3GPP access.

[0325] Here, the rejection reason value (5GMM cause value) included in the login rejection message or service request message or authentication rejection message received by the UE may be any one or more of the following: illegal UE (Illegal UE; rejection reason value #3) or illegal ME (Illegal ME; rejection reason value #6) or 5GS services not allowed (5GS services notallowed; rejection reason value #7) or N1 mode not allowed (N1 mode not allowed; rejection reason value #27) or 5GCN connection via non-3GPP access is not allowed (Non-3GPP access to 5GCN not allowed; rejection reason value #72) or temporarily not allowed for this SNPN (Temporarily not authorized for this SNPN; rejection reason value #74) or permanently not allowed for this SNPN (Permanently not authorized for this SNPN; rejection reason value #75).

[0326] In addition, the login process of this embodiment may also be an initial login process or a mobile or periodic registration update process. Furthermore, unless otherwise specified, the login process of this embodiment may be a login for loading services in SNPN or an execution of an initial login in SNPN for loading services.

[0327] It should be noted that this embodiment may be a combination of one or more processes or processes described in Section 3.1 performed by the UE and / or the network, and the behavior of the UE when receiving any one or a combination of a login rejection message, a service rejection message, or an authentication rejection message from the network. In this embodiment, any one or a combination of a login rejection message, a service rejection message, or an authentication rejection message is also referred to as a rejection message.

[0328] On the other hand, the UE of this embodiment may delete or reset the trial counter #2 and / or event counter #2 upon receiving a login accept message, a service accept message, or an authentication accept message during a login process, a service request process, or an authentication process.

[0329] The following describes in detail the processing related to the management of various counters after the UE of this embodiment receives the above-mentioned rejection message from the network. · Trial increment of counter #2

[0330] In a process (service request process) or a process (login process or authentication process) in which a UE operating in the SNPN access operation mode directly connects to an SNPN service via a non-3GPP access, or in which the UE attempts to connect, the UE may receive a rejection message (login rejection message or service rejection message or authentication rejection message) including a rejection reason value via a non-3GPP access and not guaranteeing integrity, or based on the reception thereof, the trial counter #2 or the trial counter #2 value may be incremented by 1. Here, the rejection reason value may be a rejection reason value #27 and / or a rejection reason value #72 and / or a rejection reason value #74 and / or a rejection reason value #75.

[0331] Furthermore, the addition of the trial counter #2 may also be performed during the execution of the timer T3247. Here, the timer T3247 may be a timer started when the UE receives a login rejection message, a service rejection message, or an authentication rejection message. Furthermore, the timer T3247 may also be a timer started when the integrity of various rejection messages (login rejection message, service rejection message, or authentication rejection message) received by the UE is not guaranteed.

[0332] The increment of the trial counter #2 may also be performed when the rejection reason value is the rejection reason value #27 and / or the rejection reason value #72. The increment of the trial counter #2 may also be performed when the rejection reason value is the rejection reason value #74 and / or the rejection reason value #75, and when the UE receives the rejection message (login rejection message, service rejection message, or authentication rejection message), and when the trial counter #2 is a value less than the maximum value specific to the UE installation.

[0333] Alternatively, when a UE operating in SNPN access operation mode receives a login rejection message with non-integrity guaranteed including illegal UE (Illegal UE; #3) and / or illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7) as a rejection reason value via non-3GPP access during the login process for loading services in SNPN or the initial login process in SNPN for loading services, the UE may increase the value of trial counter #2 or trial counter #2 by 1. Increment event counter #2

[0334] In the process (service request process) or the process (login process or authentication process) in which a UE operating in the SNPN access operation mode directly logs in or connects to an SNPN service via a non-3GPP access, or attempts to connect, the UE may receive a rejection message (login rejection message or service rejection message or authentication rejection message) including a rejection reason value via a non-3GPP access without ensuring integrity, or based on the reception, the value of event counter #2 or event counter #2 may be incremented by 1. Here, the rejection reason value may be an illegal UE (Illegal UE; #3) and / or an illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7).

[0335] Moreover, the addition of the event counter #2 may also be performed in the execution of the timer T3247. Here, the timer T3247 may be a timer started when the UE receives a login rejection message, a service rejection message, or an authentication rejection message. Moreover, the timer T3247 may also be a timer started when the integrity of various rejection messages (login rejection message, service rejection message, or authentication rejection message) received by the UE is not guaranteed.

[0336] The addition of event counter #2 may also be performed when the UE is not logged in on other accesses (3GPP access) and when event counter #2 is a value below a maximum value specific to the UE installation.

[0337] Alternatively, when a UE operating in the SNPN access operation mode is not in the process of logging in for loading services in the SNPN via non-3GPP access or the initial logging in the SNPN for loading services, and receives a login rejection message without integrity guarantee including illegal UE (Illegal UE; #3) and / or illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GSservices not allowed; #7) as the rejection reason value via non-3GPP access, the UE may add 1 to event counter #2 or the value of event counter #2. Set the maximum value specific to the UE installation for Trial Counter #2

[0338] In the case where a UE operating in the SNPN access operation mode directly logs in or connects to an SNPN service via a non-3GPP access (service request process) or attempts to connect (login process or authentication process) or is used for loading services in the SNPN (login process or authentication process) or logs in to the SNPN to load services, the UE may receive a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity guaranteed including a rejection reason value via the non-3GPP access or based on the reception, set a maximum value specific to the UE installation for the trial counter #2, store or add the SNPN ID that performs the login process for the loading service to the list of SNPNs that are permanently prohibited for the loading service, and perform SNPN selection for the loading service. Here, the rejection reason value may be an illegal UE (IllegalUE; #3) and / or an illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7).

[0339] Alternatively, in the process (service request process) or the process (login process or authentication process) of the UE operating in the SNPN access operation mode directly logging in or connecting to the SNPN service via non-3GPP access, the UE may set the UE installation-specific maximum value for the trial counter #2 and disable the N1 mode capability (N1 mode capability) for non-3GPP access when or based on the reception of a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity guaranteed including a rejection reason value via non-3GPP access. It should be noted that the process in which the UE receives a rejection message with integrity guaranteed may not be a process in which the UE is not logged in to the SNPN for loading services or a process (login process or authentication process) for loading services in the SNPN. Here, the rejection reason value may be that the N1 mode is not allowed (N1 mode not allowed; #27) and / or that 5GCN connection via non-3GPP access is not allowed (Non-3GPP access to 5GCN not allowed; #72).

[0340] Alternatively, in a process (service request process) or a process (login process or authentication process) in which a UE operating in the SNPN access operation mode directly logs in or connects to an SNPN service via a non-3GPP access, the UE may set a UE installation-specific maximum value for the trial counter #2 when or based on receiving a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity including a rejection reason value via the non-3GPP access. Here, the rejection reason value may be temporarily not authorized for this SNPN (Temporarily not authorized for this SNPN; #74) and / or permanently not authorized for this SNPN (Permanently not authorized for thisSNPN; #75). Set a UE installation specific maximum value for event counter #2

[0341] In the process (service request process) or the process (login process or authentication process) in which a UE operating in the SNPN access operation mode directly logs in or connects to an SNPN service via a non-3GPP access, the UE may set the value of event counter #2 or event counter #2 to a maximum value specific to the UE installation when or based on receiving a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity including a rejection reason value via a non-3GPP access. Here, the rejection reason value may be an illegal UE (Illegal UE; #3) and / or an illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7). Here, the process in which the UE receives a rejection message may not be a login process for loading services in the SNPN. Action based on trial counter #2 and rejection reason value

[0342] In the process (service request process) or the process (login process or authentication process) of attempting to connect when a UE operating in the SNPN access operation mode directly logs in or connects to an SNPN service via a non-3GPP access, when a rejection message (login rejection message or service rejection message or authentication rejection message) including a rejection reason value without ensuring integrity is received via the non-3GPP access, and when the trial counter #2 is one or more and less than the maximum value specific to the UE installation, the UE can delete the SNPN ID corresponding to the execution process from the permanently prohibited SNPN list for non-3GPP access or the temporarily prohibited SNPN list for non-3GPP access. Here, the rejection reason value can be any one or more of the rejection reason value #3 and / or the rejection reason value #6 and / or the rejection reason value #7 and / or the rejection reason value #27 and / or the rejection reason value #72 and / or the rejection reason value #74 and / or the rejection reason value #75. Moreover, the deletion of the above-mentioned SNPN ID can also be performed when the UE supports the use of the certificate provided by the certificate holder in the SNPN connection.

[0343] Moreover, in addition to the above conditions, the UE can re-enable the N1 mode capability for non-3GPP access when timer T3247, which is started when the UE receives a login reject message or a service reject message as a rejection message without integrity guarantee including a rejection reason value, expires, and can delete the corresponding SNPN ID of the execution process from the permanently prohibited SNPN list or the temporarily prohibited SNPN list when the trial counter #2 is one or more and less than the maximum value specific to the UE installation.

[0344] Alternatively, in addition to the above conditions, the UE may also delete the corresponding SNPN ID of the execution process from the permanently prohibited SNPN list for non-3GPP access or the temporarily prohibited SNPN list for non-3GPP access when the power is disconnected or the UICC including the USIM is removed from the UE.

[0345] Alternatively, in addition to the above conditions, the UE may also delete the corresponding SNPN ID for the execution process from the list of permanently prohibited SNPNs for non-3GPP access or the list of temporarily prohibited SNPNs for non-3GPP access when an entry in the list of subscription data is updated, the UE does not support the use of the certificate by the certificate holder in the connection to the SNPN, and the trial counter #2 corresponding to the updated entry is one or more and less than a maximum value specific to the UE installation.

[0346] Alternatively, in addition to the above conditions, the UE may also, when an entry in the list of subscription data is updated and the UE supports the use of the certificate by the certificate holder in a connection to the SNPN, delete the SNPN ID corresponding to the updated entry from the list of permanently prohibited SNPNs for non-3GPP access or the list of temporarily prohibited SNPNs for non-3GPP access when the trial counter #2 for the SNPN corresponding to the entry included in the list of permanently prohibited SNPNs for non-3GPP access or the list of temporarily prohibited SNPNs for non-3GPP access is one or more and less than a maximum value specific to the UE installation. Action based on event counter #2 and rejection reason value

[0347] In the process (service request process) or the process (login process or authentication process) of attempting to connect to the SNPN service via non-3GPP access when the UE operating in the SNPN access operation mode directly logs in or connects to the SNPN service via non-3GPP access, when a rejection message (login rejection message or service rejection message or authentication rejection message) without integrity guarantee including a rejection reason value is received via non-3GPP access, and when event counter #2 is less than the maximum value specific to the UE installation, the UE can set the non-3GPP access to be valid for each entry in the list of subscription data. It should be noted that the validity of non-3GPP access may refer to the validity of either or both of the connection from the UE to the SNPN via the PLMN or the direct connection via the non-3GPP access.

[0348] Here, the rejection reason value may be any one or more of the rejection reason value #3 and / or the rejection reason value #6 and / or the rejection reason value #7 and / or the rejection reason value #27 and / or the rejection reason value #72 and / or the rejection reason value #74 and / or the rejection reason value #75. Moreover, setting the above-mentioned non-3GPP access to be valid may also be performed when the UE supports the use of the certificate provided by the certificate holder in the SNPN connection. [3.3. Second embodiment]

[0349] The second embodiment of the present invention is a case where the UE is directly connected to the SNPN or SNPN service via a non-3GPP access, and the UE receives a login rejection message or a service request message or an authentication rejection message including a rejection reason value (5GMM cause value) during a login process or a service request process or an authentication process. It should be noted that in this chapter, the second embodiment is also referred to as this embodiment.

[0350] Moreover, the present embodiment is an embodiment in which different trial counters and / or different event counters are used in the case where the UE is connected to the SNPN or SNPN service via the PLMN and in the case where the UE is directly connected to the SNPN or SNPN service via the non-3GPP access. More specifically, the present embodiment is an embodiment in which the UE of the present embodiment uses trial counter #1 and event counter #1 in the case where the UE is connected to the SNPN or SNPN service via the PLMN, and uses trial counter #3 and event counter #3 in the case where the UE is directly connected to the SNPN or SNPN service via the non-3GPP access.

[0351] It should be noted that, in this embodiment, the counter stored, maintained, and managed by the UE may be a trial counter #3 or an event counter #3. It should be noted that, here, the UE that maintains and / or stores and / or manages the trial counter #3 or the event counter #3 may be a UE operating in the SNPN access operation mode.

[0352] Moreover, the UE of this embodiment may store, maintain and manage a permanently forbidden SNPN list (“permanently forbidden SNPNs” list) and / or a temporarily forbidden SNPN list (“temporarily forbidden SNPNs” list).

[0353] It should be noted that the permanently prohibited SNPN list and / or the temporarily prohibited SNPN list can be managed independently by the UE in a list associated with the case of connecting to the SNPN or SNPN service via the PLMN and a list associated with the case of directly connecting to the SNPN or SNPN service via non-3GPP access.

[0354] In other words, the UE can store, maintain and manage a permanently banned SNPN list and / or a temporarily banned SNPN list for the case of connecting to a SNPN or a SNPN service via a PLMN and a permanently banned SNPN list and / or a temporarily banned SNPN list for the case of directly connecting to a SNPN or a SNPN service via a non-3GPP access.

[0355] In addition, this embodiment is a form that is an extension of the process in Chapter 3.1.4 and further considers the case where the UE is directly connected to the SNPN via a non-3GPP access.

[0356] Here, the rejection reason value (5GMM cause value) included in the login rejection message or service request message or authentication rejection message received by the UE may be any one or more of the following: illegal UE (Illegal UE; rejection reason value #3) or illegal ME (Illegal ME; rejection reason value #6) or 5GS services not allowed (5GS services notallowed; rejection reason value #7) or N1 mode not allowed (N1 mode not allowed; rejection reason value #27) or 5GCN connection via non-3GPP access is not allowed (Non-3GPP access to 5GCN not allowed; rejection reason value #72) or temporarily not allowed for this SNPN (Temporarily not authorized for this SNPN; rejection reason value #74) or permanently not allowed for this SNPN (Permanently not authorized for this SNPN; rejection reason value #75).

[0357] In addition, the login process of this embodiment may also be an initial login process or a mobile or periodic registration update process. Furthermore, unless otherwise specified, the login process of this embodiment may be a login for loading services in SNPN or an execution of an initial login in SNPN for loading services.

[0358] It should be noted that this embodiment may be a combination of one or more processes or processes described in Section 3.1 performed by the UE and / or the network, and the behavior of the UE when receiving any one or a combination of a login rejection message, a service rejection message, or an authentication rejection message from the network. In this embodiment, any one or a combination of a login rejection message, a service rejection message, or an authentication rejection message is also referred to as a rejection message.

[0359] On the other hand, the UE of this embodiment may delete or reset the trial counter #3 and / or event counter #3 upon receiving a login accept message, a service accept message, or an authentication accept message during a login process, a service request process, or an authentication process.

[0360] The following describes in detail the processing related to the management of various counters after the UE of this embodiment receives the above-mentioned rejection message from the network. · Trial increment of counter #3

[0361] In a process (service request process) or a process (login process or authentication process) in which a UE operating in the SNPN access operation mode directly connects to an SNPN service via a non-3GPP access, or in which the UE attempts to connect, the UE may receive a rejection message (login rejection message or service rejection message or authentication rejection message) that does not guarantee integrity and includes a rejection reason value via the non-3GPP access, or based on the reception, the trial counter #3 or the trial counter #3 value may be incremented by 1. Here, the rejection reason value may be a rejection reason value #27 and / or a rejection reason value #72 and / or a rejection reason value #74 and / or a rejection reason value #75.

[0362] Furthermore, the addition of the trial counter #3 may also be performed during the execution of the timer T3247. Here, the timer T3247 may be a timer started when the UE receives a login rejection message, a service rejection message, or an authentication rejection message. Furthermore, the timer T3247 may also be a timer started when the integrity of various rejection messages (login rejection message, service rejection message, or authentication rejection message) received by the UE is not guaranteed.

[0363] The increment of the trial counter #3 may also be performed when the rejection reason value is the rejection reason value #27 and / or the rejection reason value #72. The increment of the trial counter #3 may also be performed when the rejection reason value is the rejection reason value #74 and / or the rejection reason value #75, and when the UE receives the rejection message (login rejection message, service rejection message, or authentication rejection message), and when the trial counter #3 is a value less than the maximum value specific to the UE installation.

[0364] Alternatively, when a UE operating in SNPN access operation mode receives a login rejection message with non-integrity guaranteed including illegal UE (Illegal UE; #3) and / or illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7) as a rejection reason value via non-3GPP access during the login process for loading services in SNPN or the initial login process in SNPN for loading services, the UE may increase the value of trial counter #3 or trial counter #3 by 1. Increment event counter #3

[0365] In the process (service request process) or the process (login process or authentication process) in which a UE operating in the SNPN access operation mode directly logs in or connects to an SNPN service via a non-3GPP access, or attempts to connect, the UE may receive a rejection message (login rejection message or service rejection message or authentication rejection message) that does not guarantee integrity and includes a rejection reason value via a non-3GPP access, or based on the reception, the value of event counter #3 or event counter #3 may be incremented by 1. Here, the rejection reason value may be an illegal UE (Illegal UE; #3) and / or an illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7).

[0366] Moreover, the addition of the event counter #3 may also be performed in the execution of the timer T3247. Here, the timer T3247 may be a timer started when the UE receives a login rejection message, a service rejection message, or an authentication rejection message. Moreover, the timer T3247 may also be a timer started when the integrity of various rejection messages (login rejection message, service rejection message, or authentication rejection message) received by the UE is not guaranteed.

[0367] The addition of event counter #3 may also be performed when the UE is not logged in on other accesses (3GPP access) and when event counter #3 is a value below a maximum value specific to the UE installation.

[0368] Alternatively, when a UE operating in the SNPN access operation mode is not in the process of logging in for loading services in the SNPN via non-3GPP access or the initial logging in the SNPN for loading services, and receives a login rejection message without integrity guarantee including illegal UE (Illegal UE; #3) and / or illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GSservices not allowed; #7) as the rejection reason value via non-3GPP access, the UE may add 1 to event counter #3 or the value of event counter #3. Set the UE installation-specific maximum value for trial counter #3

[0369] In the case where a UE operating in the SNPN access operation mode directly logs in or connects to an SNPN service via a non-3GPP access (service request process) or attempts to connect (login process or authentication process) or is used for loading services in the SNPN (login process or authentication process) or logs in to the SNPN to load services, the UE may receive a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity guaranteed including a rejection reason value via the non-3GPP access or based on the reception, set a maximum value specific to the UE installation for the trial counter #3, store or add the SNPN ID that performs the login process for the loading service to the list of SNPNs that are permanently prohibited for the loading service, and perform SNPN selection for the loading service. Here, the rejection reason value may be an illegal UE (IllegalUE; #3) and / or an illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7).

[0370] Alternatively, in the process (service request process) or the process (login process or authentication process) of the UE operating in the SNPN access operation mode directly logging in or connecting to the SNPN service via non-3GPP access, the UE may receive a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity guaranteed including a rejection reason value via non-3GPP access or based on the reception, set the UE installation-specific maximum value for the trial counter #3, and disable the N1 mode capability (N1 mode capability) for non-3GPP access. It should be noted that the process in which the UE receives a rejection message with integrity guaranteed may not be a process in which the UE is not logged in to the SNPN for loading services or a process (login process or authentication process) for loading services in the SNPN. Here, the rejection reason value may be that N1 mode is not allowed (N1 mode not allowed; #27) and / or 5GCN connection via non-3GPP access is not allowed (Non-3GPP access to 5GCN not allowed; #72).

[0371] Alternatively, in a process (service request process) or a process (login process or authentication process) in which a UE operating in the SNPN access operation mode directly logs in or connects to a SNPN service via a non-3GPP access, the UE may set a UE installation-specific maximum value for the trial counter #3 when or based on receiving a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity including a rejection reason value via the non-3GPP access. Here, the rejection reason value may be temporarily not authorized for this SNPN (Temporarily not authorized for this SNPN; #74) and / or permanently not authorized for this SNPN (Permanently not authorized for thisSNPN; #75). Set a UE installation specific maximum value for event counter #3

[0372] In the process (service request process) or the process (login process or authentication process) in which a UE operating in the SNPN access operation mode directly logs in or connects to an SNPN service via a non-3GPP access, the UE may set the value of event counter #3 or event counter #3 to a maximum value specific to the UE installation when or based on receiving a rejection message (login rejection message or service rejection message or authentication rejection message) with integrity including a rejection reason value via a non-3GPP access. Here, the rejection reason value may be an illegal UE (Illegal UE; #3) and / or an illegal ME (Illegal ME; #6) and / or 5GS services not allowed (5GS services not allowed; #7). Here, the process in which the UE receives a rejection message may not be a login process for loading services in the SNPN. Action based on trial counter #3 and rejection reason value

[0373] In the process (service request process) or the process (login process or authentication process) of attempting to connect to the SNPN service when the UE operating in the SNPN access operation mode directly logs in or connects to the SNPN service via non-3GPP access, when a rejection message (login rejection message or service rejection message or authentication rejection message) including a rejection reason value without ensuring integrity is received via non-3GPP access, and when the trial counter #3 is one or more and less than the maximum value specific to the UE installation, the UE can delete the SNPN ID corresponding to the execution process from the permanently prohibited SNPN list for non-3GPP access or the temporarily prohibited SNPN list for non-3GPP access. Here, the rejection reason value can be any one or more of the rejection reason value #3 and / or the rejection reason value #6 and / or the rejection reason value #7 and / or the rejection reason value #27 and / or the rejection reason value #72 and / or the rejection reason value #74 and / or the rejection reason value #75. Moreover, the deletion of the above-mentioned SNPN ID can also be performed when the UE supports the use of the certificate provided by the certificate holder in the SNPN connection.

[0374] Moreover, in addition to the above conditions, the UE can re-enable the N1 mode capability for non-3GPP access when timer T3247, which is started when the UE receives a login reject message or a service reject message as a rejection message without integrity guarantee including a rejection reason value, expires, and can delete the corresponding SNPN ID of the execution process from the permanently prohibited SNPN list or the temporarily prohibited SNPN list when the trial counter #3 is one or more and less than the maximum value specific to the UE installation.

[0375] Alternatively, in addition to the above conditions, the UE may also delete the corresponding SNPN ID of the execution process from the permanently prohibited SNPN list for non-3GPP access or the temporarily prohibited SNPN list for non-3GPP access when the power is disconnected or the UICC including the USIM is removed from the UE.

[0376] Alternatively, in addition to the above conditions, the UE may also delete the corresponding SNPN ID for the execution process from the list of permanently prohibited SNPNs for non-3GPP access or the list of temporarily prohibited SNPNs for non-3GPP access when an entry in the list of subscription data is updated, the UE does not support the use of the certificate by the certificate holder in the connection to the SNPN, and the trial counter #3 corresponding to the updated entry is one or more and less than a maximum value specific to the UE installation.

[0377] Alternatively, in addition to the above conditions, the UE may also, when an entry in the list of subscription data is updated and the UE supports the use of the certificate by the certificate holder in a connection to the SNPN, delete the SNPN ID corresponding to the updated entry from the list of permanently prohibited SNPNs for non-3GPP access or the list of temporarily prohibited SNPNs for non-3GPP access when the trial counter #3 for the SNPN corresponding to the entry included in the list of permanently prohibited SNPNs for non-3GPP access or the list of temporarily prohibited SNPNs for non-3GPP access is one or more and less than a maximum value specific to the UE installation. Action based on event counter #3 and rejection reason value

[0378] In the process (service request process) or the process (login process or authentication process) of attempting to connect to the SNPN service via non-3GPP access when the UE operating in the SNPN access operation mode directly logs in or connects to the SNPN service via non-3GPP access, when a rejection message (login rejection message or service rejection message or authentication rejection message) without integrity guarantee including a rejection reason value is received via non-3GPP access, and when event counter #3 is less than the maximum value specific to the UE installation, the UE can set the non-3GPP access to be valid for each entry in the list of subscription data. It should be noted that the validity of the non-3GPP access may refer to the validity of either or both of the connection from the UE to the SNPN via the PLMN or the direct connection via the non-3GPP access.

[0379] Here, the rejection reason value may be any one or more of the rejection reason value #3 and / or the rejection reason value #6 and / or the rejection reason value #7 and / or the rejection reason value #27 and / or the rejection reason value #72 and / or the rejection reason value #74 and / or the rejection reason value #75. Moreover, setting the above-mentioned non-3GPP access to be valid may also be performed when the UE supports the use of the certificate provided by the certificate holder in the SNPN connection. [4. Modifications]

[0380] The program that works through the device of the present invention may be a program that controls a CPU (Central Processing Unit) or the like to make the computer function to implement the functions of the embodiments of the present invention. The program or the information processed by the program is temporarily stored in a volatile memory such as a random access memory (RAM) or a non-volatile memory such as a flash memory, a hard disk drive (HDD) or other storage device system.

[0381] It should be noted that the program for realizing the functions of the embodiments involved in the present invention may also be recorded in a computer-readable recording medium. This can be achieved by reading the program recorded in the recording medium into a computer system and executing it. The "computer system" referred to here refers to a computer system built into a device, and includes a computer system of hardware such as an operating system and peripherals. In addition, a "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically retains a program for a short period of time, or other computer-readable recording media.

[0382] In addition, each functional block or each feature of the device used in the above-mentioned embodiments can be installed or executed in a circuit, such as an integrated circuit or multiple integrated circuits. Circuits designed in a manner to perform the functions described in this specification may include: a general-purpose processor, a digital signal processor (DSP), an integrated circuit for a specific purpose (ASIC), a field programmable gate array (FPGA) or other programmable logic elements, discrete gates or transistor logic, discrete hardware parts, or a combination thereof. The general-purpose processor may be a microprocessor, or it may be a processor, controller, microcontroller, or state machine of the previous type. The aforementioned circuit may be composed of digital circuits or analog circuits. In addition, in the case where integrated circuit technology that replaces the current integrated circuit appears due to advances in semiconductor technology, one or more schemes of the present invention may also use new integrated circuits based on this technology.

[0383] It should be noted that the present invention is not limited to the above-mentioned embodiments. In the embodiments, an example of a device is described, but the present invention is not limited thereto and can be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning, washing equipment, air conditioning equipment, office equipment, vending machines, other life equipment, and other terminal devices or communication devices.

[0384] The embodiments of the present invention are described in detail with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiment, and also includes design changes within the scope of the gist of the present invention. In addition, the present invention can be variously modified within the scope indicated by the claims, and the embodiments obtained by appropriately combining the technical solutions disclosed in different embodiments are also included in the technical scope of the present invention. In addition, it also includes a configuration obtained by replacing the elements that have the same effect as the elements recorded in the above-mentioned embodiments with each other.

[0385] The UE (User Equipment) of the embodiment of the present invention comprises a transceiver unit, a control unit and a storage unit, and the UE is characterized in that the UE is in a SNPN (Stand-alone Non-Public The control unit performs an operation in a SNPN access operation mode, wherein the storage unit stores a first counter, wherein the first counter is a trial counter specific to the SNPN for non-3GPP access, and in the case of directly connecting to the SNPN service via the non-3GPP access or in the process of attempting to connect, the transceiver receives a login rejection message or a service rejection message from the network via the non-3GPP access, which includes the first identification information and does not guarantee integrity, and the first identification information is a rejection reason value indicating that the N1 mode is not allowed and / or the 5GCN connection via the non-3GPP access is not allowed and / or the SNPN is temporarily not allowed and / or the SNPN is permanently not allowed and / or is an illegal UE and / or an illegal ME and / or 5GS service is not allowed, and the control unit starts a first timer based on the reception of the login rejection message or the service rejection message, and the first timer is a timer that is started when the transceiver receives the login rejection message or the service rejection message and the integrity of each message is not guaranteed, and when the first timer is being executed, the control unit adds 1 to the value of the first counter based on the reception of the login rejection message including the first identification information.

[0386] A UE (User Equipment) according to an embodiment of the present invention includes a transceiver, a control unit, and a storage unit. The UE is characterized in that the storage unit stores a first counter, which is a trial counter specific to a SNPN (Stand-alone Non-Public Network) for non-3GPP access. In a process of directly connecting to an SNPN service via a non-3GPP access or in a process of attempting to connect, the transceiver receives a login rejection message, a service rejection message, or an authentication rejection message including first identification information from a network via the non-3GPP access. The first identification information is a rejection reason value indicating that the UE is illegal and / or an illegal ME and / or that 5GS services are not allowed. The reception of the login rejection message is performed during an initial login process for loading a service. When the login rejection message, the service rejection message, or the authentication rejection message with integrity guaranteed and including the first identification information is received, the control unit sets a maximum value specific to the UE installation for the first counter.

[0387] A UE (User Equipment) according to an embodiment of the present invention includes a transceiver, a control unit, and a storage unit. The UE is characterized in that the storage unit stores a first counter and / or a first list and / or a second list, wherein the first counter is a trial counter specific to a SNPN (Stand-alone Non-Public Network) for non-3GPP access, the first list is a list of "permanently prohibited SNPNs" for non-3GPP access, and the second list is a list of "temporarily prohibited SNPNs" for non-3GPP access. In the case of directly connecting to an SNPN service via a non-3GPP access or in the process of attempting to connect, the transceiver receives a login rejection message or a service rejection message that does not guarantee integrity, including first identification information, from a network via the non-3GPP access, wherein the first identification information indicates that the UE is an illegal UE and / or an illegal ME and / or that 5GS service is not allowed and / or N1 mode is not allowed and / or that the non-3GPP access is not allowed. The control unit starts a first timer based on the reception of the login rejection message or the service rejection message, and the first timer is a timer that is started when the transceiver unit receives the login rejection message or the service rejection message and the integrity of each message is not guaranteed. When the first timer expires and the first counter is more than one and less than the maximum value specific to UE installation, the control unit deletes the corresponding SNPNID from the first list or the second list stored in the storage unit. (Cross-reference of related applications) This application claims the benefit of priority to Japanese patent application No. 2022-118516 filed on July 26, 2022, the entire contents of which are incorporated herein by reference. Description of Reference Numerals 1: Mobile communication system 10: UE_A 120: Access network_B 122: gNB 130: UPF 132: SMF 140:AMF 141: New AMF 142: Old AMF 150: UDM 200: Core Network_B 240:N3IWF 250:DN

Claims

1. A user equipment UE, the user equipment UE comprising a transceiver unit, a control unit and a storage unit, wherein the UE is characterized in that: When the UE operates in an independent non-public network SNPN access operation mode, The storage unit stores a first counter. The first counter is a trial counter specific to the SNPN for non-3GPP access, The first counter is also used in case of direct connection to the SNPN via the non-3GPP access, The control unit increments the first counter when the transceiver receives the first control information via the non-3GPP access. The first control information is a rejection reason value indicating that the N1 mode is not allowed or the 5GCN connection via the non-3GPP access is not allowed or the SNPN is not allowed temporarily or permanently. The first control information also includes a login rejection message without ensuring integrity or a service rejection message without ensuring integrity.

2. The UE according to claim 1, characterized in that The first counter is also used if the UE is connected to the SNPN service via a Public Land Mobile Network (PLMN).

3. The UE according to claim 1, characterized in that When the transceiver receives the login rejection message with guaranteed integrity or the service rejection message with guaranteed integrity including the first control information, The control unit sets a maximum value specific to UE installation for the first counter.

Images