WO2022071197A1 - User Equipment (UE) AND COMMUNICATION CONTROL METHOD - Google Patents

Abstract

In a 5G System (5GS), User Equipment (UE) needs to be connected to and registered with a Non-Public Network (NPN), but when the UE does not hold information on the NPN, in a core network, the control process of a control device and the control process of the UE are unclear. In the 5G System (5GS), when the User Equipment (UE) needs to be connected to and registered with the Non-Public Network (NPN), a communication means for providing NPN information to the UE and a control process are provided. Further, in the 5GS, a communication means and a control process are provided for when the provision of the NPN information to the UE fails.

Description

UE (User Equipment) and communication control method

This disclosure relates to UE (User Equipment) and communication control method. This application claims priority based on Japanese Patent Application No. 2020-166657 filed on October 1, 2020, the contents of which are incorporated herein by reference.

The 3GPP (3rd Generation Partnership Project) has begun studying the system architecture of the next generation, that is, the 5GS (5G System), which is the 5th generation (5G) mobile communication system, and will support new procedures and new functions. Discussions are taking place (see Non-Patent Document 1, Non-Patent Document 2, Non-Patent Document 3, and Non-Patent Document 4).

For example, optimization and diversification of communication procedures to support continuous mobile communication services for a wide variety of services, optimization of communication procedures and optimization of system architecture according to diversification, etc. are also required. It is listed as a condition.

In 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered in order to provide a wide variety of services. In 5GS, it is not possible for a specific user to use it for a specific purpose, such as NPN (Non-Public Network), which is defined separately from the public network PLMN (Public Land Mobile Network). The provision of public networks and the functions for realizing private networks are also being considered.

However, when the UE (User Equipment) needs to be connected to the NPN and registered, but the UE does not hold information about the NPN, the processing of the control device of the core network and the processing of the UE are clearly defined. is not.

One aspect of the present invention has been made in view of the above circumstances, and an object thereof is to provide the UE with NPN information when the UE needs to be connected to the NPN and registered in 5GS. It is to provide a communication means for the operation and a method for realizing the processing of the control device of the core network and the processing of the UE. Furthermore, in 5GS, it is also an object to provide a communication means when the provision of NPN information to the UE fails, and a method for realizing the processing of the control device of the core network and the processing of the UE.

A UE (User Equipment; terminal device) according to an aspect of the present invention, in the first network, a registration request message including information indicating only the onboarding service is transmitted to the control device, and the control device sends a registration request message to the control device. The first information is a reason value indicating that the onboarding service is unavailable, and includes a transmission / reception unit and a control unit for receiving a registration refusal message including the information of 1. Based on this, the control unit puts information identifying the first network into the first list and further performs network selection, the first list being used by one or more onboarding services. It is characterized by being a list containing information that identifies a network that is not possible.

A UE (User Equipment; terminal device) communication control method according to an aspect of the present invention, wherein a registration request message including information indicating only an onboarding service is transmitted to a control device in a first network. It has a step of receiving a registration refusal message including the first information from the control device, and the first information is a reason value indicating that the onboarding service is unavailable, and the first information is described above. Based on, the UE puts information identifying the first network into the first list and further performs network selection, the first list being used by one or more onboarding services. It is characterized by being a list containing information that identifies a network that is not possible.

According to one aspect of the invention, in 5GS, a communication means and a core network to enable the UE to connect to and register with the NPN even when the UE does not hold information about the NPN. It is possible to realize the control process of the control device inside and the control process of the UE.

It is a figure explaining the outline of the mobile communication system (EPS / 5GS). It is a figure explaining the detailed structure of the mobile communication system (EPS / 5GS). It is a figure explaining the apparatus configuration of a UE. It is a figure explaining the structure of the access network apparatus (gNB) in 5GS. It is a figure explaining the structure of the core network apparatus (AMF / SMF / UPF) in 5GS. It is a figure explaining the first procedure. It is a figure explaining the registration procedure. It is a figure explaining the PDU session establishment procedure. It is a figure explaining the network-led non-registration procedure. It is a figure explaining the UE-led non-registration procedure.

The 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 the outline of the 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.

In FIG. 1, the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network) _A5, access network _B120, core network _B190, and DN (Data Network) _A6. It is stated that

In the following, these devices / functions may be described by omitting symbols such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc. ..

In addition, Fig. 2 shows the devices / functions of UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5GAN120, AMF140, UPF130, SMF132, PCF160, UDM150, etc. Interfaces that connect devices and functions to each other are described.

In the following, these devices / functions are referred to as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5GAN, AMF, UPF, SMF, PCF, UDM, etc. May be omitted.

The EPS (Evolved Packet System), which is a 4G system, is configured to include an access network_A and a core network_A, but may further include a UE and / or a PDN. Further, the 5GS (5G System), which is a 5G system, is configured to include a UE, an access network_B, and a core network_B, but may further include a DN.

UE is a device that can connect to network services via 3GPP access (3GPP access network, also called 3GPPAN) and / or non-3GPP access (non-3GPP access network, also called non-3GPPAN). 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 capable of connecting to EPS or 5GS. The UE may be equipped with a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). The UE may be expressed as a user device or a terminal device.

In addition, the access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or wireless LAN access network. One or more eNB (evolved Node B) 45 are arranged in E-UTRAN. In the following, eNB45 may be described by omitting a symbol like eNB. If there are a plurality of eNBs, each eNB is connected to each other by, for example, an X2 interface. In addition, one or more access points are arranged in the wireless LAN access network.

In addition, access network_B corresponds to 5G access network (5GAN). 5GAN is composed of NG-RAN (NG Radio Access Network) and / or non-3GPP access network. One or more gNB (NR Node B) 122 is placed in NG-RAN. In the following, gNB122 may be described by omitting a symbol such as eNB. The gNB is a node that provides the NR (New Radio) user plane and the control plane to the UE, and is a node that connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). That is, gNB is a base station device newly designed for 5GS and has a different function from the base station device (eNB) used in EPS, which is a 4G system. When there are a plurality of gNBs, each gNB is connected to each other by, for example, an Xn interface.

In the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. In addition, wireless LAN access network and non-3GPP AN may be referred to as non-3GPP access. In addition, the nodes arranged in the access network_B may be collectively referred to as NG-RAN nodes.

In the following, the device included in the access network_A and / or the access network_B and / or the access network_A, and / or the device included in the access network_B is the access network or the access network device. May be called.

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

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

In the following, the core network_A and / or the core network_B, the device included in the core network_A, and / or the device included in the core network_B are referred to as a core network or a core network device. There is.

The core network (core network_A and / or core network_B) is a mobile network operator (Mobile) that connects the access network (access network_A and / or access network_B) with the PDN and / or DN. It may be an IP mobile communication network operated by Network Operator; MNO), it may be a core network for a mobile communication operator that operates and manages mobile communication system 1, or it may be an MVNO (Mobile Virtual Network Operator). ), MVNE (Mobile Virtual Network Enabler), etc. may be a core network for virtual mobile communication operators and virtual mobile communication service providers.

Also, in Fig. 1, the case where PDN and DN are the same is described, but they may be different. The PDN may be a DN (Data Network) that provides a communication service to the UE. The DN may be configured as a packet data service network or may be configured for each service. Further, the PDN may include a connected communication terminal. Therefore, connecting to the PDN may be connecting to a communication terminal or a server device arranged in the PDN. Further, sending and receiving user data to and from the PDN may be sending and receiving user data to and from a communication terminal or server device arranged in the PDN. Note that PDN may be expressed as DN, and DN may be expressed as PDN.

In the following, 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 in these are referred to as a network or network device. May be called. That is, the fact that the network and / or the network device sends and receives messages and / or executes the procedure means that the access network_A, core network_A, PDN, access network_B, core network_B, and DN It means that at least a part and / or one or more devices contained therein send / receive messages and / or perform procedures.

Also, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the PDN or DN via the access network and core network. That is, the UE can send / receive (communicate) user data with the PDN or DN. When sending and 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 is composed of an IP header and a payload part. The payload section may include devices / functions included in EPS and data transmitted / received by devices / functions included in 5GS. In addition, 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 an IP header is not added, or a UE may add another header such as a Mac header or an Ethernet (registered trademark) frame header. User data to be sent and received may be sent 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 done. Further, at least a 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 appearing below may be, for example, a semiconductor memory or SSD (semiconductor memory unit). It consists of Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each storage unit has not only the information originally set from the shipping stage, but also devices / functions other than its own device / function (for example, UE and / or access network device, and / or core network device, and /. Or, various information transmitted / received to / from PDN and / or DN) can be stored. In addition, each storage unit can store identification information, control information, flags, parameters, and the like included in control messages transmitted and received in various communication procedures described later. Further, each storage unit may store such information for each UE. In addition, each storage unit may store control messages and user data transmitted / received between 5GS and / or the devices / functions included in EPS when an interwork is performed between 5GS and EPS. can. At this time, not only those transmitted / received via the N26 interface but also those transmitted / received without the N26 interface can be stored.

[2.1. UE device configuration]
First, an example of a UE (User Equipment) device configuration 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, the transmission / reception unit_A320, and the storage unit_A340 are connected via a bus. The transmitter / receiver_A320 is connected to the antenna 310.

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

The transmission / reception unit_A320 is a functional unit for wireless communication with the base station device (eNB or gNB) in the access network via the antenna. That is, the UE may send and receive user data and / or control information between the access network device and / or the core network device and / or the PDN and / or the DN using the transmission / reception unit_A320. can.

Explaining in detail with reference to FIG. 2, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transmission / reception unit_A320. In addition, the UE can communicate with the base station device (gNB) in the 5GAN by using the transmission / reception unit_A320. In addition, the UE can send and receive NAS (Non-Access-Stratum) messages to and from the AMF via the N1 interface by using the transmitter / receiver _A320. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN.

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

[2.2. Equipment configuration of gNB]
Next, an example of the device configuration of gNB will be described with reference to FIG. The gNB is composed 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. The transmitter / receiver_B530 is connected to the antenna 510.

Control unit_B500 is a functional unit that controls the operation and function of the entire gNB. The control unit_B500 realizes various processes in gNB by reading and executing various programs stored in the storage unit_B540 as needed.

The network connection part_B520 is a functional part for gNB to communicate with AMF and / or UPF. That is, the gNB can send and receive user data and / or control information to and from the AMF and / or the UPF using the network connection unit_B520.

The transmission / reception unit_B530 is a functional unit for wireless communication with the UE via the antenna 510. That is, the gNB can transmit / receive user data and / or control information to / from the UE by using the transmission / reception unit_B530.

To explain in detail with reference to FIG. 2, gNB in 5GAN can communicate with AMF via the N2 interface by using the network connection part_B520, and UPF via the N3 interface. Can communicate with. Further, the gNB can communicate with the UE by using the transmission / reception unit_B530.

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

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

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

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

More specifically with reference to Figure 2, the AMF within the 5GCN can communicate with the gNB via the N2 interface by using the network connection _A620 and with the UDM via the N8 interface. It can communicate, it can communicate with the SMF via the N11 interface, and it can communicate with the PCF via the N15 interface. In addition, AMF can send and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN. In addition, when 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 AMF.

AMF has a function to exchange control messages with RAN using N2 interface, a function to exchange NAS messages with UE using N1 interface, a function to encrypt and protect the integrity of NAS messages, and registration management. (Registration management; RM) function, connection management (CM) function, reachability management (Reachability management) function, mobility management (Mobility management) function such as UE, SM (Session Management) between UE and SMF N2 for message forwarding function, access authentication (Access Authorization, Access Authorization) function, security anchor function (SEA; Security Anchor Functionality), security context management (SCM; Security Context Management) function, N3IWF (Non-3GPP Interworking Function) It has a function to support an interface, a function to support transmission / reception of NAS signals with a UE via N3IWF, a function to authenticate a UE connected via N3IWF, and the like.

Also, in registration management, the RM status 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 in the network, and the UE context in the AMF does not have valid location information or routing information for the UE, so the AMF cannot reach the UE. Also, in the RM-REGISTERED state, the UE is registered in the network, so the UE can receive services that require registration with the network. The RM state may be expressed as a 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state.

In other words, 5GMM-REGISTERED may be in a state where each device has established a 5GMM context or a state in which a PDU session context has been established. When each device is 5GMM-REGISTERED, UE_A10 may start sending and receiving user data and control messages, or may respond to paging. Further, when each device is 5GMM-REGISTERED, UE_A10 may execute a registration procedure other than the registration procedure for initial registration and / or a service request procedure.

Furthermore, in 5GMM-DEREGISTERED, each device may be in a state where the 5GMM context has not been established, the location information of UE_A10 may not be known to the network, or the network reaches UE_A10. It may be in an impossible state. If each device is 5GMM-DEREGISTERED, UE_A10 may start the registration procedure or establish a 5GMM context by executing the registration procedure.

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

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

The CM state may be expressed as 5GMM mode (5GMM mode). In this case, the non-connected state may be expressed as 5GMM non-connected mode (5GMM-IDLE mode), and the connected state may be expressed as 5GMM connected mode (5GMM-CONNECTED mode). Further, the non-connected state in 3GPP access may be expressed as 5GMM non-connected mode (5GMM-IDLE mode over 3GPP access) in 3GPP access, and the connected state in 3GPP access may be expressed as 5GMM connection mode (5GMM-) in 3GPP access. It may be expressed as CONNECTED mode over 3GPP access). Further, 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. -3GPP access may be expressed as 5GMM connection mode (5GMM-CONNECTED mode over non-3GPP access). The 5GMM non-connection mode may be expressed as an idle mode, and the 5GMM connection mode may be expressed as a connected mode.

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

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

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

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

The network connection part_B720 is a functional part 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 between the AMF and / or the UPF, and / or the PCF, and / or the UDM by using the network connection unit_B720.

More specifically with reference to Figure 2, the SMF within the 5GCN can communicate with the AMF via the N11 interface by using the network connection _A620 and with the UPF via the N4 interface. It can communicate, it can communicate with the PCF via the N7 interface, and it can communicate with the UDM via the N10 interface.

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

SMF has session management functions such as establishment / modification / release of PDU sessions, IP address allocation and management functions for UEs, UPF selection and control functions, and appropriate destinations (destination). ) UPF setting function for routing traffic, function for sending and receiving the SM part of NAS message, function for notifying that downlink data has arrived (Downlink Data Notification), AN via N2 interface via AMF It has a function to provide SM information peculiar to AN (for each AN) sent to, a function to determine the SSC mode (Session and Service Continuity mode) for the session, a roaming function, and the like.

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

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

The network connection unit_B720 is a functional unit for the UPF to connect to the base station device (gNB) in 5GAN and / or the SMF and / or the DN. That is, the UPF uses the network connection _B720 to send and receive user data and / or control information between the base station equipment (gNB) in 5GAN and / or the SMF and / or the DN. Can be done.

More specifically with reference to Figure 2, the UPF within the 5GCN can communicate with the gNB via the N3 interface by using the network connection _A620 and with the SMF via the N4 interface. It can communicate, it can communicate with the DN via the N6 interface, and it can communicate with other UPFs via the N9 interface.

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

The UPF acts as an anchor point for intra-RAT mobility or inter-RAT mobility, as an external PDU session point for interconnecting the DN (ie, as a gateway between the DN and the core network_B). Data forwarding function), packet routing and forwarding function, ULCL (Uplink Classifier) function that supports routing of multiple traffic flows to one DN, and multi-homed PDU session support. It has a branching point function, a QoS (Quality of Service) processing function for userplane, a function for verifying uplink traffic, a function for buffering downlink packets, and a function for triggering downlink data notification (Downlink Data Notification).

The UPF may also be a gateway for IP communication and / or non-IP communication. In addition, the UPF may have a function of transferring IP communication, or may have a function of converting between non-IP communication and IP communication. Further, the multiple gateways may be a gateway connecting the core network_B and a single DN. The UPF may have connectivity with other NFs, or 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 sent and received using a PDN connection or a PDU session. Further, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface and / or the S1-U interface and / or the S5 interface and / or the S8 interface and / or the SGi interface. Further, in the case of 5GS, the user plane may be transmitted and received via the interface between the UE and 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, the control plane is a control message sent and received to control the communication of the UE. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the MME. Further, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Further, in the case of 5GS, the control plane may be transmitted / received using the interface between the UE and NG RAN and the N2 interface. Hereinafter, the control plane may be expressed as a control plane or a C-Plane.

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

[2.6. Explanation of other devices and / or functions]
Next, other devices and / or functions will be described.

PCF has a function to provide policy rules.

In addition, UDM has an authentication information processing function, a user identification processing function, an access authentication function, a registration / mobility management function, a subscriber information management function, and the like.

