UE(user equipment)

Abstract

At present, the behavior of each device related to the equivalentSNPN is considered. Meanwhile, it is not clear how the UE handles the equivalentSNPN in the registration procedure for the on-boarding service.SOLUTION: A UserEquipment (UE) receives a registration accept message including first identification information from a network in a registration procedure for an onboarding service in an SNPN. The first identification information is a list of equivalentSNPN. Then, the UE deletes the list of equivalentSNPN stored in the UE.SELECTED DRAWING: Figure 6

Description

[Technical Field]

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

[0002] The 3GPP (3rd Generation Partnership Project) is studying the system architecture of 5GS (5G System), a fifth-generation (5G) mobile communication system, and is discussing how to support new procedures and new functions (see Non-Patent Documents 1 to 4). In recent years, there has been active discussion about functions for realizing localized services in NPN (Non-Public Network) (see Non-Patent Document 5). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 23.501 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18) [Non-patent document 2] 3GPP TS 23.502 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 18) [Non-patent document 3] 3GPP TS 24.501 V18.0.1 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 18) [Non-patent document 4] 3GPP TS 23.122 V18.0.0 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode (Release 18) [Non-patent document 5] 3GPP TR 23.700-08 V1.4.0 (2022-11); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhanced support of Non-Public Networks; Phase 2 (Release 18) Summary of the Invention [Problem to be solved by the invention]

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

[0005] Currently, the behavior of each device related to the equivalent SNPN is being studied. However, it is not clear how the UE handles the equivalent SNPN during procedures such as network selection and registration. For example, it is not clear how the UE handles the equivalent SNPN when the registration procedure is for onboarding. Furthermore, it is not clear how the UE handles the equivalent SNPN when the UE is rejected by the network during the registration procedure.

[0006] One aspect of the present invention has been made in view of the above circumstances, and its purpose is to clarify the behavior of a UE with respect to an equivalent SNPN in each procedure such as network selection and registration. [Means for solving the problem]

[0007] One embodiment of User Equipment (UE) of the present invention comprises a transceiver unit, a control unit, and a memory unit, and is characterized in that during a registration procedure for onboarding services in an SNPN, the transceiver unit receives a registration acceptance message from a network, the registration acceptance message including first identification information, the first identification information being a list of equivalent SNPNs, and the control unit deletes the list of equivalent SNPNs stored in the memory unit. [Effects of the Invention]

[0008] According to one aspect of the present invention, it is possible to clarify the behavior of a UE with respect to an equivalent SNPN in each procedure such as network selection and registration procedure. [Brief explanation of the drawings]

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

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

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

[0012] FIG. 1 shows that the mobile communication system 1 is composed of UE_A10, access network _A80, core network _A90, PDN (Packet Data Network) _A5, access network _B120, core network _B190, and DN (Data Network) _A6.

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

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

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

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

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

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

[0019] Furthermore, access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are deployed in the NG-RAN. Note that, hereinafter, the symbol for gNB 122 may be abbreviated, such as gNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to UEs and connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). In other words, the gNB is a base station device newly designed for 5GS, and has different functions from the base station device (eNB) used in the 4G system EPS. Furthermore, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

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

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

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

[0023] The core network_A corresponds to an EPC (Evolved Packet Core), which includes, for example, an MME (Mobility Management Entity), an SGW (Serving Gateway), a PGW (Packet Data Network Gateway)-U, a PGW-C, a PCRF (Policy and Charging Rules Function), and an HSS (Home Subscriber Server).

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

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

[0026] The core network (core network _A and / or core network _B) may be an IP mobile communication network operated by a mobile network operator (MNO) that connects the access network (access network _A and / or access network _B) to the PDN and / or DN, or it may be a core network for a mobile network operator that operates and manages the mobile communication system 1, or it may be a core network for a virtual mobile communication operator or virtual mobile communication service provider such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler).

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

[0028] In addition, hereinafter, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device sends or receives a message and / or performs a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein send or receive a message and / or perform a procedure.

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

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

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

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

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

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

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

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

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

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

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

[0040] [2.1. UE Device Configuration] First, an example of the device configuration of UE (User Equipment) will be explained using Figure 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

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

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

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

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

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

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

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

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

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

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

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

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

[0053] The network connection unit _B720 is a functional unit for the AMF to connect to a base station device (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF in a 5G AN. In other words, the AMF can use the network connection unit _B720 to send and receive user data and / or control information between a base station device (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF in a 5G AN.

[0054] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with a gNB via the N2 interface by using the network connection unit _A620, can communicate with a UDM via the N8 interface, can communicate with an SMF via the N11 interface, and can communicate with a PCF via the N15 interface. The AMF can also send and receive NAS messages with a UE via the N1 interface by using the network connection unit _A620. However, since the N1 interface is logical, communication between the UE and the AMF is actually performed via a 5G AN. Furthermore, if the AMF supports the N26 interface, it can communicate with an MME via the N26 interface by using the network connection unit _A620.

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

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

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

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

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

[0060] In addition, connection management manages the CM state for each UE. The CM state may be synchronized between the UE and the AMF. The CM state includes a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection established with the AMF via the N1 interface. In the CM-IDLE state, the UE does not have an N2 interface connection or an N3 interface connection. On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. In the CM-CONNECTED state, the UE may have an N2 interface connection and / or an N3 interface connection.

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

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

[0063] In addition, one or more AMFs may be placed in the core network _B. In addition, the AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). In addition, the AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs.

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

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

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

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

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

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

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

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

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

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

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

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

[0076] The UPF has functions such as an anchor point for intra-RAT mobility or inter-RAT mobility, an external PDU session point for interconnecting to DNs (i.e., a gateway between DNs and core network_B that forwards user data), packet routing and forwarding, an UL CL (Uplink Classifier) ​​function that supports routing of multiple traffic flows to one DN, a branching point function that supports multi-homed PDU sessions, a QoS (Quality of Service) processing function for the user plane, an uplink traffic verification function, downlink packet buffering, and a function to trigger downlink data notifications.

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

[0078] The user plane refers to user data transmitted and received between a UE and a network. The user plane may be transmitted and received using a PDN connection or a PDU session. Furthermore, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface, and / or the S1-U interface, and / or the S5 interface, and / or the S8 interface, and / or the SGi interface. Furthermore, in the case of 5GS, the user plane may be transmitted and received via the interface between the UE and the NG RAN, and / or the N3 interface, and / or the N9 interface, and / or the N6 interface. Hereinafter, the user plane may be referred to as the U-Plane.

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

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

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

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

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

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

[0085] Next, a PCF (Policy Control Function) may be an NF that has the function of determining a policy for controlling the behavior of the network.

[0086] Next, an NRF (Network Repository Function) may be an NF having a service discovery function. The NRF may be an NF that has a function of providing information about the discovered NF when it receives a discovery request for another NF from another NF.

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

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

[0089] Next, the SM procedure (also referred to as a procedure for SM) may include a PDU session establishment procedure, a PDU session modification procedure, and a UE-requested PDU session release procedure, each of which may be initiated by the UE or the network.

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

[0091] Next, MM procedures (also referred to as procedures for MM) may include a Registration procedure, a De-registration procedure, a Generic UE configuration update procedure, an Authentication and Authorization procedure, a Service request procedure, a Paging procedure, and a Notification procedure, each of which may be initiated by the UE or the network.

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

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

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

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

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

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

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

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

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

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

[0102] Next, the registered PLMN refers to the PLMN to which the UE is registered.

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

[0104] Next, PLMN selection may be a procedure for a UE to select a PLMN, where the PLMN selection may be performed when the UE connects to the PLMN, where the PLMN selection may be referred to as a PLMN selection process or a PLMN selection procedure.

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

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

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

[0108] Next, the UE ID is information for identifying a UE. For example, the UE ID may be SUCI, SUPI, IMSI, GUTI, 5G-GUTI, IMEI, IMEISV, TMSI, or 5G-S-TMSI. Alternatively, the UE ID may be other information set in an application or a network. Furthermore, the UE ID may be information for identifying a user.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0122] Next, the NID is information that identifies a network. An SNPN may be identified by information that combines a PLMN ID and an NID. The NID may be information that is unique within the SNPN, or may be information that is unique worldwide.

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

