User equipment (UE)

Abstract

In 5GS, for an on-boarding procedure to acquire information required for UE to be connected to an SNPN, it has not been determined which procedure, between remote provisioning via a user plane and remote provisioning via a control plane, should be selected and executed. This UE and devices in a network provide a communication means and a selection method involving: receiving / transmitting information or the like indicating requests and / or ability information; selecting, on the basis of received / transmitted information, a means from between remote provisioning via a user plane and remote provisioning via a control plane, which are mutually different in procedural configuration; and executing the means.

Description

UE (User Equipment)

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

[0002] The 3GPP (3rd Generation Partnership Project) is currently studying, discussing, and formulating specifications to support new procedures and functions in the system architecture of the 5th Generation (5G) mobile communication system, the 5GS (5G System) (see Non-Patent Documents 1 to 7). The Release 16 standard introduced the concept of a Non-Public Network (NPN), and in Release 17, the extension of its functions is being discussed.

[0003] 3GPP TS 23.501 V17.3.0 (2021-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 17)3GPP TS 23.502 V17.3.0 (2021-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 17)3GPP TS 24.501 V17.5.0 (2021-12); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17)3GPP TS 23.122 V17.5.0 (2021-12); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode (Release 17)3GPP TR 23.700-07 v17.0.0 (2021-03); Technical Specification Group Services and System Aspects; Study on enhanced support of non-public networks (Release 17)3GPP TS 23.003 V17.4.0 (2021-12); Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17)3GPP TS 33.501 V17.4.0 (2021-12); Technical Specification Group Services and System Aspects; Security architecture and procedures for 5G system (Release 17).

[0004] In the 5G System (5GS), a new core network, the 5G Core Network (5GCN), is being considered to provide a wide variety of services. Currently, for 5GS, a function to provide a non-public network that can be connected and used by specific users, such as a Non-Public Network (NPN), which is defined separately from the public network, the Public Land Mobile Network (PLMN) (see Non-Patent Document 5), is being considered (see Non-Patent Document 5).

[0005] Onboarding procedures are being considered as a means for UE (User Equipment) to acquire and provide (remote provisioning) various information required for connecting to an SNPN (Stand-alone NPN), which is a form of NPN. Here, remote provisioning is assumed to involve procedures via the user plane and procedures via the control plane. However, when each device in the UE and network (SNPN) supports both of these provisioning methods, the method for selecting the procedure to be executed during onboarding and the details of the procedure are not clear.

[0006] The present invention has been made in consideration of the above circumstances, and aims to provide a procedure selection method for a UE and each device in a network to select and execute an appropriate procedure for remote provisioning during onboarding, as well as a procedure including information transmitted and received between the UE and each device in the network required for such selection.

[0007] In an embodiment of the present invention, a UE (User Equipment) is a UE (User Equipment) comprising a transceiver unit and a control unit, wherein the transceiver unit transmits a registration request message including first and second identification information to a network in a registration procedure for onboarding, the first identification information indicating a request to perform remote provisioning via a control plane, and the second identification information indicating that the UE supports remote provisioning via the control plane; the transceiver unit receives a registration accept message including third and fourth identification information from the network, the third identification information being identification information indicating that remote provisioning via the control plane is to be performed, and the fourth identification information indicating that the network supports remote provisioning via the control plane; and the control unit, after completion of the registration procedure for onboarding, performs a procedure for remote provisioning via the control plane based on any one or more of the first to fourth identification information. In addition, a UE of one embodiment of the present invention is a UE (User Equipment) having a transceiver unit and a control unit, wherein when the transceiver unit transmits a PDU session establishment request message in a PDU session establishment procedure for provisioning via a user plane and receives a PDU session establishment rejection message including fifth identification information from the network, the control unit executes a procedure for remote provisioning via a network-initiated control plane based on the reception of the fifth identification information, and the fifth identification information is information indicating that remote provisioning via a network-initiated control plane will be executed.In addition, a UE of one embodiment of the present invention is a UE (User Equipment) having a transceiver unit and a control unit, and is characterized in that when a procedure for remote provisioning via a control plane initiated by a network is initiated while the transceiver unit is executing a PDU session establishment procedure for remote provisioning via a user plane, and when the transceiver unit receives a message to start remote provisioning via the control plane during the procedure for remote provisioning via the control plane, the control unit cancels the PDU session establishment procedure for remote provisioning via the user plane and continues the procedure for remote provisioning via the control plane initiated by the network.

[0008] According to one embodiment of the present invention, a method is provided for the UE and the core network to select either remote provisioning via user plane or remote provisioning via control plane as the method of remote provisioning during the onboarding procedure.

[0009] FIG. 1 is a diagram illustrating an overview of a mobile communication system (EPS / 5GS). FIG. 2 is a diagram illustrating a detailed configuration of a mobile communication system (EPS / 5GS). FIG. 3 is a diagram illustrating the device configuration of a UE. FIG. 4 is a diagram illustrating the configuration of an access network device (gNB) in 5GS. FIG. 5 is a diagram illustrating the configuration of a core network device (AMF / SMF / UPF) in 5GS. FIG. 6 is a diagram illustrating a registration procedure. FIG. 7 is a diagram illustrating a PDU session establishment procedure. FIG. 8 is a diagram illustrating a procedure for remote provisioning via a control plane.

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The best mode for carrying out the present invention will be described below with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system to which the present invention is applied will be described.

[0011] [1. System Overview] First, FIG. 1 is a diagram for explaining an overview 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.

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

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

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

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

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

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

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

[0019] Furthermore, access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are deployed in the NG-RAN. Note that, hereinafter, the gNB 122 may be referred to by its symbol abbreviated as eNB. 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.

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

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

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

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

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

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

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

[0027] The core network (core network_A and / or core network_B) and the access network (access network_A and / or access network_B) may differ depending on the mobile communication operator.

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

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

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

[0031] 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 portion. The payload portion 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.

[0032] In addition, access network _A, core network _A, access network _B, core network _B, PDN_A, and DN_A may include devices not shown in Fig. 2. For example, core network _A and / or core network _B and / or PDN_A and / or DN_A may include an AUSF (Authentication Server Function) and an AAA (Authentication, Authorization, and Accounting) server (AAA-S). The AAA server may be located outside the core network.

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

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

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

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

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

[0038] [2.1. Device configuration of UE] 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.

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

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

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

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

[0043] [2.1.1. Device Configuration of gNB] Next, an example of the device configuration of a gNB 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0063] [2.1.3. Device configuration of SMF] Next, an example of the device configuration of SMF132 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.

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

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

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

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

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

[0069] [2.1.4. UPF Device Configuration] Next, an example of the UPF device configuration 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.

[0070] 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 needed.

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

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

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

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

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

[0076] 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 U-Plane or UP.

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

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

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

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

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

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

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

[0084] [2.2. Explanation of Terms Used in the Present Embodiment] Next, highly specialized terms used in each embodiment and identification information used in the procedures will be explained.

[0085] A network (NW) 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, 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.

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

[0087] In addition, the SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a NAS message used in procedures 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 accept message, a PDU session establishment reject message, a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message, a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, etc. Furthermore, the procedure for SM or the SM procedure may include a PDU session establishment procedure, a PDU session modification procedure, and a UE-requested PDU session release procedure.Each procedure may be initiated from the UE or from the NW.

[0088] Furthermore, an MM (Mobility management) message (also referred to as an NAS MM message) may be an NAS message used in procedures for MM, and may be a control message transmitted and received between UE_A10 and AMF_A240. Furthermore, the MM message may include a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, etc. In addition, the procedures for MM or MM procedures may include a registration procedure, a de-registration procedure, a generic UE configuration update procedure, an authentication and authorization procedure, a service request procedure, a paging procedure, and a notification procedure.

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

[0092] There are two types of access types: 3GPP access and non-3GPP access. Here, information indicating the access type may be configured as an access type information element (IE), and may be, for example, identification information indicating the access type used in signaling between the UE and the core network or in transmitting and receiving user data.

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

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

[0095] The PDU session may also be used to transmit and receive SNPN information in remote provisioning via the user plane in the UE onboarding procedure. Details of the procedure for establishing a PDU session for onboarding or onboarding services and the procedure for remote provisioning via the user plane will be described later.

[0096] Furthermore, the DNN (Data Network Name) may be identification information that identifies the 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).

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