In addition, PCRF is connected to PGW and / or PDN, and has a function of performing QoS management for data delivery. For example, it manages the QoS of the communication path between UE_A10 and PDN. Further, the PCRF may be a device for creating and / or managing PCC (Policy and Charging Control) rules and / or routing rules used by each device when transmitting and receiving user data.

In addition, HSS is connected to MME and / or SCEF, and has a function to manage subscriber information. HSS subscriber information is referred to, for example, when controlling access to MME. In addition, the HSS may be connected to a location management device different from the MME.

In addition, SCEF is connected to DN and / or PDN, MME and HSS, and has a function as a relay device that transfers user data as a gateway connecting DN and / or PDN and core network_A. .. SCEF may be a gateway for non-IP communication. In addition, SCEF may have the ability to convert between non-IP communication and IP communication. Also, multiple such gateways may be located in the core network_A. The SCEF may be configured outside or inside the core network.

[3. Terminology / identification information used in each embodiment, explanation of procedure]
In each embodiment, at least one term / identification information and procedure to be used will be explained in advance.

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

The network refers to at least a part of the access network_B, core network_B, and DN. Further, one or more devices included in at least a part of the access network_B, the core network_B, and the DN may be referred to as a network or a network device. That is, the fact that the network performs transmission / reception and / or processing of messages may mean that devices (network devices and / or control devices) in the network execute message transmission / reception and / or processing. .. Conversely, the fact that a device in the network performs transmission / reception and / or processing of a message may mean that the network executes transmission / reception and / or processing of a message.

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

Also, the registered PLMN (registered PLMN) is the PLMN in which the UE is registered.

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

The SM (session management) message (also referred to as NAS (Non-Access-Stratum) SM message) may be a NAS message used in the procedure for SM, and is sent and received between UE_A10 and SMF_A230 via AMF_A240. It may be a control message to be performed. In addition, SM messages include PDU session establishment request messages, PDU session establishment acceptance messages, PDU session completion messages, PDU session rejection messages, PDU session change request messages, PDU session change acceptance messages, PDU session change response messages, and the like. You may. The procedure for SM may also include a PDU session establishment procedure.

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

Further, the non5GS service may be a service other than the 5GS service, and may include an EPS service and / or a non-EPS service.

In addition, the single registration mode is a mode in which UE_A10 maintains a common registration state for the 5GMM state and EMM state when N1 mode and S1 mode are available.

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

Also, in order to interwork between 5GS and EPC, UEs that support both 5GC and EPC NAS can operate in single registration mode or dual registration mode.

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

In addition, N1 mode is a mode that allows UE_A10 to access 5GC via a 5G access network. In other words, the N1 mode may be a mode in which messages are sent and received using the N1 interface.

Further, APN (Access Point Name) may be identification information that identifies the core network and / or the external network such as PDN. Furthermore, the APN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 to connect the core network A_90.

The 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. When non-IP is specified, it indicates that communication is performed by a communication method other than IP, not communication using IP.

A PDU (Protocol Data Unit / Packet Data Unit) session can be defined as a relationship between a DN that provides a PDU connectivity service and a UE, but it is established between the UE and an external gateway. It may be connectivity. By establishing a PDU session via the access network_B and the core network_B in 5GS, the UE can send and receive user data to and from the DN using the PDU session. Here, the external gateway may be UPF, SCEF, or the like. The UE can use the PDU session to send and receive user data to and from devices such as application servers located on the DN.

Note that each device (UE and / or access network device and / or core network device) may manage one or more identification information in association with each PDU session. It should be noted that these identification information may include one or more of DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and other information. It may be further included. Further, when a plurality of PDU sessions are established, the identification information associated with the PDU session may have the same content or different contents.

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

