UE (User Equipment) and communication control method

Abstract

In a 5G system (5GS), user equipment (UE) needs to be connected to and registered with a non-public network (NPN), but when the UE does not hold information regarding the NPN, the control process of the UE and the control process of a control device in a core network are unclear. The present disclosure provides a control process and a communication means for providing information regarding a non-public network (NPN) to user equipment (UE), when the UE needs to be connected to and registered with the NPN in a 5G system (5GS). The present disclosure also provides a control process and a communication means for establishing and managing a session used for providing information regarding the NPN in the 5GS.

Description

[Technical Field]

[0001] The present disclosure relates to a UE (User Equipment) and a communication control method. This application claims priority to Japanese Patent Application No. 2020-193264, filed in Japan on November 20, 2020, the contents of which are incorporated herein by reference. [Background technology]

[0002] The 3GPP (3rd Generation Partnership Project) has begun studying the system architecture of the 5GS (5G System), the next-generation, or fifth-generation (5G), mobile communication system, and is discussing support for new procedures and new functions (see Non-Patent Document 1, Non-Patent Document 2, Non-Patent Document 3, and Non-Patent Document 4).

[0003] For example, requirements include the optimization and diversification of communication procedures to support continuous mobile communication services in response to a wide variety of services, and the optimization of system architecture to match the optimization and diversification of communication procedures. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 23.501 v16.6.0 (2020-09); Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16) [Non-patent document 2] 3GPP TS 23.502 v16.6.0 (2020-09); Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16) [Non-patent document 3] 3GPP TS 24.501 v17.0.0 (2020-09); Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17) [Non-patent document 4] 3GPP TR 23.700-07 v1.0.0 (2020-09); Technical Specification Group Services and System Aspects; Study on enhanced support of non-public networks (Release 17) Summary of the Invention [Problem to be solved by the invention]

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

[0006] However, it is not clear what the core network control device and UE processes should be when a UE (User Equipment) needs to connect to and register with an NPN but the UE does not have information about the NPN.

[0007] One aspect of the present invention has been made in view of the above circumstances, and its purpose is to provide a communication means for providing NPN information to a UE when connection and registration of the UE to an NPN is required in 5GS, and a method for realizing processing by a core network control device and processing by the UE. Another purpose is to provide a communication means for establishing and managing a session used to provide NPN information in 5GS, and a method for realizing processing by a core network control device and processing by the UE. [Means for solving the problem]

[0008] One embodiment of the present invention provides a UE (User Equipment; terminal device) comprising a transceiver unit and a control unit, wherein the UE executes a PDU (Protocol Data Unit) session establishment procedure after completing a registration procedure for an onboarding service, and in the PDU session establishment procedure, the transceiver unit receives a PDU session establishment acceptance message from a control device, the control unit establishes a PDU session for the onboarding service, and when the UE moves to an EPS (Evolved Packet System), the control unit releases the PDU session.

[0009] Another aspect of the present invention is a communication control method for a UE (User Equipment; terminal device), which includes a step of performing a PDU (Protocol Data Unit) session establishment procedure after completion of a registration procedure for an onboarding service, wherein the UE receives a PDU session establishment acceptance message from a control device during the PDU session establishment procedure and establishes a PDU session for the onboarding service, and the UE releases the PDU session when moving to an EPS (Evolved Packet System). [Effects of the Invention]

[0010] According to one aspect of the present invention, in 5GS, even if the UE does not have information about the NPN, it is possible to realize a communication means, a control process of a control device in a core network, and a control process of the UE to enable the UE to connect to and register with the NPN. Furthermore, it is also possible to realize a communication means, a control process of a control device in a core network, and a control process of the UE to establish and manage a session used to provide information about the NPN. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an outline of a mobile communication system (EPS / 5GS). [Figure 2] FIG. 1 is a diagram illustrating the detailed configuration of a mobile communication system (EPS / 5GS). [Figure 3] FIG. 1 is a diagram illustrating the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Figure 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 10 is a diagram illustrating a first procedure. [Figure 7] FIG. 10 is a diagram illustrating a registration procedure. [Figure 8] A diagram explaining the PDU session establishment procedure. [Figure 9] FIG. 1 illustrates a network-initiated deregistration procedure. [Figure 10] FIG. 10 is a diagram illustrating a UE-initiated deregistration procedure. DETAILED DESCRIPTION OF THE INVENTION

[0012] The best mode for carrying out one aspect of the present invention will be described with reference to the drawings.

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

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

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

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

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

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

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

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

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

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

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

[0024] Furthermore, the RAN may be referred to as an access network, and conversely, the access network may be referred to as the RAN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0077] The PCF has a function to provide policy rules.

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

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

[0080] The HSS is connected to the MME and / or SCEF and has a function of managing subscriber information. The subscriber information of the HSS is referred to, for example, when controlling access to the MME. Furthermore, the HSS may be connected to a location management device different from the MME.

[0081] The SCEF is connected to the DN and / or PDN, the MME, and the HSS, and has functions such as a relay device that transfers user data as a gateway connecting the DN and / or PDN with the core network _A. The SCEF may also be a gateway for non-IP communication. Furthermore, the SCEF may have a function to convert between non-IP communication and IP communication. Furthermore, multiple such gateways may be located in the core network _A. The SCEF may be configured outside or inside the core network.

[0082] [3. Explanation of terms, identification information, and procedures used in each embodiment] At least one term, identification information, and procedure used in each embodiment will be explained in advance.

[0083] [3.1. Explanation of terms and identification information used in each embodiment] First, highly specialized terms used in each embodiment and identification information used in the procedures will be explained in advance.

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

[0085] Furthermore, the network may refer to a PLMN (Public Land Mobile Network) or an NPN (later described). Furthermore, when it is expressed that the UE performs network selection, it may mean that the UE performs PLMN selection or that the UE performs SNPN selection.

[0086] Also, the registered PLMN refers to the PLMN to which the UE is registered.

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

[0088] Furthermore, an SM (Session Management) message (also referred to as an NAS (Non-Access-Stratum) SM message) may be an NAS message used in a procedure for SM, and may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240. Furthermore, the SM message may include a PDU session establishment request message, a PDU session establishment acceptance message, a PDU session completion message, a PDU session rejection message, a PDU session change request message, a PDU session change acceptance message, a PDU session change response message, etc. Furthermore, the procedure for SM may include a PDU session establishment procedure.

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

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

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

[0092] In addition, the dual registration mode is a mode in which UE_A10 maintains the registration state independently in the 5GMM state and the EMM state when N1 mode and S1 mode are available. In addition, in the dual registration mode, UE_A10 may be registered with the network only in N1 mode (i.e., registered only in 5GC), may be registered with the network only in S1 mode (registered only in EPC), or may be registered with the network in both N1 mode and S1 mode (registered in both 5GC and EPC).

[0093] In addition, to interwork between 5GS and EPC, a UE that supports both 5GC and EPC NAS can operate in single registration mode or dual registration mode.

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

[0095] In addition, the N1 mode is a mode in which the UE_A10 is permitted to access the 5GC via the 5G access network. In other words, the N1 mode may be a mode in which message transmission and reception using the N1 interface are performed.

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

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

[0098] Furthermore, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between a DN that provides a PDU connectivity service and a UE, but it may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data to and from a DN by establishing a PDU session via an access network _B and a core network _B. Here, this external gateway may be a UPF, SCEF, or the like. The UE can transmit and receive user data to and from a device such as an application server located in the DN using the PDU session.

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

[0100] Furthermore, the DNN (Data Network Name) may be identification information for identifying a core network and / or an external network such as a DN. Furthermore, the DNN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 that connects the core network B190. Furthermore, the DNN may be equivalent to an APN (Access Point Name).

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

[0102] A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. UEs and / or networks can support network slices (NW slices; NS) in 5GS.

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

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

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

[0106] Furthermore, SSC (Session and Service Continuity) mode indicates the session service continuity mode supported by the system and / or each device in a 5G system (5GS). More specifically, it may be a mode indicating the type of session service continuity supported by the PDU session established between UE_A10 and UPF. Note that the SSC mode may also be a mode indicating the type of session service continuity set for each PDU session. Furthermore, the SSC mode may be composed of three modes: SSC mode 1, SSC mode 2, and SSC mode 3. Note that the SSC mode associated with a PDU session does not need to be changed while the PDU session is ongoing.

[0107] An RRC (Radio Resource Control) connection is a connection established between a UE and a base station device in an access network. More specifically, an RRC connection is a connection established at a Uu reference point between a UE and a base station device in an access network. An RRC connection may be configured with a radio bearer. An RRC connection may also be a connection established in 3GPP access. An RRC connection may also be a connection established in an RRC layer below the NAS layer. An RRC connection may also be a connection that is established and / or released by transmitting and receiving an RRC message in the RRC layer. An RRC connection may also be a connection that is suspended by transmitting and receiving an RRC message in the RRC layer.

[0108] Furthermore, the 5GMM-CONNECTED mode with RRC inactive indication is a state indicating that the state of the NAS layer is connected even though the RRC layer is in an inactive state. In other words, the 5GMM-CONNECTED mode with RRC inactive indication may be a state in which the radio bearer is released while maintaining the NAS signaling connection and / or the context of the NAS signaling connection.

[0109] Furthermore, the 5GMM-CONNECTED mode with RRC inactive indication may be a state in which the RRC connection is suspended. More specifically, the 5GMM-CONNECTED mode with RRC inactive indication may be a state in which the state of the NAS layer is connected but the RRC connection is suspended. In other words, the 5GMM-CONNECTED mode with RRC inactive indication may be a state in which the RRC connection is suspended while maintaining the NAS signaling connection and / or the context of the NAS signaling connection.

[0110] Here, the UE may transition from 5GMM-CONNECTED mode to 5GMM-CONNECTED mode with RRC inactive indication based on reception of information indicating that the RRC connection has been suspended from a lower layer. Furthermore, the UE may transition only the state for 3GPP access from 5GMM-CONNECTED mode to 5GMM-CONNECTED mode with RRC inactive indication based on reception of information indicating that the RRC connection has been suspended from a lower layer. Note that the information indicating that the RRC connection has been suspended may be an indication indicating that the RRC connection has been suspended.

[0111] Also, support of 5GMM-CONNECTED mode with RRC inactive indication may mean that maintaining the NAS layer state in a connected state is supported even when a notification indicating that the RRC layer has been deactivated is received from a lower layer. Furthermore, use of 5GMM-CONNECTED mode with RRC inactive indication may mean that maintaining the NAS layer state in a connected state even when a notification indicating that the RRC layer has been deactivated is received from a lower layer.

[0112] Furthermore, the PDU session with suspended user-plane resources is a PDU session in which user plane resources are established or re-established and a radio bearer is suspended. Here, the timing at which the radio bearer is suspended may be the timing at which the UE transitions to 5GMM-CONNECTED mode with RRC inactive indication. Furthermore, the radio bearer may be a data radio bearer.

[0113] A Non-Access Stratum (NAS) signaling connection is a connection between a UE and a core network. More specifically, a NAS signaling connection is an N1 mode connection between a UE and an AMF.

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

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

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

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

[0118] The NAS signaling connection may also be expressed as a NAS signaling connection. Furthermore, the NAS signaling connection may also be expressed as an N1 NAS signaling connection.

[0119] An Always-on PDU session is a PDU session for which user plane resources must be activated every time a UE transitions from 5GMM-IDLE state to 5GMM-CONNECTED state. Based on an instruction from a higher layer, the UE can request the core network and / or a core network device to establish a PDU session as an Always-on PDU session. The core network and / or a core network device determines whether a PDU session can be established as an Always-on PDU session. Here, the 5GMM-IDLE state may be a CM-IDLE state. Furthermore, the 5GMM-CONNECTED state may be a CM-CONNECTED state. Furthermore, the core network device that determines whether a PDU session can be established as an Always-on PDU session may be an SMF.

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

[0121] The TA list is a list that includes one or more TAs that the network has assigned to UE_A10. Note that UE_A10 may be able to move without performing a tracking area update procedure while moving within one or more TAs included in the TA list. In other words, UE_A10 may use the TA list as a group of information indicating areas that UE_A10 can move into without performing a tracking area update procedure. Note that the TA list may also be expressed as a TAI list consisting of one or more TAIs (Tracking area identities), and hereinafter, the TAI list may refer to the TA list.

[0122] An LADN (Local Area Data Network) is a DN that a UE can connect to only in a specific location and provides connectivity to a specific DNN (i.e., an LADN DNN). An LADN may be a DN that can be connected to in a specific location by using a PDU session associated with a specific DNN. Furthermore, an LADN may be a DN that can be connected to in a specific location by using a PDU session associated with a combination of a specific DNN and a specific S-NSSAI.

[0123] A PDU session for an LADN is a PDU session associated with a DNN associated with the LADN. The PDU session for an LADN may be a PDU session established for the LADN. In other words, it may be a PDU session established between a UE and an LADN, or a PDU session used for user data communication between a UE and an LADN. The PDU session for an LADN may be a PDU session that can be established only in an LADN service area. In other words, a UE may be able to establish a PDU session for an LADN by using a specific DNN in a specific location. In other words, a UE may be able to establish a PDU session for an LADN by using a combination of a specific DNN and a specific S-NSSAI in a specific location.

[0124] A Non-Public Network (NPN) is a private network that is not intended for general use, but is used by specific users for specific purposes, such as for private use by companies. There are two types of NPNs: Stand-alone Non-Public Networks (SNPNs) and Public network integrated NPNs. Note that when referring to NPNs below, it can refer to both SNPNs and Public network integrated NPNs.

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

[0126] NID (Network Identifier) ​​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 may be globally unique.

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

[0128] Furthermore, the public network integrated NPN may be realized using a DN. Specifically, the public network integrated NPN may be a network that can be realized 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 a CAG ID.

[0129] A CAG (Closed Access Groups) ID is information that identifies a group of subscribers that are permitted to connect to one or more cells associated with the CAG. A CAG may be a group identified by a CAG ID. A CAG is a group used when implementing a public network integrated NPN in a network slice. A CAG may be used to prevent UEs that are not permitted to access a network slice allocated for the NPN from attempting to access the network slice. Furthermore, a CAG ID is unique information within a PLMN.

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

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

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

[0133] Additionally, an equivalent SNPN may be a PLMN that is treated the same as any SNPN. For example, an equivalent SNPN may be one or more PLMNs that are treated the same as the registration SNPN.

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

[0135] Default UE credentials are information that a UE holds before the actual onboarding procedure. The default UE credentials may be information used to uniquely identify a UE. Furthermore, the default UE credentials may be information used to verify the security of the UE.

[0136] A Default Credential Server (DCS) is a server that can authenticate a UE using a default UE certificate. The default certificate server may be a server that can provide authentication of a UE using a default UE certificate to other devices or entities.

[0137] NPN credentials are information used by a UE for authentication to access the NPN. The NPN credentials may be a 3GPP certificate or a non-3GPP certificate.

[0138] An onboarding network (ON) is a network that provides initial registration and / or access to a UE for onboarding. In other words, a UE may register with and / or access the onboarding network to perform onboarding.

[0139] Here, the onboarding network may be realized by a PLMN. Furthermore, the onboarding network may be realized by an SNPN.

[0140] A provisioning server is a server that provides subscription data to an authenticated and approved UE, and may be a server that provides subscription data and other configuration information to an authenticated and approved UE.

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

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

[0143] UE onboarding is the provision of information to the UE and entities within the network that is necessary for the UE to gain access and connectivity to an authorized NPN.

[0144] In other words, UE onboarding may involve providing information to a UE or an entity within the network, where the information may be information required by the UE to establish access or connectivity to an NPN, and the access or connectivity to the NPN may be authorized. Furthermore, the information may be SNPN information.

[0145] In other words, when a UE attempts to access or establish connectivity to an NPN, the UE may perform UE onboarding to obtain information required for accessing or establishing connectivity to the NPN. Furthermore, the UE may perform a procedure for accessing or establishing connectivity to the NPN after performing UE onboarding.

[0146] Note that UE onboarding may also be referred to as a UE onboarding procedure, an onboarding service, or simply as onboarding.

[0147] In other words, when the term "UE onboarding procedure" is used, it may mean UE onboarding. Furthermore, when the term "onboarding service" is used, it may mean UE onboarding. Furthermore, when the term "onboarding" is used, it may mean UE onboarding.

[0148] The SNPN information is information required for a UE to access and establish connectivity to an SNPN. The SNPN information may be information used when a UE performs a procedure for accessing and establishing connectivity to an SNPN. Furthermore, the SNPN information may be subscription data and / or other configuration information. Furthermore, the SNPN information may be an NPN certificate. Furthermore, the SNPN information may be referred to as NPN information.

[0149] In addition, the UE may obtain the SNPN information from the network during UE onboarding. More specifically, the UE may obtain the SNPN information from a provisioning server or a subscription owner during UE onboarding.

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

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

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

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

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

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

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

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

[0158] 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, or in other words, a procedure in which the UE obtains SNPN information from the network via the user plane.

[0159] Specifically, the procedure for providing SNPN information via the user plane is a procedure in which, after a PDU session is established between the UE and the network, the network provides SNPN information to the UE using the PDU session.

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

[0161] In addition, the PDU session used to provide the SNPN information may be a PDU session used for providing the SNPN information. In other words, the PDU session used to provide the SNPN information may be a PDU session for providing the SNPN information.

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

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

[0164] Here, when the procedure for providing SNPN information via the control plane is used, the SNPN information may be provided to the UE by including the SNPN information in a UE Route Selection Policy (URSP) and transmitting the SNPN information to the UE. Furthermore, when the procedure for providing SNPN information via the control plane is used, the SNPN information may be provided to the UE by including the SNPN information in Protocol Configuration Options (PCO) or Extended Protocol Configuration Options (ePCO) and transmitting the SNPN information to the UE.

[0165] In other words, when the procedure for providing SNPN information via the control plane is used, the UE may acquire the SNPN information by receiving the SNPN information included in the URSP from the network.When the procedure for providing SNPN information via the control plane is used, the UE may acquire the SNPN information by receiving the SNPN information included in the PCO or ePCO from the network.

[0166] The URSP may be an information element included in a MANAGE UE POLICY COMMAND message. The PCO may be an information element included in a Session Management message (SM message). The ePCO may be an information element included in a Session Management message (SM message).

[0167] Furthermore, the UE policy management command message may be a control message transmitted and received between the PCF and the UE. Furthermore, the SM message may be a control message transmitted and received between the UE and the SMF. Furthermore, the SM message may include a PDU session establishment accept message, a PDU session modification command message, a PDU session release command message, etc.

[0168] The first list is a list including information identifying one or more networks for which the onboarding service is unavailable. The first list may be a list including information identifying one or more networks. In other words, the first list may be a set configured by information identifying one or more networks.

[0169] Here, the network identified by the network identification information may be a network in which the onboarding service is unavailable. Further, the network identified by the network identification information may be a network that does not support the onboarding service. Further, the network identified by the network identification information may be a Public Land Mobile Network (PLMN) or a Stand-alone Non-Public Network (SNPN).

[0170] Furthermore, the information identifying a network may be information identifying a PLMN or information identifying an SNPN. In other words, the information identifying a network may be a PLMN ID and / or an SNPN ID. Furthermore, the information identifying a network may be a PLMN identity and / or an SNPN identity.

[0171] Furthermore, the first list may be managed until the UE is provided with SNPN information. In other words, the first list may be released based on the provision of the SNPN information to the UE. Furthermore, the first list may be released based on the execution of a de-registration procedure.