[0124] Next, CAG (Closed Access Groups) is a group used to realize PNI-NPN. Also, CAG may be a group identified by a CAG ID. Also, CAG may be used to prevent UEs that are not authorized for NPN from attempting to access a network slice allocated for NPN.

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

[0126] Next, a CAG cell is a cell where only members of the CAG can normally obtain service.

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

[0128] Next, the SNPN access mode may be a mode in which a UE selects an SNPN. Also, the SNPN access mode may be a mode in which a UE is registered in an SNPN. Furthermore, the SNPN access mode may be a mode in which a UE is connected to an SNPN. In other words, a UE operating in the SNPN access mode may select only an SNPN when selecting a network. More specifically, a UE operating in the SNPN access mode may select only an SNPN via the Uu interface when selecting a network. In other words, a UE operating in the SNPN access mode may select an SNPN without selecting a PLMN when selecting a network. Here, a UE operating in the SNPN access mode may be expressed as a UE in SNPN access mode. Furthermore, a UE in the SNPN access mode may be an SNPN-enabled UE.

[0129] Next, the SNPN access operation mode is a mode in which a UE connects to an SNPN via the SNPN access mode or non-3GPP access. Here, "non-3GPP access" in the SNPN may refer to a case in which a UE connects to an SNPN via a PLMN. Furthermore, when a UE operates in the SNPN access mode, it may operate in the SNPN access operation mode. Furthermore, when a UE does not operate in the SNPN access mode, it does not have to operate in the SNPN access operation mode. Furthermore, a UE in the SNPN access mode may be a UE in the SNPN access operation mode. Note that the SNPN access operation mode may be read as the SNPN access mode.

[0130] Next, SNPN selection may be a procedure by which a UE selects an SNPN. Alternatively, SNPN selection may be a procedure performed when a UE connects to an SNPN. Alternatively, SNPN selection may be referred to as an SNPN selection process or an SNPN selection procedure. Alternatively, SNPN selection may be a process by which a UE selects an SNPN. Alternatively, SNPN selection may be a process performed when a UE connects to an SNPN.

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

[0132] Next, an equivalent SNPN may be an SNPN that is treated as if it were the same SNPN as any SNPN. For example, an equivalent SNPN may be one or more SNPNs that are treated the same as the registered SNPN. Furthermore, an equivalent SNPN may be an SNPN that is treated as if it were the same SNPN as any SNPN. For example, an equivalent SNPN may be one or more SNPNs that are treated the same as the registered SNPN.

[0133] Furthermore, an equivalent SNPN may be one or more SNPNs identified by the same SNPN ID as any SNPN. Note that an equivalent SNPN may also be expressed as equivalent SNPN(s).

[0134] Alternatively, equivalent SNPNs may be managed in a list. An equivalent SNPN list may refer to a list containing equivalent SNPN(s). An equivalent SNPN list may also be expressed as a list of equivalent SNPNs.

[0135] The equivalent SNPN provided by a network may be the equivalent SNPN for that network, and the equivalent SNPN provided by an onboarding network may be the equivalent SNPN for that onboarding network.

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

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

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

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

[0140] Next, the CAG information list may be a list including one or more CAG IDs. Also, the CAG information list may be an extended CAG information list.

[0141] The CAG information list may also consist of zero or more entries. Each entry may include one PLMN ID. Each entry may also include an Allowed CAG list. The Allowed CAG list may include zero or more CAG-IDs. Each entry may also optionally include an indication that the UE is only allowed to connect to 5GS via a CAG cell.

[0142] A UE attached via E-UTRAN may then perform Location Registration (LR) via a Tracking Area Update procedure, and a UE registered via NG-RAN may perform Location Registration (LR) via a Registration procedure.

[0143] The onboarding service in the SNPN may then allow the UE to connect to the SNPN, indicating that onboarding is authorized, using the default UE credentials for primary authentication such that the UE is configured with one or more entries in a "list of subscriber data." Note that the onboarding service in the SNPN may be referred to as an onboarding service or as onboarding.

[0144] Furthermore, when a UE is registered for onboarding services in an SNPN, services other than the onboarding services in the SNPN may not be available, and when a UE is not registered for onboarding services in an SNPN, the onboarding services in the SNPN may not be available.

[0145] Here, when the UE performs registration for the onboarding service in the SNPN, the UE may indicate SNPN onboarding registration in the 5GS registration type information element. Note that the registration procedure for the onboarding service may also be referred to as the onboarding procedure.

[0146] Next, an onboarding network (ON) may refer to a network where onboarding is permitted. The onboarding network may also be a network that provides initial registration and / or access to a UE for onboarding. The onboarding network may also be expressed as ONN.

[0147] Here, the onboarding network may be a PLMN and may be expressed as ON-PLMN, and further, the onboarding network may be an SNPN and may be expressed as ON-SNPN.

[0148] The onboarding network may also be a PLMN or an onboarding SNPN that enables remote provisioning for registered UEs.

[0149] Next, a provisioning server is an entity that provides credentials to a UE to enable an SNPN connection.

[0150] Here, the provisioning server may exist in the onboarding network, or may exist in an external DN different from the onboarding network.

[0151] Next, a Subscription Owner SNPN (SO-SNPN) may be an SNPN that has a subscription for a UE. The SO-SNPN may also be an SNPN that provides subscription data to a UE via a provisioning server during an onboarding procedure. The ON-SNPN and the SO-SNPN may be the same SNPN.

[0152] Next, the first SNPN may be an SNPN indicating that the onboarding service is permitted. Also, the first SNPN may be an SNPN that matches the onboarding service information. Also, if the onboarding service information is preset, the first SNPN may be an SNPN that matches the onboarding service information. In other words, the first SNPN may be an SNPN that indicates that the onboarding service is permitted and that matches the onboarding service information.

[0153] Next, the second SNPN may be an SNPN that does not indicate that the onboarding service is permitted. Also, the second SNPN may be an SNPN that does not match the onboarding service information. Also, the second SNPN may be an SNPN that does not match the onboarding service information when the onboarding service information is preset. In other words, the second SNPN may be an SNPN that does not indicate that the onboarding service is permitted and does not match the onboarding service information. In yet other words, the second SNPN may be an SNPN that does not indicate that the onboarding service is permitted and does not match the onboarding service information when the onboarding service information is preset.

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