The PDU (Protocol Data Unit / Packet 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. Further, Ethernet may indicate that communication using IP is not performed. When Unstructured is specified, it indicates that data is sent / received to the application server etc. in the DN by using the point-to-point (P2P) tunneling technology. As the P2P tunneling technique, for example, a UDP / IP encapsulation technique may be used. The PDU session type may include an IP in addition to the above. IP can be specified if the UE can use both IPv4 and IPv6.

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

A network slice instance (NSI) is composed of an instance (entity) of a network function (NF) and a set of necessary resources, and forms a network slice to be arranged. Here, NF is a processing function in the network and is adopted or defined in 3GPP. NSI is an entity of NS composed of one or more in core network_B. Further, NSI may be configured by a virtual NF (Network Function) generated by using NST (Network Slice Template). Here, NST is a logical expression of one or more NFs associated with a resource request for providing the required communication service and capability. In other words, the NSI may be an aggregate in the core network_B190 composed of a plurality of NFs. In addition, NSI may be a logical network configured to separate user data delivered by services and the like. One or more NFs may be configured in NS. The NF configured in NS may or may not be a device shared with other NS. UE and / or devices in the network are 1 or more based on NSSAI and / or S-NSSAI and / or UE usage type and / or registration information such as 1 or more NSI IDs and / or APN. Can be assigned to NS. The UE usage type is a parameter value included in the UE registration information used to identify the NSI. The UE usage type may be stored in the HSS. AMF may select SMF and UPF based on UE usage type.

In addition, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying NS. S-NSSAI may be composed of only SST (Slice / Service type) or may be composed of both SST and SD (Slice Differentiator). Here, SST is information indicating the operation of NS expected in terms of functions and services. Further, the SD may be information that interpolates the SST when selecting one NSI from a plurality of NSIs represented by the SST. The S-NSSAI may be information peculiar to each PLMN, or may be standard information shared among PLMNs. Further, the network may store one or more S-NSSAI in the registration information of the UE as the default S-NSSAI. If the S-NSSAI is the default S-NSSAI and the UE does not send a valid S-NSSAI to the network in the registration request message, the network may provide the NS related to the UE.

NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI contained in NSSAI is information that assists the access network or core network in selecting NSI. The UE may memorize the NSSAI permitted by the network for each PLMN. Also, NSSAI may be the information used to select AMF.

In addition, SSC (Session and Service Continuity) mode indicates the mode of session service continuity (Session and Service Continuity) supported by the system and / or each device in the 5G system (5GS). More specifically, it may be a mode indicating the type of session service continuation supported by the PDU session established between UE_A10 and UPF. The SSC mode may be a mode indicating the type of session service continuation set for each PDU session. Further, the SSC mode may be composed of three modes, SSC mode 1, SSC mode 2, and SSC mode 3. The SSC mode associated with the PDU session does not have to be changed for the life of the PDU session.

The RRC (Radio Resource Control) connection is a connection established between the UE and the base station device in the access network. More specifically, an RRC connection is a connection established at a Uu reference point between a UE and a base station appliance in an access network. The RRC connection may be configured with a wireless bearer. Further, the RRC connection may be a connection established in 3GPP access. Further, the RRC connection may be a connection established in the RRC layer below the NAS layer. Further, the RRC connection may be a connection established and / or released by sending and receiving an RRC message of the RRC layer. Further, the RRC connection may be a connection that is suspended by sending and receiving RRC messages of the RRC layer.

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

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

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

In addition, support for 5GMM-CONNECTED mode with RRC inactive indication means that the state of the NAS layer can be maintained in the connected state even when a notification indicating that the RRC layer has been disabled is received from the lower layer. It may mean that it is supported. Furthermore, the use of 5GMM-CONNECTED mode with RRC inactive indication means that the state of the NAS layer is maintained in the connected state even when the notification indicating that the RRC layer has been disabled is received from the lower layer. It may mean.

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

The tracking area is a single or multiple range that can be represented by the location information of UE_A10 managed by the core network. The tracking area may be composed of a plurality of cells. Further, the tracking area may be a range in which a control message such as paging is broadcast, or a range in which UE_A10 can move without performing a handover procedure. Further, the tracking area may be a routing area, a location area, or the same as these. Hereinafter, the tracking area may be TA (Tracking Area).

The TA list is a list that includes one or more TAs assigned to UE_A10 by the network. Note that UE_A10 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, the UE_A10 may be a group of information indicating an area in which the TA list can be moved without performing the tracking area update procedure. The TA list may be expressed as a TAI list composed of one or more TAI (Tracking area identity), and hereinafter, the TAI list may refer to the TA list.

LADN (Local Area Data Network) is a DN that a UE can connect to only in a specific location, and provides connectivity to a specific DNN (that is, LADN DNN). The LADN may be a DN that can be connected at a particular location by using a PDU session associated with a particular DNN. Further, the LADN may be a DN that can be connected at a specific location by using a PDU session associated with a specific combination of a specific DNN and a specific S-NSSAI.

LADN information is information related to LADN. The LADN information may be information indicating a specific LADN available to the UE. The LADN information may include LADN DNN and LADN service area information. More specifically, the LADN information may include one or more pieces of information existing for each LADN (hereinafter, referred to as information indicating LADN). Further, the information indicating LADN may include LADN DNN and LADN service area information. Here, the LADN DNN may be information that identifies the LADN, may be information that identifies the DN that is treated as the LADN, or may be a DNN that is used when establishing a PDU session for the LADN. ..

If the LADN information is the conventional LADN information, the LADN information may be the information having the configuration described above. Specifically, when the LADN information is conventional LADN information, the LADN service area may be the conventional LADN service area.

On the contrary, when the LADN information is the extended LADN information, the LADN information may be a part of the above-described configuration extended information. Specifically, if the LADN information is extended LADN information, the LADN service area may be the extended LADN service area. Further, when the LADN information is extended LADN information, the information indicating LADN may further include information indicating the period during which the LADN service area is valid and / or information indicating the particle size of the LADN service area. Further, if the LADN information is extended LADN information, the information indicating LADN may further include S-NSSAI.

The LADN service area is an area where a PDU session can be established for LADN. The LADN service area may be an area where connection to LADN is possible. Further, the LADN service area may be an area indicated by the LADN service area information. Here, the LADN service area information may be information that identifies the LADN service area, and may be provided as a set of tracking areas or as a TAI (Tracking area identity) list.

If the LADN service area is a conventional LADN service area, the LADN service area may be an area composed of tracking areas that belong to the registration area to which the UE is currently connected. In other words, if the LADN service area is a conventional LADN service area, the LADN service area may be an area composed of one or more tracking areas. Conversely, when the LADN service area is an extended LADN service area, the LADN service area may be an area composed of the tracking area, or may be covered by some base stations in the tracking area. Area may be. Further, when the LADN service area is an extended LADN service area, the LADN service area may be an area having a size other than the area configured by the tracking area, or may be an area independent of the tracking area. May be good. In other words, if the LADN service area is an extended LADN service area, the LADN service area may be an area composed of one or more tracking areas, or may be composed of one or more tracking areas. It may be an area different from the area.

Further, when the LADN service area is an area composed of one or more tracking areas, the LADN service area information may be a tracking area ID list composed of one or more tracking area IDs. On the contrary, when the LADN service area is different from the area composed of one or more tracking areas, the LADN service area information may be information that requires assistance from RAN (Radio Access Network). , Information that does not require RAN assistance may be used. Here, the information that requires RAN assistance may be cell information or base station information. Further, the information that requires RAN assistance may be a cell ID or a base station ID. Further, the information that requires RAN assistance is not limited to these, and may be information defined by RAN. Further, the information that does not require RAN assistance may be physical location information or location information that can be acquired by the application. Further, the information that does not require RAN assistance is not limited to these, and may be information that can be acquired other than RAN. Here, RAN may be expressed as an access network. Conversely, the access network may be referred to as RAN.

Expansion of the LADN service area may mean using a LADN service area having a particle size different from that of the conventional LADN service area. Further, the expansion of the LADN service area may mean using the expanded LADN information different from the conventional LADN information. Further, the extension of the LADN service area may mean connecting to the extended LADN, which is different from the conventional LADN.

That is, if each device supports the expansion of the LADN service area, the expanded LADN service area, which is different from the conventional LADN service area, may be applicable in addition to the conventional LADN service area. Further, if each device supports the expansion of the LADN service area, the expanded LADN information different from the conventional LADN information may be available in addition to the conventional LADN information. Further, if each device supports the expansion of the LADN service area, it may be possible to connect to the extended LADN different from the conventional LADN in addition to the conventional LADN.

Conversely, if some of the devices do not support the expansion of the LADN service area, the expanded LADN service area may not be adaptable and only the conventional LADN service area may be adaptable. Further, if some of the devices do not support the expansion of the LADN service area, the expanded LADN information may not be available and only the traditional LADN information may be available. Further, if some of the devices do not support the expansion of the LADN service area, it may not be possible to connect to the expanded LADN, but only to the conventional LADN.

Further, if each device supports the use restriction of the extended LADN service area, the extended LADN service area may not be applicable, and only the conventional LADN service area may be applicable. Further, if each device supports the use restriction of the extended LADN service area, the extended LADN information may not be available and only the conventional LADN information may be available. Further, if each device supports the extended usage restrictions of the LADN service area, it may not be possible to connect to the extended LADN, but only to the conventional LADN.

Conversely, if each device does not support the usage restrictions for the extended LADN service area, the extended LADN service area may also be adaptable. In addition, extended LADN information may also be available if each device does not support the use restrictions of the extended LADN service area. In addition, if each device does not support the extended usage restrictions of the LADN service area, it may be possible to connect to the extended LADN.

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

In addition, Non-Public Network (NPN) is a private network that is used by specific users for specific purposes, such as private use such as companies, not for general use. There are two types of NPN: Stand-alone Non-Public Network (SNPN) and Public network integrated NPN. When NPN is described below, it may mean both SNPN and Public network integrated NPN.

SNPN is a network operated by the NPN operator and not affected by the functional parts provided by PLMN. In other words, the SNPN is an NPN-only network independent of the publicly available PLMN. The SNPN may be a network identified by the SNPN identity (SNPN ID). The SNPN ID may be information that is a combination of the PLMN ID and the Network identifier (NID). The PLMN ID used for the SNPN ID may be information reserved for the private network, and for example, the MCC included in the PLMN ID may be 999. Further, when the UE is registered in the SNPN, the registered SNPN may be referred to as a registered SNPN or RSNPN (registered SNPN).

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

Public network integrated NPN is a network realized by using the functional parts of PLMN. In other words, the Public network integrated NPN is an NPN that is virtually realized within the PLMN. Furthermore, Public network integrated NPN is an NPN that can be created via PLMN. The Public network integrated NPN may be realized by using the function of the network slice. Specifically, the Public network integrated NPN may be a feasible network by using the network slice assigned 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 NPN may be realized by using DN. Specifically, the Public network integrated NPN may be a feasible network by using a DN for the NPN. In this case, the Public network integrated NPN may be identified by the DNN or by the combination of the DNN and the CAG ID.

The CAG (Closed Access Groups) ID is information that identifies a group of subscribers who are permitted to connect to one or more cells associated with the CAG. The CAG may be a group identified by the CAG ID. CAG is a group used to realize Public network integrated NPN in network slices. The CAG may be used to prevent attempts to access network slices assigned for NPNs from UEs that do not allow NPNs. Furthermore, the CAG ID is unique information within the PLMN.

A UE with SNPN enabled (SNPN enable UE) is a UE for which the use of SNPN is set. An SNPN-enabled UE may store at least one piece of information about the SNPN. In other words, the setting information of the UE in which the SNPN is valid may include information indicating that the SNPN can be used. In addition, SNPN-enabled UEs may support SNPN access modes. In other words, a UE with SNPN enabled may operate in SNPN access mode.

SNPN access mode (SNPN access mode) is the mode in which SNPN is selected. The SNPN access mode may be a mode in which the UE is registered in the SNPN. Further, the SNPN access mode may be a mode in which the UE is connected to the SNPN. In other words, a UE operating in SNPN access mode may select only SNPN when selecting a network. More specifically, a UE operating in SNPN access mode may select only SNPN via the Uu interface when selecting a network. In other words, a UE operating in SNPN access mode may select SNPN instead of PLMN when selecting a network. Here, a UE operating in the SNPN access mode may be expressed as a UE in the SNPN access mode. Further, the UE in the SNPN access mode may be a UE in which the SNPN is valid.

Equivalent PLMN may be an SNPN that is treated as if it were the same SNPN as any SNPN. For example, an equal SNPN may be one or more SNPNs that are treated the same as a registered SNPN.

Furthermore, the equal SNPN may be a PLMN that is treated as if it were the same SNPN as any SNPN. For example, the equal SNPN may be one or more PLMNs treated the same as the registered SNPN.

Further, the equal SNPN may be one or more SNPNs identified by the same PLMN ID as any SNPN, or may be a PLMN. For example, the equal SNPN may be one or more SNPNs identified by the same PLMN ID as the registered SNPN, or it may be a PLMN. Further, the equal SNPN may be a PLMN identified by the same PLMN ID as the registered SNPN, and an equal PLMN of the PLMN.

The default UE credentials are the information held by the UE before the actual onboarding procedure. The default UE certificate may be information used to uniquely identify the UE. In addition, the default UE certificate may be information used to prove the security of the UE.

The default certificate server (DefaultCredentialServer: DCS) is a server that can authenticate UE using the default UE certificate. It may be a server that can provide a UE authentication function using a default UE certificate to a default certificate server, another device, or an entity.

NPN credentials are information used by the UE for authentication in order 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 UE with initial registration and / or access for onboarding. In other words, the UE may register and / or access the onboarding network and perform onboarding.

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

The provisioning server is a server that provides subscription data to UEs that have been authenticated and approved. The provisioning server may be a server that provides subscription data and other configuration information to an authenticated UE.

Furthermore, the provisioning server may be a server existing in the onboarding network. Further, the provisioning server may be a server existing in the PLMN. Further, the provisioning server may be a server existing in the SNPN. Further, the provisioning server may be a server existing in the core network. In addition, the provisioning server may be a server that resides on an external DN.

The subscription owner (SO) stores the subscription data and / or other configuration information, and as a result of the UE onboarding procedure, the subscription data and / or other configuration information is transferred via the PS domain. , An entity provided to the UE. In other words, the subscription owner is the entity that stores the subscription data and / or other configuration information and provides the UE with the subscription data and / or other configuration information in the UE onboarding procedure. It's okay.

UE onboarding is to provide the UE and the entity inside the network with the information necessary for the UE to gain access and connectivity to the approved NPN.

In other words, UE onboarding may be to provide information to the UE or an entity inside the network. Here, the information may be information necessary for the UE to access the NPN and establish connectivity. Further, the access and connectivity to the NPN may be approved. Further, the information may be SNPN information.

In other words, if the UE attempts to access or establish connectivity to the NPN, the UE may perform UE onboarding to obtain the information needed to access or establish connectivity to the NPN. .. In addition, the UE may carry out procedures for establishing access to and connectivity to the NPN after performing UE onboarding.

Note that UE onboarding may be referred to as UE onboarding procedure. Further, UE onboarding may be referred to as an onboarding service. Further, UE onboarding may be referred to as onboarding.

In other words, when expressed as UE onboarding procedure, it may mean UE onboarding. Further, when the term “onboarding service” is used, it may mean UE onboarding. Further, when expressed as onboarding, it may mean UE onboarding.

SNPN information is information that the UE needs to access SNPN and establish connectivity. The SNPN information may be information used by the UE to carry out procedures for establishing access and connectivity to the SNPN. Further, the SNPN information may be subscription data and / or other setting information. Further, the SNPN information may be an NPN certificate. Further, the SNPN information may be referred to as NPN information.

The UE may acquire SNPN information from the network in UE onboarding. More specifically, the UE may obtain SNPN information from the provisioning server or subscription owner in UE onboarding.

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

The procedure for providing SNPN information is a procedure for the network to provide SNPN information to the UE. In other words, the procedure for providing SNPN information is a procedure for the UE to acquire SNPN information from the network. Further, the procedure for providing SNPN information may be a procedure for carrying out UE onboarding.

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

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

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

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

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

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

The procedure for providing SNPN information via the user plane is a procedure in which the network provides SNPN information to the UE via the user plane. In other words, the procedure for providing SNPN information via the user plane is a procedure for the UE to acquire 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 procedure for providing SNPN information 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, thereby performing the UE. SNPN information may be provided to. In other words, when using the procedure for providing SNPN information via the user plane, the UE establishes a PDU session with the network and receives the SNPN information from the network on the PDU session. SNPN information may be acquired.

The PDU session used to provide the SNPN information may be the PDU session used to provide the SNPN information. In other words, the 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 in which the network provides SNPN information to the UE via the control plane. In other words, the procedure for providing SNPN information via the control plane is a procedure for the UE to acquire 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 the URSP (UE Route Selection Policy) and transmitting it to the UE. Furthermore, when using the procedure for providing SNPN information via the control plane, the SNPN information is included in the PCO (Protocol Configuration Options) or ePCO (Extended Protocol Configuration Options) and sent to the UE, so that the SNPN information can be sent to the UE. May be provided.

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

Note that the URSP may be an information element included in the UE policy management command message (MANAGE UE POLICY COMMAND message). Further, the PCO may be an information element included in the SM message (Session Management message). Further, the ePCO may be an information element included in the 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. Further, the SM message may be a control message sent and received between the UE and the SMF. Further, the SM message includes a PDU session establishment reception message (PDU SESSION ESTABLISHMENT ACCEPT message), a PDU session change command message (PDU SESSION MODIFICATION COMMAND message), a PDU session release command message (PDU SESSION RELEASE COMMAND message), and the like. May be good.

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

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

Further, the information that identifies the network may be information that identifies PLMN or information that identifies SNPN. In other words, the information that identifies the network may be a PLMN ID and / or an SNPN ID. Further, the information that identifies the network may be PLMN identity and / or SNPN identity.

Furthermore, the first list may be managed until the SNPN information is provided to the UE. In other words, the first list may be freed based on the provision of SNPN information to the UE. In addition, the first list may be released based on the execution of the non-registration procedure.

Furthermore, the first list may be released based on power off and / or SIM retrieval. In addition, 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 as 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 only for the onboarding service. Further, the first identification information may be information indicating a registration request that can be used only by the onboarding service. The first identification information may be realized by the request type for which the onboarding service is set.

Further, the first identification information may be information indicating whether or not the UE supports registration that can be used only by the onboarding service. The first identification information may be information indicating that the UE supports registrations available only for onboarding services, or information indicating that the UE does not support registrations available only for onboarding services. May be. Further, the first identification information may be realized by a bit indicating whether or not the UE supports registration that can be used only by the onboarding service. Here, the bit indicating whether or not the UE supports registration that can be used only by the onboarding service is a bit that constitutes the 5GMM capability information element, which indicates the capability of the UE in 5G. You may.

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

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

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

Further, 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. Further, the second identification information may be information composed of the third identification information and the fourth identification information.

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

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

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

The fourth identification information is information indicating whether or not the UE supports the 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. It may be. Further, the fourth identification information may be realized by a bit indicating whether or not the UE supports acquisition of SNPN information via the control plane. Here, the bit indicating whether or not the UE supports the acquisition of SNPN information via the control plane is a bit constituting the 5GMM capability information element, which indicates the capability of the UE in 5G. You may.

Further, the fourth identification information may be information selected and determined based on the setting of the UE and / or the state of the UE and / or the user policy and / or the request of the application.

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

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

The eleventh identification information is information indicating whether or not the network supports registration that can be used only by the onboarding service. The eleventh identification information may be information indicating that the network supports registrations available only for onboarding services, or information indicating that the network does not support registrations available only for onboarding services. It may be. Further, the eleventh identification information may be realized by a bit indicating whether or not the network supports registration that can be used only by the onboarding service. Here, a bit indicating whether or not the network supports registration that can be used only by the onboarding service constitutes a 5GS network feature support information element, which indicates the ability of the network in 5G. It may be a bit to do.

Further, the eleventh identification information may be information indicating whether or not registration that can be used only by the onboarding service is permitted. The eleventh identification information may be information indicating that registration that can be used only by the onboarding service is permitted, or information indicating that registration that can be used only by the onboarding service is not permitted. There may be. Further, the eleventh identification information may be realized by a bit indicating whether or not registration that can be used only by the onboarding service is permitted.

In addition, the eleventh identification information is the identification information received by the network and / or the information associated with the NSI, and / or the capability information of the network, and / or the operator policy, and / or the state of the network, and / Or the information may be selected and determined based on the user's registration information or the like.

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

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

Further, the twelfth identification information may be information indicating that the SNPN information is provided via the control plane. Further, the twelfth identification information may be information indicating that the 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. Further, the twelfth identification information may be information composed of the thirteenth identification information and the fourteenth identification information.

Further, the twelfth identification information is one or more identification information among the second to fifth identification information received by the network, and / or information associated with NSI, and / or network capability information. And / or the information may be selected and determined based on the operator policy and / or the network status and / or the user's registration information and the like.

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

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

Further, the thirteenth identification information is one or more identification information among the second to fifth identification information received by the network, and / or information associated with NSI, and / or network capability information. And / or the information may be selected and determined based on the operator policy and / or the network status and / or the user's registration information and the like.

The 14th identification information is information indicating whether or not the network supports the provision of SNPN information via the control plane (CP). The fourteenth identification information may be information indicating that the network supports the provision of SNPN information via the control plane, or information indicating that the network does not support the provision of SNPN information via the control plane. It may be. Further, the 14th identification information may be realized by a bit indicating whether or not the network supports the provision of SNPN information via the control plane. Here, a bit indicating whether or not the network supports the provision of SNPN information via the control plane constitutes a 5GS network feature support information element, which indicates the ability of the network in 5G. It may be a bit to do.

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

Further, the 14th identification information is one or more identification information among the 2nd to 5th identification information received by the network, and / or the information associated with the NSI, and / or the capacity information of the network. And / or the information may be selected and determined based on the operator policy and / or the network status and / or the user's registration information and the like.

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

Here, the reason value may indicate that the onboarding service cannot be used. In other words, the reason value may indicate that the onboarding service is not allowed. Further, the reason value may indicate that registrations available only for onboarding services are not allowed.

Furthermore, 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 the onboarding service only has been rejected. Further, the reason value may indicate that the request for registration that can only be used for the onboarding service has been rejected.

Further, the 21st identification information may be information indicating that the onboarding service cannot be used. In other words, the 21st identification information may be information indicating that the onboarding service is not permitted. Further, the 21st identification information may be information indicating that registration that can be used only by the onboarding service is not permitted.

Furthermore, the 21st identification information may be information indicating that the network does not support the onboarding service. The 21st identification information may be information indicating that the network does not support registrations available only for onboarding services.

Further, the 21st identification information may be information indicating that the request for the onboarding service only has been rejected. Further, the 21st identification information may be information indicating that the request for registration that can be used only by the onboarding service has been rejected.

In addition, the 21st identification information is the identification information received by the network and / or the information associated with the NSI, and / or the capability information of the network, and / or the operator policy, and / or the state of the network, and / Or the information may be selected and determined based on the user's registration information or the like.

The 31st identification information is a reason value indicating the reason why the non-registration procedure was started. The 31st identification information may be a 5GSM (5GS Session Management) reason value.

Specifically, the 31st identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has been successful. On the contrary, the 31st identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has failed.

Further, the 31st identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has been completed. More specifically, the thirty-first identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has been completed normally. In other words, the 31st identification information may be information indicating that the UE has acquired the SNPN information, or may be information indicating that the network has provided the SNPN information. ..

On the contrary, the 31st identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has failed. More specifically, the thirty-first identification information may be information indicating that the provision of the SNPN information and / or the acquisition of the SNPN information has not been completed normally. In other words, the 31st identification information may be information indicating that the UE could not obtain the SNPN information, or may be information indicating that the network could not provide the SNPN information. ..

Further, the 31st identification information may be information indicating that the onboarding service has been completed. More specifically, the thirty-first identification information may be information indicating that the onboarding service has been completed normally. On the contrary, the 31st identification information may be information indicating that the onboarding service has not been completed normally.

Further, the 31st identification information may be information indicating that the onboarding service cannot be used. In other words, the thirty-first identification information may be information indicating that the onboarding service is not permitted. Further, the thirty-first identification information may be information indicating that registration that can be used only by the onboarding service is not permitted.

In addition, the 31st identification information is the identification information received by the network and / or the information associated with the NSI, and / or the capability information of the network, and / or the operator policy, and / or the state of the network, and / Or the information may be selected and determined based on the user's registration information or the like.

[3.2. Explanation of procedures used in each embodiment]
Next, the procedure used in each embodiment will be described. The procedure used in each embodiment includes a registration procedure (Registration procedure), a PDU session establishment procedure (PDU session establishment procedure), and a UE setting update procedure (Generic UE configuration update 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 each the same device (that is, the same physical device). The case where it is configured as hardware, the same logical hardware, or the same software) will be described as an example. However, the content described in this embodiment is also applicable when they are configured as different devices (ie, different physical hardware, or different logical hardware, or different software). For example, data may be transmitted / received directly 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 described with reference to FIG. 7. The registration procedure is a procedure in 5GS. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering with the access network_B and / or the core network_B and / or the DN. The UE can execute this procedure at any time, for example, when the power is turned on, as long as it is not registered in the network. In other words, the UE can start this procedure at any time if it is in the unregistered state (RM-DEREGISTERED state). In addition, each device (particularly UE and AMF) can transition to the registration state (RM-REGISTERED state) based on the completion of the registration procedure.

In addition, the registration procedure updates the location registration information of the UE in the network and / or periodically notifies the network of the status of the UE from the UE and / or updates certain parameters about the UE in the network. It may be the procedure of.

The UE may start the registration procedure when it has mobility across TAs. In other words, the UE may initiate the registration process when it moves to a TA that is different from the TA shown in the TA list it holds. In addition, the UE may initiate this procedure when the running timer expires. In addition, the UE may initiate the registration process when the context of each device needs to be updated due to disconnection or invalidation of the PDU session. In addition, the UE may initiate the registration process if there is a change in capability information and / or preferences regarding the establishment of the UE's PDU session. In addition, the UE may initiate the registration process on a regular basis. Further, the UE may start the registration procedure based on the completion of the UE setting update procedure. The UE is not limited to these, and can execute the registration procedure at any timing.

Furthermore, the UE may start the registration procedure on a regular basis even if it is in the registered state. In other words, the UE may initiate the registration process based on the expiration of the timer.

Note that the registration procedure executed based on the mobility of the UE and the registration procedure executed regularly may be expressed as the registration procedure for mobility and registration renewal. In other words, the registration procedure for mobility and renewal of registration may be a registration procedure performed based on the mobility of the UE, or may be a registration procedure performed periodically. Further, the registration procedure for mobility and registration renewal may be a registration procedure executed based on the setting update of the UE. Further, the registration procedure for mobility and registration renewal may be a registration procedure executed to establish a communication path for transmitting and receiving user data. Further, the registration procedure for mobility and registration renewal may be a registration procedure performed based on a request 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.

Next, we will explain each step of the registration procedure. The registration procedure described below may be an initial registration procedure or a registration procedure for mobility and registration renewal.

First, the UE starts the registration procedure by sending a registration request message to AMF (S800) (S802) (S804). Specifically, the UE sends an RRC message including a registration request message to 5GAN (or gNB) (S800). The registration request message is a NAS message. Further, the RRC message may be a control message transmitted / received between the UE and 5GAN (or gNB). In addition, NAS messages are processed in the NAS layer, and RRC messages are processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.

Here, the UE may send one or more identification information out of at least the first to fifth identification information by including it in the registration request message and / or the RRC message. More specifically, the UE may send at least one of the identification information from the first to the fifth identification information by including it in the registration request message and / or the RRC message, but the control is different from these. The message may be included in the control message of a layer lower than the RRC layer (for example, MAC layer, RLC layer, PDCP layer) and transmitted. By transmitting these identification information, the UE may indicate that the UE supports each function, or may indicate a request of the UE. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received to the same identification information or may be transmitted / received as different identification information.

When requesting the onboarding service, the UE may include one or more identification information among the identification information of the first to fifth identification information in the registration request message. Further, when requesting a registration that can be used only by the onboarding service, the UE may include one or more identification information among the identification information of the first to fifth identification information in the registration request message. Further, when requesting the use of the procedure for providing SNPN information, the UE may include one or more identification information among the identification information of the first to fifth identification information in the registration request message.

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

Further, when it is necessary to acquire the SNPN information, the UE may include one or more identification information among the identification information of the first to fifth identification information in the registration request message. Further, the UE may include one or more identification information among the identification information of the first to fifth identification information in the registration request message when it is necessary to execute the onboarding service. Further, the UE may include one or more identification information among the identification information of the first to fifth identification information in the registration request message when it is necessary to execute the procedure for providing the SNPN information.

Furthermore, the UE may include the first identification information in the registration request message if it supports registrations that are only available for onboarding services. More specifically, if the UE supports onboarding services, the registration request message may include first identification information indicating that the UE supports registrations that are only available for onboarding services.

Furthermore, if the UE supports the procedure for providing SNPN information, the registration request message may include a second identification information indicating the type of procedure for providing SNPN information supported by the UE. More specifically, if the UE supports the procedure for providing SNPN information via the user plane, the registration request message indicates that the UE supports the procedure for providing SNPN information via the user plane. May be included in. In addition, if the UE supports the procedure for providing SNPN information via the control plane, the registration request message includes a second identification information indicating that the procedure for providing SNPN information via the control plane is supported. May be good.

Furthermore, if the UE supports the procedure for providing SNPN information via the user plane, the UE may include the third identification information in the registration request message. More specifically, if the UE supports the procedure for providing SNPN information via the user plane, a request message for registering a third identification information indicating that the procedure for providing SNPN information via the user plane is supported. May be included in.

Furthermore, if the UE supports the procedure for providing SNPN information via the control plane, the UE may include the fourth identification information in the registration request message. More specifically, if the UE supports the procedure for providing SNPN information via the control plane, the registration request message indicates that the UE supports the procedure for providing SNPN information via the control plane. May be included in.

In addition, if the UE supports the procedure for providing SNPN information via the control plane, the registration request message includes a fourth identification information indicating that it supports the procedure for providing SNPN information using PCO or ePCO. You may. In addition, if the UE supports the procedure for providing SNPN information via the control plane, the registration request message may include a fourth identification information indicating that it supports the procedure for providing SNPN information using URSP. good.

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

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 fifth identification information in the registration request message. good. Further, the UE requests the network for 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 5 identification information in the registration request message. May be good.

The UE may also include the SM message (eg, PDU session establishment request message) in the registration request message, or send the SM message (eg, PDU session establishment request message) together with the registration request message. The PDU session establishment procedure may be started during the registration procedure.

When 5GAN (or gNB) receives an RRC message including a registration request message, it selects the AMF to which the registration request message is forwarded (S802). Note that 5GAN (or gNB) can select AMF based on the information contained in the registration request message and / or RRC message. 5GAN (or gNB) extracts the registration request message from the received RRC message and forwards the registration request message to the selected AMF (S804).

When the AMF receives the registration request message, it can execute the first condition determination. The first conditional determination is for determining whether or not the network (or AMF) accepts the UE's request. The AMF initiates the procedure (A) in FIG. 7 if the first condition determination is true, whereas the AMF initiates the procedure (B) in FIG. 7 if the first condition determination is false.

The first condition determination is the reception of the registration request message and / or each identification information contained in the registration request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and It may be executed based on / or the state of the network and / or the user's registration information and / or the context held by AMF. For example, if the network allows the UE request, the first condition determination is true, and if the network does not allow the UE request, the first condition determination may be false. Also, if the network to which the UE is registered and / or the devices in the network support the functions required by the UE, the first condition determination is true and does not support the functions required by the UE. In this case, the first condition determination may be false. Further, if the transmitted / received identification information is permitted, the first conditional determination may be true, and if the transmitted / received identification information is not permitted, the first conditional determination may be false. The condition for determining the truth of the first condition determination is not limited to the above-mentioned condition.

First, the case where the first condition discrimination is true will be described. The AMF can first execute the fourth condition determination in the procedure (A) of FIG. The fourth condition determination is for determining whether or not the AMF sends and receives SM messages to and from the SMF.

The fourth condition determination may be executed based on whether or not the AMF has received the SM message. Further, the fourth condition determination may be executed based on whether the registration request message includes the SM message. For example, if the AMF received the SM message and / or if the registration request message contained the SM message, the fourth condition determination may be true and if the AMF did not receive the SM message. And / or if the registration request message does not contain an SM message, the fourth condition determination may be false. The condition for determining the truth of the fourth condition determination is not limited to the above-mentioned condition.

AMF selects SMF if the fourth condition is true and sends and receives SM messages to and from the selected SMF, whereas AMF is false if the fourth condition is false. , Do not execute them (S806). Further, even if the fourth condition determination is true, the AMF may cancel the procedure of FIG. 7 (A) when it receives the SM message indicating rejection from the SMF. At this time, AMF can start the procedure of (B) in FIG.

In S806, when sending and receiving SM messages to and from SMF, AMF can notify SMF of the identification information received in the registration request message. The SMF can acquire the identification information received from the AMF by sending and receiving SM messages to and from the AMF.

The AMF then sends the UE via 5GAN (or gNB) as a response message to the registration request message based on the receipt of the registration request message and / or the completion of sending and receiving the SM message to and from the SMF. Send a Registration accept message (S808). For example, if the fourth condition determination is false, the AMF may send a registration acceptance message based on the receipt of the registration request message from the UE. Further, if the fourth condition determination is true, the AMF may send a registration acceptance message based on the completion of sending and receiving the SM message to and from the SMF. The registration acceptance message is a NAS message sent and received on the N1 interface, but it is included in the RRC message and sent and received between the UE and 5GAN (gNB).

AMF may send the registration acceptance message including at least one of the identification information of at least 11th to 14th. By transmitting these identification information, the AMF may indicate that the network supports each function, or may indicate that the UE request has been accepted. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received to the same identification information or may be transmitted / received as different identification information.

When permitting the onboarding service, the network may include one or more identification information among the identification information of the 11th to 14th identification information in the registration acceptance message. Further, the network may include one or more of the identification information of the 11th to 14th identification information in the registration acceptance message if the registration is allowed to be used only by the onboarding service. Further, if the network permits the use of the procedure for providing SNPN information, the network may include one or more identification information among the identification information of the 11th to 14th identification information in the registration acceptance message.

Furthermore, if the network supports the onboarding service, one or more of the identification information of the 11th to 14th identification information may be included in the registration acceptance message. Further, if the network supports the procedure for providing SNPN information, one or more of the identification information of the 11th to 14th identification information may be included in the registration acceptance message.

Further, if the network can provide the SNPN information, the network may include one or more identification information among the identification information of the 11th to 14th identification information in the registration acceptance message. Further, the network may include one or more identification information among the identification information of the 11th to 14th identification information in the registration acceptance message if the onboarding service can be executed. Further, the network may include one or more identification information among the identification information of the 11th to 14th identification information in the registration acceptance message if the procedure for providing the SNPN information can be executed.

Furthermore, if the network supports registrations that are only available for onboarding services, the eleventh identification information may be included in the registration acceptance message. More specifically, if the network supports onboarding services, the registration acceptance message may include an eleventh identity indicating that the network supports registrations that are only available for onboarding services.

Furthermore, if the network supports the procedure for providing SNPN information, the registration acceptance message may include a twelfth identification information indicating the type of procedure for providing SNPN information supported by the network. More specifically, if the network supports the procedure for providing SNPN information via the user plane, a twelfth identification information registration acceptance message indicating that the network supports the procedure for providing SNPN information via the user plane. May be included in. In addition, if the network supports the procedure for providing SNPN information via the control plane, the registration acceptance message includes a twelfth identification information indicating that the procedure for providing SNPN information via the control plane is supported. May be good.

Furthermore, if the network supports the procedure for providing SNPN information via the user plane, the 13th identification information may be included in the registration acceptance message. More specifically, if the network supports the procedure for providing SNPN information via the user plane, the 13th identification information registration acceptance message indicating that the network supports the procedure for providing SNPN information via the user plane. May be included in.

Furthermore, if the network supports the procedure for providing SNPN information via the control plane, the 14th identification information may be included in the registration acceptance message. More specifically, if the network supports the procedure for providing SNPN information via the control plane, the 14th identification information registration acceptance message indicating that the procedure for providing SNPN information via the control plane is supported. May be included in.

In addition, if the network supports the procedure for providing SNPN information via the control plane, the registration acceptance message includes the 14th identification information indicating that it supports the procedure for providing SNPN information using PCO or ePCO. You may. In addition, if the network supports the procedure for providing SNPN information via the control plane, the registration acceptance message may include the 14th identification information indicating that it supports the procedure for providing SNPN information using URSP. good.

Furthermore, even if the network indicates 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. In addition, the network allows the UE to include the identification information contained in the registration acceptance message by including one or more of the identification information in the 11th to 14th identification information in the registration acceptance message. May be good.

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

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

AMF also 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 shown that the request of the UE has been accepted by sending the registration acceptance message based on the context held by the AMF.

In addition, the AMF may send the registration acceptance message with information indicating that some UE requests have been rejected, or may send information indicating that some UE requests have been rejected. By doing so, it may indicate the reason why some requests of the UE are rejected. In addition, the UE may recognize why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. The reason for rejection may be information indicating that the content indicated by the identification information received by AMF is not permitted.

UE receives a registration acceptance message from AMF via 5GAN (gNB) (S808). By receiving the registration acceptance message, the UE can recognize that the UE's request by the registration request message has been accepted and the contents of various identification information contained in the registration acceptance message.

The UE can also send a registration completion message to AMF via 5GAN (gNB) as a response message to the registration acceptance message (S810). When the UE receives an SM message such as a PDU session establishment acceptance message, the UE may send the registration completion message including the SM message such as the PDU session establishment completion message, or by including the SM message. , May indicate that the procedure for SM has been completed. Here, the registration completion message is a NAS message sent and received on the N1 interface, but is included in the RRC message and sent and received between the UE and 5GAN (gNB).

AMF receives a registration completion message via 5GAN (gNB) (S810). Further, each device completes the procedure of (A) in FIG. 7 based on the transmission / reception of the registration acceptance message and / or the registration completion message.

Next, the case where the first condition discrimination is false will be described. In the procedure (B) of FIG. 7, the AMF sends a registration rejection message to the UE via 5GAN (gNB) as a response message to the registration request message (S812). Here, the registration refusal message is a NAS message sent and received on the N1 interface, but is included in the RRC message and sent and received between the UE and 5GAN (gNB).

Here, the AMF may send the registration refusal message including at least the 21st identification information, or may send the 21st identification information to indicate that the UE request has been rejected. However, it may indicate the reason why the UE request was rejected.

If the network does not allow the onboarding service, the 21st identification information may be included in the registration refusal message. In addition, the network may include the 21st identification information in the registration refusal message if it does not allow registrations that can only be used by the onboarding service. In addition, the network may include the 21st identification information in the registration refusal message if it does not permit the use of the SNPN information provision procedure.

Furthermore, if the network does not support the onboarding service, the 21st identification information may be included in the registration refusal message. In addition, the network may include the 21st identification information in the registration refusal message if it does not support the procedure for providing SNPN information.

Furthermore, the network may include the 21st identification information in the registration refusal message if it is not possible to provide the SNPN information. In addition, the network may include the 21st identification information in the registration refusal message if the onboarding service is not executable. In addition, the network may include the 21st identification information in the registration refusal message if it is not possible to perform the procedure for providing SNPN information.

Furthermore, if the network does not support registrations that are only available for onboarding services, the 21st identification information may be included in the registration refusal message. More specifically, if the network does not support registrations available only for onboarding services, a 21st identification refusal message indicating that the network does not support registrations available only for onboarding services. May be included in.

Furthermore, if the network does not support the onboarding service, the registration refusal message may include the 21st identification information indicating that the onboarding service is not supported. In addition, if the network does not support the procedure for providing SNPN information, it may include a 21st identification information in the registration refusal message indicating that it does not support the procedure for providing SNPN information.

In addition, if the network does not support the requested SNPN information provision procedure, it may include a 21st identification in the registration refusal message indicating that it does not support the requested SNPN information provision procedure. .. More specifically, if the network does not support the procedure for providing SNPN information via the user plane, it registers a 21st identification information indicating that it does not support the procedure for providing SNPN information via the user plane. It 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 registration refusal message will indicate that the network 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 refusal message by including the 21st identification information in the registration refusal message. Further, the network does not have to allow the UE the content indicated by the identification information included in the registration refusal message by including the 21st identification information in the registration refusal message.

In addition, AMF may include at least the 21st identification information in the registration refusal message, 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 the state of the network and / or the user's registration information and / or the context held by AMF.

Furthermore, AMF may indicate that the UE request by the registration request message has been rejected by sending a registration refusal message. In addition, the AMF may send the registration refusal message with information indicating the reason for refusal, or may send the reason for refusal to indicate the reason for refusal. Further, the UE may recognize the reason why the UE's request is rejected by receiving the information indicating the reason why the UE's request is rejected. The reason for rejection may be information indicating that the content indicated by the identification information received by AMF is not permitted.

UE receives a registration refusal message from AMF via 5GAN (gNB) (S812). By receiving the registration refusal 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 contained in the registration refusal message. Further, the UE may recognize that the request of the UE has been rejected if the registration refusal message is not received even after a predetermined period has elapsed after the registration request message is transmitted. Each device completes the procedure (B) in this procedure based on the transmission / reception of the registration refusal message.

Note that the procedure (B) in Fig. 7 may be started when the procedure in (A) in Fig. 7 is canceled. In the procedure (A) of FIG. 7, if the fourth condition determination is true, the AMF may send the registration refusal message including the SM message indicating rejection such as the PDU session establishment refusal message. , The inclusion of an SM message indicating rejection may indicate that the procedure for SM has been rejected. In that case, the UE may further receive an SM message indicating rejection, such as a PDU session establishment refusal message, or may recognize that the procedure for SM has been rejected.

Each device completes the registration procedure based on the completion of the procedure (A) or (B) in Fig. 7. Each device may transition to the state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure (A) in FIG. 7, or the procedure in (B) in FIG. 7 is completed. Based on the above, the UE may be maintained in the state of not being registered in the network (RM_DEREGISTERED state), or the UE may be transitioned to the state of not being registered in the network. Further, 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 the information transmitted / received in the registration procedure based on the completion of the registration procedure. For example, when sending and receiving information indicating that a part of the UE's request has been rejected, the reason why the UE's request has been rejected may be recognized. Further, each device may carry out this procedure again based on the reason why the request of the UE is rejected, or may carry out the registration procedure for the core network_B or another cell.

Furthermore, the UE may store the identification information received with the registration acceptance message and / or the registration refusal message based on the completion of the registration procedure, and may recognize the network decision.

For example, the UE may recognize that the onboarding service is permitted when it receives one or more identification information among the identification information of the 11th to 14th identification information. Further, the UE may recognize that if one or more of the identification information of the 11th to 14th identification information is received, the registration that can be used only by the onboarding service is permitted. Further, the UE may recognize that the use of the SNPN information provision procedure is permitted when one or more of the identification information of the 11th to 14th identification information is received.

Furthermore, the UE may recognize that the onboarding service is supported when it receives one or more of the identification information of the 11th to 14th identification information. Further, the UE may recognize that the procedure for providing SNPN information is supported when one or more of the identification information of the 11th to 14th identification information is received.

Furthermore, the UE may recognize that it is possible to provide the SNPN information of the network when receiving one or more identification information among the identification information of the 11th to 14th identification information. Further, the UE may recognize that the onboarding service can be executed when one or more of the identification information of the 11th to 14th identification information is received. Further, the UE may recognize that when one or more of the identification information of the 11th to 14th identification information is received, the procedure for providing the SNPN information can be executed.

Furthermore, the UE may recognize that if it receives the eleventh identification information, it supports registrations that can only be used by the onboarding service. More specifically, the UE may recognize that the onboarding service is supported if it receives an eleventh identification that indicates that the network supports registrations that are only available for the onboarding service. ..

Furthermore, the UE may recognize that the SNPN information provision procedure is supported when it receives the twelfth identification information indicating the type of SNPN information provision procedure supported by the network. More specifically, if the UE receives a twelfth identification information indicating that it supports the procedure for providing SNPN information via the user plane, the procedure for providing SNPN information via the user plane is supported. May be recognized. Furthermore, the UE recognizes that it supports the procedure for providing SNPN information via the control plane when it receives the twelfth identification information indicating that it supports the procedure for providing SNPN information via the control plane. You may.

Furthermore, when the UE receives the thirteenth identification information, it may recognize that the procedure for providing the SNPN information via the user plane is supported. More specifically, if the UE receives a thirteenth identification that indicates that it supports the procedure for providing SNPN information via the user plane, the procedure for providing SNPN information via the user plane is supported. May be recognized.

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

In addition, the UE recognizes that the procedure for providing SNPN information via the control plane is supported when it receives the 14th identification information indicating that it supports the procedure for providing SNPN information using PCO or ePCO. You may recognize that the procedure for providing SNPN information using PCO or ePCO is supported. In addition, the UE recognizes that the procedure for providing SNPN information via the control plane is supported when it receives the 14th identification information indicating that it supports the procedure for providing SNPN information using URSP. You may recognize that the procedure for providing SNPN information using URSP is 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. Further, even if the UE recognizes that when one or more of the identification information of the 11th to 14th identification information is received, the content indicated by the identification information included in the registration acceptance message is permitted. good.

In addition, the UE recognizes that if one or more of the identification information of the 11th to 14th identification information is received, the establishment of a PDU session for a function other than the onboarding service is prohibited. You may. In addition, the UE is set to prohibit the establishment of a PDU session for functions other than the onboarding service when one or more of the identification information of the 11th to 14th identification information is received. You may. In other words, the UE sets the PDU session establishment procedure for functions other than the onboarding service not to start when one or more of the identification information of the 11th to 14th identification information is received. You may.

Furthermore, the UE recognizes that if one or more of the identification information of the 11th to 14th identification information is received, the establishment of the PDU session other than the procedure for providing the SNPN information is prohibited. You may. Furthermore, the UE is set so that when one or more of the identification information of the 11th to 14th identification information is received, the establishment of the PDU session other than the procedure for providing the SNPN information is prohibited. May be good. In other words, if the UE receives one or more of the identification information of the 11th to 14th identification information, the PDU session establishment procedure for the PDU session other than the procedure for providing the SNPN information is not started. It may be set as follows. Furthermore, the UE is set so that when one or more of the identification information of the 11th to 14th identification information is received, the PDU session establishment procedure for purposes other than the procedure for providing the SNPN information is not started. You may.

The period during which establishment of a PDU session other than for the procedure for providing SNPN information is prohibited may be a period managed by a timer. In other words, the UE may be set so that the establishment of a PDU session other than for the procedure for providing SNPN information is not prohibited based on the expiration of the timer.

Furthermore, the period during which the establishment of a PDU session other than the procedure for providing SNPN information is prohibited may be until a new registration procedure and / or a non-registration procedure is executed. In other words, the UE may be configured not to be prohibited from establishing a PDU session other than for the SNPN information provision procedure based on the execution of a new registration procedure and / or a non-registration procedure.

Furthermore, the period during which the establishment of a PDU session other than for the procedure for providing SNPN information is prohibited may be until the power is turned off and / or until the USIM is taken out. In other words, the UE may be set so that the establishment of a PDU session other than for the procedure for providing SNPN information is not prohibited based on the power off and / or the retrieval of USIM.

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

Furthermore, the PDU session other than for the procedure for providing SNPN information may be a PDU session other than for the onboarding service. Further, the PDU session other than the procedure for providing SNPN information may be a PDU session for a function other than the onboarding service.

For example, the PDU session other than the procedure for providing SNPN information may be a PDU session for the IMS service. Further, the PDU session other than the procedure for providing SNPN information may be a PDU session for emergency service. Further, the PDU session other than the procedure for providing SNPN information may be a PDU session for LADN. Further, the PDU session other than the procedure for providing SNPN information may be a PDU session for CIoT.

In other words, the PDU session other than the procedure for providing SNPN information may be a PDU session for the IMS service. Further, the PDU session other than the procedure for providing SNPN information may be a PDU session for emergency service. Further, the PDU session other than the procedure for providing SNPN information may be a PDU session for LADN. Further, the PDU session other than the procedure for providing SNPN information may be a PDU session for CIoT.

Furthermore, the PDU session establishment procedure for purposes other than the procedure for providing SNPN information may be the PDU session establishment procedure for the IMS service. Further, the PDU session establishment procedure for purposes other than the procedure for providing SNPN information may be a PDU session establishment procedure for emergency services. Further, the PDU session establishment procedure for purposes other than the procedure for providing SNPN information may be the PDU session establishment procedure for LADN. Further, the PDU session establishment procedure for purposes other than the procedure for providing SNPN information may be the PDU session establishment procedure for CIoT.

Not limited to the above, the PDU session other than the SNPN information provision procedure may be a PDU session other than the PDU session established and used for the SNPN information provision procedure.

Furthermore, the UE may recognize the type of permitted SNPN information provision procedure when it receives the twelfth identification information indicating the type of SNPN information provision procedure supported by the network. More specifically, if the UE receives a twelfth identification that indicates that it supports the procedure for providing SNPN information via the user plane, it is authorized to use the procedure for providing SNPN information via the user plane. You may recognize that. In addition, the UE recognizes that if it receives a twelfth identification that indicates that it supports the procedure for providing SNPN information via the control plane, it is authorized to use the procedure for providing SNPN information via the control plane. You may.

Furthermore, when the UE receives the thirteenth identification information, it may recognize that the use of the procedure for providing SNPN information via the user plane is permitted. More specifically, if the UE receives a thirteenth identification that indicates that it supports the procedure for providing SNPN information via the user plane, it is authorized to use the procedure for providing SNPN information via the user plane. You may recognize that.

Furthermore, when the UE receives the 14th identification information, it may recognize that the use of the procedure for providing SNPN information via the control plane is permitted. More specifically, if the UE receives a 14th identification that indicates that it supports the procedure for providing SNPN information via the control plane, it is authorized to use the procedure for providing SNPN information via the control plane. You may recognize that.

Furthermore, the UE may decide whether or not to establish a PDU session when receiving one or more identification information among the identification information of the 11th to 14th identification information. In other words, the UE decides whether to initiate the PDU session establishment procedure to establish a PDU session when it receives one or more of the identification information of the 11th to 14th identification information. You may.

For example, if the UE receives one or more of the identification information of the 11th to 14th identification information, the UE may start the PDU session establishment procedure for establishing the PDU session, or the PDU session. May be established. In addition, the UE may initiate a PDU session establishment procedure to establish a PDU session when it receives a twelfth identification that indicates that it supports the procedure for providing SNPN information via the user plane. A PDU session may be established. Further, when the UE receives the thirteenth identification information, the UE may start the PDU session establishment procedure for establishing the PDU session, or may establish the PDU session.

On the contrary, even if the UE is set not to start the PDU session establishment procedure for establishing the PDU session when one or more of the identification information of the 11th to 14th identification information is received. You do not have to establish a PDU session. In addition, the UE is configured not to initiate the PDU session establishment procedure to establish a PDU session when it receives a twelfth identification that indicates that it supports the procedure for providing SNPN information via the control plane. It may or may not have to establish a PDU session. Further, 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.

Furthermore, the UE may start the PDU session establishment procedure when it receives the 14th identification information indicating that it supports the procedure for providing SNPN information using PCO or ePCO. Conversely, the UE does not have to start the PDU session establishment procedure when it receives the 14th identification information indicating that it supports the procedure for providing SNPN information using URSP.

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 permitted. Conversely, the UE may not initiate the PDU session establishment procedure if the procedure for providing SNPN information using URSP is supported and / or permitted.

Furthermore, the UE may start the PDU session establishment procedure when carrying out the procedure for providing SNPN information using PCO or ePCO. On the contrary, when the UE performs the procedure for providing SNPN information using URSP, it is not necessary to start the procedure for establishing a PDU session.

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

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

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

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

Furthermore, the UE may start the timer when it receives one or more identification information among the identification information of the 11th to 14th identification information. Further, the UE may start the non-registration procedure based on the expiration of the timer.

Furthermore, the network may start a timer when one or more of the identification information of the 11th to 14th identification information is transmitted. In addition, the network may initiate the non-registration procedure based on the expiration of the timer.

Here, the timer may be a timer indicating an expiration date for which registration can be used only for the onboarding service. In other words, the timer may be a timer indicating a deadline for executing the procedure for providing SNPN information.

Furthermore, the UE may recognize that the onboarding service is not permitted when it receives the 21st identification information. In addition, the UE may recognize that upon receiving the 21st identification, registrations that are only available to the onboarding service are not allowed. In addition, the UE may recognize that it has been authorized to use the SNPN information provision procedure when it receives the 21st identification information.

Furthermore, the UE may recognize that the onboarding service is not supported when it receives the 21st identification information. In addition, the UE may recognize that the procedure for providing SNPN information is not supported when it receives the 21st identification information.

Furthermore, the UE may recognize that when the 21st identification information is received, it is not possible to provide and / or acquire the SNPN information. Further, the UE may recognize that the onboarding service cannot be executed when the 21st identification information is received. Further, the UE may recognize that the procedure for providing the SNPN information cannot be executed when the 21st identification information is received.

Furthermore, when the UE receives the 21st identification information, it may recognize that the registration that can be used only by the onboarding service is not supported. More specifically, if the UE receives a 21st identification that indicates that the network does not support registrations that are only available for onboarding services, then registrations that are only available for onboarding services are not supported. May be recognized.

Furthermore, the UE may recognize that the onboarding service is not supported when it receives the 21st identification information indicating that the onboarding service is not supported. Further, the UE may recognize that the procedure for providing SNPN information is not supported when it receives the 21st identification information indicating that the procedure for providing SNPN information is not supported.

In addition, if the UE receives a 21st identification that indicates that it does not support the requested SNPN information provision procedure, it may recognize that the requested SNPN information provision procedure is not supported. good. More specifically, if the UE receives a 21st identification that indicates that it does not support the procedure for providing SNPN information via the user plane, the procedure for providing SNPN information via the user plane is supported. You may recognize that it is not. Furthermore, if the UE receives the 21st identification information indicating that it does not support the procedure for providing SNPN information via the control plane, it means that the procedure for providing SNPN information via the control plane is not supported. You may recognize it.

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

Furthermore, when the UE receives the 21st identification information, the UE may add the network identification information to the 1st list. Further, when the UE receives the 21st identification information, it may create a first list and add the network identification information to the created first list.

More specifically, the UE may add the network identification information to the first list when it receives the 21st identification information indicating that it does not support the procedure for providing SNPN information. In addition, the UE may add the network identification to the first list if it receives a 21st identification that indicates it does not support the onboarding service. In addition, the UE may add the network identification to the first list if it receives a 21st identification that indicates that the network does not support registrations available only for onboarding services.

Here, the network identification information may be information that identifies the network in which the UE is currently located. More specifically, when the UE is located on the PLMN, the network identification information may be information that identifies the PLMN on which the UE is currently located. Conversely, when the UE is located in the SNPN, the network identification information may be information that identifies the SNPN in which the UE is currently located.

For example, when this procedure is executed in the first network, the identification information of the network may be the information for identifying the first network. More specifically, when this procedure is executed in the first PLMN, the network identification information may be information that identifies the first PLMN. Further, when this procedure is executed in the first SNPN, the network identification information may be information that identifies the first SNPN.

The period in which the first list is maintained may be the period managed by the timer. In other words, the UE may release or delete the first list based on the 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.

Furthermore, the period during 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 acquisition of the SNPN information.

Furthermore, the period during which the first list is maintained may be until the non-registration procedure and / or the second network selection is executed. In other words, the UE may release or delete the first list based on the unregistration procedure and / or the execution of the second network selection.

Furthermore, the period during which the first list is maintained may be until the power is turned off and / or until the USIM is taken out. In other words, the UE may release or delete the first list based on power off and / or USIM retrieval.

Furthermore, the UE may re-execute the first network selection when it receives the 21st identification information. Further, when the UE receives the 21st identification information, it may re-execute the first network selection and select a network different from the network in which it is currently located. In addition, the UE may initiate the registration process on the new network of choice after the re-execution of the first network selection is complete.

More specifically, the UE may re-execute the first network selection when it receives the 21st identification information indicating that it does not support the procedure for providing SNPN information. Further, the UE may re-execute the first network selection if it receives the 21st identification information indicating that it does not support the onboarding service. In addition, the UE may re-execute the first network selection if it receives a 21st identification that indicates that the network does not support registrations available only for onboarding services.

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

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

Note that the behavior performed when each identification information is received may be performed based on the received identification information. For example, the behavior performed when the eleventh identification information is received may be performed based on the received eleventh identification information. Further, the behavior performed when the twelfth identification information is received may be performed based on the received twelfth identification information. Further, the behavior performed when the thirteenth identification information is received may be performed based on the received thirteenth identification information. Further, the behavior performed when the 14th identification information is received may be performed based on the received 14th identification information. Further, the behavior performed when the 21st identification information is received may be performed based on the received 21st identification information.

[3.2.2. PDU session establishment procedure]
Next, an outline of the PDU session establishment procedure for establishing a PDU session for a DN will be described with reference to FIG. The PDU session establishment procedure is a procedure in 5GS. Hereinafter, this procedure refers to the procedure for establishing a PDU session. The PDU session establishment procedure is a procedure for each device to establish a PDU session. Each device can start the PDU session establishment procedure at any time when the registration procedure is completed and the registration state is reached. In addition, each device may be able to execute the PDU session establishment procedure in the registration procedure. In addition, each device may establish a PDU session based on the completion of the PDU session establishment procedure.

The PDU session establishment procedure may be a procedure initiated by the UE or a procedure requested and initiated by the UE. In other words, the PDU session establishment procedure may be a UE request PDU session establishment procedure. Each device can establish a plurality of PDU sessions by executing the PDU session establishment procedure a plurality of times.

Here, if the PDU session establishment procedure is a PDU session establishment procedure for establishing a PDU session for LADN, each device establishes a PDU session for LADN based on the completion of the PDU session establishment procedure. You may. In other words, if the PDU session establishment procedure is a PDU session establishment procedure using LADN DNN, each device may establish a PDU session for LADN based on the completion of the PDU session establishment procedure.

In addition, if the UE is located in an area where connection to LADN is possible and / or in the LADN service area, the PDU session establishment procedure is required to establish a PDU session for LADN. May start. Conversely, if the UE is located outside the LADN service area, execution of the PDU session establishment procedure for establishing a PDU session for LADN may be prohibited.

In other words, each device establishes a PDU session for LADN if the UE is located in an area where it can connect to LADN and / or if the UE is located in the LADN service area. In addition, the PDU session establishment procedure may be executed. Conversely, the network appliance may reject the request for a PDU session establishment procedure to establish a PDU session for LADN if the UE is located outside the LADN service area.

First, the UE sends a NAS message including a PDU session establishment request message to the SMF via 5GAN (gNB) and AMF (S900) (S902) (S904), PDU session. Start the establishment procedure.

Specifically, the UE sends a NAS message including a PDU session establishment request message to AMF via 5GAN (gNB) via the N1 interface (S900). The NAS message including the PDU session establishment request message may be an MM message. Further, the MM message may be an uplink NAS transport (UL NAS TRANSPORT) message. Here, when it is expressed that the PDU session establishment request message includes identification information and / or a value, it may mean that it is included in the MM message including the PDU session establishment request message.

Here, the UE may send one or more identification information by including it in a PDU session establishment request message and / or a NAS message, but a control message different from these, for example, a layer lower than the RRC layer. It may be included in the control message of (for example, MAC layer, RLC layer, PDCP layer) and transmitted. These identifications may be included in these messages to indicate the UE's request. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information.

When the AMF receives the NAS message including the PDU session establishment request message (S900), it extracts the PDU session establishment request message from the NAS message and selects SMF as the forwarding destination of the PDU session establishment request message (S902). In addition, AMF is the identification information and / or subscriber information contained in the PDU session establishment request message and / or NAS message, and / or the capacity information of the network, and / or the operator policy, and / or the state of the network. And / or the transfer destination SMF may be selected based on the user's registration information and / or the context held by the AMF.

AMF forwards the PDU session establishment request message to the selected SMF via the N11 interface (S904).

When the SMF receives the PDU session establishment request message (S904), it recognizes various identification information contained in the PDU session establishment request message. Then, the SMF executes the third condition determination. The third condition determination is for the SMF to determine whether or not to accept the UE's request. In the third condition determination, the SMF determines whether the third condition determination is true or false. If the third condition determination is true, the procedure of FIG. 8 (A) is started, and if the third condition determination is false, the procedure of FIG. 8 (B) is started.

The third condition determination is the PDU session establishment request message and / or each identification information included in the PDU session establishment request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy. , And / or based on the state of the network, and / or the user's registration information, and / or the context held by the SMF, etc. For example, if the network allows the UE request, the third condition may be true. Also, if the network does not allow the UE request, the third condition determination may be false. Furthermore, if the network to which the UE is connected and / or the devices in the network support the functions required by the UE, the third condition determination may be true and does not support the functions required by the UE. In this case, the third condition determination may be false. Further, if the transmitted / received identification information is permitted, the third condition determination may be true, and if the transmitted / received identification information is not permitted, the third condition determination may be false. The condition for determining the truth of the third condition determination is not limited to the above-mentioned condition.

Next, the steps when the third condition determination is true, that is, each step of the procedure (A) in FIG. 8 will be described. The SMF selects the UPF to which the PDU session is established, sends a session establishment request message to the selected UPF via the N4 interface (S906), and starts the procedure of (A) in FIG.

Here, the SMF obtains each identification information and / or subscriber information and / or network capability information acquired based on the reception of the PDU session establishment request message, and / or the operator policy, and / or the network status. And / or one or more UPFs may be selected based on the user's registration information and / or the context held by the SMF. When a plurality of UPFs are selected, the SMF may send a session establishment request message to each UPF.

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

The SMF receives the session establishment response message from the UPF via the N4 interface as a response message to the session establishment request message (S908). The SMF may assign an address to the UE based on the reception of the PDU session establishment request message and / or the selection of the UPF and / or the reception of the session establishment response message.

The SMF receives the PDU session establishment request message and / or selects the UPF and / or receives the session establishment response message and / or completes the address assignment of the address assigned to the UE. Sends a PDU session establishment acceptance message to (S910) (S912).

Specifically, when the SMF sends a PDU session establishment acceptance message to the AMF via the N11 interface (S910), the AMF that receives the PDU session establishment request message establishes a PDU session to the UE via the N1 interface. Send a NAS message containing an acceptance message (S912). The PDU session establishment acceptance message may be a NAS message and may be a response message to the PDU session establishment request. In addition, the PDU session establishment acceptance message may be sent and received by including the N1 interface in the MM message. Further, the MM message may be a NAS message or a downlink NAS transport (DL NAS TRANSPORT) message. Here, when it is expressed that the PDU session establishment acceptance message includes identification information and / or a value, it may mean that it is included in the MM message including the PDU session establishment acceptance message. In addition, the PDU session establishment acceptance message can indicate that the PDU session establishment has been accepted.

Here, the SMF and AMF may indicate that the UE request by the PDU session establishment request has been accepted by sending the PDU session establishment acceptance message.

SMF and AMF may send one or more identification information in the PDU session establishment acceptance message. In addition, SMF and AMF may indicate that the network supports each function by transmitting these identification information, or may indicate that the request of the UE has been accepted. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received to the same identification information or may be transmitted / received as different identification information.

In addition, SMF and AMF indicate whether to include one or more identification information in the PDU session establishment acceptance message, each identification information received and / or subscriber information, and / or network capability information, and / or operator policy. , And / or the state of the network, and / or the user's registration information, and / or the context held by AMF, etc., may be selected and determined.

Also, SMF and AMF can include the selected and / or allowed PDU session ID in the PDU session establishment acceptance message. SMF and AMF can also specify a PDU session type that indicates the type of PDU session selected and / or allowed. As the PDU session type, any one of IPv4, IPv6, IPv4v6, Ethernet, and Unstructured can be specified as described above. The SMF and AMF can also include the SSC mode of the selected and / or allowed PDU session in the PDU session establishment acceptance message.

Furthermore, SMF and AMF can include the approved QoS rule group in the PDU session establishment acceptance message. The approved QoS rule group may include one or more QoS rules. Further, if a plurality of QoS flows and / or user plane radio bearers are established in this procedure, the approved QoS rule group may include a plurality of QoS rules. Conversely, if only one QoS flow and / or user plane radio bearer is established in this procedure, the approved QoS rule group may include one QoS rule.

In addition, the SMF may send the PDU session establishment acceptance message with information indicating that some requests from the UE have been rejected, or information indicating that some requests from the UE have been rejected. May indicate why some of the UE's requests were rejected. In addition, the UE may recognize why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. The reason for rejection may be information indicating that the content indicated by the identification information received by the SMF is not permitted.

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

Specifically, the UE sends a PDU session establishment completion message to the AMF via the N1 interface (S914). When the AMF receives the PDU session establishment completion message from the UE, it sends the PDU session establishment completion message to the SMF via the N11 interface (S916).

The PDU session establishment completion message sent by AMF to SMF may be a response message to the PDU session establishment acceptance message sent from SMF to AMF by S910. Further, the PDU session establishment completion message may be a NAS message. Further, the PDU session establishment completion message may be any message indicating that the PDU session establishment procedure is completed.

When the SMF receives the PDU session establishment completion message from the AMF via the N11 interface (S916), the SMF can execute the second condition determination. The second condition determination is to determine the type of message sent and received on the N4 interface. If the second condition determination is true, the SMF sends a session change request message to the UPF via the N4 interface (S918) and receives a session change acceptance message sent by the UPF as its response message (S918). S920). If the second condition determination is false, the SMF sends a session establishment request message to the UPF via the N4 interface (S918) and receives a session change acceptance message sent by the UPF as its response message (S918). S920).