[0172] Additionally, the first list may be released based on a power-off and / or SIM removal. Additionally, the first list may be released based on the expiration of a timer.

[0173] Furthermore, the first list may be managed for each access. Specifically, the first list may be managed separately as a list for 3GPP access and a list for non-3GPP access.

[0174] In addition, the PDU session for the onboarding service is a PDU session established for the onboarding service. The PDU session for the onboarding service may be a PDU session established to perform the SNPN information provision procedure.

[0175] Furthermore, the PDU session for the onboarding service may be a PDU session used in the onboarding service. Furthermore, the PDU session for the onboarding service may be a PDU session used in the SNPN information provision procedure.

[0176] Furthermore, the PDU session for the onboarding service may be a PDU session established in a network for the onboarding service, where the network for onboarding may be an SNPN or a PLMN.

[0177] Furthermore, the PDU session for the onboarding service may be a PDU session that is established when the registration procedure for the onboarding service is complete. Furthermore, the PDU session for the onboarding service may be a PDU session that is established when the registration that can only be used for the onboarding service is complete.

[0178] Furthermore, each device may establish a PDU session for the onboarding service to perform the onboarding service. Further, each device may establish a PDU session for the onboarding service to perform a procedure for providing SNPN information.

[0179] Furthermore, each device may perform an onboarding service using the PDU session for the onboarding service. Furthermore, each device may perform a procedure for providing SNPN information using the PDU session for the onboarding service.

[0180] Here, the PDU session for the onboarding service may be realized by an Always-on PDU session, in other words, the PDU session for the onboarding service may be established as an Always-on PDU session.

[0181] Furthermore, establishing a PDU session for an onboarding service may refer to establishing an Always-on PDU session, in other words, establishing an Always-on PDU session may refer to establishing a PDU session that handles a QoS flow for the onboarding service.

[0182] The first identification information is information indicating only the onboarding service. Furthermore, the first identification information may be information indicating a request for only the onboarding service. Furthermore, the first identification information may be information indicating a request for registration that can be used only for the onboarding service. Note that the first identification information may be realized by a request type in which the onboarding service is set.

[0183] Furthermore, the first identification information may be information indicating whether the UE supports registration that allows only the onboarding service to be used. The first identification information may be information indicating that the UE supports registration that allows only the onboarding service to be used, or may be information indicating that the UE does not support registration that allows only the onboarding service to be used. Furthermore, the first identification information may be realized by a bit indicating whether the UE supports registration that allows only the onboarding service to be used. Here, the bit indicating whether the UE supports registration that allows only the onboarding service to be used may be a bit constituting a 5GMM capability information element that indicates the UE's capabilities in 5G.

[0184] Furthermore, the first identification information may be a default UE certificate. Furthermore, the first identification information may be information identifying the UE. Furthermore, the first identification information may be information identifying a default certificate server. Furthermore, the first identification information may be information identifying a network to which the UE wishes to connect.

[0185] Furthermore, the first identification information may be information selected and determined based on the UE configuration, and / or the UE status, and / or user policy, and / or application requirements.

[0186] The second identification information is information indicating a type of SNPN information provision procedure supported by the UE. The second identification information may be information indicating that the UE supports acquisition of SNPN information via a user plane (UP), or may be information indicating that the UE supports acquisition of SNPN information via a control plane (CP). Furthermore, the second identification information may be realized by a bit indicating a type of SNPN information provision procedure supported by the UE. Here, the bit indicating the type of SNPN information provision procedure supported by the UE may be a bit constituting a 5GMM capability information element indicating the UE's capabilities in 5G.

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

[0188] Furthermore, the second identification information may be information selected and determined based on the UE configuration, and / or the UE status, and / or user policy, and / or application requirements.

[0189] The third identification information is information indicating whether the UE supports acquisition of SNPN information via a user plane (UP). The third identification information may be information indicating that the UE supports acquisition of SNPN information via a user plane, or may be information indicating that the UE does not support acquisition of SNPN information via a user plane. Furthermore, the third identification information may be realized by a bit indicating whether the UE supports acquisition of SNPN information via a user plane. Here, the bit indicating whether the UE supports acquisition of SNPN information via a user plane may be a bit constituting a 5GMM capability information element indicating the UE's capabilities in 5G.

[0190] Furthermore, the third identification information may be information selected and determined based on the UE configuration, and / or the UE status, and / or user policy, and / or application requirements.

[0191] The fourth identification information is information indicating whether the UE supports acquisition of SNPN information via a control plane (CP). The fourth identification information may be information indicating that the UE supports acquisition of SNPN information via a control plane, or may be information indicating that the UE does not support acquisition of SNPN information via a control plane. Furthermore, the fourth identification information may be realized by a bit indicating whether the UE supports acquisition of SNPN information via a control plane. Here, the bit indicating whether the UE supports acquisition of SNPN information via a control plane may be a bit constituting a 5GMM capability information element indicating the UE's capabilities in 5G.

[0192] Furthermore, the fourth identification information may be information selected and determined based on the UE settings, and / or the UE status, and / or user policy, and / or application requirements.

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

[0194] Furthermore, the fifth identification information may be information selected and determined based on the UE settings, and / or the UE status, and / or user policy, and / or application requirements.

[0195] The sixth identification information is information indicating a Follow-on request. Here, the sixth identification information may be information indicating a Follow-on request pending. Conversely, the sixth identification information may be information indicating no follow-on request pending.

[0196] Furthermore, the sixth identification information may be information indicating 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.

[0197] Furthermore, the sixth identification information may be realized by a bit indicating a Follow-on request, where the bit indicating the Follow-on request may be a bit constituting a 5GS (5G System) registration type indicating the UE's capability in 5G.

[0198] Furthermore, the sixth identification information may be information selected and determined based on the UE settings, and / or the UE status, and / or user policy, and / or application requirements.

[0199] The eleventh identification information is information indicating whether the network supports registration that can be used only for the onboarding service. The eleventh identification information may be information indicating that the network supports registration that can be used only for the onboarding service, or may be information indicating that the network does not support registration that can be used only for the onboarding service. Furthermore, the eleventh identification information may be realized by a bit indicating whether the network supports registration that can be used only for the onboarding service. Here, the bit indicating whether the network supports registration that can be used only for the onboarding service may be a bit constituting a 5GS network feature support information element that indicates the network's capabilities in 5G.

[0200] Furthermore, the eleventh identification information may be information indicating whether or not a registration that allows only the onboarding service is permitted. The eleventh identification information may be information indicating that a registration that allows only the onboarding service is permitted, or may be information indicating that a registration that allows only the onboarding service is not permitted. Furthermore, the eleventh identification information may be realized by a bit that indicates whether or not a registration that allows only the onboarding service is permitted.

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

[0202] The twelfth identification information is information indicating a type of SNPN information provision procedure supported by the network. The twelfth identification information may be information indicating that the network supports providing SNPN information via a user plane (UP), or may be information indicating that the network supports providing SNPN information via a control plane (CP). Furthermore, the twelfth identification information may be realized by a bit indicating a type of SNPN information provision procedure supported by the network. Here, the bit indicating the type of SNPN information provision procedure supported by the network may be a bit constituting a 5GS network feature support information element indicating the network capabilities in 5G.

[0203] Furthermore, the twelfth identification information may be information indicating that the SNPN information is provided via a user plane. Further, the twelfth identification information may be information indicating that providing the SNPN information via a user plane is supported.

[0204] Furthermore, the twelfth identification information may be information indicating that the SNPN information is provided via a control plane. Furthermore, the twelfth identification information may be information indicating that providing the SNPN information via a control plane is supported.

[0205] Furthermore, the 12th identification information may be information that includes the meaning indicated by the 13th identification information and the meaning indicated by the 14th identification information. Furthermore, the 12th identification information may be information that is composed of the 13th identification information and the 14th identification information.

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

[0207] The thirteenth identification information is information indicating whether the network supports providing SNPN information via a user plane (UP). The thirteenth identification information may be information indicating that the network supports providing SNPN information via a user plane, or may be information indicating that the network does not support providing SNPN information via a user plane. Furthermore, the thirteenth identification information may be realized by a bit indicating whether the network supports providing SNPN information via a user plane. Here, the bit indicating whether the network supports providing SNPN information via a user plane may be a bit constituting a 5GS network feature support information element indicating the network's capabilities in 5G.

[0208] Furthermore, the thirteenth identification information may be information indicating that the SNPN information is provided via a user plane. Further, the thirteenth identification information may be information indicating that the provision of the SNPN information via a user plane is supported.

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

[0210] The fourteenth identification information is information indicating whether the network supports providing SNPN information via a control plane (CP). The fourteenth identification information may be information indicating that the network supports providing SNPN information via a control plane, or may be information indicating that the network does not support providing SNPN information via a control plane. Furthermore, the fourteenth identification information may be realized by a bit indicating whether the network supports providing SNPN information via a control plane. Here, the bit indicating whether the network supports providing SNPN information via a control plane may be a bit constituting a 5GS network feature support information element indicating the network's capabilities in 5G.

[0211] Furthermore, the fourteenth identification information may be information indicating that the SNPN information is provided via the control plane. Furthermore, the fourteenth identification information may be information indicating that providing the SNPN information via the control plane is supported.

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

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

[0214] Here, the reason value may indicate that the onboarding service is unavailable, or in other words, that the onboarding service is not permitted, or further, that a registration that only allows the onboarding service is not permitted.

[0215] Additionally, the reason value may indicate that the network does not support onboarding services.The reason value may indicate that the network does not support registrations that are only enabled for onboarding services.

[0216] Further, the reason value may indicate that a request for onboarding services only was denied. Further, the reason value may indicate that a request for registration with onboarding services only enabled was denied.

[0217] Furthermore, the 21st identification information may be information indicating that the onboarding service is unavailable. In other words, the 21st identification information may be information indicating that the onboarding service is not permitted. Furthermore, the 21st identification information may be information indicating that registration that allows only the onboarding service is not permitted.

[0218] Furthermore, the 21st identification information may be information indicating that the network does not support the onboarding service. The 21st identification information may be information indicating that the network does not support registration that can only be used for the onboarding service.

[0219] Furthermore, the 21st identification information may be information indicating that a request for only onboarding services has been rejected. Further, the 21st identification information may be information indicating that a request for registration that can only be used for onboarding services has been rejected.

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

[0221] The 31st identification information is a cause value indicating why the de-registration procedure was initiated. The 31st identification information may be a 5GS Session Management (5GSM) cause value.

[0222] Specifically, the 31st identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has been successful. Conversely, the 31st identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has been unsuccessful.

[0223] Furthermore, the 31st identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has been completed. More specifically, the 31st identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has been successfully completed. In other words, the 31st identification information may be information indicating that the UE has acquired the SNPN information, or may be information indicating that the network has provided the SNPN information.

[0224] Conversely, the 31st identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has failed. More specifically, the 31st identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has not been completed successfully. In other words, the 31st identification information may be information indicating that the UE has not been able to acquire the SNPN information, or may be information indicating that the network has not been able to provide the SNPN information.

[0225] Furthermore, the 31st identification information may be information indicating that the onboarding service has been completed. More specifically, the 31st identification information may be information indicating that the onboarding service has been successfully completed. Conversely, the 31st identification information may be information indicating that the onboarding service has not been successfully completed.

[0226] Furthermore, the 31st identification information may be information indicating that the onboarding service is unavailable. In other words, the 31st identification information may be information indicating that the onboarding service is not permitted. Furthermore, the 31st identification information may be information indicating that registration that allows only the onboarding service is not permitted.

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

[0228] The 41st identification information is information indicating a request for an Always-on PDU session. The 41st identification information may be an Always-on PDU session requested information element.

[0229] Furthermore, the 41st identification information may be information indicating whether or not the PDU session is requested to be established as an Always-on PDU session. For example, the 41st identification information may be information indicating that the PDU session is requested to be established as an Always-on PDU session. Conversely, the 41st identification information may be information indicating that the PDU session is not requested to be established as an Always-on PDU session.

[0230] Furthermore, the 41st identification information may be information indicating whether or not to request establishment of an Always-on PDU session. For example, the 41st identification information may be information indicating that establishment of an Always-on PDU session is requested. Conversely, the 41st identification information may be information indicating that establishment of an Always-on PDU session is not requested.

[0231] Furthermore, the 41st identification information may be information selected and determined based on the UE settings, and / or the UE state, and / or a user policy, and / or an application request. Furthermore, the 41st identification information may be information selected and determined based on a control message and / or information transmitted and received in another procedure such as a registration procedure.

[0232] The 42nd identification information is information indicating a request for an onboarding service. The 42nd identification information may be information indicating a request for establishing a PDU session for the onboarding service.

[0233] Furthermore, the 42nd identification information may be information indicating whether or not the use of an onboarding service is requested. For example, the 42nd identification information may be information indicating that the use of an onboarding service is requested. Conversely, the 42nd identification information may be information indicating that the use of an onboarding service is not requested.

[0234] Furthermore, the 42nd identification information may be information indicating whether or not to request establishment of a PDU session for the onboarding service. For example, the 42nd identification information may be information indicating that establishment of a PDU session for the onboarding service is requested. Conversely, the 42nd identification information may be information indicating that establishment of a PDU session for the onboarding service is not requested.

[0235] Furthermore, the 42nd identification information may be information selected and determined based on the UE configuration, and / or the UE state, and / or a user policy, and / or an application request. Furthermore, the 42nd identification information may be information selected and determined based on a control message and / or information transmitted and received in another procedure such as a registration procedure.

[0236] The 51st identification information is information indicating an Always-on PDU session. The 51st identification information may be an Always-on PDU session indication information element.

[0237] Furthermore, the 51st identification information may be information indicating whether the PDU session is established as an Always-on PDU session. For example, the 51st identification information may be information indicating that the PDU session is established as an Always-on PDU session. Conversely, the 51st identification information may be information indicating that the PDU session is not established as an Always-on PDU session.

[0238] Furthermore, the 51st identification information may be information indicating whether an Always-on PDU session can be established. For example, the 51st identification information may be information indicating that an Always-on PDU session must be established. Conversely, the 51st identification information may be information indicating that an Always-on PDU session is not permitted to be established.

[0239] Furthermore, the 51st identification information may be information selected or determined by the network based on received identification information, and / or information associated with the NSI, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, etc. Furthermore, the 51st identification information may be information selected or determined based on control messages and / or information transmitted and received in another procedure such as a registration procedure.

[0240] The 52nd identification information is information indicating an onboarding service. The 52nd identification information may be information indicating that the PDU session to be established is a PDU session for an onboarding service.

[0241] Furthermore, the 52nd identification information may be information indicating whether or not use of the onboarding service is permitted. For example, the 52nd identification information may be information indicating that use of the onboarding service is permitted. Conversely, the 52nd identification information may be information indicating that use of the onboarding service is not permitted.

[0242] Furthermore, the 52nd identification information may be information indicating whether establishment of a PDU session for the onboarding service is permitted. For example, the 52nd identification information may be information indicating that establishment of a PDU session for the onboarding service is permitted. Conversely, the 52nd identification information may be information indicating that establishment of a PDU session for the onboarding service is not permitted.

[0243] Furthermore, the 52nd identification information may be information selected or determined by the network based on received identification information, and / or information associated with the NSI, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, etc. Furthermore, the 52nd identification information may be information selected or determined based on control messages and / or information transmitted or received in another procedure, such as a registration procedure.

[0244] [3.2. Description of procedures used in each embodiment] Next, procedures used in each embodiment will be described. The procedures used in each embodiment include a registration procedure, a PDU session establishment procedure, and a generic UE configuration update procedure. Each procedure will be described below.

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

[0246] [3.2.1. Registration Procedure] First, the registration procedure will be explained using FIG. 7. The registration procedure is a procedure in 5GS. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure initiated by the UE to register with the access network _B and / or the core network _B and / or the DN. If the UE is not registered with the network, it can execute this procedure at any time, for example, when it is powered on. In other words, if the UE is in the deregistered state (RM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and AMF) can transition to the registered state (RM-REGISTERED state) based on the completion of the registration procedure.

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

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

[0249] Furthermore, the UE may initiate the registration procedure periodically even when in the registered state, i.e., the UE may initiate the registration procedure based on the expiration of a timer.

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

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

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

[0253] Here, the UE may transmit one or more pieces of identification information among at least the first to sixth pieces of identification information in a registration request message and / or an RRC message. More specifically, the UE may transmit one or more pieces of identification information among at least the first to sixth pieces of identification information in a registration request message and / or an RRC message, or may transmit the one or more pieces of identification information in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, a MAC layer, an RLC layer, or a PDCP layer). By transmitting this identification information, the UE may indicate that the UE supports each function or may indicate a request from the UE. Furthermore, when multiple pieces of identification information are transmitted and received, two or more pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support of each function and the information indicating a request to use each function may be transmitted and received as the same identification information or may be transmitted and received as different identification information.

[0254] When the UE requests an onboarding service, the UE may include one or more of the identities from the first to sixth identities in the registration request message. Furthermore, when the UE requests a registration that can only be used for the onboarding service, the UE may include one or more of the identities from the first to sixth identities in the registration request message. Furthermore, when the UE requests use of a procedure for providing SNPN information, the UE may include one or more of the identities from the first to sixth identities in the registration request message.

[0255] Furthermore, if the UE supports an onboarding service, it may include one or more of the first to sixth identities in the registration request message. Furthermore, if the UE supports a procedure for providing SNPN information, it may include one or more of the first to sixth identities in the registration request message.

[0256] Furthermore, if the UE needs to acquire SNPN information, it may include one or more of the identification information of the first to sixth identification information in the registration request message. Furthermore, if the UE needs to perform an onboarding service, it may include one or more of the identification information of the first to sixth identification information in the registration request message. Furthermore, if the UE needs to perform a procedure for providing SNPN information, it may include one or more of the identification information of the first to sixth identification information in the registration request message.

[0257] Furthermore, if the procedure is a registration procedure for an onboarding service, the UE may include one or more of the identification information of the first to sixth identification information in the registration request message.

[0258] Furthermore, if the UE supports registration that allows only the onboarding service, the UE may include the first identification information in the registration request message. More specifically, if the UE supports the onboarding service, the UE may include the first identification information indicating that the UE supports registration that allows only the onboarding service in the registration request message.

[0259] Furthermore, if the UE supports the SNPN information provision procedure, the UE may include, in the registration request message, second identification information indicating a type of SNPN information provision procedure supported by the UE. More specifically, if the UE supports the SNPN information provision procedure via the user plane, the UE may include, in the registration request message, second identification information indicating support for the SNPN information provision procedure via the user plane. Furthermore, if the UE supports the SNPN information provision procedure via the control plane, the UE may include, in the registration request message, second identification information indicating support for the SNPN information provision procedure via the control plane.

[0260] Furthermore, if the UE supports the procedure for providing SNPN information via the user plane, the UE may include third identification information in the registration request message. More specifically, if the UE supports the procedure for providing SNPN information via the user plane, the UE may include third identification information indicating that the procedure for providing SNPN information via the user plane is supported in the registration request message.

[0261] Furthermore, if the UE supports the procedure for providing SNPN information via the control plane, the UE may include fourth identification information in the registration request message. More specifically, if the UE supports the procedure for providing SNPN information via the control plane, the UE may include fourth identification information indicating that the procedure for providing SNPN information via the control plane is supported in the registration request message.

