JP2023068236A - UE (User Equipment) - Google Patents

Abstract

To provide communication means and a control method for realizing non-public network functionality in 5GS.SOLUTION: The invention provides a method and communication means for procedures for initial registration of UE and periodic or movement-based registration to realize non-public network functionality in 5GS. The invention further provides a method and communication means for a non-registration procedure initiated by the UE after the registration procedure is completed.SELECTED DRAWING: Figure 7

Description

The present invention relates to UE (User Equipment).

3GPP (3rd Generation Partnership Project), which has been carrying out standardization activities for mobile communication systems in recent years, is studying SAE (System Architecture Evolution), which is the system architecture of LTE (Long Term Evolution).

In recent years, 3GPP has also been studying next-generation communication technologies and system architecture for 5G (5th Generation) mobile communication systems. 5G System) (see Non-Patent Document 1). In 5GS, technical issues for connecting a wide variety of terminals to cellular networks are extracted and solutions are specified.

3GPP TS 24.501 V17.4.1 (2021-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17)

In 5GS (5G System), 5GCN (5G Core Network), which is a new core network, is under consideration in order to provide a wide variety of services.

Furthermore, 5G has defined network slices, which are logical networks that provide specific network functions and specific network characteristics for specific service types or groups. For example, a network slice may be a logical network provided for terminals with low-latency functions, or a logical network provided for sensor terminals used in IoT (Internet of Things). good.

Furthermore, we are considering eNPN (enhanced NPN) as a work item to enhance NPN (Non-Public Network), and to provide NPN information to UE when UE needs to connect to and register with NPN. Communication means between UE and ONN (Onboarding Network) is also under study.

However, the practical method for satisfying the above requirements is not clear.

The present invention has been made in view of the circumstances as described above, and aims to provide a method for realizing functions for eNPN in 5GS.

A UE (User Equipment) of one embodiment of the present invention, comprising a control unit and a transmission/reception unit, the UE stores a valid 5G-GUTI (5G-Globally Unique Temporary Identifier), and the UE is a SNPN (Stand-alone Non-Public Network) onboarding service, the control unit includes the valid 5G-GUTI in the 5GS mobile identity IE, and the transceiver unit includes the 5GS mobile identity IE. and transmitting a non-registration request message containing:

According to the present invention, it is possible to support SNPN onboarding services in 5GS.

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

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system to which the present invention is applied will be described.

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

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

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

Figure 2 also shows devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170, etc. The interfaces that connect these devices/functions together are described.

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

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

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

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

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

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

NG-RAN stands for Radio Access Network connecting to 5GCN, where NR or E-UTRA or both may be used. In other words, NG-RAN may be E-UTRAN.

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

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

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

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

Also, hereinafter, core network_A and/or core network_B, devices included in core network_A, and/or devices included in core network_B are the core network, or the core network device or the core network It may be called an internal device.

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

The core network (Core Network_A and/or Core Network_B) and the access network (Access Network_A and/or Access Network_B) may be different for each mobile communication operator.

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

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

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

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

In addition, devices not shown in FIG. 2 may be configured in access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A. For example, Core Network_A and/or Core Network_B and/or PDN_A and/or DN_A include an AUSF (Authentication Server Function) or an AAA (Authentication, authorization, and accounting) server (AAA-S). good too. AAA servers may be located outside the core network.

Here, AUSF is a core network device with authentication functions for 3GPP access and non-3GPP access. Specifically, it is a network function unit that receives a request for authentication for 3GPP access and/or non-3GPP access from the UE and performs an authentication procedure.

Also, the AAA server is a device with authentication and authorization and billing functions that connects with AUSF directly or indirectly through other network devices. The AAA server may be a network device within the core network. Note that the AAA server may not be included in CoreNetwork_A and/or CoreNetwork_B, but may be included in PLMN and/or SNPN. That is, the AAA server may be a core network device or a device outside the core network. For example, the AAA server may be a server device within the PLMN and/or SNPN managed by the 3rd Party.

In FIG. 2, for the sake of simplification of the drawing, each device/function is described one by one, but the mobile communication system 1 may be configured with a plurality of similar devices/functions. Specifically, the mobile communication system 1 includes a plurality of UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and/or UDM150. Such devices and functions may be configured.

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

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

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

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

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

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

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

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

The control unit_B500 is a functional unit that controls the operations and functions of the entire gNB. The control unit_B500 realizes various processes in the gNB by reading and executing various programs stored in the storage unit_B540 as necessary.

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

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

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

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

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

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

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

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

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

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

Also, in registration management, the RM state for each UE is managed. The RM state may be synchronized between the UE and AMF. The RM state includes a non-registered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered with the network, so the UE context in the AMF does not have valid location and routing information for the UE, so the AMF cannot reach the UE. Also, in the RM-REGISTERED state, the UE is registered with the network so that the UE can receive services that require registration with the network. Note that the RM state may be expressed as a 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as a 5GMM-REGISTERED state.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Note that the user plane is user data transmitted and received between the UE and the network. User plane may be transmitted and received using a PDN connection or a PDU session. Furthermore, for EPS, the user plane may be transmitted and received using the LTE-Uu interface and/or the S1-U interface and/or the S5 interface and/or the S8 interface and/or the SGi interface. Furthermore, for 5GS, the user plane may be transmitted and received via the interface between the UE and the NG RAN, and/or the N3 interface, and/or the N9 interface, and/or the N6 interface. Hereinafter, the user plane may be expressed as U-Plane.

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

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