Note that the second condition determination may be executed based on whether or not a session on the N4 interface for the PDU session has been established. For example, if the session on the N4 interface for the PDU session is established, the second condition determination may be true, and if the session on the N4 interface for the PDU session is not established, the second condition is true. The condition determination of is false. The condition for determining the truth of the second condition determination is not limited to the above-mentioned condition.

Each device completes the procedure (A) during the PDU session establishment procedure based on the transmission / reception of the PDU session establishment completion message and / or the transmission / reception of the session change response message and / or the transmission / reception of the session establishment response message. When the procedure (A) during this procedure is completed, the UE is in a state where a PDU session for the DN has been established. Here, if the PDU session establishment procedure is a PDU session establishment procedure for establishing a PDU session for LADN, each device is for LADN based on the completion of procedure (A) during this procedure. PDU session may be established.

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

The PDU session establishment refusal message may be a NAS message or an SM message transmitted from the SMF to the UE. Further, the PDU session establishment refusal message may be any message indicating that the establishment of the PDU session has been rejected. In addition, the PDU session establishment refusal message may be sent and received by including the N1 interface in the MM message. Further, the MM message may be a NAS message or a downlink NAS transport (DL NAS TRANSPORT) message. Here, when it is expressed that the PDU session establishment refusal message includes identification information and / or a value, it may mean that it is included in the MM message including the PDU session establishment refusal message.