[0262] Furthermore, when the UE supports the procedure for providing SNPN information via the control plane, the UE may include, in the registration request message, fourth identification information indicating that the procedure for providing SNPN information using PCO or ePCO is supported. Furthermore, when the UE supports the procedure for providing SNPN information via the control plane, the UE may include, in the registration request message, fourth identification information indicating that the procedure for providing SNPN information using URSP is supported.

[0263] Furthermore, when the UE requests the use of the SNPN information providing procedure, it may include a fifth identification in the registration request message. Furthermore, when the UE requests the use of the SNPN information providing procedure, it may include a fifth identification indicating a type of SNPN information providing procedure requested by the UE in the registration request message. More specifically, when the UE requests the use of the SNPN information providing procedure via the user plane, it may include a fifth identification indicating the SNPN information providing procedure via the user plane in the registration request message. Furthermore, when the UE requests the use of the SNPN information providing procedure via the control plane, it may include a fifth identification indicating the SNPN information providing procedure via the control plane in the registration request message.

[0264] Furthermore, the UE may include a sixth identification in the registration request message when the procedure is a registration procedure for an onboarding service. More specifically, the UE may include a sixth identification indicating "Follow-on request pending" in the registration request message when the procedure is a registration procedure for an onboarding service.

[0265] Furthermore, the UE may indicate to the network the content indicated by the identification information included in the registration request message by including one or more of the identification information from the first to sixth identification information in the registration request message. Furthermore, the UE may request to the network the content indicated by the identification information included in the registration request message by including one or more of the identification information from the first to sixth identification information in the registration request message.

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

[0267] The UE may also initiate a PDU session establishment procedure during the registration procedure by sending an SM message (e.g., a PDU session establishment request message) included 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.

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

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

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

[0271] First, we will explain the case where the first condition determination is true. In the procedure of (A) in Figure 7, the AMF can first execute the fourth condition determination. The fourth condition determination is for determining whether the AMF transmits and receives SM messages to and from the SMF.

[0272] Furthermore, the fourth condition determination may be performed based on whether the AMF has received an SM message. Furthermore, the fourth condition determination may be performed based on whether an SM message is included in the registration request message. For example, if the AMF has received an SM message and / or if the registration request message includes an SM message, the fourth condition determination may be true, and if the AMF has not received an SM message and / or if the registration request message does not include an SM message, the fourth condition determination may be false. Furthermore, the conditions that determine the truth or falsity of the fourth condition determination do not have to be limited to the conditions described above.

[0273] If the fourth condition determination is true, the AMF selects an SMF and performs transmission and reception of SM messages with the selected SMF, whereas if the fourth condition determination is false, the AMF does not perform these operations (S806). Also, even if the fourth condition determination is true, the AMF may terminate the procedure of (A) in Figure 7 if it receives an SM message indicating rejection from the SMF. In this case, the AMF can start the procedure of (B) in Figure 7.

[0274] In addition, in S806, when transmitting and receiving an SM message with the SMF, the AMF can notify the SMF of the identification information received in the registration request message. The SMF can obtain the identification information received from the AMF by transmitting and receiving an SM message with the AMF.

[0275] Next, the AMF transmits a registration accept message to the UE via the 5G AN (or gNB) as a response message to the registration request message based on the reception of the registration request message and / or the completion of the transmission and reception of an SM message with the SMF (S808). For example, if the fourth condition determination is false, the AMF may transmit the registration accept message based on the reception of the registration request message from the UE. Also, if the fourth condition determination is true, the AMF may transmit the registration accept message based on the completion of the transmission and reception of an SM message with the SMF. Note that the registration accept message is a NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) included in an RRC message.

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

[0277] The network may include one or more identities from identities 11 to 14 in the registration accept message if it allows onboarding services. Furthermore, the network may include one or more identities from identities 11 to 14 in the registration accept message if it allows registration that can only use onboarding services. Furthermore, the network may include one or more identities from identities 11 to 14 in the registration accept message if it allows use of the SNPN information provision procedure.

[0278] Furthermore, if the network supports an onboarding service, it may include one or more identities from the eleventh to fourteenth identities in the registration accept message. Furthermore, if the network supports a procedure for providing SNPN information, it may include one or more identities from the eleventh to fourteenth identities in the registration accept message.

[0279] Furthermore, the network may include one or more of the identities of the eleventh to fourteenth identities in the registration accept message if it is capable of providing SNPN information. Furthermore, the network may include one or more of the identities of the eleventh to fourteenth identities in the registration accept message if it is capable of performing an onboarding service. Furthermore, the network may include one or more of the identities of the eleventh to fourteenth identities in the registration accept message if it is capable of performing a procedure for providing SNPN information.

[0280] Furthermore, if the network supports registration that allows only onboarding services, the network may include an eleventh identification in the registration accept message. More specifically, if the network supports onboarding services, the network may include an eleventh identification in the registration accept message indicating that the network supports registration that allows only onboarding services.

[0281] Furthermore, if the network supports the SNPN information provision procedure, it may include twelfth identification information indicating the type of SNPN information provision procedure supported by the network in the registration accept message. More specifically, if the network supports the SNPN information provision procedure via the user plane, it may include twelfth identification information indicating that it supports the SNPN information provision procedure via the user plane in the registration accept message. Furthermore, if the network supports the SNPN information provision procedure via the control plane, it may include twelfth identification information indicating that it supports the SNPN information provision procedure via the control plane in the registration accept message.

[0282] Furthermore, if the network supports the procedure for providing SNPN information via the user plane, the network may include thirteenth identification information in the registration accept message. More specifically, if the network supports the procedure for providing SNPN information via the user plane, the network may include thirteenth identification information indicating that the network supports the procedure for providing SNPN information via the user plane in the registration accept message.

[0283] Furthermore, if the network supports the procedure for providing SNPN information via the control plane, the network may include a fourteenth identification in the registration accept message. More specifically, if the network supports the procedure for providing SNPN information via the control plane, the network may include a fourteenth identification indicating that the network supports the procedure for providing SNPN information via the control plane in the registration accept message.

[0284] Furthermore, if the network supports the procedure for providing SNPN information via the control plane, it may include, in the registration accept message, fourteenth identification information indicating that the procedure for providing SNPN information using PCO or ePCO is supported. Furthermore, if the network supports the procedure for providing SNPN information via the control plane, it may include, in the registration accept message, fourteenth identification information indicating that the procedure for providing SNPN information using URSP is supported.

[0285] Furthermore, the network may include one or more of the 11th to 14th identities in the registration accept message to indicate to the UE the content indicated by the identities included in the registration accept message. Furthermore, the network may include one or more of the 11th to 14th identities in the registration accept message to permit the UE to accept the content indicated by the identities included in the registration accept message.

[0286] Furthermore, the AMF may select and determine which of the 11th to 14th identification information to include in the registration acceptance message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0287] Furthermore, the AMF can include an SM message (e.g., a PDU session establishment acceptance message) in the registration acceptance message and send it, or can send an SM message (e.g., a PDU session establishment acceptance message) together with the registration acceptance message. However, this sending method may be performed when an SM message (e.g., a PDU session establishment request message) is included in the registration request message and the fourth condition determination is true. Also, this sending method may be performed when an SM message (e.g., a PDU session establishment request message) is included in the registration request message and the fourth condition determination is true. By performing such a sending method, the AMF can indicate that the procedure for SM has been accepted in the registration procedure.

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

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

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

[0291] The UE can further transmit a registration complete message to the AMF via the 5G AN (gNB) as a response message to the registration accept message (S810). When the UE receives an SM message such as a PDU session establishment accept message, the UE may transmit an SM message such as a PDU session establishment complete message in the registration complete message, or may indicate that the SM procedure has been completed by including the SM message. Here, the registration complete message is an NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) in an RRC message.

[0292] The AMF receives a registration completion message via the 5G AN (gNB) (S810). In addition, each device completes the procedure of (A) in FIG. 7 based on the transmission and reception of the registration acceptance message and / or the registration completion message.

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

[0294] Here, the AMF may send the registration rejection message including at least the 21st identification information, or by sending the 21st identification information, may indicate that the UE request has been rejected or may indicate the reason why the UE request has been rejected.

[0295] The network may include the 21st identifier in the registration reject message if it does not allow the onboarding service. Furthermore, the network may include the 21st identifier in the registration reject message if it does not allow a registration that can only use the onboarding service. Furthermore, the network may include the 21st identifier in the registration reject message if it does not allow the use of the SNPN information provision procedure.

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

[0297] Furthermore, the network may include the 21st identification information in the registration reject message if the network is unable to provide the SNPN information. Furthermore, the network may include the 21st identification information in the registration reject message if the network is unable to perform the onboarding service. Furthermore, the network may include the 21st identification information in the registration reject message if the network is unable to perform the SNPN information providing procedure.

[0298] Furthermore, if the network does not support registration that allows onboarding services only, the network may include a 21st identification in the registration reject message. More specifically, if the network does not support registration that allows onboarding services only, the network may include a 21st identification in the registration reject message indicating that the network does not support registration that allows onboarding services only.

[0299] Furthermore, if the network does not support the onboarding service, the network may include, in the registration rejection message, 21st identification information indicating that the onboarding service is not supported. Furthermore, if the network does not support the SNPN information provision procedure, the network may include, in the registration rejection message, 21st identification information indicating that the SNPN information provision procedure is not supported.

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

[0301] Furthermore, the network may include the 21st identification information in the registration rejection message to indicate to the UE the content indicated by the identification information included in the registration rejection message. Furthermore, the network may include the 21st identification information in the registration rejection message to not allow the UE to use the content indicated by the identification information included in the registration rejection message.

[0302] Furthermore, the AMF may select and decide 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 context held by the AMF, etc.

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

[0304] 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 UE's request via the registration request message has been rejected and the contents of the various identification information included in the registration rejection message. Furthermore, if the UE does not receive a registration rejection message even after a predetermined period has elapsed since sending the registration request message, the UE may recognize that the UE's request has been rejected. Each device completes the procedure (B) in this procedure based on the transmission and reception of the registration rejection message.

[0305] Note that the procedure in Figure 7(B) may be started when the procedure in Figure 7(A) is stopped. In the procedure in Figure 7(A), if the fourth condition determination is true, the AMF may send a registration rejection message including an SM message indicating rejection, such as a PDU session establishment rejection message, or may indicate that the procedure for SM has been rejected by including an SM message indicating rejection. In this case, the UE may further receive an SM message indicating rejection, such as a PDU session establishment rejection message, or may recognize that the procedure for SM has been rejected.

[0306] Each device completes the registration procedure based on the completion of the procedure of (A) or (B) in Figure 7. Note that each device may transition to a state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure of (A) in Figure 7, or may maintain a state in which the UE is not registered in the network (RM_DEREGISTERED state) or transition to a state in which the UE is not registered in the network based on the completion of the procedure of (B) in Figure 7. Furthermore, the transition of each device to each state may be based on the completion of the registration procedure or on the establishment of a PDU session.

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

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

[0309] For example, the UE may recognize that an onboarding service is authorized if it receives one or more identities from identities 11 to 14. Furthermore, the UE may recognize that a registration that can only be used for the onboarding service is authorized if it receives one or more identities from identities 11 to 14. Furthermore, the UE may recognize that use of the SNPN information provision procedure is authorized if it receives one or more identities from identities 11 to 14.

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

[0311] Furthermore, the UE may recognize that the network is capable of providing SNPN information when it receives one or more of the identities of the eleventh to fourteenth identities. Furthermore, the UE may recognize that the network is capable of providing SNPN information when it receives one or more of the identities of the eleventh to fourteenth identities. Furthermore, the UE may recognize that the network is capable of providing SNPN information when it receives one or more of the identities of the eleventh to fourteenth identities.

[0312] Furthermore, the UE may recognize that an onboarding service-only registration is supported if the UE receives the eleventh identification. More specifically, the UE may recognize that an onboarding service is supported if the UE receives the eleventh identification indicating that the network supports an onboarding service-only registration.

[0313] Furthermore, the UE may recognize that the SNPN information providing procedure is supported when it receives twelfth identification information indicating a type of SNPN information providing procedure supported by the network. More specifically, the UE may recognize that the SNPN information providing procedure via the user plane is supported when it receives twelfth identification information indicating that the SNPN information providing procedure via the user plane is supported. Furthermore, the UE may recognize that the SNPN information providing procedure via the control plane is supported when it receives twelfth identification information indicating that the SNPN information providing procedure via the control plane is supported.

[0314] Furthermore, the UE may recognize that the SNPN information providing procedure via the user plane is supported if the UE receives the thirteenth identification information. More specifically, the UE may recognize that the SNPN information providing procedure via the user plane is supported if the UE receives the thirteenth identification information indicating that the UE supports the SNPN information providing procedure via the user plane.

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

[0316] Furthermore, when the UE receives fourteenth identification information indicating that the UE supports a procedure for providing SNPN information using a PCO or an ePCO, the UE may recognize that the procedure for providing SNPN information via the control plane is supported, or may recognize that the procedure for providing SNPN information using a PCO or an ePCO is supported. Furthermore, when the UE receives fourteenth identification information indicating that the UE supports a procedure for providing SNPN information using a URSP, the UE may recognize that the procedure for providing SNPN information via the control plane is supported, or may recognize that the procedure for providing SNPN information using a URSP is supported.

[0317] Furthermore, when the UE receives one or more of the identification information from the eleventh to fourteenth identification information, the UE may recognize the content indicated by the received identification information. Furthermore, when the UE receives one or more of the identification information from the eleventh to fourteenth identification information, the UE may recognize that the content indicated by the identification information included in the registration accept message is permitted.

[0318] Furthermore, the UE may recognize that establishment of a PDU session for a function other than the onboarding service is prohibited when it receives one or more identification information from the 11th to 14th identification information. Furthermore, the UE may be configured to prohibit establishment of a PDU session for a function other than the onboarding service when it receives one or more identification information from the 11th to 14th identification information. In other words, the UE may be configured to prevent initiation of a PDU session establishment procedure for a function other than the onboarding service when it receives one or more identification information from the 11th to 14th identification information.

[0319] Furthermore, the UE may recognize that establishment of a PDU session other than that for the SNPN information provision procedure is prohibited when it receives one or more identification information from among the 11th to 14th identification information. Furthermore, the UE may be configured to prohibit establishment of a PDU session other than that for the SNPN information provision procedure when it receives one or more identification information from among the 11th to 14th identification information. In other words, the UE may be configured to prevent initiation of a PDU session establishment procedure for a PDU session other than that for the SNPN information provision procedure when it receives one or more identification information from among the 11th to 14th identification information. Furthermore, the UE may be configured to prevent initiation of a PDU session establishment procedure for a PDU session other than that for the SNPN information provision procedure when it receives one or more identification information from among the 11th to 14th identification information.

[0320] The period during which establishment of PDU sessions other than those for the SNPN information provision procedure is prohibited may be a period managed by a timer. In other words, the UE may be configured so that establishment of PDU sessions other than those for the SNPN information provision procedure is not prohibited based on the expiration of the timer.

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

[0322] Furthermore, the period during which establishment of PDU sessions other than those for the SNPN information provision procedure is prohibited may be the period until the UE is powered off and / or the USIM is removed. In other words, the UE may be configured so that establishment of PDU sessions other than those for the SNPN information provision procedure is not prohibited based on the powering off and / or the removal of the USIM.

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

[0324] Furthermore, the PDU session other than that for the SNPN information provision procedure may be a PDU session other than that for the onboarding service. Furthermore, the PDU session other than that for the SNPN information provision procedure may be a PDU session for a function other than the onboarding service.

[0325] For example, the PDU session other than that for the SNPN information provision procedure may be a PDU session for an IMS service. Furthermore, the PDU session other than that for the SNPN information provision procedure may be a PDU session for an emergency service. Furthermore, the PDU session other than that for the SNPN information provision procedure may be a PDU session for an LADN. Furthermore, the PDU session other than that for the SNPN information provision procedure may be a PDU session for a CIoT.

[0326] In other words, the PDU session other than that for the SNPN information provision procedure may be a PDU session for an IMS service. Furthermore, the PDU session other than that for the SNPN information provision procedure may be a PDU session for an emergency service. Furthermore, the PDU session other than that for the SNPN information provision procedure may be a PDU session for an LADN. Furthermore, the PDU session other than that for the SNPN information provision procedure may be a PDU session for a CIoT.

[0327] Furthermore, the PDU session establishment procedure for purposes other than the SNPN information provision procedure may be a PDU session establishment procedure for an IMS service. Furthermore, the PDU session establishment procedure for purposes other than the SNPN information provision procedure may be a PDU session establishment procedure for an emergency service. Furthermore, the PDU session establishment procedure for purposes other than the SNPN information provision procedure may be a PDU session establishment procedure for an LADN. Furthermore, the PDU session establishment procedure for purposes other than the SNPN information provision procedure may be a PDU session establishment procedure for a CIoT.

[0328] Furthermore, without being limited to the above, the PDU session other than that for the procedure of providing SNPN information may be any PDU session other than that established and used for the procedure of providing SNPN information.

[0329] Furthermore, the UE may recognize the type of the permitted SNPN information providing procedure when it receives twelfth identification information indicating the type of SNPN information providing procedure supported by the network. More specifically, the UE may recognize that use of the SNPN information providing procedure via the user plane is permitted when it receives twelfth identification information indicating that the SNPN information providing procedure via the user plane is supported. Furthermore, the UE may recognize that use of the SNPN information providing procedure via the control plane is permitted when it receives twelfth identification information indicating that the SNPN information providing procedure via the control plane is supported.

[0330] Furthermore, the UE may recognize that it is authorized to use the SNPN information providing procedure via the user plane if it receives the thirteenth identification information. More specifically, the UE may recognize that it is authorized to use the SNPN information providing procedure via the user plane if it receives the thirteenth identification information indicating that it supports the SNPN information providing procedure via the user plane.

[0331] Furthermore, the UE may recognize that it is authorized to use the SNPN information providing procedure via the control plane if it receives the fourteenth identification information. More specifically, the UE may recognize that it is authorized to use the SNPN information providing procedure via the control plane if it receives the fourteenth identification information indicating that it supports the SNPN information providing procedure via the control plane.

[0332] Furthermore, the UE may determine whether to establish a PDU session when it receives one or more of the identification information from the 11th to 14th identification information. In other words, the UE may determine whether to initiate a PDU session establishment procedure to establish a PDU session when it receives one or more of the identification information from the 11th to 14th identification information.

[0333] For example, when the UE receives one or more of the 11th to 14th identification information, the UE may initiate a PDU session establishment procedure to establish a PDU session or may establish a PDU session. Furthermore, when the UE receives 12th identification information indicating that the UE supports a procedure for providing SNPN information via the user plane, the UE may initiate a PDU session establishment procedure to establish a PDU session or may establish a PDU session. Furthermore, when the UE receives 13th identification information, the UE may initiate a PDU session establishment procedure to establish a PDU session or may establish a PDU session.

[0334] Conversely, when the UE receives one or more of the eleventh to fourteenth identification information, the UE may be configured not to initiate a PDU session establishment procedure for establishing a PDU session, or may not establish a PDU session. Furthermore, when the UE receives twelfth identification information indicating that the UE supports a procedure for providing SNPN information via the control plane, the UE may be configured not to initiate a PDU session establishment procedure for establishing a PDU session, or may not establish a PDU session. Furthermore, when the UE receives fourteenth identification information, the UE may be configured not to initiate a PDU session establishment procedure for establishing a PDU session, or may not establish a PDU session.

