JP2023053426A - UE (User Equipment) - Google Patents

Abstract

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

Description

The present disclosure relates to UE (User Equipment).

3GPP (3rd Generation Partnership Project) has started to study the system architecture of 5GS (5G System), which is the next-generation mobile communication system, i.e., the 5th generation (5G), and supports new procedures and new functions. Discussions have been made (see Non-Patent Document 1, Non-Patent Document 2, Non-Patent Document 3, Non-Patent Document 4, Non-Patent Document 5, Non-Patent Document 6, and Non-Patent Document 5).

For example, optimization and diversification of communication procedures to support continuous mobile communication services in response to a wide variety of services, and optimization of system architecture in accordance with optimization and diversification of communication procedures. mentioned as a condition.

3GPP TS 23.501 v17.2.0 (2021-09); Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 17) 3GPP TS 23.502 v17.2.0 (2021-09); Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 17) 3GPP TS 24.501 v17.4.0 (2021-09); Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (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.122 V17.4.0 (2021-09); Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode (Release 17) 3GPP TS 23.003 V17.3.0 (2021-09); Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17)

In 5GS (5G System), 5GCN (5G Core Network), which is a new core network, is under consideration in order to provide a wide variety of services. In 5GS, a non-public network such as NPN (Non-Public Network) that can be used by specific users for specific purposes is defined separately from PLMN (Public Land Mobile Network), which is a public network. Functions for providing a public network and realizing a private network are also being considered. Further, communication means between UE and ONN (Onboarding Network) is also under study as a communication means for providing NPN information to UE when connection and registration of UE to NPN are required.

Currently, regarding the handling of the 5GS mobile identity IE during the initial registration procedure, the behavior is not clear when the UE has not performed the initial registration for the onboarding service. In other words, in the initial registration procedure, if the UE does not hold a valid 5G-GUTI or a SUCI other than the onboarding SUCI and has not initiated initial registration for the onboarding service, the UE , it cannot determine whether the 5GS mobile identity IE should be included in the registration request message, and it cannot determine what information should be included when the 5GS mobile identity IE is included in the registration request message.

One aspect of the present invention has been made in view of the circumstances as described above, and the purpose thereof is that, in the initial registration procedure, the UE holds a valid 5G-GUTI or a SUCI other than the onboarding SUCI. and has not initiated initial registration for onboarding services, the UE shall include the 5GS mobile identity IE in the registration request message and clarify the information to be included in the 5GS mobile identity IE.

A UE of one aspect of the present invention includes a control unit, and if the UE does not hold a valid 5G-GUTI or a SUCI other than an onboarding SUCI, and The control unit includes the PEI in the 5GS mobile identity IE if the initial registration for the mobile identity has not started.

According to one aspect of the present invention, it is possible to clarify the information to be included in the 5GS mobile identity IE if the UE has not initiated initial registration for the onboarding service.

1 is a diagram explaining an outline of a mobile communication system (EPS/5GS); FIG. FIG. 2 is a diagram illustrating a detailed configuration of a mobile communication system (EPS/5GS); It is a figure explaining the apparatus structure of UE. FIG. 2 is a diagram explaining the configuration of an access network device (gNB) in 5GS; FIG. 2 is a diagram illustrating the configuration of core network equipment (AMF/SMF/UPF) in 5GS; It is a figure explaining a registration procedure.

A best mode for carrying out one aspect of the present invention will be described with reference to the drawings.

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

In FIG. 1, a mobile communication system 1 includes UE_A10, access network_A80, core network_A90, PDN (Packet Data Network)_A5, access network_B120, core network_B190, and DN (Data Network)_A6. It is stated that

In the following, these devices and functions may be described with abbreviated symbols such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc. .

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, etc. Interfaces for connecting devices/functions to each other are described.

In the following, these devices/functions are abbreviated as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, etc. may be omitted.

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

A UE is a device capable of connecting to a network service via a 3GPP access (also called a 3GPP access network, 3GPP AN) and/or a non-3GPP access (also called a non-3GPP access network, non-3GPP AN). be. The UE may be a terminal device capable of wireless communication, such as a mobile phone or a smartphone, and may be a terminal device connectable to both EPS and 5GS. A UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Note that the UE may be expressed as a user equipment, or may be expressed as a terminal equipment.

Also, the 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 arranged in the E-UTRAN. In addition, below, eNB45 may be described by abbreviate|omitting a symbol like eNB. Also, if there are multiple eNBs, each eNB is connected to each other, for example, by an X2 interface. Also, one or more access points are arranged in the wireless LAN access network.

Also, access network_B corresponds to a 5G access network (5G AN). 5G AN consists of NG-RAN (NG Radio Access Network) and/or non-3GPP access network. One or more gNBs (NR NodeBs) 122 are arranged in the NG-RAN. In the following description, the gNB 122 may be described by omitting the symbol, such as eNB. A gNB is a node that provides an NR (New Radio) user plane and a control plane to a UE, and is a node that connects to a 5GCN via an NG interface (including an N2 interface or an N3 interface). That is, the gNB is a base station apparatus newly designed for 5GS, and has functions different from those of the base station apparatus (eNB) used in EPS, which is a 4G system. Also, if there are multiple gNBs, each gNB is connected to each other, for example, by an Xn interface.

Also, hereinafter, E-UTRAN and NG-RAN may be referred to as 3GPP access. Also, wireless LAN access networks and non-3GPP ANs are sometimes referred to as non-3GPP access. In addition, the nodes arranged in access network_B may also be collectively referred to as NG-RAN nodes.

Also, hereinafter, access network_A and/or access network_B and/or devices included in access network_A and/or devices included in access network_B are access networks or access network devices sometimes referred to as

Furthermore, the RAN may be expressed as an access network. Conversely, the access network may be referred to as RAN.

Also, Core Network_A corresponds to EPC (Evolved Packet Core). EPC includes MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc. placed.

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

In addition, hereinafter, core network_A and/or core network_B, devices included in core network_A, and/or devices included in core network_B are referred to as core networks or core network devices. There is

The core network (core network_A and/or core network_B) is a mobile communication carrier (Mobile It may be an IP mobile communication network operated by a network operator (MNO), a core network for a mobile communication carrier that operates and manages the mobile communication system 1, or a mobile virtual network operator (MVNO). ), MVNE (Mobile Virtual Network Enabler) and other core networks for virtual mobile communication operators and virtual mobile communication service providers.

Also, although FIG. 1 describes the case where the PDN and DN are the same, they may be different. The PDN may be a DN (Data Network) that provides communication services to the UE. Note that the DN may be configured as a packet data service network, or may be configured for each service. Additionally, the PDN may include connected communication terminals. Therefore, connecting to a PDN may be connecting to a communication terminal or server device located in the PDN. Furthermore, transmitting/receiving user data to/from the PDN may be transmitting/receiving user data to/from a communication terminal or server device located in the PDN. PDN may be expressed as DN, and DN may be expressed as PDN.

Also, hereinafter, access network_A, core network_A, PDN, access network_B, core network_B, at least a part of DN, and/or one or more devices included therein are referred to as network or network device is sometimes called. That is, the fact that the network and/or network devices send/receive messages and/or perform procedures means that Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN It means that at least some and/or one or more devices included therein send and receive messages and/or perform procedures.

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

Here, IP communication is data communication using IP, and data is transmitted and received by IP packets. An IP packet consists of an IP header and a payload. The payload part may include data transmitted and received by devices/functions included in EPS and devices/functions included in 5GS. Non-IP communication is data communication that does not use IP, and data is transmitted and received in a format different from the structure of IP packets. For example, non-IP communication may be data communication realized by sending and receiving application data to which no IP header is attached, or may be data communication realized by attaching another header such as a MAC header or Ethernet (registered trademark) frame header to the UE. User data to be transmitted and received may be transmitted and received.