Here, the SMF may indicate that the UE request by the PDU session establishment request has been rejected by sending the PDU session establishment refusal message. In addition, the SMF may send the PDU session establishment rejection message with information indicating the reason for rejection, or may send the reason for rejection to indicate the reason for rejection. Further, the UE may recognize the reason why the UE's request is rejected by receiving the information indicating the reason why the UE's request is rejected. The reason for rejection may be information indicating that the content indicated by the identification information received by the SMF is not permitted.

The SMF and / or AMF may send one or more identifications and / or backoff timer values in the PDU session establishment rejection message, these identifications, and / or the backoff timer. By sending a value, it may indicate that the UE's request has been rejected, or it may indicate why the UE's request has been rejected.

In addition, the SMF and / or AMF may instruct the UE to set the backoff timer value to the value to be transmitted by transmitting the backoff timer value, or the backoff with the transmitted value set. You may instruct to start the timer.

It should be noted that SMF and / or AMF may include each identification information received in the PDU session establishment refusal message, and / or subscriber information, and / or network capability information, and /. Alternatively, it may be selected and determined based on the operator policy and / or the state of the network and / or the user's registration information and / or the context held by the AMF.

By receiving the PDU session establishment refusal message, the UE can recognize that the UE request by the PDU session establishment request has been rejected and the contents of various identification information included in the PDU session establishment refusal message.