[2.6. Other devices and/or functions and/or terms in this embodiment]
Other devices and/or functions and/or terminology and/or identification information and/or messages sent, received and stored by each device are then described.

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

SM (session management) messages (also called NAS (Non-Access-Stratum) SM messages) may be NAS messages used in procedures for SM, and are transmitted and received between UE_A10 and SMF_A230 via AMF_A240. may be a control message that In addition, SM messages include a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session modification request message, and a PDU session establishment request message. PDU session modification command message, PDU session modification complete message, PDU session modification command reject message, PDU session modification reject message. PDU session release request message, PDU session release reject message, PDU session release command message, PDU session release complete A message or the like may be included.

In addition, procedures for SM or SM procedures include PDU session establishment procedure, PDU session modification procedure, PDU session release procedure (UE-requested PDU session release procedure). may be Note that each procedure may be a procedure started from the UE, or may be a procedure started from the NW (network).

Also, an MM (Mobility management) message (also referred to as a NAS MM message) may be a NAS message used in procedures for MM, and may be a control message transmitted and received between UE_A10 and AMF_A240. Further, the MM message includes a Registration request message, a Registration accept message, a Registration reject message, a De-registration request message, a De-registration accept message. ) message, configuration update command message, configuration update complete message, Service request message, Service accept message, Service reject message, Notification ) message, Notification response message, etc. may be included.

Also, the procedures for MM or MM procedures are Registration procedure, De-registration procedure or De-registration procedure, Generic UE configuration update procedure, Authentication/Authorization procedure, A service request procedure, a paging procedure, a notification procedure may be included.

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

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

A PDN (Packet Data Network) type indicates a 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 to be performed by a communication method other than IP, rather than using IP.

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

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

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

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