[0335] Furthermore, the UE may initiate a PDU session establishment procedure when it receives the fourteenth identification information indicating that it supports the SNPN information providing procedure using PCO or ePCO. Conversely, the UE may not initiate a PDU session establishment procedure when it receives the fourteenth identification information indicating that it supports the SNPN information providing procedure using URSP.

[0336] In other words, the UE may initiate a PDU session establishment procedure if the SNPN information provision procedure using the PCO or ePCO is supported and / or permitted, and conversely, the UE may not initiate a PDU session establishment procedure if the SNPN information provision procedure using the URSP is supported and / or permitted.

[0337] Furthermore, when the UE performs the SNPN information provision procedure using PCO or ePCO, the UE may initiate a PDU session establishment procedure. Conversely, when the UE performs the SNPN information provision procedure using URSP, the UE may not initiate a PDU session establishment procedure.

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

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

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

[0341] Further, the PDU session establishment procedure may be a PDU session establishment procedure for an onboarding service. Further, the PDU session establishment procedure may be a PDU session establishment procedure for an onboarding service. Further, the PDU session establishment procedure may be a PDU session establishment procedure for establishing a PDU session for an onboarding service. Further, the PDU session establishment procedure may be a PDU session establishment procedure for an onboarding service.

[0342] Furthermore, the UE may start a timer when receiving one or more identities from the 11th to 14th identities, and may initiate a de-registration procedure based on expiration of the timer.

[0343] Furthermore, the network may start a timer when transmitting one or more of the eleventh to fourteenth identities. Furthermore, the network may start a de-registration procedure based on the expiration of the timer.

[0344] Here, the timer may be a timer indicating a time limit during which a registration that can be used only for onboarding services is valid, in other words, a time limit during which a procedure for providing SNPN information can be executed.

[0345] Furthermore, the UE may configure the NAS signaling connection not to be released after the procedure is completed. More specifically, if the procedure is a registration procedure for an onboarding service, the UE may configure the NAS signaling connection not to be released after the procedure is completed.

[0346] In other words, if this procedure is a registration procedure for an onboarding service, the UE may not release the NAS signaling connection after completing this procedure, whereas if this procedure is not a registration procedure for an onboarding service, the UE may release the NAS signaling connection after completing this procedure.

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

[0348] In other words, if this procedure is a registration procedure for an onboarding service, each device may not release the NAS signaling connection after completing this procedure. Conversely, if this procedure is not a registration procedure for an onboarding service, each device may release the NAS signaling connection after completing this procedure.

[0349] Furthermore, the UE may be configured to not release the NAS signaling connection if it has transmitted a registration request message including one or more of the identification information 1 to 6. More specifically, the UE may be configured to not release the NAS signaling connection after the procedure is completed if it has transmitted a registration request message including one or more of the identification information 1 to 6.

[0350] In other words, if the UE includes one or more of the first to sixth identities in the registration request message, the UE may not release the NAS signaling connection after completing this procedure. Conversely, if the UE does not include one or more of the first to sixth identities in the registration request message, the UE may release the NAS signaling connection after completing this procedure.

[0351] Furthermore, the UE may be configured to not release the NAS signaling connection when the UE transmits a registration request message including sixth identification information indicating information indicating a follow-on request pending. More specifically, the UE may be configured to not release the NAS signaling connection after the procedure is completed when the UE transmits a registration request message including sixth identification information indicating information indicating a follow-on request pending.

[0352] In other words, if the UE includes the sixth identification information indicating a Follow-on request pending in the registration request message, the UE may not release the NAS signaling connection after the completion of this procedure. Conversely, if the UE includes the sixth identification information indicating a No follow-on request pending in the registration request message, the UE may release the NAS signaling connection after the completion of this procedure.

[0353] Furthermore, the network may be configured not to release the NAS signaling connection when a registration request message including one or more of the identification information 1 to 6 is received. More specifically, the network may be configured not to release the NAS signaling connection after completion of this procedure when a registration request message including one or more of the identification information 1 to 6 is received.

[0354] In other words, if one or more of the first to sixth identities are included in the registration request message, the network may not release the NAS signaling connection after the completion of this procedure. Conversely, if one or more of the first to sixth identities are not included in the registration request message, the network may release the NAS signaling connection after the completion of this procedure.

[0355] Furthermore, the network may be configured to prevent the NAS signaling connection from being released when a registration request message including a sixth identification indicating information indicating a follow-on request pending is received. More specifically, the network may be configured to prevent the NAS signaling connection from being released after the procedure is completed when a registration request message including a sixth identification indicating information indicating a follow-on request pending is received.

[0356] In other words, if the sixth identification information indicating information indicating a follow-on request pending is included in the registration request message, the network may not release the NAS signaling connection after the completion of this procedure. Conversely, if the sixth identification information indicating a no follow-on request pending is included in the registration request message, the network may release the NAS signaling connection after the completion of this procedure.

[0357] Furthermore, the UE may recognize that the onboarding service is not authorized when the 21st identification information is received. Furthermore, the UE may recognize that the registration that can only be used for the onboarding service is not authorized when the 21st identification information is received. Furthermore, the UE may recognize that the use of the SNPN information provision procedure is authorized when the 21st identification information is received.

[0358] Furthermore, the UE may recognize that the onboarding service is not supported when receiving the 21st identification information. Furthermore, the UE may recognize that the SNPN information provision procedure is not supported when receiving the 21st identification information.

[0359] Furthermore, the UE may recognize that provision and / or acquisition of SNPN information is not possible when receiving the 21st identification information. Furthermore, the UE may recognize that execution of an onboarding service is not possible when receiving the 21st identification information. Furthermore, the UE may recognize that execution of a procedure for providing SNPN information is not possible when receiving the 21st identification information.

[0360] Furthermore, the UE may recognize that onboarding service-only registration is not supported if it receives the 21st identification information. More specifically, the UE may recognize that onboarding service-only registration is not supported if it receives the 21st identification information indicating that the network does not support onboarding service-only registration.

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

[0362] Furthermore, the UE may recognize that the requested SNPN information providing procedure is not supported when the UE receives 21st identification information indicating that the UE does not support the requested SNPN information providing procedure. More specifically, the UE may recognize that the SNPN information providing procedure is not supported when the UE receives 21st identification information indicating that the UE does not support the SNPN information providing procedure via the user plane. Furthermore, the UE may recognize that the SNPN information providing procedure is not supported when the UE receives 21st identification information indicating that the UE does not support the SNPN information providing procedure via the control plane.

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

[0364] Furthermore, when the UE receives the 21st identification information, the UE may add the identification information of the network to the first list. Furthermore, when the UE receives the 21st identification information, the UE may create a first list and add the identification information of the network to the created first list.

[0365] More specifically, the UE may add the network identification information to the first list when receiving the 21st identification information indicating that the UE does not support the SNPN information provision procedure. Furthermore, the UE may add the network identification information to the first list when receiving the 21st identification information indicating that the UE does not support the onboarding service. Furthermore, the UE may add the network identification information to the first list when receiving the 21st identification information indicating that the network does not support registration available only for the onboarding service.

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

[0367] For example, if the procedure is performed in a first network, the network identity may be information identifying the first network. More particularly, if the procedure is performed in a first PLMN, the network identity may be information identifying the first PLMN. Furthermore, if the procedure is performed in a first SNPN, the network identity may be information identifying the first SNPN.

[0368] The period for which the first list is maintained may be a period managed by a timer, i.e., the UE may release or delete the first list based on the expiration of the timer.

[0369] Furthermore, the first list may be maintained until the procedure for providing the SNPN information is completed. In other words, the UE may release or delete the first list based on the completion of the procedure for providing the SNPN information.

[0370] Furthermore, the first list may be maintained 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.

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

[0372] Furthermore, the first list may be maintained until a de-registration procedure and / or a second network selection is performed. In other words, the UE may release or delete the first list based on the execution of a de-registration procedure and / or a second network selection.

[0373] Furthermore, the first list may be maintained until the UE is powered off and / or the USIM is removed, i.e., the UE may release or delete the first list based on the powering off and / or the removal of the USIM.

[0374] Furthermore, the UE may re-perform the first network selection when it receives the 21st identification information. Furthermore, the UE may re-perform the first network selection when it receives the 21st identification information, and may select a network other than the network in which it is currently located. Furthermore, the UE may initiate a registration procedure in the selected new network after completing the re-performed first network selection.

[0375] More specifically, the UE may re-perform the first network selection if it receives the 21st identification information indicating that the network does not support the SNPN information provision procedure. Furthermore, the UE may re-perform the first network selection if it receives the 21st identification information indicating that the network does not support the onboarding service. Furthermore, the UE may re-perform the first network selection if it receives the 21st identification information indicating that the network does not support registration available only for the onboarding service.

[0376] Furthermore, when the UE receives the 21st identification information, the UE may start a timer, where the timer may indicate a time limit for managing the first list. In other words, the UE may release or delete the first list based on the expiration of the timer.

[0377] Furthermore, the timer may be a timer indicating a time limit for prohibiting the registration procedure, In other words, the UE may start the registration procedure based on the expiration of the timer.

[0378] Note that the behavior to be performed when each piece of identification information is received may be performed based on the received identification information. For example, the behavior to be performed when eleventh identification information is received may be performed based on the received eleventh identification information. Furthermore, the behavior to be performed when twelfth identification information is received may be performed based on the received twelfth identification information. Furthermore, the behavior to be performed when thirteenth identification information is received may be performed based on the received thirteenth identification information. Furthermore, the behavior to be performed when fourteenth identification information is received may be performed based on the received fourteenth identification information. Furthermore, the behavior to be performed when twenty-first identification information is received may be performed based on the received twenty-first identification information.

[0379] [3.2.2. PDU Session Establishment Procedure] Next, an overview of the PDU session establishment procedure performed to establish a PDU session for a DN will be explained using Figure 8. The PDU session establishment procedure is a procedure in 5GS. Hereinafter, this procedure refers to the PDU session establishment procedure. The PDU session establishment procedure is a procedure used by each device to establish a PDU session. Note that each device can start the PDU session establishment procedure at any time after the registration procedure is completed and the device is in a registered state. Furthermore, each device may be able to execute the PDU session establishment procedure during the registration procedure. Furthermore, each device may establish a PDU session based on the completion of the PDU session establishment procedure.

[0380] The PDU session establishment procedure may be initiated by the UE or may be initiated by the UE. In other words, the PDU session establishment procedure may be a UE-requested PDU session establishment procedure. Each device can establish multiple PDU sessions by performing the PDU session establishment procedure multiple times.

[0381] Here, the UE may initiate a PDU session establishment procedure to establish a PDU session for the onboarding service when the registration procedure for the onboarding service is completed. Furthermore, the UE may initiate a PDU session establishment procedure to establish an Always-on PDU session when the registration procedure for the onboarding service is completed. Furthermore, the UE may initiate a PDU session establishment procedure to establish an Always-on PDU session as a PDU session for the onboarding service when the registration procedure for the onboarding service is completed.

[0382] Furthermore, the UE may initiate a PDU session establishment procedure to establish a PDU session for the onboarding service when registration allowing only the onboarding service is complete. Furthermore, the UE may initiate a PDU session establishment procedure to establish an Always-on PDU session when registration allowing only the onboarding service is complete. Furthermore, the UE may initiate a PDU session establishment procedure to establish an Always-on PDU session as a PDU session for the onboarding service when registration allowing only the onboarding service is complete.

[0383] Furthermore, the UE may initiate a PDU session establishment procedure to establish a PDU session for the onboarding service when registered with the network for the onboarding service. Furthermore, the UE may initiate a PDU session establishment procedure to establish an Always-on PDU session when registered with the network for the onboarding service. Furthermore, the UE may initiate a PDU session establishment procedure to establish an Always-on PDU session as a PDU session for the onboarding service when registered with the network for the onboarding service.

[0384] First, the UE initiates the PDU session establishment procedure by sending a NAS message including a PDU session establishment request message to the SMF via the 5G AN (gNB) and AMF (S900) (S902) (S904).

[0385] Specifically, the UE transmits a NAS message including a PDU session establishment request message to the AMF via the N1 interface and the 5G AN (gNB) (S900). The NAS message including the PDU session establishment request message may be an MM message. Furthermore, the MM message may be an uplink NAS transport (UL NAS TRANSPORT) message. Here, the expression "identification information and / or a value is included in the PDU session establishment request message" may mean that the identification information and / or a value is included in the MM message including the PDU session establishment request message.

[0386] Here, the UE can transmit at least one or more of the identification information items 41 and 42 in a PDU session establishment request message and / or a NAS message, but may also transmit the identification information in a control message other than these, for example, a control message of a layer lower than the RRC layer (for example, a MAC layer, an RLC layer, or a PDCP layer). The identification information may indicate a request from the UE by being included in these messages. Furthermore, when multiple identification information items are transmitted and received, two or more of the identification information items may be configured as one or more identification information items.

[0387] Specifically, the UE may include the 41st identity and / or the 42nd identity in a PDU session establishment request message. Furthermore, the UE may include the DNN and / or S-NSSAI in an uplink NAS transport message together with the PDU session establishment request message including at least the 41st identity and / or the 42nd identity. Furthermore, the UE may transmit the uplink NAS transport message to the AMF (S900). In other words, the UE may transmit the DNN and / or S-NSSAI to the AMF together with the PDU session establishment request message including the 41st identity and / or the 42nd identity. In yet another word, the UE may transmit the PDU session establishment request message including the 41st identity and / or the 42nd identity to the AMF together with the DNN and / or S-NSSAI.

[0388] Furthermore, when requesting an onboarding service, the UE may include one or more identification information from the identification information of identification numbers 41 to 42 in the PDU session establishment request message. Furthermore, when requesting establishment of a PDU session for the onboarding service, the UE may include one or more identification information from the identification information of identification numbers 41 to 42 in the PDU session establishment request message. Furthermore, when requesting use of the onboarding service, the UE may include one or more identification information from the identification information of identification numbers 41 to 42 in the PDU session establishment request message.

[0389] Furthermore, if the registration procedure for the onboarding service has been completed, the UE may include one or more of the identification information from identification information 41 to 42 in the PDU session establishment request message. Furthermore, if the registration that can only be used for the onboarding service has been completed, the UE may include one or more of the identification information from identification information 41 to 42 in the PDU session establishment request message.

[0390] Furthermore, when the UE is registered with a network for onboarding service, the UE may include one or more identities among the identities 41 to 42 in the PDU session establishment request message, where the network for onboarding service may be an SNPN or a PLMN.

[0391] Furthermore, if it is necessary to obtain SNPN information, the UE may include one or more identification information from the identification information of the 41st to 42nd in the PDU session establishment request message. Furthermore, if it is necessary to perform an onboarding service, the UE may include one or more identification information from the identification information of the 41st to 42nd in the PDU session establishment request message. Furthermore, if it is necessary to perform a procedure for providing SNPN information, the UE may include one or more identification information from the identification information of the 41st to 42nd in the PDU session establishment request message.

[0392] Furthermore, if this procedure is a PDU session establishment procedure for an onboarding service, the UE may include one or more identification information from the identification information 41 to 42 in the PDU session establishment request message.

[0393] Furthermore, the UE may request establishment of a PDU session for the onboarding service when this procedure is a PDU session establishment procedure for the onboarding service. Furthermore, the UE may request establishment of an Always-on PDU session when this procedure is a PDU session establishment procedure for the onboarding service. Furthermore, the UE may request establishment of an Always-on PDU session as a PDU session for the onboarding service when this procedure is a PDU session establishment procedure for the onboarding service.

[0394] Furthermore, the UE may request establishment of an Always-on PDU session as a PDU session for the onboarding service. In this case, the UE may include the 41st identification information in the PDU session establishment request message. More specifically, in this case, the UE may include the 41st identification information indicating that it requests establishment of an Always-on PDU session in the PDU session establishment request message. In other words, in this case, the UE may include the 41st identification information indicating that it requests that the PDU session be established as an Always-on PDU session in the PDU session establishment request message.

[0395] Furthermore, when the UE requests establishment of a PDU session for the onboarding service, the UE may include the 42nd identification information in the PDU session establishment request message. More specifically, in this case, the UE may include the 41st identification information indicating that it is requesting use of the onboarding service in the PDU session establishment request message. In other words, in this case, the UE may include the 41st identification information indicating that it is requesting establishment of a PDU session for the onboarding service in the PDU session establishment request message.

[0396] Furthermore, the UE may indicate to the network the contents indicated by the identification information included in the PDU session establishment request message by including one or more of the identification information from identification information Nos. 41 to 42 in the PDU session establishment request message. Furthermore, the UE may request to the network the contents indicated by the identification information included in the PDU session establishment request message by including one or more of the identification information from identification information Nos. 41 to 42 in the PDU session establishment request message.

[0397] Furthermore, the UE may select and decide whether to include one or more of the identification information 41 to 42 in the PDU session establishment request message based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0398] When the AMF receives a NAS message including a PDU session establishment request message (S900), it extracts the PDU session establishment request message from the NAS message and selects an SMF as a transfer destination of the PDU session establishment request message (S902). Note that the AMF may select the transfer destination SMF based on the identification information, subscriber information, network capability information, operator policy, network status, user registration information, and / or context held by the AMF, etc., included in the PDU session establishment request message and / or the NAS message.

[0399] The AMF transfers the PDU session establishment request message to the selected SMF via the N11 interface (S904).

[0400] When the SMF receives the PDU session establishment request message (S904), it recognizes various identification information included in the PDU session establishment request message. Then, the SMF performs a third condition determination. The third condition determination is for the SMF to determine whether to accept the UE request. In the third condition determination, the SMF determines whether the third condition determination is true or false. If the third condition determination is true, the SMF starts the procedure in (A) of Figure 8, and if the third condition determination is false, the SMF starts the procedure in (B) of Figure 8.

[0401] The third condition determination may be performed based on the PDU session establishment request message, and / or each identification information included in the PDU session establishment 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 the SMF. For example, if the network permits the UE request, the third condition determination may be true. If the network does not permit the UE request, the third condition determination may be false. Furthermore, if the network to which the UE is connected and / or a device within the network supports the function requested by the UE, the third condition determination may be true. If the function requested by the UE is not supported, the third condition determination may be false. Furthermore, if the identification information to be transmitted and received is permitted, the third condition determination may be true. If the identification information to be transmitted and received is not permitted, the third condition determination may be false. The conditions for determining whether the third condition determination is true or false do not have to be limited to the above-described conditions.

[0402] Next, we will explain the steps when the third condition determination is true, i.e., each step of the procedure in (A) of Figure 8. The SMF selects a UPF with which to establish a PDU session, and sends a session establishment request message to the selected UPF via the N4 interface (S906), starting the procedure in (A) of Figure 8.

[0403] Here, the SMF may select one or more UPFs based on the identification information, subscriber information, network capability information, operator policy, network status, user registration information, and / or context held by the SMF, etc. acquired based on the reception of the PDU session establishment request message. If multiple UPFs are selected, the SMF may send the session establishment request message to each UPF.

[0404] The UPF receives a session establishment request message from the SMF via the N4 interface (S906) and creates a context for the PDU session. Furthermore, the UPF sends a session establishment response message to the SMF via the N4 interface based on the reception of the session establishment request message and / or the creation of the context for the PDU session (S908).

[0405] The SMF receives a session establishment response message from the UPF via the N4 interface as a response message to the session establishment request message (S908). The SMF may perform address allocation of an address to be assigned to the UE based on the reception of the PDU session establishment request message, and / or the selection of the UPF, and / or the reception of the session establishment response message.