[0155] First, the first identification information is a 5GS registration type information element (IE). The first identification information may be an information element for indicating a type of requested registration. The first identification information may also indicate information indicating initial registration, mobility registration updating, periodic registration updating, emergency registration, SNPN onboarding registration, disaster roaming mobility registration updating, or disaster roaming initial registration.

[0156] Next, the second identification information may be UE capability information. Also, the second identification information may be information indicating that an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN is supported. Also, the second identification information may be information indicating that an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN is not supported. The second identification information may be information indicating whether an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN is supported.

[0157] The second identification information may also be an Equivalent SNPN indicator (ESI). Here, information indicating whether an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN is supported may be set in the ESI. Also, information indicating that an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN is supported may be set in the ESI. Also, information indicating that an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN is not supported may be set in the ESI.

[0158] Furthermore, the second identification information may be information in a 5GMM capability information element (IE), where the 5GMM capability IE may be a 5GMM capability.

[0159] Next, the tenth identification information may be an equivalent SNPN. Alternatively, the tenth identification information may be a list of equivalent SNPNs. Alternatively, the tenth identification information may be a list including one or more equivalent SNPNs, where each entry in the list may include an SNPN ID.

[0160] The tenth identification information may also be a list that does not include an equivalent SNPN, in other words, the tenth identification information may be an empty list.

[0161] Next, the eleventh identification information may be a reason value indicating a reason for rejecting the UE request. Also, the eleventh identification information may be a 5GMM cause. Also, the eleventh identification information may be a 5GMM cause value.

[0162] In addition, the 11th identification information may be a reason value indicating #3 (Illegal UE), or #6 (Illegal ME), or #7 (5GS services not allowed), or #13 (Roaming not allowed in this tracking area), or #22 (Congestion), or #62 (No network slices available), or #74 (Temporarily not authorized for this SNPN), or #75 (Permanently not authorized for this SNPN).

[0163] Here, #3 (Illegal UE) and #6 (Illegal ME) may be cause values ​​indicating that the UE is illegal. Also, #7 (5GS services not allowed) may be a cause value indicating that 5GS services are not allowed. Also, #13 (Roaming not allowed in this tracking area) may be a cause value indicating that roaming in the tracking area is not allowed. Also, #22 (Congestion) may be a cause value indicating congestion. Also, #62 (No network slices available) may be a cause value indicating that network slices are not available. Also, #74 (Temporarily not authorized for this SNPN) may be a cause value indicating that the SNPN is temporarily not authorized. Also, #75 (Permanently not authorized for this SNPN) may be a cause value indicating that the SNPN is permanently not authorized.

[0164] The eleventh identification information may also be a reason value other than those described above. For example, the eleventh identification information may be a reason value indicating #9 (UE identity cannot be derived by the network), or #10 (implicitly de-registered), or #11 (PLMN not allowed), or #12 (Tracking area not allowed), or #15 (No suitable cells in tracking area), or #27 (N1 mode not allowed), or #31 (Redirection to EPC required), or #72 (Non-3GPP access to 5GCN not allowed), or #73 (Serving network not authorized), or #76 (Not authorized for this CAG or authorized for CAG cells only), or #77 (Wireline access area not allowed), or #78 (PLMN not allowed to operate at the present UE location), or #79 (UAS services not allowed), or #80 (Disaster roaming for the determined PLMN with disaster condition not allowed).

[0165] Next, the twelfth identification information may be a reason value indicating the reason for rejecting the UE request, or may be a 5GMM cause value indicating that the equivalent SNPN is not allowed, or may be a 5GMM cause.

[0166] [3. Description of procedures used in each embodiment] Next, the procedures used in each embodiment will be described.

[0167] In each embodiment, as shown in FIG. 2, the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are each configured as the same device (i.e., the same physical hardware, the same logical hardware, or the same software). However, the contents described in this embodiment are also applicable to cases where these are configured as different devices (i.e., different physical hardware, different logical hardware, or different software). For example, data may be transmitted and received directly between these devices, or data may be transmitted and received via the N26 interface between the AMF and MME, or data may be transmitted and received via the UE.

[0168] [3.1. Obtaining system information] First, a process related to acquiring system information will be described. Acquiring system information may involve a UE acquiring and storing information broadcast by an NG-RAN node that provides access to one or more SNPNs.

[0169] Here, the information broadcast by the NG-RAN may include one or more PLMN IDs and / or a list of one or more NIDs per PLMN ID that identifies NPNs to which the NG-RAN provides access. Furthermore, the presence of an NID list for a PLMN ID may indicate that the associated PLMN ID and NID identify an SNPN. In other words, the UE may be able to identify an SNPN based on the NID list per PLMN ID broadcast by the NG-RAN node. Thus, the NG-RAN node may broadcast information identifying the SNPN, and the UE may receive and store the information identifying the SNPN.

[0170] The information broadcast by the NG-RAN node may also include human-readable network names for each SNPN, which are used only for manual SNPN selection, and / or information to prevent UEs that do not support the SNPN from accessing the cell, and / or an indication for each SNPN of whether UE access using credentials from a Credentials Holder (CH) is supported, and / or a list of Group IDs (GINs) for network selection supported for each SNPN, and / or an indication for each SNPN of whether to allow registration attempts from UEs that are not explicitly configured to select the SNPN.

[0171] Furthermore, if the SNPN supports onboarding of UEs to the SNPN, the NG-RAN node may additionally broadcast, for each cell, an indication indicating whether onboarding is currently enabled in the SNPN (onboarding enabled indication). In other words, for example, the NG-RAN node may broadcast information identifying the ON-SNPN in a cell where the SNPN can be used as an ON-SNPN.

[0172] The UE may acquire the system information based on a system information acquisition procedure, and the UE acquiring the system information may or may not be operating in the SNPN access mode.

[0173] In addition, the UE may use or take into consideration the SNPN information included in the received system information to perform SNPN selection or SNPN selection for onboarding services in network selection, which will be described later.

[0174] [3.2. Network Selection] Next, a process related to network selection will be described. Network selection is a process by which an unregistered UE selects a PLMN, NPN, or SNPN to register with before performing a registration procedure. For example, the UE may perform network selection to select a different network when powering on, when removing or inserting a SIM, or when the registration procedure fails.

[0175] PLMN selection and SNPN selection will now be described.

[0176] 3.2.1. PLMN Selection First, PLMN selection will be described.

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

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

[0179] Also, there may be two modes for PLMN selection: automatic PLMN selection mode and manual PLMN selection mode.

[0180] Alternatively, the PLMN selection may be a CAG selection, or if the UE supports CAG, the PLMN selection may be a CAG selection.

[0181] The PLMN selection steps are described below.

[0182] The UE may select and attempt to register with another PLMN if it is available and permissible for (i), (ii), (iii), (iv), and (v) in the following order:

[0183] (i) The UE may select the HPLMN or the highest priority EHPLMN that is available.

[0184] (ii) The UE may select each PLMN in the "User Controlled PLMN Selector with Access Technology" data file in the SIM.

[0185] (iii) The UE may select each PLMN in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM or each PLMN stored in the UE.