A PLMN (Public land mobile network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by an operator who is a (mobile) communication carrier, and the operator can be identified by the PLMN ID. In this document, PLMN may mean PLMN ID. The PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the IMSI (International Mobile Subscriber Identity) of the UE may be the Home PLMN (HPLMN). PLMN may mean core network.

Furthermore, the UE may hold an Equivalent HPLMN list for identifying one or more EHPLMNs (Equivalent HPLMN, equivalent HPLMN) in USIM. A PLMN different from HPLMN and/or EHPLMN may be VPLMN (Visited PLMN).

A PLMN successfully registered by the UE may be an RPLMN (Registered PLMN). Each device receives from RPLMN and/or holds and/or stores an equivalent PLMN list for identifying one or more EPLMNs (Equivalent PLMN, equivalent PLMN) that can be used equivalently to RPLMNs in PLMN selection of the UE. You may

The current PLMN refers to the PLMN requested by the UE and/or the PLMN selected by the UE and/or the RPLMN and/or the PLMN allowed by the network and/or the core network device sending and receiving messages. It may be the PLMN to which it belongs.

Requesting PLMN means the destination network of the message when the UE sends the message. Specifically, it may be the PLMN selected by the UE when the UE sends the message. The requested PLMN is the PLMN requested by the UE and may be the current PLMN. Also, when the UE is in the registered state, the requested PLMN may be the registered PLMN.

NPN (Non-public network) is a network intended for non-public specifications. There are two types of NPN: SNPN (Stand-alone non-public network) and PNI-NPN (Public network integrated non-public network). SNPN and PNI-NPN may be deployed in 5GS. In this document, references to NPN may mean SNPN or PNI-NPN or both.

A SNPN (Stand-alone non-public network) is a network operated by an NPN operator that does not rely on network functionality provided by a PLMN. In other words, SNPN is a network independent from PLMN and can only be accessed by specific UEs. A SNPN may be identified by a PLMN ID and a NID (Network Identifier).

Here, the PLMN ID that identifies the SNPN need not be unique. For example, one or more PLMN IDs reserved for use in private networks may be used for NPN.

Also, SNPN (Stand-alone Non-Public Network) is a network that is identified by an SNPN ID composed of a combination of a PLMN ID and an NID (Network Identifier), and that only specific UEs are allowed to connect. SNPN may stand for core network. Here, a UE permitted to connect to SNPN may be an SNPN enabled UE.

Furthermore, the UE may hold an Equivalent SNPN list for identifying one or more ESNPNs (Equivalent SNPN, equivalent SNPN) in USIM. A SNPN different from HSNPN and/or ESNPN may be VPLMN (Visited PLMN).

The SNPN successfully registered by the UE may be a Registered SNPN (RSPNN). Each device receives and/or maintains an Equivalent SNPN list from the RSNPN for identifying one or more ESNPNs (Equivalent PLMN, Equivalent PLMN) that can be used equivalently to the RSNPN in the UE's PLMN selection or SNPN selection, and / or may be stored.

A PNI-NPN (Public network integrated non-public network) is an NPN deployed with PLMN support. In other words, it is a network that implements non-public specifications using PLMN functions.

Onboarding services in SNPN allow a MS (UE) to access a SNPN that indicates onboarding using default UE credentials.

The registration procedure for SNPN onboarding services may be Initial registration for onboarding services in SNPN. Additionally, or the registration procedure for the SNPN onboarding service may be a registration procedure for mobile registration update when the UE is registered for the SNPN onboarding service. The registration procedure for the SNPN onboarding service may be referred to as an SNPN onboarding registration.

In the registration procedure for the SNPN onboarding service, the selected SNPN may be referred to as ON-SNPN (Onboarding Standalone Non-Public Network). Furthermore, an SNPN having a subscription management function may be expressed as SO-SNPN (Subscription Owner Standalone Non-Public Network). ON-SNPN and SO-SNPN may be implemented in the same SNPN.

Onboarding and/or onboarding services are functions and/or services that allow the UE to access the onboarding network using default credentials to provision the UE with SNPN credentials for primary authentication. can mean

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

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

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

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

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

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

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

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

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

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

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

A registration area is a set of one or more TAs assigned to a UE by the AMF. Note that UE_A 10 may be able to move without transmitting/receiving a signal for tracking area update while moving within one or more TAs included in the registration area. In other words, the registration area may be a group of information indicating areas to which UE_A10 can move without performing a tracking area update procedure. A registration area may be identified by a TAI list consisting of one or more TAIs.

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

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

GUTI may be 5G-GUTI (5G-Globally Unique Temporary Identifier), 4G-GUTI (4G-Globally Unique Temporary Identifier), or other. TMSI may be 5G-TMSI (5G Temporary Mobile Subscription Identifier) or may be other.

The SUCI may be an onboarding SUCI (Subscription Concealed Identifier) or any other SUCI. In other words, the onboarding SUCI may be the SUCI. An onboarding SUCI may be derived and/or generated from an onboarding SUPI (Subscription Permanent Identifier). Also, the onboarding SUCI may be a special SUCI used for onboarding among SUCIs.

The onboarding SUPI may be derived and/or generated by the UE in SNPN access mode from default UE credentials, during the initial registration procedure for the SNPN's onboarding service and during the SNPN's onboarding service. It may be used as information identifying the UE while being registered for the service. An onboarding SUPI may be a SUPI. Also, the onboarding SUPI may be a special SUPI used for onboarding among SUPIs.

Default UE credentials are information configured in the UE to make the UE uniquely identifiable and to enable the UE to perform onboarding services verifiably and securely.

5GMM capability is information for providing the network with UE information related to interworking with 5GCN or EPS. In other words, the 5GMM capability is MM-related capability information of the UE. The 5GMM capability may be the 5GMM capability IE of 5GS.

UE security capability refers to the security algorithms used by the UE and the network and supported by the UE in N1 mode for NAS security and to NR (5G AN) and 5GCN for AS (Access-Stratum) security. Indicates the security algorithms supported between E-UTRA (E-UTRAN). The UE security capability may be a 5GS UE security capability IE (Information Element).

The UE and the network realize a secure connection using the security algorithm indicated by the UE security capability when the UE is connected to 5GC.

N1 mode is a mode of a UE allowed to access and/or connect to 5GCN via 5G AN. In other words, the N1 mode is a UE mode in which communication using the N1 interface is permitted. That is, a UE in N1 mode (UE in N1 mode) can access and/or connect to the 5GCN via the 5G AN and/or using the N1 interface.

The Last visited registered TAI is a TAI included in a registration area (registration/registered area) in which the UE has registered with the network, and is information indicating the TA last visited by the UE. The Last visited registered TAI may be the Last visited registered TAI IE of 5GS, and may be indicated by 5GS tracking area identity, which is information for identifying a TA within the area covered by 5GS.

The S1 UE network capability is information for indicating the security algorithms supported by the S1 mode UE, the Iu mode UE, and the Gb mode UE. In other words, the S1 UE security capability is information for notifying the network of the security algorithms supported by the UE when the UE accesses the core network via the 3G and/or 4G access network. Security algorithms supported in S1 mode are supported for both NAS security and AS security. The S1 UE network capability may be used by the UE and network. The S1 UE security capability may be the S1 UE security capability IE of 5GS or the UE security capability IE of EPS.

The UE and/or the network use the security algorithm indicated by the S1 UE security capability to achieve a secure connection when the UE is connected to the EPC.

The S1 mode may be a UE mode in which the UE is permitted to communicate using the S1 interface (interface between E-UTRAN (or eNB) and EPC). That is, a UE in S1 mode (UE in S1 mode) can connect to a core network via E-UTRAN.

Iu mode is a mode of UE that is allowed to connect to the core network via GERAN (GSM/GPRS Radio Access Network) or UTRAN (Universal/ UMTS (Mobile Telecommunications System) Terrestrial Radio Access Network) and Iu interface. .

Gb mode is a UE mode in which connection to the core network is permitted via a Gb interface between GERAN BSS (Base Station System) and SGSN (Service GPRS (General Packet Radio Services/System) Support Node).

Mobile station classmark 2 is information for notifying the network of the priority of mobile station (MS) equipment (UE). Mobile station classmark 2 may be Mobile station classmark 2 IE of 5GS.

Supported codecs is information for providing the network with information about audio codecs supported by the mobile (UE). Supported codecs may be the Supported codecs IE and/or the Supported codec list IE of 5GS.

SRVCC (Single Radio Voice Call Continuity) is a voice call handover technology for maintaining voice calls between LTE and 3G.

5G-SRVCC is a voice call handover technology for maintaining voice calls between 5G and 3G.

The first timer is for counting the effective time of the onboarding SUCI. The stored onboarding SUCI may be valid while the first timer is running. The first timer may be the second timer.

The first timer may be stopped upon acquisition of a new 5G-GUTI for onboarding services in SNPN and/or completion of unregistration procedures. The onboarding SUCI may be removed from the UE upon stopping or expiration of the first timer.

The second timer is a timer for counting the effective time of SUCI. The stored SUCI may be valid while the second timer is running. The second timer may be T3519 of 5GS.

The second timer may be stopped upon acquisition of a new 5G-GUTI and/or completion of the deregistration procedure. The SUCI may be removed from the UE upon stopping or expiration of the second timer.

[3. Description of procedures used in each embodiment]
Next, procedures used in each embodiment will be described. The procedures used in each embodiment include a registration procedure and a UE-initiated de-registration procedure. is included. Each procedure will be explained below.

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

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

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

A UE may initiate a registration procedure upon mobility across a TA (Tracking Area). In other words, the UE may initiate the registration procedure when moving to a TA different from the TA indicated in the TA list (TAI list or registration area) it holds. Additionally, the UE may initiate this procedure when a running backoff timer or other timer expires. Additionally, the UE may initiate a registration procedure when the context of each device needs to be updated due to PDU session disconnection or invalidation. In addition, the UE may initiate a registration procedure when there is a change in capability information and/or preferences regarding the UE's PDU session establishment. Further, the UE may initiate registration procedures periodically. Further, the UE may, based on the completion of the UE configuration update procedure, or based on the completion of the registration procedure, or based on the completion of the PDU session establishment procedure, or based on the completion of the PDU session management procedure, or in each procedure The registration procedure may be initiated based on information received from the network or based on expiry or deactivation of the backoff timer. Note that the UE is not limited to these, and can execute the registration procedure at any timing.

In addition, the procedure for transitioning from the state in which the UE is not registered in the network to the state in which it is registered is referred to as an initial registration procedure or a registration procedure for initial registration. Alternatively, the registration procedure performed while the UE is registered with the network may be referred to as a registration procedure for mobility and periodic registration update or a mobility and periodic registration update. mobility and periodic registration procedures).