[0406] The SMF sends a PDU session establishment accept message to the UE via the AMF based on the reception of the PDU session establishment request message, and / or the selection of a UPF, and / or the reception of a session establishment response message, and / or the completion of address allocation of an address to be assigned to the UE (S910) (S912).

[0407] Specifically, the SMF sends a PDU session establishment accept message to the AMF via the N11 interface (S910). The AMF, having received the PDU session establishment request message, sends a NAS message including the PDU session establishment accept message to the UE via the N1 interface (S912). The PDU session establishment accept message is an NAS message and may be a response message to the PDU session establishment request. The PDU session establishment accept message may be transmitted and received via the N1 interface, being included in an MM message. The MM message may be an NAS message or a downlink NAS transport (DL NAS TRANSPORT) message. Here, the expression "identification information and / or values ​​are included in the PDU session establishment accept message" may mean that the identification information and / or values ​​are included in the MM message including the PDU session establishment accept message. The PDU session establishment accept message may indicate that the establishment of the PDU session has been accepted.

[0408] Here, the SMF and / or AMF may indicate that the UE's request for PDU session establishment has been accepted by sending a PDU session establishment acceptance message.

[0409] The SMF and / or AMF may include one or more identification information items among at least identification information items 51 to 52 in the PDU session establishment acceptance message and transmit it. Note that the SMF and / or AMF may indicate that the network supports each function by transmitting this identification information item, or may indicate that the UE's request has been accepted. Furthermore, when multiple identification information items are transmitted and received, two or more of these identification information items may be configured as one or more identification information items. Note that the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information or as different identification information.

[0410] Furthermore, when the SMF and / or AMF authorizes the onboarding service, it may include one or more identification information from the identification information of 51 to 52 in the PDU session establishment acceptance message. Furthermore, when the SMF and / or AMF authorizes the establishment of a PDU session for the onboarding service, it may include one or more identification information from the identification information of 51 to 52 in the PDU session establishment acceptance message. Furthermore, when the SMF and / or AMF authorizes the use of the onboarding service, it may include one or more identification information from the identification information of 51 to 52 in the PDU session establishment acceptance message.

[0411] Furthermore, the SMF and / or AMF may include one or more identification information from the identification information 51 to 52 in the PDU session establishment accept message if the registration procedure for the onboarding service has been completed. Furthermore, the SMF and / or AMF may include one or more identification information from the identification information 51 to 52 in the PDU session establishment accept message if the registration that can only be used for the onboarding service has been completed.

[0412] Furthermore, the SMF and / or AMF may include one or more identities among the identities 51 to 52 in the PDU session establishment accept message when the UE is registered in a network for onboarding services, where the network for onboarding services may be an SNPN or a PLMN.

[0413] Furthermore, the SMF and / or AMF may include one or more identification information from the identification information in items 51 to 52 in the PDU session establishment accept message if it is necessary to provide SNPN information. Furthermore, the SMF and / or AMF may include one or more identification information from the identification information in items 51 to 52 in the PDU session establishment accept message if it is necessary to perform an onboarding service. Furthermore, the SMF and / or AMF may include one or more identification information from the identification information in items 51 to 52 in the PDU session establishment accept message if it is necessary to perform a procedure for providing SNPN information.

[0414] Furthermore, the SMF and / or AMF may include one or more of the identification information of identification information 51 to 52 in the PDU session establishment acceptance message if this procedure is a PDU session establishment procedure for an onboarding service.

[0415] Furthermore, the SMF and / or AMF may instruct the establishment of an Always-on PDU session as a PDU session for the onboarding service. In this case, the SMF and / or AMF may include the 51st identification information in the PDU session establishment accept message. More specifically, in this case, the SMF and / or AMF may include the 51st identification information indicating that an Always-on PDU session needs to be established in the PDU session establishment accept message. In other words, in this case, the SMF and / or AMF may include the 51st identification information indicating that the PDU session is to be established as an Always-on PDU session in the PDU session establishment accept message.

[0416] Furthermore, when the SMF and / or AMF authorizes the establishment of a PDU session for the onboarding service, the SMF and / or AMF may include the 52nd identification information in the PDU session establishment accept message. More specifically, in this case, the SMF and / or AMF may include the 51st identification information indicating that use of the onboarding service is authorized in the PDU session establishment accept message. In other words, in this case, the SMF and / or AMF may include the 51st identification information indicating that establishment of a PDU session for the onboarding service is authorized in the PDU session establishment accept message.

[0417] Furthermore, the SMF and / or AMF may indicate to the UE the content indicated by the identification information included in the PDU session establishment accept message by including one or more identification information from the identification information of identification numbers 51 to 52 in the PDU session establishment accept message. Furthermore, the SMF and / or AMF may indicate to the UE the content indicated by the identification information included in the PDU session establishment accept message by including one or more identification information from the identification information of identification numbers 51 to 52 in the PDU session establishment accept message.

[0418] Furthermore, the SMF and / or AMF may select and decide whether to include one or more of the identification information from items 51 to 52 in the PDU session establishment acceptance message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0419] The SMF and / or AMF may also include the selected and / or allowed PDU session ID in the PDU session establishment accept message. The SMF and / or AMF may also specify a PDU session type indicating the type of the selected and / or allowed PDU session. As described above, the PDU session type may be any of IPv4, IPv6, IPv4v6, Ethernet, and Unstructured. The SMF and / or AMF may also include the SSC mode of the selected and / or allowed PDU session in the PDU session establishment accept message.

[0420] Furthermore, the SMF and / or AMF may include the approved QoS rule set in the PDU session establishment accept message. The approved QoS rule set may include one or more QoS rules. Furthermore, if multiple QoS flows and / or user plane radio bearers are established in this procedure, the approved QoS rule set may include multiple QoS rules. Conversely, if only one QoS flow and / or one user plane radio bearer is established in this procedure, the approved QoS rule set may include one QoS rule.

[0421] Furthermore, the SMF may include information indicating that some of the UE's requests have been rejected in the PDU session establishment acceptance message and transmit it, or may indicate the reason why some of the UE's requests have been rejected by transmitting the information indicating that some of the UE's requests have been rejected. Furthermore, the UE may recognize the reason why some of the UE's requests have been rejected by receiving the information indicating that some of the UE's requests have been rejected. Note that the reason for the rejection may be information indicating that the content indicated by the identification information received by the SMF is not permitted.

[0422] Furthermore, if the SMF and / or AMF has already established a PDU session for the onboarding service, it may release the PDU session. More specifically, if the SMF and / or AMF has already established a PDU session for the onboarding service, it may perform a local release of the PDU session. Furthermore, if the SMF and / or AMF has already established a PDU session for the onboarding service, it may proceed with this procedure.

[0423] Furthermore, the SMF and / or AMF may release the PDU session for the onboarding service if this procedure is a PDU session establishment procedure for the onboarding service. More specifically, the SMF and / or AMF may perform a local release of the PDU session for the onboarding service if this procedure is a PDU session establishment procedure for the onboarding service. Furthermore, the SMF and / or AMF may proceed with this procedure if this procedure is a PDU session establishment procedure for the onboarding service.

[0424] Furthermore, the SMF and / or AMF may release the established PDU session when the registration procedure for the onboarding service is completed. Furthermore, the SMF and / or AMF may perform a local release of the established PDU session when the registration procedure for the onboarding service is completed.

[0425] Furthermore, the SMF and / or AMF may release the established PDU session when the onboarding service only enabled registration is completed. Furthermore, the SMF and / or AMF may perform a local release of the established PDU session when the onboarding service only enabled registration is completed.

[0426] Furthermore, the SMF and / or AMF may release an established PDU session when registered to the network for the onboarding service. Furthermore, the SMF and / or AMF may perform a local release of an established PDU session when registered to the network for the onboarding service.

[0427] Here, the established PDU session may be a PDU session for an onboarding service. Further, the established PDU session may be an Always-on PDU session.

[0428] The UE receives a PDU session establishment accept message from the SMF (S910) (S912). Specifically, after the PDU session establishment accept message is sent from the SMF to the AMF (S910), the UE receives a NAS message including the PDU session establishment accept message from the AMF via the N1 interface (S912). Based on receiving the PDU session establishment accept message and / or the NAS message including the PDU session establishment accept message, the UE may send a PDU session establishment complete message to the SMF via the AMF (S914) (S916). By receiving the PDU session establishment accept message, the UE can detect that the UE's request for PDU session establishment has been accepted.

[0429] Specifically, the UE sends a PDU session establishment completion message to the AMF via the N1 interface (S914). Upon receiving the PDU session establishment completion message from the UE, the AMF sends a PDU session establishment completion message to the SMF via the N11 interface (S916).

[0430] The PDU session establishment completion message sent by the AMF to the SMF may be a response message to the PDU session establishment acceptance message sent from the SMF to the AMF in S910. The PDU session establishment completion message may also be a NAS message. The PDU session establishment completion message may be any message indicating that the PDU session establishment procedure is completed.

[0431] When the SMF receives a PDU session establishment completion message from the AMF via the N11 interface (S916), it can perform a second condition determination. The second condition determination is for determining the type of message sent and received on the N4 interface. If the second condition determination is true, the SMF sends a session change request message to the UPF via the N4 interface (S918) and receives a session change accept message sent from the UPF as a response message (S920). If the second condition determination is false, the SMF sends a session establishment request message to the UPF via the N4 interface (S918) and receives a session change accept message sent from the UPF as a response message (S920).

[0432] The second condition determination may be performed based on whether a session on the N4 interface for the PDU session is established. For example, if a session on the N4 interface for the PDU session is established, the second condition determination may be true, and if a session on the N4 interface for the PDU session is not established, the second condition determination may be false. The conditions for determining whether the second condition determination is true or false do not have to be limited to the above-described conditions.

[0433] Each device completes the procedure (A) during the PDU session establishment procedure based on the transmission and reception of a PDU session establishment completion message, and / or the transmission and reception of a session modification response message, and / or the transmission and reception of a session establishment response message. When the procedure (A) during this procedure is completed, the UE is in a state where a PDU session for the DN is established.

[0434] Next, each step of procedure (B) during the PDU session establishment procedure will be described. The SMF sends a PDU session establishment reject message to the UE via the AMF (S922) (S924). Specifically, the SMF sends a PDU session establishment reject message to the AMF via the N11 interface (S922). When the AMF receives a PDU session establishment request message from the SMF via the N11 interface (S922), it sends a PDU session establishment reject message to the UE using the N1 interface (S924).

[0435] The PDU session establishment rejection message may be a NAS message or an SM message sent from the SMF to the UE. The PDU session establishment rejection message may be any message indicating that the establishment of a PDU session has been rejected. The PDU session establishment rejection message may be transmitted and received via the N1 interface, being included in an MM message. The MM message may be a NAS message or a downlink NAS transport (DL NAS TRANSPORT) message. Here, the expression "identification information and / or values ​​are included in the PDU session establishment rejection message" may mean that the identification information and / or values ​​are included in the MM message containing the PDU session establishment rejection message.

[0436] Here, the SMF may indicate that the UE's request for PDU session establishment has been rejected by transmitting a PDU session establishment rejection message. Furthermore, the SMF may include information indicating the reason for the rejection in the PDU session establishment rejection message, or may indicate the reason for the rejection by transmitting the reason for the rejection. Furthermore, the UE may recognize the reason for the rejection of the UE's request by receiving information indicating the reason for the rejection. Note that the reason for the rejection may be information indicating that the content indicated by the identification information received by the SMF is not permitted.

[0437] The SMF and / or AMF may include one or more identification information and / or back-off timer values ​​in the PDU session establishment rejection message and may indicate that the UE request has been rejected or the reason why the UE request has been rejected by sending these identification information and / or back-off timer values.

[0438] Furthermore, the SMF and / or AMF may transmit a back-off timer value to instruct the UE to set the back-off timer value to the transmitted value, or may instruct the UE to start a back-off timer set to the transmitted value.

[0439] Furthermore, if the SMF and / or AMF has already established a PDU session for the onboarding service, it may release the PDU session. More specifically, if the SMF and / or AMF has already established a PDU session for the onboarding service, it may perform a local release of the PDU session. Furthermore, if the SMF and / or AMF has already established a PDU session for the onboarding service, it may include a cause value in the PDU session establishment rejection message.

[0440] Furthermore, the SMF and / or AMF may release the PDU session for the onboarding service if this procedure is a PDU session establishment procedure for the onboarding service. More specifically, the SMF and / or AMF may perform a local release of the PDU session for the onboarding service if this procedure is a PDU session establishment procedure for the onboarding service. Furthermore, the SMF and / or AMF may include a cause value in the PDU session establishment rejection message if this procedure is a PDU session establishment procedure for the onboarding service.

[0441] Furthermore, the SMF and / or AMF may release the established PDU session when the registration procedure for the onboarding service is completed. Furthermore, the SMF and / or AMF may perform a local release of the established PDU session when the registration procedure for the onboarding service is completed.

[0442] Furthermore, the SMF and / or AMF may release the established PDU session when the onboarding service only enabled registration is completed. Furthermore, the SMF and / or AMF may perform a local release of the established PDU session when the onboarding service only enabled registration is completed.

[0443] Furthermore, the SMF and / or AMF may release an established PDU session when registered to the network for the onboarding service. Furthermore, the SMF and / or AMF may perform a local release of an established PDU session when registered to the network for the onboarding service.

[0444] Here, the established PDU session may be a PDU session for an onboarding service. Further, the established PDU session may be an Always-on PDU session.

[0445] Here, the reason value may be a 5GSM reason value. Furthermore, the reason value may be information indicating that a PDU session cannot be established. Furthermore, the reason value may be information indicating that establishment of a PDU session is prohibited.

[0446] Furthermore, the reason value may be information indicating that a PDU session for an onboarding service cannot be established. Furthermore, the reason value may be information indicating that a PDU session for an onboarding service is prohibited from being established.

[0447] Furthermore, the SMF and / or AMF may select and decide whether to include one or more identification information in the PDU session establishment rejection message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0448] By receiving the PDU session establishment rejection message, the UE can recognize that the UE's request for PDU session establishment has been rejected, and the contents of the various identification information included in the PDU session establishment rejection message.

[0449] Each device completes the PDU session establishment procedure based on the completion of the procedure of (A) or (B) in Figure 8. Note that each device may transition to a state in which the PDU session is established based on the completion of the procedure of (A) in Figure 8, or may recognize that the PDU session establishment procedure has been rejected based on the completion of the procedure of (B) in Figure 8, and may transition to a state in which the PDU session is not established. Furthermore, upon completion of the procedure of (A) in Figure 8, the UE can communicate with the DN using the established PDU session.

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

[0451] Furthermore, the UE may store the identification information received along with the PDU session establishment accept message and / or the PDU session establishment reject message and may recognize the network's decision based on the completion of the PDU session establishment procedure.

[0452] For example, the UE may recognize that the onboarding service is authorized if it receives one or more identities from identities 51 to 52. Furthermore, the UE may recognize that establishment of a PDU session for the onboarding service is authorized if it receives one or more identities from identities 51 to 52. Furthermore, the UE may recognize that use of the onboarding service is authorized if it receives one or more identities from identities 51 to 52.

[0453] Furthermore, the UE may recognize that the network's SNPN information can be provided using the PDU session when it receives one or more of the identification information from identification numbers 51 to 52. Furthermore, the UE may recognize that the network's SNPN information can be provided using the PDU session when it receives one or more of the identification information from identification numbers 51 to 52. Furthermore, the UE may recognize that the network's SNPN information can be provided using the PDU session when it receives one or more of the identification information from identification numbers 51 to 52.

[0454] Furthermore, the UE may establish a PDU session for the onboarding service when it receives the PDU session accept message. Furthermore, the UE may establish an Always-on PDU session when it receives the PDU session accept message. Furthermore, the UE may establish an Always-on PDU session as the PDU session for the onboarding service when it receives the PDU session accept message.

[0455] Furthermore, when the UE receives the PDU session accept message, the UE may recognize that the PDU session to be established is a PDU session for an onboarding service. Furthermore, when the UE receives the PDU session accept message, the UE may recognize that the PDU session to be established is an Always-on PDU session.

[0456] Furthermore, the UE may establish a PDU session for the onboarding service when this procedure is a PDU session establishment procedure for the onboarding service. Furthermore, the UE may establish an Always-on PDU session when this procedure is a PDU session establishment procedure for the onboarding service. Furthermore, the UE may establish an Always-on PDU session as a PDU session for the onboarding service when this procedure is a PDU session establishment procedure for the onboarding service.

[0457] Furthermore, the UE may recognize that the PDU session to be established is a PDU session for an onboarding service if the procedure is a PDU session establishment procedure for an onboarding service. Furthermore, the UE may recognize that the PDU session to be established is an Always-on PDU session if the procedure is a PDU session establishment procedure for an onboarding service.

[0458] Furthermore, the UE may establish a PDU session for the onboarding service when the registration procedure for the onboarding service is completed. Furthermore, the UE may establish an Always-on PDU session when the registration procedure for the onboarding service is completed. Furthermore, the UE may establish an Always-on PDU session as a PDU session for the onboarding service when the registration procedure for the onboarding service is completed.

[0459] Furthermore, the UE may recognize that the PDU session to be established is a PDU session for the onboarding service when the registration procedure for the onboarding service is completed. Furthermore, the UE may recognize that the PDU session to be established is an Always-on PDU session when the registration procedure for the onboarding service is completed.

[0460] Furthermore, the UE may establish a PDU session for the onboarding service when registration allowing only the onboarding service is completed. Furthermore, the UE may establish an Always-on PDU session when registration allowing only the onboarding service is completed. Furthermore, the UE may establish an Always-on PDU session as a PDU session for the onboarding service when registration allowing only the onboarding service is completed.

[0461] Furthermore, the UE may recognize that the PDU session to be established is a PDU session for the onboarding service when the registration that allows only the onboarding service is completed. Furthermore, the UE may recognize that the PDU session to be established is an Always-on PDU session when the registration that allows only the onboarding service is completed.

[0462] Furthermore, the UE may establish a PDU session for the onboarding service when registered with the network for the onboarding service. Furthermore, the UE may establish an Always-on PDU session when registered with the network for the onboarding service. Furthermore, the UE may establish an Always-on PDU session as a PDU session for the onboarding service when registered with the network for the onboarding service.

[0463] Furthermore, the UE may recognize that the PDU session to be established is a PDU session for the onboarding service when registered with the network for the onboarding service. Furthermore, the UE may recognize that the PDU session to be established is an Always-on PDU session when registered with the network for the onboarding service.

[0464] Furthermore, the UE may establish a PDU session for the onboarding service when it receives one or more identification information from identification numbers 51 to 52. Furthermore, the UE may establish an Always-on PDU session when it receives one or more identification information from identification numbers 51 to 52. Furthermore, the UE may establish an Always-on PDU session as a PDU session for the onboarding service when it receives one or more identification information from identification numbers 51 to 52.

[0465] Furthermore, the UE may recognize that the PDU session to be established is a PDU session for an onboarding service when it receives one or more identification information from identification information Nos. 51 to 52. Furthermore, the UE may recognize that the PDU session to be established is an Always-on PDU session when it receives one or more identification information from identification information Nos. 51 to 52.

[0466] Furthermore, the UE may establish an Always-on PDU session if it receives the 51st identification. More specifically, the UE may establish an Always-on PDU session if it receives the 51st identification indicating that an Always-on PDU session needs to be established. Furthermore, the UE may establish an Always-on PDU session if it receives the 51st identification indicating that the PDU session is to be established as an Always-on PDU session.