[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, may be configured as logical (virtual) hardware configured on general-purpose hardware, or may be configured as software. May be. Also, at least part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

In addition, each storage unit (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) in each device/function that appears below is, for example, a semiconductor memory, SSD ( Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each storage unit stores not only information originally set from the shipping stage, but also devices/functions other than the own device/function (for example, UE, and/or access network device, and/or core network device, and/or or PDN and/or DN), and can store various types of information sent and received. Further, each storage unit can store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures to be described later. Also, each storage unit may store these pieces of information for each UE. In addition, when interworking between 5GS and EPS, each storage unit can store control messages and user data sent and received between devices and functions included in 5GS and/or EPS. can. At this time, not only data sent and received via the N26 interface but also data sent and received without the N26 interface can be stored.

[2.1. Equipment configuration of UE]
First, a device configuration example of UE (User Equipment) will be described with reference to FIG. The UE is composed of a control unit_A300, an antenna 310, a transmission/reception unit_A320, and a storage unit_A340. The control unit_A300, transmission/reception unit_A320, and storage unit_A340 are connected via a bus. Transceiver_A 320 is connected to antenna 310 .

The control unit_A300 is a functional unit that controls the operations and functions of the entire UE. The control unit _A300 realizes various processes in the UE by reading and executing various programs stored in the storage unit _A340 as necessary.

Transceiver_A320 is a functional unit for wirelessly communicating with a base station apparatus (eNB or gNB) in an access network via an antenna. That is, the UE can transmit/receive user data and/or control information to/from an access network device and/or a core network device and/or a PDN and/or a DN using the transmitting/receiving unit_A320. can.

To explain in detail with reference to FIG. 2, the UE can communicate with the base station apparatus (eNB) in E-UTRAN via the LTE-Uu interface by using the transceiver _A320. Also, the UE can communicate with the base station apparatus (gNB) within the 5G AN by using the transceiver _A320. Also, the UE can transmit and receive AMF and NAS (Non-Access-Stratum) messages via the N1 interface by using the transmitting/receiving unit_A320. However, since the N1 interface is a logical one, in practice the communication between the UE and the AMF will take place over the 5G AN.

The storage unit_A340 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UE.

[2.2. Equipment configuration of gNB]
Next, a device configuration example of the gNB will be described using FIG. The gNB consists of a control unit_B500, an antenna 510, a network connection unit_B520, a transmission/reception unit_B530, and a storage unit_B540. The control unit_B500, network connection unit_B520, transmission/reception unit_B530, and storage unit_B540 are connected via a bus. Transceiver_B 530 is connected to antenna 510 .

The control unit_B500 is a functional unit that controls the operations 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 storage unit_B540 as necessary.

Network connection unit_B520 is a functional unit for gNB to communicate with AMF and/or UPF. That is, the gNB can transmit and receive user data and/or control information to/from AMF and/or UPF using Network Connection Unit_B520.

Transceiver_B 530 is a functional unit for wireless communication with UE via antenna 510 . That is, the gNB can transmit/receive user data and/or control information to/from the UE using the transmitting/receiving unit_B530.

To explain in detail with reference to FIG. 2, the gNB in the 5G AN can communicate with the AMF through the N2 interface by using the Network Connection Part_B520, and the UPF through the N3 interface. can communicate with Also, the gNB can communicate with the UE by using the transceiver_B530.

The storage unit_B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB.

[2.3. Equipment configuration of AMF]
Next, an example configuration of the AMF will be described with reference to FIG. The AMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. AMF may be a node that handles the control plane.

The control unit_B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit_B700 implements various processes in the AMF by reading and executing various programs stored in the storage unit_B740 as necessary.

Network connection unit_B720 is a functional unit for AMF to connect with a base station apparatus (gNB) in 5G AN, and/or SMF, and/or PCF, and/or UDM, and/or SCEF. That is, AMF uses the network connection unit _B720 to connect the user Data and/or control information can be sent and received.

To explain in detail with reference to FIG. 2, AMF in 5GCN can communicate with gNB through N2 interface by using network connection part_A620, and with UDM through N8 interface. It can communicate with SMF via the N11 interface and with PCF via the N15 interface. Also, the AMF can transmit and receive NAS messages with the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is a logical one, in practice the communication between the UE and the AMF will take place over the 5G AN. Also, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit_A620.

The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the AMF.

The AMF has functions to exchange control messages with the RAN using the N2 interface, functions to exchange NAS messages with the UE using the N1 interface, encryption and integrity protection functions for NAS messages, and registration management. (Registration management; RM) function, Connection management (CM) function, Reachability management function, Mobility management function such as UE, SM (Session Management) between UE and SMF N2 for message forwarding function, Access Authentication (Access Authorization) function, Security Anchor Functionality (SEA), Security Context Management (SCM) function, N3IWF (Non-3GPP Interworking Function) It has a function to support interfaces, a function to support transmission and reception of NAS signals with UEs via N3IWF, a function to authenticate UEs connected via N3IWF, and so on.

Also, in registration management, the RM state for each UE is managed. The RM state may be synchronized between the UE and AMF. The RM state includes a non-registered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered with the network, so the UE context in the AMF does not have valid location and routing information for the UE, so the AMF cannot reach the UE. Also, in the RM-REGISTERED state, the UE is registered with the network so that the UE can receive services that require registration with the network. Note that the RM state may 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.

In other words, 5GMM-REGISTERED may be a state in which each device has established a 5GMM context or a state in which each device has established a PDU session context. Note that if each device is 5GMM-REGISTERED, UE_A 10 may start sending and receiving user data and control messages, and may respond to paging. Furthermore, it should be noted that if each device is 5GMM-REGISTERED, UE_A 10 may perform registration procedures other than those for initial registration and/or service request procedures.

Furthermore, 5GMM-DEREGISTERED may be a state where each device has not established a 5GMM context, a state where the location information of UE_A10 is not grasped by the network, or a state where the network reaches UE_A10. It may be in a state of being disabled. Note that if each device is 5GMM-DEREGISTERED, UE_A 10 may initiate a registration procedure or establish a 5GMM context by performing the registration procedure.

Also, in connection management, the CM state for each UE is managed. CM states may be synchronized between the UE and the AMF. CM states include a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In CM-IDLE state, the UE is in RM-REGISTERED state but does not have a NAS signaling connection established with AMF over the N1 interface. Also, in the CM-IDLE state, the UE does not have a connection of the N2 interface (N2 connection) and a connection of the N3 interface (N3 connection). On the other hand, in the CM-CONNECTED state, it has a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-CONNECTED state, the UE may have a connection on the N2 interface (N2 connection) and/or a connection on the N3 interface (N3 connection).

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

Note that the CM state may be expressed as a 5GMM mode. In this case, the disconnected state may be expressed as a 5GMM disconnected mode (5GMM-IDLE mode), and the connected state may be expressed as a 5GMM connected mode (5GMM-CONNECTED mode). Furthermore, the disconnected state in 3GPP access may be expressed as 5GMM disconnected mode over 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access may be expressed as 5GMM connected mode over 3GPP access (5GMM-IDLE mode over 3GPP access). CONNECTED mode over 3GPP access). Furthermore, the non-connected state in non-3GPP access may be expressed as 5GMM non-connected mode (5GMM-IDLE mode over non-3GPP access) in non-3GPP access, and the connected state in non-3GPP access is non- -It may be expressed as 5GMM-CONNECTED mode over non-3GPP access. Note that the 5GMM non-connected mode may be expressed as an idle mode, and the 5GMM connected mode may be expressed as a connected mode.

Also, one or more AMFs may be arranged in core network_B. Also, the AMF may be an NF that manages one or more NSIs (Network Slice Instances). Also, the AMF may be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among multiple NSIs.

Note that N3IWF is a device and/or function placed between non-3GPP access and 5GCN when UE connects to 5GS via non-3GPP access.

[2.4. Equipment configuration of SMF]
Next, an example of the SMF device configuration will be described with reference to FIG. The SMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF may be a node handling the control plane.

The control unit_B700 is a functional unit that controls the operations and functions of the entire SMF. The control unit_B700 realizes various processes in the SMF by reading out and executing various programs stored in the storage unit_B740 as necessary.

Network connection unit_B720 is a functional unit for SMF to connect with AMF and/or UPF and/or PCF and/or UDM. That is, the SMF can send and receive user data and/or control information to/from AMF and/or UPF and/or PCF and/or UDM using network connection part_B720.

To explain in detail with reference to FIG. 2, SMF in 5GCN can communicate with AMF through N11 interface by using network connection part_A620, and with UPF through N4 interface. Through the N7 interface, it can communicate with the PCF, and through the N10 interface, it can communicate with the UDM.

The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of SMF.

The SMF includes Session Management functions such as PDU session establishment, modification, and release, IP address allocation for UEs and their management functions, UPF selection and control functions, appropriate destinations (destinations, etc.). ), a function to send and receive the SM part of NAS messages, a function to notify that downlink data has arrived (Downlink Data Notification), AN via the N2 interface via AMF It has a function to provide AN-specific (for each AN) SM information, a function to determine the SSC mode (Session and Service Continuity mode) for the session, a roaming function, and so on.

[2.5. Equipment configuration of UPF]
Next, an example configuration of the UPF will be described with reference to FIG. The UPF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. A UPF may be a node that handles the control plane.

The control unit_B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit_B700 implements various processes in the UPF by reading and executing various programs stored in the storage unit_B740 as necessary.

Network connection unit_B720 is a functional unit for UPF to connect with base station apparatus (gNB) in 5G AN and/or SMF and/or DN. That is, the UPF uses the network connection unit _B720 to transmit and receive user data and/or control information between the base station apparatus (gNB) in the 5G AN and/or the SMF and/or the DN. can be done.

To explain in detail with reference to FIG. 2, UPF in 5GCN can communicate with gNB through N3 interface by using network connection part_A620, and with SMF through N4 interface. It can communicate, through the N6 interface it can communicate with DNs, and it can communicate with other UPFs through the N9 interface.

The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UPF.

UPF functions as an anchor point for intra-RAT mobility or inter-RAT mobility, as an external PDU session point for interconnecting DNs (that is, as a gateway between DNs and core network_B, users data forwarding function), packet routing and forwarding function, UL CL (Uplink Classifier) function that supports routing of multiple traffic flows for one DN, multi-homed PDU session support It has branching point function, QoS (Quality of Service) processing function for user plane, uplink traffic verification function, downlink packet buffering, downlink data notification triggering function, and so on.

UPF may also be a gateway for IP and/or non-IP communications. Also, the UPF may have the function of transferring IP communication, or the function of converting between non-IP communication and IP communication. Furthermore, multiple gateways may be gateways that connect core network_B and a single DN. Note that the UPF may have connectivity with other NFs, and may be connected to each device via other NFs.

Note that the user plane is user data transmitted and received between the UE and the network. The user plane may be transmitted and received using PDN connections or PDU sessions. Furthermore, for 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, for 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 expressed as U-Plane.

Furthermore, a control plane is a control message that is transmitted and received to control UE communication and the like. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the MME. Additionally, for EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Furthermore, for 5GS, the control plane may be transmitted and received using the interface between the UE and the NG RAN and the N2 interface. Hereinafter, the control plane may be expressed as a control plane or as a C-Plane.

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

[2.6. Description of other devices and/or functions]
Next, other devices and/or functions are described.

The PCF has functions such as providing policy rules.

The UDM also has authentication credential processing functions, user identification processing functions, access authentication functions, registration/mobility management functions, subscription management functions, and the like.

In addition, the PCRF is connected to the PGW and/or PDN and has functions such as QoS management for data delivery. For example, it manages the QoS of the communication path between UE_A10 and PDN. Furthermore, the PCRF may be a device that creates and/or manages PCC (Policy and Charging Control) rules and/or routing rules used when each device transmits and receives user data.

Also, the HSS is connected to the MME and/or SCEF and has functions such as managing subscriber information. HSS subscriber information is referred to, for example, during MME access control. Furthermore, the HSS may be connected with a location management device different from the MME.

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

[3.1. Description of terms and identification information used in each embodiment]
First, highly technical terms used in each embodiment and identification information used in procedures will be explained in advance.

Network refers to at least part of Access Network_B, Core Network_B, and DN. Also, one or more devices included in at least part of access network_B, core network_B, and DN may be referred to as a network or a network device. In other words, the fact that a network performs message transmission/reception and/or processing may mean that a device in the network (a network device and/or a control device) performs message transmission/reception and/or processing. . Conversely, a device in the network performing message transmission/reception and/or processing may mean that the network performs message transmission/reception and/or processing.

Furthermore, the network may refer to PLMN (Public Land Mobile Network) or NPN to be described later. Furthermore, when it is expressed that the UE performs network selection, it may indicate that the UE performs PLMN selection, or it may indicate that the UE performs SNPN selection.

A registered PLMN is a PLMN in which the UE is registered.

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

SM (session management) messages (also called NAS (Non-Access-Stratum) SM messages) may be NAS messages used in procedures for SM, and are transmitted and received between UE_A10 and SMF_A230 via AMF_A240. may be a control message that Further, the SM messages include a PDU session establishment request message, a PDU session establishment accept message, a PDU session complete message, a PDU session reject message, a PDU session change request message, a PDU session change accept message, a PDU session change response message, etc. may The procedures for SM may also include PDU session establishment procedures.

Also, the 5GS (5G System) service may be a connection service provided using the core network_B190. Furthermore, the 5GS service may be a service different from the EPS service or a service similar to the EPS service.

Also, non 5GS services may be services other than 5GS services, and may include EPS services and/or non-EPS services.

Also, single registration mode is a mode in which UE_A 10 maintains a common registration state for 5GMM state and EMM state when N1 mode and S1 mode are available.

Also, dual registration mode is a mode in which UE_A 10 maintains the registration state independently of the 5GMM state and the EMM state when N1 mode and S1 mode are available. In dual registration mode, UE_A10 may be registered in the network only in N1 mode (that is, registered only in 5GC), or registered in the network only in S1 mode (registered only in EPC). Alternatively, it may be registered with the network in both N1 and S1 modes (registered with both 5GC and EPC).

Also, in order to interwork with 5GS and EPC, a UE that supports both 5GC and EPC NAS can operate in single registration mode or dual registration mode.

Also, S1 mode is a mode in which UE_A10 is permitted to access EPC via E-UTRAN. In other words, the S1 mode may be a mode in which message transmission/reception is performed using the S1 interface. Note that the S1 interface may consist of the S1-MME interface and the S1-U interface.

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

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

A PDN (Packet Data Network) type indicates the type of PDN connection, and includes IPv4, IPv6, IPv4v6, and non-IP. When IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is sent and received using IPv6. When IPv4v6 is specified, it indicates that data is sent and received using IPv4 or IPv6. If non-IP is specified, it indicates that communication is to be performed by a communication method other than IP, rather than using IP.

A PDU (Protocol Data Unit) session can also be defined as an association between a DN that provides PDU connectivity services and a UE, but is the connectivity established between the UE and an external gateway. There may be. In 5GS, by establishing a PDU session via access network_B and core network_B, the UE can transmit and receive user data to and from the DN using the PDU session. Here, the external gateway may be UPF, SCEF, or the like. A UE can transmit and receive user data to and from a device such as an application server located in a DN using a PDU session.

Note that each device (UE, and/or access network device, and/or core network device) may associate and manage one or more pieces of identification information with respect to a PDU session. In addition, these identification information may include one or more of DNN, QoS rules, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and other information. Further may be included. Furthermore, when multiple PDU sessions are established, each piece of identification information associated with a PDU session may have the same content or different content.

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