In addition, the registration procedure for mobility registration update and the registration procedure for periodic registration update. registration update) and independent procedures.

New AMF 141 in FIG. 6 indicates the AMF in which UE_A10 is registered by this procedure, and old AMF 142 means the AMF in which UE was registered by the procedure before this procedure. If no AMF change occurs in this procedure, no interface between old AMF142 and new AMF141 and no procedure between old AMF142 and new AMF141 occur, and new AMF141 can be the same device as old AMF142. In this embodiment, when AMF is described, it may mean new AMF 141, old AMF 142, or both. In addition, new AMF141 and old AMF142 may be AMF140.

First, UE_A 10 starts a registration procedure by transmitting a registration request message to new AMF 141 (S600) (S602) (S604). Specifically, the UE transmits an RRC message including a registration request message to the 5G AN 120 (or gNB) (S600). Note that the registration request message is a NAS message sent and received on the N1 interface. Also, the RRC message may be a control message sent and received between the UE and the 5G AN 120 (or gNB). Also, NAS messages are processed in the NAS layer, and RRC messages are processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

Here, UE_A10 can include at least information for identifying the UE in the registration request message and/or the RRC message and transmit it. Here, the information (UE ID) for identifying the UE may be the 5GS mobile identity IE. The handling of the 5GS mobile identity IE is explained below.

The UE may include the 5G-GUTI in the 5GS mobile identity IE if the UE has a valid 5G-GUTI and if the UE registers with the PLMN.

If the UE has a valid 5G-GUTI, and if the UE registers with the SNPN, and if the UE does not perform the initial registration procedure for the onboarding service of the SNPN, the UE will set the 5G-GUTI to the 5GS mobile identity IE. may be included.

If the UE does not have a valid 5G-GUTI and a SUCI other than the onboarding SUCI is available, or if a SUCI other than the onboarding SUCI is available, the UE shall send the SUCI or a SUCI generated from it to 5GS. May be included in mobile identity IE.

The UE may include the onboarding SUCI in the 5GS mobile identity IE when the UE performs the initial registration procedure for the SNPN onboarding service or when the UE is registered with the SNPN onboarding service.

Specifically, in the initial registration procedure for the SNPN onboarding service, the UE may include the onboarding SUCI in the 5GS mobile identity IE. Additionally, the UE may include the onboarding SUCI in the 5GS mobile identity IE when the UE is registered with the SNPN onboarding service and performs registration procedures for mobility and periodic registration renewal.

Furthermore, UE_A 10 may transmit a registration request message and/or an RRC message including identification information indicating the type of this procedure.

Here, the identification information indicating the type of this procedure may be 5GS registration type IE, and this procedure is for initial registration (initial registration), or for updating registration information accompanying movement (mobility registration updating), or Information indicating that the registration process is for periodic registration updating, emergency registration, or SNPN onboarding registration. It's okay.

In other words, if this procedure is a registration procedure for initial registration, UE_A10 may send a registration request message including 5GS registration type IE indicating initial registration. If this procedure is a registration procedure for updating registration information accompanying movement, UE_A10 may transmit a registration request message including 5GS registration type IE indicating mobility registration updating. If this procedure is a registration procedure for updating registration information periodically, UE_A10 may send a registration request message including 5GS registration type IE indicating periodic registration updating. If this procedure is an emergency registration, UE_A10 may send a registration request message containing a 5GS registration type IE indicating emergency registration. If this procedure is the initial registration procedure for the SNPN onboarding service, UE_A10 may send a registration request message containing a 5GS registration type IE indicating SNPN onboarding registration.

UE_A10 may include UE capability information in the registration request message to inform the network of the functions that UE_A10 supports. Here, the UE capability information may be the 5G MM capability IE of 5GS.

Here, UE_A10 may include the 5GMM capability IE in the registration request message, except when this procedure (registration procedure) is a periodic registration renewal procedure.

UE_A10 may include the UE security capability in the registration request message to signal the security algorithm. UE_A10 may include the UE security capability IE in the registration request message, except when this procedure (registration procedure) is a periodic registration renewal procedure.

If UE_A10 remembers a valid last visited registered TAI, UE_A10 may include the Last visited registered TAI IE in the Registration Request message.