[0186] (iv) The UE may select, in random order, other PLMNs with received high quality signals.

[0187] (v) The UE may select other PLMNs in order of decreasing signal quality.

[0188] (vi) The UE may select a PLMN that broadcasts the PLMN ID of a PLMN determined by the UE to be in a disaster state or that is a PLMN that is a prohibited PLMN that broadcasts a disaster-related indication and that meets the following conditions:

[0189] (vi-a) (vi-a) may be the behavior when the indication of applicability of the list of PLMNs to be used in disaster situations provided by the VPLMN is set to true. The UE may select each PLMN in the list of PLMNs to be used in disaster situations stored in the UE associated with the PLMN ID of the UE-determined PLMN in the disaster situation, if any, in the order based on this list. Otherwise, if the UE does not have a stored list of PLMNs to be used in disaster situations associated with the PLMN ID of the UE-determined PLMN in the disaster situation, the UE may select each PLMN in the list of PLMNs to be used in disaster situations stored in the UE associated with the PLMN ID of the HPLMN, if any, in the order based on this list.

[0190] (vi-b) If the indication of applicability of the list of PLMNs to be used in disaster situations provided by the VPLMN is set to false, the UE may select each PLMN in the list of PLMNs to be used in disaster situations stored in the UE associated with the HPLMN, if any, in order based on this list.

[0191] (vii) The UE may broadcast the PLMN ID of the UE-determined PLMN in a disaster state or may select a PLMN relative to other forbidden PLMNs that broadcast a disaster-related indication, in random order.

[0192] When carrying out the above procedures, the following requirements may apply:

[0193] In (a)(i) to (vii), the behavior when the UE supports CAG is as follows:

[0194] (a-1) If the UE is provided with a non-empty CAG information list, the UE may consider the PLMN indicated by the NG-RAN cell only if:

[0195] (a-1-A) When the cell is a CAG cell, and the cell broadcasts a CAG-ID for a PLMN for which there is an entry in the CAG information list with the PLMN ID of the PLMN, and the CAG ID is included in the Allowed CAG list.

[0196] (a-1-B) Or, if the cell is not a CAG cell and there is no entry with the PLMN ID of the PLMN in the CAG information list, or if the cell is not a CAG cell and there is an entry with the PLMN ID of the PLMN in the CAG information list, but the entry does not include an indication that the UE is only allowed to access 5GS via the CAG cell.

[0197] (a-2) If the UE is provided with an empty CAG information list or is not provided with a CAG information list, the UE may consider the PLMN indicated by the NG-RAN cell only if the cell is not a CAG cell.

[0198] If there are one or more PLMNs available and allowable, but registration to those PLMNs fails due to location registration failure, or if an entry in the CAG information list blocks the registration attempt, the UE will again select such a PLMN and transition to a restricted service state.

[0199] After completing the above PLMN selection process, the UE may perform a registration procedure with the selected network.

[0200] Furthermore, when the UE performs initial registration to a PLMN, the UE may indicate in the PLMN selection that the selected PLMN is a PLMN ID selected by the NG-RAN node, and the NG-RAN may notify the AMF of the PLMN ID that identifies the selected PLMN indicated by the UE.

[0201] 3.2.2. SNPN Selection Next, SNPN selection will be described.

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

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

[0204] The SNPN selection may also be referred to as an SNPN selection mode procedure, which may be an automatic SNPN selection mode procedure or a manual SNPN selection mode procedure.

[0205] The SNPN selection mode procedure may be a procedure performed in an automatic SNPN selection mode or a procedure performed in a manual SNPN selection mode. In other words, the automatic SNPN selection mode procedure may be a procedure performed in an automatic SNPN selection mode, and the manual SNPN selection procedure may be a procedure performed in a manual SNPN selection mode.

[0206] Also, there may be two modes for SNPN selection: an automatic SNPN selection mode and a manual SNPN selection mode.

[0207] The SNPN selection may also be an SNPN selection for onboarding services at the SNPN.

[0208] The ON-SNPN selection may be an SNPN selection for an onboarding service and may be performed when the UE onboards. Note that the ON-SNPN selection may be one form of SNPN selection.

[0209] Also, a UE that performs SNPN selection or ON-SNPN selection may be operating in an SNPN access mode.

[0210] The SNPN selection or ON-SNPN selection may include an automatic SNPN selection mode and a manual SNPN selection mode. Note that the automatic SNPN selection may be one form of automatic network selection, and the manual SNPN selection may be one form of manual network selection.

[0211] Here, in the automatic SNPN selection mode, the UE may select an SNPN based on the NSPN to which it last registered, a subscribed SNPN, or a "list of preferred SNPNs" which is a list of SNPNs managed by the UE or CH.

[0212] Also here, in manual SNPN selection mode, the UE may provide the user with a list of SNPNs and associated human-readable network names of the available SNPNs.

[0213] Furthermore, the UE may perform SNPN selection by using or considering information received from an NG-RAN node and / or information identifying the SNPN stored in the UE when acquiring the system information. Here, a UE supporting UE onboarding may be configured with pre-configured ON-SNPN selection information. Furthermore, a UE performing ON-SNPN selection may compare the pre-configured ON-SNPN selection information with the system information acquired from the NG-RAN node. More specifically, in the ON-SNPN selection, the UE may compare information identifying the SNPN (e.g., an SNPN network identifier and / or GIN) included in the pre-configured ON-SNPN selection information with the onboarding enabled indication included in the acquired system information.

[0214] The steps for selecting an SNPN are described below.

[0215] If there is at least one entry in the list of subscriber data, the UE may select one entry, if any, in the list of subscriber data to use for automatic SNPN selection. Also, if there is at least one entry in the list of subscriber data, the UE may select a PLMN subscription, if any, to use for automatic SNPN selection.

[0216] Alternatively, if there are zero or more entries in the list of subscriber data, the UE has a USIM with a PLMN subscription, and the UE is provided with SNPN selection parameters associated with the PLMN subscription, the UE may select one entry, if any, in the list of subscriber data to use for automatic SNPN selection.Also, if there are zero or more entries in the list of subscriber data, the UE has a USIM with a PLMN subscription, and the UE is provided with SNPN selection parameters associated with the PLMN subscription, the UE may select one PLMN subscription, if any, to use for automatic SNPN selection.

[0217] The UE may select one SNPN, if available and permitted, in the following order: (a) to (c).

[0218] (a) The UE may select the SNPN with which the UE last registered or an equivalent SNPN. Note that, in the case of SNPN selection after the registration procedure for the onboarding service is completed, the UE may not select an equivalent SNPN.

[0219] (b) The UE may select an SNPN identified by the SNPN identifier of the subscribed SNPN in the selected entry of the list of subscriber data in the UE, if any.

[0220] (c) If the UE supports connection to an SNPN using credentials from the credential holder, or an SNPN using the SNPN selection parameters of the selected entry in the list of subscriber data, or an SNPN associated with the selected PLMN, it may select the following SNPN:

[0221] (c-1) The UE may broadcast an indication that it supports connections using credentials from the credential holder and may select an SNPN identified by an SNPN identifier included in a user-controlled preferred list of preferred SNPNs.