[0098] A PLMN (Public Land Mobile Network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by an operator, which is a (mobile) communications carrier, and the operator can be identified by a PLMN ID. An operator may manage one or more PLMNs. In this document, PLMN may also mean PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of a UE's IMSI (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN).

[0099] Furthermore, the UE may maintain an Equivalent HPLMN list in its Universal Subscriber Identity Module (USIM) to identify one or more Equivalent HPLMNs (E-HPLMNs). A PLMN different from the HPLMN and / or E-HPLMN may be a Visited PLMN (VPLMN). A PLMN to which the UE has successfully registered may be a Registered PLMN (RPLMN). The current PLMN may be a PLMN requested by the UE, a PLMN selected by the UE, an RPLMN, a PLMN permitted by the network, and / or a PLMN to which a core network device that transmits or receives messages belongs. Note that a service provided by a PLMN may be referred to as a PLMN service, and a service provided by an SNPN may be referred to as an SNPN service.

[0100] 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. A network slice may also be simply referred to as a slice.

[0101] 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 an NS, of which one or more are configured within a core network_B. An NSI may also be composed of a virtual network function (NF) generated using a network slice template (NST).

[0102] Here, an NST is a logical representation of one or more NFs associated with resource requirements for providing the required communication services and capabilities. In other words, an NSI may be a collection of multiple NFs within the core network_B190. An NSI may also be a logical network configured to separate user data delivered by services, etc. An NS may be configured with one or more NFs. The NFs configured in an NS may or may not be devices shared with other NSs.

[0103] 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 NSI IDs, and / or an APN. 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 the SMF 132 and the 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 common 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 an NS related to the UE.

[0105] Furthermore, the S-NSSAI transmitted and received between the UE and the NW may be expressed as an S-NSSAI IE (Information element). Furthermore, the S-NSSAI IE transmitted and received between the UE and the NW may be configured with an S-NSSAI configured with an SST and / or SD of the registered PLMN, and / or an SST and / or SD indicating the S-NSSAI of the HPLMN to which the S-NSSAI is mapped. One or more S-NSSAIs stored in the UE and / or NW may be configured with an SST and / or SD, or may be configured with an S-NSSAI configured with an SST and / or SD, and / or an SST and / or SD indicating the S-NSSAI of the HPLMN to which the S-NSSAI is mapped.

[0106] 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 NSSAI. The UE may store an NSSAI allowed by the network for each PLMN. The NSSAI may also be information used to select an AMF. The UE may apply each NSSAI (allowed NSSAI, and / or configured NSSAI, and / or rejected NSSAI, and / or pending NSSAI, and / or first NSSAI) to the PLMN and the EPLMN.

[0107] A mapped S-NSSAI is an S-NSSAI of an HPLMN that is mapped to an S-NSSAI of a registered PLMN in a roaming scenario. The UE may store one or more mapped S-NSSAIs that are mapped to the configured NSSAI and the S-NSSAI included in the allowed NSSAI for each access type. Furthermore, the UE may store one or more mapped S-NSSAIs for the first NSSAI, the rejected NSSAI, and / or the S-NSSAI included in the pending NSSAI.

[0108] The Network Slice-Specific Authentication and Authorization (NSSAA) function is a function for realizing network slice-specific authentication and authorization. Network slice-specific authentication and authorization allows UE authentication and authorization to be performed outside the core network, such as by a third party. PLMNs and network devices with NSSAA functionality can perform NSSAA procedures for a certain S-NSSAI based on the UE's registration information. Furthermore, UEs with NSSAA functionality can manage, store, and send / receive pending NSSAIs and third rejected NSSAIs. In this document, NSSAA may be referred to as the network slice-specific authentication and authorization procedure or the authentication and authorization procedure.

[0109] The S-NSSAI requiring an NSSAA is an S-NSSAI requiring an NSSAA that is managed by a core network and / or a core network device. Furthermore, the S-NSSAI requiring an NSSAA may be an S-NSSAI other than the HPLMN, where the S-NSSAI requiring an NSSAA that is managed by a core network and / or a core network device becomes a mapped S-NSSAI.

[0110] The core network and / or core network device may store an S-NSSAI requiring an NSSAA by associating the S-NSSAI with information indicating whether an NSSAA is required. The core network and / or core network device may further store an S-NSSAI requiring an NSSAA in association with information indicating whether an NSSAA has been completed, or information indicating that the NSSAA has been completed and is permitted or successful. The core network and / or core network device may manage an S-NSSAI requiring an NSSAA as information unrelated to the access network.

[0111] Also, a configured NSSAI is an NSSAI provided and stored in the UE. The UE may store a configured NSSAI for each PLMN. The UE may store a configured NSSAI in association with a PLMN. In this document, a configured NSSAI associated with a PLMN may be expressed as a configured NSSAI for the PLMN, a configured NSSAI of the PLMN, a configured NSSAI for the PLMN, or a configured NSSAI associated with the PLMN. Also, a UE may not be associated with a PLMN and may store a configured NSSAI that is valid for all PLMNs, and such a configured NSSAI may be referred to as a "default configured NSSAI."

[0112] The configured NSSAI may be associated with multiple PLMNs, which may be EPLMNs.

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

[0114] Furthermore, the requested NSSAI is an NSSAI provided by the UE to the network during the registration procedure. In the registration procedure, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI or configured NSSAI stored by the UE. In the PDU session establishment procedure, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI stored by the UE.

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

[0116] Also, the allowed NSSAI is information indicating one or more network slices to which the UE is permitted. In other words, the allowed NSSAI is information identifying a network slice to which the network permits the UE to connect.

[0117] The UE and / or NW may store and manage the allowed NSSAI for each access (3GPP access or non-3GPP access) as information of the UE. The UE and / or NW may further manage the allowed NSSAI in association with a registration area.

[0118] Furthermore, the UE and / or NW may store and manage an allowed NSSAI associated with a PLMN as information of the UE. The allowed NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

[0119] In this document, an allowed NSSAI associated with a PLMN and an access type may be expressed as an allowed NSSAI for the PLMN and access type, or an allowed NSSAI for the access type of the PLMN. An S-NSSAI included in an allowed NSSAI may be expressed as an allowed S-NSSAI. An allowed S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0120] Further, the rejected NSSAI is information indicating one or more network slices to which the UE is not permitted. In other words, the rejected NSSAI is information identifying a network slice to which the network does not permit the UE to connect. The rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value.

[0121] Here, the rejection reason value is information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and the network may store and manage the rejected NSSAI appropriately based on the rejection reason value associated with each S-NSSAI.

[0122] Furthermore, the rejected NSSAI may be included in an NAS message transmitted from the network to the UE, such as a registration accept message, a configuration update command, or a registration reject message, or in an RRC message including an NAS message. The S-NSSAI included in the rejected NSSAI may be expressed as the rejected S-NSSAI.

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

[0124] The UE and / or NW may store and manage the rejected NSSAI associated with the PLMN as information of the UE. The rejected NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

[0125] 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 be a TA (Tracking Area). A tracking area may be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking area code) and a PLMN.

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

[0127] The TAIs included in the TAI list may belong to one PLMN or multiple PLMNs. If multiple TAIs included in the TAI list belong to different PLMNs, those PLMNs may be EPLMNs.

[0128] The UE ID is information for identifying a UE. Specifically, for example, the UE ID may be a SUCI (Subscription Concealed Identifier), a SUPI (Subscription Permanent Identifier), a GUTI (Globally Unique Temporary Identifier), an IMEI (International Mobile Subscriber Identity), an IMEISV (IMEI Software Version), or a TMSI (Temporary Mobile Subscriber Identity). Alternatively, the UE ID may be other information set in an application or a network. Furthermore, the UE ID may be information for identifying a user.

[0129] The N1 NAS signaling connection is a connection between the UE and the network (AMF), and may be managed and exist independently for 3GPP access and non-3GPP access.

[0130] The state in which the N1 NAS signaling connection is established may be 5GMM-CONNECTED mode. The state in which the N1 NAS signaling connection is not established may be 5GMM-IDLE mode.

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

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

[0133] An SNPN (Stand-alone Non-Public Network) is a type of NPN that is a 5GS network deployed for non-public use. It is operated by an NPN operator and is independent of the NFs provided by the PLMN. In other words, an SNPN may be an NPN-dedicated network that is independent of the PLMN. An SNPN is identified by a combination of a PLMN ID and a Network Identifier (NID). The PLMN ID used for the SNPN ID may be information reserved for private networks; for example, the MCC included in the PLMN ID may be 999.

[0134] Furthermore, a UE capable of using an SNPN may support an SNPN access mode. A UE configured to operate in the SNPN access mode may be able to select an SNPN and register with the SNPN, but may not be able to select a PLMN. A UE configured to operate in the SNPN access mode may be able to perform an SNPN selection procedure, but may not be able to perform a PLMN selection procedure. Even if a UE is capable of using an SNPN (SNPN enabled), a UE not configured to operate in the SNPN access mode may not be able to select an SNPN and register with the SNPN, but may be able to select a PLMN. A UE not configured to operate in the SNPN access mode may not be able to perform an SNPN selection procedure, but may be able to perform a PLMN selection procedure.

[0135] Also, a UE operating in SNPN access mode may be able to select an SNPN via Uu (3GPP access). Also, a UE operating in SNPN access mode may be able to select an SNPN via Uu or NWu established via a PDU session provided by a selected PLMN via Uu or NWu (non-3GPP access). Also, a UE not operating in SNPN access mode may be able to select a PLMN via Uu or NWu established via a PDU session provided by a selected SNPN via Uu or NWu (non-3GPP access).

[0136] NID (Network Identifier) ​​is information that identifies a network. An SNPN may be identified by information that combines a PLMN ID and an NID. The NID may be unique information within the SNPN, or may be unique information.

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

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

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

[0140] 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 or an SNPN access operation mode. In other words, an SNPN-enabled UE may operate in an SNPN access mode or an SNPN access operation mode.

[0141] Also, the SNPN access mode is a mode in which a UE selects only an SNPN. More specifically, a UE in the SNPN access mode may be a mode of a UE when performing procedures, processes, etc. for registering and connecting to an SNPN. Furthermore, a UE that performs SNPN selection or ON-SNPN selection as network selection, or performs a normal registration procedure to an SNPN, or performs a registration procedure for onboarding, or performs a procedure for remote provisioning, must operate in the SNPN access mode. Here, a UE operating in the SNPN access mode may be referred to as a UE in the SNPN access mode. Furthermore, a UE in the SNPN access mode may be a UE in which an SNPN is enabled.

[0142] Also, the SNPN access operation mode is a mode of connecting to the SNPN via the SNPN access mode or non-3GPP access. Here, "non-3GPP access" in the SNPN may refer to a case where the UE connects to the SNPN via a PLMN. Also, when the UE operates in the SNPN access mode, it may operate in the SNPN access operation mode. Also, when the UE does not operate in the SNPN access mode, it may not operate in the SNPN access operation mode. Furthermore, a UE in the SNPN access mode may be a UE in the SNPN access operation mode.

[0143] The SNPN selection process may be a process for selecting an SNPN. Alternatively, the SNPN selection process may be a process for a UE to select an SNPN. Alternatively, the SNPN selection process may be a process performed when a UE connects to an SNPN. The SNPN selection process may be referred to as SNPN selection or an SNPN selection procedure. SNPN selection may be referred to as an SNPN selection process or an SNPN selection procedure. The SNPN selection procedure may be referred to as an SNPN selection process or an SNPN selection.

[0144] A UE operating in an SNPN access mode or an SNPN access operation mode may perform the SNPN selection process. A UE not operating in an SNPN access mode or an SNPN access operation mode may not perform the SNPN selection process. The SNPN selection process may include an automatic SNPN selection mode and a manual SNPN selection mode. The SNPN selection procedure may be performed without registration. In other words, the SNPN selection procedure may be performed when the UE has not completed registration with the network.