If UE_A10 supports the S1 mode, UE_A10 shall transmit the S1 UE security capability IE to inform the EPC of the security algorithm used for access, except when this procedure (registration procedure) is a periodic registration renewal procedure. MAY be included in the registration request message.

If UE_A10 supports 5G-SRVCC from NG-RAN to UTRAN, UE_A10 may include Mobile station classmark 2 IE in the Registration Request message.

If UE_A10 supports 5G-SRVCC from NG-RAN to UTRAN, UE_A10 may include the Supported codecs IE in the Registration Request message.

The registration procedure for the SNPN onboarding service may be an initial registration procedure for the SNPN onboarding service, or a registration update for movement when the UE is registered for the SNPN onboarding service. may be a registration procedure for

In addition, the case where this procedure is a registration procedure for SNPN's onboarding service means that the 5GS registration type IE sent and received during this procedure indicates the registration procedure for SNPN's onboarding service (SNPN onboarding registration). can mean

In other words, if this procedure is a registration procedure for the SNPN onboarding service, the UE may include a 5GS registration type IE in the registration request message indicating the registration procedure for the SNPN onboarding service, and send the registration request message. may be sent to the core network.

Further, the case where this procedure (registration procedure) is a registration procedure for an SNPN may mean a case where the PLMN ID and NID that identify the SNPN are transmitted and received between the core network and the UE during this procedure. In other words, when this procedure (registration procedure) is a registration procedure for SNPN, when the UE is in the SNPN access operation mode, it may mean that the UE selects the SNPN, and furthermore, if the UE is the NID It may mean that the IE is included in the registration request message.

If this procedure (registration procedure) is a registration procedure for an SNPN, and if the UE has a valid 5G-GUTI assigned by another SNPN, then the UE initiates the registration procedure for the SNPN's onboarding service. or the UE is not registered for the SNPN onboarding service, the UE shall include its 5G-GUTI in the 5GS mobile identity IE, the NID of the other SNPN in the NID IE, and the 5GS mobile identity IE and NID The IE MAY be included in the Registration Request message.

In other words, the UE may include the NID IE in the Registration Request message when the UE connects to the SNPN using the default UE credentials of another SNPN.

UE_A10 may include and transmit these identification information and/or IE in a control message different from these, for example, a control message of a layer lower than the RRC layer (eg, MAC layer, RLC layer, PDCP layer) good. By transmitting these pieces of identification information, UE_A10 may indicate that UE_A10 supports each function, may indicate a UE request, or may indicate both of them. . Furthermore, when a plurality of identification information are transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. Information indicating support for each function and information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

UE_A10 may include the above identification information and/or IE in the registration request message and/or the RRC message including the registration request message, for example, including the PLMN ID and/or AMF identification information. good. Here, the AMF identification information may be information that identifies an AMF or a set of AMFs, such as 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) or GUAMI (Globally Unique AMF Identifier). you can

Also, UE_A 10 transmits an SM message (eg, PDU session establishment request message) in the registration request message, or transmits an SM message (eg, PDU session establishment request message) together with the registration request message, The PDU session establishment procedure may be initiated during the registration procedure.

When the 5G AN 120 (or gNB) receives the RRC message including the registration request message, it selects an AMF to transfer the registration request message (S602). Note that the 5G AN 120 (or gNB) can select an AMF based on one or more identification information included in the registration request message and/or the RRC message including the registration request message.

For example, 5G AN 120 (or gNB) may select AMF based on requested NSSAI. Specifically, the 5G AN (or gNB) may select an AMF included in or with connectivity to the network slice identified by the S-NSSAI included in the requested NSSAI.

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

When the new AMF 141 receives the registration request message, it can perform the first condition determination. The first condition determination is for determining whether or not the network (or new AMF 141) accepts the UE request. The new AMF 141 executes the procedures from S606 to S612 if the first condition determination is true. On the other hand, if the first condition determination is false, the new AMF 141 may execute the procedure of S610 without executing the procedures of S606 to S608.

Alternatively, the new AMF 141 may make the first condition determination after requesting the UE context from the old AMF 142 and receiving the UE context from the old AMF 142 (S606, S608). In that case, the new AMF 141 may execute S610 and/or S612 if the first conditional determination is true. On the other hand, new AMF 141 may execute S610 if the first condition determination is false.

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

The first condition determination is the reception of the registration request message, and/or each identification information included in the registration request message, and/or subscriber information, and/or network capability information, and/or operator policy, and It may be performed based on network conditions, and/or user registration information, and/or context held by the AMF, and/or the like.

For example, the first conditional decision may be true if the network grants the UE's request, and the first conditional decision may be false if the network does not grant the UE's request. In addition, if the network to which the UE is registered and/or the device in the network supports the function requested by the UE, the first condition determination is true and does not support the function requested by the UE. , the first conditional decision may be false. Further, the first conditional determination may be true if the transmitted/received identification information is permitted, and the first conditional determination may be false if the transmitted/received identification information is not permitted.

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

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

Here, the UE context transmitted from new AMF 141 to old AMF 142 may include UE ID and allowed NSSAI. Further, the UE context may include configured NSSAI and/or rejected NSSAI, NSSAI and/or pending NSSAI, and/or fourth rejected NSSAI. In addition, the allowed NSSAI and/or configured NSSAI and/or rejected NSSAI and/or pending NSSAI and/or fourth rejected NSSAI included in the UE context and S-NSSAI included in each NSSAI are sent to the UE. may be associated with information as to whether or not the notification of has been completed.