Also, the PDU (Protocol Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet, and Unstructured. When IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Also, Ethernet may indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data is sent and received to the application server, etc. in the DN using Point-to-Point (P2P) tunneling technology. For example, UDP/IP encapsulation technology may be used as the P2P tunneling technology. Note that the PDU session type may include IP in addition to the above. IP can be specified if the UE is capable of using both IPv4 and IPv6.

Also, an RRC (Radio Resource Control) connection is a connection established between a UE and a base station apparatus within an access network. More specifically, an RRC connection is a connection established at a Uu reference point between a UE and a base station device within the access network. An RRC connection may consist of radio bearers. Furthermore, the RRC connection may be a connection established in 3GPP access. Furthermore, the RRC connection may be a connection established in the RRC layer below the NAS layer. Furthermore, the RRC connection may be a connection that is established and/or released by sending and receiving RRC messages in the RRC layer. Furthermore, the RRC connection may be a connection that is suspended due to transmission and reception of RRC messages in the RRC layer.

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

The NAS signaling connection may be connectivity via 3GPP access or connectivity via non-3GPP access.

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

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

Here, the Uu reference point may be the reference point between the UE and the gNB. Additionally, the NWu reference point may be the reference point between the UE and the N3IWF. Furthermore, the N2 reference point may be the reference point between the gNB or N3IWF and AMF.

Note that the NAS signaling connection may also be expressed as a NAS signaling connection. Furthermore, a NAS signaling connection may be expressed as an N1 NAS signaling connection.

A tracking area is a single or multiple ranges that can be represented by the location information of UE_A 10 managed by the core network. A tracking area may consist of multiple cells. Furthermore, the tracking area may be a range in which control messages such as paging are broadcast, or a range in which UE_A 10 can move without performing a handover procedure. Further, the tracking area may be a routing area, a location area, or the like. Hereinafter, the tracking area may be a TA (Tracking Area).

The TA list is a list containing one or more TAs assigned to UE_A10 by the network. Note that UE_A 10 may be able to move without executing the tracking area update procedure while moving within one or more TAs included in the TA list. In other words, for UE_A10, the TA list may be a group of information indicating areas to which UE_A10 can move without performing a tracking area update procedure. Note that the TA list may be expressed as a TAI list composed of one or more TAIs (Tracking area identities), and hereinafter, the TAI list may refer to the TA list.

PLMN selection may be a procedure for selecting a PLMN. Also, PLMN selection may be a procedure for the UE to select a PLMN. PLMN selection may also be a procedure performed when a UE connects to a PLMN. PLMN selection may be referred to as a PLMN selection process or a PLMN selection procedure.

A SUCI (Subscription Concealed Identifier) may be a privacy preserving identifier that includes a concealed SUPI, as specified in 3GPP TS 23.003. Also, SUCI may be composed of SUPI Type, Home Network Identifier, Routing Indicator, Protection Scheme Id, Home Network Public Key Identifier, and Scheme Output.

Also, SUPI (Subscription Permanent Identifier) may be the world's only 5G Subscription Permanent Identifier assigned to each subscriber in a 5G system as specified in 3GPP TS 23.003. SUPI may be defined as SUPI type and IMSI or NSI or Global Cable Identifier (GCI) or Global Line Identifier (GLI). Also, the SUPI type may indicate IMSI, or NSI, or GCI, or GLI. That is, when the SUPI type indicates IMSI, the SUPI may consist of the SUPI type indicating IMSI and IMSI. Similarly, when the SUPI type indicates NSI, the SUPI may consist of the SUPI type indicating NSI and the NSI. Also, when the SUPI type indicates GCI, the SUPI may consist of the SUPI type indicating GCI and GCI. Also, when the SUPI type indicates GLI, the SUPI may consist of the SUPI type indicating GLI and GLI.

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

5G-GUTI (5G Globally Unique Temporary Identifier) is an unambiguous UE identifier that does not reveal the user's permanent identity, as specified in 3GPP TS 23.003. It may be information for providing Also, 5G-GUTI may be information that can also identify the AMF and the network. 5G-GUTI may also be information used by the network and the UE to establish the identity of the UE. Also, the 5G-GUTI may consist of two elements: one that identifies the AMF that has assigned the 5G-GUTI, and one that uniquely identifies the UE within the AMF that has assigned the 5G-GUTI. The former may be GUAMI (Globally Unique AMF Identifier) and the latter may be 5G-TMSI (5G-Temporary Mobile Subscriber Identity). That is, 5G-GUTI may consist of GUAMI and 5G-TMSI.

IMEI (International Mobile station Equipment Identity) is TAC (Type Allocation Code), SNR (Serial Number) and CD (Check Digit)/SD (Spare Digit) as specified in 3GPP TS 23.003. may be configured.

Also, IMEISV (International Mobile station Equipment Identity and Software Version number) is composed of TAC (Type Allocation Code), SNR (Serial Number) and SVN (Software Version Number) as specified in 3GPP TS 23.003. may be

5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) may be short for 5G-GUTI as specified in 3GPP TS 23.003. 5G-S-TMSI may also enable more efficient radio signaling procedures, such as paging (also called paging procedure) and service requests (also called service request procedure). Also, for paging, the UE may be paged using 5G-S-TMSI. 5G-S-TMSI may consist of AMF Set ID, AMF Pointer and 5G-TMSI.

A MAC address (Media Access Control address) is the hardware address of a device connected to a shared medium, as defined in the Internet Engineering Task Force (IETF) Request for Comments (RFC). you can Also, the MAC address may be a unique identification number assigned to the UE or network device.

An IEEE Extended Unique Identifier (EUI-64) may be a 64-bit long identifier standardized by IEEE. EUI-64 may also be used when automatically generating IPv6 addresses.

Also, the PEI (Permanent Equipment Identifier) may be information for identifying the UE as specified in 3GPP TS 23.003. Also, PEI may be defined as PEI type and IMEI or IMEISV or MAC address or IEEE EUI-64. Here, the PEI type may indicate IMEI or IMEISV or MAC address or EUI-64. That is, when the PEI type indicates IMEI, the PEI may consist of the PEI type indicating IMEI and the IMEI. Similarly, when the PEI type indicates IMEISV, the PEI may consist of the PEI type indicating IMEISV and IMEISV. Also, when the PEI type indicates a MAC address, the PEI may be composed of the PEI type indicating the MAC address and the MAC address. Also, when the PEI type indicates EUI-64, the PEI may consist of the PEI type indicating EUI-64 and EUI-64.

Also, the 5GS mobile identity may be SUCI or 5G-GUTI or IMEI or IMEISV or 5G-S-TMSI or MAC address or IE to provide EUI-64. 5GS mobile identity uses a registration request message or a registration acceptance message in a registration procedure, a de-registration request message (de-registration request message) in a UE-initiated de-registration procedure (de-registration procedure). or a service request message in a service request procedure, or a configuration update command in a configuration update procedure, or an identifier response message in an identification procedure, or a security mode control procedure ( Security mode control procedure) may be information included in a security mode completion message or the like. 5GS mobile identity may also be referred to as a 5GS mobile identity information element (IE).

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

A Non-Public Network (NPN) is a non-public network that is not intended for general use but is used by specific users for specific purposes such as private use such as companies. There are two types of NPN: Stand-alone Non-Public Network (SNPN) and Public network integrated NPN. In addition, when described as NPN below, both SNPN and Public network integrated NPN may be meant.

A SNPN is a network operated by an NPN operator and unaffected by the functionality provided by a PLMN. In other words, the SNPN is an NPN-only network independent of the publicly available PLMN. A SNPN may be a network identified by a SNPN identity (SNPN ID). The SNPN ID may be information that is a combination of the PLMN ID and Network Identifier (NID). The PLMN ID used for the SNPN ID may be information reserved for a private network, and the MCC included in the PLMN ID may be 999, for example. Furthermore, if the UE is registered with a SNPN, the registered SNPN may be referred to as a registered SNPN or RSNPN (registered SNPN).

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

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

Furthermore, public network integrated NPNs may be implemented using DNs. Specifically, a 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 DNN, or by a combination of DNN and CAG ID.

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

An SNPN enabled UE is a UE configured to use SNPN. A SNPN-enabled UE may store at least one piece of information about the SNPN. In other words, the configuration information of the SNPN-enabled UE may include information indicating that SNPN can be used. Additionally, an SNPN-enabled UE may support an SNPN access mode or an SNPN access mode of operation. In other words, a SNPN enabled UE may operate in SNPN access mode or SNPN access operation mode.

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

SNPN access operation mode is a mode of connecting to SNPN via SNPN access mode or non-3GPP access. Here, "non-3GPP access" in SNPN may refer to the case where UE is connected to SNPN via PLMN. The UE may also operate in the SNPN access operation mode when operating in the SNPN access mode. Also, the UE may not operate in the SNPN access mode of operation if it does not operate in the SNPN access mode. Furthermore, the UE in SNPN access mode may be a UE in SNPN access mode of operation.

SNPN selection may be the procedure of selecting an SNPN. SNPN selection may also be a procedure for the UE to select a SNPN. SNPN selection may also be a procedure performed when a UE connects to a SNPN. SNPN selection may be referred to as an SNPN selection process or an SNPN selection procedure.

SNPN selection may also be the process of selecting an SNPN. SNPN selection may also be the process by which the UE selects a SNPN. SNPN selection may also be a process performed when a UE connects to a SNPN.

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

An equivalent SNPN (equivalent PLMN) may be a SNPN that is treated as if it were the same SNPN as any SNPN. For example, an equivalent SNPN may be one or more SNPNs treated the same as a registered SNPN.

Additionally, an equivalent SNPN may refer to a PLMN that is treated as if it were the same SNPN as any SNPN. For example, an equivalent SNPN may be one or more PLMNs treated the same as a registered SNPN.

Furthermore, equivalent SNPNs may be one or more SNPNs or PLMNs identified by the same PLMN ID as any SNPN. For example, an equivalent SNPN may be one or more SNPNs or PLMNs identified by the same PLMN ID as the registered SNPN. Further, the equivalent SNPN may be the PLMN identified by the same PLMN ID as the registered SNPN, and the equivalent PLMN of said PLMN.

Default UE credentials are information that the UE has before the actual onboarding procedure. The default UE credentials may be information used to uniquely identify the UE. Additionally, the default UE credentials may be information used to prove the security of the UE.

A Default Credential Server (DCS) is a server that can authenticate a UE using default UE credentials. It may be a default certificate server, a server capable of providing authentication of UEs using default UE certificates to other devices or entities.

NPN credentials are information that the UE uses for authentication to access the NPN. The NPN certificate may be a 3GPP certificate or a non-3GPP certificate.

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

Here, the onboarding network may be realized by PLMN. Additionally, the onboarding network may be implemented by SNPN.

A Provisioning Server is a server that provides subscription data to authenticated UEs. A Provisioning Server may be a server that provides subscription data and other configuration information to authorized UEs.

Additionally, the provisioning server may be a server present in the onboarding network. Additionally, the provisioning server may be a server residing in the PLMN. Additionally, the provisioning server may be a server residing in the SNPN. Additionally, the provisioning server may be a server residing in the core network. Additionally, the provisioning server may be a server that resides in an external DN.

A Subscription Owner (SO) stores subscription data and/or other configuration information and, as a result of the UE onboarding procedure, sends the subscription data and/or other configuration information via the PS domain. , is an entity that provides to the UE. In other words, the subscription owner is the entity that stores the subscription data and/or other configuration information, and is the entity that provides the subscription data and/or other configuration information to the UE in the UE onboarding procedure. you can

UE onboarding is the provision of information to the UE and entities within the network necessary for the UE to gain access and connectivity to an approved NPN.

In other words, UE onboarding may be the provision of information to the UE and entities internal to the network. Here, the information may be information necessary for the UE to access the NPN and establish connectivity. Further, access or connectivity to the NPN may be authorized. Further, the information may be SNPN information.

Further in other words, when the UE attempts to access or establish connectivity with the NPN, the UE may perform UE onboarding to obtain the information necessary to access or establish connectivity with the NPN. . Furthermore, the UE may perform procedures for accessing the NPN and establishing connectivity after performing UE onboarding.

Note that UE onboarding may also be referred to as a UE onboarding procedure. Furthermore, UE onboarding may be referred to as an onboarding service. Furthermore, UE onboarding may be referred to as onboarding.