[0222] (c-2) The UE may broadcast an indication that it supports connections using credentials from the credential holder and may select an SNPN identified by an SNPN identifier included in the credential holder-controlled preferred list of preferred SNPNs.

[0223] (c-3) The UE may broadcast an indication that it supports connections using credentials from the credential holder and may select an SNPN that broadcasts a GIN that is included in the credential holder-controlled priority list of the GIN.

[0224] (c-4) The UE may select an SNPN identified by an SNPN identifier that is not included in the SNPN selection parameters of an entry in the list of subscriber data or in the SNPN selection parameters associated with the PLMN subscription, that does not broadcast a GIN included in the credential holder controlled preference list of GINs, and that broadcasts an indication that the SNPN will allow registration attempts from UEs that are not explicitly configured to select an SNPN.

[0225] The UE may limit its search to NG-RAN access technologies for the SNPN.

[0226] Once the UE has selected an SNPN, if a PLMN subscription is selected, the UE may attempt to register with the selected SNPN using the NG-RAN access technology and subscriber identifier and credentials from the selected entry in the list of subscriber data or from the USIM.

[0227] If the registration matches, the UE may indicate the selected SNPN.

[0228] If registration is not possible because there is no SNPN that is available, authorized, and identified by an SNPN identifier in the UE's subscriber data list entry, the UE may indicate "no service" to the user, wait until a new SNPN is available, authorized, and identified by an SNPN identifier in the UE's subscriber data list entry, and repeat the SNPN selection mode procedure and / or registration procedure.

[0229] If there were SNPNs available, allowed, and identified by SNPN identifiers in entries in the UE's subscriber data list, but registration to those SNPNs failed due to a location registration failure, the UE may again select one of those SNPNs and transition to a restricted service state.

[0230] Next, SNPN selection in the onboarding service will be described.

[0231] When the UE needs to connect to one SNPN for onboarding service in the SNPN, the UE may select one first SNPN.

[0232] Also, if one or more first SNPNs are available, the UE selects one of the first SNPNs based on a prioritized list of SNPNs for the onboarding service. In other words, if there are one or more available first SNPNs, the UE selects one of the first SNPNs based on a prioritized list of SNPNs for the onboarding service.

[0233] Also, for onboarding services in an SNPN, the UE may not select a second SNPN.

[0234] Once the UE has selected an SNPN for the onboarding service, the UE may attempt initial registration for the onboarding service at the selected SNPN. Also, once the UE has selected an SNPN for the onboarding service, the UE may attempt initial registration for the onboarding service at the SNPN on the selected SNPN using the NG-RAN access technology and default UE credentials for primary authentication.

[0235] If the registration fails and one or more other first SNPNs are available, the UE may select such other SNPN based on a prioritized list of SNPNs for the onboarding service and may attempt initial registration for the onboarding service at the selected SNPN. Also, if the registration fails and one or more other first SNPNs are available, the UE may select such other SNPN based on a prioritized list of SNPNs for the onboarding service and may attempt initial registration for the onboarding service at the selected SNPN using the NG-RAN access technology and default UE credentials for primary authentication.

[0236] In other words, if registration fails and there are one or more other available first SNPNs, the UE may select such other SNPN based on a prioritized list of SNPNs for the onboarding service and may attempt initial registration for the onboarding service at the selected SNPN. Also, if registration fails and there are one or more other available first SNPNs, the UE may select such other SNPN based on a prioritized list of SNPNs for the onboarding service and may attempt initial registration for the onboarding service at the selected SNPN using the NG-RAN access technology and default UE credentials for primary authentication.

[0237] Also, if registration fails and one or more other first SNPNs are available, the UE may perform SNPN selection not for onboarding services at the SNPN according to the SNPN selection mode of the UE.

[0238] In other words, if registration fails and there are one or more other available first SNPNs, the UE may perform SNPN selection for a non-onboarding service in the SNPN according to the SNPN selection mode of the UE.

[0239] If the registration fails and no other first SNPN is available, the UE may perform an SNPN selection for a non-onboarding service in the SNPN according to the SNPN selection mode of the UE.

[0240] In other words, if registration fails and there is no other available first SNPN, the UE may perform SNPN selection not for onboarding services in the SNPN according to the SNPN selection mode of the UE.

[0241] If registration is not possible because the first SNPN is unavailable, the UE may indicate to higher layers that there is no onboarding service, transition to a limited service state, wait until a new first SNPN becomes available, and repeat the SNPN selection mode procedure and / or registration procedure. Alternatively, if registration is not possible because the first SNPN is unavailable, the UE may perform an SNPN selection for a non-onboarding service among the SNPNs according to the UE's SNPN selection mode.

[0242] In other words, if registration is not possible because there is no available first SNPN, the UE may indicate to higher layers that there is no onboarding service, transition to a limited service state, wait until a new first SNPN becomes available, and repeat the SNPN selection mode procedure and / or registration procedure. Also, if registration is not possible because there is no available first SNPN, the UE may perform an SNPN selection for a non-onboarding service among the SNPNs according to the UE's SNPN selection mode.

[0243] Alternatively, if one or more first SNPNs exist but registration to all of the first SNPNs fails due to location registration failures, the UE may indicate to higher layers that there is no onboarding service, transition to a limited service state, wait until one new first SNPN becomes available, and repeat the SNPN selection mode procedure and / or registration procedure. Alternatively, if one or more first SNPNs exist but registration to all of the first SNPNs fails due to location registration failures, the UE may perform SNPN selection for a non-onboarding service among the SNPNs according to the UE's SNPN selection mode.

[0244] After completing the above SNPN selection process, the UE may perform a registration procedure with the selected network.

[0245] Furthermore, when the UE performs initial registration to an SNPN or an ON-SNPN, the UE may indicate in the SNPN selection that the selected SNPN or ON-SNPN is a PLMN ID and NID selected by the NG-RAN node. Furthermore, the NG-RAN may notify the AMF of the PLMN ID and NID that identify the selected SNPN indicated by the UE.

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

[0247] The registration procedure may also be a registration procedure for initial registration. The registration procedure may also be a registration procedure for mobility and periodic registration update. The registration procedure may also be a registration procedure for onboarding services. The registration procedure may also be a registration procedure for emergency services. The registration procedure may also be referred to as registration.

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

[0249] The network in this procedure may be an SNPN or a PLMN, or may be an onboarding network.

[0250] In addition, the UE may perform a registration procedure after performing SNPN selection or PLMN selection.

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

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

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

[0254] Next, each step of the registration procedure will be described. Note that the registration procedure described below may be a registration procedure for initial registration or a registration procedure for mobility and registration update. Note that the AMF may be the AMF of the SNPN if the registration procedure is performed in the SNPN, or may be the AMF of the PLMN if the registration procedure is performed in the PLMN.

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

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

[0257] Specifically, the UE may indicate a 5GS registration type information element to the AMF by sending first identification information. Here, the UE may indicate SNPN onboarding registration in the first identification information. In other words, the UE may indicate SNPN onboarding registration to the AMF in the 5GS registration type information element. Also, the UE may send the first identification information when indicating registration for onboarding service in the SNPN.