Also, in the UE context, information of S-NSSAI requiring NSSAA procedure, and/or information indicating that the NSSAA procedure has been completed for the UE, indicating that authentication has succeeded, and/or information indicating that authentication has failed. may be included.

In addition, the UE context includes S-NSSAI information requiring management of the maximum number of UEs connected to the slice, information indicating that the maximum number of UEs has been reached, and/or reached the maximum number of UEs connected to the slice. It may include information indicating whether or not

Information about the characteristics of these S-NSSAIs may be managed as one piece of information. , whether or not management of the maximum number of UEs connected to the slice is required, and whether or not the maximum number of UEs connected to the slice has been reached may be associated and stored.

The new AMF 141 may send a control message to the UE based on the first conditional determination determination and/or based on receiving the UE context from the old AMF 142 (S610). The control message may be a registration accept message or a registration reject message.

In addition, the AMF determines whether or not to include each identification information in the control message and/or information to notify, each identification information received, and/or subscriber information, and/or network capability information, and/or operator Selections and decisions may be made based on policies and/or network conditions and/or user registration information and/or context held by the AMF.

Also, if the control message is a registration accept message, the AMF may send the registration accept message including an SM message (e.g., PDU session establishment accept message), or send an SM message (e.g., PDU session establishment accept message) together with the registration accept message. acknowledgment message) can be sent. However, this transmission method may be performed when an SM message (eg, a PDU session establishment request message) is included in the registration request message. Also, this transmission method may be performed when an SM message (eg, a PDU session establishment request message) is transmitted along with the registration request message. By performing such a transmission method, the AMF can indicate in the registration procedure that the procedure for the SM has been accepted.

In addition, AMF receives each identification information, and/or subscriber information, and/or network capability information, and/or operator policy, and/or network status, and/or user registration information, and/or Based on the context held by the AMF, etc., it may indicate that the UE's request has been accepted by sending a Registration Accept message, or indicate that the UE's request has been rejected by sending a Registration Reject message. may be indicated.

If the AMF newly assigns a 5G-GUTI to the UE, it may send the registration acceptance message including the 5G-GUTI. If this procedure (registration procedure) is a registration procedure for SNPN's onboarding service, the AMF may not include 5G-GUTI in the registration acceptance message. i.e. if the UE has sent a 5GS registration type IE indicating the registration procedure for the SNPN onboarding service (SNPN onboarding registration) and/or if the UE is registered for the SNPN onboarding service, the AMF is newly The assigned 5G-GUTI may not be included in the registration acceptance message.

Or, if this procedure (registration procedure) is a registration procedure for the SNPN onboarding service, and if the AMF newly allocates a 5G-GUTI for the SNPN onboarding service to the UE, the AMF The 5G-GUTI for onboarding service of the newly assigned SNPN may be included in the registration acceptance message.

Or, even if this procedure (registration procedure) is a registration procedure for SNPN's onboarding service, if AMF newly allocates 5G-GUTI to the UE, AMF will assign 5G-GUTI. May be included in the registration acceptance message.

The UE receives the control message via the 5G AN (gNB) (S608). If the control message is a registration acceptance message, the UE receives the registration acceptance message to recognize that the UE's request in the registration request message has been accepted and the contents of various identification information included in the registration acceptance message. can do. Or, if the control message is a registration rejection message, the UE receives the registration rejection message indicating that the UE's request in the registration request message is rejected, and the content of various identification information included in the registration rejection message. can be recognized. Also, the UE may recognize that the UE's request has been rejected if it does not receive the control message even after a predetermined period of time has elapsed after sending the registration request message.

The UE may store the received 5G-GUTI as a 5G-GUTI for SNPN's onboarding service if this procedure (registration procedure) is a registration procedure for SNPN, or if this procedure (registration procedure) is a registration procedure for SNPN. It may be stored as 5G-GUTI for use other than the boarding service.

The UE may further transmit a registration complete message to the AMF via the 5G AN (gNB) as a response message to the registration accept message if the control message is a registration accept message (S610). In addition, when the UE receives an SM message such as a PDU session establishment accept message, the UE may include an SM message such as a PDU session establishment complete message in the registration completion message, or may include the SM message. , may indicate that the procedure for SM is complete. Here, the registration completion message is a NAS message transmitted and received on the N1 interface, but is included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

AMF receives the registration complete message via 5G AN (gNB) (S612). Also, each device completes this procedure based on transmission/reception of a registration acceptance message and/or a registration completion message.

Alternatively, each device may complete the registration procedure based on sending and receiving registration rejection messages.

Each device may transition to or maintain a state in which the UE is registered with the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on transmission/reception of the registration acceptance message and/or the registration completion message. , based on the transmission/reception of the registration rejection message, the UE transitions to a state (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) on which the UE has received the registration rejection message for the current PLMN or SNPN and is not registered with the network on the access (RM_DEREGISTERED state or 5GMM-DEREGISTERED state); You can maintain. Also, transition to each state of each device may be performed based on transmission/reception of a registration completion message or completion of a registration procedure.

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

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

Further, the UE may delete one or more stored NSSAIs based on completion of the registration procedure. Specifically, UE_A10 stores the first The rejected NSSAI and/or the third rejected NSSAI and/or the fourth rejected NSSAI may be deleted.

Further, UE_A10 may, based on the completion of this procedure, if UE_A10 transitions to the non-registered state on certain accesses (3GPP access and non-3GPP access) to the current PLMN, or UE_A10 may perform the registration procedure in a new registration area. is successful, or if UE_A10 has performed a registration procedure in a new registration area resulting in a transition to a non-registered state or a registered state on an access, UE_A10 shall set the current PLMN, the current registration area, and/or or delete the second rejected NSSAI associated with that access type.