In other words, when we refer to a UE onboarding procedure, we may mean UE onboarding. Furthermore, when referring to an onboarding service, it may mean UE onboarding. Furthermore, the expression onboarding may mean UE onboarding.

The SNPN information is information necessary for the UE to access the SNPN and establish connectivity. The SNPN information may be information used by the UE to perform procedures for establishing access and connectivity to the SNPN. Additionally, the SNPN information may be subscription data and/or other configuration information. Additionally, the SNPN information may be an NPN certificate. Furthermore, SNPN information may be referred to as NPN information.

Note that the UE may acquire SNPN information from the network during UE onboarding. More specifically, the UE may obtain SNPN information from the provisioning server or subscription owner at UE onboarding.

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

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

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

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

Further, the UE may release the first list based on completion of the SNPN information provision procedure. In other words, the UE may release the first list based on completion of obtaining SNPN information.

More specifically, if the UE retains the first list, it may release the first list upon completion of the SNPN information provision procedure. In other words, if the UE retains the first list, the UE may release the first list based on completion of obtaining SNPN information.

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

Here, the SNPN information provision procedure may include a SNPN information provision procedure via the user plane and a SNPN information provision procedure via the control plane.

A procedure for providing SNPN information via the user plane is a procedure for the network to provide SNPN information to the UE via the user plane. In other words, the procedure for providing SNPN information via the user plane is the procedure for the UE to obtain SNPN information from the network via the user plane.

Specifically, the procedure for providing SNPN information via the user plane is a procedure for providing SNPN information from the network to the UE using the PDU session after establishing a PDU session between the UE and the network. .

Here, when using the SNPN information provision procedure via the user plane, the network establishes a PDU session with the UE, and transmits the SNPN information to the UE on the PDU session, so that the UE may provide SNPN information to In other words, when using the SNPN information provision procedure via the user plane, the UE establishes a PDU session with the network, receives SNPN information from the network on the PDU session, and the UE SNPN information may be obtained at

Note that the PDU session used to provide SNPN information may be the PDU session used to provide SNPN information. In other words, a PDU session used to provide SNPN information may be a PDU session for providing SNPN information.

The procedure for providing SNPN information via the control plane is a procedure for the network to provide SNPN information to the UE via the control plane. In other words, the procedure for providing SNPN information via the control plane is the procedure for the UE to obtain SNPN information from the network via the control plane.

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.

Here, when using the procedure for providing SNPN information via the control plane, the SNPN information may be provided to the UE by including the SNPN information in a URSP (UE Route Selection Policy) and transmitting it to the UE. Furthermore, when using the SNPN information provision procedure via the control plane, the SNPN information is included in PCO (Protocol Configuration Options) or ePCO (Extended Protocol Configuration Options) and sent to the UE, so that the SNPN information to the UE may be provided.

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

Note that the URSP may be an information element included in a MANAGE UE POLICY COMMAND message. Furthermore, the PCO may be an information element included in an SM message (Session Management message). Furthermore, the ePCO may be an information element included in an SM message (Session Management message).

Furthermore, the UE policy management command message may be a control message sent and received between the PCF and the UE. Furthermore, SM messages may be control messages sent and received between the UE and the SMF. Furthermore, the SM message includes a PDU SESSION ESTABLISHMENT ACCEPT message, a PDU SESSION MODIFICATION COMMAND message, a PDU SESSION RELEASE COMMAND message, etc. good too.

The first list is a list containing information identifying one or more networks for which the onboarding service is unavailable. The first list may be a list containing information identifying one or more networks. In other words, the first list may be a set of information identifying one or more networks.

Here, the network identified by the information identifying the network may be a network for which the onboarding service is disabled. Further, the network identified by the network identifying information may be a network that does not support onboarding services. Furthermore, the network identified by the information identifying the network may be PLMN (Public Land Mobile Network) or SNPN (Stand-alone Non-Public Network).

Furthermore, the information identifying the network may be information identifying the PLMN or information identifying the SNPN. In other words, the information identifying the network may be the PLMN ID and/or the SNPN ID. Further, the network identifying information may be PLMN identity and/or SNPN identity.

Additionally, the first list may be managed until the SNPN information is provided to the UE. In other words, the first list may be released based on providing SNPN information to the UE. Additionally, the first list may be released upon performance of the non-registration procedure.

Further, the first list may be released upon power off and/or removal of the SIM. Additionally, the first list may be released based on the expiration of the timer.

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

The first identification information is information indicating only the onboarding service. Further, the first identification information may be information indicating a request for onboarding services only. Furthermore, the first identification information may be information indicating a request for registration that can only use the onboarding service. Note that the first identification information may be realized by the request type for which the onboarding service is set.

Furthermore, the first identification information may be information indicating whether or not the UE supports registration that allows only onboarding services to be used. The first identification information may be information indicating that the UE supports registration that allows only the onboarding service to be used, or information that indicates that the UE does not support registration that allows only the onboarding service to be used. may be Further, the first identification information may be implemented by a bit indicating whether the UE supports registrations that are only available for onboarding services. Here, the bit indicating whether or not the UE supports registration that can only use the onboarding service is a bit that constitutes a 5GMM capability information element that indicates the UE's capability in 5G. may

Additionally, the first identity may be a default UE certificate. Furthermore, the first identification information may be information identifying the UE. Further, the first identification information may be information identifying a default certificate server. Furthermore, the first identification information may be information that identifies a network to be connected.

Further, the first identification information may be information selected and determined based on UE configuration and/or UE state and/or user policy and/or application requirements.

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

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

Further, the second identification information may be information selected and determined based on UE configuration and/or UE state and/or user policy and/or application requirements.

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

Further, the third identification information may be information selected and determined based on UE configuration and/or UE state and/or user policy and/or application requirements.

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

Furthermore, the fourth identification information may be information selected and determined based on UE configuration and/or UE state and/or user policy and/or application requirements.

The fifth identification information is information indicating the type of SNPN information provision procedure requested by the UE. The fifth identification information may be information indicating that the UE requests acquisition of SNPN information via the user plane (UP), or information indicating that the UE requests acquisition of SNPN information via the control plane (CP). It may be information indicating a request. Furthermore, the fifth identification information may be implemented by a bit indicating the type of SNPN information provision procedure requested by the UE. Here, the bit indicating the type of SNPN information provision procedure requested by the UE may be a bit constituting a 5GS update type information element.

Further, the fifth identification information may be information selected and determined based on UE configuration and/or UE state and/or user policy and/or application requirements.

The sixth identification information is information indicating Follow-on request. Here, the sixth identification information may be information indicating Follow-on request pending. Conversely, the sixth identification information may be information indicating No follow-on request pending.

Further, the sixth identification information may be information indicating whether NAS signaling needs to be maintained after completion of this procedure. Here, the sixth identification information may be information indicating that NAS signaling needs to be maintained after completion of this procedure. Conversely, the sixth identification information may be information indicating that there is no need to maintain NAS signaling after completing this procedure.

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

Further, the sixth identification information may be information selected and determined based on UE configuration and/or UE state and/or user policy and/or application requirements.

The seventh identity may be the 5GS mobile identity IE. Also, the seventh identification information may be information including one or more eighth identification information.

Also, during the registration procedure, the UE may deal with the seventh identity. Also, the seventh identification information may be information included in the registration request message and/or the registration acceptance message and/or the registration rejection message.

The eighth identity information may be information included in the 5GS mobile identity IE. In other words, the eighth identification information may be information included in the seventh identification information. Also, one or more eighth identification information may be included in the seventh identification information.

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

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

Also, the ninth identification information may be information included in the registration request message. Also, the ninth identification information may be information used when performing initial registration for onboarding services in SNPN. Also, the ninth identification information may be information indicating to perform initial registration for the onboarding service at the SNPN.

Also, the ninth identification information may be information indicating whether to support initial registration for the onboarding service in the SNPN. The ninth identification information may be information indicating support for initial registration for onboarding services at the SNPN. The ninth identification information may be information indicating that the SNPN does not support initial registration for onboarding services.

Further, the ninth identification information may be information selected and determined based on UE settings and/or UE status and/or user policy and/or application requirements.

The eleventh identification information is information indicating whether or not the network supports registration where only the onboarding service can be used. The eleventh identification information may be information indicating that the network supports registration that allows only onboarding services to be used, or information that indicates that the network does not support registrations that allow only onboarding services to be used. may be Further, the eleventh identification may be implemented by a bit indicating whether the network supports registrations that are only available for onboarding services. Here, the bit indicating whether the network supports registrations that are only available for onboarding services constitutes the 5GS network feature support information element, which indicates the network's capabilities in 5G. It may be a bit that

Furthermore, the eleventh identification information may be information indicating whether or not a registration that allows only the onboarding service is permitted. The eleventh identification information may be information indicating that a registration that can only use the onboarding service is permitted, or information that indicates that a registration that can only use the onboarding service is not permitted. There may be. Further, the eleventh identification information may be implemented by a bit indicating whether or not a registration with only onboarding services is allowed.

Furthermore, the eleventh identification information is identification information received by the network, and/or information associated with the NSI, and/or network capability information, and/or operator policy, and/or network status, and / Or it may be information selected or determined based on user registration information or the like.

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

Furthermore, the twelfth identification information may be information indicating that SNPN information is provided via the user plane. Furthermore, the twelfth identification information may be information indicating that provision of SNPN information via the user plane is supported.

Further, the twelfth identification information may be information indicating that SNPN information is provided via the control plane. Furthermore, the twelfth identification information may be information indicating that provision of SNPN information via the control plane is supported.

Further, the twelfth identification information may be information including the meaning indicated by the thirteenth identification information and the meaning indicated by the fourteenth identification information. Furthermore, the twelfth identification information may be information composed of the thirteenth identification information and the fourteenth identification information.

Further, the twelfth identification information is identification information received by the network, and/or information associated with the NSI, and/or network capability information, and/or operator policy, and/or network status, and / Or it may be information selected or determined based on user registration information or the like.

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

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

Furthermore, the thirteenth identification information is identification information received by the network, and/or information associated with the NSI, and/or network capability information, and/or operator policy, and/or network status, and / Or it may be information selected or determined based on user registration information or the like.

The fourteenth identification information is information indicating whether or not the network supports provision of SNPN information via the control plane (CP). The fourteenth identification information may be information indicating that the network supports provision of SNPN information via the control plane, or information indicating that the network does not support provision of SNPN information via the control plane. may be Furthermore, the fourteenth identification information may be implemented by a bit indicating whether the network supports providing SNPN information via the control plane. Here, the bit indicating whether the network supports providing SNPN information via the control plane constitutes the 5GS network feature support information element, which indicates the network's capabilities in 5G. It may be a bit that

Furthermore, the fourteenth identification information may be information indicating that SNPN information is provided via the control plane. Furthermore, the fourteenth identification information may be information indicating that provision of SNPN information via the control plane is supported.

Furthermore, the fourteenth identification information is identification information received by the network, and/or information associated with the NSI, and/or network capability information, and/or operator policy, and/or network status, and / Or it may be information selected or determined based on user registration information or the like.

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

Here, the reason value may indicate that the onboarding service is unavailable. In other words, the reason value may indicate that the onboarding service is not allowed. Further, the reason value may indicate that registrations with only onboarding services are not allowed.

Further, the reason value may indicate that the network does not support the onboarding service. The reason value may indicate that the network does not support registrations that are only available for onboarding services.

Further, the reason value may indicate that the request for onboarding services only has been denied. Further, the reason value may indicate that a request for registration with only onboarding services available has been denied.

Furthermore, the twenty-first identification information may be information indicating that the onboarding service is disabled. In other words, the twenty-first identification information may be information indicating that the onboarding service is not permitted. Furthermore, the 21st identification information may be information indicating that a registration that allows only onboarding services is not permitted.

Furthermore, the twenty-first identification information may be information indicating that the network does not support the onboarding service. The twenty-first identification information may be information indicating that the network does not support registrations that are only available for onboarding services.