Each device completes the PDU session establishment procedure based on the completion of the procedure (A) or (B) in FIG. In addition, each device may transition to the state in which the PDU session is established based on the completion of the procedure of FIG. 8 (A), or the PDU is based on the completion of the procedure of FIG. 8 (B). You may recognize that the session establishment procedure has been rejected, or you may transition to a state where the PDU session has not been established. Furthermore, the UE can communicate with the DN using the established PDU session by completing the procedure (A) in FIG.

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

In addition, the UE may store the identification information received with the PDU session establishment acceptance message and / or the PDU session establishment rejection message based on the completion of the PDU session establishment procedure, and may recognize the network decision. good.

Further, when the UE receives the back-off timer value, the UE may set the back-off timer value to the back-off timer, or may start the back-off timer in which the received back-off timer value is set.

[3.2.3. Non-registration procedure]
Next, the de-registration procedure will be described. Hereinafter, the non-registration procedure is also referred to as this procedure. The non-registration procedure is a procedure initiated by the UE or the network, and is a procedure for canceling the registration of the UE. The non-registration procedure may be a procedure for changing the state of the UE to the non-registration state.

The UE and the network can execute this procedure at any time as long as the UE is registered in the network. In other words, the UE and the network can start this procedure at any time if the UE is in the registered state. In addition, each device (particularly UE and AMF) can transition to the non-registered state based on the completion of the registration procedure.

Furthermore, devices in the core network such as AMF may start this procedure based on the update of network settings and / or the update of operator policy. The trigger of this procedure may be the detection of the mobility of the UE, the detection of the state change of the UE and / or the access network and / or the core network, or the state change of the network slice. It may be. Further, the trigger of this procedure may be the reception of a request from the DN and / or the application server of the DN, a change in network settings, or a change in operator policy. .. Further, the trigger of this procedure may be the expiration of the running timer. The triggers for the devices in the core network to start this procedure are not limited to these. Further, this procedure may be executed at any timing as long as each device has established a 5GMM context and / or each device is in the 5GMM connection mode.

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

Furthermore, the trigger of this procedure may be the expiration of the timer. Here, the timer may be a timer managed by the UE and / or the network. More specifically, the timer may be a timer indicating an expiration date for which registration is only available for onboarding services. In other words, the timer may be a timer indicating a deadline for executing the procedure for providing SNPN information.

In addition, each device sends and receives a message containing identification information indicating the reason why the registration of the UE is canceled and / or identification information indicating that the network needs to be reselected during this procedure. You may. In addition, each device may release the context of the UE or initiate network-directed behavior upon completion of this procedure.

The UE may recognize the reason why the registration of the UE is canceled based on the control information sent and received by this procedure. In addition, the UE may release the context of the UE or initiate network reselection as it recognizes why the UE is unregistered. In other words, the device in the core network leads the procedure and also sends the control message and control information of the procedure to the UE to make the UE aware of the reason why the UE is deregistered. May be good. Further, the device in the core network may release the context of the UE by recognizing the reason why the UE is unregistered, or may cause the UE to start reselecting the network.

The non-registration procedure includes a network-led non-registration procedure and a UE-led non-registration procedure. The network-led non-registration procedure and the UE-led non-registration procedure will be explained below.

[3.2.3.1. Network-led non-registration procedure]
First, the network-initiated de-registration procedure will be described with reference to FIG. Hereinafter, the network-led non-registration procedure is also referred to as this procedure. The network-led non-registration procedure is a network-led procedure among the non-registration procedures. Each step of this procedure will be explained below.

First, AMF starts the non-registration procedure by sending a deregistration request message to the UE via 5GAN (or gNB) (S900).

AMF may send the registration acceptance message with at least the 31st identification information. By transmitting these identification information, the AMF may indicate the reason why the registration of the UE is canceled, or may indicate that the network needs to be reselected. Further, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received to the same identification information or may be transmitted / received as different identification information.

AMF may include the 31st identification information in the non-registration request message when the onboarding service is completed. Further, the AMF may include the 31st identification information in the non-registration request message when the procedure for providing the SNPN information is completed.

Furthermore, AMF may include the 31st identification information in the non-registration request message if the onboarding service is not completed. Further, the AMF may include the 31st identification information in the non-registration request message if the procedure for providing the SNPN information is not completed.

Furthermore, AMF may include the 31st identification information in the non-registration request message if the onboarding service is successful. In addition, the AMF may include the 31st identification information in the non-registration request message if the procedure for providing the SNPN information is successful. In addition, the AMF may include the 31st identification information in the non-registration request message if the SNPN information is successfully provided.

Furthermore, AMF may include the 31st identification information in the non-registration request message if the onboarding service fails. In addition, the AMF may include the 31st identification information in the non-registration request message if the procedure for providing SNPN information fails. In addition, the AMF may include the 31st identification information in the non-registration request message if the provision of SNPN information fails.

Furthermore, the AMF may include the 31st identification information in the non-registration request message when the timer managed by the UE and / or the network has expired. In addition, the AMF may include the 31st identification in the non-registration request message when the registration, which is only available for onboarding services, is no longer valid.

Furthermore, AMF may include the 31st identification information in the non-registration request message if it is not possible to provide the SNPN information. In addition, the AMF may include the 31st identification in the non-registration request message if the onboarding service is not executable. In addition, AMF may include the 31st identification information in the non-registration request message if it is not possible to carry out the procedure for providing SNPN information.

Furthermore, when the onboarding service is completed, the AMF may include the 31st identification information indicating that the onboarding service is completed in the non-registration request message. Further, when the procedure for providing SNPN information is completed, AMF may include the 31st identification information indicating that the procedure for providing SNPN information is completed in the non-registration request message.

Furthermore, if the onboarding service is not completed, the AMF may include the 31st identification information indicating that the onboarding service has not been completed in the non-registration request message. Furthermore, if the procedure for providing SNPN information is not completed, AMF may include the 31st identification information indicating that the procedure for providing SNPN information has not been completed in the non-registration request message.

Furthermore, if the onboarding service is successful, the AMF may include the 31st identification information indicating that the onboarding service was successful in the non-registration request message. Further, if the procedure for providing the SNPN information is successful, the AMF may include the 31st identification information indicating that the procedure for providing the SNPN information is successful in the non-registration request message. Further, if the provision of SNPN information is successful, the AMF may include the 31st identification information indicating that the provision of SNPN information is successful in the non-registration request message.

Furthermore, if the onboarding service fails, the AMF may include the 31st identification information indicating that the onboarding service has failed in the non-registration request message. Further, if the procedure for providing SNPN information fails, the AMF may include the 31st identification information indicating that the procedure for providing SNPN information has failed in the non-registration request message. Further, if the provision of SNPN information fails, the AMF may include the 31st identification information indicating that the provision of SNPN information has failed in the non-registration request message.

Furthermore, if the timer managed by the UE and / or the network has expired, the AMF may include the 31st identification information indicating that the timer has expired in the non-registration request message. In addition, the AMF will include in the non-registration request message a thirty-first identification that indicates that the registration that is only available to the onboarding service is no longer valid if the registration that is only available to the onboarding service is no longer valid. You may.

Furthermore, the AMF may indicate to the UE the content indicated by the identification information included in the non-registration request message by including the 31st identification information in the non-registration request message. Further, the AMF does not have to allow the UE the content indicated by the identification information included in the non-registration request message by including the 31st identification information in the non-registration request message.

In addition, AMF may include each identification information received, and / or subscriber information, and / or network capability information, and / or operator policy, and / or whether to include the 31st identification information in the non-registration request message. It may be selected and determined based on the state of the network and / or the user's registration information and / or the context held by AMF.

AMF also 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. A request to release the context of the UE may be indicated by sending a non-registration request message based on the context held by the AMF.

UE receives a non-registration request message via 5GAN (gNB) (S900). The UE may recognize the reason why the UE is unregistered and may perform network reselection based on the non-registration request message and / or the identification information contained in the non-registration request message. .. In addition, the UE sends a Deregistration accept message to AMF via 5GAN (gNB) as a response message to the non-registration request message based on the identification information contained in the non-registration request message. May be good (S902).

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

In addition, each process that the UE shown above executes based on the reception of each identification information may be executed during this procedure or after the completion of this procedure, or may be executed based on the completion of this procedure after the completion of this procedure. good.

Further, each device may perform processing based on the information transmitted / received in this procedure based on the completion of this procedure. For example, when the update information for the setting information is transmitted and received, each device may release the context of the UE. In addition, if the UE sends and receives information indicating that the network needs to be reselected and / or the registration procedure must be performed, the UE initiates the network reselection and / or registration procedure based on the completion of this procedure. You may.

Furthermore, the UE may store the identification information received with the non-registration request message based on the completion of this procedure, or may recognize the network decision.

For example, when the UE receives the 31st identification information, it may recognize that the onboarding service has been completed. Further, when the UE receives the 31st identification information, it may recognize that the procedure for providing the SNPN information has been completed.

Furthermore, when the UE receives the 31st identification information, it may recognize that the onboarding service has not been completed. Further, when the UE receives the 31st identification information, it may recognize that the procedure for providing the SNPN information has not been completed.

Furthermore, when the UE receives the 31st identification information, it may determine whether or not the onboarding service has been completed. Further, when the UE receives the 31st identification information, it may determine whether or not the procedure for providing the SNPN information has been completed.

Furthermore, the UE may recognize that the onboarding service has succeeded when it receives the 31st identification information. Further, when the UE receives the 31st identification information, it may recognize that the procedure for providing the SNPN information is successful. Further, the UE may recognize that the provision and / or acquisition of the SNPN information is successful when the 31st identification information is received.

Furthermore, the UE may recognize that the onboarding service has failed when it receives the 31st identification information. Further, the UE may recognize that the procedure for providing the SNPN information has failed when the 31st identification information is received. Further, the UE may recognize that the provision and / or acquisition of the SNPN information has failed when the 31st identification information is received.

Furthermore, when the UE receives the 31st identification information, it may determine whether the onboarding service has succeeded or failed. Further, when the UE receives the 31st identification information, it may determine whether the procedure for providing the SNPN information is successful or unsuccessful. Further, when the UE receives the 31st identification information, it may determine whether the provision and / or acquisition of the SNPN information is successful or unsuccessful.