[0258] Furthermore, the UE may indicate to the AMF that it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN by transmitting the second identification information. Furthermore, the UE may indicate to the AMF that it does not support an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN by transmitting the second identification information. Furthermore, the UE may indicate to the AMF whether it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN by transmitting the second identification information.

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

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

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

[0262] The UE may also transmit identification information other than the first and second identification information in the registration request message.

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

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

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

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

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

[0268] Specifically, if the AMF receives the first identification information, it may recognize that the UE indicates registration for onboarding services in the SNPN.

[0269] Furthermore, when the AMF receives the second identification information, it may include the tenth identification information in the second control message. In other words, when the UE indicates in the second identification information that it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN, the AMF may include the tenth identification information in the second control message. Furthermore, when the UE indicates in the second identification information that it does not support an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN, the AMF may not include the tenth identification information in the second control message.

[0270] Furthermore, the AMF may indicate to the UE the contents indicated by one or more of the tenth to twelfth identities by including them in a registration accept message and sending them. The AMF may also indicate to the UE the contents of these identities by sending a registration accept message.

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

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

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

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

[0275] Next, the UE receives a registration accept message from the AMF via the 5G AN (gNB) (S806). The UE may also receive the registration accept message from the AMF, including one or more of the tenth to twelfth identification information.

[0276] Here, by receiving the registration acceptance message, the UE can recognize that the UE's request via the registration request message has been accepted, and the contents of the various identification information included in the registration acceptance message.

[0277] Specifically, when the UE receives the tenth identification information, the UE may store the tenth identification information.

[0278] Furthermore, when the UE receives the tenth identification information, the UE may delete the SNPN IDs in the temporarily prohibited SNPN list or the permanently prohibited SNPN list from the received tenth identification information. In other words, when the UE receives the tenth identification information, and further, if the registration is not for emergency services and is not for onboarding services at an SNPN, the UE may delete the SNPN IDs in the temporarily prohibited SNPN list or the permanently prohibited SNPN list from the received tenth identification information.

[0279] Furthermore, when the UE receives the tenth identification information, the UE may add the SNPN ID of the registered SNPN that transmitted the tenth identification information to the equivalent SNPN list stored in the UE.

[0280] In addition, when the UE receives the tenth identification information, the UE may update the equivalent SNPN list stored in the UE.

[0281] Furthermore, when the UE receives the tenth identification information, and if the tenth identification information does not include an equivalent SNPN list, the UE may delete the equivalent SNPN list stored in the UE.

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

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

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

[0285] Alternatively, the UE may perform SNPN selection or PLMN selection based on receiving the registration accept message, and at this time, the UE may perform SNPN selection or PLMN selection without deleting the equivalent SNPN.

[0286] Alternatively, the UE may perform SNPN selection or PLMN selection based on the transmission of the registration complete message, and at this time, the UE may perform SNPN selection or PLMN selection without deleting the equivalent SNPN.

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

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

[0289] Specifically, the network may transmit the eleventh identification information to the UE to indicate the reason for the registration rejection. Also, the network may transmit the eleventh identification information to the UE to indicate a reason value indicating #3 (Illegal UE), #6 (Illegal ME), #7 (5GS services not allowed), #13 (Roaming not allowed in this tracking area), #22 (Congestion), #62 (No network slices available), #74 (Temporarily not authorized for this SNPN), or #75 (Permanently not authorized for this SNPN).

[0290] Furthermore, the network may transmit eleventh identification information indicating #3 (Illegal UE) or #6 (Illegal ME) when rejecting UE registration because the UE is an illegal UE. Furthermore, the network may transmit eleventh identification information indicating #7 (5GS services not allowed) when rejecting UE registration because 5GS services are not allowed. Furthermore, the network may transmit eleventh identification information indicating #13 (Roaming not allowed in this tracking area) when rejecting UE registration because roaming in the tracking area is not allowed. Furthermore, the network may transmit eleventh identification information indicating #22 (Congestion) when rejecting UE registration because congestion occurs. Furthermore, the network may transmit eleventh identification information indicating #62 (No network slices available) when rejecting UE registration because network slices are not available. The network may also send eleventh identification information indicating #74 (Temporarily not authorized for this SNPN) if it rejects the UE registration because it temporarily does not approve the SNPN, and may also send eleventh identification information indicating #75 (Permanently not authorized for this SNPN) if it rejects the UE registration because it permanently does not approve the SNPN.

[0291] The network may also transmit the twelfth identification information to the UE, indicating a reason value indicating that the equivalent SNPN is not allowed.

[0292] The network may also send a twelfth identification if it rejects the UE's registration because the equivalent SNPN is not allowed.

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

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

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

[0296] Next, the UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S810). The UE may also receive from the AMF a registration rejection message including one or more of the identification information items 10 to 12. By receiving the registration rejection message, the UE can recognize that the UE's request via the registration request message has been rejected and the contents of the various identification information included in the registration rejection message.

[0297] Furthermore, if the UE receives a registration rejection message, the UE may perform SNPN selection or PLMN selection without deleting the equivalent SNPN list.

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

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

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

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

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

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

[0304] Furthermore, the UE may perform SNPN selection or PLMN selection based on the completion of the registration procedure.

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

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

[0307] In this embodiment, the network may be an onboarding network, where the onboarding network may be an SNPN, an equivalent SNPN, or a PLMN.

[0308] Also, in this embodiment, PLMN selection and / or SNPN selection and / or registration procedures may be performed.

[0309] In addition, in this embodiment, a registration procedure for an onboarding service may be performed. In addition, in this embodiment, a registration procedure for an onboarding service in an SNPN may be performed. Here, performing the registration procedure for an onboarding service in an SNPN may indicate SNPN onboarding registration in a 5GS registration type information element.

[0310] In this embodiment, a registration procedure for emergency services may also be implemented.

[0311] In this embodiment, the first control message may be a registration request message.

[0312] In addition, in this embodiment, the second control message may be a registration acceptance message or a registration rejection message.

[0313] Furthermore, the behavior of the UE and the network when receiving each control message may be the same as the behavior of the UE and the network in each of the above-mentioned procedures.

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

[0315] First, the UE transmits a first control message to the network, and the UE may transmit the first control message to the network including one or more pieces of identification information among the first and second pieces of identification information.

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

[0317] Specifically, the UE may indicate a 5GS registration type information element to the network by sending first identification information. Here, the UE may indicate SNPN onboarding registration in the first identification information. In other words, the UE may indicate SNPN onboarding registration to the network in the 5GS registration type information element. Also, the UE may send the first identification information when indicating registration for onboarding service in the SNPN.

[0318] The UE may also indicate to the network that it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN by transmitting the second identification information. The UE may also indicate to the network that it does not support an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN by transmitting the second identification information. The UE may also indicate to the network whether it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN by transmitting the second identification information.

[0319] Furthermore, the UE may select and decide whether to include one or more of the first and second identification information in the first control message based on the state of the UE and / or the received identification information, etc.

[0320] Next, the network receives a first control message from the UE. The network may also receive the first control message from the UE, the first control message including one or more of the first and second identification information.

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

[0322] Specifically, if the network receives the first identification information, it may recognize that the UE indicates registration for onboarding services in the SNPN.