Furthermore, the twenty-first identification information may be information indicating that the request for the onboarding service only has been denied. Furthermore, the twenty-first identification information may be information indicating that a request for registration that allows only onboarding services has been rejected.

Furthermore, the twenty-first identification information is identification information received by the network, and/or information associated with the NSI, and/or network capability information, and/or operator policy, and/or network status, and / Or it may be information selected or determined based on user registration information or the like.

[3.2. Description of procedures used in each embodiment]
Next, procedures used in each embodiment will be described. The procedures used in each embodiment include a registration procedure. Each procedure will be explained below.

In each embodiment, as shown in FIG. 2, HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are respectively the same device (that is, the same physical device). A case where they are configured as hardware, the same logical hardware, or the same software) will be described as an example. However, the contents described in this embodiment are also applicable when they are configured as different devices (that is, different physical hardware, different logical hardware, or different software). For example, data may be directly transmitted/received between them, data may be transmitted/received via the N26 interface between AMF and MME, or data may be transmitted/received via UE.

[3.2.1. Registration procedure]
First, the registration procedure will be explained using FIG. The registration procedure is the procedure in 5GS. Hereinafter, this procedure refers to the registration procedure. A registration procedure is a procedure for UE-initiated registration to access network_B and/or core network_B and/or DN. As long as the UE is not registered with the network, the UE can execute this procedure at any time, such as when it is powered on. In other words, the UE can start this procedure at any timing as long as it is in the non-registered state (RM-DEREGISTERED state). Also, each device (especially UE and AMF) can transition to the registered state (RM-REGISTERED state) based on the completion of the registration procedure.

Also, the registration procedure may be an initial registration initiated by the UE. Also, the registration procedure may be mobility and periodic registration.

Also, the registration procedure may be a registration procedure for onboarding services at SNPN or PLMN. The registration procedure may also be an initial registration for onboarding services at the SNPN or PLMN.

Further, the registration procedure updates the location registration information of the UE in the network and/or periodically informs the network of the UE status from the UE and/or updates certain parameters of the UE in the network. procedure may be used.

A UE may initiate a registration procedure upon mobility across TAs. In other words, the UE may initiate the registration procedure when moving to a TA different from the TA indicated in the TA list it maintains. Additionally, the UE may initiate this procedure when a running timer expires. Additionally, the UE may initiate a registration procedure when the context of each device needs to be updated due to PDU session disconnection or invalidation. In addition, the UE may initiate a registration procedure when there is a change in capability information and/or preferences regarding the UE's PDU session establishment. Further, the UE may initiate registration procedures periodically. Additionally, the UE may initiate a registration procedure upon completion of the UE configuration update procedure. Note that the UE is not limited to these, and can execute the registration procedure at any timing.

Furthermore, the UE may initiate registration procedures periodically even in the registered state. In other words, the UE may initiate the registration procedure based on timer expiration.

Note that the registration procedure performed based on the mobility of the UE and the registration procedure performed periodically may be expressed as the registration procedure for mobility and registration update. In other words, the registration procedure for mobility and registration update may be a registration procedure performed based on the UE's mobility, or a registration procedure performed periodically. Further, the registration procedure for mobility and registration update may be a registration procedure performed based on the UE's configuration update. Further, the registration procedure for mobility and registration renewal may be a registration procedure performed to establish a communication path for sending and receiving user data. Further, the registration procedure for mobility and registration renewal may be a registration procedure performed on demand from the network. Further, in other words, the registration procedure for mobility and registration renewal may be a registration procedure other than the initial registration procedure. Hereinafter, the registration procedure for mobility and registration renewal may be referred to as this procedure.

Each step of the registration process is described below. Note that the registration procedure described below may be an initial registration procedure or a registration procedure for mobility and registration renewal.

First, the UE initiates the registration procedure by sending a Registration request message to the AMF (S800) (S802) (S804). Specifically, the UE transmits an RRC message including a registration request message to the 5G AN (or gNB) (S800). Note that the registration request message is a NAS message. Also, the RRC message may be a control message sent and received between the UE and the 5G AN (or gNB). Also, NAS messages are processed in the NAS layer, and RRC messages are processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

Here, the UE may include at least one identification information among the first to ninth identification information in the registration request message and/or the RRC message and transmit it. More specifically, the UE can include and transmit one or more identification information among at least the first to ninth identification information in the registration request message and / or the RRC message, but control different from these It may be included in a message, for example, a control message of a layer lower than the RRC layer (eg, MAC layer, RLC layer, PDCP layer) and transmitted. By transmitting these pieces of identification information, the UE may indicate that the UE supports each function or indicate the UE's request. Furthermore, when a plurality of identification information are transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. Information indicating support for each function and information indicating a request to use each function may be transmitted/received as the same identification information, or may be transmitted/received as different identification information.

The UE may include one or more of the identities of the first to ninth identities in the registration request message when requesting the onboarding service. Further, the UE may include one or more of the identities of the first to ninth identities in the registration request message when requesting a registration that can only use the onboarding service. Further, when the UE requests to use the SNPN information provision procedure, the UE may include one or more of the identification information of the first to ninth identification information in the registration request message.

Further, if the UE supports the onboarding service, the UE may include one or more of the identities of the first to ninth identities in the registration request message. Furthermore, if the UE supports the procedure for providing SNPN information, the UE may include one or more identities among the identities of the first to ninth identities in the registration request message.

Furthermore, the UE may include one or more of the identification information of the first to ninth identification information in the registration request message when acquisition of SNPN information is required. Furthermore, the UE may include one or more identities of the first to ninth identities in the registration request message if it is required to perform the onboarding service. Furthermore, the UE may include one or more of the identification information of the first to ninth identification information in the registration request message when execution of the SNPN information provision procedure is required.

Further, the UE may include one or more of the identities of the first to ninth identities in the registration request message if this procedure is a registration procedure for the onboarding service.

Further, the UE may include the first identification information in the registration request message if it supports registration with only onboarding services available. More specifically, if the UE supports the onboarding service, the UE may include in the registration request message first identification information indicating that the UE supports registration that is only available for the onboarding service.

Further, if the UE supports SNPN information provision procedures, the UE may include second identification information in the registration request message indicating the type of SNPN information provision procedures supported by the UE. More specifically, if the UE supports the SNPN information provision procedure via the user plane, the UE sends the second identity indicating that it supports the SNPN information provision procedure via the user plane to the Registration Request message. may be included in Further, if the UE supports the procedure for providing SNPN information via the control plane, the UE includes second identification information in the registration request message indicating that it supports the procedure for providing SNPN information via the control plane. good too.

In addition, the UE may include the third identification information in the registration request message if it supports the procedure of providing SNPN information via user plane. More specifically, if the UE supports the SNPN information provisioning procedure via the user plane, the UE sends a third identity indicating that it supports the SNPN information provisioning procedure via the user plane in the Registration Request message. may be included in

Furthermore, the UE may include the fourth identification information in the registration request message if it supports the provisioning procedure of SNPN information via control plane. More specifically, if the UE supports the SNPN information provision procedure via the control plane, the UE sends the fourth identification information indicating that it supports the SNPN information provision procedure via the control plane to the Registration Request message. may be included in

Furthermore, if the UE supports the SNPN information provision procedure via the control plane, the UE includes in the registration request message a fourth identification indicating that it supports the SNPN information provision procedure using the PCO or ePCO. may Furthermore, if the UE supports the SNPN information provision procedure via the control plane, the UE may include fourth identification information in the registration request message indicating that it supports the SNPN information provision procedure using the URSP. good.

Further, the UE may include the fifth identification information in the registration request message when requesting use of the SNPN information provision procedure. Further, when the UE requests to use the SNPN information provision procedure, the UE may include in the registration request message fifth identification information indicating the type of SNPN information provision procedure requested by the UE. More specifically, if the UE requests use of the SNPN information provision procedure via the user plane, the UE may include in the registration request message a fifth identification indicating the SNPN information provision procedure via the user plane. good. Further, when the UE requests use of the SNPN information provision procedure via the control plane, the UE may include in the registration request message a fifth identification indicating the SNPN information provision procedure via the control plane.

Furthermore, the UE may include the sixth identification information in the registration request message if this procedure is a registration procedure for onboarding services. More specifically, the UE may include a sixth identification in the registration request message indicating "Follow-on request pending" if this procedure is a registration procedure for an onboarding service.

Furthermore, the UE may indicate to the network the content indicated by the identification information included in the registration request message by including one or more identification information among the identification information of the first to ninth identification information in the registration request message. good. Furthermore, the UE requests the content indicated by the identification information included in the registration request message from the network by including one or more identification information among the identification information of the first to ninth identification information in the registration request message. good too.

In addition, the UE determines whether to include one or more identification information among the first to ninth identification information in the registration request message, subscriber information, and/or network status, and/or user registration information, and / Or you may select and determine based on the context etc. which UE hold|maintains.

In addition, the UE transmits a registration request message including an SM message (eg, a PDU session establishment request message), or transmits an SM message (eg, a PDU session establishment request message) together with the registration request message, The PDU session establishment procedure may be initiated during the registration procedure.

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

If the AMF receives the registration request message, it can perform a first condition determination. The first condition determination is for determining whether or not the network (or AMF) accepts the request from the UE. The AMF initiates the procedure of FIG. 6(A) if the first conditional determination is true, whereas the AMF initiates the procedure of FIG. 6(B) if the first conditional determination is false.

The first condition determination is the reception of the registration request message, and/or each identification information included in the registration request message, and/or subscriber information, and/or network capability information, and/or operator policy, and It may be performed based on network conditions, and/or user registration information, and/or context held by the AMF, and/or the like. For example, the first conditional decision may be true if the network grants the UE's request, and the first conditional decision may be false if the network does not grant the UE's request. In addition, if the network to which the UE is registered and/or the device in the network supports the function requested by the UE, the first condition determination is true and does not support the function requested by the UE. , the first conditional decision may be false. Further, the first conditional determination may be true if the transmitted/received identification information is permitted, and the first conditional determination may be false if the transmitted/received identification information is not permitted. Note that the conditions for determining whether the first condition determination is true or false are not limited to the conditions described above.

First, the case where the first condition determination is true will be described. The AMF can first execute the fourth condition determination in the procedure of (A) in FIG. The fourth condition determination is for determining whether or not AMF will transmit/receive an SM message to/from SMF.

Note that the fourth condition determination may be performed based on whether or not the AMF has received the SM message. Also, the fourth condition determination may be performed based on whether the SM message is included in the registration request message. For example, if AMF received an SM message and/or if the registration request message contained an SM message, then the fourth conditional decision may be true, and if AMF did not receive an SM message, and/or if the registration request message did not contain an SM message, the fourth condition determination may be false. Incidentally, the conditions for determining whether the fourth condition determination is true or false need not be limited to the conditions described above.

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

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

The network may include one or more of the identities of the eleventh to fourteenth identities in the registration acceptance message when allowing the onboarding service. In addition, the network may include one or more of the identities of the eleventh to fourteenth identities in the registration accept message when allowing registrations that can only use the onboarding service. Further, the network may include one or more of the identities of the eleventh to fourteenth identities in the registration acceptance message if the network authorizes the use of the SNPN information provision procedure.

Further, the network may include one or more of the identities of the eleventh to fourteenth identities in the registration acceptance message if it supports the onboarding service. Further, the network may include one or more of the identities of the eleventh to fourteenth identities in the registration acceptance message if the network supports the procedure for providing SNPN information.

Further, the network may include one or more of the identities of the eleventh to fourteenth identities in the registration acceptance message if SNPN information can be provided. Further, the network may include one or more of the identities of the eleventh to fourteenth identities in the registration acceptance message if the onboarding service can be performed. Furthermore, the network may include one or more identification information among the identification information of the eleventh to fourteenth identification information in the registration acceptance message if the network is capable of performing the SNPN information provision procedure.