[0145] Furthermore, a UE not operating in the SNPN access mode or the SNPN access operation mode may perform the PLMN selection process. A UE operating in the SNPN access mode or the SNPN access operation mode may not perform the PLMN selection process. The PLMN selection procedure may be performed without registration. In other words, the PLMN selection procedure may be performed when the UE has not completed registration with the network. The PLMN selection process may include an automatic PLMN selection mode and a manual PLMN selection mode.

[0146] A UE in an SNPN access operation mode may refer to a UE in an SNPN access mode or a UE that accesses an SNPN via non-3GPP. In other words, even if a UE is not in an SNPN access mode, it may be a UE in an SNPN access operation mode if it connects to an SNPN via non-3GPP.

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

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

[0149] 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 a UE authentication function using the default UE certificate to another device or entity. The DCS may include an AAA server, or may include an AUSF and a UDM. Alternatively, the DCS may include an AAA server, or may include an AUSF and a UDM. Conversely, the functions of the DCS may be realized by the AAA server, or may be realized by the AUSF and a UDM.

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

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

[0152] Here, the onboarding network may be realized by a PLMN. Furthermore, the onboarding network may be realized by an SNPN. Note that the SNPN that provides access to the UE for onboarding may be an Onboarding Standalone Non-Public Network (ON-SNPN).

[0153] A provisioning server (PVS) 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.

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

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

[0156] Also, a CH (Credentials Holder) may be an entity other than the credential holder that authenticates and authorizes access to the SNPN of the UE.

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

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

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

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

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

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

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

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

[0165] The SNPN information provision procedure is a procedure for the network to provide SNPN information to the UE. In other words, the SNPN information provision procedure is a procedure for the UE to obtain SNPN information from the network. Furthermore, the SNPN information provision procedure may be a procedure for performing UE onboarding. In this specification, the SNPN information provision procedure is also referred to as a UE remote provisioning procedure, UE remote provisioning, remote provisioning procedure, remote provisioning, etc.

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

[0167] Furthermore, the UE may obtain the SNPN information from the network in a procedure for providing the SNPN information. More specifically, the UE may obtain the SNPN information from the provisioning server or the subscription owner in a procedure for providing the SNPN information.

[0168] Here, the procedure for providing SNPN information may include a procedure for providing SNPN information via a user plane and a procedure for providing SNPN information via a control plane. Note that the procedure for providing SNPN information via the user plane is also referred to as a remote provisioning procedure via a user plane, etc. Also, the procedure for providing SNPN information via the control plane is also referred to as a remote provisioning procedure via a control plane, etc.

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

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

[0171] 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 over the PDU session. In other words, when the procedure for providing SNPN information via the user plane is used, the UE may acquire the SNPN information by establishing a PDU session with the network and receiving the SNPN information from the network over the PDU session.

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

[0173] 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. In other words, the procedure for providing SNPN information via the control plane is a procedure in which the UE obtains SNPN information from the network via the control plane.

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

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

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

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

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

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

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

[0181] Furthermore, each device may perform remote provisioning via the user plane using a PDU session for the onboarding service. In other words, the remote provisioning procedure via the user plane may be composed of a procedure for establishing a PDU session for onboarding and a provisioning process via the established PDU session for onboarding. Here, the UE may obtain the FQDN or IP address of a provisioning server (PVS) for remote provisioning via the user plane during the procedure for establishing the PDU session for onboarding.

[0182] A UE operating in an SNPN access mode or an SNPN access operation mode may perform an onboarding network selection process. In other words, when an onboarding network selection process is performed, the UE may operate in an SNPN access mode or an SNPN access operation mode.

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

[0184] In this embodiment, the first identification information may be capability information indicating the remote provisioning method supported by UE_A10. Note that the remote provisioning method may include remote provisioning via the user plane and remote provisioning via the control plane.

[0185] Here, the capability information of the UE indicated by the first identification information may indicate that it supports only remote provisioning via the user plane, or that it supports only remote provisioning via the control plane, or that it supports both remote provisioning via the user plane and remote provisioning via the control plane.

[0186] Furthermore, the UE may indicate to the core network the provisioning methods supported by the UE by including the first identification information in a message sent by the UE to the core network. More specifically, for example, the UE may indicate to the core network the provisioning methods supported by the UE by including the first identification information in a registration request message in a registration procedure for onboarding, and the core network may recognize the provisioning methods supported by the UE based on receiving the first identification information.

[0187] Furthermore, for example, the UE may not include the first identification information in a registration request message in the registration procedure for onboarding, thereby allowing the core network to recognize that the UE only supports remote provisioning via the user plane.

[0188] Furthermore, for example, the first identification information may be an identification information that is transmitted only when the UE supports remote provisioning via the control plane in the registration procedure for onboarding. In this case, for example, when the UE transmits a registration request message without including the first identification information in the registration procedure for onboarding, the core network or each device may recognize that the UE supports only remote provisioning via the user plane.

[0189] Furthermore, the UE and each device in the core network may execute a procedure for remote provisioning via a user plane following the transmission and reception of the first identification information. More specifically, the UE and each device in the core network may execute a procedure for remote provisioning determined by the core network after completion of the registration procedure for onboarding based on the first identification information transmitted and received in the registration procedure for onboarding.

[0190] Note that the behavior of the UE, the core network, or each device regarding the transmission and reception of the first identification information is not limited to these, and details including other behaviors will be described later.

[0191] The second identification information in this embodiment may be information indicating a remote provisioning method that the UE requests from the core network. The remote provisioning method may include remote provisioning via a user plane and remote provisioning via a control plane.

[0192] The UE may include, in the second identification information, a remote provisioning method supported by the UE, which is indicated by the first identification information. In other words, for example, if the UE supports both remote provisioning via the control plane and remote provisioning via the user plane, the UE may transmit the second identification information including information indicating a request for remote provisioning via the control plane, a request for remote provisioning via the user plane, or both.

[0193] Note that the behavior of the UE, the core network, or each device regarding the transmission and reception of the second identification information is not limited to these, and details including other behaviors will be described later.

[0194] The third identification information in this embodiment may be capability information indicating a remote provisioning method supported by the core network, where the remote provisioning method may include remote provisioning via a user plane and remote provisioning via a control plane.

[0195] Here, the core network may transmit the third identification information based on receiving the first and / or second identification information from the UE. More specifically, for example, in a registration procedure, when the network receives a registration request message including the first and / or second identification information from the UE, the core network or each device may transmit to the UE a registration accept message or a registration reject message including the third identification information as a response message to the registration request message.

[0196] Furthermore, the core network may include third identification information in the registration accept message or the registration reject message to indicate to the UE the remote provisioning method supported by the core network.

[0197] Furthermore, a UE that receives a registration accept message including the third identification information may recognize the method of remote provisioning selected by the network or each device, and may perform either a procedure for remote provisioning via the user plane or a procedure for remote provisioning via the control plane based on or after receiving the third identification information.

[0198] Note that the behavior of the UE, the core network, or each device regarding the transmission and reception of the third identification information is not limited to these, and details including other behaviors will be described later.

[0199] The fourth identification information in this embodiment may be information indicating a provisioning method accepted or selected by the core network, where the remote provisioning method may include remote provisioning via a user plane and remote provisioning via a control plane.

[0200] Here, the core network may transmit the fourth identification information based on receiving the first and / or second identification information from the UE. More specifically, for example, in a registration procedure, when the network receives a registration request message including the first and / or second identification information from the UE, the core network or each device may transmit to the UE a registration accept message or a registration reject message including the fourth identification information as a response message to the registration request message.

[0201] Note that the behavior of the UE, the core network, or each device regarding the transmission and reception of the fourth identification information is not limited to these, and details including other behaviors will be described later.

[0202] The fifth identification information in this embodiment may be information indicating a timer that limits the initiation or execution of a UE-initiated session management procedure, and / or a timer value that indicates a period that limits the initiation or execution of a UE-initiated session management procedure, and / or identification information that includes a request from the core network to the UE to start or execute a timer that limits the UE-initiated session management procedure.

[0203] A UE that receives the fifth identification information may store the timer value indicated by the fifth identification information, may set the timer value in the timer indicated by the fifth identification information, or may replace or update the value of the timer that the UE has already stored.

[0204] Next, the UE may start a timer to limit the initiation or execution of a UE-initiated session management procedure. The timer may be started or executed based on receipt of the fifth identification information, based on completion of the procedure for receiving the fifth identification information, or at any time after completion of the procedure for receiving the fifth identification information. Here, the procedure for receiving the fifth identification information may be a registration procedure.

[0205] Furthermore, the UE may not initiate or execute a procedure for session management until the timer indicated by the fifth identification information expires. In other words, while the timer is running, the UE may be restricted or prohibited from transmitting a request message in the session management procedure. Here, the session management procedure may be a PDU session establishment procedure for remote provisioning via a user plane. More specifically, while the timer is running, execution of the PDU session establishment procedure for remote provisioning via a user plane may be restricted or prohibited.

[0206] Furthermore, if the fifth identification information does not include a timer value, or if it only includes information requesting the core network to start the timer to the UE, the timer value indicating the period during which the start or execution of a UE-initiated session management procedure is restricted may be a value pre-configured or implemented in the UE, or may be a value received and stored by the UE from the core network before receiving the fifth identification information.

[0207] Note that the behavior of the UE, the core network, or each device regarding the transmission and reception of the fifth identification information is not limited to these, and details including other behaviors will be described later.

[0208] The tenth identification information in this embodiment may be information indicating a provisioning method accepted or selected by the network. Here, the remote provisioning method may include remote provisioning via a user plane and remote provisioning via a control plane. The tenth identification information may also be a reason value indicating that an inappropriate provisioning procedure is being performed.

[0209] For example, the tenth identification information may be identification information to be included in a PDU session establishment rejection message that rejects a PDU session establishment procedure initiated by the UE as a remote provisioning procedure via a user plane that is not intended by the network, when the UE initiates the PDU session establishment procedure. Furthermore, the network may initiate a network-initiated remote provisioning procedure via a control plane after the PDU session establishment procedure.