[0323] Furthermore, if the network receives the second identification information, it may include the tenth identification information in the second control message. In other words, if the UE indicates in the second identification information that it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN, the network may include the tenth identification information in the second control message. Furthermore, if the UE indicates in the second identification information that it does not support an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN, the network may not include the tenth identification information in the second control message.

[0324] Also, if the first identity indicates that the UE registers for onboarding services in an SNPN, the network may not include the tenth identity in the second control message. In other words, if the first identity indicates that the UE registers for onboarding services in an SNPN, the network may not include the tenth identity in the second control message even if the UE indicates that it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN in the second identity.

[0325] In addition, if the UE indicates in the second identification information that it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN, the network may determine whether to include a tenth identification information in the second control message depending on whether the UE indicates registration for onboarding services at an SNPN in the first identification information.

[0326] In addition, if the UE indicates in the second identification information that it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN, and if the UE does not indicate registration for onboarding services at an SNPN in the first identification information, the network may include a tenth identification information in the second control message.

[0327] Furthermore, if the UE indicates in the second identification information that it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN, and if the UE indicates in the first identification information that it registers for an onboarding service in an SNPN, the network may not include the tenth identification information in the second control message.

[0328] Also, if the first identification information indicates that the UE is registered for onboarding services in an SNPN, the network may not include the tenth identification information in the second control message if the UE indicates in the second identification information that it does not support an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN.

[0329] Also, if the first identification information indicates that the UE does not indicate registration for onboarding services in the SNPN, the network may not include the tenth identification information in the second control message if the UE indicates in the second identification information that it does not support an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN.

[0330] The network behavior may be implemented after receiving the first control message, or after receiving one or more of the first and second identification information.

[0331] Furthermore, when the network receives the first control message, the network may perform a behavior upon receiving each piece of identification information included in the first control message.

[0332] The network may also forward each received identification information to other NFs.

[0333] Next, the network sends a second control message to the UE, where the network may include one or more of the tenth to twelfth identification information in the second control message.

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

[0335] Specifically, the network may indicate a list of equivalent SNPNs to the UE by transmitting a tenth identification. Alternatively, the network may indicate a list of available equivalent SNPNs to the UE by transmitting the tenth identification. Alternatively, the network may indicate to the UE that there are no available equivalent SNPNs by transmitting an empty tenth identification.

[0336] Here, the equivalent SNPN indicated by the tenth identification information may be an equivalent SNPN for the onboarding network. In other words, the equivalent SNPN indicated by the tenth identification information may be one or more SNPNs that are treated the same as the onboarding network.

[0337] Also, if the first identification information indicates that the UE is registered for onboarding services in an SNPN, the equivalent SNPN indicated by the tenth identification information may be an equivalent SNPN for the onboarding network.

[0338] Also, if the first identification information does not indicate that the UE is registered for onboarding services at an SNPN, the equivalent SNPN indicated by the tenth identification information may be an equivalent SNPN to the registered SNPN or an equivalent SNPN to the SO-SNPN.

[0339] In addition, the network may select and decide whether to include one or more of the tenth to twelfth identification information in the second control message based on the state of the UE and / or information received from other NFs, etc.

[0340] The network may also determine whether to send the second control message and / or each identification information based on the state of the UE and / or information received from other NFs, etc.

[0341] The UE then receives a second control message from the network. The UE may also receive a second control message from the network that includes one or more of the tenth to twelfth identities.

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

[0343] Specifically, when the UE receives the tenth identification information, the UE may store the tenth identification information.

[0344] Furthermore, when the UE receives the tenth identification information, the UE may delete the SNPN IDs in the temporarily prohibited SNPN list or the permanently prohibited SNPN list from the received tenth identification information. In other words, when the UE receives the tenth identification information, and further, if the registration is not for emergency services and is not for onboarding services at an SNPN, the UE may delete the SNPN IDs in the temporarily prohibited SNPN list or the permanently prohibited SNPN list from the received tenth identification information.

[0345] Furthermore, when the UE receives the tenth identification information, the UE may add the SNPN ID of the registered SNPN that transmitted the tenth identification information to the equivalent SNPN list stored in the UE.

[0346] In addition, when the UE receives the tenth identification information, the UE may update the equivalent SNPN list stored in the UE.

[0347] Furthermore, when the UE receives the tenth identification information, and if the tenth identification information does not include an equivalent SNPN list, the UE may delete the equivalent SNPN list stored in the UE.

[0348] Additionally, if the UE receives a tenth identification that is an empty list, the UE may recognize that there is no equivalent SNPN available.

[0349] In addition, the UE may delete the equivalent SNPN list stored in the UE when it receives the tenth identification information and / or when the first identification information indicates that the UE is registered for onboarding services at an SNPN.

[0350] In addition, the UE may delete the received tenth identification information if it receives the tenth identification information and / or if the first identification information indicates that the UE is registered for onboarding services in the SNPN.

[0351] In addition, if the UE receives the tenth identification information and / or if the first identification information indicates that the UE is registered for onboarding services in the SNPN, the UE may ignore the received tenth identification information.

[0352] In addition, when the UE receives the tenth identification information and / or when the first identification information indicates that the UE is registered for onboarding services at an SNPN, the UE may not need to update the equivalent SNPN list stored in the UE.

[0353] Furthermore, when the UE receives the tenth identification information and / or when the first identification information indicates that the UE is registering for onboarding services at an SNPN, the UE may not add the SNPN ID of the registered SNPN that sent the tenth identification information to the equivalent SNPN list stored in the UE.

[0354] Here, the equivalent SNPN indicated by the tenth identification information may be an equivalent SNPN for the onboarding network. In other words, the equivalent SNPN indicated by the tenth identification information may be one or more SNPNs that are treated the same as the onboarding network.

[0355] Also, if the first identification information indicates that the UE is registered for onboarding services in an SNPN, the equivalent SNPN indicated by the tenth identification information may be an equivalent SNPN for the onboarding network.

[0356] Also, if the first identification information does not indicate that the UE is registered for onboarding services at an SNPN, the equivalent SNPN indicated by the tenth identification information may be an equivalent SNPN to the registered SNPN or an equivalent SNPN to the SO-SNPN.

[0357] In addition, if the UE indicates in the second identification information that it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN, and if it does not receive the tenth identification information, it may delete the equivalent SNPN list stored in the UE.

[0358] The UE may perform the above behavior after receiving the second control message, or after receiving one or more of the tenth to twelfth identification information.

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

[0360] Furthermore, when the UE performs SNPN selection again after receiving the second control message, it may not select an equivalent SNPN. In other words, when the UE performs SNPN selection again after completing registration for the onboarding service, it may not select an equivalent SNPN.

[0361] Furthermore, if the UE deletes the equivalent SNPN list stored in the UE, the UE does not need to select an equivalent SNPN in the SNPN selection.

[0362] In addition, if the UE deletes or ignores the received tenth identification information, it does not need to select an equivalent SNPN in the SNPN selection.

[0363] Furthermore, if the first identification information indicates that the UE is registered for onboarding services at an SNPN, and if the UE has not deleted the equivalent SNPN list stored in the UE, then the equivalent SNPN need not be selected in the SNPN selection.

[0364] Furthermore, if the first identification information indicates that the UE is registered for onboarding services at an SNPN, and if the UE does not delete or ignore the received tenth identification information, the UE may not select an equivalent SNPN in the SNPN selection.

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