[0467] Furthermore, the UE may recognize that the PDU session to be established is an Always-on PDU session when it receives the 51st identification. More specifically, the UE may recognize that the PDU session to be established is an Always-on PDU session when it receives the 51st identification indicating that an Always-on PDU session needs to be established. Furthermore, the UE may recognize that the PDU session to be established is an Always-on PDU session when it receives the 51st identification indicating that the PDU session is to be established as an Always-on PDU session.

[0468] Furthermore, the UE may establish a PDU session for the onboarding service if it receives the 52nd identification information. More specifically, the UE may establish a PDU session for the onboarding service if it receives the 51st identification information indicating that use of the onboarding service is authorized. Furthermore, the UE may establish a PDU session for the onboarding service if it receives the 51st identification information indicating that establishment of a PDU session for the onboarding service is authorized.

[0469] Furthermore, the UE may recognize that the PDU session to be established is a PDU session for the onboarding service when it receives the 52nd identification information. More specifically, the UE may recognize that the PDU session to be established is a PDU session for the onboarding service when it receives the 51st identification information indicating that use of the onboarding service is authorized. Furthermore, the UE may recognize that the PDU session to be established is a PDU session for the onboarding service when it receives the 51st identification information indicating that establishment of the PDU session for the onboarding service is authorized.

[0470] Furthermore, when the UE receives one or more of the identification information from identification numbers 51 to 52, the UE may recognize the content indicated by the received identification information. Furthermore, when the UE receives one or more of the identification information from identification numbers 51 to 52, the UE may recognize that the content indicated by the identification information included in the PDU session establishment accept message is permitted.

[0471] Furthermore, when the UE receives a back-off timer value, the UE may set the back-off timer to the back-off timer value, or may start the back-off timer set to the received back-off timer value.

[0472] Furthermore, the UE may recognize that establishment of a new PDU session is prohibited based on the completion of the PDU session establishment procedure. Furthermore, the UE may configure that establishment of a new PDU session is prohibited based on the completion of the PDU session establishment procedure. Furthermore, the UE may configure that transmission of a PDU session establishment request message is prohibited based on the completion of the PDU session establishment procedure.

[0473] In other words, the UE may configure the PDU session establishment procedure so that a new PDU session establishment procedure is not initiated based on the completion of the PDU session establishment procedure.Furthermore, the UE may configure the PDU session establishment request message is not transmitted based on the completion of the PDU session establishment procedure.

[0474] Specifically, the UE may recognize that the establishment of a new PDU session is prohibited when it receives the PDU session establishment acceptance message. Furthermore, the UE may configure the UE to prohibit the establishment of a new PDU session when it receives the PDU session establishment acceptance message. Furthermore, the UE may configure the UE to prohibit the transmission of a PDU session establishment request message when it receives the PDU session establishment acceptance message.

[0475] In other words, the UE may be configured to not initiate a new PDU session establishment procedure when it receives a PDU session establishment accept message, and may also be configured to not transmit a PDU session establishment request message when it receives a PDU session establishment accept message.

[0476] Furthermore, the UE may recognize that establishment of a new PDU session is prohibited when this procedure is a PDU session establishment procedure for an onboarding service. Furthermore, the UE may configure that establishment of a new PDU session is prohibited when this procedure is a PDU session establishment procedure for an onboarding service. Furthermore, the UE may configure that transmission of a PDU session establishment request message is prohibited when this procedure is a PDU session establishment procedure for an onboarding service.

[0477] In other words, the UE may configure the PDU session establishment procedure so that a new PDU session establishment procedure is not initiated when the procedure is a PDU session establishment procedure for an onboarding service.Furthermore, the UE may configure the PDU session establishment request message is not transmitted when the procedure is a PDU session establishment procedure for an onboarding service.

[0478] The period during which the establishment of a new PDU session is prohibited may be a period managed by a timer. In other words, the UE may be configured so that the establishment of a new PDU session is not prohibited based on the expiration of the timer.

[0479] Furthermore, the period during which the establishment of a new PDU session is prohibited may be until a new registration procedure and / or a deregistration procedure is performed. In other words, the UE may be configured so that the establishment of a new PDU session is not prohibited based on the execution of a new registration procedure and / or a deregistration procedure.

[0480] Furthermore, the period during which the establishment of a new PDU session is prohibited may be until the UE is powered off and / or until the USIM is removed. In other words, the UE may be configured so that the establishment of a new PDU session is not prohibited based on the powering off and / or removal of the USIM.

[0481] Furthermore, the area in which the establishment of a new PDU session is prohibited may be within the same network. In other words, the UE may be configured not to prohibit the establishment of a new PDU session based on movement to another network. More specifically, the UE may be configured not to prohibit the establishment of a new PDU session based on movement to another PLMN or another SNPN.

[0482] Here, the new PDU session may refer to a PDU session for a newly established onboarding service. In other words, the PDU session established by the new PDU session establishment procedure may be a PDU session for an onboarding service.

[0483] Furthermore, when it is expressed that the establishment of a new PDU session is prohibited, it may mean that the establishment of a new PDU session for an onboarding service is prohibited. In other words, setting a new PDU session establishment procedure not to be initiated may mean setting a PDU session establishment procedure for establishing a new PDU session for an onboarding service not to be initiated.

[0484] Furthermore, if the UE executes this procedure while a PDU session for the onboarding service has already been established, the UE may release the PDU session. In other words, if the UE executes the PDU session establishment procedure for the onboarding service while a PDU session for the onboarding service has already been established, the UE may release the PDU session.

[0485] More specifically, if the UE executes this procedure while a PDU session for an onboarding service has already been established, the UE may perform a local release of the PDU session. In other words, if the UE executes the PDU session establishment procedure while a PDU session for an onboarding service has already been established, the UE may perform a local release of the PDU session.

[0486] Furthermore, the UE may release the PDU session for the onboarding service if this procedure is a PDU session establishment procedure for the onboarding service. In other words, the UE may release the established PDU session if this procedure is a PDU session establishment procedure for the onboarding service.

[0487] More specifically, if the procedure is a PDU session establishment procedure for an onboarding service, the UE may perform a local release of the PDU session for the onboarding service. In other words, if the procedure is a PDU session establishment procedure for an onboarding service, the UE may perform a local release of the established PDU session.

[0488] Furthermore, if the UE executes a new PDU session establishment procedure while a PDU session for an onboarding service has already been established, the UE may release the PDU session. In other words, if the UE executes a PDU session establishment procedure for a new onboarding service while a PDU session for an onboarding service has already been established, the UE may release the PDU session.

[0489] More specifically, if the UE executes a new PDU session establishment procedure while a PDU session for an onboarding service has already been established, the UE may perform local release of the PDU session. In other words, if the UE executes a PDU session establishment procedure for a new onboarding service while a PDU session for an onboarding service has already been established, the UE may perform local release of the PDU session.

[0490] Furthermore, the UE may release the established PDU session when the new PDU session establishment procedure is performed after the registration procedure for the onboarding service is completed. Furthermore, the UE may perform a local release of the established PDU session when the new PDU session establishment procedure is performed after the registration procedure for the onboarding service is completed.

[0491] Furthermore, the UE may release the established PDU session when a new PDU session establishment procedure is performed in a state where registration only for onboarding services is completed. Furthermore, the UE may perform a local release of the established PDU session when a new PDU session establishment procedure is performed in a state where registration only for onboarding services is completed.

[0492] Furthermore, the UE may release the established PDU session when it performs a new PDU session establishment procedure while registered with the network for the onboarding service. Furthermore, the UE may perform a local release of the established PDU session when it performs a new PDU session establishment procedure while registered with the network for the onboarding service.

[0493] Here, the established PDU session may be a PDU session for an onboarding service. Further, the established PDU session may be an Always-on PDU session.

[0494] 3.2.3. Non-registration Procedures Next, the de-registration procedure will be described. Hereinafter, the de-registration procedure will also be referred to as this procedure. The de-registration procedure is a procedure initiated by the UE or the network to cancel the registration of the UE. The de-registration procedure may be a procedure to change the state of the UE to the unregistered state.

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

[0496] Furthermore, a device in the core network, such as the AMF, may initiate this procedure based on an update to the network configuration and / or an update to the operator policy. The trigger for this procedure may be detection of UE mobility, detection of a change in the status of the UE, the access network, and / or the core network, or a change in the status of a network slice. The trigger for this procedure may be reception of a request from the DN and / or the DN's application server, a change in the network configuration, or a change in the operator policy. The trigger for this procedure may also be expiration of a running timer. The triggers for the device in the core network to initiate this procedure are not limited to these. Furthermore, this procedure may be performed at any time as long as each device has established a 5GMM context and / or is in 5GMM connected mode.

[0497] Furthermore, the trigger for this procedure may be the completion of the SNPN information provision procedure. In other words, the trigger for this procedure may be the completion of the SNPN information provision. Furthermore, the trigger for this procedure may be the completion of the onboarding service.

[0498] Furthermore, the trigger for this procedure may be the expiration of a timer. Here, the timer may be a timer managed by the UE and / or the network. More specifically, the timer may be a timer indicating a time limit during which a registration that can be used only for onboarding services is valid. In other words, the timer may be a timer indicating a time limit during which the SNPN information provision procedure can be performed.

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

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

[0501] The unregistration procedure is classified into a network-initiated unregistration procedure and a UE-initiated unregistration procedure. The network-initiated unregistration procedure and the UE-initiated unregistration procedure will be explained below.

[0502] 3.2.3.1. Network-Initiated Deregistration Procedures First, the network-initiated de-registration procedure will be explained using Figure 9. Hereinafter, the network-initiated de-registration procedure will also be referred to as this procedure. The network-initiated de-registration procedure is a de-registration procedure that is initiated by the network. Each step of this procedure will be explained below.

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

[0504] The AMF may transmit at least 31st identification information in the registration accept message. By transmitting these identification information, the AMF may indicate the reason for deregistration of the UE or the need for network reselection. Furthermore, two or more of these identification information may be configured as one or more identification information. Furthermore, the information indicating support of each function and the information indicating a request for use of each function may be transmitted and received as the same identification information or as different identification information.

[0505] The AMF may include the 31st identity information in the unregistration request message when the onboarding service is completed. Further, the AMF may include the 31st identity information in the unregistration request message when the SNPN information provision procedure is completed.

[0506] Furthermore, the AMF may include the 31st identity information in the non-registration request message if the onboarding service is not completed. Further, the AMF may include the 31st identity information in the non-registration request message if the SNPN information provision procedure is not completed.

[0507] Furthermore, the AMF may include the 31st identity information in the non-registration request message if the onboarding service is successful. Further, the AMF may include the 31st identity information in the non-registration request message if the SNPN information provision procedure is successful. Further, the AMF may include the 31st identity information in the non-registration request message if the SNPN information provision is successful.

[0508] Furthermore, the AMF may include the 31st identity in the non-registration request message if the onboarding service fails. Further, the AMF may include the 31st identity in the non-registration request message if the SNPN information provision procedure fails. Further, the AMF may include the 31st identity in the non-registration request message if the SNPN information provision fails.

[0509] Furthermore, the AMF may include the 31st identity in the unregistration request message if a timer managed by the UE and / or the network expires. Further, the AMF may include the 31st identity in the unregistration request message if a registration available only for onboarding services is no longer valid.

[0510] Furthermore, the AMF may include the 31st identity in the non-registration request message if the provision of SNPN information is not possible. Further, the AMF may include the 31st identity in the non-registration request message if the execution of an onboarding service is not possible. Further, the AMF may include the 31st identity in the non-registration request message if the execution of a procedure for providing SNPN information is not possible.

[0511] Furthermore, if the onboarding service is completed, the AMF may include a 31st identification information indicating that the onboarding service is completed in the non-registration request message. Further, if the SNPN information provision procedure is completed, the AMF may include a 31st identification information indicating that the SNPN information provision procedure is completed in the non-registration request message.

[0512] Furthermore, if the onboarding service is not completed, the AMF may include in the non-registration request message a 31st identification indicating that the onboarding service is not completed. Further, if the SNPN information provision procedure is not completed, the AMF may include in the non-registration request message a 31st identification indicating that the SNPN information provision procedure is not completed.

[0513] Furthermore, if the onboarding service is successful, the AMF may include in the non-registration request message a 31st identity indicating that the onboarding service is successful.Furthermore, if the SNPN information provision procedure is successful, the AMF may include in the non-registration request message a 31st identity indicating that the SNPN information provision procedure is successful.Furthermore, if the SNPN information provision is successful, the AMF may include in the non-registration request message a 31st identity indicating that the SNPN information provision is successful.

[0514] Furthermore, if the onboarding service fails, the AMF may include in the non-registration request message a 31st identity indicating that the onboarding service has failed.Furthermore, if the SNPN information provision procedure has failed, the AMF may include in the non-registration request message a 31st identity indicating that the SNPN information provision procedure has failed.Furthermore, if the SNPN information provision has failed, the AMF may include in the non-registration request message a 31st identity indicating that the SNPN information provision has failed.

[0515] Furthermore, when a timer managed by the UE and / or the network expires, the AMF may include in the unregistration request message a 31st identification indicating that the timer has expired. Furthermore, when a registration available for only the onboarding service is no longer valid, the AMF may include in the unregistration request message a 31st identification indicating that the registration available for only the onboarding service is no longer valid.

[0516] Furthermore, the AMF may indicate to the UE the content indicated by the identification information included in the non-registration request message by including the 31st identification information in the non-registration request message. Furthermore, the AMF may not permit the UE to access the content indicated by the identification information included in the non-registration request message by including the 31st identification information in the non-registration request message.

[0517] Furthermore, the AMF may select and decide whether to include the 31st identification information in the non-registration request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

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

[0519] The UE receives a deregistration request message via a 5G AN (gNB) (S1100). The UE may recognize the reason for deregistration of the UE based on the deregistration request message and / or identification information included in the deregistration request message, and may perform network reselection. Furthermore, the UE may transmit a deregistration accept message to the AMF via the 5G AN (gNB) as a response message to the deregistration request message based on the identification information included in the deregistration request message (S1102).

[0520] When the UE sends a non-registration acceptance message, the AMF receives the non-registration acceptance message via the 5G AN (gNB) (S1102). In addition, each device completes this procedure based on the transmission and reception of the non-registration request message and / or the non-registration acceptance message.

[0521] In addition, each of the processes performed by the UE based on the reception of each identification information shown above may be performed during this procedure or after completion of this procedure, or may be performed after completion of this procedure based on the completion of this procedure.

[0522] Furthermore, each device may perform processing based on the information transmitted and received in this procedure based on the completion of this procedure. For example, if an update to the configuration information is transmitted and received, each device may release the context of the UE. Furthermore, if information indicating that a network reselection and / or registration procedure is required is transmitted and received, the UE may initiate a network reselection and / or registration procedure based on the completion of this procedure.

[0523] Furthermore, the UE may store the identification information received with the unregistration request message and may recognize the network's decision based on the completion of this procedure.

[0524] For example, when the UE receives the 31st identification information, the UE may recognize that the onboarding service is completed. Furthermore, when the UE receives the 31st identification information, the UE may recognize that the SNPN information provision procedure is completed.

[0525] Furthermore, when the UE receives the 31st identification information, the UE may recognize that the onboarding service has not been completed. Furthermore, when the UE receives the 31st identification information, the UE may recognize that the SNPN information provision procedure has not been completed.

[0526] Furthermore, when the UE receives the 31st identification information, the UE may determine whether the onboarding service is completed. Furthermore, when the UE receives the 31st identification information, the UE may determine whether the SNPN information provision procedure is completed.

[0527] Furthermore, the UE may recognize that the onboarding service has been successful if the 31st identification information is received. Furthermore, the UE may recognize that the SNPN information provision procedure has been successful if the 31st identification information is received. Furthermore, the UE may recognize that the SNPN information provision and / or acquisition has been successful if the 31st identification information is received.

[0528] Furthermore, the UE may recognize that the onboarding service has failed if it receives the 31st identification information. Furthermore, the UE may recognize that the SNPN information provision procedure has failed if it receives the 31st identification information. Furthermore, the UE may recognize that the provision and / or acquisition of SNPN information has failed if it receives the 31st identification information.

[0529] Furthermore, when the UE receives the 31st identification information, it may determine whether the onboarding service is successful or unsuccessful. Furthermore, when the UE receives the 31st identification information, it may determine whether the SNPN information provision procedure is successful or unsuccessful. Furthermore, when the UE receives the 31st identification information, it may determine whether the provision and / or acquisition of the SNPN information is successful or unsuccessful.

[0530] Furthermore, when the UE receives the 31st identification information, the UE may recognize that a timer managed by the UE and / or the network has expired. Furthermore, when the UE receives the 31st identification information, the UE may recognize that the registration that can only be used for onboarding services is no longer valid.

[0531] Furthermore, the UE may recognize that provision and / or acquisition of SNPN information is not possible when receiving the 31st identification information. Furthermore, the UE may recognize that execution of an onboarding service is not possible when receiving the 31st identification information. Furthermore, the UE may recognize that execution of a procedure for providing SNPN information is not possible when receiving the 31st identification information.

[0532] Furthermore, the UE may recognize that the onboarding service is completed when it receives 31st identification information indicating that the onboarding service is completed. Furthermore, the UE may recognize that the SNPN information provision procedure is completed when it receives 31st identification information indicating that the SNPN information provision procedure is completed.

[0533] Furthermore, the UE may recognize that the onboarding service has not been completed if it receives 31st identification information indicating that the onboarding service has not been completed.Furthermore, the UE may recognize that the SNPN information provision procedure has not been completed if it receives 31st identification information indicating that the SNPN information provision procedure has not been completed.

[0534] Furthermore, the UE may recognize that the onboarding service is successful when receiving 31st identification information indicating that the onboarding service is successful.Further, the UE may recognize that the SNPN information provision procedure is successful when receiving 31st identification information indicating that the SNPN information provision procedure is successful.Further, the UE may recognize that the SNPN information provision and / or acquisition is successful when receiving 31st identification information indicating that the SNPN information provision is successful.

[0535] Furthermore, the UE may recognize that the onboarding service has failed if it receives 31st identification information indicating that the onboarding service has failed. Further, the UE may recognize that the SNPN information provision procedure has failed if it receives 31st identification information indicating that the SNPN information provision procedure has failed. Further, the UE may recognize that the provision and / or acquisition of SNPN information has failed if it receives 31st identification information indicating that the SNPN information provision has failed.

[0536] Furthermore, the UE may recognize that a timer managed by the UE and / or the network has expired if it receives a 31st identification indicating that the timer has expired. Furthermore, the UE may recognize that a registration capable of using only the onboarding service has expired if it receives a 31st identification indicating that the registration capable of using only the onboarding service has expired.

[0537] Furthermore, when the UE receives the 31st identification information, the UE may recognize the content indicated by the received identification information. Furthermore, when the UE receives the 31st identification information, the UE may recognize that the content indicated by the received identification information is not permitted.

[0538] Furthermore, the UE may release or delete the first list when receiving the 31st identification information. Furthermore, the UE may delete the network identification information from the first list when receiving the 31st identification information.

[0539] More specifically, when the UE receives the 31st identification information indicating that the onboarding service is completed, the UE may release or delete the first list. Furthermore, when the UE receives the 31st identification information indicating that the SNPN information provision procedure is completed, the UE may release or delete the first list.