[0210] Further, for example, the network may send the tenth identification information to indicate to the UE that it will initiate and execute a procedure via the control plane after the ongoing procedure is completed.

[0211] Note that the behavior of the UE, core network, or each device regarding the transmission and reception of the tenth identification information is not limited to these, and details including other behaviors will be described later.

[0212] [3. Embodiments of the Present Invention] [3.1. Description of Procedures or Processing Used in Each Embodiment] Next, procedures used in each embodiment will be described. The procedures or processing used in each embodiment include obtaining system information, network selection, a registration procedure, a remote provisioning procedure, and a non-registration procedure.

[0213] Here, the remote provisioning procedure may include a remote provisioning procedure via a user plane and a remote provisioning procedure via a control plane. In other words, in each embodiment of the present invention, either or both of a remote provisioning procedure via a user plane and a remote provisioning procedure via a control plane may be executed as the remote provisioning procedure.

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

[0215] Each procedure will be explained below.

[0216] [3.1.1. System Information Acquisition] Next, a process related to system information acquisition will be described. System information acquisition may involve a UE acquiring and storing information broadcast by an NG-RAN node that provides access to one or more SNPNs.

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

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

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

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

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

[0222] [3.1.2. Network Selection] Next, we will explain the process related to network selection. Network selection is a process that an unregistered UE performs to select a PLMN, NPN, or SNPN to register with before performing the registration procedure. For example, the UE may perform network selection to select a different network when powering up, when removing or inserting a SIM card, or if the registration procedure fails.

[0223] Unless otherwise specified, the network selection in this embodiment may be a process for selecting an SNPN (SNPN selection), or may be a process for selecting an ON-SNPN (ON-SNPN selection). Here, the ON-SNPN selection may be an SNPN selection for an onboarding service, and may be performed when a UE performs UE onboarding. The ON-SNPN selection may be one form of SNPN selection.

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

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

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

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

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

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

[0230] Furthermore, when the UE performs initial registration with an SNPN or ON-SNPN, the UE may indicate the PLMN ID and NID selected by the NG-RAN node for the SNPN or ON-SNPN selected in the network selection. Furthermore, the NG-RAN may notify the AMF of the PLMN ID and NID identifying the selected SNPN indicated by the UE.

[0231] [3.1.3. Registration Procedure] The registration procedure will be described with reference to FIG. 6. Here, the registration procedure in the present invention may be a registration procedure for an onboarding service. Hereinafter, unless otherwise specified, the registration procedure for onboarding will also be referred to as this procedure. Furthermore, this procedure may be a procedure executed by a UE in SNPN access mode.

[0232] Hereinafter, unless otherwise specified, the registration procedure may be a registration procedure for an onboarding service, and is also referred to as a registration procedure for an onboarding service, or a registration procedure for onboarding, or this procedure.

[0233] Here, the registration procedure for onboarding may be an initial registration procedure.

[0234] 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, and / or the PLMN. If the UE is not registered with a network, it can execute this procedure at any time, for example, when it is powered on. In other words, if the UE is in a deregistered state (5GMM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and the AMF) can transition to a registered state (5GMM-REGISTED state) based on the completion of the registration procedure. Note that each registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state (registered state or unregistered state) for 3GPP access and the registration state for non-3GPP access.

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

[0236] A UE may initiate a registration procedure when it moves across tracking areas (TAs). In other words, a UE may initiate a registration procedure when it moves to a TA different from the TA indicated in its TA list (TAI list or registration area). Furthermore, a UE may initiate this procedure when a running backoff timer or other timer expires. Furthermore, a UE may initiate a registration procedure when a context update for each device is required due to a PDU session disconnection or invalidation. Furthermore, a UE may initiate a registration procedure when a change occurs in the UE's capability information and / or preferences related to PDU session establishment. Furthermore, a UE may initiate a registration procedure periodically. Furthermore, a UE may initiate a registration procedure based on the completion of a UE configuration update procedure, a registration procedure, a PDU session establishment procedure, a PDU session management procedure, information received from the network in each procedure, or the expiration or stopping of a backoff timer. Note that the UE may perform the registration procedure at any timing, not limited to these.

[0237] The procedure for the UE to transition from a state where it is not registered in the network to a state where it is registered may be referred to as an initial registration procedure or a registration procedure for initial registration, and the registration procedure performed when the UE is registered in the network may be referred to as a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0238] In addition, the UE may perform the above-mentioned network selection before the registration procedure or in the initial state of the registration procedure to select and determine the PLMN, SNPN, or ON-SNPN requested by the UE.

[0239] In Figure 6, new AMF141 indicates the AMF to which UE_A10 is registered through this procedure, and old AMF142 refers to the AMF to which the UE was registered through a procedure prior to this procedure. If no AMF changes occur during this procedure, the interface between old AMF142 and new AMF141 and the procedure between old AMF142 and new AMF141 do not occur, and new AMF141 may be the same device as old AMF142. Note that in this document, when referring to AMF, it may mean new AMF141, old AMF142, or both. Furthermore, new AMF141 and old AMF142 may be AMF140.

[0240] First, UE_A10 starts the registration procedure by sending a registration request message to new AMF141 (S600) (S602) (S604). Specifically, the UE sends an RRC message including the registration request message to 5G AN120 (or gNB) (S600). Note that the registration request message is a NAS message transmitted and received on the N1 interface. Also, the RRC message may be a control message transmitted and received between the UE and 5G AN120 (or gNB). Also, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

[0241] Here, UE_A10 may transmit the first identification information and / or the second identification information in a registration request message, and / or an NAS message including a registration request, and / or an RRC message. Note that the first and second identification information may be configured as a combination of these.

[0242] Furthermore, UE_A10 may transmit a registration request message and / or an RRC message including identification information indicating the type of this procedure. Here, the identification information indicating the type of this procedure may be a 5GS registration type IE, and may be information indicating that this procedure is a registration procedure for initial registration, for updating registration information due to movement, for periodic registration information update, or for emergency registration.

[0243] Here, the identification information indicating the type of this procedure being the 5GS registration type IE may mean that the identification information indicating the type of this procedure is included and set in the 5GS registration type IE.

[0244] Furthermore, the 5GS registration type IE, which is identification information indicating the type of this procedure, may be information indicating that it is a registration procedure for onboarding. Here, the information indicating that it is a registration procedure for onboarding may further include information indicating the type of procedure for UE remote provisioning to be executed after this procedure. More specifically, the 5GS registration type IE, which is identification information indicating the type of this procedure, may be information indicating a registration procedure for onboarding for remote provisioning via the user plane or a registration procedure for remote provisioning via the control plane. Furthermore, for example, the 5GS registration type IE indicating the registration procedure for onboarding for remote provisioning via the user plane may be SNPN onboarding registration, and the 5GS registration type IE indicating the registration procedure for remote provisioning via the control plane may be information meaning SNPN onboarding registration for remote provisioning via the control plane.

[0245] Additionally, the registration procedure for the onboarding service may be performed as a normal initial registration procedure.

[0246] Alternatively, in a registration procedure for an onboarding service, the UE may perform the registration procedure using information indicating that the registration procedure is for onboarding. In a registration procedure for an onboarding service, the UE may perform the registration procedure using information indicating that the registration procedure is for updating registration information due to movement or for periodic registration information update.

[0247] In addition, the registration procedure for the onboarding service may refer to the initial registration procedure with the onboarding service and / or the mobility and periodic registration procedures initiated by the UE while it is registered with the onboarding service.

[0248] In order to notify the network of the functions supported by UE_A10, UE_A10 may include the capability information of the UE in the registration request message, and may include the first identification information as the capability information of the UE. Here, the capability information of the UE may be the 5G MM capability of 5GS.

[0249] UE_A10 may transmit the first 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 these identification information, UE_A10 may indicate that UE_A10 supports each function, may indicate a UE request, or may indicate both.In addition, the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0250] Furthermore, UE_A10 may select and decide whether to send the first identification information to the network based on the UE's capability information, and / or UE policy, and / or UE status, and / or user registration information, and / or context held by the UE, etc.

[0251] Furthermore, UE_A10 may indicate that it requests network capability information indicating that the network supports the function corresponding to the first identification information by sending the first identification information in a registration request message.

[0252] The UE_A10 may include information other than the first identification information in the registration request message and / or the RRC message containing the registration request message, for example, the UE ID and / or the network ID and / or the AMF identification information and / or the requested NSSAI, and may transmit the same. Here, the network ID may be information for identifying an SNPN or an ON-SNPN.

[0253] Here, the AMF identification information may be information that identifies an AMF or a collection of AMFs, for example, 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier).

[0254] In addition, the UE may request the execution of a procedure for UE remote provisioning via the control plane after completion of this procedure being performed as a registration procedure for the onboarding service by sending a registration request message including the first and / or second identification information.

[0255] In addition, UE_A10 may 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.

[0256] When the 5G AN 120 (or gNB) receives an RRC message including a registration request message, it selects an AMF to which to transfer the registration request message (S602). Note that the 5G AN 120 (or gNB) can select an AMF based on one or more pieces of identification information included in the registration request message and / or the RRC message including the registration request message. Specifically, the 5G AN (or gNB) may select a new AMF 141 to which to send the registration request message based on first identification information.

[0257] For example, the 5G AN 120 (or gNB) may select, based on the first identification information, an AMF that supports a function corresponding to the capability information indicated by the first identification information. Specifically, the 5G AN (or gNB) may select an AMF that corresponds to the capability information of the UE indicated by the first identification information and supports a registration procedure for an onboarding service.

[0258] Note that the method for selecting an AMF is not limited to this, and the 5G AN (or gNB) may select an AMF based on other conditions. The 5G AN (or gNB) extracts a registration request message from the received RRC message and transfers the registration request message to the selected new AMF (S604). Note that if the first identification information is not included in the registration request message but is included in the RRC message, the identification information included in the RRC message may be transferred to the selected AMF (new AMF 141) together with the registration request message (S604).