Furthermore, when the UE receives the 31st identification information, it may recognize that the timer managed by the UE and / or the network has expired. In addition, the UE may recognize that upon receiving the 31st identification, the registration, which is only available to the onboarding service, is no longer valid.

Furthermore, the UE may recognize that when the 31st identification information is received, it is not possible to provide and / or acquire the SNPN information. Further, the UE may recognize that the onboarding service cannot be executed when the 31st identification information is received. Further, the UE may recognize that the procedure for providing the SNPN information cannot be executed when the 31st identification information is received.

Further, the UE may recognize that the onboarding service has been completed when it receives the 31st identification information indicating that the onboarding service has been completed. Further, the UE may recognize that the SNPN information provision procedure has been completed when it receives the 31st identification information indicating that the SNPN information provision procedure has been completed.

Further, the UE may recognize that the onboarding service has not been completed when it receives the 31st identification information indicating that the onboarding service has not been completed. Further, the UE may recognize that the SNPN information provision procedure has not been completed when it receives the 31st identification information indicating that the SNPN information provision procedure has not been completed.

Furthermore, the UE may recognize that the onboarding service has succeeded when it receives the 31st identification information indicating that the onboarding service has succeeded. Further, the UE may recognize that the procedure for providing SNPN information has been successful when it receives the 31st identification information indicating that the procedure for providing SNPN information has been successful. Further, the UE may recognize that the provision and / or acquisition of the SNPN information is successful when it receives the 31st identification information indicating that the provision of the SNPN information is successful.

Further, the UE may recognize that the onboarding service has failed when it receives the 31st identification information indicating that the onboarding service has failed. Further, the UE may recognize that the procedure for providing SNPN information has failed when it receives the 31st identification information indicating that the procedure for providing SNPN information has failed. Further, the UE may recognize that the provision and / or acquisition of the SNPN information has failed when it receives the 31st identification information indicating that the provision of the SNPN information has failed.

Furthermore, when the UE receives the 31st identification information indicating that the timer has expired, it may recognize that the timer managed by the UE and / or the network has expired. In addition, the UE recognizes that the registration available only for the onboarding service is no longer valid when it receives the 31st identification information indicating that the registration available only for the onboarding service is no longer valid. You may.

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

Furthermore, when the UE receives the 31st identification information, the first list may be released or deleted. Further, when the UE receives the 31st identification information, the UE may remove the network identification information from the 1st list.

More specifically, when the UE receives the 31st identification information indicating that the onboarding service is completed, the first list may be released or deleted. Further, when the UE receives the 31st identification information indicating that the procedure for providing the SNPN information is completed, the first list may be released or deleted.

Furthermore, when the UE receives the 31st identification information indicating that the onboarding service is successful, the first list may be released or deleted. Further, when the UE receives the 31st identification information indicating that the procedure for providing the SNPN information is successful, the first list may be released or deleted. Further, when the UE receives the 31st identification information indicating that the provision of the SNPN information is successful, the first list may be released or deleted.

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

Furthermore, the UE may release or delete the first list if the onboarding service is successful. Further, the UE may release or delete the first list if the procedure for providing SNPN information is successful. Further, the UE may release or delete the first list if the acquisition of the SNPN information is successful.

Here, the network identification information may be information that identifies the network in which the UE is currently located. More specifically, when the UE is located on the PLMN, the network identification information may be information that identifies the PLMN on which the UE is currently located. Conversely, when the UE is located in the SNPN, the network identification information may be information that identifies the SNPN in which the UE is currently located.

For example, when this procedure is executed in the first network, the identification information of the network may be the information for identifying the first network. More specifically, when this procedure is executed in the first PLMN, the network identification information may be information that identifies the first PLMN. Further, when this procedure is executed in the first SNPN, the network identification information may be information that identifies the first SNPN.

Furthermore, the UE may execute the second network selection when it receives the 31st identification information. Further, when the UE receives the 31st identification information, it may perform a second network selection and select the target SNPN. In addition, the UE may initiate the registration process on the new network of choice after completing the execution of the second network selection.

More specifically, the UE may perform a second network selection when it receives the 31st identification information indicating that the onboarding service has been completed. Further, the UE may perform a second network selection when it receives the 31st identification information indicating that the procedure for providing the SNPN information has been completed.

Furthermore, the UE may execute a second network selection when it receives the 31st identification information indicating that the onboarding service was successful. In addition, the UE may perform a second network selection if it receives the 31st identification information indicating that the procedure for providing the SNPN information was successful. In addition, the UE may perform a second network selection if it receives a thirty-first identification that indicates a successful provision of SNPN information.

Conversely, when the UE receives the 31st identification information, it may add the network identification information to the 1st list. Further, when the UE receives the 31st identification information, it may create a first list and add the network identification information to the created first list.

More specifically, the UE may add the network identification information to the first list when it receives the 31st identification information indicating that the onboarding service has not been completed. Further, the UE may add the network identification information to the first list when it receives the 31st identification information indicating that the procedure for providing the SNPN information has not been completed.

Furthermore, the UE may add the network identification information to the first list when it receives the 31st identification information indicating that the onboarding service has failed. Further, the UE may add the network identification information to the first list when it receives the 31st identification information indicating that the procedure for providing the SNPN information has failed. Further, the UE may add the network identification information to the first list when it receives the 31st identification information indicating that the provision of the SNPN information has failed.

Furthermore, the UE may add the network identification information to the first list when it receives the 31st identification information indicating that the timer has expired. In addition, the UE may add the network identification to the first list when it receives a thirty-first identification indicating that the registration, which is only available for onboarding services, is no longer valid.

Furthermore, the UE may add the network identification information to the first list if the onboarding service has not been completed. In addition, the UE may add the network identification information to the first list if the procedure for providing the SNPN information has not been completed. Further, the UE may add the network identification information to the first list if the acquisition of the SNPN information is not completed.

Furthermore, the UE may add the network identification information to the first list if the onboarding service fails. In addition, the UE may add the network identification information to the first list if the procedure for providing SNPN information fails. Further, the UE may add the network identification information to the first list if the acquisition of the SNPN information fails.

Here, the network identification information may be information that identifies the network in which the UE is currently located. More specifically, when the UE is located on the PLMN, the network identification information may be information that identifies the PLMN on which the UE is currently located. Conversely, when the UE is located in the SNPN, the network identification information may be information that identifies the SNPN in which the UE is currently located.

For example, when this procedure is executed in the first network, the identification information of the network may be the information for identifying the first network. More specifically, when this procedure is executed in the first PLMN, the network identification information may be information that identifies the first PLMN. Further, when this procedure is executed in the first SNPN, the network identification information may be information that identifies the first SNPN.

Furthermore, the UE may re-execute the first network selection when it receives the 31st identification information. Further, when the UE receives the 31st identification information, it may re-execute the first network selection and select a network different from the network in which it is currently located. In addition, the UE may initiate the registration process on the new network of choice after the re-execution of the first network selection is complete.

More specifically, the UE may re-execute the first network selection when it receives the 31st identification information indicating that the onboarding service has not been completed. Further, the UE may re-execute the first network selection when it receives the 31st identification information indicating that the procedure for providing the SNPN information has not been completed.

Furthermore, the UE may re-execute the first network selection when it receives the 31st identification information indicating that the onboarding service has failed. Further, the UE may re-execute the first network selection if it receives the 31st identification information indicating that the procedure for providing the SNPN information has failed. Further, the UE may re-execute the first network selection if it receives the 31st identification information indicating that the provision of SNPN information has failed.

Furthermore, the UE may re-execute the first network selection when it receives the 31st identification information indicating that the timer has expired. In addition, the UE may re-execute the first network selection if it receives a thirty-first identification that indicates that the registration, which is only available for onboarding services, is no longer valid.

Furthermore, the UE may start the timer when it receives the 31st identification information. Here, the timer may be a timer indicating a deadline for managing the first list. In other words, the UE may release or delete the first list based on the expiration of the timer.

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

Note that the behavior performed when each identification information is received may be performed based on the received identification information. For example, the behavior performed when the 31st identification information is received may be performed based on the received 31st identification information.

In the above procedure, by sending and receiving the non-registration request message, the device in the core network can instruct the UE to release the setting information already applied by the UE, and the UE is executing. You can instruct to stop or change the function.

[3.2.3.2. UE-led non-registration procedure]
First, the UE-initiated de-registration procedure will be described with reference to FIG. 10. Hereinafter, the UE-led non-registration procedure is also referred to as this procedure. The UE-led non-registration procedure is a procedure that is initiated by the UE among the non-registration procedures. Each step of this procedure will be explained below.

First, the UE starts the non-registration procedure by sending a deregistration request message to AMF via 5GAN (or gNB) (S1000).

The UE may send the registration acceptance message including at least the 31st identification information. By transmitting these identification information, the UE may indicate the reason why the registration of the UE is canceled, or may indicate that the network needs to be reselected. Further, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received to the same identification information or may be transmitted / received as different identification information.

The UE may include the 31st identification information in the non-registration request message when the onboarding service is completed. Further, the UE may include the 31st identification information in the non-registration request message when the procedure for providing the SNPN information is completed.

Furthermore, the UE may include the 31st identification information in the non-registration request message if the onboarding service is not completed. Further, the UE may include the 31st identification information in the non-registration request message if the procedure for providing the SNPN information is not completed.

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

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

Furthermore, the UE may include the 31st identification information in the non-registration request message when the timer managed by the UE and / or the network has expired. In addition, the UE may include the 31st identification in the non-registration request message when the registration, which is only available for onboarding services, is no longer valid.

Furthermore, the UE may include the 31st identification information in the non-registration request message if it is not possible to provide and / or obtain the SNPN information. Further, the UE may include the 31st identification information in the non-registration request message if the onboarding service cannot be executed. Further, the UE may include the 31st identification information in the non-registration request message if it is not possible to execute the procedure for providing the SNPN information.

Furthermore, when the onboarding service is completed, the UE may include the 31st identification information indicating that the onboarding service is completed in the non-registration request message. Further, when the procedure for providing SNPN information is completed, the UE may include the 31st identification information indicating that the procedure for providing SNPN information is completed in the non-registration request message.

Furthermore, if the onboarding service is not completed, the UE may include the 31st identification information indicating that the onboarding service has not been completed in the non-registration request message. Further, if the procedure for providing SNPN information is not completed, the UE may include the 31st identification information indicating that the procedure for providing SNPN information is not completed in the non-registration request message.

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

Furthermore, if the onboarding service fails, the UE may include the 31st identification information indicating that the onboarding service has failed in the non-registration request message. Further, if the procedure for providing SNPN information fails, the UE may include the 31st identification information indicating that the procedure for providing SNPN information has failed in the non-registration request message. In addition, the UE may include in the non-registration request message a thirty-first identification information indicating that the provision of SNPN information has failed if the provision and / or acquisition of SNPN information fails.

Further, the UE may include the 31st identification information indicating that the timer has expired in the non-registration request message when the timer managed by the UE and / or the network has expired. In addition, the UE will include in the non-registration request message a thirty-first identification that indicates that the registration that is only available to the onboarding service is no longer valid if the registration that is only available to the onboarding service is no longer valid. You may.

Furthermore, the UE may indicate to the AMF the content indicated by the identification information included in the non-registration request message by including the 31st identification information in the non-registration request message. Further, the UE does not have to allow AMF the content indicated by the identification information included in the non-registration request message by including the 31st identification information in the non-registration request message.

It should be noted that the UE asks whether to include the 31st identification information in the non-registration request message, each identification information received, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and / or. It may be selected and determined based on the state of the network and / or the user's registration information and / or the context held by the UE.

In addition, the UE is the received identification information and / or the subscriber information and / or the ability information of the UE, and / or the state of the UE, and / or the registration information of the user, and / or the context held by the UE, etc. A request to release the context of the UE may be indicated by sending a non-registration request message based on.

AMF receives a non-registration request message via 5GAN (gNB) (S1000). The AMF may recognize the reason why the UE is unregistered based on the non-registration request message and / or the identification information contained in the non-registration request message. In addition, AMF sends a Deregistration accept message to the UE via 5GAN (gNB) as a response message to the non-registration request message based on the identification information contained in the non-registration request message. May be good (S1002).

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

In addition, each process shown above by AMF based on the reception of each identification information may be executed during or after the completion of this procedure, or may be executed based on the completion of this procedure after the completion of this procedure. good.

Further, each device may perform processing based on the information transmitted / received in this procedure based on the completion of this procedure. For example, when the update information for the setting information is transmitted and received, each device may release the context of the UE. In addition, if the UE sends and receives information indicating that the network needs to be reselected and / or the registration procedure must be performed, the UE initiates the network reselection and / or registration procedure based on the completion of this procedure. You may.

Furthermore, the UE may store the identification information received with the non-registration request message based on the completion of this procedure, or may recognize the network decision.

For example, the UE may recognize that the onboarding service has been completed when the 31st identification information is transmitted. Further, the UE may recognize that the procedure for providing the SNPN information has been completed when the 31st identification information is transmitted.

Furthermore, the UE may recognize that the onboarding service has not been completed when the 31st identification information is transmitted. Further, the UE may recognize that the procedure for providing the SNPN information has not been completed when the 31st identification information is transmitted.

Furthermore, the UE may determine whether or not the onboarding service has been completed when the 31st identification information is transmitted. Further, the UE may determine whether or not the procedure for providing the SNPN information has been completed when the 31st identification information is transmitted.

Furthermore, the UE may recognize that the onboarding service was successful when the 31st identification information is transmitted. Further, the UE may recognize that the procedure for providing the SNPN information is successful when the 31st identification information is transmitted. Further, the UE may recognize that the provision and / or acquisition of the SNPN information is successful when the 31st identification information is transmitted.

Furthermore, the UE may recognize that the onboarding service has failed when the 31st identification information is transmitted. Further, the UE may recognize that the procedure for providing the SNPN information has failed when the 31st identification information is transmitted. Further, the UE may recognize that the provision and / or acquisition of the SNPN information has failed when the 31st identification information is transmitted.

Furthermore, the UE may determine whether the onboarding service succeeded or failed when the 31st identification information was transmitted. Further, when the UE transmits the 31st identification information, it may determine whether the procedure for providing the SNPN information is successful or unsuccessful. Further, when the UE transmits the 31st identification information, it may determine whether the provision and / or acquisition of the SNPN information is successful or unsuccessful.

Furthermore, the UE may recognize that the timer managed by the UE and / or the network has expired when the 31st identification information is transmitted. In addition, the UE may recognize that the registration, which is only available to the onboarding service, is no longer valid when the 31st identification information is transmitted.

Furthermore, the UE may recognize that it is not possible to provide and / or obtain the SNPN information when the 31st identification information is transmitted. Further, the UE may recognize that the onboarding service cannot be executed if the 31st identification information is transmitted. Further, the UE may recognize that it is not possible to execute the procedure for providing the SNPN information when the 31st identification information is transmitted.

Furthermore, the UE may recognize that the onboarding service has been completed when it transmits the 31st identification information indicating that the onboarding service has been completed. Further, the UE may recognize that the SNPN information provision procedure has been completed when the 31st identification information indicating that the SNPN information provision procedure has been completed is transmitted.

Further, the UE may recognize that the onboarding service has not been completed when the 31st identification information indicating that the onboarding service has not been completed is transmitted. Further, the UE may recognize that the SNPN information provision procedure has not been completed when the 31st identification information indicating that the SNPN information provision procedure has not been completed is transmitted.

Furthermore, the UE may recognize that the onboarding service has succeeded when it sends the 31st identification information indicating that the onboarding service has succeeded. Further, the UE may recognize that the procedure for providing SNPN information has been successful when the third identification information indicating that the procedure for providing SNPN information has been successful is transmitted. Further, the UE may recognize that the provision and / or acquisition of the SNPN information is successful when the 31st identification information indicating that the provision of the SNPN information is successful is transmitted.

Furthermore, the UE may recognize that the onboarding service has failed when it sends the 31st identification information indicating that the onboarding service has failed. Further, the UE may recognize that the procedure for providing SNPN information has failed when the third identification information indicating that the procedure for providing SNPN information has failed is transmitted. Further, the UE may recognize that the provision and / or acquisition of the SNPN information has failed when the 31st identification information indicating that the provision of the SNPN information has failed is transmitted.

Furthermore, when the UE transmits the 31st identification information indicating that the timer has expired, the UE may recognize that the timer managed by the UE and / or the network has expired. In addition, the UE recognizes that the registration available only for the onboarding service is no longer valid if it sends the 31st identification information indicating that the registration available only for the onboarding service is no longer valid. You may.

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