Additionally, the network may include the eleventh identification information in the registration accept message if it supports registrations that are only available for onboarding services. More specifically, if the network supports onboarding services, the network may include in the registration accept message an eleventh identification that indicates that the network supports registrations that are only available for onboarding services.

Further, if the network supports SNPN information provisioning procedures, the network may include in the registration acceptance message a twelfth identification indicating the type of SNPN information provisioning procedures supported by the network. More specifically, if the network supports the procedure for providing SNPN information via the user plane, the network shall include a twelfth identity indicating that it supports the procedure for providing SNPN information via the user plane in the Registration Acceptance message. may be included in In addition, if the network supports the procedure for providing SNPN information via the control plane, the network may include in the registration accept message a twelfth identification indicating that it supports the procedure for providing SNPN information via the control plane. good too.

Additionally, the network may include the thirteenth identification information in the registration accept message if it supports the provisioning procedure of SNPN information via the user plane. More specifically, if the network supports the procedure for providing SNPN information via the user plane, the network shall include a thirteenth identity indicating that it supports the procedure for providing SNPN information via the user plane in the registration acceptance message. may be included in

In addition, the network may include the fourteenth identification information in the registration accept message if the network supports provisioning procedures for SNPN information via the control plane. More specifically, if the network supports the procedure for providing SNPN information via the control plane, the network adds the 14th identification information indicating that it supports the procedure for providing SNPN information via the control plane to the registration acceptance message. may be included in

In addition, if the network supports the SNPN information provisioning procedure via the control plane, the network shall include in the registration acceptance message a fourteenth identification information indicating that it supports the SNPN information provisioning procedure using the PCO or ePCO. may In addition, if the network supports the SNPN information provisioning procedure via the control plane, the network may include in the registration accept message a fourteenth identifier indicating support for the SNPN information provisioning procedure using URSP. good.

Furthermore, the network may indicate to the UE the content indicated by the identification information included in the registration acceptance message by including one or more identification information among the identification information of the 11th to 14th identification information in the registration acceptance message. good. Further, the network includes one or more identification information among the identification information of the eleventh to fourteenth identification information in the registration acceptance message, thereby permitting the UE the content indicated by the identification information included in the registration acceptance message. good too.

In addition, the AMF determines which of the 11th to 14th identities is to be included in the registration acceptance message for each of the received identities, and/or subscriber information, and/or network capability information, and/or Alternatively, it may be selected and determined based on operator policy and/or network status and/or user registration information and/or context held by AMF.

Also, the AMF may send a registration accept message including an SM message (eg, a PDU session establishment accept message), or may send an SM message (eg, a PDU session establishment accept message) along with the registration accept message. However, this transmission method may be performed when an SM message (for example, a PDU session establishment request message) is included in the registration request message and the fourth condition determination is true. Also, this transmission method may be performed when an SM message (eg, a PDU session establishment request message) is included with the registration request message and the fourth condition determination is true. By performing such a transmission method, the AMF can indicate in the registration procedure that the procedure for the SM has been accepted.

In addition, AMF receives each 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 It may be indicated that the request of the UE has been accepted by sending a registration acceptance message based on the context held by the AMF.

Further, the AMF may send the registration acceptance message including information indicating that some of the requests of the UE have been rejected, or send information indicating that some of the requests of the UE have been rejected. may indicate why some of the UE's requests were rejected. Further, the UE may know why some of the UE's requests were rejected by receiving information indicating that some of the UE's requests were rejected. The reason for the refusal may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

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

Furthermore, the UE can transmit a registration complete message to the AMF via the 5G AN (gNB) as a response message to the registration accept message (S810). Here, the registration completion message is a NAS message transmitted and received on the N1 interface, but is included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

AMF receives the registration complete message via 5G AN (gNB) (S810). Also, each device completes the procedure of (A) in FIG. 6 based on transmission/reception of the registration acceptance message and/or the registration completion message.

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

Here, the AMF may include at least the 21st identification information in the registration rejection message, or may indicate that the UE request is rejected by sending the 21st identification information. and may indicate the reason why the UE's request was rejected.

The network may include the twenty-first identification information in the registration rejection message if it does not allow the onboarding service. Further, the network may include the twenty-first identification information in the registration rejection message if it does not allow registrations that are only available for onboarding services. Additionally, the network may include the twenty-first identification information in the registration rejection message if it does not authorize the use of the SNPN information provisioning procedure.

Additionally, the network may include the twenty-first identification in the registration rejection message if it does not support the onboarding service. Additionally, the network may include the twenty-first identification information in the registration rejection message if it does not support the SNPN information provisioning procedure.

Additionally, the network may include the twenty-first identification information in the registration rejection message if SNPN information cannot be provided. Additionally, the network may include the twenty-first identification information in the registration rejection message if the onboarding service cannot be performed. Additionally, the network may include the twenty-first identification information in the registration rejection message if the SNPN information provisioning procedure is not viable.

Additionally, the network may include the twenty-first identification in the registration rejection message if the network does not support registration with only onboarding services available. More specifically, if the network does not support registrations that are only available for onboarding services, the network does not support registrations that are only available for onboarding services. may be included in

Further, if the network does not support the onboarding service, the network may include in the registration rejection message a twenty-first identification indicating that it does not support the onboarding service. Further, if the network does not support the SNPN information provision procedure, the network may include in the registration rejection message a twenty-first identification indicating that it does not support the SNPN information provision procedure.

Further, if the network does not support the requested SNPN information provisioning procedure, the network may include in the registration rejection message a twenty-first identification indicating that it does not support the requested SNPN information provisioning procedure. . More specifically, if the network does not support the procedure for providing SNPN information via the user plane, it registers a 21st identity indicating that it does not support the procedure for providing SNPN information via the user plane. MAY be included in the rejection message. In addition, if the network does not support the procedure for providing SNPN information via the control plane, the network shall include the twenty-first identification information in the registration rejection message indicating that it does not support the procedure for providing SNPN information via the control plane. may be included.

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

In addition, the AMF determines whether to include at least the twenty-first identification information in the registration rejection message for each identification information received, and/or subscriber information, and/or network capability information, and/or operator policy, and/or It may be selected and determined based on network conditions and/or user registration information and/or context held by the AMF.

Additionally, the AMF may send a Registration Reject message to indicate that the UE's request via the Registration Request message has been rejected. Further, the AMF may transmit the registration refusal message including information indicating the reason for refusal, or may indicate the reason for refusal by transmitting the reason for refusal. Additionally, the UE may know why the UE's request was rejected by receiving information indicating why the UE's request was rejected. The reason for the refusal may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

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

Incidentally, the procedure of (B) in FIG. 6 may be started when the procedure of (A) in FIG. 6 is canceled.

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

Further, each device may perform processing based on information transmitted and received during the registration procedure upon completion of the registration procedure. For example, if information is sent or received indicating that some of the UE's requests were rejected, it may know why the UE's requests were rejected. Furthermore, each device may perform this procedure again, or may perform the registration procedure for Core Network_B or another cell, based on the reason why the UE's request was rejected.

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

For example, the UE may recognize that the onboarding service has been granted if it receives one or more of the identities of the eleventh through fourteenth identities. Further, if the UE receives one or more of the identities of the eleventh to fourteenth identities, it may recognize that the registration for which only the onboarding service is available is granted. Furthermore, if the UE receives one or more of the identities of the eleventh to fourteenth identities, it may recognize that it is authorized to use the SNPN information provision procedure.

Further, the UE may recognize that the onboarding service is supported if it receives one or more of the identities of the eleventh to fourteenth identities. Further, if the UE receives one or more of the identities of the eleventh to fourteenth identities, it may recognize that the SNPN information provision procedure is supported.

Further, the UE may recognize that the SNPN information of the network can be provided if it receives one or more of the identities of the eleventh to fourteenth identities. Further, the UE may recognize that the onboarding service can be performed if it receives one or more of the identities of the eleventh to fourteenth identities. Further, the UE may recognize that the SNPN information providing procedure can be performed when receiving one or more of the identities of the eleventh to fourteenth identities.

Further, if the UE receives the eleventh identification information, the UE may recognize that registrations that are only available for onboarding services are supported. More specifically, the UE may recognize that the onboarding service is supported if it receives an eleventh identification indicating that the network supports registrations that only allow the onboarding service. .

Further, the UE may recognize that the SNPN information provisioning procedure is supported when receiving the twelfth identification information indicating the type of SNPN information provisioning procedure supported by the network. More specifically, if the UE receives a twelfth identification indicating that the UE supports the SNPN information provisioning procedure via the user plane, the UE supports the SNPN information provisioning procedure via the user plane. may be recognized. Further, if the UE receives the twelfth identification information indicating that it supports the SNPN information provisioning procedure via the control plane, the UE recognizes that the SNPN information provisioning procedure via the control plane is supported. may

Further, if the UE receives the thirteenth identification information, the UE may recognize that the procedure for providing SNPN information via the user plane is supported. More specifically, if the UE receives the thirteenth identification information indicating that it supports the SNPN information provisioning procedure via the user plane, the UE supports the SNPN information provisioning procedure via the user plane. may be recognized.

Further, if the UE receives the fourteenth identification information, the UE may recognize that the procedure for providing SNPN information via the control plane is supported. More specifically, when the UE receives the 14th identification information indicating that the UE supports the SNPN information provision procedure via the control plane, the UE supports the SNPN information provision procedure via the control plane. may be recognized.

Further, when the UE receives the 14th identification information indicating that the SNPN information provision procedure using PCO or ePCO is supported, the UE recognizes that the SNPN information provision procedure via the control plane is supported. or recognize that procedures for providing SNPN information using PCO or ePCO are supported. Furthermore, when the UE receives the 14th identification information indicating that the SNPN information provision procedure using URSP is supported, the UE recognizes that the SNPN information provision procedure via the control plane is supported. or may recognize that procedures for providing SNPN information using URSP are supported.

Further, when the UE receives one or more identification information among the identification information of the 11th to 14th identification information, the UE may recognize the content indicated by the received identification information. Furthermore, when the UE receives one or more identification information among the identification information of the 11th to 14th identification information, the UE recognizes that the content indicated by the identification information included in the registration acceptance message is permitted. good.

Further, if the UE receives one or more of the identities of the 11th to 14th identities, it recognizes that establishment of a PDU session for functions other than the onboarding service is prohibited. You may Furthermore, the UE is configured to prohibit establishment of a PDU session for functions other than the onboarding service when receiving one or more identification information among the identification information of the 11th to 14th identification information. may In other words, when the UE receives one or more identification information among the identification information of the 11th to 14th identification information, the UE sets the PDU session establishment procedure for functions other than the onboarding service not to start. may

Furthermore, if the UE receives one or more identification information among the identification information of the 11th to 14th identification information, it recognizes that the establishment of a PDU session other than for the SNPN information provision procedure is prohibited. may Furthermore, when the UE receives one or more identification information among the identification information of the 11th to 14th identification information, the UE is set to prohibit the establishment of a PDU session other than for the SNPN information provision procedure. good too. In other words, when the UE receives one or more identification information among the identification information of the 11th to 14th identification information, the PDU session establishment procedure for the PDU session other than the SNPN information provision procedure is not started. can be set as Furthermore, when the UE receives one or more identification information among the identification information of the 11th to 14th identification information, it is set so that the PDU session establishment procedure other than for the SNPN information provision procedure is not started. may

Note that the period during which the establishment of a PDU session other than for the SNPN information provision procedure is prohibited may be a period managed by a timer. In other words, the UE may be configured not to be barred from establishing PDU sessions other than for the SNPN information provision procedure based on timer expiration.

Furthermore, the period during which the establishment of PDU sessions other than for the SNPN information provision procedure is prohibited may be until a new registration procedure and/or non-registration procedure is performed. In other words, the UE may be configured such that the establishment of PDU sessions other than for the SNPN information provision procedure is not prohibited based on performing a new registration procedure and/or a non-registration procedure.