[0259] When the new AMF 141 receives the registration request message, it can execute a first condition determination. The first condition determination is for determining whether the network (or the new AMF 141) accepts the UE's request. When the first condition determination is true, the new AMF 141 executes the procedures from S606 to S612. On the other hand, when the first condition determination is false, the new AMF 141 may execute the procedures from S606 to S608 and / or S610 instead of executing the procedures from S606 to S608.

[0260] Here, the procedure of S609 may be an authentication / security procedure. Note that, when this procedure is executed as a registration procedure for an onboarding service, the AMF may receive and store an FQDN or an IP address of a provisioning server (PVS) from a Default Credential Server (DCS) via an Authentication Server Function (AUSF) during the procedure of S609. Here, the PVS may be a server that provisions information or a certificate (credentials) of an SNPN to a UE in the procedure for the onboarding service. Furthermore, the FQDN or IP address of the PVS transmitted and received in S609 may be used when the UE connects to the PVS and obtains information or a certificate (credentials) of the SNPN in a procedure for remote provisioning via a user plane that is executed after completion of this procedure executed as a registration procedure for the onboarding service.

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

[0262] Here, if the first condition determination is true, the control message sent and received in S610 may be a Registration accept message, and if the first condition determination is false, the control message sent and received in S610 may be a Registration reject message.

[0263] Here, if this procedure is being performed as a registration procedure for onboarding, the 5GMM cause information element (IE) included in the registration rejection message may include "Onboarding services terminated" as the reason value for the registration rejection.

[0264] Furthermore, the first condition determination may be performed based on the receipt of a registration request message, and / or each identification information contained in the registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0265] 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 the 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.

[0266] If the AMF indicated in the AMF identification information included in the message received by new AMF 141 from the UE is old AMF 142, new AMF 141 executes the procedures of S606 and S608, and if the AMF indicated in the AMF identification information included in the message received by new AMF 141 from UE_A10 is new AMF 141, new AMF 141 does not execute the procedures of S606 and S608. In other words, if an AMF change occurs due to this procedure, the procedures of S606 and S608 are executed, and if no AMF change occurs, the procedures of S606 and S608 are skipped.

[0267] The UE context transfer procedure (S606, S608) will be described. The new AMF 141 sends a UE context request message to the old AMF 142 (S606). The old AMF 142 sends the UE context to the new AMF 141 based on the received UE context request message. The new AMF 141 generates a UE context based on the received UE context.

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

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

[0270] The new AMF 141 may transmit a control message including one or more of the third to fifth identification information. By transmitting this identification information and / or the control message, the new AMF 141 may indicate that the network supports the function indicated by the identification information, may indicate that the UE request has been accepted, may indicate that the request from the UE is not permitted or supported, or may indicate a combination of these. The third to fifth identification information may also be configured as information combining any two or more of them.

[0271] Here, for example, the third identification information may be capability information indicating that the new AMF 141 and / or the core network supports the function corresponding to the capability information indicated by the first identification information received from the UE.

[0272] Furthermore, for example, when new AMF 141 receives first identification information from the UE, even if new AMF 141 does not include second identification information in the control message that is a registration accept message, new AMF 141 may indicate to the UE that new AMF 141 and / or the core network recognize the capability information of the UE indicated by the first identification information and / or that new AMF 141 and / or the core network supports the function corresponding to the capability indicated by the first identification information. Conversely, when new AMF 141 does not include third identification information in the control message that is a registration message, new AMF 141 may indicate to the UE that new AMF 141 and / or the core network do not recognize the capability information of the UE indicated by the first identification information and / or that new AMF 141 and / or the core network do not support the function corresponding to the capability indicated by the first identification information.

[0273] Furthermore, if the new AMF 141 does not receive the first identification information from the UE, the new AMF 141 may transmit the control message with or without including the second identification information.

[0274] Here, the fourth identification information may be a response corresponding to the request content of the UE indicated by the second identification information received from the UE, and may indicate that the request from the UE is permitted. For example, when the AMF accepts or permits the request of the UE indicated by the second identification information, the AMF may include the fourth identification information in a control message and transmit it to the UE. Also, for example, when the AMF accepts or permits the request of the UE indicated by the second identification information, the AMF may include only the fourth identification information in the control message.

[0275] In addition, if the AMF does not receive the second identification information from the UE, it may send the fourth identification information by including it in the control message, or it may send it without including it.

[0276] Here, the AMF may include the fifth identification information in the control message based on receiving the first and / or second identification information from the UE. Note that the timer value indicated by the fifth identification information for limiting the UE from initiating a remote provisioning procedure via a user plane, i.e., a PDU session establishment procedure, may be determined based on an operator policy.

[0277] Furthermore, when the control message is a registration acceptance message, 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 also be performed when an SM message (e.g., a PDU session establishment request message) is included in the registration request message. Also, this sending method may be performed when an SM message (e.g., a PDU session establishment request message) is sent together with the registration request message. By performing such a sending method, the AMF can indicate that the procedure for SM has been accepted in the registration procedure.

[0278] In addition, the AMF may indicate that the UE's request has been accepted by sending a registration acceptance message, or may indicate that the UE's request has been rejected by sending a registration rejection 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.

[0279] The UE receives a control message via a 5G AN (gNB) (S610). If the control message is a registration accept message, the UE can recognize by receiving the registration accept message that the UE's request in the registration request message has been accepted and the contents of various identification information included in the registration accept message. Alternatively, if the control message is a registration reject message, the UE can recognize by receiving a registration reject message that the UE's request in the registration request message has been rejected and the contents of various identification information included in the registration reject message. Furthermore, if the UE does not receive a control 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.

[0280] If the control message is a registration accept message, the UE may further transmit a registration complete message to the AMF via the 5G AN (gNB) as a response message to the registration accept message (S610). 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.

[0281] The AMF receives a registration completion message via the 5G AN (gNB) (S612). In addition, each device completes this procedure based on the transmission and reception of the registration acceptance message and / or the registration completion message.

[0282] Alternatively, each device may complete the registration procedure based on sending or receiving a registration acceptance message or a registration rejection message.

[0283] Each device may transition to or maintain a state in which the UE is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on sending and receiving a registration accept message and / or a registration complete message, or may transition to or maintain a state in which the UE is not registered in the network on the access from which the registration reject message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on sending and receiving a registration reject message. Also, the transition to each state of each device may be based on sending and receiving a registration complete message or completion of the registration procedure.

[0284] 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 core network_A or another cell.

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

[0286] For example, when the UE receives the third and / or fourth identification information in the registration accept message, the UE may recognize that it is authorized to perform a procedure for remote provisioning via the control plane after the completion of this procedure, which is being performed as the registration procedure for onboarding. Alternatively, when the UE receives the third and / or fourth identification information in the registration accept message, the UE may recognize that it is authorized to perform a procedure for remote provisioning via the control plane and / or a procedure for remote provisioning via the user plane after the completion of this procedure, which is being performed as the registration procedure for onboarding. Alternatively, when the UE receives the third and / or fourth identification information in the registration accept message, the UE may recognize that it is authorized to perform a procedure for remote provisioning after the completion of this procedure, which is being performed as the registration procedure for onboarding.

[0287] Furthermore, if the UE receives the third and / or fourth identification information in the registration accept message, the UE may recognize that the network supports procedures for remote provisioning over the control plane and / or procedures for remote provisioning over the user plane.

[0288] Furthermore, if the UE receives a registration accept message that does not include both the third and fourth identification information, it may recognize that it is authorized to perform procedures for remote provisioning via the user plane after completing this procedure, which is being performed as a registration procedure for onboarding.

[0289] Furthermore, if the UE receives a registration accept message that does not include both the third and fourth identities, it may recognize that the network only supports procedures for remote provisioning via the user plane.

[0290] Furthermore, when the UE receives the fifth identification information, upon completion of this procedure, which is a registration procedure for the onboarding service, the UE may start a timer based on a timer value indicated by the fifth identification information, and while the timer is running, the initiation of a remote provisioning procedure via the user plane, i.e., a PDU session establishment procedure, may be restricted. Here, the restriction on the initiation of a PDU session establishment procedure may be a state in which the transmission of a PDU session establishment request message by the UE is restricted or prohibited.

[0291] When the UE receives the fifth identification information, the UE may start a timer based on the fifth identification information upon completion of this procedure, regardless of whether other identification information is included. More specifically, even if the UE recognizes that only remote provisioning via the user plane is permitted by this procedure, a UE that receives a control message including the fifth identification information may be restricted from performing a remote provisioning procedure via the user plane until the timer based on the fifth identification information expires.

[0292] Furthermore, based on the completion of this procedure, the UE and each device in the network may initiate and execute a procedure for UE remote provisioning in the onboarding service. Here, the procedure for UE remote provisioning may be a remote provisioning procedure via the user plane or a remote provisioning procedure via the control plane. Furthermore, as the remote provisioning procedure via the user plane, a PDU session establishment procedure and remote provisioning via the established PDU session may be executed. Furthermore, as the remote provisioning procedure via the control plane, a network-initiated Mobility Management (MM) procedure may be executed, and as the MM procedure, for example, a UE Parameter Update (UPU) procedure may be executed.

[0293] [3.1.4. Remote Provisioning Procedure] Next, the remote provisioning procedure of the UE will be described. Hereinafter, the remote provisioning procedure will be referred to as the procedure for remote provisioning or the actual procedure.

[0294] This procedure may be a procedure for a UE to obtain information and / or credentials of a destination SNPN when connecting to the SNPN. Furthermore, this procedure may be a procedure and process for the UE to receive and obtain SNPN information from the network. Note that the network from which the UE obtains SNPN information may be an onboarding network (ON), which may be an ON-SNPN or an ON-PLMN. In the present invention, unless otherwise specified, the onboarding network refers to an ON-SNPN.

[0295] Note that onboarding including this procedure may be performed when the UE does not have or store information or a certificate (credential) of the SNPN to which it is connected. Conversely, when the UE has information or a certificate (credential) of the SNPN to which it is connected, onboarding including this procedure does not need to be performed.

[0296] The remote provisioning procedure may include a remote provisioning procedure via a user plane and a remote provisioning procedure via a control plane, and may be performed by a UE in an SNPN access mode.