[0540] Furthermore, the UE may release or delete the first list when receiving 31st identification information indicating that the onboarding service is successful. Furthermore, the UE may release or delete the first list when receiving 31st identification information indicating that the SNPN information provision procedure is successful. Furthermore, the UE may release or delete the first list when receiving 31st identification information indicating that the SNPN information provision is successful.

[0541] Furthermore, the UE may release or delete the first list when the onboarding service is completed. Furthermore, the UE may release or delete the first list when the procedure for providing SNPN information is completed. Furthermore, the UE may release or delete the first list when the acquisition of SNPN information is completed.

[0542] Furthermore, the UE may release or delete the first list if the onboarding service is successful. Furthermore, the UE may release or delete the first list if the SNPN information provision procedure is successful. Furthermore, the UE may release or delete the first list if the SNPN information is successfully acquired.

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

[0544] For example, if the procedure is performed in a first network, the network identity may be information identifying the first network. More particularly, if the procedure is performed in a first PLMN, the network identity may be information identifying the first PLMN. Furthermore, if the procedure is performed in a first SNPN, the network identity may be information identifying the first SNPN.

[0545] Furthermore, the UE may perform a second network selection when receiving the 31st identification information. Furthermore, the UE may perform a second network selection and select a target SNPN when receiving the 31st identification information. Furthermore, the UE may initiate a registration procedure in the selected new network after completing the second network selection.

[0546] More specifically, the UE may perform the second network selection when receiving the 31st identification information indicating that the onboarding service has been completed. Further, the UE may perform the second network selection when receiving the 31st identification information indicating that the SNPN information providing procedure has been completed.

[0547] Furthermore, the UE may perform a second network selection when receiving a 31st identification information indicating that the onboarding service is successful. Furthermore, the UE may perform a second network selection when receiving a 31st identification information indicating that the SNPN information provision procedure is successful. Furthermore, the UE may perform a second network selection when receiving a 31st identification information indicating that the SNPN information provision is successful.

[0548] Conversely, when the UE receives the 31st identification information, the UE may add the identification information of the network to the first list. Furthermore, when the UE receives the 31st identification information, the UE may create a first list and add the identification information of the network to the created first list.

[0549] More specifically, when the UE receives the 31st identification information indicating that the onboarding service has not been completed, the UE may add the network identification information to the first list. Furthermore, when the UE receives the 31st identification information indicating that the SNPN information provision procedure has not been completed, the UE may add the network identification information to the first list.

[0550] Furthermore, the UE may add the network identification information to the first list when receiving 31st identification information indicating that the onboarding service has failed. Further, the UE may add the network identification information to the first list when receiving 31st identification information indicating that the SNPN information provision procedure has failed. Further, the UE may add the network identification information to the first list when receiving 31st identification information indicating that the SNPN information provision has failed.

[0551] Furthermore, the UE may add the network identification information to the first list when receiving a 31st identification information indicating that the timer has expired. Furthermore, the UE may add the network identification information to the first list when receiving a 31st identification information indicating that the onboarding service-only registration is no longer valid.

[0552] Furthermore, the UE may add the identification information of the network to the first list if the onboarding service has not been completed. Furthermore, the UE may add the identification information of the network to the first list if the procedure for providing SNPN information has not been completed. Furthermore, the UE may add the identification information of the network to the first list if the acquisition of SNPN information has not been completed.

[0553] Furthermore, the UE may add the network identification information to the first list if the onboarding service fails. Further, the UE may add the network identification information to the first list if the SNPN information provision procedure fails. Further, the UE may add the network identification information to the first list if the SNPN information acquisition procedure fails.

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

[0555] For example, if the procedure is performed in a first network, the network identity may be information identifying the first network. More particularly, if the procedure is performed in a first PLMN, the network identity may be information identifying the first PLMN. Furthermore, if the procedure is performed in a first SNPN, the network identity may be information identifying the first SNPN.

[0556] Furthermore, the UE may re-perform the first network selection when receiving the 31st identification information. Furthermore, the UE may re-perform the first network selection when receiving the 31st identification information, and may select a network other than the network in which it is currently located. Furthermore, the UE may initiate a registration procedure in the selected new network after completing the re-performed first network selection.

[0557] More specifically, the UE may re-perform the first network selection if it receives the 31st identification information indicating that the onboarding service has not been completed. Furthermore, the UE may re-perform the first network selection if it receives the 31st identification information indicating that the SNPN information provision procedure has not been completed.

[0558] Furthermore, the UE may re-perform the first network selection if it receives 31st identification information indicating that the onboarding service has failed. Furthermore, the UE may re-perform the first network selection if it receives 31st identification information indicating that the SNPN information provision procedure has failed. Furthermore, the UE may re-perform the first network selection if it receives 31st identification information indicating that the SNPN information provision has failed.

[0559] Furthermore, the UE may re-perform the first network selection if it receives a 31st identification indicating that the timer has expired. Furthermore, the UE may re-perform the first network selection if it receives a 31st identification indicating that the onboarding service-only registration is no longer valid.

[0560] Furthermore, when the UE receives the 31st identification information, the UE may start a timer, where the timer may indicate a time limit for managing the first list. In other words, the UE may release or delete the first list based on the expiration of the timer.

[0561] Furthermore, the timer may be a timer indicating a time limit for prohibiting the registration procedure, In other words, the UE may start the registration procedure based on the expiration of the timer.

[0562] Note that the behavior to be performed when each piece of identification information is received may be performed based on the received identification information. For example, the behavior to be performed when the 31st identification information is received may be performed based on the received 31st identification information.

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

[0564] 3.2.3.2. UE-initiated de-registration procedure First, the UE-initiated de-registration procedure will be explained using FIG. 10. Hereinafter, the UE-initiated de-registration procedure will also be referred to as this procedure. The UE-initiated de-registration procedure is a de-registration procedure that is initiated by the UE. Each step of this procedure will be explained below.

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

[0566] The UE may transmit at least 31 identification information in the registration accept message. By transmitting this identification information, the UE may indicate the reason for deregistration of the UE or the need for network reselection. Furthermore, two or more of these identification information may be configured as one or more identification information. Furthermore, the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information or as different identification information.

[0567] When the onboarding service is completed, the UE may include the 31st identification information in the non-registration request message. Furthermore, when the UE completes the SNPN information provision procedure, the 31st identification information may be included in the non-registration request message.

[0568] Furthermore, if the onboarding service is not completed, the UE may include the 31st identification information in the non-registration request message. Furthermore, if the UE does not complete the SNPN information provision procedure, the 31st identification information may be included in the non-registration request message.

[0569] Furthermore, the UE may include the 31st identity information in the non-registration request message if the onboarding service is successful. Furthermore, the UE may include the 31st identity information in the non-registration request message if the SNPN information provision procedure is successful. Furthermore, the UE may include the 31st identity information in the non-registration request message if the SNPN information provision and / or acquisition is successful.

[0570] Furthermore, the UE may include the 31st identity information in the non-registration request message if the onboarding service fails. Further, the UE may include the 31st identity information in the non-registration request message if the procedure for providing SNPN information fails. Further, the UE may include the 31st identity information in the non-registration request message if the provision and / or acquisition of SNPN information fails.

[0571] Furthermore, the UE may include the 31st identity in the unregistration request message if a timer managed by the UE and / or the network expires. Furthermore, the UE may include the 31st identity in the unregistration request message if a registration available only for onboarding services is no longer valid.

[0572] Furthermore, the UE may include the 31st identity information in the non-registration request message if it is not capable of providing and / or obtaining SNPN information. Furthermore, the UE may include the 31st identity information in the non-registration request message if it is not capable of performing an onboarding service. Furthermore, the UE may include the 31st identity information in the non-registration request message if it is not capable of performing a procedure for providing SNPN information.

[0573] Furthermore, when the onboarding service is completed, the UE may include, in the non-registration request message, a 31st identification information indicating that the onboarding service is completed. Furthermore, when the UE completes the SNPN information provision procedure, the UE may include, in the non-registration request message, a 31st identification information indicating that the SNPN information provision procedure is completed.

[0574] Furthermore, if the onboarding service is not completed, the UE may include, in the non-registration request message, 31st identification information indicating that the onboarding service is not completed. Furthermore, if the UE does not complete the SNPN information provision procedure, the UE may include, in the non-registration request message, 31st identification information indicating that the SNPN information provision procedure is not completed.

[0575] Furthermore, if the onboarding service is successful, the UE may include, in the non-registration request message, 31st identification information indicating that the onboarding service is successful. Furthermore, if the procedure for providing the SNPN information is successful, the UE may include, in the non-registration request message, 31st identification information indicating that the procedure for providing the SNPN information is successful. Furthermore, if the provision and / or acquisition of the SNPN information is successful, the UE may include, in the non-registration request message, 31st identification information indicating that the provision of the SNPN information is successful.

[0576] Furthermore, if the onboarding service fails, the UE may include, in the non-registration request message, 31st identification information indicating that the onboarding service has failed. Furthermore, if the procedure for providing the SNPN information fails, the UE may include, in the non-registration request message, 31st identification information indicating that the procedure for providing the SNPN information has failed. Furthermore, if the provision and / or acquisition of the SNPN information fails, the UE may include, in the non-registration request message, 31st identification information indicating that the provision of the SNPN information has failed.

[0577] Furthermore, when a timer managed by the UE and / or the network expires, the UE may include, in the non-registration request message, a 31st identification indicating that the timer has expired. Furthermore, when a registration available for only the onboarding service is no longer valid, the UE may include, in the non-registration request message, a 31st identification indicating that the registration available for only the onboarding service is no longer valid.

[0578] Furthermore, the UE may indicate to the AMF the content indicated by the identification information included in the non-registration request message by including the 31st identification information in the non-registration request message. Furthermore, the UE may not permit the AMF to indicate the content indicated by the identification information included in the non-registration request message by including the 31st identification information in the non-registration request message.

[0579] Furthermore, the UE may select and decide whether to include the 31st identification information in the non-registration request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the UE, etc.

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

[0581] The AMF receives a deregistration request message via a 5G AN (gNB) (S1000). The AMF may recognize the reason for deregistration of the UE based on the deregistration request message and / or identification information included in the deregistration request message. Furthermore, the AMF may send a deregistration accept message to the UE via the 5G AN (gNB) as a response message to the deregistration request message based on the identification information included in the deregistration request message (S1002).

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

[0583] In addition, each process that the AMF performs based on the reception of each identification information shown above may be performed during this procedure or after completion of this procedure, or may be performed after completion of this procedure based on the completion of this procedure.

[0584] Furthermore, each device may perform processing based on the information transmitted and received in this procedure based on the completion of this procedure. For example, if an update to the configuration information is transmitted and received, each device may release the context of the UE. Furthermore, if information indicating that a network reselection and / or registration procedure is required is transmitted and received, the UE may initiate a network reselection and / or registration procedure based on the completion of this procedure.

[0585] Furthermore, the UE may store the identification information received with the unregistration request message and may recognize the network's decision based on the completion of this procedure.

[0586] For example, when the UE sends the 31st identification information, the UE may recognize that the onboarding service is completed. Furthermore, when the UE sends the 31st identification information, the UE may recognize that the SNPN information provision procedure is completed.

[0587] Furthermore, the UE may recognize that the onboarding service has not been completed when the 31st identification information is sent. Furthermore, the UE may recognize that the SNPN information provision procedure has not been completed when the 31st identification information is sent.

[0588] Furthermore, when the UE transmits the 31st identification information, the UE may determine whether the onboarding service is completed. Furthermore, when the UE transmits the 31st identification information, the UE may determine whether the SNPN information provision procedure is completed.

[0589] Furthermore, the UE may recognize that the onboarding service has been successful if the 31st identification information has been sent. Furthermore, the UE may recognize that the SNPN information provision procedure has been successful if the 31st identification information has been sent. Furthermore, the UE may recognize that the SNPN information provision and / or acquisition has been successful if the 31st identification information has been sent.

[0590] Furthermore, the UE may recognize that the onboarding service has failed if the 31st identification information is sent. Furthermore, the UE may recognize that the SNPN information provision procedure has failed if the 31st identification information is sent. Furthermore, the UE may recognize that the provision and / or acquisition of SNPN information has failed if the 31st identification information is sent.

[0591] Furthermore, when the UE sends the 31st identification information, the UE may determine whether the onboarding service is successful or unsuccessful. Furthermore, when the UE sends the 31st identification information, the UE may determine whether the procedure for providing the SNPN information is successful or unsuccessful. Furthermore, when the UE sends the 31st identification information, the UE may determine whether the provision and / or acquisition of the SNPN information is successful or unsuccessful.

[0592] Furthermore, when the UE transmits the 31st identification information, the UE may recognize that a timer managed by the UE and / or the network has expired. Furthermore, when the UE transmits the 31st identification information, the UE may recognize that a registration that can only be used for onboarding services is no longer valid.

[0593] Furthermore, the UE may recognize that if the 31st identification information is sent, provision and / or acquisition of SNPN information is not possible. Furthermore, the UE may recognize that if the 31st identification information is sent, execution of an onboarding service is not possible. Furthermore, the UE may recognize that if the 31st identification information is sent, execution of a procedure for providing SNPN information is not possible.

[0594] Furthermore, the UE may recognize that the onboarding service is completed when it transmits 31st identification information indicating that the onboarding service is completed. Furthermore, the UE may recognize that the SNPN information provision procedure is completed when it transmits 31st identification information indicating that the SNPN information provision procedure is completed.

[0595] Furthermore, the UE may recognize that the onboarding service has not been completed if it transmits 31st identification information indicating that the onboarding service has not been completed.Furthermore, the UE may recognize that the SNPN information provision procedure has not been completed if it transmits 31st identification information indicating that the SNPN information provision procedure has not been completed.

[0596] Furthermore, the UE may recognize that the onboarding service is successful if it transmits 31st identification information indicating that the onboarding service is successful. Further, the UE may recognize that the SNPN information provision procedure is successful if it transmits 31st identification information indicating that the SNPN information provision procedure is successful. Further, the UE may recognize that the provision and / or acquisition of the SNPN information is successful if it transmits 31st identification information indicating that the SNPN information provision is successful.

[0597] Furthermore, the UE may recognize that the onboarding service has failed if it transmits 31st identification information indicating that the onboarding service has failed. Further, the UE may recognize that the SNPN information provision procedure has failed if it transmits 31st identification information indicating that the SNPN information provision procedure has failed. Further, the UE may recognize that the provision and / or acquisition of SNPN information has failed if it transmits 31st identification information indicating that the SNPN information provision has failed.

[0598] Furthermore, the UE may recognize that a timer managed by the UE and / or the network has expired if the UE transmits a 31st identification indicating that the timer has expired. Furthermore, the UE may recognize that a registration capable of using only the onboarding service has expired if the UE transmits a 31st identification indicating that the registration capable of using only the onboarding service has expired.

[0599] Furthermore, when the UE transmits the 31st identification information, the UE may recognize the content indicated by the transmitted identification information. Furthermore, when the UE transmits the 31st identification information, the UE may recognize that the content indicated by the transmitted identification information is not permitted.

[0600] Furthermore, the UE may release or delete the first list when transmitting the 31st identification information. Furthermore, the UE may delete the network identification information from the first list when transmitting the 31st identification information.

[0601] More specifically, when the UE transmits the 31st identification information indicating that the onboarding service is completed, the UE may release or delete the first list. Furthermore, when the UE transmits the 31st identification information indicating that the SNPN information provision procedure is completed, the UE may release or delete the first list.

[0602] Furthermore, the UE may release or delete the first list when it transmits 31st identification information indicating that the onboarding service is successful. Furthermore, the UE may release or delete the first list when it transmits 31st identification information indicating that the SNPN information provision procedure is successful. Furthermore, the UE may release or delete the first list when it transmits 31st identification information indicating that the SNPN information provision is successful.

[0603] Furthermore, the UE may release or delete the first list when the onboarding service is completed. Furthermore, the UE may release or delete the first list when the procedure for providing SNPN information is completed. Furthermore, the UE may release or delete the first list when the acquisition of SNPN information is completed.

[0604] Furthermore, the UE may release or delete the first list if the onboarding service is successful. Furthermore, the UE may release or delete the first list if the SNPN information provision procedure is successful. Furthermore, the UE may release or delete the first list if the SNPN information is successfully acquired.

[0605] Furthermore, the UE may release or delete the first list when receiving a non-registration acceptance message. Furthermore, the UE may delete the network identification information from the first list when receiving a non-registration acceptance message.

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

[0607] For example, if the procedure is performed in a first network, the network identity may be information identifying the first network. More particularly, if the procedure is performed in a first PLMN, the network identity may be information identifying the first PLMN. Furthermore, if the procedure is performed in a first SNPN, the network identity may be information identifying the first SNPN.

[0608] Furthermore, the UE may perform a second network selection when the 31st identification information is transmitted. Furthermore, the UE may perform a second network selection and select a target SNPN when the 31st identification information is transmitted. Furthermore, the UE may initiate a registration procedure in the selected new network after completing the second network selection.

[0609] More specifically, the UE may perform the second network selection when it transmits the 31st identification information indicating that the onboarding service is completed. Furthermore, the UE may perform the second network selection when it transmits the 31st identification information indicating that the SNPN information providing procedure is completed.

[0610] Furthermore, the UE may perform a second network selection if it transmits a 31st identification information indicating that the onboarding service is successful. Furthermore, the UE may perform a second network selection if it transmits a 31st identification information indicating that the SNPN information provision procedure is successful. Furthermore, the UE may perform a second network selection if it transmits a 31st identification information indicating that the SNPN information provision is successful.

[0611] Furthermore, the UE may perform a second network selection when receiving the non-registration acceptance message. Furthermore, the UE may perform a second network selection and select a target SNPN when receiving the non-registration acceptance message. Furthermore, the UE may initiate a registration procedure in the selected new network after completing the second network selection.

[0612] Conversely, when the UE transmits the 31st identification information, the UE may add the identification information of the network to the first list. Furthermore, when the UE transmits the 31st identification information, the UE may create a first list and add the identification information of the network to the created first list.

[0613] More specifically, if the UE sends the 31st identification information indicating that the onboarding service has not been completed, the UE may add the network identification information to the first list. Further, if the UE sends the 31st identification information indicating that the SNPN information provision procedure has not been completed, the UE may add the network identification information to the first list.

[0614] Furthermore, the UE may add the network identification information to the first list if it sends 31st identification information indicating that the onboarding service has failed. Furthermore, the UE may add the network identification information to the first list if it sends 31st identification information indicating that the SNPN information provision procedure has failed. Furthermore, the UE may add the network identification information to the first list if it sends 31st identification information indicating that the SNPN information provision has failed.

[0615] Furthermore, the UE may add the network identification information to the first list if the UE transmits a 31st identification information indicating that the timer has expired. Furthermore, the UE may add the network identification information to the first list if the UE transmits a 31st identification information indicating that the onboarding service-only registration is no longer valid.

[0616] Furthermore, the UE may add the identification information of the network to the first list if the onboarding service has not been completed. Furthermore, the UE may add the identification information of the network to the first list if the procedure for providing SNPN information has not been completed. Furthermore, the UE may add the identification information of the network to the first list if the acquisition of SNPN information has not been completed.

[0617] Furthermore, the UE may add the network identification information to the first list if the onboarding service fails. Further, the UE may add the network identification information to the first list if the SNPN information provision procedure fails. Further, the UE may add the network identification information to the first list if the SNPN information acquisition procedure fails.