Furthermore, when the UE sends the 31st identification information, the 1st list may be released or deleted. In addition, the UE may remove the network identification information from the first list if it sends the 31st identification information.

More specifically, when the UE sends the 31st identification information indicating that the onboarding service is completed, the 1st list may be released or deleted. Further, when the UE sends the 31st identification information indicating that the procedure for providing the SNPN information is completed, the first list may be released or deleted.

Furthermore, when the UE sends the 31st identification information indicating that the onboarding service is successful, the first list may be released or deleted. Further, when the UE sends the 31st identification information indicating that the procedure for providing the SNPN information is successful, the first list may be released or deleted. Further, when the UE sends the 31st identification information indicating that the provision of the SNPN information is successful, the first list may be released or deleted.

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

Furthermore, the UE may release or delete the first list if the onboarding service is successful. Further, the UE may release or delete the first list if the procedure for providing SNPN information is successful. Further, the UE may release or delete the first list if the acquisition of the SNPN information is successful.

Furthermore, when the UE receives the non-registration acceptance message, the first list may be released or deleted. In addition, the UE may remove the network identification information from the first list when it receives an unregistered acceptance message.

Here, the network identification information may be information that identifies the network in which the UE is currently located. More specifically, when the UE is located on the PLMN, the network identification information may be information that identifies the PLMN on which the UE is currently located. Conversely, when the UE is located in the SNPN, the network identification information may be information that identifies the SNPN in which the UE is currently located.

For example, when this procedure is executed in the first network, the identification information of the network may be the information for identifying the first network. More specifically, when this procedure is executed in the first PLMN, the network identification information may be information that identifies the first PLMN. Further, when this procedure is executed in the first SNPN, the network identification information may be information that identifies the first SNPN.

Furthermore, the UE may execute the second network selection when the 31st identification information is transmitted. In addition, the UE may perform a second network selection and select the target SNPN if it has transmitted the 31st identification information. In addition, the UE may initiate the registration process on the new network of choice after completing the execution of the second network selection.

More specifically, the UE may perform a second network selection if it sends the 31st identification information indicating that the onboarding service has been completed. In addition, the UE may perform a second network selection if it sends the 31st identification information indicating that the procedure for providing the SNPN information has been completed.

Furthermore, the UE may perform a second network selection if it sends the 31st identification information indicating that the onboarding service was successful. In addition, the UE may perform a second network selection if it sends a thirty-first identification piece indicating that the procedure for providing SNPN information was successful. In addition, the UE may perform a second network selection if it sends a thirty-first identification piece indicating that the SNPN information has been successfully provided.

Furthermore, the UE may execute a second network selection when it receives the non-registration acceptance message. In addition, the UE may perform a second network selection and select the target SNPN when it receives the unregistered acceptance message. In addition, the UE may initiate the registration process on the new network of choice after completing the execution of the second network selection.

Conversely, if the UE sends the 31st identification information, the UE may add the network identification information to the 1st list. Further, when the UE sends the 31st identification information, the UE may create a first list and add the network identification information to the created first list.

More specifically, if the UE sends the 31st identification information indicating that the onboarding service has not been completed, the UE may add the network identification information to the 1st list. Further, if the UE sends the 31st identification information indicating that the procedure for providing the SNPN information has not been completed, the UE may add the network identification information to the 1st list.

Furthermore, if the UE sends the 31st identification information indicating that the onboarding service has failed, the UE may add the network identification information to the 1st list. In addition, the UE may add the network identification information to the first list if it sends the 31st identification information indicating that the procedure for providing the SNPN information has failed. In addition, the UE may add the network identification information to the first list if it sends a thirty-first identification information indicating that the provision of SNPN information has failed.

Furthermore, if the UE sends the 31st identification information indicating that the timer has expired, the UE may add the network identification information to the 1st list. In addition, the UE may add the network identification to the first list if it sends a thirty-first identification indicating that the registration, which is only available for onboarding services, is no longer valid.

Furthermore, the UE may add the network identification information to the first list if the onboarding service has not been completed. In addition, the UE may add the network identification information to the first list if the procedure for providing the SNPN information has not been completed. Further, the UE may add the network identification information to the first list if the acquisition of the SNPN information is not completed.

Furthermore, the UE may add the network identification information to the first list if the onboarding service fails. In addition, the UE may add the network identification information to the first list if the procedure for providing SNPN information fails. Further, the UE may add the network identification information to the first list if the acquisition of the SNPN information fails.

Furthermore, the UE may add the network identification information to the first list when it receives the unregistered acceptance message. Further, when the UE receives the unregistered acceptance message, it may create a first list and add the network identification information to the created first list.

Here, the network identification information may be information that identifies the network in which the UE is currently located. More specifically, when the UE is located on the PLMN, the network identification information may be information that identifies the PLMN on which the UE is currently located. Conversely, when the UE is located in the SNPN, the network identification information may be information that identifies the SNPN in which the UE is currently located.

For example, when this procedure is executed in the first network, the identification information of the network may be the information for identifying the first network. More specifically, when this procedure is executed in the first PLMN, the network identification information may be information that identifies the first PLMN. Further, when this procedure is executed in the first SNPN, the network identification information may be information that identifies the first SNPN.

Furthermore, when the UE transmits the 31st identification information, the UE may re-execute the 1st network selection. Further, if the UE transmits the 31st identification information, it may re-execute the first network selection and select a network different from the network in which it is currently located. In addition, the UE may initiate the registration process on the new network of choice after the re-execution of the first network selection is complete.

More specifically, the UE may re-execute the first network selection if it sends the 31st identification information indicating that the onboarding service has not been completed. Further, the UE may re-execute the first network selection if it sends the 31st identification information indicating that the procedure for providing the SNPN information has not been completed.

Furthermore, the UE may re-execute the first network selection if it sends the 31st identification information indicating that the onboarding service has failed. Further, the UE may re-execute the first network selection if it sends the 31st identification information indicating that the procedure for providing the SNPN information has failed. In addition, the UE may re-execute the first network selection if it sends the 31st identification information indicating that the provision of SNPN information has failed.

Furthermore, the UE may re-execute the first network selection if it sends the 31st identification information indicating that the timer has expired. In addition, the UE may re-execute the first network selection if it sends a thirty-first identification that indicates that the registration, which is only available for onboarding services, is no longer valid.

Furthermore, the UE may re-execute the first network selection when it receives the non-registration acceptance message. Further, when the UE receives the unregistered acceptance message, it may re-execute the first network selection and select a network different from the network in which it is currently located. In addition, the UE may initiate the registration process on the new network of choice after the re-execution of the first network selection is complete.

Furthermore, the UE may start the timer when the 31st identification information is transmitted. In addition, the UE may start a timer when it receives an unregistered acceptance message.

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

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

Note that the behavior performed when each identification information is transmitted may be performed based on the transmitted identification information. For example, the behavior performed when the 31st identification information is transmitted may be performed based on the transmitted 31st identification information.

In the above procedure, by sending and receiving the non-registration request message, the device in the core network can instruct the UE to release the setting information already applied by the UE, and the UE is executing. You can instruct to stop or change the function.

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

Even if the UE decides whether to execute the first procedure based on the UE setting information and / or the information received from the network, and / or the UE mode, and / or the UE capability information. good.

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

Here, the UE may start the PDU session establishment procedure in the first network based on the completion of the registration procedure (S604). When the PDU session establishment procedure is started, each device may perform the PDU session establishment procedure in the first network.

Next, based on the completion of the registration procedure and / or the completion of the PDU session establishment procedure, each device performs the procedure for providing SNPN information (S606). Next, based on the completion of the procedure for providing SNPN information, each device performs a non-registration procedure in the first network (S608).

Next, the UE makes a second network selection based on the completion of the non-registration procedure (S610). Next, based on the second network selection, the UE connects to the selected second network and initiates the registration process (S612). Next, based on the start of the registration procedure, each device performs the registration procedure in the second network. With the above, the first procedure is completed.

Here, the first network may be SNPN or PLMN. Further, the first network may be a network for onboarding services.

Furthermore, the second network may be SNPN. Further, the second network may be the network that the UE was trying to connect to. In addition, the second network may be the target SNPN.

Furthermore, the second network may be a different network from the first network. Conversely, the second network may be the same network as the first network.

Furthermore, the procedure for providing SNPN information may be carried out between the UE and the provisioning server. Here, the provisioning server may exist in the first network. In addition, the provisioning server may reside on the second network. Conversely, the provisioning server may reside on a different network than the first and second networks.

Further, the PDU session establishment procedure may be a procedure for establishing a PDU session for providing SNPN information. In other words, the PDU session establishment procedure may be a procedure for establishing a PDU session used in the procedure for providing SNPN information. Further, the PDU session establishment procedure may be a procedure for establishing a PDU session for the onboarding service. Further, the PDU session establishment procedure may be a procedure for establishing a PDU session used in the onboarding service.

Here, the UE may decide whether or not to execute the PDU session establishment procedure based on the identification information sent and received in the registration procedure. For example, the UE may initiate the PDU session establishment procedure if it recognizes that the registration procedure permits the use of the SNPN information provision procedure. More specifically, the UE may initiate the PDU session establishment procedure if it recognizes that the registration procedure has allowed the use of the procedure for providing SNPN information via the user plane. In addition, the UE may initiate the PDU session establishment procedure if it recognizes that it is authorized to use the SNPN information provision procedure using PCO or ePCO.

On the contrary, the UE does not have to start the PDU session establishment procedure when it recognizes that the use of the SNPN information provision procedure via the control plane is permitted in the registration procedure. More specifically, the UE may not initiate the PDU session establishment procedure if it recognizes that the registration procedure has allowed the use of the SNPN information provision procedure using the URSP.

Furthermore, the non-registration procedure may be executed based on the completion of the procedure for providing SNPN information. Specifically, each device may perform a non-registration procedure based on the completion of the SNPN information provision procedure. In addition, each device may perform a non-registration procedure based on the success of the procedure for providing SNPN information.

Furthermore, the non-registration procedure may be executed after the procedure for providing SNPN information is completed. Specifically, each device may execute the non-registration procedure after completing the procedure for providing SNPN information. Further, each device may execute the non-registration procedure after the procedure for providing the SNPN information is successful.

On the contrary, the non-registration procedure may be executed without completing the procedure for providing SNPN information. Specifically, each device may perform a non-registration procedure based on the expiration of the timer. In addition, each device may perform a non-registration procedure based on the failure of the SNPN information provision procedure.

Furthermore, the non-registration procedure may be executed before the completion of the procedure for providing SNPN information. Specifically, each device may execute a non-registration procedure when the timer expires. Further, each device may execute a non-registration procedure if the procedure for providing SNPN information fails.

Furthermore, when the procedure for providing SNPN information is completed, the non-registration procedure may be a UE-led non-registration procedure. In other words, each device may perform a UE-led non-registration procedure when the procedure for providing SNPN information is completed.

Furthermore, if the procedure for providing SNPN information is successful, the non-registration procedure may be a UE-led non-registration procedure. In other words, each device may perform a UE-led non-registration procedure if the procedure for providing SNPN information is successful.

When the onboarding service is completed, the non-registration procedure may be a UE-led non-registration procedure. In other words, each device may perform a UE-led non-registration procedure once the onboarding service is complete.

Furthermore, if the onboarding service is successful, the non-registration procedure may be a UE-led non-registration procedure. In other words, each device may perform a UE-led non-registration procedure if the onboarding service is successful.

Furthermore, when the timer managed by the UE expires, the non-registration procedure may be a UE-led non-registration procedure. In other words, each device may perform a UE-led non-registration procedure when the timer managed by the UE expires.

On the contrary, if the procedure for providing SNPN information is not completed, the non-registration procedure may be a network-led non-registration procedure. In other words, each device may perform a network-led non-registration procedure if the procedure for providing SNPN information is not completed.

Furthermore, if the procedure for providing SNPN information fails, the non-registration procedure may be a network-led non-registration procedure. In other words, each device may perform a network-led non-registration procedure if the procedure for providing SNPN information fails.

Furthermore, if the onboarding service is not completed, the non-registration procedure may be a network-led non-registration procedure. In other words, each device may perform a network-driven non-registration procedure if the onboarding service is not completed.

Furthermore, if the onboarding service fails, the non-registration procedure may be a network-led non-registration procedure. In other words, each device may perform a network-driven non-registration procedure if the onboarding service fails.

Furthermore, when the timer managed by the network expires, the non-registration procedure may be a network-led non-registration procedure. In other words, each device may perform a network-driven non-registration procedure when the network-managed timer expires.

Furthermore, if the registration that can only be used for the onboarding service is no longer valid, the non-registration procedure may be a network-led non-registration procedure. In other words, each device may perform a network-driven non-registration procedure when registrations that are only available for onboarding services are no longer valid.

Furthermore, if the execution of the procedure during the first procedure ends in failure, each device does not have to carry out the subsequent procedures. In this case, each device may perform processing based on the information contained in the control message based on the failure to execute the procedure, or may perform processing based on the information contained in the control message. , You may complete the first procedure.

Specifically, when a registration refusal message is sent and received in the registration procedure, the UE may perform processing based on the information contained in the registration refusal message, or based on the information contained in the registration refusal message. The first procedure may be completed by carrying out the process.

Furthermore, if the execution of the procedure during the first procedure ends in failure, each device may restart the first procedure from the beginning. In this case, each device may perform processing based on the information contained in the control message based on the failure to execute the procedure, or after performing the processing based on the information contained in the control message, each device may perform the processing. You may re-execute the first procedure from the beginning.

Specifically, when a registration refusal message is sent and received in the registration procedure, the UE may perform processing based on the information contained in the registration refusal message, or based on the information contained in the registration refusal message. After performing the process, the first network selection may be re-executed.

[5. Modification example]
The program that operates on the apparatus according to one aspect of the present invention is a program that controls a Central Processing Unit (CPU) or the like to operate a computer so as to realize the functions of the embodiment according to one aspect of the present invention. Is also good. The program or the information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, Hard Disk Drive (HDD), or other storage device system.

It should be noted that the program for realizing the function of the embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. It may be realized by loading the program recorded on this recording medium into a computer system and executing it. The term "computer system" as used herein is a computer system built into a device, and includes hardware such as an operating system and peripheral devices. Further, the "computer-readable recording medium" is a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another recording medium that can be read by a computer. Is also good.

Further, each functional block or various features of the device used in the above-described embodiment can be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein can be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or others. Programmable Logic Devices, Discrete Gate or Transistor Logic, Discrete Hardware Components, or Combinations thereof. The general purpose processor may be a microprocessor, a conventional processor, a controller, a microcontroller, or a state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. Further, when an integrated circuit technology that replaces the current integrated circuit appears due to the progress of semiconductor technology, one or a plurality of aspects of the present invention can also use a new integrated circuit according to the technology.

Note that one aspect of the present invention is not limited to the above-described embodiment. In the embodiment, one example of the device has been described, but one aspect of the present invention is not limited to this, and is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device. , Kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices such as living 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 includes design changes and the like within a range not deviating from the gist of the present invention. Further, the present invention can be variously modified within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in the different embodiments are also included in the technical scope of the present invention. Will be. Further, the elements described in each of the above-described embodiments are included, and a configuration in which elements having the same effect are replaced with each other is also included.

Claims (4)

1. UE (User Equipment)
   In the first network
   Send a registration request message to the controller containing information indicating only the onboarding service.
   Receive a registration refusal message containing the first information from the control device,
   It has a transmitter / receiver unit and a control unit.
   The first information is the reason value indicating that the onboarding service is unavailable.
   Based on the first information, the control unit puts the information identifying the first network into the first list, further performs network selection, and performs network selection.
   The first list is a list containing information identifying one or more networks in which the onboarding service is unavailable.
   UE characterized by that.
2. The control unit deletes the first list based on the completion of acquisition of the SNPN information.
   The UE according to claim 1, wherein the UE is characterized in that.
3. The transmitter / receiver
   After completing the acquisition of SNPN information, execute the non-registration procedure and
   In the non-registration procedure, a non-registration acceptance message is received from the control device, and the non-registration acceptance message is received.
   The control unit deletes the first list based on the receipt of the non-registration acceptance message.
   The UE according to claim 1, wherein the UE is characterized in that.
4. It is a communication control method for UE (User Equipment).
   In the first network
   A step to send a registration request message to the controller containing information indicating only the onboarding service, and
   It has a step of receiving a registration refusal message containing the first information from the control device.
   The first information is the reason value indicating that the onboarding service is unavailable.
   Based on the first information, the UE puts information identifying the first network into the first list and further performs network selection.
   The first list is a list containing information identifying one or more networks in which the onboarding service is unavailable.
   UE communication control method characterized by that.

Images