[0297] Each remote provisioning procedure will be explained below.

[0298] [3.1.4.1. Remote Provisioning Procedure via User Plane] Next, the remote provisioning procedure of the UE via the user plane will be described. Note that this procedure may be a procedure performed by a UE in SNPN access mode. Hereinafter, the remote provisioning procedure of the UE via the user plane will also be referred to as the remote provisioning procedure via the user plane, or the procedure for remote provisioning via the user plane, or the UP remote provisioning procedure, or the procedure for UP remote provisioning, or simply this procedure, etc.

[0299] The purpose of this procedure is to perform UP remote provisioning, in which the UE receives and / or acquires and / or stores information about the SNPN to be connected to and / or credentials, such as credentials, from the network via the user plane before connecting to the SNPN. After completing onboarding, including this procedure, the UE may connect to the SNPN using the information, credentials, etc. received and stored in this procedure.

[0300] This procedure may comprise a procedure for establishing a connection for performing remote provisioning via a user plane, and a procedure or process for acquiring information about the SNPN and / or qualification information, such as credential(s), via the network using the established user plane connection. More specifically, this procedure may comprise, for example, a PDU session establishment procedure initiated by the UE, and a procedure or process for acquiring information about the SNPN and / or qualification information, such as credential(s), using the established PDU session.

[0301] This procedure may be performed by a UE in an SNPN access mode, and may be performed after the completion of the registration procedure for onboarding.

[0302] In this procedure, the UE may obtain or be provisioned with, for example, information about the SNPN and / or qualification information, such as credential(s), from a provisioning server (also referred to as PVS) in the DN, PLMN, or SNPN. The UE may receive the FQDN (Fully Qualified Domain Name) or IP address of the provisioning server from the network, included in a PDU session establishment accept message in the PDU session establishment procedure described below. Here, the PDU session establishment accept message may be included in a NAS message.

[0303] Also, in this chapter, unless otherwise specified, the PDU session establishment procedure for remote provisioning via the user plane is also referred to as the PDU session establishment procedure in this procedure, or the PDU session establishment procedure, or the PDU session establishment procedure for onboarding services.

[0304] Furthermore, in the PDU session establishment procedure in this procedure, the established PDU session may be a user plane resource for remote provisioning or may be a connectivity service for sending and receiving user data including SNPN information and / or qualification information such as credential(s).

[0305] Below, an overview of the PDU session establishment procedure, which is a procedure for establishing a PDU session, which is a connection for remote provisioning via the user plane in this procedure, will be explained using Fig. 7. Note that in the explanation of this procedure, the terms "network", "core network", "PLMN", etc. may also mean "SNPN".

[0306] The PDU session establishment procedure is a session management procedure in 5GS. The PDU session establishment procedure in this procedure is a procedure for each device to establish a PDU session. Note that each device can start the PDU session establishment procedure in this procedure at any time after the registration procedure for onboarding is completed and the device enters a registered state. Furthermore, each device may establish a PDU session to be used as a user plane connection for remote provisioning via the user plane based on the completion of the PDU session establishment procedure in this procedure.

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

[0308] Here, when the registration procedure for the onboarding service is completed, the UE may initiate a PDU session establishment procedure to establish a PDU session for the onboarding service. Note that the established PDU session may be used to perform remote provisioning via the user plane. More specifically, for example, the remote provisioning via the user plane may be performed using the PDU session established in the PDU session establishment procedure for the onboarding service, which is performed after the registration procedure for the onboarding service is completed. Furthermore, the PDU session established in the PDU session establishment procedure for the onboarding service may be a PDU session that can be used only for the onboarding service or whose usage is restricted. In other words, the PDU session established in the PDU session establishment procedure for the onboarding service may be a PDU session that can be used only for remote provisioning via the user plane or whose usage is restricted.

[0309] Furthermore, the UE may initiate a PDU session establishment procedure to establish a PDU session for the onboarding service if registration that allows only the onboarding service is completed.

[0310] Furthermore, the UE may initiate a PDU session establishment procedure to establish a PDU session for the onboarding service when the UE is registered with the network for the onboarding service.

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

[0312] Here, the AMF may further include the FQDN or IP address of a provisioning server (PVS) in the message including the PDU session establishment request and send it to the SMF (S904). Note that here, the FQDN or IP address of the PVS that the AMF sends to the SMF may be information received and stored from the DCS (Default Credential Server) via the AUSF in Authentication / Security (S609) performed during the registration procedure for onboarding.

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

[0314] Here, when establishing a PDU session for an onboarding service, the UE may not include a DNN and / or S-NSSAI(s) in an NAS message (MM message) including a PDU session establishment request message. Alternatively, a UE that has completed the registration procedure for the onboarding service may not include a DNN and / or S-NSSAI(s) in an MM message in the PDU session establishment procedure to the network registered for the onboarding service. Note that, when the AMF receives an NAS message including a PDU session establishment request from a UE that has completed the registration procedure for the onboarding service, it may establish a PDU session using the S-NSSAI and / or DNN included in Onboarding Configuration Data retained as information for UE onboarding. Conversely, a PDU session established in a PDU session establishment procedure initiated by a UE that has not performed the registration procedure for the onboarding service may be a normal PDU session.

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

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

[0317] 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 7, and if the third condition determination is false, the SMF starts the procedure in (B) of Figure 7.

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

[0319] Next, we will explain the steps when the third condition determination is true, i.e., each step of the procedure in (A) of Figure 7. 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 7.

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

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

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

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

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

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

[0326] The SMF may also transmit a PDU session establishment accept message including a fully qualified domain name (FQDN) or an IP address of a provisioning server (PVS) to the UE (S910). In this case, the UE that has received the PDU session establishment accept message including the FQDN or IP address of the provisioning server (PVS) from the network may perform a procedure, process, or provisioning to obtain information about the SNPN and / or credential information such as credential(s) using the FQDN or IP address of the provisioning server (PVS) via the PDU session for the onboarding service established in this procedure.

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

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

[0329] The UE receives a PDU session establishment acceptance message from the SMF (S910) (S912). Specifically, after the PDU session establishment acceptance message is sent from the SMF to the AMF (S910), the UE receives a NAS message including the PDU session establishment acceptance message from the AMF via the N1 interface (S912). As described above, the UE may receive the PDU session establishment acceptance message including the FQDN (Fully Qualified Domain Name) or IP address of the provisioning server (PVS).