Furthermore, the period during which establishment of PDU sessions other than for SNPN information provision procedures is prohibited may be until power is turned off and/or USIM is removed. In other words, the UE may be configured not to be prohibited from establishing PDU sessions other than for SNPN information provision procedures based on power off and/or retrieval of USIM.

Here, the PDU session other than the SNPN information providing procedure may be a normal PDU session. More specifically, the PDU session other than the SNPN information provision procedure may be a PDU session for sending and receiving normal user data.

Furthermore, the PDU session other than for the SNPN information provision procedure may be a PDU session other than for the onboarding service. In addition, the PDU sessions other than for SNPN information provision procedures may be PDU sessions for functions other than onboarding services.

For example, a PDU session other than for SNPN information provisioning procedures may be a PDU session for IMS services. Furthermore, the PDU session other than for the SNPN information provision procedure may be a PDU session for emergency services. Furthermore, the PDU session other than for the SNPN information provision procedure may be a PDU session for LADN. Furthermore, the PDU session other than for the SNPN information provision procedure may be a PDU session for CIoT.

In other words, a PDU session other than the SNPN information provisioning procedure may be a PDU session for the IMS service. In addition, the PDU sessions other than those for SNPN information provision procedures may be PDU sessions for emergency services. Furthermore, the PDU session other than for the SNPN information provision procedure may be a PDU session for LADN. Furthermore, the PDU session other than for the SNPN information provision procedure may be a PDU session for CIoT.

Furthermore, the PDU session establishment procedure for non-SNPN information provision procedures may be the PDU session establishment procedure for IMS services. Further, the PDU session establishment procedure for non-SNPN information provision procedures may be a PDU session establishment procedure for emergency services. Further, the PDU session establishment procedure for non-SNPN information provision procedures may be the PDU session establishment procedure for LADN. Further, the PDU session establishment procedure for non-SNPN information provision procedures may be the PDU session establishment procedure for CIoT.

Note that the PDU session other than for the SNPN information provision procedure may be any PDU session other than the PDU session established and used for the SNPN information provision procedure.

Further, the UE may recognize the types of SNPN information provisioning procedures allowed when receiving the twelfth identification information indicating the types of SNPN information provisioning procedures supported by the network. More specifically, if the UE receives a twelfth identification indicating that it supports the SNPN information provision procedure via the user plane, it is authorized to use the SNPN information provision procedure via the user plane. can recognize that. Further, if the UE receives a twelfth identification indicating that it supports the SNPN information provisioning procedure via the control plane, it knows that it is authorized to use the SNPN information provisioning procedure via the control plane. You may

Further, if the UE receives the thirteenth identification information, it may know that it is authorized to use the SNPN information provisioning procedure via the user plane. More specifically, if the UE receives a thirteenth identification indicating that it supports the SNPN information provision procedure via the user plane, it is allowed to use the SNPN information provision procedure via the user plane. can recognize that.

Further, if the UE receives the fourteenth identification information, the UE may recognize that it is authorized to use the SNPN information provisioning procedure via the control plane. More specifically, if the UE receives a 14th identification indicating that it supports the SNPN information provisioning procedure via the control plane, it is authorized to use the SNPN information provisioning procedure via the control plane. can recognize that.

Furthermore, the UE may determine whether to establish a PDU session when receiving one or more of the identities of the eleventh to fourteenth identities. In other words, when the UE receives one or more identification information among the identification information of the 11th to 14th identification information, it determines whether to start the PDU session establishment procedure for establishing the PDU session. may

For example, when the UE receives one or more identification information among the identification information of the 11th to 14th identification information, the UE may start a PDU session establishment procedure for establishing a PDU session, or may be established. Further, the UE may initiate a PDU session establishment procedure to establish a PDU session when receiving the twelfth identification information indicating that the UE supports the SNPN information provision procedure via the user plane; A PDU session may be established. Furthermore, when the UE receives the thirteenth identification information, the UE may initiate a PDU session establishment procedure for establishing a PDU session, or may establish a PDU session.

Conversely, if the UE receives one or more identification information among the identification information of the 11th to 14th identification information, even if it is set not to start the PDU session establishment procedure for establishing the PDU session. may or may not establish a PDU session. Further, when the UE receives the twelfth identification information indicating that it supports the SNPN information provision procedure via the control plane, the UE is set not to start the PDU session establishment procedure for establishing the PDU session. PDU session may not be established. Furthermore, when the UE receives the 14th identification information, the UE may be set not to start the PDU session establishment procedure for establishing the PDU session, or may not establish the PDU session.

Further, the UE may initiate a PDU session establishment procedure if it receives the 14th identification information indicating that it supports the SNPN information provisioning procedure using PCO or ePCO. Conversely, if the UE receives the 14th identification information indicating that it supports the SNPN information provisioning procedure using URSP, it may not initiate the PDU session establishment procedure.

In other words, the UE may initiate the PDU session establishment procedure if the procedure for providing SNPN information using PCO or ePCO is supported and/or allowed. Conversely, the UE may not initiate the PDU session establishment procedure if the procedure for providing SNPN information using URSP is supported and/or allowed.

Furthermore, the UE may initiate a PDU session establishment procedure when implementing the SNPN information provision procedure with PCO or ePCO. Conversely, the UE may not initiate the PDU session establishment procedure when implementing the SNPN information provision procedure using URSP.

Here, the PDU session may be a PDU session used in the SNPN information provision procedure. In other words, the PDU session may be a PDU session for the SNPN information provision procedure. Further, the PDU session may be a PDU session for a SNPN information provision procedure.

Further, the PDU session may be a PDU session used in an onboarding service. In other words, the PDU session may be a PDU session for onboarding services. Further, the PDU session may be a PDU session for onboarding services.

Further, the PDU session establishment procedure may be a PDU session establishment procedure for a SNPN information provision procedure. Further, the PDU session establishment procedure may be a PDU session establishment procedure for a SNPN information providing procedure. Further, the PDU session establishment procedure may be a PDU session establishment procedure for establishing a PDU session for a SNPN information provision procedure. Further, the PDU session establishment procedure may be a PDU session establishment procedure for a SNPN information providing procedure.

Further, the PDU session establishment procedure may be a PDU session establishment procedure for onboarding services. Further, the PDU session establishment procedure may be a PDU session establishment procedure for onboarding services. Further, the PDU session establishment procedure may be a PDU session establishment procedure for establishing a PDU session for onboarding service. Further, the PDU session establishment procedure may be a PDU session establishment procedure for onboarding service.

Further, the UE may start a timer if it receives one or more of the identities of the eleventh to fourteenth identities. Additionally, the UE may initiate a de-registration procedure based on expiration of said timer.

Further, the network may start a timer when transmitting one or more of the identities of the eleventh to fourteenth identities. Additionally, the network may initiate a non-registration procedure upon expiration of said timer.

Here, the timer may be a timer indicating a validity period of a registration that can only use the onboarding service. In other words, the timer may be a timer that indicates a time limit during which the SNPN information provision procedure can be executed.

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

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

Further, each device may be configured such that the NAS signaling connection is not released if this procedure is a registration procedure for onboarding services. More specifically, each device may be configured such that if this procedure is a registration procedure for an onboarding service, the NAS signaling connection will not be released after this procedure is completed.

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

Furthermore, the UE may be set so that the NAS signaling connection is not released when it transmits a registration request message including one or more pieces of identification information among the first to ninth pieces of identification information. More specifically, when the UE transmits a registration request message containing one or more pieces of identification information among the pieces of identification information 1 to 9, the NAS signaling connection is set not to be released after this procedure is completed. good too.

In other words, the UE does not need to release the NAS signaling connection after completing this procedure if one or more of the first to ninth pieces of identification information are included in the registration request message. Conversely, if the UE does not include one or more identification information among the first to ninth identification information in the registration request message, the UE may release the NAS signaling connection after completing this procedure.

Further, the UE may set the NAS signaling connection not to be released when the UE transmits the registration request message including the sixth identification information indicating information indicating Follow-on request pending. More specifically, when the UE transmits a registration request message including the sixth identification information indicating Follow-on request pending, the NAS signaling connection may be set not to be released after this procedure is completed. good.

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

Furthermore, the network may be set so that the NAS signaling connection is not released when a registration request message containing one or more of the first to ninth identification information is received. More specifically, if the network receives a registration request message containing one or more identification information among identification information from 1 to 9, the NAS signaling connection is set not to be released after this procedure is completed. good too.

In other words, the network may not release the NAS signaling connection after completing this procedure if one or more of the first to ninth identification information is included in the registration request message. Conversely, the network may release the NAS signaling connection after completing this procedure if one or more of the first to ninth identities is not included in the registration request message.

Further, the network may configure the NAS signaling connection not to be released upon receipt of a registration request message including a sixth identification indicating information indicating Follow-on request pending. More specifically, if the network receives a registration request message containing the sixth identification information indicating Follow-on request pending, the network may be set so that the NAS signaling connection is not released after completion of this procedure. good.

In other words, the network may not release the NAS signaling connection after completion of this procedure if the sixth identification information indicating information indicating Follow-on request pending was included in the registration request message. Conversely, the network may release the NAS signaling connection after completion of this procedure if the sixth identification was included in the registration request message indicating No follow-on request pending.

Additionally, the UE may recognize that the onboarding service is not allowed if the twenty-first identification is received. Further, the UE may recognize that registration with only onboarding services is not allowed when the twenty-first identification is received. Further, the UE may recognize that it is authorized to use the SNPN information provision procedure when it receives the twenty-first identification information.

Further, the UE may recognize that the onboarding service is not supported if it receives the twenty-first identification. Further, the UE may recognize that the SNPN information provision procedure is not supported when the twenty-first identification is received.

Further, the UE may recognize that it may not be able to provide and/or obtain SNPN information when it receives the twenty-first identification. Further, the UE may recognize that it is not capable of performing the onboarding service when it receives the twenty-first identification. Further, the UE may recognize that it is not able to perform the SNPN information provision procedure when it receives the twenty-first identification information.

Further, if the UE receives the twenty-first identification, the UE may recognize that registration with only onboarding services is not supported. More specifically, if the UE receives the 21st identification information indicating that the network does not support registrations with only onboarding services available, the UE will not support registrations with only onboarding services available. may be recognized.

Further, the UE may recognize that the onboarding service is not supported when receiving the twenty-first identification indicating that the onboarding service is not supported. Further, the UE may recognize that the SNPN information provision procedure is not supported when receiving the twenty-first identification information indicating that the SNPN information provision procedure is not supported.

Further, if the UE receives the 21st identification information indicating that the requested SNPN information provision procedure is not supported, the UE may recognize that the requested SNPN information provision procedure is not supported. good. More specifically, if the UE receives the 21st identification indicating that the UE does not support the SNPN information provisioning procedure via the user plane, the SNPN information provisioning procedure via the user plane is supported. You may recognize that there is no Further, when the UE receives the twenty-first identification information indicating that the SNPN information provision procedure via the control plane is not supported, the UE indicates that the SNPN information provision procedure via the control plane is not supported. may recognize.

Further, when the UE receives the 21st identification information, the UE may recognize the content indicated by the received identification information. Further, when the UE receives the twenty-first identification, the UE may recognize that the content indicated by the received identification is not permitted.

Further, the UE may add the identity of the network to the first list when receiving the twenty-first identity. Further, when the UE receives the twenty-first identification information, the UE may create a first list and add the network identification information to the created first list.

More specifically, the UE may add the identity of the network to the first list if it receives a twenty-first identity indicating that it does not support the SNPN information provisioning procedure. Further, the UE may add the identification of the network to the first list when receiving a twenty-first identification indicating that the UE does not support the onboarding service. Further, the UE may add the identity of the network to the first list if it receives a twenty-first identity indicating that the network does not support registrations that allow only onboarding services.

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