Further, each device may initiate SM procedures by sending and receiving SM messages based on the UE transitioning to or maintaining a network-registered state (RM_REGISTERED state or 5GMM-REGISTERED state).

[3.2. UE-initiated non-registration procedure]
Next, the UE-initiated de-registration procedure (UE-initiated de-registration procedure) will be described using FIG. Hereinafter, this procedure refers to a UE-initiated non-registration procedure. The UE-initiated non-registration procedure is UE-initiated by Access Network_A, and/or Core Network_A, and/or Access Network_B, and/or Core Network_B, and/or DN, and / Or a procedure for deregistration to the PDN. This procedure may be a procedure for mobility management initiated by the UE with respect to the network.

This procedure may be classified into a non-registration procedure by switching off the UE and a non-registration procedure otherwise. Furthermore, this procedure may be performed for each access type (3GPP access or non-3GPP access) or for both access types (3GPP access and non-3GPP access).

UE_A10 may initiate this procedure based on UE_A10 being powered off or the USIM being removed from UE_A10.

Also, based on other UE requests, UE_A 10 may initiate and perform de-registration procedures for appropriate access types.

If UE_A10 is registered with SNPN's onboarding service, UE_A10 may initiate this procedure when it has completed setting up one or more entries in the "list of subscriber data."

In other words, if UE_A10 is registered for SNPN's onboarding service, UE_A10 will use this procedure to initiate the non-registration procedure for SNPN's onboarding service if subscriber information acquisition is complete. You can When the acquisition of subscriber information is completed,
UE_A10 may send a DEREGISTRATION REQUEST message to AMF (S700). The de-registration request message may include the De-registration type IE and/or the generated 5GS mobile identity IE.

The De-registration type IE may include information indicating that this procedure is due to power off of the UE (Switch off) or information indicating otherwise (Normal de-registration).

Furthermore, the De-registration type IE may include information indicating the access type (3GPP access, non-3GPP access, or both).

The 5GS mobile identity IE included in the non-registration request message may be generated as follows.

UE_A10 may include a valid 5G-GUTI in the 5GS mobile identity IE if UE_A10 stores a valid 5G-GUTI and UE_A10 is not registered with SNPN's onboarding service.

If UE_A10 does not remember a valid 5G-GUTI, and if a SUCI other than the onboarding SUCI is available, and if UE_A10 is not registered with SNPN's onboarding service, UE_A10 will use that SUCI other than the onboarding SUCI. may be included in the 5GS mobile identity IE.

Alternatively, if UE_A10 does not store a valid 5G-GUTI and UE_A10 is not registered with SNPN's onboarding service, UE_A10 may include an onboarding SUCI in the 5GS mobile identity IE as follows.

If the second timer is not running, UE_A 10 generates a new SUCI other than the onboarding SUCI and sends a non-registration request message including the 5GS mobile identity IE including the new non-onboarding SUCI SUCI, A second timer may be started and the value of the SUCI other than the new onboarding SUCI may be stored.

If the second timer is running, UE_A 10 may send a non-registration request message including a 5GS mobile identity IE including SUCIs other than the onboarding SUCI to store.

If UE_A10 is registered with SNPN's onboarding service and if the onboarding SUCI is available, UE_A10 may include the onboarding SUCI in the 5GS mobile identity IE.

Alternatively, if UE_A10 is registered with SNPN's onboarding service, UE_A10 may include the onboarding SUCI in the 5GS mobile identity IE as follows:

If the first timer is not running, UE_A 10 generates a new onboarding SUCI, sends a non-registration request message containing the 5GS mobile identity IE containing the new onboarding SUCI, and starts the first timer. and store the new Onboarding SUCI value.

If the first timer is running, UE_A10 may send a non-registration request message including the 5GS mobile identity IE including the onboarding SUCI to store.

Note that UE_A10 storing a valid 5G-GUTI may mean that the 5G-GUTI stored by UE_A10 is available. Similarly, UE_A10 storing a valid SUCI may mean that the SUCI stored by UE_A10 is available. Similarly, UE_A10 storing a valid SUPI may mean that the SUPI stored by UE_A10 is available.

Upon receiving the deregistration request message, the AMF may send a DEREGISTRATION ACCEPT message to the UE if the De-registration type IE does not indicate power off (S702).

If the UE receives the non-registration accept message, the UE stops the first timer and/or the second timer if the first timer and/or the second timer is running, and stores the SUCI and / Or you may remove the onboarding SUCI.

If this procedure is a de-registration procedure by powering off the UE, each device may complete this procedure based on the transmission and reception of the de-registration request message. On the other hand, if the procedure is not a power-off deregistration procedure, each device may complete the procedure based on sending and receiving a deregistration accept message.

It should be noted that each device, based on the transmission and reception of the non-registration request message and/or the non-registration accept message, the UE has received a registration rejection message for the current PLMN or SNPN and is not registered in the network on the access ( RM_DEREGISTERED state or 5GMM-DEREGISTERED state). Also, the transition to each state of each device may be performed based on the completion of this procedure.

[4. Embodiments of the present invention]
Embodiments of the present invention may be a combination of one or more of the procedures described in Section 3. For example, in this embodiment, based on the completion of the initial registration procedure described in Section 3.1, the UE transitions to the registered state, and the registration procedure for movement and periodic registration update in Section 3.1 may be performed. .

Also, after transitioning to the registered state based on the completion of the initial registration procedure described in Chapter 3.1, the non-registration procedure described in Chapter 3.2 may be implemented.