[0330] Next, the UE may send a PDU session establishment complete message to the SMF via the AMF based on receiving the PDU session establishment accept message and / or the NAS message including the PDU session establishment accept message (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.

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

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

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

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

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

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

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

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

[0339] Here, the SMF and / or AMF may indicate that the UE request has been rejected or may indicate the reason why the UE request has been rejected by sending a PDU session establishment rejection message including the 10th identification information.

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

[0341] For example, a UE that receives a PDU session establishment rejection message including the 10th identification information may recognize that it needs to perform remote provisioning via the control plane rather than remote provisioning via the user plane based on this procedure, and may perform the remote provisioning procedure via the control plane after completing this procedure.

[0342] Each device completes the PDU session establishment 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 PDU session is established based on the completion of the procedure of (A) in Figure 7, or may recognize that the PDU session establishment procedure has been rejected based on the completion of the procedure of (B) in Figure 7, and may transition to a state in which the PDU session is not established. Furthermore, upon completion of the procedure of (A) in Figure 7, the UE can communicate with the DN using the established PDU session. Furthermore, upon completion of the procedure, the UE can communicate with the PVS of the DN using the established PDU session for the onboarding service.

[0343] Furthermore, when the UE receives the PDU session establishment accept message, it may establish a PDU session for the onboarding service. Furthermore, when the UE receives the PDU session accept message, it may recognize that the PDU session to be established is a PDU session for the onboarding service. Furthermore, when the UE receives the PDU session accept message, it may establish a PDU session for the onboarding service if this procedure is a PDU session establishment procedure for the onboarding service. Furthermore, when this procedure is a PDU session establishment procedure for the onboarding service, it may recognize that the PDU session to be established is a PDU session for the onboarding service. Furthermore, when the registration procedure for the onboarding service is completed, it may establish a PDU session for the onboarding service. Furthermore, when the registration procedure for the onboarding service is completed, it may recognize that the PDU session to be established is a PDU session for the onboarding service. Furthermore, when the registration for the onboarding service is completed, it may establish a PDU session for the onboarding service. Furthermore, the UE may recognize that the PDU session to be established is a PDU session for the onboarding service when registration for the onboarding service is completed. 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 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.

[0344] In this procedure, the established PDU session may be a restricted PDU session for UE remote provisioning via the user plane, and the established PDU session may also be used to provide onboarding services to the UE.

[0345] [3.1.4.1. Remote provisioning procedure via control plane] Next, the remote provisioning procedure of a UE via the control plane will be described with reference to Fig. 8. Hereinafter, the remote provisioning procedure of a UE via the control plane will also be referred to as the control plane remote provisioning procedure, or the procedure for control plane remote provisioning, or the CP remote provisioning procedure, or the procedure for CP remote provisioning, or simply this procedure, etc.

[0346] The purpose of this procedure is to perform CP remote provisioning, in which the UE receives and / or acquires and / or stores information about the SNPN to connect to and / or credentials, such as credentials, from the network via the control plane before connecting to the SNPN. After completing onboarding, the UE may connect to the SNPN using the information received and stored in this procedure.

[0347] This procedure may be performed by a UE in SNPN access mode. Furthermore, this procedure may be initiated and performed by the network after the onboarding registration procedure is completed. Here, the onboarding registration procedure may be the procedure described in Section 3.1.3, in which one or more of the first to fifth identification information items are transmitted and received and completed.

[0348] More specifically, for example, this procedure may be a network-initiated Mobility Management (MM) procedure. More specifically, for example, this procedure may be a UE Parameter Update (UPU) procedure, a Generic UE configuration update procedure, a DL NAS transport procedure, or the like. In a procedure for remote provisioning via a control plane, the UE may receive a NAS message including information on a destination SNPN and / or qualification information such as credential(s) from the core network in any of these or other procedures. Here, for example, the NAS message may be a DL NAS transport message and may include a container information element or a transparent container information element including information on the SNPN and / or qualification information such as credential(s).

[0349] Next, as a specific example of a procedure for remote provisioning via the control plane, a UE Parameter Update procedure (also referred to as a UPU procedure) will be described with reference to FIG.

[0350] Here, the UPU procedure may be initiated by the UDM or may be initiated by a decision to execute this procedure by the UDM, which will be described later. Alternatively, the UE may recognize that this procedure has been initiated based on receiving a DL NAS transport message including a UPU container information element.

[0351] First, the UDM that decided to start this procedure sends a notification message to the affected AMF about the changes in information about the UE, including data (UDM Update Data) that needs to be transparently delivered to the UE. Here, the UDM Update Data sent from the UDM to the AMF may include information about the SNPN and / or credentials, e.g., credential(s), as updated parameters to be delivered to the UE.

[0352] Next, the AMF sends a DL NAS transport message to the served UE (S800). Here, the AMF may include the transparent container received from the DUM in the DL NAS transport message. Here, the transparent container may be a UPU transparent container (UE parameters update transparent container) and may be included in the DL NAS transport message as a UPU transparent container information element. Furthermore, the transparent container may include the above-mentioned SNPN information and / or qualification information such as credential(s), or may be UDM Update Data including these. Furthermore, the UE may confirm that the UDM Update Data included in the received DL NAS transport message is provided by the HPLMN, the SNPN, or a CH (Credentials Holder). Furthermore, the UE may store the SNPN information and / or qualification information such as credential(s).

[0353] Next, if the UDM requests the UE to send an acknowledgment, the UE may include a transparent container containing the UE acknowledgment in a UL NAS transport message and send it to the serving AMF (S802).

[0354] Furthermore, each device of the UE and / or core network may complete this procedure by the UE receiving a DL NAS transport message, or the UE sending a UL NAS transport message, or the AMF receiving the UL NAS transport message sent by the UE.

[0355] Furthermore, the UE may recognize that the remote provisioning via the control plane is complete by completing this procedure or by receiving a DL NAS transport message containing information about the SNPN and / or credentials, e.g., credential(s). After completing this procedure, the UE may use the received information about the SNPN and / or credentials, e.g., credential(s), to initiate and perform a registration procedure for connection to the SNPN and / or a PDU session establishment procedure for establishing a normal PDU session for transmitting and receiving user data.

[0356] [3.1.6. De-registration procedure] Next, the de-registration procedure will be explained. 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 UE's registration with the network. It may also be a procedure to set the UE state to a de-registered state (5GMM-DEREGISTERED state).

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

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

[0359] Furthermore, the trigger for this procedure may be completion of the SNPN information provision procedure. In other words, the trigger for this procedure may be completion of the SNPN information provision. Furthermore, the trigger for this procedure may be completion of remote provisioning via the user plane or the control plane in the onboarding service.

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

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

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

[0363] Unless otherwise specified, the de-registration procedure in the present invention may be a procedure initiated and executed by the UE or the core network to de-register a UE that has completed a remote provisioning procedure from an onboarding destination network (e.g., an ON-SNPN or an ON-PLMN). Specifically, the onboarding destination network may be, for example, an ON-SNPN or ON-PLMN to which the UE has registered for onboarding, and this procedure may de-register the UE from the ON-SNPN or ON-PLMN.

[0364] In addition, the network-initiated deregistration procedure may be a procedure that is initiated by the AMF sending a deregistration request message to the UE via the 5G AN (or gNB), and completed by the UE receiving the deregistration request message sending a deregistration accept message to the AMF via the 5G AN (or gNB).

[0365] In addition, the UE-initiated deregistration procedure may be initiated by the UE sending a deregistration request message to the AMF via the 5G AN (or gNB), and completed by the AMF receiving the deregistration request message sending a deregistration accept message to the UE via the 5G AN (or gNB).

[0366] Here, the non-registration procedure initiated by the UE (UE-initiated non-registration procedure) may be a procedure initiated by the UE after completing the registration procedure for onboarding and / or remote provisioning via the user plane or the control plane. More specifically, for example, the non-registration procedure may be a procedure executed by a UE after completing the registration procedure for onboarding and successfully completing remote provisioning of an SO-SNPN credential via the user plane or the control plane, to deregister from the ON-SNPN. Alternatively, for example, the non-registration procedure may be a procedure executed by a UE after completing the registration procedure for onboarding and successfully completing remote provisioning of an SO-SNPN credential via the user plane or the control plane, to deregister from the ON-SNPN.

[0367] Furthermore, here, the network-initiated de-registration procedure (UE-initiated de-registration procedure) may be a network-initiated de-registration procedure triggered by the expiration of a timer based on an ON-SNPN policy that is initiated when the registration procedure for onboarding is completed and the UE is registered with the ON-SNPN. More specifically, for example, when the UE is registered with the ON-SNPN for onboarding, the procedure may be triggered and executed by the expiration of an implementation-specific timer that is started by the AMF based on the ON-SNPN policy to de-register the UE from the ON-SNPN. Note that the timer that the AMF starts based on the ON-SNPN policy when the UE is registered with the ON-SNPN may be a 5GS mobility management timer, which may be a "Timer for onboarding services."

[0368] Furthermore, the de-registration procedure in the present invention may be a procedure executed as part of a procedure for onboarding, and the UE and / or the network may complete onboarding based on the completion of this procedure. Here, the procedure for onboarding may be composed of a registration procedure for onboarding (described in Chapter 3.1.3, etc.), a remote provisioning procedure via the user plane or the control plane (described in Chapter 3.1.4, etc.), and a de-registration procedure. Furthermore, if implicit de-registration is executed after each procedure in onboarding instead of this procedure, onboarding may be completed based on the UE transitioning to a de-registered state by implicit de-registration.

[0369] [3.2. First Embodiment] In a first embodiment of the present invention, a registration procedure for onboarding indicates to a network that remote provisioning via a control plane will be performed, and the network performs the remote provisioning via the control plane. Here, the registration procedure for remote provisioning may be the registration procedure described in Section 3.1.3, and the UE and the network may transmit and receive identification information for performing remote provisioning via the control plane. Note that the first embodiment will also be referred to as the present embodiment in this section.

[0370] Unless otherwise specified, this embodiment may be implemented by a combination of one or more procedures or processes described in Section 3.1, or by transmitting and receiving identification information.

[0371] This embodiment may be executed when the UE and / or the network have completed the system information acquisition and / or network selection described in 3.1.1 to 3.1.3. Here, the UE may have received and acquired information (NID and NID) of the SNPN (ON-SNPN) to which it is onboarding during the system information acquisition, and may have completed or determined the selection of a specific SNPN as the network to which it is connected for onboarding based on the information.

[0372] Here, a UE that has completed or determined the selection of an SNPN as the network to connect to for onboarding may send a registration request message in the registration procedure for onboarding, including first identification information indicating that the UE supports remote provisioning via the control plane, and / or second identification information indicating that the UE requests remote provisioning via the control plane.

[0373] Next, the network (SNPN) and each device that received the first and / or second identification information may transmit a registration accept message that is a response to the registration request message, including third identification information indicating that the network (SNPN) supports remote provisioning via the control plane and / or fourth identification information indicating that remote provisioning via the control plane will be performed. The UE may receive the registration accept message including the third or fourth identification information transmitted by the network, and the UE that receives the registration accept message including the third and / or fourth identification information may recognize that remote provisioning via the control plane has been accepted and will be performed.

[0374] Furthermore, after the registration procedure for onboarding is completed, each device of the UE and the network may perform a procedure for remote provisioning via the control plane based on any one or more of the first to fourth identification information sent and received during the registration procedure for onboarding.

[0375] Also, here, for example, the second identification information may be a registration type indicating a request to execute remote provisioning via the control plane. More specifically, for example, when a UE requests remote provisioning via the control plane, a registration type information element (IE) included in a registration request message transmitted by the UE in a registration procedure for onboarding may be a value or information indicating SNPN onboarding registration for executing remote provisioning via the control plane, and may be the second identification information in this specification.

[0376] For example, when the UE requests remote provisioning via the user plane, the second identification information may not be included in the registration request message in the registration procedure for onboarding, and the registration type information element may be "SNPN onboarding registration."

[0377] [3.3. Second embodiment] The second embodiment of the present invention relates to the behavior of each device of the UE and the network (SNPN) when a procedure for remote provisioning via a control plane initiated by the network is initiated while the UE is executing a PDU session establishment procedure for remote provisioning via a user plane, or when a PDU session establishment accept message including identification information indicating that remote provisioning via the control plane will be performed is received from the network during a PDU session establishment procedure for remote provisioning initiated by the UE.

[0378] Furthermore, if a procedure for network-initiated CP remote provisioning is initiated while the UE is performing a PDU session establishment procedure for UP remote provisioning, this is an abnormal case, and the UE and network devices cannot handle it in their normal manner.

[0379] The present embodiment aims to clarify or define the behavior of each device in the UE and the network for executing processing including handling of such abnormal cases.

[0380] Examples of each behavior in this embodiment are described below (Chapter 3.3.1 to Chapter 3.3.3). Unless otherwise specified, each example of behavior in this embodiment may be performed by a combination of one or more procedures or processes described in Chapter 3.1, or by transmitting and receiving identification information.

[0381] [3.3.1] Here, as an example of the second embodiment, it is assumed that the UE receives a PDU session establishment rejection message from the core network during a PDU session establishment procedure for remote provisioning via the user plane, the PDU session establishment rejection message including identification information indicating that remote provisioning via the control plane will be performed.

[0382] In one example of the second embodiment, for example, after completing a registration procedure for onboarding, the UE transmits a PDU session establishment request message in a PDU session establishment procedure for provisioning via the user plane, and receives a PDU session establishment rejection message from the network, the PDU session establishment rejection message including tenth identification information indicating that remote provisioning via the control plane is to be performed, where the tenth identification information may be a rejection reason value.

[0383] Furthermore, a UE that receives the tenth identification information included in the PDU session establishment rejection message may recognize that it should perform remote provisioning via the control plane instead of UE-initiated remote provisioning via the user plane, or may perform a network-initiated remote provisioning procedure via the control plane.

[0384] In addition, the UE and each device in the network may transmit and receive one or more of the first to fifth identification information during the registration procedure for onboarding. Furthermore, for example, the UE may recognize that a procedure for remote provisioning via the user plane has been accepted or needs to be performed based on the registration procedure for onboarding or the identification information transmitted and received during the registration procedure for onboarding. Alternatively, for example, the UE may initiate a procedure for remote provisioning via the user plane based on the fact that a procedure for network-initiated remote provisioning via the control plane has not been initiated for a certain period of time based on the value of a timer indicated by the fifth identification information received during the registration procedure, and the timer indicated by the fifth identification information may be started in the UE based on completion of the registration procedure for onboarding.

[0385] Furthermore, the timing at which the UE receives the PDU session establishment rejection message including the 10th identification information from the network may be before or after the start of remote provisioning via the network-initiated control plane.

[0386] [3.3.2.] Here, as an example of the second embodiment, it is assumed that, when a procedure for remote provisioning via a network-initiated control plane is initiated while a UE is executing a PDU session establishment procedure for remote provisioning via a user plane, the UE aborts the ongoing PDU session establishment procedure and executes the procedure for remote provisioning via a network-initiated control plane.

[0387] In one example of the second embodiment, for example, after completing the registration procedure for onboarding, if the UE receives a message instructing the UE to initiate the procedure for remote provisioning via the control plane, and the procedure for remote provisioning via the control plane initiated by the network is initiated while the UE is executing a PDU session establishment procedure for remote provisioning via the user plane, the UE may cancel the ongoing PDU session establishment procedure. Note that, during the registration procedure for onboarding, the UE and the network may have transmitted and received any one or more of the first to fifth identification information, as described above.

[0388] Here, "a procedure for NW-initiated CP remote provisioning is initiated during execution of a PDU session establishment procedure for remote provisioning via the user plane" may mean, for example, that a procedure for network-initiated remote provisioning via the control plane is initiated and executed at any timing between when the UE transmits a PDU session establishment request message during the PDU session establishment procedure and when the UE receives a PDU session establishment acceptance or rejection response message from the network. Note that, here, "initiation of a procedure for network-initiated remote provisioning via the control plane" may mean, for example, that the UE receives a message for initiating remote provisioning via the control plane. In other words, for example, when the UE receives a DL NAS Transport message from the network during a UPU procedure executed for remote provisioning via the control plane, the UE may recognize that remote provisioning via the control plane has been initiated.

[0389] The message for initiating remote provisioning via the control plane is not limited to a DL NAS transport message, but may be any message received by the UE within the remote provisioning procedure via the control plane.

[0390] Furthermore, "aborting a PDU session establishment procedure for remote provisioning via the user plane that is currently being performed by the UE" may mean, for example, suspending the procedure without waiting for a PDU session establishment acceptance or rejection message that is a response message to a PDU session establishment request message sent by the UE, or may mean, for example, ignoring a message related to the PDU session establishment procedure that is received after the UE has aborted the PDU session establishment procedure.

[0391] Furthermore, the UE may recognize the initiation of a procedure for network-initiated remote provisioning via the control plane, for example, by receiving a DL NAS Transport message in a UPU procedure. Also, for example, the UE may recognize that remote provisioning via the control plane is to be performed instead of remote provisioning via the user plane, based on the initiation of a procedure for network-initiated remote provisioning via the control plane during a PDU session establishment procedure.

[0392] Based on the above procedures and / or recognition, for example, if a procedure for remote provisioning via the control plane initiated by the network is initiated while a PDU session establishment procedure for remote provisioning via the user plane is being executed and the UE receives a message to start remote provisioning via the control plane during the procedure for remote provisioning via the control plane, the UE may cancel the PDU session establishment procedure, which is the procedure for remote provisioning via the user plane that is currently being executed, or may continue to execute the procedure for remote provisioning via the control plane initiated and initiated by the network.

[0393] [3.3.3.] Here, it is assumed that if a network-initiated procedure for remote provisioning via the control plane is initiated while the UE is performing a PDU session establishment procedure for remote provisioning via the user plane, the UE will not abort the ongoing PDU session establishment procedure and will not abort the procedure for remote provisioning via the user plane, but will continue it.

[0394] For example, if, after completing the registration procedure for onboarding, the UE is executing a PDU session establishment procedure for remote provisioning via the user plane and receives a message initiating a procedure for remote provisioning via the control plane initiated by the network, the UE does not abort the ongoing PDU session establishment procedure but continues it.

[0395] Here, as described in Chapter 3.3.2, if a procedure for CP remote provisioning initiated by the network is initiated while a PDU session establishment procedure for remote provisioning via the user plane is being executed, the UE does not recognize the start of the procedure executed for remote provisioning via the control plane, or if it recognizes it, ignores it, does not terminate the ongoing PDU session establishment procedure, but continues it, and executes UP remote provisioning using the PDU session established in the PDU session establishment procedure for remote provisioning via the user plane.

[0396] In the embodiment of this chapter, the UE may not execute a procedure for remote provisioning initiated by the network via the control plane, and may not transmit a response message to a message received from the network, for example.

[0397] As described above, the embodiment of this chapter may be a case where a procedure for provisioning initiated by a UE is not stopped but continued regardless of the situation. The procedure for provisioning initiated by a UE may be remote provisioning via a user plane.

[0398] [3.4. Third Embodiment] A third embodiment of the present invention is an embodiment in which a UE starts a timer based on completion of a registration procedure for onboarding, and does not start or execute a procedure for remote provisioning via the user plane until the timer expires. Here, the timer that the UE starts based on completion of a registration procedure for onboarding may be based on a timer value indicated by fifth identification information that the UE received from the network during the registration procedure. Furthermore, the procedure for remote provisioning via the user plane may be a PDU session establishment procedure for establishing a PDU session for remote provisioning of the UE via the user plane. Note that the first embodiment will also be referred to as this embodiment in this chapter.

[0399] Unless otherwise specified, this embodiment may be implemented by a combination of one or more procedures or processes described in Section 3.1, or by transmitting and receiving identification information.

[0400] Furthermore, the UE in this embodiment may recognize the accepted remote provisioning procedure or the remote provisioning procedure to be executed based on the onboarding registration procedure, identification information or messages transmitted and received in the onboarding registration procedure, a UE policy, or a network policy. For example, the UE may recognize that a remote provisioning procedure via the user plane has been accepted or needs to be executed. Or, for example, the UE may recognize that a remote provisioning procedure via the control plane has been accepted or needs to be executed. Or, for example, the UE may recognize that a remote provisioning procedure via the user plane and a remote provisioning procedure via the control plane have been accepted or that either one needs to be executed. Note that subsequent behavior may or may not be based on the UE's recognition.

[0401] In this embodiment, the UE first starts a timer based on the fifth identification information received from the network during the registration procedure for onboarding (also referred to as a timer based on the fifth identification information). Here, while the timer is running, the UE may be restricted or prohibited from performing a procedure for remote provisioning via the user plane. More specifically, for example, while the UE is running a timer based on the timer value indicated by the fifth identification information, the UE may be restricted or prohibited from starting and performing a PDU session establishment procedure as a procedure for remote provisioning via the user plane.

[0402] Next, the UE may initiate and perform a procedure for remote provisioning via a user plane upon expiration of the timer based on the fifth identity. More specifically, for example, the UE may initiate a PDU session establishment procedure for remote provisioning via a user plane upon expiration of the timer based on the fifth identity, and may send a PDU session establishment message to the network.

[0403] For example, when a UE that is running a timer based on the fifth identification information receives a message for initiating remote provisioning via the network-initiated control plane, the UE may stop the timer and execute the initiated remote provisioning procedure via the control plane. Alternatively, when a UE that is running a timer based on the fifth identification information receives a message for initiating remote provisioning via the network-initiated control plane, the UE may not stop the running timer, but may start and execute the procedure for remote provisioning via the user plane upon expiration of the timer.

[0404] [4. Modifications] A program running on an apparatus according to 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.

[0405] A program for implementing the functions of the embodiments of the present invention may be recorded on a computer-readable recording medium. The program may be read 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 also 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.

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

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

[0408] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the present invention. Furthermore, the present invention allows various modifications within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Also included are configurations in which elements described in the above embodiments are substituted with elements that achieve similar effects. (Cross-Reference to Related Applications) This application claims priority to Japanese Patent Application No. 2022-006056, filed January 19, 2022, the entire contents of which are incorporated herein by reference.

[0409] 1 Mobile communication system 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access network_A (E-UTRAN) 90 Core network_A 120 Access network_B (5G AN) 122 gNB 130 UPF 132 SMF 140 AMF 141 new AMF 142 old AMF 150 UDM 160 PCF 190 Core network_B

Claims

1. A UE (User Equipment) including a transceiver unit and a control unit, The transceiver unit transmits a registration request message including first or second identification information to a network in a registration procedure for onboarding; the first identification information indicates that the UE supports remote provisioning via a control plane; the second identification information indicates a request to perform remote provisioning via a control plane; the transceiver receives a registration acceptance message from the network, the registration acceptance message including the third or fourth identification information; the third identification indicates that the network supports remote provisioning via a control plane; the fourth identification information indicates that remote provisioning via a control plane is to be performed; the control unit executes a procedure for remote provisioning via a control plane based on one or more of the first to fourth identification information after the registration procedure for the onboarding is completed. A UE characterized by:

2. the second identification information is a registration type indicating a request to perform remote provisioning via a control plane; The UE according to claim 1 , characterized in that:

3. When the transceiver unit receives a message from the network to start a procedure for remote provisioning via the control plane initiated by the network during execution of a PDU session establishment procedure for remote provisioning via the user plane, The control unit Aborting a PDU session establishment procedure for remote provisioning via the user plane; continuing a procedure for remote provisioning via the network-initiated control plane; The UE of claim 1 .