[0366] In this embodiment, the network may be an SNPN, an equivalent SNPN, or a PLMN.

[0367] Also, in this embodiment, PLMN selection and / or SNPN selection and / or registration procedures may be performed.

[0368] In this embodiment, the first control message may be a registration request message.

[0369] In addition, in this embodiment, the second control message may be a registration acceptance message or a registration rejection message.

[0370] Furthermore, the behavior of the UE and the network when receiving each control message may be the same as the behavior of the UE and the network in each of the above-mentioned procedures.

[0371] In this embodiment, the network may or may not be an onboarding network. Also, in this embodiment, a registration procedure for the onboarding service may or may not be performed.

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

[0373] First, the UE transmits a first control message to the network, and the UE may transmit the first control message to the network including one or more pieces of identification information among the first and second pieces of identification information.

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

[0375] Specifically, the UE may indicate a 5GS registration type information element to the network by sending first identification information. Here, the UE may indicate SNPN onboarding registration in the first identification information. In other words, the UE may indicate SNPN onboarding registration to the network in the 5GS registration type information element. Also, the UE may send the first identification information when indicating registration for onboarding service in the SNPN.

[0376] The UE may also indicate to the network that it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN by transmitting the second identification information. The UE may also indicate to the network that it does not support an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN by transmitting the second identification information. The UE may also indicate to the network whether it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN by transmitting the second identification information.

[0377] Furthermore, the UE may select and decide whether to include one or more of the first and second identification information in the first control message based on the state of the UE and / or the received identification information, etc.

[0378] Next, the network receives a first control message from the UE. The network may also receive the first control message from the UE, the first control message including one or more of the first and second identification information.

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

[0380] Specifically, if the network receives the first identification information, it may recognize that the UE indicates registration for onboarding services in the SNPN.

[0381] Furthermore, if the network receives the second identification information, it may include the tenth identification information in the second control message. In other words, if the UE indicates in the second identification information that it supports an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN, the network may include the tenth identification information in the second control message. Furthermore, if the UE indicates in the second identification information that it does not support an equivalent SNPN, an equivalent SNPN list, or a function using an equivalent SNPN, the network may not include the tenth identification information in the second control message.

[0382] The network behavior may be implemented after receiving the first control message, or after receiving one or more of the first and second identification information.

[0383] Furthermore, when the network receives the first control message, the network may perform a behavior upon receiving each piece of identification information included in the first control message.

[0384] The network may also forward each received identification information to other NFs.

[0385] Next, the network sends a second control message to the UE, where the network may include one or more of the tenth to twelfth identification information in the second control message.

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

[0387] Specifically, the network may transmit the eleventh identification information to the UE to indicate the reason for the registration rejection. Furthermore, the network may transmit the eleventh identification information to the UE to indicate a cause value indicating #3 (Illegal UE), #6 (Illegal ME), #7 (5GS services not allowed), #13 (Roaming not allowed in this tracking area), #22 (Congestion), #62 (No network slices available), #74 (Temporarily not authorized for this SNPN), or #75 (Permanently not authorized for this SNPN). Furthermore, the network may transmit the eleventh identification information to the UE to indicate a cause value other than the above.

[0388] Furthermore, the network may transmit eleventh identification information indicating #3 (Illegal UE) or #6 (Illegal ME) when rejecting UE registration because the UE is an illegal UE. Furthermore, the network may transmit eleventh identification information indicating #7 (5GS services not allowed) when rejecting UE registration because 5GS services are not allowed. Furthermore, the network may transmit eleventh identification information indicating #13 (Roaming not allowed in this tracking area) when rejecting UE registration because roaming in the tracking area is not allowed. Furthermore, the network may transmit eleventh identification information indicating #22 (Congestion) when rejecting UE registration because congestion occurs. Furthermore, the network may transmit eleventh identification information indicating #62 (No network slices available) when rejecting UE registration because network slices are not available. The network may also send eleventh identification information indicating #74 (Temporarily not authorized for this SNPN) if it rejects the UE registration because it temporarily does not approve the SNPN, and may also send eleventh identification information indicating #75 (Permanently not authorized for this SNPN) if it rejects the UE registration because it permanently does not approve the SNPN.

[0389] The network may also transmit the twelfth identification information to the UE, indicating a reason value indicating that the equivalent SNPN is not allowed.

[0390] The network may also send a twelfth identification if it rejects the UE's registration because the equivalent SNPN is not allowed.

[0391] In addition, when transmitting the eleventh or twelfth identification information, the network may transmit the tenth identification information, which is an empty list.

[0392] Additionally, the network may or may not transmit the tenth identification information.

[0393] In addition, the network may select and decide whether to include one or more of the tenth to twelfth identification information in the second control message based on the state of the UE and / or information received from other NFs, etc.

[0394] The network may also determine whether to send the second control message and / or each identification information based on the state of the UE and / or information received from other NFs, etc.

[0395] The UE then receives a second control message from the network. The UE may also receive a second control message from the network that includes one or more of the tenth to twelfth identities.

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

[0397] Specifically, when the UE receives the eleventh identification information, the UE may delete the equivalent SNPN list stored in the UE.

[0398] More specifically, if the UE receives 11th identification information indicating #3 (Illegal UE), or #6 (Illegal ME), or #7 (5GS services not allowed), or #13 (Roaming not allowed in this tracking area), or #22 (Congestion), or #62 (No network slices available), or #74 (Temporarily not authorized for this SNPN), or #75 (Permanently not authorized for this SNPN), the UE may delete the equivalent SNPN list stored in the UE.

[0399] In addition, when the UE receives eleventh identification information indicating a reason value other than those mentioned above, the UE may delete the equivalent SNPN list stored in the UE.

[0400] In addition, when the UE receives the 12th identification information, the UE may delete the equivalent SNPN list stored in the UE.

[0401] In addition, when the UE receives the 11th identification information, and if the first identification information indicates that the UE is registered for onboarding services at an SNPN, the UE may delete the equivalent SNPN list stored in the UE.

[0402] In addition, when the UE receives the tenth identification information, which is an empty list, the UE may delete the equivalent SNPN list stored in the UE.

[0403] In addition, the UE may perform SNPN selection or PLMN selection after deleting the equivalent SNPN list stored in the UE.

[0404] The UE may perform the above behavior after receiving the second control message, or after receiving one or more of the tenth to twelfth identification information.

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

[0406] 5. Variations A program running on an apparatus according to one aspect of the present invention may be a program that controls a central processing unit (CPU) or the like to cause a computer to function so as to realize the functions of an embodiment according to one aspect of the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a random access memory (RAM), a non-volatile memory such as a flash memory, a hard disk drive (HDD), or another storage device system.

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

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

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

[0410] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted with elements that achieve the same effect are also included. [Explanation of symbols]

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

Claims

[Claim 1] User Equipment (UE), The UE includes a transceiver, a controller, and a memory unit; During the registration process for onboarding services at SNPN, the transceiver receives a registration acceptance message from a network, the registration acceptance message including first identification information; the first identification information is a list of equivalent SNPNs; The control unit deletes the list of equivalent SNPNs stored in the storage unit. A UE characterized by:

Images