UE(User Equipment)

Abstract

To solve the problem in which: communication means of UE (User Equipment) and an ONN (Onboarding Network) is being studied in 5GS (5G System); but regarding the handling of a 5GS mobile identity IE during an initial registration procedure, it is not made clear how the UE behaves when the UE has not performed initial registration for an onboarding service.SOLUTION: In 5GS (5G System), when UE (User Equipment) does not hold an effective 5G-GUTI or a SUCI other than an onboarding SUCI and has not started initial registration for an onboarding service, information to be included in a 5GS mobile identity IE gets clarified.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] This disclosure relates to UE (User Equipment).

Background Art

[0002] In 3GPP (3rd Generation Partnership Project), discussions have been initiated on the system architecture of 5GS (5G System), which is the next-generation, i.e., 5th-generation (5G) mobile communication system, and discussions are being held on the support for new procedures and new functions (see Non-Patent Document 1, Non-Patent Document 2, Non-Patent Document 3, Non-Patent Document 4, Non-Patent Document 5, Non-Patent Document 6, and Non-Patent Document 5).

[0003] For example, optimization and diversification of communication procedures for supporting continuous mobile communication services according to various services, and optimization of the system architecture in accordance with the optimization and diversification of communication procedures are also cited as requirements.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

[0005] In 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered to provide a wide variety of services. Furthermore, 5GS is also considering the provision of a private network, such as an NPN (Non-Public Network), which is defined separately from the public network PLMN (Public Land Mobile Network), and which can be used by specific users for specific purposes, as well as the functions to realize such a private network. In addition, a communication method between the UE and ONN (Onboarding Network) is being considered as a means of providing NPN information to the UE when connection and registration of the UE to the NPN is required.

[0006] Currently, the handling of 5GS mobile identity IEs during the initial registration process is unclear, particularly regarding how the UE behaves when it has not initiated the initial registration for the onboarding service. In other words, if the UE does not possess a valid 5G-GUTI or a SUCI other than the onboarding SUCI during the initial registration process, and has not initiated the initial registration for the onboarding service, the UE cannot determine whether or not to include the 5GS mobile identity IE in the registration request message, nor can it determine what information should be included if the 5GS mobile identity IE is to be included in the registration request message.

[0007] One aspect of the present invention has been made in view of the above circumstances, and its purpose is that, in the initial registration procedure, if the UE does not possess a valid 5G-GUTI or a SUCI other than the onboarding SUCI, and has not initiated initial registration for the onboarding service, the UE will include a 5GS mobile identity IE in the registration request message and clarify the information to be included in the 5GS mobile identity IE. [Means for solving the problem]

[0008] A UE in one aspect of the present invention comprises a control unit, wherein if the UE does not hold a valid 5G-GUTI or a SUCI other than an onboarding SUCI, and the UE has not initiated initial registration for onboarding services in an SNPN, the control unit includes a PEI in the 5GS mobile identity IE. [Effects of the Invention]

[0009] According to one aspect of the present invention, it is possible to clarify the information to be included in the 5GS mobile identity IE when the UE has not initiated initial registration for onboarding services. [Brief explanation of the drawing]

[0010] [Figure 1] This is a diagram illustrating the general outline of the mobile communication system (EPS / 5GS). [Figure 2] This diagram illustrates the detailed configuration of the mobile communication system (EPS / 5GS). [Figure 3] This is a diagram illustrating the equipment configuration of the UE. [Figure 4] This diagram illustrates the configuration of the access network device (gNB) in 5GS. [Figure 5] This diagram illustrates the configuration of the core network equipment (AMF / SMF / UPF) in 5GS. [Figure 6] This is a diagram explaining the registration procedure. [Modes for carrying out the invention]

[0011] With reference to the drawings, the best mode for carrying out one aspect of the present invention will be described.

[0012] [1. System Overview] First, Figure 1 is a diagram illustrating the general structure of the mobile communication system 1 used in each embodiment, and Figure 2 is a diagram illustrating the detailed configuration of the mobile communication system 1.

[0013] FIG. 1 shows that the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network)_A5, access network_B120, core network_B190, and DN (Data Network)_A6.

[0014] Hereinafter, these devices / functions may be described by omitting symbols such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0015] Also, FIG. 2 shows devices / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, etc., and interfaces connecting these devices / functions to each other.

[0016] Hereinafter, these devices / functions may be described by omitting symbols such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, etc.

[0017] Note that the EPS (Evolved Packet System), which is a 4G system, is composed of access network_A and core network_A, but may further include UE and / or PDN. Also, the 5GS (5G System), which is a 5G system, is composed of UE, access network_B and core network_B, but may further include DN.

[0018] A UE is a device capable of connecting to network services via 3GPP access (also known as a 3GPP access network or 3GPP AN) and / or non-3GPP access (also known as a non-3GPP access network or non-3GPP AN). A UE may be a wireless communication terminal device such as a mobile phone or smartphone, and may be a terminal device capable of connecting to both EPS and 5GS. A UE may be equipped with a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). A UE may also be referred to as a user device or a terminal device.

[0019] Furthermore, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. E-UTRAN has one or more eNBs (evolved Node B)45. Note that in the following, eNB45 may be written simply as eNB. If there are multiple eNBs, each eNB is connected to the others, for example, by an X2 interface. Furthermore, the wireless LAN access network has one or more access points.

[0020] Furthermore, access network_B corresponds to the 5G access network (5G AN). The 5G AN consists of NG-RAN (NG Radio Access Network) and / or non-3GPP access networks. One or more gNBs (NR NodeBs)122 are located in the NG-RAN. Note that, below, gNB122 may be written with the symbol omitted, such as eNB. A gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node that connects to the 5GCN via an NG interface (including the N2 interface or N3 interface). In other words, a 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. Also, if there are multiple gNBs, each gNB is connected to the others, for example, by an Xn interface.

[0021] Furthermore, in the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. Similarly, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. Additionally, 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 the devices included in access network_A and / or the devices included in access network_B may be referred to as access networks or access network devices.

[0023] Furthermore, RAN can also be referred to as an access network. Conversely, an access network can also be called a RAN.

[0024] Furthermore, Core Network A corresponds to EPC (Evolved Packet Core). EPC is configured with, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc.

[0025] Furthermore, Core Network B corresponds to 5GCN (5G Core Network). 5GCN includes, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), and UDM (Unified Data Management). Here, 5GCN may also be expressed as 5GC.

[0026] Furthermore, in the following, Core Network A and / or Core Network B, the devices included in Core Network A and / or Core Network B may be referred to as the Core Network or Core Network devices.

[0027] The core network (Core Network A and / or Core Network B) may be an IP mobile communication network operated by a Mobile Network Operator (MNO) that connects the access network (Access Network A and / or Access Network B) to the PDN and / or DN; it may be a core network for a mobile network operator that operates and manages 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).

[0028] Furthermore, although Figure 1 shows a case where the PDN and DN are the same, they may be different. The PDN may be a Data Network (DN) that provides communication services to the UE. The DN may be configured as a packet data service network, or it may be configured for each service. In addition, the PDN may include connected communication terminals. Therefore, connecting to the PDN may also mean connecting to communication terminals or server devices located in the PDN. Furthermore, sending and receiving user data with the PDN may also mean sending and receiving user data with communication terminals or server devices located in the PDN. Note that the PDN may be referred to as DN, and the DN may be referred to as PDN.

[0029] Furthermore, in the following, access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein may be referred to as a network or network device. In other words, when a network and / or network device sends and receives messages and / or performs procedures, it means that access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein send and receive messages and / or perform procedures.

[0030] Furthermore, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the PDN or DN via the access network and the core network. That is, the UE can send and receive (communicate) user data with the PDN or DN. When sending and receiving user data, non-IP communication may be used in addition to IP (Internet Protocol) communication.

[0031] Here, IP communication refers to data communication using IP, where data is sent and received via IP packets. An IP packet consists of an IP header and a payload. The payload may include data sent 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, where data is sent and received in a format different from the structure of an IP packet. For example, non-IP communication may be data communication realized by sending and receiving application data without an IP header, or it may be user data sent and received by the UE with other headers such as a MAC header or an Ethernet® frame header attached.