For example, if the procedure is performed in a first network, the network identification information may be information identifying the first network. More specifically, if the procedure is performed in the first PLMN, the network identification information may be information identifying the first PLMN. Further, if the procedure is performed at a first SNPN, the network identification information may be information identifying the first SNPN.

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

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

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

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

Further, the period of time that the first list is maintained may be until the non-registration procedure and/or the second network selection are performed. In other words, the UE may release or delete the first list based on performing the non-registration procedure and/or the second network selection.

Furthermore, the period for which the first list is maintained may be until the power is turned off and/or until the USIM is removed. In other words, the UE may release or delete the first list upon power off and/or retrieval of USIM.

Further, the UE may re-perform the first network selection upon receiving the twenty-first identification. Further, the UE may re-perform the first network selection and select a different network than the one in which it is currently located if the UE receives the twenty-first identification. Further, the UE may initiate a registration procedure with the new selected network after completing the re-performation of the first network selection.

More specifically, the UE may re-perform the first network selection if it receives the twenty-first identification indicating that it does not support the SNPN information provisioning procedure. Further, the UE may re-perform the first network selection when receiving the twenty-first identification indicating that the UE does not support the onboarding service. Further, the UE may re-perform the first network selection if it receives twenty-first identification information indicating that the network does not support registrations that are available for onboarding services only.

Further, the UE may start a timer upon receiving the twenty-first identification. Here, the timer may be a timer that indicates a time limit for managing the first list. In other words, the UE may release or delete the first list based on expiration of the timer.

Further, the timer may be a timer indicating a time limit for prohibiting the registration procedure. In other words, the UE may initiate a registration procedure based on expiration of said timer.

It should be noted that the behavior that is performed when each piece of identification information is received may be performed based on the received identification information. For example, the behavior to be implemented when the eleventh identification is received may be implemented based on the received eleventh identification. Further, the behavior to be implemented upon receipt of the twelfth identification may be performed based on the received twelfth identification. Furthermore, the behavior to be implemented when the thirteenth identification is received may be implemented based on the received thirteenth identification. Further, the behavior to be performed upon receiving the fourteenth identification may be performed based on the received fourteenth identification. Furthermore, the behavior to be implemented when the twenty-first identification information is received may be implemented based on the received twenty-first identification information.

[4. First embodiment]
Next, a first embodiment will be described. Hereinafter, the first embodiment will be referred to as the present embodiment. In this embodiment, the UE performs a registration procedure. Also, the registration procedure in this embodiment may be referred to as a first procedure. Also, this embodiment may be behavior that is implemented during initial registration.

It should be noted that the UE may decide whether to perform the registration procedure based on UE configuration information and/or information received from the network and/or UE mode and/or UE capability information.

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

A first embodiment will be described with reference to FIG. The UE may include the third identification information in the registration request message when performing initial registration for the onboarding service in the first network.

The following behavior may be the behavior the UE handles the 5GS mobile identity IE during initial registration. Also, the following behavior may be the behavior that the UE handles the 5GS mobile identity IE during the registration procedure.

If the UE does not have a valid 5G-GUTI or a SUCI other than the onboarding SUCI, and if the UE has not initiated initial registration for onboarding services at the SNPN, the seventh identification The information may include eighth identification information. The UE may also include the eighth identity in the seventh identity if the UE does not have a valid 5G-GUTI or a SUCI other than the onboarding SUCI. The UE may also include the eighth identity in the seventh identity if the UE has not initiated initial registration for the onboarding service at the SNPN.

Here, the seventh identification information may be information set before starting the registration procedure. Also, the seventh identification information may be information set during the registration procedure.

Here, the eighth identification information may be information set before starting the registration procedure. Also, the eighth identification information may be information set during the registration procedure.

Here, the seventh identification information may determine information including the eighth identification information before starting the registration procedure. Also, the seventh identity may determine the information that includes the eighth identity during the registration process.

Here, the UE may perform SNPN selection when selecting a SNPN for onboarding services. Also, when the UE selects a SNPN for the onboarding service, it may select a SNPN that is allowed to use onboarding. Also, the UE may select an SNPN that is allowed to use onboarding when performing onboarding services in the SNPN.

Here, the UE may perform PLMN selection when selecting a PLMN for onboarding services. Also, when the UE selects a PLMN for the onboarding service, it may select a PLMN that is allowed to use onboarding. Also, the UE may select a PLMN that is permitted to use onboarding when implementing an onboarding service in the PLMN.

Also, the UE may select SNPN as the first network in SNPN selection. Specifically, in SNPN selection, the UE may select SNPN as the first network and send a registration request message to the first network.

Also, the UE may select PLMN as the first network in PLMN selection. Specifically, in PLMN selection, the UE may select PLMN as the first network and send a registration request message to the first network.

The UE may decide whether to select SNPN or PLMN as the first network based on preset information.

The UE may also decide whether to select SNPN or PLMN as the first network based on default UE credentials. The UE may also decide whether to select SNPN or PLMN as the first network if configured with default UE credentials.

The UE may also decide whether to select SNPN or PLMN as the first network based on default PLMN credentials. The UE may also decide whether to select SNPN or PLMN as the first network if it is equipped with a USIM configured with default PLMN credentials.

Note that the UE may determine whether the first network is SNPN or PLMN based on preset information. In other words, the UE may determine whether the first network is SNPN or PLMN if it holds preconfigured information.

Also, the UE may determine that the first network is the SNPN based on preset information indicating the SNPN. In other words, the UE may determine that the first network is SNPN if information indicating SNPN is set in advance.

Also, the UE may determine that the first network is the SNPN based on preset information indicating that the SNPN can be used. In other words, the UE may determine that the first network is SNPN when information indicating that SNPN can be used is set in advance.

Also, the UE may determine that the first network is the SNPN based on preset information indicating that the PLMN cannot be used. In other words, the UE may determine that the first network is the SNPN if the UE is preconfigured with information indicating that the PLMN cannot be used.

Also, the UE may determine that the first network is the PLMN based on preset information indicating the PLMN. In other words, the UE may determine that the first network is the PLMN if the information indicating the PLMN is set in advance.

Also, the UE may determine that the first network is the PLMN based on preset information indicating that the PLMN is available. In other words, the UE may determine that the first network is the PLMN when information indicating that the PLMN can be used is set in advance.

Also, the UE may determine that the first network is the PLMN based on information indicating that the preset SNPN cannot be used. In other words, the UE may determine that the first network is the PLMN if it is preconfigured with information indicating that SNPN cannot be used.

Here, the preset information may be referred to as preset information or preconfigured information.

Here, when performing SNPN selection, the UE may perform registration procedures for onboarding services in SNPN access operation mode. In other words, the UE may send a registration request message to the first network in the SNPN access operation mode when performing SNPN selection.

Here, when the UE performs PLMN selection, it may perform registration procedures for onboarding services in modes other than SNPN access operation mode. In other words, the UE may send a registration request message to the first network in a non-SNPN access mode of operation when PLMN selection is performed.

Here, the UE may operate in SNPN access operation mode when performing SNPN selection. Specifically, when performing SNPN selection, the UE may operate in SNPN access operation mode and perform registration procedures for onboarding services.

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

Here, the registration procedure for the onboarding service may be a registration procedure implemented in the first network. Further, the registration procedure for the onboarding service may be a registration procedure for the UE to register to use only the onboarding service. Further, the registration procedure for the onboarding service may be a registration procedure for registering that the onboarding service is viable. Further, the registration procedure for the onboarding service may be a registration procedure for registering that the procedure for providing SNPN information is viable.

In other words, each device may only be enabled for the onboarding service if the registration procedure for the onboarding service is successfully completed. Further, each device may be capable of performing the onboarding service if the registration procedure for the onboarding service is successfully completed. Further, each device may be capable of performing the SNPN information provisioning procedure if the registration procedure for the onboarding service is successfully completed.

Here, the network for onboarding service may be a network for each device to perform onboarding service. In other words, the network for the onboarding service may be the network for each device to perform the procedure of providing SNPN information. Further, the network for onboarding services may be an onboarding network.

Further, the network for onboarding services may be a network with restricted use of services other than onboarding services. Furthermore, the network for onboarding services may be a network that is only available for onboarding services. The network for onboarding service may be realized by SNPN or by PLMN.

If the execution of the procedures in the first procedure fails, each device may not perform subsequent procedures. In this case, each device may perform processing based on the information included in the control message based on the failure of the execution of the procedure, or may perform processing based on the information included in the control message. , may complete the first procedure.

Specifically, in the registration procedure, if a registration rejection message is sent and received, the UE may perform processing based on the information included in the registration rejection message, or may perform processing based on the information included in the registration rejection message. The first procedure may be completed by performing the processing.

Furthermore, each device may restart the first procedure from the beginning if the execution of the procedures in the first procedure fails. In this case, each device may perform processing based on the information included in the control message based on the failure of the execution of the procedure, or after performing processing based on the information included in the control message, The first procedure may be re-executed from the beginning.

Specifically, in the registration procedure, if a registration rejection message is sent and received, the UE may perform processing based on the information included in the registration rejection message, or may perform processing based on the information included in the registration rejection message. After performing the process, the first network selection may be performed again.

In addition, the UE may be configured not to move to the EPS if the registration procedure for the onboarding service is completed. Further, the UE may set information indicating that the S1 mode is not supported in the S1 mode capability information when the registration procedure for the onboarding service is completed.

In addition, the UE may be configured not to be able to move to the EPS if the registration for which only the onboarding service is available is completed. Furthermore, the UE may set, in the S1 mode capability information, information indicating that the S1 mode is not supported when the registration for using only the onboarding service is completed.

Furthermore, the UE may be configured not to be able to move to the EPS when it registers with the network for the onboarding service. Further, when the UE registers with the network for the onboarding service, the UE may set information indicating that the S1 mode is not supported in the S1 mode capability information.

[5. Modification]
The program that runs on the device according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like to make a computer function so as to implement the functions of the embodiments according to the present invention. Programs or information handled by the programs are temporarily stored in volatile memory such as random access memory (RAM), nonvolatile memory such as flash memory, hard disk drives (HDD), or other storage systems.

A program for realizing the functions of the embodiments related to the present invention may be recorded in a computer-readable recording medium. It may be realized by causing a computer system to read and execute the program recorded on this recording medium. The "computer system" here is a computer system built in the device, and includes hardware such as an operating system and peripheral devices. In addition, "computer-readable recording medium" means a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically retains a program for a short period of time, or any other computer-readable recording medium. Also good.

Also, each functional block, or features, of the apparatus used in the embodiments described above may be implemented or performed in an electrical circuit, such as an integrated circuit or multiple integrated circuits. Electrical circuits designed to perform the functions described herein may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general-purpose processor may be a microprocessor or any conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit, or may be composed of an analog circuit. In addition, if semiconductor technology progresses and an integrated circuit technology that replaces the current integrated circuit appears, one or more aspects of the present invention can use the new integrated circuit based on that technology.

In addition, this invention is not limited to the above-mentioned embodiment. In the embodiments, an example of the device is described, but the present invention is not limited to this, and stationary or non-movable electronic equipment installed indoors and outdoors, such as AV equipment, kitchen equipment , cleaning/washing equipment, air-conditioning equipment, office equipment, vending machines, other household equipment, and other terminal equipment or communication equipment.

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like are included within the scope of the present invention. In addition, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included in the technical scope of the present invention. be Moreover, it is an element described in each said embodiment, and the structure which replaced the element with which the same effect is produced is also included.

1 Mobile communication system
5 PDN_A
6 DN_A
10 UE_A
30 PGW-U
32PGW-C
35 SGW
40 MMEs
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
140AMF
150UDM
160PCF
190 Core Network_B

Claims (1)

User Equipment (UE),
The UE comprises a control unit,
if the UE does not have a valid 5G-GUTI or a SUCI other than the onboarding SUCI,
and if the UE has not initiated initial registration for onboarding services at SNPN,
The UE, wherein the control unit includes PEI in the 5GS mobile identity IE.

Images