An example of a specific embodiment of the present invention will be described below.

[4.1. First embodiment]
A first embodiment (hereinafter referred to as the present embodiment) will be described below.

In the following, the first embodiment describes a form in which the UE initiates a non-registration procedure when the UE is registered for the SNPN onboarding service.

First, the UE transitions to the registered state for the SNPN onboarding service through a registration procedure (see Section 3.1 Registration Procedure).

Then, when the UE has acquired and/or prepared credentials (subscriber information) through the SNPN onboarding service, it may initiate a UE-initiated non-registration procedure (see UE-initiated non-registration in section 3.2). (see registration procedure).

Specifically, if UE_A10 is registered with SNPN's onboarding service, and if the onboarding SUCI is available, UE_A10 may include the onboarding SUCI in the 5GS mobile identity IE.

Alternatively, if UE_A10 is registered with the SNPN onboarding service and the first timer is not running, UE_A10 generates an onboarding SUCI, and the 5GS mobile identity IE including the generated onboarding SUCI to start a first timer and store the new onboarding SUCI value.

On the other hand, if UE_A10 is registered with the SNPN onboarding service and the first timer is running, UE_A10 sends a non-registration request message containing a 5GS mobile identity IE containing an onboarding SUCI to store can be sent.

The de-registration request message includes a De-registration type IE, and the De-registration type IE is information (Switch off) indicating that this procedure is due to power off of the UE or other information. It may be information (Normal de-registration) indicating that.

Furthermore, the De-registration type IE may indicate the access type targeted by this procedure (non-registration request procedure), and may indicate 3GPP access or non-3GPP access or both.

The AMF sends a non-registration accept message to the UE based on receiving the non-registration request message from the UE. The UE may stop the first timer if it is running and delete the stored onboarding SUCI upon receipt of the non-registration accept message.

As described above, each device may execute the non-registration procedure after acquiring the qualification information (subscriber information) by the SNPN onboarding service.

[4.2. Second embodiment]
A second embodiment (hereinafter referred to as the present embodiment) will be described below.

Hereinafter, in the second embodiment, a form in which the UE initiates a non-registration procedure when not registered for the SNPN onboarding service will be described.

First, the UE transitions to a state registered with the PLMN through the registration procedure (see registration procedure in section 3.1). The UE may transition to a state with a valid 5G-GUTI through a registration procedure.

Then, when the UE is powered off, it may initiate a UE-initiated de-registration procedure (see UE-initiated de-registration procedure in section 3.2).

Specifically, UE_A10 may include a valid 5G-GUTI in the 5GS mobile identity IE if UE_A10 stores a valid 5G-GUTI and UE_A10 is not registered with SNPN's onboarding service.

or if UE_A10 does not remember a valid 5G-GUTI and if SUCIs other than the onboarding SUCI are available, and if UE_A10 is not registered with SNPN's onboarding service, UE_A10 will use a SUCI other than the onboarding SUCI. The SUCI may be included in the 5GS mobile identity IE.

Or, if UE_A10 does not remember a valid 5G-GUTI, and UE_A10 is not registered with SNPN's onboarding service, and if the second timer is not running, UE_A10 will receive a new non-onboarding SUCI. Generate a SUCI, send a non-registration request message containing the 5GS mobile identity IE containing the new non-onboarding SUCI SUCI, start the first timer, and store the value of the new non-onboarding SUCI SUCI. you can

On the other hand, if UE_A10 does not store a valid 5G-GUTI, and if UE_A10 is not registered with the SNPN onboarding service, and if a second timer is running, UE_A10 will store other than the onboarding SUCI to store. may send a non-registration request message containing the 5GS mobile identity IE containing the SUCI of

The de-registration request message includes a De-registration type IE, and the De-registration type IE is information (Switch off) indicating that this procedure is due to power off of the UE or other information. It may be information (Normal de-registration) indicating that.

Furthermore, the De-registration type IE may indicate the access type targeted by this procedure (non-registration request procedure), and may indicate 3GPP access or non-3GPP access or both.

The AMF sends a non-registration accept message to the UE based on receiving the non-registration request message from the UE. The UE may stop the second timer if it is running and delete the stored SUCI upon receipt of the non-registration accept message.

Thus, each device may perform a UE-initiated unregistration procedure if it is not registered with the SNPN's onboarding service.

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

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

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

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

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

1 Mobile communication system
10 UE_A
30 PGW-U
32PGW-C
35 SGW
40 MMEs
45 eNB
50 HSS
60 PCRF
80 Access Network_A (E-UTRAN)
90 Core Network_A
120 Access Network_B (5G AN)
122 gNB
130 UPF
132 SMF
140AMF
150UDM
160PCF
190 Core Network_B

Claims (2)

UE (User Equipment),
comprising a control unit and a transmitting/receiving unit,
If the UE stores a valid 5G-GUTI (5G-Globally Unique Temporary Identifier) and the UE is not registered for a Stand-alone Non-Public Network (SNPN) onboarding service,
The control unit includes the valid 5G-GUTI in the 5GS mobile identity IE,
The transceiver unit transmits a non-registration request message containing the 5GS mobile identity IE.
A UE characterized by: If the UE does not store a valid 5G-GUTI and if a first SUCI other than an onboarding SUCI (Subscription Concealed Identifier) is available, if the UE is not registered with the SNPN onboarding service,
The control unit includes the first SUCI in the 5GS mobile identity IE,
The transmitting/receiving unit transmits the non-registration request message including the 5GS mobile identity IE.
The UE according to claim 1, characterized by:

Images