[0032] [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 a diagram. Each device may be configured as physical hardware, as logical (virtual) hardware configured on general-purpose hardware, or as software. Furthermore, at least some (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

[0033] Furthermore, each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) within each device / function described below is composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each memory unit can store not only the information originally set at the time of shipment, but also various information transmitted and received with devices / functions other than its own device / function (for example, UE, and / or access network devices, and / or core network devices, and / or PDN, and / or DN). In addition, each memory unit can store identification information, control information, flags, parameters, etc. contained in control messages transmitted and received within the various communication procedures described later. Furthermore, each memory unit may store this information for each UE. In addition, when interworking between 5GS and EPS occurs, each memory unit can store control messages and user data transmitted and received with devices / functions contained within 5GS and / or EPS. In this case, not only data transmitted and received via the N26 interface can be stored, but also data transmitted and received without using the N26 interface.

[0034] [2.1. UE Equipment Configuration] First, an example of the UE (User Equipment) configuration will be explained using Figure 3. The UE consists of a control unit_A300, an antenna 310, a transceiver_A320, and a storage unit_A340. The control unit_A300, transceiver_A320, and storage unit_A340 are connected via a bus. The transceiver_A320 is connected to the antenna 310.

[0035] The control unit_A300 is a functional unit that controls the operation and functions of the entire UE. The control unit_A300 realizes various processes in the UE by reading and executing various programs stored in the memory unit_A340 as needed.

[0036] The transceiver unit A320 is a functional unit for wireless communication with base station equipment (eNB or gNB) within the access network via an antenna. In other words, the UE can use the transceiver unit A320 to send and receive user data and / or control information between the access network equipment and / or core network equipment and / or PDN and / or DN.

[0037] Referring to Figure 2, the UE can communicate with the base station equipment (eNB) in E-UTRAN via the LTE-Uu interface using the transceiver unit A320. The UE can also communicate with the base station equipment (gNB) in 5G AN using the transceiver unit A320. Furthermore, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface using the transceiver unit A320. However, since the N1 interface is logical, actual communication between the UE and the AMF takes place via the 5G AN.

[0038] Memory unit A340 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the UE.

[0039] [2.2. gNB System Configuration] Next, an example of the gNB's device configuration will be explained using Figure 4. The gNB consists of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, network connection unit_B520, transceiver unit_B530, and storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0040] The control unit B500 is a functional unit that controls the operation and functions of the entire gNB. The control unit B500 implements various processes in the gNB by reading and executing various programs stored in the memory unit B540 as needed.

[0041] The network connection unit B520 is a functional unit that allows the gNB to communicate with the AMF and / or UPF. In other words, the gNB can use the network connection unit B520 to send and receive user data and / or control information with the AMF and / or UPF.

[0042] The transceiver unit B530 is a functional unit for wireless communication with the UE via the antenna 510. In other words, the gNB can send and receive user data and / or control information to and from the UE using the transceiver unit B530.

[0043] Referring to Figure 2, the gNB within the 5G AN can communicate with the AMF via the N2 interface and with the UPF via the N3 interface by using the network connection unit B520. Furthermore, the gNB can communicate with the UE by using the transceiver unit B530.

[0044] Memory unit B540 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the gNB.

[0045] [2.3. AMF Equipment Configuration] Next, an example of the AMF's device configuration will be explained using Figure 5. The AMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The AMF may be a node that handles the control plane.

[0046] The control unit B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit B700 implements various processes in the AMF by reading and executing various programs stored in the memory unit B740 as needed.

[0047] The network connection unit_B720 is a functional unit that allows the AMF to connect to base station equipment (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF within the 5G AN. In other words, the AMF can use the network connection unit_B720 to send and receive user data and / or control information with base station equipment (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF within the 5G AN.

[0048] Referring to Figure 2, the AMF within 5GCN can communicate with the gNB via the N2 interface, the UDM via the N8 interface, the SMF via the N11 interface, and the PCF via the N15 interface, using the network connection unit _A620. Furthermore, the AMF can send and receive NAS messages with the UE via the N1 interface using the network connection unit _A620. However, since the N1 interface is logical, actual communication between the UE and the AMF takes place via the 5G AN. Additionally, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface using the network connection unit _A620.

[0049] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the AMF.

[0050] Furthermore, 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) function, connection management (CM) function, reachability management function, mobility management function for UEs, etc., forwarding SM (Session Management) messages between the UE and the SMF, access authentication (Access Authentication, Access Authorization) function, security anchor function (SEA), security context management (SCM), support for the N2 interface to the N3IWF (Non-3GPP Interworking Function), support for sending and receiving NAS signals with the UE via the N3IWF, and authentication of UEs connected via the N3IWF.

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

[0052] In other words, 5GMM-REGISTERED means that each device may have established a 5GMM context or a PDU session context. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may start sending and receiving user data and control messages, and may respond to paging. In addition, 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.

[0053] Furthermore, 5GMM-DEREGISTERED may occur even if each device has not established a 5GMM context, or if the location information of UE_A10 is not known to the network, or if the network is unreachable to UE_A10. If each device is in a 5GMM-DEREGISTERED state, UE_A10 may initiate the registration procedure, or establish a 5GMM context by executing the registration procedure.

[0054] Furthermore, connection management manages the CM state for each UE. The CM state may be synchronized between the UE and the AMF. There are two CM states: disconnected state (CM-IDLE state) and 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. Also, in the CM-IDLE state, the UE does not have an N2 connection or an N3 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. Also, in the CM-CONNECTED state, the UE may have an N2 connection and / or an N3 connection.

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

[0056] Furthermore, the CM state may be expressed as 5GMM mode. In this case, the disconnected state may be expressed as 5GMM-IDLE mode, and the connected state may be expressed as 5GMM-CONNECTED mode. Additionally, the disconnected state in 3GPP access may be expressed as 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access may be expressed as 5GMM-CONNECTED mode over 3GPP access. Furthermore, the disconnected state in non-3GPP access may be expressed as 5GMM-IDLE mode over non-3GPP access, and the connected state in non-3GPP access may be expressed as 5GMM-CONNECTED mode over non-3GPP access. Note that 5GMM-IDLE mode may also be expressed as idle mode, and 5GMM-CONNECTED mode may also be expressed as connected mode.

[0057] Furthermore, one or more AMFs may be located within core network_B. Also, an AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). Additionally, an AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs.

[0058] Furthermore, N3IWF is a device and / or function placed between the non-3GPP access and 5GCN when the UE connects to 5GS via non-3GPP access.

[0059] [2.4. SMF Equipment Configuration] Next, an example of the SMF device configuration will be explained using Figure 5. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF may be a node that handles the control plane.

[0060] The control unit B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit B700 implements various processes in the SMF by reading and executing various programs stored in the memory unit B740 as needed.

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

[0062] Referring to Figure 2, the SMF within 5GCN can communicate with the AMF via the N11 interface, the UPF via the N4 interface, the PCF via the N7 interface, and the UDM via the N10 interface by using the network connection unit A620.

[0063] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the SMF.

[0064] SMF has session management functions such as establishing, modifying, and releasing PDU sessions; IP address allocation and management functions for UEs; UPF selection and control functions; UPF configuration functions for routing traffic to appropriate destinations; functions for sending and receiving the SM portion of NAS messages; functions for notifying when downlink data has arrived (Downlink Data Notification); functions for providing AN-specific (AN-specific) SM information transmitted to ANs via the N2 interface through AMF; functions for determining the SSC mode (Session and Service Continuity mode) for sessions; and roaming functions.

[0065] [2.5. UPF Equipment Configuration] Next, an example of the UPF's configuration will be explained using Figure 5. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The UPF 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 UPF. The control unit B700 implements various processes in the UPF by reading and executing various programs stored in the memory unit B740 as needed.

[0067] The network connection unit B720 is a functional unit that allows the UPF to connect with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN. In other words, the UPF can use the network connection unit B720 to send and receive user data and / or control information with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN.

[0068] Referring to Figure 2, the UPF within 5GCN can communicate with the gNB via the N3 interface, the SMF via the N4 interface, the DN via the N6 interface, and other UPFs via the N9 interface by using the network connection unit A620.

[0069] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the UPF.

[0070] UPF has functions such as acting as an anchor point for intra-RAT mobility or inter-RAT mobility, acting as an external PDU session point for interconnecting to DNs (i.e., acting as a gateway between DNs and core network B to forward user data), routing and forwarding packets, an UL CL (Uplink Classifier) ​​function that supports routing multiple traffic flows to a single 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 notification.

[0071] Furthermore, the UPF may also be a gateway for IP communication and / or non-IP communication. The UPF may also have the function of forwarding IP communication, and may also have the function of converting non-IP communication to IP communication. In addition, multiple gateways may be gateways connecting the core network B to a single DN. The UPF may also have connectivity to other NFs, and may connect to each device via other NFs.

[0072] Furthermore, the user plane refers to user data transmitted and received between the UE and the network. The user plane may be transmitted and received using a PDN connection or a PDU session. In addition, 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 U-Plane.

[0073] Furthermore, the control plane refers to the control messages transmitted and received for communication control of the UE, etc. The control plane may be transmitted and received using the NAS (Non-Access-Stratum) signaling connection between the UE and the MME. In addition, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. In addition, 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.

[0074] Furthermore, the U-Plane (User Plane; UP) may also be a communication channel for sending and receiving user data, and may consist of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may also be a communication channel for sending and receiving control messages, and may consist of multiple bearers.

[0075] [2.6. Description of other devices and / or functions] Next, we will describe the other devices and / or functions.

[0076] PCF has functions such as providing policy rules.

[0077] Furthermore, UDM has functions such as authentication credential processing, user identification processing, access authentication, registration / mobility management, and subscription management.

[0078] Furthermore, the PCRF is connected to the PGW and / or PDN and has functions for managing QoS for data delivery. For example, it manages the QoS of the communication channel between UE_A10 and the PDN. In addition, the PCRF may also be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used by each device when sending and receiving user data.

[0079] Furthermore, the HSS is connected to the MME and / or SCEF and has functions such as managing subscriber information. The subscriber information of the HSS is referenced, for example, when the MME performs access control. In addition, the HSS may be connected to a location management device other than the MME.

[0080] [3. Explanation of terms, identification information, and procedures used in each embodiment] In each embodiment, at least one terminology, identification information, and procedure used will be explained beforehand.

[0081] [3.1. Explanation of terms and identification information used in each embodiment] First, we will explain in advance the highly specialized terminology and identification information used in each embodiment and procedure.

[0082] The term "network" refers to at least a portion of Access Network B, Core Network B, and DN. Furthermore, one or more devices included in at least a portion of Access Network B, Core Network B, and DN may be referred to as a network or network device. In other words, the statement that a network performs message transmission and / or processing may also mean that devices within the network (network devices, and / or control devices) perform message transmission and / or processing. Conversely, the statement that devices within the network perform message transmission and / or processing may also mean that the network performs message transmission and / or processing.

[0083] Furthermore, the network may refer to either a PLMN (Public Land Mobile Network) or an NPN, as described later. Additionally, when it is stated that the UE performs network selection, it may indicate that the UE performs PLMN selection or that the UE performs SNPN selection.

[0084] Furthermore, a registered PLMN is a PLMN to which a UE is registered.

[0085] Furthermore, an equivalent PLMN is a PLMN that is treated as the same as any other PLMN in the network. For example, an equivalent PLMN may be one or more PLMNs that are treated the same as registered PLMNs.

[0086] Furthermore, SM (Session Management) messages (also referred to as NAS (Non-Access-Stratum) SM messages) may be NAS messages used in procedures for SM, and may be control messages sent and received between UE_A10 and SMF_A230 via AMF_A240. In addition, SM messages may include PDU session establishment request messages, PDU session establishment acceptance messages, PDU session completion messages, PDU session rejection messages, PDU session change request messages, PDU session change acceptance messages, PDU session change response messages, etc. Furthermore, procedures for SM may include PDU session establishment procedures.

[0087] Furthermore, the 5GS (5G System) service may be a connectivity service provided using the core network_B190. In addition, the 5GS service may be a different service from the EPS service, or it may be a similar service to the EPS service.

[0088] Furthermore, non-5GS services may be any service other than 5GS services, and may include EPS services and / or non-EPS services.

[0089] Furthermore, single registration mode is a mode in which UE_A10 maintains a common registration state for 5GMM state and EMM state when N1 mode and S1 mode are available.

[0090] Furthermore, the dual registration mode is a mode in which UE_A10 maintains the registration status of 5GMM state and EMM state independently when N1 mode and S1 mode are available. Note that in dual registration mode, UE_A10 may be registered to the network in N1 mode only (i.e., registered only to 5GC), or registered to the network in S1 mode only (registered only to EPC), or registered to the network in both N1 mode and S1 mode (registered to both 5GC and EPC).

[0091] Furthermore, in order to interwork with 5GS and EPC, UEs that support both 5GC and EPC NAS can operate in single registration mode or dual registration mode.

[0092] Furthermore, S1 mode is a mode in which UE_A10 is permitted to access EPC via E-UTRAN. In other words, S1 mode may be a mode in which messages are sent and received using the S1 interface. Note that the S1 interface may consist of the S1-MME interface and the S1-U interface.

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

[0094] Furthermore, the APN (Access Point Name) can be any identification information that identifies the core network and / or external networks such as PDNs. In addition, the APN can also be used as information to select gateways such as PGW_A30 / UPF_A235 to which the core network A_90 is connected.

[0095] Furthermore, the PDN (Packet Data Network) type indicates the type of PDN connection, and includes IPv4, IPv6, IPv4v6, and non-IP. If IPv4 is specified, it means that data will be sent and received using IPv4. If IPv6 is specified, it means that data will be sent and received using IPv6. If IPv4v6 is specified, it means that data will be sent and received using either IPv4 or IPv6. If non-IP is specified, it means that communication will be conducted using a communication method other than IP, rather than IP-based communication.

[0096] Furthermore, a PDU (Protocol Data Unit) session can be defined as the relationship between a DN and an UE that provides PDU connectivity services, but it may also be connectivity established between the UE and an external gateway. In 5GS, the UE can send and receive user data to and from the DN using the PDU session by establishing a PDU session via access network_B and core network_B. Here, this external gateway may be UPF, SCEF, etc. The UE can use the PDU session to send and receive user data with devices such as application servers located on the DN.

[0097] Furthermore, each device (UE, and / or access network device, and / or core network device) may manage one or more pieces of identification information associated with each PDU session. These pieces of identification information may include one or more of the following: DNN, QoS rules, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, or they may include other information. In addition, if multiple PDU sessions are established, the pieces of identification information associated with each PDU session may be the same or different.

[0098] Furthermore, the DNN (Data Network Name) may be identification information that identifies the core network and / or external networks such as DNs. In addition, the DNN can be used as information to select gateways such as PGW_A30 / UPF_A235 to which the core network B190 is connected. Furthermore, the DNN may be equivalent to the APN (Access Point Name).

[0099] Furthermore, the PDU (Protocol Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet, and 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 will not be performed. If Unstructured is specified, it indicates that data will be sent and received to application servers, etc., on the DN using Point-to-Point (P2P) tunneling technology. As a P2P tunneling technology, for example, UDP / IP encapsulation technology may be used. In addition to the above, IP may also be included as a PDU session type. IP can be specified when the UE can use both IPv4 and IPv6.

[0100] Furthermore, an RRC (Radio Resource Control) connection is a connection established between a UE and a base station device in the access network. More specifically, an RRC connection is a connection established at the Uu reference point between the UE and the base station device in the access network. An RRC connection may consist of a radio bearer. Furthermore, an RRC connection may be a connection established in 3GPP access. Furthermore, an RRC connection may be a connection established at the RRC layer below the NAS layer. Furthermore, an RRC connection may be a connection established and / or released by sending and receiving RRC messages at the RRC layer. Furthermore, an RRC connection may be a connection suspended by sending and receiving RRC messages at the RRC layer.

[0101] Furthermore, the NAS (Non-Access Stratum) signaling connection is the connectivity between the UE and the core network. More specifically, the NAS signaling connection is the N1 mode connectivity between the UE and the AMF.

[0102] The NAS signaling connection may be via 3GPP access or via non-3GPP access.

[0103] Specifically, if the NAS signaling connection is connected via 3GPP access, the NAS signaling connection may consist of an RRC connection via a Uu reference point and an NG connection via an N2 reference point.

[0104] Conversely, if the NAS signaling connection is connected via 3GPP access, the NAS signaling connection may consist of an IPsec tunnel via an NWu reference point and an NG connection via an N2 reference point.

[0105] Here, the Uu reference point may be a reference point between the UE and the gNB. Furthermore, the NWu reference point may be a reference point between the UE and the N3IWF. Furthermore, the N2 reference point may be a reference point between the gNB or N3IWF and the AMF.

[0106] Furthermore, the NAS signaling connection may also be referred to as the NAS signaling connection. In addition, the NAS signaling connection may also be referred to as the N1 NAS signaling connection.

[0107] A tracking area is one or more ranges managed by the core network that can be represented by the location information of UE_A10. A tracking area may consist of multiple cells. Furthermore, a tracking area may be the range to which control messages such as paging are broadcast, or the range to which UE_A10 can move without handover procedures. Furthermore, a tracking area may be a routing area, a location area, or something similar. Hereinafter, a tracking area may also be a TA (Tracking Area).

[0108] The TA list is a list containing one or more TAs that the network has assigned to UE_A10. UE_A10 may move within one or more TAs included in the TA list without performing the tracking area update procedure. In other words, the TA list may be a set of information indicating the areas that UE_A10 can move within without performing the tracking area update procedure. The TA list may also be expressed as a TAI list, which consists of one or more TAIs (Tracking area identities), and hereafter, the term TAI list may refer to the TA list.

[0109] PLMN selection may be a procedure for selecting a PLMN. Alternatively, PLMN selection may be a procedure performed by a UE when connecting to a PLMN. PLMN selection may also be referred to as a PLMN selection process or a PLMN selection procedure.

[0110] A SUCI (Subscription Concealed Identifier) ​​may be a privacy-preserving identifier that includes a concealed SUPI (Concealed SUPI), as defined in 3GPP TS 23.003. Furthermore, a SUCI may consist 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.

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

[0112] Furthermore, IMSI (International Mobile Subscription Identity) may consist of MCC (Mobile Country Code), MNC (Mobile Network Code), and MSIN (Mobile Subscriber Identification Number), as specified in 3GPP TS 23.003.

[0113] Furthermore, 5G-GUTI (5G Globally Unique Temporary Identifier) ​​may be information that provides an unambiguous identifier for a UE, as defined in 3GPP TS 23.003, without revealing the UE or the user's permanent identity. 5G-GUTI may also be information that can identify the AMF and the network. Furthermore, 5G-GUTI may be information used by the network and the UE to establish the UE's identity. 5G-GUTI may consist of two elements: one that identifies the AMF to which the 5G-GUTI is assigned, and another that uniquely identifies the UE within the AMF to which the 5G-GUTI is assigned. The former may be GUAMI (Globally Unique AMF Identifier), and the latter may be 5G-TMSI (5G-Temporary Mobile Subscriber Identity). In other words, 5G-GUTI may consist of GUAMI and 5G-TMSI.

[0114] Furthermore, the IMEI (International Mobile Station Equipment Identity) may consist of the TAC (Type Allocation Code), SNR (Serial Number), and CD (Check Digit) / SD (Spare Digit), as specified in 3GPP TS 23.003.

[0115] Furthermore, IMEISV (International Mobile station Equipment Identity and Software Version number) may consist of TAC (Type Allocation Code), SNR (Serial Number), and SVN (Software Version Number), as specified in 3GPP TS 23.003.

[0116] 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​may be an abbreviation of 5G-GUTI, as specified in 3GPP TS 23.003. Furthermore, 5G-S-TMSI may enable more efficient radio signaling procedures (e.g., paging (also referred to as paging procedures) and service requests (also referred to as service request procedures)). Additionally, for paging, the UE may use 5G-S-TMSI for paging. 5G-S-TMSI may consist of an AMF Set ID, an AMF Pointer, and the 5G-TMSI itself.

[0117] Furthermore, the MAC address (Media Access Control address) may be the hardware address of a device connected to shared media, as defined in the IETF (Internet Engineering Task Force) RFC (Request for Comments). Alternatively, the MAC address may be a unique identification number assigned to the UE or network device.

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

[0119] Furthermore, the Permanent Equipment Identifier (PEI) may be information for identifying the UE, as specified in 3GPP TS 23.003. The PEI may be defined as a PEI type and an IMEI or IMEISV or MAC address or IEEE EUI-64. Here, the PEI type may represent an IMEI or IMEISV or MAC address or EUI-64. That is, when the PEI type represents an IMEI, the PEI may consist of a PEI type representing the IMEI and the IMEI. Similarly, when the PEI type represents an IMEISV, the PEI may consist of a PEI type representing the IMEISV and the IMEISV. Also, when the PEI type represents a MAC address, the PEI may consist of a PEI type representing the MAC address and the MAC address. Furthermore, when the PEI type represents an EUI-64, the PEI may consist of a PEI type representing the EUI-64 and the EUI-64.

[0120] Furthermore, 5GS mobile identity may be an IE for providing SUCI, 5G-GUTI, IMEI, IMEISV, 5G-S-TMSI, MAC address, or EUI-64. 5GS mobile identity may be information included in registration request messages or registration acceptance messages in a registration procedure, deregistration request messages (also called deregistration request messages) in a deregistration procedure initiated by a UE, service request messages in a service request procedure, configuration update commands in a configuration update procedure, identifier response messages in an identification procedure, or security mode completion messages in a security mode control procedure. 5GS mobile identity may also be referred to as a 5GS mobile identity information element (IE).

[0121] UEs not operating in SNPN access mode or SNPN access operation mode may perform PLMN selection. UEs operating in SNPN access mode or SNPN access operation mode do not need to perform PLMN selection. PLMN selection may be performed without registration. In other words, PLMN selection may be performed if the UE has not completed registration to the network. PLMN selection may have an automatic PLMN selection mode and a manual PLMN selection mode.

[0122] Furthermore, a Non-Public Network (NPN) is a private network not intended for general use, but rather for specific purposes by specific users, such as private use by companies. There are two types of NPNs: Stand-alone Non-Public Network (SNPN) and Public network integrated NPN. Note that when NPN is mentioned below, it may refer to both SNPN and Public network integrated NPN.

[0123] An SNPN is a network operated by an NPN operator and unaffected by the functional components provided by a PLMN. In other words, an SNPN is a dedicated NPN network independent of the publicly accessible PLMN. An SNPN may be a network identified by an SNPN identity (SNPN ID). The SNPN ID may be a combination of a PLMN ID and a Network identifier (NID). The PLMN ID used in the SNPN ID may be information reserved for a private network; for example, the MCC included in the PLMN ID may be 999. Furthermore, if a UE is registered with an SNPN, the registered SNPN may be referred to as a registered SNPN or RSNPN (registered SNPN).

[0124] A Network Identifier (NID) is information that identifies a network. An SNPN may be identified by a combination of a PLMN ID and an NID. The NID may be unique within the SNPN or unique globally.

[0125] A Public Network Integrated NPN (NPN) is a network implemented using the functional parts of PLMN. In other words, a Public Network Integrated NPN is an NPN virtually implemented within PLMN. Furthermore, a Public Network Integrated NPN is an NPN that can be created via PLMN. A Public Network Integrated NPN may also be implemented using the network slice function. Specifically, a Public Network Integrated NPN may be a network that can be implemented using a network slice allocated for an NPN. In this case, a Public Network Integrated NPN may be identified by S-NSSAI, or by a combination of S-NSSAI and CAG ID.

[0126] Furthermore, a Public Network Integrated NPN may be implemented using a Domain Name (DN). Specifically, a Public Network Integrated NPN may be a network that can be implemented by using a DN for the NPN. In this case, the Public Network Integrated NPN may be identified by the DNN, or by a combination of the DNN and the CAG ID.

[0127] A CAG (Closed Access Groups) ID is information that identifies a group of subscribers who are permitted to connect to one or more cells associated with the CAG. A CAG may be a group identified by its CAG ID. CAGs are groups used when implementing Public Network Integrated Networks (NPNs) on network slices. CAGs may also be used to prevent unauthorized users (UEs) from attempting to access network slices allocated for NPNs. Furthermore, a CAG ID is unique information within the PLMN.

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

[0129] SNPN access mode is a mode in which SNPN is selected. SNPN access mode may also be a mode in which the UE is registered with SNPN. Furthermore, SNPN access mode may also be a mode in which the UE is connected to SNPN. In other words, a UE operating in SNPN access mode may select only SNPN when selecting a network. More specifically, a UE operating in SNPN access mode may select only SNPN via the Uu interface when selecting a network. In other words, a UE operating in SNPN access mode may select SNPN instead of PLMN when selecting a network. Here, a UE operating in SNPN access mode may also be referred to as a UE in SNPN access mode. Furthermore, a UE in SNPN access mode may also be a UE with SNPN enabled.

[0130] SNPN access operation mode is a mode of connection to SNPN via SNPN access mode or non-3GPP access. Here, "non-3GPP access" in SNPN may refer to the case where the UE connects to SNPN via PLMN. Furthermore, the UE may operate in SNPN access mode or in SNPN access operation mode. Also, if the UE does not operate in SNPN access mode, it does not have to operate in SNPN access operation mode. In addition, a UE in SNPN access mode may also be a UE in SNPN access operation mode.

[0131] SNPN selection may be a procedure for selecting an SNPN. Alternatively, SNPN selection may be a procedure performed by the UE when connecting to an SNPN. SNPN selection may also be referred to as an SNPN selection process or an SNPN selection procedure.

[0132] Furthermore, SNPN selection may be a process for selecting an SNPN. Alternatively, SNPN selection may be a process performed by the UE when connecting to an SNPN.

[0133] UEs operating in SNPN access mode or SNPN access operation mode may perform SNPN selection. UEs not operating in SNPN access mode or SNPN access operation mode do not need to perform SNPN selection. SNPN selection may have an automatic SNPN selection mode and a manual SNPN selection mode. SNPN selection may be performed without registration. In other words, SNPN selection may be performed if the UE has not completed registration to the network.

[0134] An equivalent PLMN may be an SNPN that is treated as the same as any other SNPN. For example, an equivalent PLMN may be one or more SNPNs that are treated the same as registered SNPNs.

[0135] Furthermore, an Equal SNPN may be a PLMN that is treated as if it were the same SNPN as any other SNPN. For example, an Equal SNPN may be one or more PLMNs that are treated the same as a registered SNPN.

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

[0137] Default UE credentials are information held by a UE before the actual onboarding process. Default UE credentials may be used to uniquely identify the UE. Furthermore, default UE credentials may be used to verify the security of the UE.

[0138] A Default Credential Server (DCS) is a server that can authenticate UEs using a default UE certificate. A DCS may also be a server that can provide authentication functionality for UEs using a default UE certificate to other devices or entities.

[0139] NPN certificates (NPN credentials) are information that a UE uses for authentication to access an NPN. An NPN certificate may be a 3GPP certificate or a non-3GPP certificate.

[0140] The Onboarding Network (ON) is a network that provides UEs with initial registration and / or access for onboarding purposes. In other words, UEs may register with and / or access the Onboarding Network and undergo onboarding. The Onboarding Network may also be referred to as ONN.

[0141] Here, the onboarding network may be implemented by PLMN. Furthermore, the onboarding network may be implemented by SNPN.

[0142] A provisioning server is a server that provides subscription data to authenticated and authorized UEs. A provisioning server may also provide the authenticated and authorized UEs with subscription data and other configuration information.

[0143] Furthermore, the provisioning server may be a server located in the onboarding network. Furthermore, the provisioning server may be a server located in the PLMN. Furthermore, the provisioning server may be a server located in the SPN. Furthermore, the provisioning server may be a server located in the core network. Furthermore, the provisioning server may be a server located in an external DN.

[0144] A Subscription Owner (SO) is an entity that stores subscription data and / or other configuration information and provides subscription data and / or other configuration information to the UE via the PS domain as a result of the UE onboarding procedure. In other words, a Subscription Owner is an entity that stores subscription data and / or other configuration information and may be an entity that provides subscription data and / or other configuration information to the UE during the UE onboarding procedure.

[0145] UE onboarding involves providing UEs and internal network entities with the information necessary for the UEs to gain access to and connectivity to authorized NPNs.

[0146] In other words, UE onboarding may involve providing information to the UE and entities within the network. This information may be necessary for the UE to access or establish connectivity to the NPN. Furthermore, this access to or connectivity to the NPN may be authorized. In addition, this information may be SNPN information.

[0147] To put it another way, if a UE attempts to access or establish connectivity to the NPN, the UE may obtain the necessary information for accessing or establishing connectivity to the NPN by conducting UE onboarding. Furthermore, the UE may perform procedures for accessing or establishing connectivity to the NPN after conducting UE onboarding.

[0148] Furthermore, UE onboarding may also be referred to as the UE onboarding procedure. Additionally, UE onboarding may be referred to as the onboarding service. Furthermore, UE onboarding may also be referred to simply as onboarding.

[0149] In other words, when we say "UE onboarding procedure," we may mean UE onboarding. Furthermore, when we say "onboarding service," we may mean UE onboarding. Furthermore, when we say "onboarding," we may mean UE onboarding.

[0150] SNPN information is information necessary for the UE to access or establish connectivity to the SNPN. SNPN information may also be information used by the UE when performing procedures to access or establish connectivity to the SNPN. Furthermore, SNPN information may also be subscription data and / or other configuration information. Furthermore, SNPN information may also be an NPN certificate. Furthermore, SNPN information may be referred to as NPN information.

[0151] Furthermore, the UE may obtain SNPN information from the network during UE onboarding. More specifically, the UE may obtain SNPN information from the provisioning server or the subscription owner during UE onboarding.

[0152] In other words, the network may provide SNPN information to the UE during UE onboarding. More specifically, the provisioning server or subscription owner may provide SNPN information to the UE during UE onboarding.

[0153] The SNPN information provision procedure is the procedure for the network to provide SNPN information to the UE. In other words, the SNPN information provision procedure is the procedure for the UE to obtain SNPN information from the network. Furthermore, the SNPN information provision procedure may also be a procedure for performing UE onboarding.

[0154] The network may provide SNPN information to the UE in the SNPN information provision procedure. More specifically, the provisioning server or subscription owner may provide SNPN information to the UE in the SNPN information provision procedure.

[0155] Furthermore, the UE may obtain SNPN information from the network during the SNPN information provision procedure. More specifically, the UE may obtain SNPN information from the provisioning server or the subscription owner during the SNPN information provision procedure.

[0156] Furthermore, the UE may release the first list upon completion of the procedure for providing SNPN information. In other words, the UE may release the first list upon completion of obtaining SNPN information.

[0157] More specifically, if the UE holds the first list, it may release the first list upon completion of the procedure for providing SNPN information. In other words, if the UE holds the first list, it may release the first list upon completion of obtaining SNPN information.

[0158] Conversely, the UE may release the first list in the non-registration procedure performed upon completion of the SNPN information provision procedure. More specifically, if the UE holds the first list, it may release the first list in the non-registration procedure performed upon completion of the SNPN information provision procedure.

[0159] Here, the procedure for providing SNPN information may include both a procedure for providing SNPN information via the user plane and a procedure for providing SNPN information via the control plane.

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

[0161] Specifically, the procedure for providing SNPN information via the user plane is a procedure in which, after establishing a PDU session between the UE and the network, the network uses the PDU session to provide SNPN information to the UE.

[0162] In this case, if the procedure for providing SNPN information via the user plane is used, the network may provide SNPN information to the UE by establishing a PDU session with the UE and transmitting the SNPN information to the UE over the PDU session. In other words, if the procedure for providing SNPN information via the user plane is used, the UE may obtain SNPN information by establishing a PDU session with the network and receiving the SNPN information from the network over the PDU session.

[0163] Furthermore, the PDU session used to provide SNPN information may be a PDU session used for the purpose of providing SNPN information. In other words, the PDU session used to provide SNPN information may be a PDU session for the purpose of providing SNPN information.

[0164] The procedure for providing SNPN information via the control plane is the procedure by which the network provides SNPN information to the UE via the control plane. In other words, the procedure for providing SNPN information via the control plane is the procedure by which the UE obtains SNPN information from the network via the control plane.

[0165] Specifically, the procedure for providing SNPN information via the control plane is a procedure for providing SNPN information from the network to the UE using control messages transmitted and received on the control plane.

[0166] In this case, when using the procedure for providing SNPN information via the control plane, the SNPN information may be provided to the UE by including it in the URSP (UE Route Selection Policy) and sending it to the UE. Furthermore, when using the procedure for providing SNPN information via the control plane, the SNPN information may also be provided to the UE by including it in the PCO (Protocol Configuration Options) or ePCO (Extended Protocol Configuration Options) and sending it to the UE.

[0167] In other words, when using the procedure for providing SNPN information via the control plane, the UE may obtain SNPN information by receiving the SNPN information contained in the URSP from the network. When using the procedure for providing SNPN information via the control plane, the UE may obtain SNPN information by receiving the SNPN information contained in the PCO or ePCO from the network.

[0168] Furthermore, URSP may be an information element included in the MANAGE UE POLICY COMMAND message. In addition, PCO may be an information element included in the SM message (Session Management message). Furthermore, ePCO may be an information element included in the SM message (Session Management message).

[0169] Furthermore, UE policy management command messages may be control messages sent and received between the PCF and the UE. Furthermore, SM messages may be control messages sent and received between the UE and the SMF. Furthermore, SM messages may include PDU session establishment acceptance messages, PDU session modification command messages, PDU session release command messages, etc.

[0170] The first list is a list containing information that identifies one or more networks for which onboarding services are unavailable. The first list may also be a list containing information that identifies one or more networks. In other words, the first list may be a set of information that identifies one or more networks.

[0171] Here, the network identified by the network identification information may be a network where onboarding services are unavailable. Furthermore, the network identified by the network identification information may be a network that does not support onboarding services. Furthermore, the network identified by the network identification information may be a PLMN (Public Land Mobile Network) or an SNPN (Stand-alone Non-Public Network).

[0172] Furthermore, the network identification information may be information that identifies the PLMN, or information that identifies the SNPN. In other words, the network identification information may be the PLMN ID and / or the SNPN ID. Furthermore, the network identification information may be the PLMN identity and / or the SNPN identity.

[0173] Furthermore, the first list may be maintained until the SNPN information is provided to the UE. In other words, the first list may be released upon the provision of the SNPN information to the UE. Furthermore, the first list may be released upon the execution of the non-registration procedure.

[0174] Furthermore, the first list may be released based on power off and / or SIM removal. Furthermore, the first list may be released based on timer expiration.

[0175] Furthermore, the first list may be managed on a per-access basis. Specifically, the first list may be managed separately as a list for 3GPP access and a list for non-3GPP access.

[0176] The first identification information is information that indicates only the onboarding service. Furthermore, the first identification information may also be information that indicates only the request for the onboarding service. Furthermore, the first identification information may also be information that indicates a registration request that is only available for the onboarding service. In addition, the first identification information may be realized by the request type in which the onboarding service is configured.

[0177] Furthermore, the first identification information may also be information indicating whether the UE supports registration that is only available for onboarding services. The first identification information may also be information indicating that the UE supports registration that is only available for onboarding services, or information indicating that the UE does not support registration that is only available for onboarding services. Furthermore, the first identification information may be implemented by bits indicating whether the UE supports registration that is only available for onboarding services. Here, the bits indicating whether the UE supports registration that is only available for onboarding services may also be bits that constitute a 5GMM capability information element, which indicates the UE's capabilities in 5G.

[0178] Furthermore, the first identification information may be the default UE certificate. Furthermore, the first identification information may be information that identifies the UE. Furthermore, the first identification information may be information that identifies the default certificate server. Furthermore, the first identification information may be information that identifies the network to be connected to.

[0179] Furthermore, the first identification information may be information selected and determined based on the UE's settings, and / or the UE's state, and / or user policies, and / or application requirements.

[0180] The second identification information indicates the type of SNPN information provision procedure supported by the UE. The second identification information may indicate that the UE supports obtaining SNPN information via the user plane (UP), or it may indicate that the UE supports obtaining SNPN information via the control plane (CP). Furthermore, the second identification information may be implemented by bits indicating the type of SNPN information provision procedure supported by the UE. Here, the bits indicating the type of SNPN information provision procedure supported by the UE may be bits that constitute a 5GMM capability information element, which indicates the UE's capabilities in 5G.

[0181] Furthermore, the second identification information may include the meaning indicated by the third identification information and the meaning indicated by the fourth identification information. Furthermore, the second identification information may be composed of the third identification information and the fourth identification information.

[0182] Furthermore, the second identification information may be information selected and determined based on the UE's settings, and / or the UE's state, and / or user policies, and / or application requirements.

[0183] The third identifier is information indicating whether the UE supports the acquisition of SNPN information via the user plane (UP). The third identifier may be information indicating that the UE supports the acquisition of SNPN information via the user plane, or it may be information indicating that the UE does not support the acquisition of SNPN information via the user plane. Furthermore, the third identifier may be implemented by a bit indicating whether the UE supports the acquisition of SNPN information via the user plane. Here, the bit indicating whether the UE supports the acquisition of SNPN information via the user plane may be a bit that constitutes a 5GMM capability information element, which indicates the UE's capability in 5G.

[0184] Furthermore, the third identification information may be information selected and determined based on the UE's settings, and / or the UE's state, and / or user policies, and / or application requirements.

[0185] The fourth identifier is information indicating whether the UE supports obtaining SNPN information via the control plane (CP). The fourth identifier may be information indicating that the UE supports obtaining SNPN information via the control plane, or it may be information indicating that the UE does not support obtaining SNPN information via the control plane. Furthermore, the fourth identifier may be implemented by a bit indicating whether the UE supports obtaining SNPN information via the control plane. Here, the bit indicating whether the UE supports obtaining SNPN information via the control plane may be a bit that constitutes a 5GMM capability information element, which indicates the UE's capability in 5G.

[0186] Furthermore, the fourth identification information may be information selected and determined based on the UE's settings, and / or the UE's state, and / or user policies, and / or application requirements.

[0187] The fifth identifier is information indicating the type of procedure for providing SNPN information requested by the UE. The fifth identifier may be information indicating that the UE requests the acquisition of SNPN information via the user plane (UP), or information indicating that the UE requests the acquisition of SNPN information via the control plane (CP). Furthermore, the fifth identifier may be implemented by bits indicating the type of procedure for providing SNPN information requested by the UE. Here, the bits indicating the type of procedure for providing SNPN information requested by the UE may be bits that constitute a 5GS update type information element.

[0188] Furthermore, the fifth identification information may be information selected and determined based on the UE's settings, and / or the UE's state, and / or user policies, and / or application requirements.

[0189] The sixth identifier is information indicating a follow-on request. Here, the sixth identifier may also be information indicating a follow-on request pending. Conversely, the sixth identifier may also be information indicating no follow-on request pending.

[0190] Furthermore, the sixth identification information may indicate whether or not it is necessary to maintain NAS signaling after the completion of this procedure. Here, the sixth identification information may be information indicating that it is necessary to maintain NAS signaling after the completion of this procedure. Conversely, the sixth identification information may be information indicating that it is not necessary to maintain NAS signaling after the completion of this procedure.

[0191] Furthermore, the sixth identification information may be implemented by bits indicating a Follow-on request. Here, the bits indicating a Follow-on request may be bits that constitute a 5GS (5G System) registration type, indicating the UE's capability in 5G.

[0192] Furthermore, the sixth identification information may be information selected and determined based on the UE's settings, and / or the UE's state, and / or user policies, and / or application requirements.

[0193] The seventh identification information may be 5GS mobile identity IE. Furthermore, the seventh identification information may be information containing one or more eighth identification information.

[0194] Furthermore, during the registration process, the UE may handle the seventh identification information. The seventh identification information may be information contained in the registration request message and / or the registration acceptance message and / or the registration rejection message.

[0195] The eighth piece of identification information may be information included in 5GS mobile identity IE. In other words, the eighth piece of identification information may be information included in the seventh piece of identification information. Furthermore, one or more pieces of the eighth piece of identification information may be included in the seventh piece of identification information.

[0196] Furthermore, the eighth identification information may be a PEI (Permanent Equipment Identifier). Furthermore, the eighth identification information may be a SUCI (Subscription Concealed Identifier). Furthermore, the eighth identification information may be a 5G-GUTI (5G-Globally Unique Temporary Identifier). Furthermore, the eighth identification information may be an IMEI (International Mobile station Equipment Identity). Furthermore, the eighth identification information may be an IMEISV (International Mobile station Equipment Identity and Software Version number). Furthermore, the eighth identification information may be a 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier). Furthermore, the eighth identification information may be a MAC address (Media Access Control address). Furthermore, the eighth identification information may be an EUI-64 (Extended Unique Identifier-64).

[0197] The ninth identification information may be information indicating an SNPN onboarding registration. Furthermore, the ninth identification information may be information included in 5GS registration type IE. Furthermore, the ninth identification information may be information included in 5GS registration type. Furthermore, the ninth identification information may be information indicating an SNPN onboarding registration included in 5GS registration type IE. Furthermore, the ninth identification information may be information indicating an SNPN onboarding registration included in 5GS registration type.

[0198] Furthermore, the ninth identification information may be information included in the registration request message. Furthermore, the ninth identification information may be information used when performing initial registration for onboarding services in SNPN. Furthermore, the ninth identification information may be information indicating that initial registration for onboarding services in SNPN is being performed.

[0199] Furthermore, the ninth identification information may be information indicating whether or not it supports initial registration for onboarding services in SNPN. The ninth identification information may be information indicating that it supports initial registration for onboarding services in SNPN. The ninth identification information may be information indicating that it does not support initial registration for onboarding services in SNPN.

[0200] Furthermore, the ninth identifying information may be information selected and determined based on the UE's configuration, and / or the UE's state, and / or user policies, and / or application requirements.

[0201] The eleventh identifier is information indicating whether the network supports registration that is only available for onboarding services. The eleventh identifier may be information indicating that the network supports registration that is only available for onboarding services, or it may be information indicating that the network does not support registration that is only available for onboarding services. Furthermore, the eleventh identifier may be implemented by bits indicating whether the network supports registration that is only available for onboarding services. Here, the bits indicating whether the network supports registration that is only available for onboarding services may be bits that constitute a 5GS network feature support information element, which indicates the network's capabilities in 5G.

[0202] Furthermore, the 11th identification information may also be information indicating whether or not registration for onboarding services only is permitted. The 11th identification information may also be information indicating whether or not registration for onboarding services only is permitted, or information indicating that registration for onboarding services only is not permitted. Furthermore, the 11th identification information may be implemented by a bit indicating whether or not registration for onboarding services only is permitted.

[0203] Furthermore, the 11th identification information may be information selected and determined by the network based on received identification information, and / or information associated with the NSI, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, etc.

[0204] The twelfth identification information is information indicating the type of SNPN information provision procedure supported by the network. The twelfth identification information may indicate that the network supports the provision of SNPN information via the user plane (UP), or it may indicate that the network supports the provision of SNPN information via the control plane (CP). Furthermore, the twelfth identification information may be implemented by bits indicating the type of SNPN information provision procedure supported by the network. Here, the bits indicating the type of SNPN information provision procedure supported by the network may be bits that constitute a 5GS network feature support information element, which indicates the network's capabilities in 5G.

[0205] Furthermore, the 12th identification information may also be information indicating that SNPN information is provided via the user plane. Furthermore, the 12th identification information may also be information indicating that the provision of SNPN information via the user plane is supported.

[0206] Furthermore, the 12th identification information may be information indicating that SNPN information is provided via the control plane. Furthermore, the 12th identification information may be information indicating that the provision of SNPN information via the control plane is supported.

[0207] Furthermore, the 12th identification information may include the meaning indicated by the 13th identification information and the meaning indicated by the 14th identification information. Furthermore, the 12th identification information may be composed of the 13th identification information and the 14th identification information.

[0208] Furthermore, the 12th identification information may be information selected and determined by the network based on received identification information, and / or information associated with the NSI, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, etc.

[0209] The 13th identifier is information indicating whether the network supports the provision of SNPN information via the user plane (UP). The 13th identifier may be information indicating that the network supports the provision of SNPN information via the user plane, or it may be information indicating that the network does not support the provision of SNPN information via the user plane. Furthermore, the 13th identifier may be implemented by bits indicating whether the network supports the provision of SNPN information via the user plane. Here, the bits indicating whether the network supports the provision of SNPN information via the user plane may be bits that constitute a 5GS network feature support information element, which indicates the network's capabilities in 5G.

[0210] Furthermore, the 13th identification information may also be information indicating that SNPN information is provided via the user plane. Furthermore, the 13th identification information may also be information indicating that the provision of SNPN information via the user plane is supported.

[0211] Furthermore, the 13th identification information may be information selected and determined by the network based on received identification information, and / or information associated with the NSI, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, etc.

[0212] The 14th identifier is information indicating whether the network supports the provision of SNPN information via the control plane (CP). The 14th identifier may be information indicating that the network supports the provision of SNPN information via the control plane, or it may be information indicating that the network does not support the provision of SNPN information via the control plane. Furthermore, the 14th identifier may be implemented by bits indicating whether the network supports the provision of SNPN information via the control plane. Here, the bits indicating whether the network supports the provision of SNPN information via the control plane may be bits that constitute a 5GS network feature support information element, which indicates the network's capabilities in 5G.

[0213] Furthermore, the 14th identification information may also be information indicating that SNPN information is provided via the control plane. Furthermore, the 14th identification information may also be information indicating that the provision of SNPN information via the control plane is supported.

[0214] Furthermore, the 14th identification information may be information selected and determined by the network based on received identification information, and / or information associated with the NSI, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, etc.

[0215] The 21st identification information is a reason value indicating the reason why the registration procedure was rejected. The 21st identification information may be a 5GSM (5GS Session Management) reason value.

[0216] Here, the reason value may indicate that the onboarding service is unavailable. In other words, the reason value may indicate that the onboarding service is not permitted. Furthermore, the reason value may indicate that registration that only allows the onboarding service is not permitted.

[0217] Furthermore, the reason value may indicate that the network does not support onboarding services. The reason value may also indicate that the network does not support registration that is only available for onboarding services.

[0218] Furthermore, the reason value may indicate that a request for onboarding services only was rejected. Furthermore, the reason value may indicate that a request for registration that is only available for onboarding services was rejected.

[0219] Furthermore, the 21st identification information may indicate that the onboarding service is unavailable. In other words, the 21st identification information may indicate that the onboarding service is not permitted. Furthermore, the 21st identification information may indicate that registration that is only available for onboarding services is not permitted.

[0220] Furthermore, the 21st identification information may indicate that the network does not support onboarding services. The 21st identification information may also indicate that the network does not support registrations that are only available for onboarding services.

[0221] Furthermore, the 21st identification information may indicate that a request for onboarding services only was rejected. Furthermore, the 21st identification information may indicate that a request for registration available only for onboarding services was rejected.

[0222] Furthermore, the 21st identification information may be information selected and determined by the network based on received identification information, and / or information associated with the NSI, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, etc.

[0223] [3.2. Description of the procedures used in each embodiment] Next, the procedures used in each embodiment will be described. Note that the procedures used in each embodiment include a registration procedure. The following describes each procedure.

[0224] In each embodiment, the explanation will be based on the example where the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are configured as the same device (i.e., the same physical hardware, the same logical hardware, or the same software), as shown in Figure 2. However, the contents described in this embodiment are also applicable when 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 them, 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.

[0225] [3.2.1. Registration Procedure] First, the registration procedure will be explained using Figure 6. The registration procedure is a procedure in 5GS. Hereafter, "this procedure" refers to the registration procedure. The registration procedure is a procedure in which the UE takes the lead in registering with access network_B and / or core network_B and / or DN. If the UE is not registered with the network, it can execute this procedure at any time, for example, when the power is turned on. In other words, if the UE is in the unregistered state (RM-DEREGISTERED state), it can start this procedure at any time. In addition, each device (especially the UE and AMF) can transition to the registered state (RM-REGISTERED state) based on the completion of the registration procedure.

[0226] Furthermore, the registration process may be an initial registration initiated by the UE, or it may be a mobility and periodic registration.

[0227] Furthermore, the registration procedure may be the registration procedure for onboarding services at SNPN or PLMN. Alternatively, the registration procedure may be the initial registration for onboarding services at SNPN or PLMN.

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

[0229] A UE may initiate the registration process when it moves across TAs. In other words, a UE may initiate the registration process when it moves to a TA different from the one indicated in its TA list. Furthermore, a UE may initiate this process when a running timer expires. Furthermore, a UE may initiate the registration process when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, a UE may initiate the registration process if there is a change in the capability information and / or preferences related to the establishment of the UE's PDU session. Furthermore, a UE may initiate the registration process periodically. Furthermore, a UE may initiate the registration process based on the completion of a UE configuration update procedure. Note that a UE can perform the registration process at any time it chooses, not limited to these.

[0230] Furthermore, even if the UE is registered, it may initiate the registration process periodically. In other words, the UE may initiate the registration process based on the expiration of a timer.

[0231] Furthermore, the registration procedure performed based on the mobility of the UE and the registration procedure performed periodically may be referred to as the registration procedure for mobility and registration renewal. In other words, the registration procedure for mobility and registration renewal may be a registration procedure performed based on the mobility of the UE, or a registration procedure performed periodically. Moreover, the registration procedure for mobility and registration renewal may be a registration procedure performed based on a configuration update of the UE. Moreover, the registration procedure for mobility and registration renewal may be a registration procedure performed to establish a communication channel for sending and receiving user data. Moreover, the registration procedure for mobility and registration renewal may be a registration procedure performed based on a request from the network. In other words, the registration procedure for mobility and registration renewal may be a registration procedure other than the initial registration procedure. Hereinafter, the registration procedure for mobility and registration renewal may be referred to as this procedure.

[0232] Next, we will explain each step of the registration process. Note that the registration process described below may refer to the initial registration process or the registration process for mobility and registration renewal.

[0233] First, the UE initiates the registration process by sending a Registration request message to the AMF (S800)(S802)(S804). Specifically, the UE sends an RRC message containing the Registration request message to the 5G AN (or gNB) (S800). The Registration request message is a NAS message. The RRC message may be a control message sent and received between the UE and the 5G AN (or gNB). The NAS message is processed at the NAS layer, and the RRC message is processed at the RRC layer. The NAS layer is a higher layer than the RRC layer.

[0234] Here, the UE may include one or more of the identification information from at least the first to 9 in the registration request message and / or RRC message. More specifically, the UE may include one or more of the identification information from at least the first to 9 in the registration request message and / or RRC message, but may also include them in a different control message, for example, a control message at a lower layer than the RRC layer (e.g., MAC layer, RLC layer, PDCP layer). The UE may indicate that it supports each function by transmitting this identification information, or it may indicate a request from the UE. Furthermore, if multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. The information indicating support for each function and the information indicating a request to use each function may be transmitted and received with the same identification information, or they may be transmitted and received as different identification information.

[0235] If a UE requests onboarding services, it may include one or more of the identifiers from the first to the ninth sets of identifiers in the registration request message. Furthermore, if a UE requests registration that is only available for onboarding services, it may include one or more of the identifiers from the first to the ninth sets of identifiers in the registration request message. Furthermore, if a UE requests the use of the SNPN information provision procedure, it may include one or more of the identifiers from the first to the ninth sets of identifiers in the registration request message.

[0236] Furthermore, if the UE supports onboarding services, it may include one or more of the identifiers from the first to the ninth sets of identifiers in the registration request message. Furthermore, if the UE supports the procedure for providing SNPN information, it may include one or more of the identifiers from the first to the ninth sets of identifiers in the registration request message.

[0237] Furthermore, if the UE needs to obtain SNPN information, it may include one or more of the identifiers from the first to the 9 identifiers in the registration request message. Furthermore, if the UE needs to perform onboarding services, it may include one or more of the identifiers from the first to the 9 identifiers in the registration request message. Furthermore, if the UE needs to perform procedures for providing SNPN information, it may include one or more of the identifiers from the first to the 9 identifiers in the registration request message.

[0238] Furthermore, if this procedure is a registration procedure for onboarding services, the UE may include one or more of the identification information from items 1 through 9 in the registration request message.

[0239] Furthermore, if the UE supports registrations that are only available for onboarding services, it may include a first identifier in the registration request message. More specifically, if the UE supports onboarding services, it may include a first identifier in the registration request message indicating that the UE supports registrations that are only available for onboarding services.

[0240] Furthermore, if the UE supports SNPN information provision procedures, it may include a second identifier in the registration request message indicating the type of SNPN information provision procedure that the UE supports. More specifically, if the UE supports SNPN information provision procedures via the user plane, it may include a second identifier in the registration request message indicating that it supports SNPN information provision procedures via the user plane. Furthermore, if the UE supports SNPN information provision procedures via the control plane, it may include a second identifier in the registration request message indicating that it supports SNPN information provision procedures via the control plane.

[0241] Furthermore, if the UE supports the procedure for providing SNPN information via the user plane, it may include a third identifier in the registration request message. More specifically, if the UE supports the procedure for providing SNPN information via the user plane, it may include a third identifier in the registration request message indicating that it supports the procedure for providing SNPN information via the user plane.

[0242] Furthermore, if the UE supports the procedure for providing SNPN information via the control plane, it may include a fourth identifier in the registration request message. More specifically, if the UE supports the procedure for providing SNPN information via the control plane, it may include a fourth identifier in the registration request message indicating that it supports the procedure for providing SNPN information via the control plane.

[0243] Furthermore, if the UE supports the procedure for providing SNPN information via the control plane, it may include a fourth identifier in the registration request message indicating support for the procedure for providing SNPN information using a PCO or ePCO. Furthermore, if the UE supports the procedure for providing SNPN information via the control plane, it may include a fourth identifier in the registration request message indicating support for the procedure for providing SNPN information using URSP.

[0244] Furthermore, if the UE requests the use of an SNPN information provision procedure, it may include a fifth identifier in the registration request message. Furthermore, if the UE requests the use of an SNPN information provision procedure, it may include a fifth identifier in the registration request message indicating the type of SNPN information provision procedure requested by the UE. More specifically, if the UE requests the use of an SNPN information provision procedure via the user plane, it may include a fifth identifier in the registration request message indicating the SNPN information provision procedure via the user plane. Furthermore, if the UE requests the use of an SNPN information provision procedure via the control plane, it may include a fifth identifier in the registration request message indicating the SNPN information provision procedure via the control plane.

[0245] Furthermore, if this procedure is a registration procedure for onboarding services, the UE may include a sixth identifier in the registration request message. More specifically, if this procedure is a registration procedure for onboarding services, the UE may include a sixth identifier indicating "Follow-on request pending" in the registration request message.

[0246] Furthermore, the UE may include one or more of the identification information from the first to the 9th set of identification information in the registration request message, thereby indicating to the network what the identification information included in the registration request message represents. Furthermore, the UE may include one or more of the identification information from the first to the 9th set of identification information in the registration request message, thereby requesting to the network what the identification information included in the registration request message represents.

[0247] Furthermore, the UE may select and decide whether to include one or more of the identification information from the first to the ninth categories 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.

[0248] Furthermore, the UE may initiate the PDU session establishment procedure during the registration procedure by including an SM message (e.g., a PDU session establishment request message) in the registration request message, or by sending an SM message (e.g., a PDU session establishment request message) together with the registration request message.

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

[0250] When the AMF receives a registration request message, it can perform a first conditional determination. This first conditional determination determines whether the network (or the AMF) will accept the UE's request. If the first conditional determination is true, the AMF initiates the procedure shown in Figure 6(A); if the first conditional determination is false, it initiates the procedure shown in Figure 6(B).

[0251] Furthermore, the first condition determination may be performed based on the receipt of a registration request message, and / or each piece of identification information contained 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 context held by AMF, etc. For example, if the network permits the UE's request, the first condition determination is true, and if the network does not permit the UE's request, the first condition determination may be false. Also, if the network to which the UE is registered, and / or the devices within the network, support the function requested by the UE, the first condition determination is true, and if they do not support the function requested by the UE, the first condition determination may be false. Furthermore, if the transmitted and received identification information is permitted, the first condition determination is true, and if the transmitted and received identification information is not permitted, the first condition determination may be false. Furthermore, the conditions that determine the truth or falsity of the first condition determination are not limited to those described above.

[0252] First, let's explain the case where the first condition is true. In the procedure shown in Figure 6(A), the AMF can first perform the fourth condition. The fourth condition is used to determine whether or not the AMF will send and receive SM messages with the SMF.

[0253] Furthermore, the fourth condition determination may be performed based on whether or not the AMF has received an SM message. Alternatively, the fourth condition determination may be performed based on whether or not the registration request message contains an SM message. For example, if the AMF has received an SM message and / or the registration request message contains an SM message, the fourth condition determination may be true, and if the AMF has not received an SM message and / or the registration request message does not contain an SM message, the fourth condition determination may be false. Furthermore, the conditions that determine the truth or falsity of the fourth condition determination are not limited to those described above.

[0254] Next, based on the receipt of the registration request message and / or the completion of the transmission and reception of SM messages with the SMF, the AMF sends a Registration Accept message to the UE via the 5G AN (or gNB) as a response message to the Registration Request message (S808). For example, if the fourth condition determination is false, the AMF may send a Registration Accept message based on the receipt of the Registration Request message from the UE. Alternatively, if the fourth condition determination is true, the AMF may send a Registration Accept message based on the completion of the transmission and reception of SM messages with the SMF. Note that the Registration Accept message is a NAS message transmitted and received on the N1 interface, but it is included in the RRC message transmitted and received between the UE and the 5G AN (gNB).

[0255] The AMF may include at least one of the identification information items 11 through 14 in the registration acceptance message. The AMF may also use this identification information to indicate that the network supports each function, or that the UE's request has been accepted. Furthermore, if multiple identification information items are sent or received, two or more of these identification information items may be combined into one or more identification information items. The information indicating support for each function and the information indicating a request to use each function may be sent or received with the same identification information, or with different identification information.

[0256] If the network allows onboarding services, it may include one or more of the identifiers from the identifiers listed in sections 11 through 14 in the registration acceptance message. Furthermore, if the network allows registrations that are only available for onboarding services, it may include one or more of the identifiers from the identifiers listed in sections 11 through 14 in the registration acceptance message. Furthermore, if the network allows the use of the SNPN information provision procedure, it may include one or more of the identifiers from the identifiers listed in sections 11 through 14 in the registration acceptance message.

[0257] Furthermore, if the network supports onboarding services, it may include one or more of the identification information from items 11 through 14 in the registration acceptance message. Furthermore, if the network supports the procedure for providing SNPN information, it may include one or more of the identification information from items 11 through 14 in the registration acceptance message.

[0258] Furthermore, if the network is able to provide SNPN information, it may include one or more of the identifiers from the 11th to 14th sets of identifiers in the registration acceptance message. Furthermore, if the network is able to perform onboarding services, it may include one or more of the identifiers from the 11th to 14th sets of identifiers in the registration acceptance message. Furthermore, if the network is able to perform the procedure for providing SNPN information, it may include one or more of the identifiers from the 11th to 14th sets of identifiers in the registration acceptance message.

[0259] Furthermore, if the network supports registrations that are only available for onboarding services, it may include an eleventh identifier in the registration acceptance message. More specifically, if the network supports onboarding services, it may include an eleventh identifier in the registration acceptance message indicating that the network supports registrations that are only available for onboarding services.

[0260] Furthermore, if the network supports SNPN information provision procedures, it may include a 12th identifier in the registration acceptance message indicating the type of SNPN information provision procedure the network supports. More specifically, if the network supports SNPN information provision procedures via the user plane, it may include a 12th identifier in the registration acceptance message indicating support for SNPN information provision procedures via the user plane. Furthermore, if the network supports SNPN information provision procedures via the control plane, it may include a 12th identifier in the registration acceptance message indicating support for SNPN information provision procedures via the control plane.

[0261] Furthermore, if the network supports the procedure for providing SNPN information via the user plane, it may include a 13th identifier in the registration acceptance message. More specifically, if the network supports the procedure for providing SNPN information via the user plane, it may include a 13th identifier in the registration acceptance message indicating that it supports the procedure for providing SNPN information via the user plane.

[0262] Furthermore, if the network supports the procedure for providing SNPN information via the control plane, it may include a 14th identifier in the registration acceptance message. More specifically, if the network supports the procedure for providing SNPN information via the control plane, it may include a 14th identifier in the registration acceptance message indicating that it supports the procedure for providing SNPN information via the control plane.

[0263] Furthermore, if the network supports the procedure for providing SNPN information via the control plane, it may include a 14th identifier in the registration acceptance message indicating support for the procedure for providing SNPN information using a PCO or ePCO. Furthermore, if the network supports the procedure for providing SNPN information via the control plane, it may include a 14th identifier in the registration acceptance message indicating support for the procedure for providing SNPN information using URSP.

[0264] Furthermore, the network may indicate to the UE what the identification information included in the registration acceptance message represents by including one or more of the identification information from the 11th to 14th identification information in the registration acceptance message. Furthermore, the network may allow the UE what the identification information included in the registration acceptance message represents by including one or more of the identification information from the 11th to 14th identification information in the registration acceptance message.

[0265] Furthermore, AMF may select and decide which of the identification information items 11 through 14 to include in the registration acceptance message, based on each received identification information item, 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 AMF.

[0266] Furthermore, AMF may send an SM message (e.g., a PDU session establishment acceptance message) in the registration acceptance message, or send an SM message (e.g., a PDU session establishment acceptance message) together with the registration acceptance message. However, this method of transmission may be performed only if the registration request message includes an SM message (e.g., a PDU session establishment request message) and the fourth condition determination is true. Alternatively, this method of transmission may be performed only if the registration request message includes an SM message (e.g., a PDU session establishment request message) and the fourth condition determination is true. By performing such a transmission method, AMF can indicate in the registration procedure that the procedure for the SM has been accepted.

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

[0268] Furthermore, the AMF may include information in the registration acceptance message indicating that some of the UE's requests have been rejected, or may indicate the reason why some of the UE's requests have been rejected by sending information indicating that some of the UE's requests have been rejected. Furthermore, the UE may become aware of the reason why some of its requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. The reason for rejection may also be information indicating that the content of the identification information received by the AMF is not permitted.

[0269] The UE receives a registration acceptance message from the AMF via the 5G AN (gNB) (S808). Upon receiving the registration acceptance message, the UE can recognize that its request in the registration request message has been accepted, and can also recognize the content of the various identification information contained in the registration acceptance message.

[0270] Furthermore, the UE can send a registration completion message to the AMF via the 5G AN(gNB) as a response message to the registration acceptance message (S810). Here, the registration completion message is a NAS message sent and received on the N1 interface, but it is included in the RRC message sent and received between the UE and the 5G AN(gNB).

[0271] The AMF receives a registration completion message via 5G AN(gNB) (S810). Each device also completes the procedure in Figure 6(A) based on the sending and receiving of the registration acceptance message and / or registration completion message.

[0272] Next, we will explain the case where the first condition determination is false. In the procedure shown in Figure 6(B), the AMF sends a registration rejection message to the UE via the 5G AN(gNB) as a response message to the registration request message (S812). Here, the registration rejection message is a NAS message sent and received on the N1 interface, but it is included in the RRC message sent and received between the UE and the 5G AN(gNB).

[0273] Here, the AMF may include at least the 21st identification information in the registration rejection message, or may indicate that the UE's request has been rejected by including the 21st identification information, or may indicate the reason why the UE's request has been rejected.

[0274] The network may include the 21st identification information in the registration rejection message if it does not permit the onboarding service. Furthermore, the network may include the 21st identification information in the registration rejection message if it does not permit registration that is only available for the onboarding service. Furthermore, the network may include the 21st identification information in the registration rejection message if it does not permit the use of the SNPN information provision procedure.

[0275] Furthermore, if the network does not support onboarding services, it may include the 21st identification information in the registration rejection message. Furthermore, if the network does not support the procedure for providing SNPN information, it may include the 21st identification information in the registration rejection message.

[0276] Furthermore, if the network is unable to provide SNPN information, it may include a 21st identification information in the registration rejection message. Furthermore, if the network is unable to perform onboarding services, it may include a 21st identification information in the registration rejection message. Furthermore, if the network is unable to perform the procedure for providing SNPN information, it may include a 21st identification information in the registration rejection message.

[0277] Furthermore, if the network does not support registrations that are only available for onboarding services, it may include a 21st identifier in the registration rejection message. More specifically, if the network does not support registrations that are only available for onboarding services, it may include a 21st identifier in the registration rejection message indicating that the network does not support registrations that are only available for onboarding services.

[0278] Furthermore, if the network does not support onboarding services, it may include a 21st identifier indicating that it does not support onboarding services in the registration rejection message. Furthermore, if the network does not support the SNPN information provision procedure, it may include a 21st identifier indicating that it does not support the SNPN information provision procedure in the registration rejection message.

[0279] Furthermore, if the network does not support the procedure for providing the requested SNPN information, the network may include in the registration rejection message the 21st identification information indicating that it does not support the procedure for providing the requested SNPN information. More specifically, if the network does not support the procedure for providing SNPN information via the user plane, the network may include in the registration rejection message the 21st identification information indicating that it does not support the procedure for providing SNPN information via the user plane. Furthermore, if the network does not support the procedure for providing SNPN information via the control plane, the network may include in the registration rejection message the 21st identification information indicating that it does not support the procedure for providing SNPN information via the control plane.

[0280] Furthermore, by including the 21st identification information in the registration rejection message, the network may indicate to the UE the content indicated by the identification information included in the registration rejection message. Furthermore, by including the 21st identification information in the registration rejection message, the network may not permit the UE the content indicated by the identification information included in the registration rejection message.

[0281] Note that the AMF may select and determine whether to include at least the 21st 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 the context held by the AMF, etc.

[0282] Furthermore, by sending the registration rejection message, the AMF may indicate that the request of the UE by the registration request message has been rejected. Furthermore, the AMF may include in the registration rejection message information indicating the reason for the rejection, 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 the 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.

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

[0284] Note that the procedure of (B) in FIG. 6 may also be started when the procedure of (A) in FIG. 6 is aborted.

[0285] Each device completes the registration procedure based on the completion of the procedure of (A) or (B) in FIG. 6. Note that each device may transition to a state where the UE is registered with the network (RM_REGISTERED state) based on the completion of the procedure of (A) in FIG. 6, or may maintain a state where the UE is not registered with the network (RM_DEREGISTERED state) or transition to a state where the UE is not registered with the network based on the completion of the procedure of (B) in FIG. 6. Also, the transition of each device to each state may be performed based on the completion of the registration procedure or may be performed based on the establishment of a PDU session.

[0286] Furthermore, each device may perform processing based on the information transmitted and received in the registration procedure based on the completion of the registration procedure. For example, when information indicating that some requests of the UE have been rejected is transmitted and received, the reason for the rejection of the UE's request may be recognized. Furthermore, each device may perform this procedure again based on the reason for the rejection of the UE's request, or may perform a registration procedure for the core network_B or another cell.

[0287] Furthermore, based on the completion of the registration process, the UE may store the identification information received along with the registration acceptance message and / or registration rejection message, and may recognize the network's decision.

[0288] For example, if the UE receives one or more of the identification information from the 11th to 14th sets of identification information, it may recognize that onboarding services have been authorized. Furthermore, if the UE receives one or more of the identification information from the 11th to 14th sets of identification information, it may recognize that registration for onboarding services only has been authorized. Furthermore, if the UE receives one or more of the identification information from the 11th to 14th sets of identification information, it may recognize that the use of the SNPN information provision procedure has been authorized.

[0289] Furthermore, if the UE receives one or more of the identification information from the 11th to 14th identification information, it may recognize that the onboarding service is supported. Furthermore, if the UE receives one or more of the identification information from the 11th to 14th identification information, it may recognize that the SNPN information provision procedure is supported.

[0290] Furthermore, the UE may recognize that it is able to provide network SNPN information if it receives one or more of the identification information from the 11th to 14th sets of identification information. Furthermore, the UE may recognize that it is able to perform onboarding services if it receives one or more of the identification information from the 11th to 14th sets of identification information. Furthermore, the UE may recognize that it is able to perform the SNPN information provision procedure if it receives one or more of the identification information from the 11th to 14th sets of identification information.

[0291] Furthermore, if the UE receives the 11th identification, it may recognize that registrations that are only available for onboarding services are supported. More specifically, if the UE receives the 11th identification indicating that the network supports registrations that are only available for onboarding services, it may recognize that onboarding services are supported.

[0292] Furthermore, the UE may recognize that an SNPN information delivery procedure is supported if it receives a 12th identification indicating the type of SNPN information delivery procedure supported by the network. More specifically, the UE may recognize that an SNPN information delivery procedure via the user plane is supported if it receives a 12th identification indicating that an SNPN information delivery procedure via the user plane is supported. Furthermore, the UE may recognize that an SNPN information delivery procedure via the control plane is supported if it receives a 12th identification indicating that an SNPN information delivery procedure via the control plane is supported.

[0293] Furthermore, if the UE receives the 13th identification information, it may recognize that the procedure for providing SNPN information via the user plane is supported. More specifically, if the UE receives the 13th identification information indicating that the procedure for providing SNPN information via the user plane is supported, it may recognize that the procedure for providing SNPN information via the user plane is supported.

[0294] Furthermore, if the UE receives the 14th identification information, it may recognize that the procedure for providing SNPN information via the control plane is supported. More specifically, if the UE receives the 14th identification information indicating that the procedure for providing SNPN information via the control plane is supported, it may recognize that the procedure for providing SNPN information via the control plane is supported.

[0295] Furthermore, if the UE receives a 14th identification information indicating support for the SNPN information provision procedure using a PCO or ePCO, it may recognize that the SNPN information provision procedure via the control plane is supported, or that the SNPN information provision procedure using a PCO or ePCO is supported. Furthermore, if the UE receives a 14th identification information indicating support for the SNPN information provision procedure using URSP, it may recognize that the SNPN information provision procedure via the control plane is supported, or that the SNPN information provision procedure using URSP is supported.

[0296] Furthermore, if the UE receives one or more of the identification information from the 11th to 14th identification information, it may recognize the content indicated by the received identification information. Furthermore, if the UE receives one or more of the identification information from the 11th to 14th identification information, it may recognize that the content indicated by the identification information included in the registration acceptance message has been authorized.

[0297] Furthermore, the UE may recognize that the establishment of a PDU session for functions other than onboarding services is prohibited if it receives one or more of the identifiers from the 11th to 14th sets of identifiers. In other words, the UE may configure itself so that the establishment of a PDU session for functions other than onboarding services is prohibited if it receives one or more of the identifiers from the 11th to 14th sets of identifiers.

[0298] Furthermore, if the UE receives one or more of the identifiers from the 11th to 14th sets of identifiers, it may recognize that the establishment of PDU sessions other than those for the SNPN information provision procedure is prohibited. Furthermore, the UE may configure the system so that if it receives one or more of the identifiers from the 11th to 14th sets of identifiers, the establishment of PDU sessions other than those for the SNPN information provision procedure is prohibited. In other words, if the UE receives one or more of the identifiers from the 11th to 14th sets of identifiers, it may configure the system so that the PDU session establishment procedure for PDU sessions other than those for the SNPN information provision procedure is not initiated. Furthermore, if the UE receives one or more of the identifiers from the 11th to 14th sets of identifiers, it may configure the system so that the PDU session establishment procedure for purposes other than the SNPN information provision procedure is not initiated.

[0299] Furthermore, the period during which the establishment of PDU sessions other than those for providing SNPN information is prohibited may be managed by a timer. In other words, the UE may configure the system so that the establishment of PDU sessions other than those for providing SNPN information is not prohibited based on the expiration of the timer.

[0300] Furthermore, the period during which the establishment of PDU sessions other than those for providing SNPN information is prohibited may be until a new registration procedure and / or non-registration procedure is performed. In other words, the UE may configure the system so that the establishment of PDU sessions other than those for providing SNPN information is not prohibited based on the performance of a new registration procedure and / or non-registration procedure.

[0301] Furthermore, the period during which the establishment of PDU sessions other than those for providing SNPN information is prohibited may be until the power is turned off and / or until the USIM is removed. In other words, the UE may be configured so that the establishment of PDU sessions other than those for providing SNPN information is not prohibited based on the power being turned off and / or the USIM being removed.

[0302] Here, the PDU session other than the procedure for providing SNPN information may be a normal PDU session. More specifically, the PDU session other than the procedure for providing SNPN information may be a PDU session for transmitting and receiving normal user data.

[0303] Furthermore, the PDU session other than the procedure for providing SNPN information may be a PDU session other than for onboarding services. Furthermore, the PDU session other than the procedure for providing SNPN information may be a PDU session for functions other than onboarding services.

[0304] For example, the PDU session other than the procedure for providing SNPN information may be a PDU session for IMS services. Furthermore, the PDU session other than the procedure for providing SNPN information may be a PDU session for emergency services. Furthermore, the PDU session other than the procedure for providing SNPN information may be a PDU session for LADN. Furthermore, the PDU session other than the procedure for providing SNPN information may be a PDU session for CIoT.

[0305] In other words, the PDU session other than the procedure for providing SNPN information may be a PDU session for IMS services. Furthermore, the PDU session other than the procedure for providing SNPN information may be a PDU session for emergency services. Furthermore, the PDU session other than the procedure for providing SNPN information may be a PDU session for LADN. Furthermore, the PDU session other than the procedure for providing SNPN information may be a PDU session for CIoT.

[0306] Furthermore, a PDU session establishment procedure other than for the provision of SNPN information may be a PDU session establishment procedure for IMS services. Furthermore, a PDU session establishment procedure other than for the provision of SNPN information may be a PDU session establishment procedure for emergency services. Furthermore, a PDU session establishment procedure other than for the provision of SNPN information may be a PDU session establishment procedure for LADN. Furthermore, a PDU session establishment procedure other than for the provision of SNPN information may be a PDU session establishment procedure for CIoT.

[0307] Furthermore, in addition to the above, any PDU session other than the one established and used for the SNPN information provision procedure is acceptable, as long as it is a PDU session other than the one established and used for the SNPN information provision procedure.

[0308] Furthermore, if the UE receives a 12th identification, indicating the types of SNPN information delivery procedures supported by the network, it may recognize the types of authorized SNPN information delivery procedures. More specifically, if the UE receives a 12th identification, indicating support for SNPN information delivery procedures via the user plane, it may recognize that it is authorized to use SNPN information delivery procedures via the user plane. Furthermore, if the UE receives a 12th identification, indicating support for SNPN information delivery procedures via the control plane, it may recognize that it is authorized to use SNPN information delivery procedures via the control plane.

[0309] Furthermore, if the UE receives the 13th identification information, it may recognize that it is authorized to use the procedure for providing SNPN information via the user plane. More specifically, if the UE receives the 13th identification information indicating support for the procedure for providing SNPN information via the user plane, it may recognize that it is authorized to use the procedure for providing SNPN information via the user plane.

[0310] Furthermore, if the UE receives the 14th identification information, it may recognize that it is authorized to use the SNPN information provision procedure via the control plane. More specifically, if the UE receives the 14th identification information indicating support for the SNPN information provision procedure via the control plane, it may recognize that it is authorized to use the SNPN information provision procedure via the control plane.

[0311] Furthermore, if the UE receives one or more of the identifiers from the 11th to 14th sets of identifiers, it may decide whether or not to establish a PDU session. In other words, if the UE receives one or more of the identifiers from the 11th to 14th sets of identifiers, it may decide whether or not to initiate the PDU session establishment procedure to establish a PDU session.

[0312] For example, if the UE receives one or more of the 11th to 14th pieces of identification information, it may initiate a PDU session establishment procedure to establish a PDU session, or it may establish a PDU session. Furthermore, if the UE receives a 12th piece of identification information indicating support for the procedure of providing SNPN information via the user plane, it may initiate a PDU session establishment procedure to establish a PDU session, or it may establish a PDU session. Furthermore, if the UE receives a 13th piece of identification information, it may initiate a PDU session establishment procedure to establish a PDU session, or it may establish a PDU session.

[0313] Conversely, if the UE receives one or more of the 11th to 14th pieces of identification information, it may configure itself not to initiate the PDU session establishment procedure to establish a PDU session, or it may choose not to establish a PDU session. Furthermore, if the UE receives the 12th piece of identification information indicating support for the procedure of providing SNPN information via the control plane, it may configure itself not to initiate the PDU session establishment procedure to establish a PDU session, or it may choose not to establish a PDU session. Furthermore, if the UE receives the 14th piece of identification information, it may configure itself not to initiate the PDU session establishment procedure to establish a PDU session, or it may choose not to establish a PDU session.

[0314] Furthermore, if the UE receives a 14th identification indicating support for the SNPN information provision procedure using a PCO or ePCO, it may initiate the PDU session establishment procedure. Conversely, if the UE receives a 14th identification indicating support for the SNPN information provision procedure using URSP, it does not have to initiate the PDU session establishment procedure.

[0315] In other words, the UE may initiate the PDU session establishment procedure if the procedure for providing SNPN information using a PCO or ePCO is supported and / or permitted. Conversely, the UE does not have to initiate the PDU session establishment procedure if the procedure for providing SNPN information using URSP is supported and / or permitted.

[0316] Furthermore, if the UE implements the procedure for providing SNPN information using a PCO or ePCO, it may initiate the PDU session establishment procedure. Conversely, if the UE implements the procedure for providing SNPN information using URSP, it is not required to initiate the PDU session establishment procedure.

[0317] Here, the PDU session may be a PDU session used in the SNPN information provision procedure. In other words, the PDU session may be a PDU session for the SNPN information provision procedure. Furthermore, the PDU session may be a PDU session for the SNPN information provision procedure.

[0318] Furthermore, the PDU session may be a PDU session used in the onboarding service. In other words, the PDU session may be a PDU session for the onboarding service.

[0319] Furthermore, the PDU session establishment procedure may be a PDU session establishment procedure for the SNPN information provision procedure. Furthermore, the PDU session establishment procedure may be a PDU session establishment procedure for the SNPN information provision procedure. Furthermore, the PDU session establishment procedure may be a PDU session establishment procedure for establishing a PDU session for the SNPN information provision procedure. Furthermore, the PDU session establishment procedure may be a PDU session establishment procedure for the SNPN information provision procedure.

[0320] Furthermore, the PDU session establishment procedure may be a PDU session establishment procedure for onboarding services. Furthermore, the PDU session establishment procedure may be a PDU session establishment procedure for onboarding services. Furthermore, the PDU session establishment procedure may be a PDU session establishment procedure for establishing PDU sessions for onboarding services. Furthermore, the PDU session establishment procedure may be a PDU session establishment procedure for onboarding services.

[0321] Furthermore, the UE may start a timer if it receives one or more of the identification information from the 11th to 14th identification information. Furthermore, the UE may initiate a non-registration procedure based on the expiration of the timer.

[0322] Furthermore, the network may start a timer if it transmits one or more of the identification information from the 11th to 14th identification information. Furthermore, the network may initiate a non-registration procedure based on the expiration of the timer.

[0323] Here, the timer may be a timer indicating the expiration date for registrations that are only available for onboarding services. In other words, the timer may be a timer indicating the expiration date for the procedure to provide SNPN information.

[0324] Furthermore, the UE may configure the NAS signaling connection not to be released after the completion of this procedure. More specifically, if this procedure is a registration procedure for onboarding services, the UE may configure the NAS signaling connection not to be released after the completion of this procedure.

[0325] In other words, if this procedure is a registration procedure for onboarding services, the UE does not need to release the NAS signaling connection after the procedure is completed. Conversely, if this procedure is not a registration procedure for onboarding services, the UE may release the NAS signaling connection after the procedure is completed.

[0326] Furthermore, each device may be configured to prevent the NAS signaling connection from being released if this procedure is a registration procedure for onboarding services. More specifically, each device may be configured to prevent the NAS signaling connection from being released after this procedure is completed if this procedure is a registration procedure for onboarding services.

[0327] In other words, if this procedure is a registration procedure for onboarding services, each device does not need to release the NAS signaling connection after the procedure is completed. Conversely, if this procedure is not a registration procedure for onboarding services, each device may release the NAS signaling connection after the procedure is completed.

[0328] Furthermore, the UE may configure the NAS signaling connection not to be released if it sends a registration request message containing one or more of the identification information from the first to the 9. More specifically, the UE may configure the NAS signaling connection not to be released after the completion of this procedure if it sends a registration request message containing one or more of the identification information from the first to the 9.

[0329] In other words, if the UE includes one or more of the identification information from the first to the ninth set of identifiers in the registration request message, it does not need to release the NAS signaling connection after the completion of this procedure. Conversely, if the UE does not include one or more of the identification information from the first to the ninth set of identifiers in the registration request message, it may release the NAS signaling connection after the completion of this procedure.

[0330] Furthermore, the UE may configure the NAS signaling connection not to be released if it sends a registration request message containing a sixth identifier indicating a Follow-on request pending. More specifically, the UE may configure the NAS signaling connection not to be released after the completion of this procedure if it sends a registration request message containing a sixth identifier indicating a Follow-on request pending.

[0331] In other words, if the UE includes a sixth identifier indicating a follow-on request pending in the registration request message, it does not need to release the NAS signaling connection after the completion of this procedure. Conversely, if the UE includes a sixth identifier indicating no follow-on request pending in the registration request message, it may release the NAS signaling connection after the completion of this procedure.

[0332] Furthermore, the network may be configured so that the NAS signaling connection is not released if it receives a registration request message containing one or more of the identification information from the first to the ninth set of identification information. More specifically, the network may be configured so that the NAS signaling connection is not released after the completion of this procedure if it receives a registration request message containing one or more of the identification information from the first to the ninth set of identification information.

[0333] In other words, if one or more of the identification information from the first to the ninth is included in the registration request message, the network does not need to release the NAS signaling connection after the completion of this procedure. Conversely, if one or more of the identification information from the first to the ninth is not included in the registration request message, the network may release the NAS signaling connection after the completion of this procedure.

[0334] Furthermore, the network may be configured so that the NAS signaling connection is not released when it receives a registration request message containing a sixth identifier indicating a Follow-on request pending. More specifically, the network may be configured so that the NAS signaling connection is not released after the completion of this procedure when it receives a registration request message containing a sixth identifier indicating a Follow-on request pending.

[0335] In other words, if the registration request message contains a sixth identifier indicating a follow-on request pending, the network does not need to release the NAS signaling connection after the completion of this procedure. Conversely, if the registration request message contains a sixth identifier indicating no follow-on request pending, the network may release the NAS signaling connection after the completion of this procedure.

[0336] Furthermore, the UE may recognize that onboarding services are not permitted if it receives the 21st identification information. Furthermore, the UE may recognize that registrations that are only available for onboarding services are not permitted if it receives the 21st identification information. Furthermore, the UE may recognize that it is permitted to use the SNPN information provision procedure if it receives the 21st identification information.

[0337] Furthermore, if the UE receives the 21st identification information, it may recognize that the onboarding service is not supported. Furthermore, if the UE receives the 21st identification information, it may recognize that the procedure for providing SNPN information is not supported.

[0338] Furthermore, if the UE receives the 21st identification information, it may recognize that it is not possible to provide and / or obtain SNPN information. Furthermore, if the UE receives the 21st identification information, it may recognize that it is not possible to perform onboarding services. Furthermore, if the UE receives the 21st identification information, it may recognize that it is not possible to perform the SNPN information provision procedure.

[0339] Furthermore, if the UE receives the 21st identification, it may recognize that registrations that are only available for onboarding services are not supported. More specifically, if the UE receives the 21st identification indicating that the network does not support registrations that are only available for onboarding services, it may recognize that registrations that are only available for onboarding services are not supported.

[0340] Furthermore, if the UE receives the 21st identification information indicating that it does not support the onboarding service, it may recognize that the onboarding service is not supported. Furthermore, if the UE receives the 21st identification information indicating that it does not support the SNPN information provision procedure, it may recognize that the SNPN information provision procedure is not supported.

[0341] Furthermore, if the UE receives a 21st identification indicating that it does not support the requested SNPN information provision procedure, it may recognize that the requested SNPN information provision procedure is not supported. More specifically, if the UE receives a 21st identification indicating that it does not support the SNPN information provision procedure via the user plane, it may recognize that the SNPN information provision procedure via the user plane is not supported. Furthermore, if the UE receives a 21st identification indicating that it does not support the SNPN information provision procedure via the control plane, it may recognize that the SNPN information provision procedure via the control plane is not supported.

[0342] Furthermore, if the UE receives the 21st identification information, it may recognize the content indicated by the received identification information. Furthermore, if the UE receives the 21st identification information, it may recognize that the content indicated by the received identification information is not permitted.

[0343] Furthermore, if the UE receives the 21st identification information, it may add the network identification information to the first list. Furthermore, if the UE receives the 21st identification information, it may create the first list and add the network identification information to the created first list.

[0344] More specifically, if the UE receives a 21st identification indicating that it does not support the SNPN information provision procedure, it may add the network's identification to the first list. Furthermore, if the UE receives a 21st identification indicating that it does not support onboarding services, it may add the network's identification to the first list. Furthermore, if the UE receives a 21st identification indicating that the network does not support registrations that are only available for onboarding services, it may add the network's identification to the first list.

[0345] Here, the network identification information may be information that identifies the network on which the UE is currently located. More specifically, if the UE is located in a PLMN, the network identification information may be information that identifies the PLMN on which the UE is currently located. Conversely, if the UE is located in an SNPN, the network identification information may be information that identifies the SNPN on which the UE is currently located.

[0346] For example, if this procedure is performed on a first network, the network identification information may be information that identifies the first network. More specifically, if this procedure is performed on a first PLMN, the network identification information may be information that identifies the first PLMN. Furthermore, if this procedure is performed on a first SNPN, the network identification information may be information that identifies the first SNPN.

[0347] Furthermore, the period during which the first list is maintained may be a period managed by a timer. In other words, the UE may release or delete the first list based on the expiration of the timer.

[0348] Furthermore, the period during which the first list is maintained may be until the SNPN information provision procedure is completed. In other words, the UE may release or delete the first list based on the completion of the SNPN information provision procedure.

[0349] Furthermore, the period for which the first list is maintained may be until the onboarding service is completed. In other words, the UE may release or delete the first list based on the completion of the onboarding service.

[0350] Furthermore, the period during which the first list is maintained may be until the provision and / or acquisition of SNPN information is completed. In other words, the UE may release or delete the first list based on the completion of the acquisition of SNPN information.

[0351] Furthermore, the period during which the first list is maintained may be until the unregistration procedure and / or the second network selection is performed. In other words, the UE may release or delete the first list based on the performance of the unregistration procedure and / or the second network selection.

[0352] Furthermore, the period during which the first list is maintained may be until the power is turned off and / or until the USIM is removed. In other words, the UE may release or delete the first list based on the power being turned off and / or the USIM being removed.

[0353] Furthermore, if the UE receives the 21st identification information, it may re-execute the first network selection. Furthermore, if the UE receives the 21st identification information, it may re-execute the first network selection and select a network different from the network in which it is currently located. Furthermore, after completing the re-execution of the first network selection, the UE may initiate the registration process in the newly selected network.

[0354] More specifically, the UE may re-perform the first network selection if it receives a 21st identification criterion indicating that it does not support the SNPN information provision procedure. Furthermore, the UE may re-perform the first network selection if it receives a 21st identification criterion indicating that it does not support onboarding services. Furthermore, the UE may re-perform the first network selection if it receives a 21st identification criterion indicating that the network does not support registrations that are only available for onboarding services.

[0355] Furthermore, the UE may start a timer when it receives the 21st identification information, which may be a timer indicating the expiration date for managing the first list. In other words, the UE may release or delete the first list based on the expiration of the timer.

[0356] Furthermore, the timer may also be a timer indicating a deadline for prohibiting the registration procedure. In other words, the UE may initiate the registration procedure based on the expiration of the timer.

[0357] Furthermore, the actions performed upon receiving each piece of identification information may be based on the received identification information. For example, the action performed upon receiving the 11th piece of identification information may be based on the received 11th piece of identification information. Furthermore, the action performed upon receiving the 12th piece of identification information may be based on the received 12th piece of identification information. Furthermore, the action performed upon receiving the 13th piece of identification information may be based on the received 13th piece of identification information. Furthermore, the action performed upon receiving the 14th piece of identification information may be based on the received 14th piece of identification information. Furthermore, the action performed upon receiving the 21st piece of identification information may be based on the received 21st piece of identification information.

[0358] [4. First Embodiment] Next, a first embodiment will be described. Hereinafter, the first embodiment will be referred to as this embodiment. In this embodiment, the UE performs a registration procedure. The registration procedure in this embodiment may also be referred to as the first procedure. Furthermore, this embodiment may be an action performed during initial registration.

[0359] Furthermore, the UE may decide whether to perform the registration procedure based on the UE's configuration information, and / or information received from the network, and / or the UE's mode, and / or the UE's capability information.

[0360] Furthermore, in the first embodiment, the first network may be an onboarding network. The first network may also be a network used for onboarding services. The first network may also be an SNPN. The first network may also be a PLMN. The first network may also be an SNPN used for onboarding services. The first network may also be a PLMN used for onboarding services. The first network may also be an ON-SNPN (Onboarding SNPN). The first network may also be an ON-PLMN (Onboarding PLMN).

[0361] A first embodiment will be described with reference to Figure 6. When the UE performs initial registration for onboarding services in the first network, it may include third identification information in the registration request message.

[0362] The following behaviors may occur when the UE handles the 5GS mobile identity IE during initial registration. Furthermore, the following behaviors may occur when the UE handles the 5GS mobile identity IE during the registration process.

[0363] If the UE does not possess a valid 5G-GUTI or a SUCI other than the onboarding SUCI, and the UE has not initiated initial registration for onboarding services in the SNPN, the seventh identification information may include the eighth identification information.

[0364] Here, the seventh identification information may be information set before the registration procedure begins. Alternatively, the seventh identification information may be information set during the registration procedure.

[0365] Here, the eighth identification information may be information set before the registration procedure begins. Alternatively, the eighth identification information may be information set during the registration procedure.

[0366] Here, the seventh identification information may be determined to include the eighth identification information before commencing the registration procedure. Alternatively, the seventh identification information may be determined to include the eighth identification information during the registration procedure.

[0367] Here, the UE may perform an SNPN selection if it chooses an SNPN for onboarding services. Furthermore, the UE may select an SNPN that is authorized for onboarding if it chooses an SNPN for onboarding services. Also, the UE may select an SNPN that is authorized for onboarding if it performs onboarding services on an SNPN.

[0368] Here, the UE may perform a PLMN selection if it chooses a PLMN for onboarding services. Furthermore, the UE may select a PLMN that is authorized for onboarding if it chooses a PLMN for onboarding services. Also, the UE may select a PLMN that is authorized for onboarding if it performs onboarding services on a PLMN.

[0369] Furthermore, the UE may select an SNMP as the first network in the SNMP selection process. Specifically, the UE may select an SNMP as the first network in the SNMP selection process and send a registration request message to the first network.

[0370] Furthermore, the UE may select PLMN as the first network in the PLMN selection process. Specifically, the UE may select PLMN as the first network in the PLMN selection process and send a registration request message to the first network.

[0371] The UE may decide whether to select SNPN or PLMN as the first network based on pre-configured information.

[0372] Furthermore, the UE may decide whether to select SNPN or PLMN as the first network based on its default UE credentials.

[0373] Furthermore, the UE may decide whether to select SNPN or PLMN as the first network based on the default PLMN credentials. Also, if the UE has a USIM configured with default PLMN credentials, it may decide whether to select SNPN or PLMN as the first network.

[0374] Furthermore, the UE may determine whether the first network is an SNMP or a PLMN based on pre-configured information. In other words, if the UE has pre-configured information, it may determine whether the first network is an SNMP or a PLMN.

[0375] Furthermore, the UE may determine that the first network is an SNMP based on pre-configured information indicating the SNMP. In other words, the UE may determine that the first network is an SNMP if information indicating the SNMP is pre-configured.

[0376] Furthermore, the UE may determine that the first network is an SNMP based on information indicating that a pre-configured SNMP is available. In other words, the UE may determine that the first network is an SNMP if information indicating that an SNMP is available is pre-configured.

[0377] Furthermore, the UE may determine that the first network is an SNMP based on information indicating that a pre-configured PLMN is unavailable. In other words, the UE may determine that the first network is an SNMP if information indicating that a PLMN is unavailable is pre-configured.

[0378] Furthermore, the UE may determine that the first network is a PLMN based on pre-configured information indicating a PLMN. In other words, the UE may determine that the first network is a PLMN if information indicating a PLMN is pre-configured.

[0379] Furthermore, the UE may determine that the first network is a PLMN based on information indicating that a pre-configured PLMN is available. In other words, the UE may determine that the first network is a PLMN if information indicating that a PLMN is available is pre-configured.

[0380] Furthermore, the UE may determine that the first network is a PLMN based on information indicating that a pre-configured SNMP is unavailable. In other words, the UE may determine that the first network is a PLMN if information indicating that an SNMP is unavailable is pre-configured.

[0381] Here, the information that has been set up in advance may be called pre-configured information.

[0382] Here, if the UE performs an SNMP selection, it may perform a registration procedure for the onboarding service in SNMP access operation mode. In other words, if the UE performs an SNMP selection, it may send a registration request message to the first network in SNMP access operation mode.

[0383] Here, if the UE performs PLMN selection, it may perform the registration procedure for the onboarding service in a mode other than SNPN access operation mode. In other words, if PLMN selection is performed, the UE may send a registration request message to the first network in a mode other than SNPN access operation mode.

[0384] Here, the UE may operate in SNPN access operation mode when performing SNPN selection. Specifically, when the UE performs SNPN selection, it may operate in SNPN access operation mode and perform the registration procedure for onboarding services.

[0385] Here, the UE may operate in PLMN access operation mode when performing PLMN selection. Specifically, the UE may operate in PLMN access operation mode when performing PLMN selection and perform the registration procedure for onboarding services.

[0386] Here, the registration procedure for the onboarding service may be a registration procedure performed in the first network. Furthermore, the registration procedure for the onboarding service may be a registration procedure for the UE to perform registration that is only usable for the onboarding service. Furthermore, the registration procedure for the onboarding service may be a registration procedure for performing registration that enables the onboarding service to be performed. Furthermore, the registration procedure for the onboarding service may be a registration procedure for performing registration that enables the provision of SNPN information.

[0387] In other words, if the registration process for the onboarding service is successfully completed, each device may only be capable of using the onboarding service. Furthermore, if the registration process for the onboarding service is successfully completed, each device may be capable of performing the onboarding service. Furthermore, if the registration process for the onboarding service is successfully completed, each device may be capable of performing the procedure for providing SNPN information.

[0388] Here, the network for onboarding services may be the network through which each device performs onboarding services. In other words, the network for onboarding services may be the network through which each device performs the procedure for providing SNPN information. Furthermore, the network for onboarding services may be the onboarding network itself.

[0389] Furthermore, the network for onboarding services may be a network in which the use of services other than onboarding services is restricted. Alternatively, the network for onboarding services may be a network in which only onboarding services are available. The network for onboarding services may be implemented by SNPN or by PLMN.

[0390] If the execution of a procedure during the first procedure fails, each device does not need to perform the subsequent procedures. In this case, each device may perform processing based on the information contained in the control message based on the failure of the procedure execution, or it may complete the first procedure by performing processing based on the information contained in the control message.

[0391] Specifically, if a registration rejection message is sent or received during the registration process, the UE may perform actions based on the information contained in the registration rejection message, or may complete the first procedure by performing actions based on the information contained in the registration rejection message.

[0392] Furthermore, if the execution of a procedure during the first procedure fails, each device may restart the first procedure from the beginning. In this case, each device may perform processing based on the information contained in the control message based on the failure of the procedure execution, or it may perform processing based on the information contained in the control message and then restart the first procedure from the beginning.

[0393] Specifically, if a registration rejection message is sent or received during the registration process, the UE may perform processing based on the information contained in the registration rejection message, or, after performing processing based on the information contained in the registration rejection message, may re-execute the first network selection.

[0394] Furthermore, the UE may configure the system to prevent movement to the EPS once the registration process for the onboarding service is complete. Additionally, the UE may set information in the S1 mode capability information indicating that S1 mode is not supported once the registration process for the onboarding service is complete.

[0395] Furthermore, the UE may configure the system so that it cannot move to the EPS once registration that only allows onboarding services is complete. Additionally, the UE may set information in the S1 mode capability information indicating that S1 mode is not supported once registration that only allows onboarding services is complete.

[0396] Furthermore, the UE may configure the system to prevent movement to the EPS if it has registered with the network for onboarding services. Additionally, the UE may configure the S1 mode capability information to indicate that S1 mode is not supported if it has registered with the network for onboarding services.

[0397] [5. Variant] The program that operates in the device according to the present invention may be a program that controls the Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of the embodiment according to the present invention. The program or the information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, a Hard Disk Drive (HDD), or other storage system.

[0398] Furthermore, a program for realizing the functions of the embodiments related to the present invention may be recorded on a computer-readable recording medium. This can also be realized by loading the program recorded on this recording medium into a computer system and executing it. The term "computer system" here refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other computer-readable recording medium.

[0399] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, such as an integrated circuit or a combination of integrated circuits. An 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, a conventional processor, controller, microcontroller, or state machine. The aforementioned electrical circuit may consist of digital circuits or analog circuits. Also, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, one or more aspects of the present invention may use new integrated circuits based on such technologies.

[0400] It should be noted that the present invention is not limited to the embodiments described above. Although one example of a device is described in the embodiments, the present invention is not limited thereto 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 and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0401] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included. [Explanation of Symbols]

[0402] 1. Mobile communication systems 5 PDN_A 6 DN_A 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

Claims

[Claim 1] User Equipment (UE), The aforementioned UE comprises a transmitting / receiving unit and a control unit, If the aforementioned UE does not possess a valid 5G-GUTI (5G Globally Unique Temporary Identifier) ​​or a SUCI other than an onboarding SUCI (Subscription Concealed Identifier), Furthermore, if the UE has not initiated initial registration for the onboarding service in SNPN, The control unit, The 5GS mobile identity IE includes PEI (Permanent Equipment Identifier). I chose PLMN for the onboarding service. It operates in PLMN access operation mode. Complete the registration process for the onboarding service. The aforementioned PEI consists of a PEI type indicating the IMEI (International Mobile Station Equipment Identity) and the IMEI itself. A UE characterized by the following:

Images