[0618] Furthermore, the UE may add the identification information of the network to the first list when receiving the non-registration acceptance message. Furthermore, the UE may create a first list and add the identification information of the network to the created first list when receiving the non-registration acceptance message.

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

[0620] For example, if the procedure is performed in a first network, the network identity may be information identifying the first network. More particularly, if the procedure is performed in a first PLMN, the network identity may be information identifying the first PLMN. Furthermore, if the procedure is performed in a first SNPN, the network identity may be information identifying the first SNPN.

[0621] Furthermore, the UE may re-perform the first network selection when the 31st identification information is transmitted. Furthermore, the UE may re-perform the first network selection when the 31st identification information is transmitted, and may select a network other than the network in which the UE is currently located. Furthermore, the UE may initiate a registration procedure in the selected new network after completing the re-performed first network selection.

[0622] More specifically, the UE may re-perform the first network selection if the UE sends the 31st identification information indicating that the onboarding service has not been completed. Furthermore, the UE may re-perform the first network selection if the 31st identification information indicates that the SNPN information provision procedure has not been completed.

[0623] Furthermore, the UE may re-perform the first network selection if it transmits 31st identification information indicating that the onboarding service has failed. Furthermore, the UE may re-perform the first network selection if it transmits 31st identification information indicating that the SNPN information provision procedure has failed. Furthermore, the UE may re-perform the first network selection if it transmits 31st identification information indicating that the SNPN information provision has failed.

[0624] Furthermore, the UE may re-perform the first network selection if the UE transmits a 31st identification indicating that the timer has expired. Furthermore, the UE may re-perform the first network selection if the UE transmits a 31st identification indicating that the onboarding service-only registration is no longer valid.

[0625] Furthermore, the UE may re-perform the first network selection when it receives the non-registration acceptance message. Furthermore, the UE may re-perform the first network selection when it receives the non-registration acceptance message, and may select a network other than the network in which it is currently located. Furthermore, the UE may initiate a registration procedure in the selected new network after completing the re-performed first network selection.

[0626] Furthermore, the UE may start a timer when it transmits the 31st identity information. Furthermore, the UE may start a timer when it receives a non-registration acceptance message.

[0627] Here, the timer may be a timer indicating a time limit for managing the first list. In other words, the UE may release or delete the first list based on the expiration of the timer.

[0628] Furthermore, the timer may be a timer indicating a time limit for prohibiting the registration procedure, In other words, the UE may start the registration procedure based on the expiration of the timer.

[0629] Note that the behavior to be performed when each piece of identification information is transmitted may be performed based on the transmitted identification information. For example, the behavior to be performed when the 31st identification information is transmitted may be performed based on the transmitted 31st identification information.

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

[0631] 4. First Embodiment Next, a first embodiment will be described. Hereinafter, the first embodiment will be referred to as the present embodiment. In the present embodiment, the UE executes a first procedure.

[0632] In addition, the UE may determine whether to perform the first 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.

[0633] [4.1. First Procedure] Next, the first procedure will be described with reference to FIG. 6. Hereinafter, the first procedure will be referred to as the main procedure. In the first procedure, first, the UE selects a first network (S600). Next, based on the first network selection, the UE connects to the selected first network and starts a registration procedure in the first network (S602). Next, based on the start of the registration procedure, each device performs a registration procedure in the first network.

[0634] In other words, the UE may perform a registration procedure for the onboarding service after connecting to the selected first network. In other words, each device may perform a registration procedure for the onboarding service after the UE connects to the first network.

[0635] 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 allows only the onboarding service to be used. Furthermore, the registration procedure for the onboarding service may be a registration procedure for performing registration that allows the onboarding service to be performed. Furthermore, the registration procedure for the onboarding service may be a registration procedure for performing registration that allows a procedure for providing SNPN information to be performed.

[0636] In other words, if the registration procedure for the onboarding service is successfully completed, each device may be able to use only the onboarding service. Furthermore, if the registration procedure for the onboarding service is successfully completed, each device may be able to execute the onboarding service. Furthermore, if the registration procedure for the onboarding service is successfully completed, each device may be able to execute the procedure for providing SNPN information.

[0637] Next, the UE may initiate a PDU session establishment procedure in the first network based on the completion of the registration procedure (S604). When the PDU session establishment procedure is initiated, each device may perform a PDU session establishment procedure in the first network.

[0638] In other words, the UE may perform a PDU session establishment procedure in the first network after completing the registration procedure for the onboarding service. In other words, each device may perform a PDU session establishment procedure in the first network after completing the registration procedure for the onboarding service.

[0639] Next, based on the completion of the registration procedure and / or the completion of the PDU session establishment procedure, each device performs a procedure to provide SNPN information (S606). Next, based on the completion of the procedure to provide SNPN information, each device performs a de-registration procedure in the first network (S608).

[0640] Next, based on the completion of the non-registration procedure, the UE selects a second network (S610). Next, based on the second network selection, the UE connects to the selected second network and starts a registration procedure (S612). Next, based on the start of the registration procedure, each device performs a registration procedure in the second network. This completes the first procedure.

[0641] Here, the first network may be an SNPN or a PLMN, and may be a network for onboarding services.

[0642] Furthermore, the second network may be an SNPN, or the second network may be a network to which the UE was attempting to connect, or the second network may be a target SNPN.

[0643] Furthermore, the second network may be a different network than the first network, or conversely, the second network may be the same network as the first network.

[0644] Here, the network for the onboarding service may be a network through which each device performs the onboarding service. In other words, the network for the onboarding service may be a network through which each device performs the SNPN information provision procedure. Furthermore, the network for the onboarding service may be an onboarding network.

[0645] Furthermore, the network for the onboarding service may be a network in which the use of services other than the onboarding service is restricted. Furthermore, the network for the onboarding service may be a network in which only the onboarding service can be used. Note that the network for the onboarding service may be realized by an SNPN or a PLMN.

[0646] Furthermore, the SNPN information provision procedure may be performed between the UE and a provisioning server, where the provisioning server may be located in a first network, or the provisioning server may be located in a second network, or conversely, the provisioning server may be located in a network different from the first network and the second network.

[0647] Furthermore, the PDU session establishment procedure may be a procedure for establishing a PDU session for a procedure for providing SNPN information. In other words, the PDU session establishment procedure may be a procedure for establishing a PDU session used in a procedure for providing SNPN information. Furthermore, the PDU session establishment procedure may be a procedure for establishing a PDU session for an onboarding service. Furthermore, the PDU session establishment procedure may be a procedure for establishing a PDU session used in an onboarding service.

[0648] Furthermore, the PDU session establishment procedure may be a procedure for establishing a PDU session for an onboarding service. Furthermore, in the PDU session establishment procedure, each device may establish a PDU session for an onboarding service.

[0649] Here, the UE may determine whether to perform the PDU session establishment procedure based on the identification information transmitted and received during the registration procedure. For example, the UE may initiate the PDU session establishment procedure if it recognizes during the registration procedure that use of the SNPN information provision procedure is permitted. More specifically, the UE may initiate the PDU session establishment procedure if it recognizes during the registration procedure that use of the SNPN information provision procedure via the user plane is permitted. Furthermore, the UE may initiate the PDU session establishment procedure if it recognizes during the registration procedure that use of the SNPN information provision procedure using the PCO or ePCO is permitted.

[0650] Conversely, if the UE recognizes during the registration procedure that the use of the SNPN information provision procedure via the control plane is permitted, the UE may not initiate a PDU session establishment procedure. More specifically, if the UE recognizes during the registration procedure that the use of the SNPN information provision procedure using the URSP is permitted, the UE may not initiate a PDU session establishment procedure.

[0651] Furthermore, the UE may establish a PDU session for the onboarding service in a PDU session establishment procedure.

[0652] Furthermore, the UE may release the PDU session for the onboarding service when it moves to another network. In other words, the UE may release the PDU session for the onboarding service when it moves to another network after completing the PDU session establishment procedure.

[0653] Furthermore, the UE may perform a local release of the PDU session for the onboarding service when it moves to another network. In other words, after the PDU session establishment procedure is completed, the UE may perform a local release of the PDU session for the onboarding service when it moves to another network.

[0654] Furthermore, the UE may release the PDU session for the onboarding service when it moves to the EPS. In other words, the UE may release the PDU session for the onboarding service when it moves to the EPS after completing the PDU session establishment procedure.

[0655] Furthermore, the UE may perform a local release of the PDU session for the onboarding service when moving to the EPS. In other words, the UE may perform a local release of the PDU session for the onboarding service when moving to the EPS after completing the PDU session establishment procedure.

[0656] Furthermore, the UE may not map the PDU session for the onboarding service to a PDN connection when moving to the EPS. In other words, the UE may be configured not to map the PDU session for the onboarding service to a PDN connection when moving to the EPS after completing the PDU session establishment procedure.

[0657] Furthermore, the UE may not establish a PDN connection corresponding to a PDU session for the onboarding service in the EPS when moving to the EPS. In other words, the UE may be configured not to establish a PDN connection corresponding to a PDU session for the onboarding service in the EPS when moving to the EPS after completing the PDU session establishment procedure.

[0658] Furthermore, the UE may release the PDU session for the onboarding service when it moves to another PLMN or another SNPN. In other words, after the PDU session establishment procedure is completed, the UE may release the PDU session for the onboarding service when it moves to another PLMN or another SNPN.

[0659] Furthermore, the UE may perform a local release of the PDU session for the onboarding service when it moves to another PLMN or another SNPN. In other words, after the PDU session establishment procedure is completed, the UE may perform a local release of the PDU session for the onboarding service when it moves to another PLMN or another SNPN.

[0660] Furthermore, when the UE moves to another PLMN or another SNPN, the UE may not transfer the PDU session for the onboarding service to the new PLMN or new SNPN. In other words, the UE may be configured not to transfer the PDU session for the onboarding service to the new PLMN or new SNPN when the UE moves to another PLMN or another SNPN after the PDU session establishment procedure is completed.

[0661] Furthermore, when the UE moves to another PLMN or another SNPN, the UE may not include information associated with a PDU session for the onboarding service in a registration request message during a registration procedure performed in the new PLMN or new SNPN. In other words, when the UE moves to another PLMN or another SNPN after the PDU session establishment procedure is completed, the UE may be configured not to include information associated with a PDU session for the onboarding service in a registration request message during a registration procedure performed in the new PLMN or new SNPN.

[0662] Here, the information associated with the PDU session may be an S-NSSAI associated with the PDU session. Furthermore, the information associated with the PDU session may be a Mapped S-NSSAI associated with the PDU session. Furthermore, the information associated with the PDU session may be a DNN associated with the PDU session or a PDU session ID that identifies the PDU session.

[0663] Here, the release of the PDU session for the onboarding service may be realized by executing a PDU session release procedure or by executing a local release of the PDU session. In other words, each device may release the PDU session for the onboarding service by executing a PDU session release procedure. Furthermore, each device may release the PDU session for the onboarding service by executing a local release of the PDU session for the onboarding service.

[0664] Furthermore, the PDU session release procedure may be a UE-requested PDU session release procedure or a network-requested PDU session release procedure.

[0665] If the PDU session release procedure is a UE-requested PDU session release procedure, the UE sends a PDU session release request (PDU SESSION RELEASE REQUEST) message to the SMF. Next, the SMF receives the PDU session release request from the UE. After receiving the PDU session release request message, the SMF sends a PDU session release command (PDU SESSION RELEASE COMMAND) message to the UE. Next, the UE receives a PDU session release command message from the SMF. After receiving the PDU session release command message, the UE sends a PDU session release complete (PDU SESSION RELEASE COMPLETE) message to the SMF. Finally, the SMF receives a PDU session release complete message from the UE.

[0666] Conversely, if the PDU session release procedure is a network-requested PDU session release procedure, the SMF sends a PDU SESSION RELEASE COMMAND message to the UE. Next, the UE receives the PDU SESSION RELEASE COMMAND message from the SMF. After receiving the PDU SESSION RELEASE COMMAND message, the UE sends a PDU SESSION RELEASE COMPLETE message to the SMF. Finally, the SMF receives a PDU SESSION RELEASE COMPLETE message from the UE.

[0667] Furthermore, the deregistration procedure may be executed based on the completion of the SNPN information provision procedure. Specifically, each device may execute the deregistration procedure based on the completion of the SNPN information provision procedure. Furthermore, each device may execute the deregistration procedure based on the success of the SNPN information provision procedure.

[0668] Furthermore, the unregistration procedure may be executed after the SNPN information provision procedure is completed. Specifically, each device may execute the unregistration procedure after the SNPN information provision procedure is completed. Furthermore, each device may execute the unregistration procedure after the SNPN information provision procedure is successful.

[0669] Conversely, the deregistration procedure may be performed without being based on the completion of the SNPN information provision procedure. Specifically, each device may perform the deregistration procedure based on the expiration of a timer. Furthermore, each device may perform the deregistration procedure based on the failure of the SNPN information provision procedure.

[0670] Furthermore, the deregistration procedure may be performed before the completion of the SNPN information provision procedure. Specifically, each device may perform the deregistration procedure when a timer expires. Furthermore, each device may perform the deregistration procedure when the SNPN information provision procedure fails.

[0671] Furthermore, when the procedure for providing SNPN information is completed, the deregistration procedure may be a UE-initiated deregistration procedure. In other words, when the procedure for providing SNPN information is completed, each device may perform a UE-initiated deregistration procedure.

[0672] Furthermore, if the SNPN information providing procedure is successful, the de-registration procedure may be a UE-initiated de-registration procedure. In other words, if the SNPN information providing procedure is successful, each device may perform a UE-initiated de-registration procedure.

[0673] When the onboarding service is completed, the unregistration procedure may be a UE-initiated unregistration procedure. In other words, when the onboarding service is completed, each device may perform a UE-initiated unregistration procedure.

[0674] Furthermore, if the onboarding service is successful, the de-registration procedure may be a UE-initiated de-registration procedure. In other words, each device may perform a UE-initiated de-registration procedure if the onboarding service is successful.

[0675] Furthermore, when a timer managed by the UE expires, the de-registration procedure may be a UE-initiated de-registration procedure. In other words, each device may perform a UE-initiated de-registration procedure when a timer managed by the UE expires.

[0676] Conversely, if the procedure for providing SNPN information is not completed, the de-registration procedure may be a network-initiated de-registration procedure. In other words, each device may perform a network-initiated de-registration procedure if the procedure for providing SNPN information is not completed.

[0677] Furthermore, if the procedure for providing SNPN information fails, the de-registration procedure may be a network-initiated de-registration procedure. In other words, if the procedure for providing SNPN information fails, each device may perform a network-initiated de-registration procedure.

[0678] Furthermore, if the onboarding service is not completed, the de-registration procedure may be a network-initiated de-registration procedure. In other words, each device may perform a network-initiated de-registration procedure if the onboarding service is not completed.

[0679] Furthermore, if the onboarding service fails, the de-registration procedure may be a network-initiated de-registration procedure. In other words, each device may perform a network-initiated de-registration procedure if the onboarding service fails.

[0680] Furthermore, the de-registration procedure may be a network-initiated de-registration procedure when a network-managed timer expires. In other words, each device may perform a network-initiated de-registration procedure when a network-managed timer expires.

[0681] Furthermore, if the onboarding service-only enabled registration is no longer valid, the de-registration procedure may be a network-initiated de-registration procedure. In other words, each device may perform a network-initiated de-registration procedure if the onboarding service-only enabled registration is no longer valid.

[0682] Furthermore, if the execution of a procedure in the first procedure ends in failure, each device may not execute the subsequent procedure. In this case, each device may execute processing based on the information included in the control message based on the failure of the execution of the procedure, or may complete the first procedure by executing processing based on the information included in the control message.

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

[0684] Furthermore, if execution of a procedure in the first procedure ends in failure, each device may restart the first procedure from the beginning. In this case, based on the failure of execution of the procedure, each device may perform processing based on information included in the control message, or may restart the first procedure from the beginning after performing processing based on information included in the control message.

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

[0686] Furthermore, the UE may set the S1 mode capability information to not allow movement to the EPS when the registration procedure for the onboarding service is completed. Furthermore, the UE may set the S1 mode capability information to information indicating that the S1 mode is not supported when the registration procedure for the onboarding service is completed.

[0687] Furthermore, the UE may configure the UE so that movement to the EPS is not possible when registration that allows only the onboarding service is completed. Furthermore, the UE may configure the S1 mode capability information to indicate that the S1 mode is not supported when registration that allows only the onboarding service is completed.

[0688] Furthermore, the UE may be configured to disable movement to the EPS when registered with the network for the onboarding service. Furthermore, the UE may set information indicating that the S1 mode is not supported in the S1 mode capability information when registered with the network for the onboarding service.

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

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

[0691] Additionally, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an ...

Claims

1. A UE (User Equipment), A transmitter / receiver and a controller are provided, The UE performs a PDU (Protocol Data Unit) session establishment procedure after completing a registration procedure for an onboarding service; In the PDU session establishment procedure, The transceiver unit receives a PDU session establishment acceptance message from the control device; The control unit establishes a PDU session for an onboarding service; When the UE moves to the Evolved Packet System (EPS), The transceiver unit transmits a PDU session release request message to the control device to release the PDU session; The control unit controls the PDU session so as not to map it to a PDN connection; The PDU session is an Always-on PDU session, and is a PDU session for which user plane resources must be activated every time the UE transitions from a 5GMM-IDLE state to a 5GMM-CONNECTED state. A UE characterized by:

2. When the UE moves to another PLMN (Public Land Mobile Network) or another SNPN (Stand-alone Non-Public Network), The transceiver unit transmits a PDU session release request message to the control device to release the PDU session; The control unit controls the PDU session so as not to map it to a PDN connection.

2. The UE of claim 1 .

3. Based on the completion of the PDU session establishment procedure, the control unit sets the transceiver unit so that a new PDU session establishment procedure is not started.

2. The UE of claim 1 .

4. When a new PDU session establishment procedure is executed while the PDU session is established, the control unit releases the PDU session.

2. The UE of claim 1 .

5. The PDU session establishment acceptance message includes information indicating an onboarding service; 2. The UE of claim 1 .

6. A communication control method for UE (User Equipment), performing a PDU (Protocol Data Unit) session establishment procedure after completing a registration procedure for the onboarding service; In the PDU session establishment procedure, the UE receiving a PDU session establishment acceptance message from the control device; Establish a PDU session for the onboarding service, When the UE moves to the Evolved Packet System (EPS), Sending a PDU session release request message to the control device to release the PDU session; Controlling the PDU session so that it is not mapped to a PDN connection; The PDU session is an Always-on PDU session, and is a PDU session for which user plane resources must be activated every time the UE transitions from a 5GMM-IDLE state to a 5GMM-CONNECTED state. A UE communication control method characterized by:

7. When the UE moves to another PLMN (Public Land Mobile Network) or another SNPN (Stand-alone Non-Public Network), Sending a PDU session release request message to the control device to release the PDU session; Controlling the PDU session so that it is not mapped to a PDN connection; 7. The UE communication control method according to claim 6.

8. Based on the completion of the PDU session establishment procedure, the UE configures a new PDU session establishment procedure not to be initiated.

7. The UE communication control method according to claim 6.

9. If a new PDU session establishment procedure is performed while the PDU session is established, the UE releases the PDU session.

7. The UE communication control method according to claim 6.

10. The PDU session establishment acceptance message includes information indicating an onboarding service; 7. The UE communication control method according to claim 6.

Images