WO2022107781A1 - User equipment (ue) - Google Patents

Abstract

The purpose of the present invention is to clarify a method of using non-3GPP access to connect to a SNPN service, a method of connecting to a PLMN service via a SNPN connected using non-3GPP access, and a method of connecting to a SNPN service via a PLMN connected using non-3GPP access. This UE is provided with a control unit which, in the case of connecting to the SNPN service using 3GPP access or using non-3GPP access via PLMN, does not operate in SNPN access mode in the case of non-3GPP access, and does operate in SNPN access mode in the case of 3GPP access.

Description

UE (User Equipment)

The present invention relates to UE (User Equipment). This application claims priority based on Japanese Patent Application No. 2020-193360 filed in Japan on November 20, 2020, the contents of which are incorporated herein by reference.

In 3GPP (3rd Generation Partnership Project), the system architecture of 5GS (5G System), which is a 5th generation (5G) mobile communication system, is being studied, and discussions are being held to support new procedures and new functions. (See Non-Patent Documents 1 to 3). The concept of NPN (Non-Public Network) was introduced in the Release 16 standard, and its functional expansion is discussed in Release 17 (see Non-Patent Document 4).

In Non-Patent Document 4, the support for non-3GPP access to SNPN (Stand-alone NPN), which is a form of NPN, was planned to be discussed, but it has not been discussed yet. Furthermore, specifically, a method of connecting to the SNPN service using non-3GPP access, a method of connecting to the PLMN service via the SNPN connected using non-3GPP access, and a method of connecting to the PLMN service using non-3GPP access. Nothing is disclosed about how to connect to the SNPN service via the connected PLMN.

One aspect of the present invention has been made in view of the above circumstances, and is a method of connecting to an SNPN service using non-3GPP access or PLMN via a SNPN connected using non-3GPP access. The purpose is to clarify how to connect to the service and how to connect to the SNPN service via PLMN connected using non-3GPP access.

The UE of one aspect of the present invention is a UE (User Equipment) provided with a control unit, and is an SNPN (Stand-alone) using 3GPP access via PLMN (Public Land Mobile Network) using non-3GPP access. When connecting to a Non-Public Network) service, the control unit is characterized in that it does not operate in the SNPN access mode on non-3GPP access and operates in the SNPN access mode on 3GPP access.

According to one aspect of the present invention, a method of connecting to the SNPN service using non-3GPP access, a method of connecting to the PLMN service via the SNPN connected using non-3GPP access, and a non-3GPP access. It is possible to provide a method of connecting to the SNPN service via the PLMN connected using it.

It is a figure explaining the outline of the mobile communication system 1. It is a figure explaining the detailed structure of the mobile communication system 1. It is a figure explaining the outline of the mobile communication system 2. It is a figure explaining the detailed structure of the mobile communication system 2. It is a figure explaining the detailed structure of the mobile communication system 2. It is a figure explaining the outline of the mobile communication system 3. It is a figure explaining the detailed structure of the mobile communication system 3. It is a figure explaining the detailed structure of the mobile communication system 3. It is a figure explaining the apparatus configuration of UE. It is a figure explaining the structure of the access network apparatus (gNB) in 5GS. It is a figure explaining the structure of the core network apparatus (AMF / SMF / UPF / N3IWF / NF) in 5GS. It is a figure explaining the registration procedure. It is a figure explaining the PDU session establishment procedure.

Hereinafter, the best mode for carrying out one aspect of 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 one aspect of the present invention is applied will be described.

[1. System overview]
Here, each mobile communication system will be described.

First, FIG. 1 is a diagram for explaining the outline of the mobile communication system 1, and FIG. 2 is a diagram for explaining the detailed configuration thereof. Further, FIG. 3 is a diagram for explaining the outline of the mobile communication system 2, and FIGS. 4 and 5 are diagrams for explaining the detailed configuration thereof. Further, FIG. 6 is a diagram for explaining the outline of the mobile communication system 3, and FIGS. 7 and 8 are diagrams for explaining the detailed configuration thereof.

FIG. 1 shows communication system 1 composed of UE (User Equipment) _10, access network _100, core network _200, and DN (Data Network) _250.

Here, in the following, these symbols may be omitted. Further, the access network_100 in FIG. 1 may be 3GPP access or non-3GPP access, but here, it is assumed that it is non-3GPP access. Communication system 1 in FIG. 1 assumes that the UE connects directly to an SNPN service (hereinafter, also referred to as a service provided by SNPN, or SNPN) via non-3GPP access. In other words, when connecting directly to the SNPN service, the UE executes the registration procedure for the core network_200 via non-3GPP access (access network_100) in the SNPN and becomes registered. After that, the PDU session established by executing the PDU session establishment procedure (hereinafter, also referred to as the first PDU session) becomes communicable with DN_250. At this time, it can be said that the UE is connected to the SNPN service. Further, the access network_100 and / or the core network_200 and / or the DN_250 can be said to be networks constituting the SNPN. Further, it can be said that the device / network functions included in the access network_100, the core network_200, and the DN_250 are the device / network functions constituting the SNPN. Communication system 1 is such a communication system.

In addition, Fig. 2 shows the device / network functions such as UE_10, AMF_210, SMF_220, UPF_230, N3IWF_240, DN_250, and the interface for connecting them to each other.

Here, in the following, these symbols may be omitted. AMF, SMF, UPF, and N3IWF may be included in the core network_200. Also, although not shown in FIG. 2, a base station appliance or access point is installed between the UE and the N3IWF. The base station device or access point may be included in the access network.

Further, FIG. 3 shows a communication system 2 composed of UE_10, access network_102, core network_202, DN_252, core network_200, and DN_250.

Here, in the following, these symbols may be omitted. Further, the access network_102 in FIG. 3 may be 3GPP access or non-3GPP access, but here, it is assumed that it is non-3GPP access. Communication system 2 in FIG. 3 assumes that the UE connects to the SNPN service via the PLMN. Specifically, in the communication system 2 of FIG. 3, the UE first connects to the PLMN service (hereinafter, also referred to as a service provided by PLMN, or PLMN) via non-3GPP access, and then Furthermore, it is assumed to connect to the SNPN service via 3GPP access or non-3GPP access. More specifically, first, in PLMN, the UE executes a registration procedure for the core network_202 via non-3GPP access (access network_102) and enters the registration state, and then PDUs. Using the PDU session established by executing the session establishment procedure (hereinafter, also referred to as the second PDU session), it becomes possible to communicate with DN_252. At this time, it can be said that the UE is connected to the PLMN service. Here, when the UE connects to the SNPN service via PLMN, the parts of access network_102, core network_202, and DN_252 that make up PLMN, and / or the second PDU session, and / Alternatively, the user plane resources (communication resources for sending and receiving user data) constituting the second PDU session may be treated as 3GPP access or non-3GPP access (access network_100). Then, when the UE further connects to the SNPN service via PLMN, after executing the registration procedure for the core network_200 via its 3GPP access or non-3GPP access and entering the registration state. , The PDU session established by executing the PDU session establishment procedure (hereinafter, also referred to as the third PDU session) becomes communicable with DN_250. At this time, it can be said that the UE is connected to the SNPN service via the PLMN. Further, the access network_102 and / or the core network_202 and / or the DN_252 can be said to be networks constituting the PLMN. Further, it can be said that the device / network functions included in the access network_102, the core network_202, and the DN_252 are the device / network functions constituting the PLMN. It also accesses the access network_102, core network_202, and DN_252 parts that make up PLMN, and / or the user plane resources that make up the second PDU session and / or the second PDU session. When treated as network_100, access network_100 and / or core network_200 and / or DN_250 are networks that make up SNPN, or networks that make up SNPN through PLMN, or SNPN services via PLMN. It can be said that it is a network that constitutes the SNPN when connecting to. The device / network functions included in the access network_100, core network_200, and DN_250 are the device / network function constituting the SNPN, the device / network function constituting the SNPN via PLMN, or via PLMN. It can be said that it is a device / network function that constitutes the SNPN when connecting to the SNPN service. Communication system 2 is such a communication system.

Further, the third PDU session may be said to be a PDU session using the second PDU session, or may be said to be a PDU session included in the second PDU session. In this way, it can be said that the third PDU session is a PDU session different from a normal PDU session (first PDU session or second PDU session).

The access network_100 shown by the broken line in Fig. 3 is not used in communication system 2. The access network_100 is shown by a broken line in order to compare communication system 2 with communication system 1.

Also shown in Figure 4 are the access network_102, core network_202, and DN_252 parts that make up the PLMN, and / or the user planes that make up the second PDU session and / or the second PDU session. It is a detailed configuration of communication system 2 when the resource is treated as non-3GPP access (access network_100). FIG. 4 shows devices / network functions such as UE_10, AMF_210, AMF_212, SMF_220, SMF_222, UPF_230, UPF_232, N3IWF_240, N3IWF_242, DN_250, DN_252, and interfaces for connecting them to each other.

Here, in the following, these symbols may be omitted. AMF_212, SMF_222, UPF_232, and N3IWF_242 may be included in the core network_202. In addition, AMF_210, SMF_220, UPF_230, and N3IWF_240 may be included in the core network_200. Also, although not shown in FIG. 4, a base station appliance or access point is installed between the UE and N3IWF_242. The base station device or access point may be included in access network_102.

Also shown in Figure 5 are the access network_102, core network_202, and DN_252 parts that make up the PLMN, and / or the user plane that makes up the second PDU session and / or the second PDU session. It is a detailed configuration of communication system 2 when the resource is treated as 3GPP access (access network_100). FIG. 5 describes device / network functions such as UE_10, AMF_210, AMF_212, SMF_220, SMF_222, UPF_230, UPF_232, N3IWF_242, DN_250, DN_252, NF_260, and interfaces for connecting them to each other.

Here, in the following, these symbols may be omitted. AMF_212, SMF_222, UPF_232, and N3IWF_242 may be included in the core network_202. In addition, AMF_210, SMF_220, UPF_230, and NF_260 may be included in the core network_200. Also, although not shown in FIG. 5, a base station device or access point is installed between the UE and N3IWF_242. The base station device or access point may be included in access network_102.

Here, the NF_260 may be a gateway (hereinafter, also referred to as an end point) installed in the SNPN for the UE to connect to the SNPN service via the PLMN.

Further, NF_260 may be a device / network function installed in the core network_200 of SNPN. In this case, NF_260 may be an existing device / network function (for example, AMF, SMF, UPF, etc.) installed in the core network_200, or may be a new device / network function.

Further, NF_260 may be a device / function installed in the access network_100 of SNPN. In this case, the base station device installed in the access network_100 may have this function.

Further, the NF_260 may have a function of transferring control information and user data (non-control information) to an appropriate device / network function, for example. Specifically, the NF_260 transfers the control information and user data received from the DN_252 to the device / network function constituting the SNPN by using the second PDU session established between the UE and the DN_252. It may have a function of transferring control information and user data received from the function and / or the device / network function constituting the SNPN to DN_252 or a second PDU session. More specifically, the NF_260 uses the second PDU session to send an MM message (eg, registration request message, etc.) and / or SM message (eg, PDU session establishment request message, etc.) to the SNPN sent from the UE. , MM message received from the device / network function (eg, AMF or SMF) that constitutes the SNPN and / or the device / network function that constitutes the SNPN (eg, AMF or SMF) when received from DN_252. It may have a function of transferring (for example, a registration acceptance message, etc.) and / or an SM message (for example, a PDU session establishment acceptance message, etc.) to DN_252 or a second PDU session.

In addition, NF_260 performs encryption processing and encryption processing (ciphering) processing for MM messages (for example, registration request message etc.) and / or SM messages (for example, PDU session establishment request message etc.) for SNPN transmitted from UE received from DN_252. / Or the function to execute the integrity protection process, and / or the MM message (eg, registration acceptance message, etc.) and / or SM message received from the device / network function (for example, AMF or SMF) that constitutes the SNPN. It may have a function to perform encryption processing and / or integrity protection processing (for example, PDU session establishment acceptance message, etc.).

Further, the NF_260 may have a function of determining whether or not the UE connects to the SNPN service via the PLMN.

Further, the NF_260 may have a function of storing the third PDU session and the second PDU session in association with each other when the third PDU session is established between the UE and the DN_250. Specifically, the NF_260 has the ability to transfer user data sent from the UE to DN_250 when a third PDU session is established, and / or receive user data from DN_250. If so, it may have a function to transfer to DN_252.

Further, FIG. 6 shows a communication system 3 composed of UE_10, access network_100, core network_200, DN_250, core network_202, and DN_252.

Here, in the following, these symbols may be omitted. Further, the access network_100 in FIG. 6 may be 3GPP access or non-3GPP access, but here, it is assumed that it is non-3GPP access. Communication system 3 in FIG. 6 assumes that the UE connects to the PLMN service via the SNPN. Specifically, in the communication system 3 of FIG. 6, the UE first connects to the SNPN service via non-3GPP access, and then connects to the PLMN service via 3GPP access or non-3GPP access. It is supposed to be done. More specifically, first, the UE performs a registration procedure for the core network_200 via non-3GPP access (access network_100) in the SNPN, and then enters the registration state, and then the PDU. Using the PDU session established by executing the session establishment procedure (hereinafter, also referred to as the fourth PDU session), it becomes possible to communicate with DN_250. Here, the fourth PDU session may be the same as the first PDU session described above. At this time, it can be said that the UE is connected to the SNPN service. Here, when the UE connects to the PLMN service via the SNPN, the parts of the access network_100, core network_200, and DN_250 that make up the SNPN, and / or the fourth PDU session, and / Alternatively, the user plane resources that make up the fourth PDU session may be treated as 3GPP access or non-3GPP access (access network_102). Then, when the UE further connects to the PLMN service via the SNPN, after executing the registration procedure for the core network_202 via its 3GPP access or non-3GPP access and entering the registration state. , The PDU session established by executing the PDU session establishment procedure (hereinafter, also referred to as the fifth PDU session) becomes communicable with DN_252. At this time, it can be said that the UE is connected to the PLMN service via the SNPN. Further, the access network_100 and / or the core network_200 and / or the DN_250 can be said to be networks constituting the SNPN. Further, it can be said that the device / network functions included in the access network_100, the core network_200, and the DN_250 are the device / network functions constituting the SNPN. It also accesses the access network_100, core network_200, and DN_250 parts that make up the SNPN, and / or the user plane resources that make up the fourth PDU session and / or the fourth PDU session. When treated as network_102, access network_102 and / or core network_202 and / or DN_252 are networks that make up PLMN, or networks that make up PLMN through SNPN, or PLMN services via SNPN. It can be said that it is a network that constitutes PLMN when connecting to. The device / network function included in the access network_102, core network_202, and DN_252 is the device / network function constituting the PLMN, the device / network function constituting the PLMN via the SNPN, or via the SNPN. It can be said that it is a device / network function that constitutes PLMN when connecting to the PLMN service. Communication system 3 is such a communication system.

Further, the fifth PDU session may be said to be a PDU session using the fourth PDU session, or may be said to be a PDU session included in the fourth PDU session. In this way, it can be said that the fifth PDU session is a PDU session different from the normal PDU session (fourth PDU session).

Note that the access network_102 shown by the broken line in Fig. 6 is not used in communication system 3. The access network_102 is described by a broken line in order to compare the communication system 3 with the communication system 2.

Also shown in Figure 7 are the access network_100, core network_200, and DN_250 parts that make up the SNPN, and / or the user plane that makes up the fourth PDU session and / or the fourth PDU session. This is the detailed configuration of communication system 3 when the resource is treated as non-3GPP access (access network_102). FIG. 7 describes devices / network functions such as UE_10, AMF_210, AMF_212, SMF_220, SMF_222, UPF_230, UPF_232, N3IWF_240, N3IWF_242, DN_250, DN_252, and interfaces for connecting them to each other.

Here, in the following, these symbols may be omitted. AMF_210, SMF_220, UPF_230, and N3IWF_240 may be included in the core network_200. In addition, AMF_212, SMF_222, UPF_232, and N3IWF_242 may be included in the core network_202. Also, although not shown in FIG. 7, a base station device or access point is installed between the UE and N3IWF_240. The base station device or access point may be included in access network_100.

Also shown in Figure 8 are the access network_100, core network_200, and DN_250 parts that make up the SNPN, and / or the user plane that makes up the fourth PDU session and / or the fourth PDU session. It is a detailed configuration of the communication system 3 when the resource is treated as 3GPP access (access network_102). FIG. 8 describes device / network functions such as UE_10, AMF_210, AMF_212, SMF_220, SMF_222, UPF_230, UPF_232, N3IWF_240, DN_250, DN_252, NF_262, and interfaces for connecting them to each other.

Here, in the following, these symbols may be omitted. AMF_210, SMF_220, UPF_230, and N3IWF_240 may be included in the core network_200. In addition, AMF_212, SMF_222, UPF_232, and NF_262 may be included in the core network_202. Also, although not shown in FIG. 8, a base station device or access point is installed between the UE and N3IWF_240. The base station device or access point may be included in access network_100.

Here, the NF_262 may be a gateway (hereinafter, also referred to as an end point) installed in the PLMN for the UE to connect to the PLMN service via the SNPN.

NF_262 may be a device / network function installed in PLMN's core network_202. In this case, NF_262 may be an existing device / network function (for example, AMF, SMF, UPF, etc.) installed in the core network_202, or may be a new device / network function.

Further, NF_262 may be a device / function installed in the access network_102 of PLMN. In this case, the base station device installed in the access network_102 may have this function.

Further, the NF_262 may have a function of transferring control information and user data (non-control information) to an appropriate device / network function, for example. Specifically, NF_262 uses the fourth PDU session established between the UE and DN_250 to transfer the control information and user data received from DN_250 to the device / network functions that make up PLMN. It may have a function of transferring control information and user data received from a function and / or a device / network function constituting PLMN to DN_250 or a fourth PDU session. More specifically, NF_262 uses the fourth PDU session to send MM messages (eg registration request messages, etc.) and / or SM messages (eg, PDU session establishment request messages, etc.) to the PLMN sent from the UE. , MM message received from the device / network function (eg, AMF or SMF) that constitutes PLMN, and / or the device / network function that constitutes PLMN (eg, AMF or SMF) when received from DN_250. It may have a function of transferring (for example, a registration acceptance message, etc.) and / or an SM message (for example, a PDU session establishment acceptance message, etc.) to DN_250 or a fourth PDU session.

In addition, NF_262 is encrypted (ciphering) processing for MM messages (for example, registration request message etc.) and / or SM messages (for example, PDU session establishment request message etc.) for PLMN transmitted from UE received from DN_250. / Or the function to execute the integrity protection process, and / or the MM message (eg, registration acceptance message, etc.) and / or SM message received from the device / network function (for example, AMF or SMF) that constitutes PLMN. It may have a function to perform encryption processing and / or integrity protection processing (for example, PDU session establishment acceptance message, etc.).

Further, the NF_262 may have a function of determining whether or not the UE connects to the PLMN service via the SNPN.

Further, NF_262 may have a function of storing the fifth PDU session and the fourth PDU session in association with each other when the fifth PDU session is established between the UE and DN_252. Specifically, the NF_262 has the ability to transfer user data sent from the UE to DN_252 when a fifth PDU session is established, and / or receive user data from DN_252. If so, it may have a function to transfer to DN_250.

Further, 5GS (5G System), which is a 5G system, is configured to include a UE, an access network, and a core network, but may further include a DN.

The UE can also connect to network services via 3GPP access (3GPP access network, also referred to as 3GPPAN) and / or non-3GPP access (non-3GPP access network, also referred to as non-3GPPAN). It is a device. Further, the UE may be a terminal device capable of wireless communication such as a mobile phone or a smartphone, and may be a terminal device capable of connecting to EPS (Evolved Packet System) which is a 4G system and 5GS. In addition, the UE may be provided with UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). The UE may be expressed as a user device or a terminal device.

Further, the access network may be referred to as a 5G access network (5GAN). 5GAN is composed of NG-RAN (NGRadioAccessNetwork) and / or non-3GPP access network (non-3GPPAN).

In addition, one or more base station devices are installed in NG-RAN. The base station device may be, for example, gNB (gNodeB). The gNB is a node that provides the NR (New Radio) user plane and the control plane to the UE, and is a node that connects to the 5GC via an NG interface (including an N2 interface or an N3 interface). That is, gNB is a base station device newly designed for 5GS and has a different function from the base station device (eNB) used in EPS. When there are a plurality of gNBs, each gNB is connected to each other by, for example, an Xn interface.

Also, NG-RAN may be referred to as 3GPP access. In addition, non-3GPP AN may be referred to as non-3GPP access. In addition, the nodes arranged in the access network may be collectively referred to as NG-RAN nodes.

Further, the device included in the access network and / or the device included in the access network may be referred to as an access network device.

In addition, base station equipment or access points are located in the access network.

Also, the core network is compatible with 5GC (5G Core Network). For example, AMF, UPF, SMF, PCF, N3IWF and the like are arranged in 5GC. Here, 5GC may be expressed as 5GCN.

Further, in the following, the core network and / or the device included in the core network may be referred to as a core network device.

The core network may be an IP mobile communication network operated by a mobile network operator (MNO) that connects an access network and a DN, or a mobile that operates and manages a mobile communication system. It may be a core network for a communication operator, or it may be a core network for a virtual mobile communication operator such as MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler) or a virtual mobile communication service provider.

Further, the DN may be a DN that provides a communication service to the UE. Further, the DN may be configured as a packet data service network or may be configured for each service. Further, the DN may include a connected communication terminal. Therefore, connecting to the DN may be connecting to a communication terminal or a server device arranged in the DN. Further, sending and receiving user data to and from the DN may be sending and receiving user data to and from a communication terminal or server device arranged in the DN.

In the following, at least a part of an access network, a core network, and a DN may be referred to as a network or a network device. Further, one or more devices included in at least a part of an access network, a core network, and a DN may be referred to as a network or a network device. That is, a network or network device sending and receiving messages and / or performing procedures means that at least a portion of the access network, core network, DN, or one or more devices contained therein send and receive messages. And / or perform the procedure.

Also, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the DN via the access network and the core network. That is, the UE can send / receive (communicate) user data with the DN. Further, when the UE sends and receives user data, not only IP (Internet Protocol) communication but also non-IP communication may be used.

Here, IP communication is data communication using IP, and data is transmitted and received by IP packets. An IP packet is composed of an IP header and a payload part. The payload section may include devices / functions included in EPS and data transmitted / received by devices / functions included in 5GS.

In addition, non-IP communication is data communication that does not use IP, and data is sent and received in a format different from the structure of IP packets. For example, non-IP communication may be data communication realized by sending and receiving application data to which an IP header is not added, or a UE may add another header such as a Mac header or an Ethernet (registered trademark) frame header. User data to be sent and received may be sent and received.

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

In addition, each storage unit (storage unit_340, storage unit_540, storage unit_740) in each device / function appearing below is, for example, a semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive). ) Etc. In addition, each storage unit has not only the information originally set from the shipping stage, but also devices / functions other than its own device / function (for example, UE and / or access network device, and / or core network device, and /. Or, various information transmitted / received to / from PDN and / or DN) can be stored. In addition, each storage unit can store identification information, control information, flags, parameters, and the like included in control messages transmitted and received in various communication procedures described later. Further, each storage unit may store such information for each UE.

[2.1. UE device configuration]
First, an example of a device configuration of UE (User Equipment) will be described with reference to FIG. The UE is composed of a control unit_300, an antenna_310, a transmission / reception unit_320, and a storage unit_340. The control unit _300, the transmission / reception unit _320, and the storage unit _340 are connected via a bus. The transmitter / receiver_320 is connected to the antenna_310.

Control unit_300 is a functional unit that controls the operation and functions of the entire UE. The control unit_300 may process all the functions that the other functional units (transmission / reception unit_320, storage unit_340) in the UE do not have. The control unit_300 realizes various processes in the UE by reading and executing various programs stored in the storage unit_340 as needed.

The transmission / reception unit_320 is a functional unit for wireless communication with a base station device or the like in the access network via the antenna_310. That is, the UE may send / receive user data and / or control information to / from the access network device and / or the core network device and / or the PDN and / or DN by using the transmission / reception unit_320. can.

In addition, the UE can communicate with the base station device (gNB) in 5GAN by using the transmission / reception unit_320. In addition, the UE can send and receive NAS (Non-Access-Stratum) messages to and from the AMF via the N1 interface by using the transmitter / receiver _320.

The storage unit_340 is a functional unit for storing programs, user data, control information, etc. required for each operation of the UE. Further, the storage unit_340 may have a function of storing control information transmitted / received to / from the access network device, the core network device, and the DN.

[2.2. Equipment configuration of gNB (base station equipment) and access point]
Next, an example of the device configuration of gNB will be described with reference to FIG. The gNB is composed of a control unit_500, an antenna_510, a network connection unit_520, a transmission / reception unit_530, and a storage unit_540. The control unit _500, the network connection unit _520, the transmission / reception unit _530, and the storage unit _540 are connected via a bus. The transmitter / receiver_530 is connected to the antenna_510.

Control unit_500 is a functional unit that controls the operation and functions of the entire gNB. The control unit_500 may process all the functions that the other functional units (network connection unit_520, transmission / reception unit_530, storage unit_540) in the base station apparatus do not have. The control unit_500 realizes various processes in gNB by reading and executing various programs stored in the storage unit_540 as needed.

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

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

The gNB in 5GAN can communicate with AMF via the N2 interface and can communicate with UPF via the N3 interface by using the network connection part_520. Further, the gNB can communicate with the UE by using the transmission / reception unit_530.

The storage unit_540 is a functional unit for storing programs, user data, control information, etc. required for each operation of gNB. Further, the storage unit_540 may have a function of storing control information transmitted / received to / from the UE, another access network device (base station device), the core network device, and the DN.

The access point may have the same device configuration as gNB.

[2.3. AMF device configuration]
Next, an example of the AMF device configuration will be described with reference to FIG. The AMF consists of a control unit_700, a network connection unit_720, and a storage unit_740. The control unit_700, network connection unit_720, and storage unit_740 are connected via a bus. The AMF may be a node that handles the control plane (also referred to as the C-plane).

Control unit_700 is a functional unit that controls the operation and functions of the entire AMF. The control unit_700 may process all the functions that the other functional units (network connection unit_720, storage unit_740) in the AMF do not have. The control unit _700 realizes various processes in the AMF by reading and executing various programs stored in the storage unit _740 as needed.

The network connection part_720 is a base station device and / or N3IWF, and / or other AMF, and / or SMF, and / or PCF, and / or NSSF (Network Slice Selection Function), and / or. It is a functional part for connecting to UDM (Unified Data Management) and / or SCEF. That is, the AMF uses the network connection _720 to use the base station equipment and / or N3IWF, and / or other AMF, and / or SMF, and / or PCF, and / or NSSF, and / or UDM. User data and / or control information can be sent and received with and / or SCEF.

The AMF in 5GCN can communicate with the base station device or N3IWF via the N2 interface and with other AMFs via the N14 interface by using the network connection _720. , Can communicate with SMF via N11 interface, can communicate with PCF via N15 interface, can communicate with NSSF via N22 interface, UDM via N8 interface Can communicate with. In addition, AMF can send and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_720. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN.

The storage unit_740 is a functional unit for storing programs, user data, control information, etc. required for each operation of AMF. Further, the storage unit_740 may have a function of storing control information transmitted / received to / from the UE, the access network device, another core network device, and the DN.

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

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

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

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

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

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

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

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

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

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

Control unit_700 is a functional unit that controls the operation and functions of the entire SMF. The control unit_500 may process all the functions that the other functional units (network connection unit_720, storage unit_740) in the SMF do not have. The control unit _700 realizes various processes in the SMF by reading and executing various programs stored in the storage unit _740 as needed.

The network connection part_720 is a functional part for SMF to connect with AMF and / or UPF, and / or PCF, and / or UDM. That is, the SMF can send and receive user data and / or control information between the AMF and / or the UPF, and / or the PCF, and / or the UDM by using the network connection unit_720.

The SMF in the 5GCN can communicate with the AMF via the N11 interface, with the UPF via the N4 interface, and via the N7 interface by using the network connection _720. , Can communicate with PCF and can communicate with UDM via N10 interface.

The storage unit_740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the SMF. Further, the storage unit_740 may have a function of storing control information transmitted / received to / from the UE, the access network device, another core network device, and the DN.

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

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

Control unit_700 is a functional unit that controls the operation and functions of the entire UPF. The control unit_700 may process all the functions that the other functional units (network connection unit_720, storage unit_740) in the AMF do not have. The control unit _700 realizes various processes in the UPF by reading and executing various programs stored in the storage unit _740 as needed.

The network connection unit_720 is a functional unit for the UPF to connect to the base station device (gNB) in 5GAN and / or the SMF and / or the DN. That is, the UPF uses the network connection _720 to control user data and / or control between the base station equipment and / or the N3IWF, and / or the SMF, and / or the DN, and / or other UPFs. Information can be sent and received.

The UPF in 5GCN can communicate with the base station device or N3IWF via the N3 interface, and can communicate with the SMF via the N4 interface by using the network connection part_720, N6. It can communicate with the DN via the interface and with other UPFs via the N9 interface.

The storage unit_740 is a functional unit for storing programs, user data, control information, etc. required for each operation of UPF. Further, the storage unit_740 may have a function of storing control information transmitted / received to / from the UE, the access network device, another core network device, and the DN.

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

The UPF may also be a gateway for IP communication and / or non-IP communication. In addition, the UPF may have a function of transferring IP communication, or may have a function of converting between non-IP communication and IP communication. Further, the plurality of gateways to be arranged may be a gateway connecting the core network and a single DN. The UPF may have connectivity with other NFs, or may be connected to each device via other NFs.

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

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

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

[2.6. N3IWF device configuration]
Next, an example of the apparatus / functional configuration of the N3IWF used in each embodiment will be described with reference to FIG. N3IWF is placed in the core network when the UE connects to 5GS via non-3GPP access (Untrusted non-3GPP Access). N3IWF consists of a control unit_700, a network connection unit_720, and a storage unit_740. The control unit_700, network connection unit_720, and storage unit_740 are connected via a bus.

Control unit_700 is a functional unit that controls the operation and functions of the entire N3IWF. The control unit_500 may process all the functions that the other functional units (network connection unit_720, storage unit_740) in the N3IWF do not have. The control unit _700 realizes various processes in the N3 IWF by reading and executing various programs stored in the storage unit _740 as needed.

The network connection unit_720 is a functional unit for N3IWF to communicate with the base station device or access point and / or AMF and / or UPF. That is, the N3IWF can send and receive control information and / or user data to and from the base station device or the access point by using the network connection unit_720. In addition, N3IWF can send and receive control information and / or user data to and from AMF and / or UPF, etc. using the network connection unit_720.

That is, the N3IWF can communicate with the base station device or the access point via the Y2 interface by using the network connection unit_720. The N3IWF can also communicate with the AMF via the N2 interface. The N3IWF can also communicate with the UPF via the N3 interface.

It should be noted that the above only describes the communication between the N3IWF and a typical device / function, and it goes without saying that the N3IWF can communicate with a device / function other than the above, that is, a core network device other than the above. ..

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

N3IWF has a function to establish an IPsec tunnel with the UE, a function to terminate the N2 interface for the control plane, a function to terminate the N3 interface for the user plane, a function to relay NAS signaling between the UE and AMF, and a PDU session. Ability to process N2 signaling from SMF for and QoS, a function to establish IPsec SA (Security Association) to support PDU session traffic, a function to relay user plane packets between UE and UPF (IPsec) Includes packet encapsulation / decapsulation for N3 tunnels), functions as a local mobility anchor within an untrusted non-3GPP access network, and the ability to select AMF. All of these functions are controlled by the control unit_700.

Note that NF_260 may have the same device configuration as N3IWF, except that the access used is 3GPP access.

[2.7. Explanation of other devices and / or functions and identification information in this embodiment]
Next, other devices and / or functions and identification information will be described.

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

Further, NSSF (Network Slice Selection Function) may be a network function (also referred to as NF) having a function of selecting a network slice serving a UE.

Further, NWDAF (Network Data Analytics Function) may be an NF having a function of collecting data from an NF or an application function (also referred to as AF).

Further, the PCF (Policy Control Function) may be an NF having a function of determining a policy for controlling the behavior of the network.

Further, the NRF (Network Repository Function) may be an NF having a service discovery function. The NRF may be an NF having a function of providing information on the discovered NF when receiving a discovery request of another NF from one NF.

In addition, SM (session management) messages (also referred to as NAS (Non-Access-Stratum) SM messages) may be NAS messages used in procedures for SM, and may be sent and received between UE and SMF via AMF. It may be a control message to be performed. Further, the SM message includes a PDU session establishment request message, a PDU session establishment acceptance message, a PDU session establishment reject message, and a PDU session modification request (PDU session modification). request) message, PDU session modification command (PDU session modification command) message, PDU session modification completion message (PDU session modification complete), PDU session change command rejection (PDU session modification command reject) message, PDU session modification rejection (PDU session modification) reject message, PDU session release request message, PDU session release reject message, PDU session release command message, PDU session release complete (PDU session release complete) A message or the like may be included.

In addition, the procedure for SM or SM procedure includes PDU session establishment procedure (PDU session establishment procedure), PDU session modification procedure (PDU session modification procedure), and PDU session release procedure (UE-requested PDU session release procedure). It may be. In addition, each procedure may be a procedure started from UE or a procedure started from NW.

Further, the MM (Mobility management) message (also referred to as NAS MM message) may be a NAS message used for the procedure for MM, and may be a control message sent and received between UE10 and AMF. In addition, the MM messages include a Registration request message, a Registration acceptance message, a Registration reject message, a De-registration request message, and a De-registration accept message. ) Messages, configuration update command messages, configuration update complete messages, service request messages, service accept messages, service reject messages, notifications ) Messages, Notification response messages, etc. may be included.

In addition, the procedure for MM or MM procedure is registration procedure (Registration procedure), deregistration procedure (De-registration procedure), generic UE configuration update procedure, authentication / approval procedure, service request procedure ( Service request procedure), paging procedure (Paging procedure), notification procedure (Notification procedure) may be included.

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

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

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

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

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

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

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

PLMN (Public land mobile network) is a communication network that provides mobile wireless communication services. PLMN is a network managed by an operator who is a telecommunications carrier, and the operator can be identified by the 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 Home PLMN (HPLMN). Further, the UE may have an Equivalent HPLMN list for identifying one or more EPLMNs (Equivalent HPLMNs) in the USIM. The PLMN different from HPLMN and / or EPLMN may be VPLMN (Visited PLMN). The PLMN successfully registered by the UE may be an RPLMN (Registered PLMN). The service provided by PLMN may be read as PLMN service, and the service provided by SNPN may be read as SNPN service.

Also, SNPN is a type of NPN that is a 5GS deployed for non-public use, and is an NF-independent NPN operated by the NPN operator and provided by PLMN. The SNPN is identified by a combination of PLMNID and NID (Network Identifier). Also, UEs that can use SNPN may support SNPN access modes. Also, a UE configured to operate in the SNPN access mode may be able to select the SNPN and register it with the SNPN, or it may not be able to select the PLMN. Also, the UE configured to operate in the SNPN access mode may or may not be able to execute the PLMN selection procedure. Also, even if the UE is SNPN enabled (SNPN enabled), the UE that is not set to operate in the SNPN access mode does not have to select the SNPN and register it in the SNPN, and the PLMN May be selectable. Further, a UE that is not set to operate in the SNPN access mode may not be able to execute the SNPN selection procedure, or may be able to execute the PLMN selection procedure.

Also, the UE operating in SNPN access mode may be able to select SNPN via Uu (3GPP access). Also, UEs operating in SNPN access mode can select SNPN via Uu or NWu established via PDU session provided by PLMN selected via Uu or NWu (non-3GPP access). May be good. Also, UEs that do not operate in SNPN access mode can select PLMN via Uu or NWu established via a PDU session provided by the SNPN selected via Uu or NWu (non-3GPP access). May be good.

The SNPN access mode may be managed and applied on an access basis. That is, it may be managed and applied separately for 3GPP access and non-3GPP access. In other words, activation or deactivation of the SNPN access mode for 3GPP access and activation or deactivation of the SNPN access mode for non-3GPP access may be independent. That is, when the SNPN access mode for 3GPP access is activated, the SNPN access mode for non-3GPP access may be activated or deactivated. Further, when the SNPN access mode for 3GPP access is deactivated, the SNPN access mode for non-3GPP access may be activated or deactivated.

Here, the SNPN access mode (SNPN access mode for 3GPP access) for 3GPP access includes the SNPN access mode (SNPN access mode over 3GPP access) in 3GPP access and the SNPN access mode (SNPN access mode via 3GPP access) via 3GPP access. ) May be called.

In addition, the SNPN access mode (SNPN access mode for non-3GPP access) for non-3GPP access is the SNPN access mode (SNPN access mode over non-3GPP access) for non-3GPP access, or SNPN via non-3GPP access. It may be referred to as an access mode (SNPN access mode via non-3GPP access).

Also, "activation" may be read as "working", and "deactivating" may be read as "not working". That is, the activation of the SNPN access mode for 3GPP access may mean that it operates in the SNPN access mode for 3GPP access. Also, deactivating the SNPN access mode for 3GPP access may mean that it does not operate in the SNPN access mode for 3GPP access. Further, the activation of the SNPN access mode for non-3GPP access may mean that the operation is performed in the SNPN access mode for non-3GPP access. Also, deactivating the SNPN access mode for non-3GPP access may mean that it does not operate in the SNPN access mode for non-3GPP access.

Further, as the state of the SNPN access mode in the UE, there may be the following first to ninth states.

Here, the first state is the state in which the UE does not operate in the SNPN access mode.

The second state is the state in which the UE operates in the SNPN access mode.

The third state is a state in which the 3GPP access does not operate in the SNPN access mode, and the non-3GPP access does not operate in the SNPN access mode.

The fourth state is a state in which the 3GPP access does not operate in the SNPN access mode, and the non-3GPP access operates in the SNPN access mode.

The fifth state is a state in which the 3GPP access operates in the SNPN access mode and the non-3GPP access does not operate in the SNPN access mode.

The sixth state is a state in which the 3GPP access operates in the SNPN access mode, and the non-3GPP access operates in the SNPN access mode.

The seventh state is a state in which it operates in the SNPN access mode when connecting to the SNPN service, and a state in which it does not operate in the SNPN access mode when connecting to the PLMN service.

The eighth state is that when connecting to the SNPN via non-3GPP access and then connecting to the PLMN via non-3GPP access, the SNPN operates in SNPN access mode. , PLMN does not operate in SNPN access mode. The eighth state is that when connecting to the SNPN via 3GPP access and then connecting to the PLMN via 3GPP access, the SNPN operates in the SNPN access mode and the PLMN is connected. It may not operate in SNPN access mode.

In addition, the ninth state is that when connecting to PLMN via non-3GPP access and then connecting to SNPN via non-3GPP access, operate in SNPN access mode for PLMN. However, it is in a state of operating in the SNPN access mode for the SNPN. In addition, the ninth state is that when connecting to PLMN via 3GPP access and then connecting to SNPN via 3GPP access, PLMN does not operate in SNPN access mode and goes to SNPN. On the other hand, it may be in a state of operating in the SNPN access mode.

The first state, the second state, the seventh state, the eighth state, and the ninth state may be applied when the SNPN access mode is not managed for each access. Further, the third state, the fourth state, the fifth state, and the sixth state may be applied states when the SNPN access mode is managed for each access. Further, the seventh state and the eighth state may be applied when connecting to the PLMN service via the SNPN. Further, the seventh state and the ninth state may be applied when connecting to the SNPN service via PLMN.

A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. UEs and / or networks can support network slices (NW slices; NS) in 5GS. Network slices may also be referred to simply as slices.

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

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

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

Also, configured NSSAI (also called configured NSSAI, configured NSSAI) is NSSAI supplied and stored in the UE. The UE may store the configured NSSAI for each PLMN. configured NSSAI may be information set by the network (or PLMN). S-NSSAI included in configured NSSAI may be expressed as configured S-NSSAI. configured S-NSSAI may be configured to include S-NSSAI and mapped S-NSSAI.

Also, requested NSSAI (also called Requested NSSAI, Requested NSSAI) is NSSAI provided from the UE to the network during the registration procedure. The requested NSSAI may be an allowed NSSAI or a configured NSSAI stored in the UE. Specifically, requested NSSAI may be information indicating a network slice that the UE wants to access. The S-NSSAI included in the requested NSSAI may be expressed as requested S-NSSAI. For example, requested NSSAI is included in an RRC (Radio Resource Control) message that includes a NAS message or NAS (Non-Access-Stratum) message sent from the UE to the network, such as a registration request message or a PDU session establishment request message. Will be done.

Also, allowed NSSAI (also referred to as allowed NSSAI, Allowed NSSAI) is information indicating one or more network slices allowed by the UE. In other words, allowed NSSAI is information that identifies the network slice that the network has allowed to connect to the UE. The UE and the network each store and manage allowed NSSAI for each access (3GPP access or non-3GPP access) as UE information. S-NSSAI included in allowed NSSAI may be expressed as allowed S-NSSAI. The allowed S-NSSAI may be configured to include S-NSSAI and mapped S-NSSAI.

Also, mapped S-NSSAI (also called Mapped S-NSSAI, Mapped S-NSSAI) is HPLMN's S-NSSAI mapped to S-NSSAI of registered PLMN in roaming scenarios. The UE may store one or more mapped S-NSSAI mapped to the configured NSSAI and the S-NSSAI included in the Allowed NSSAI of each access type. Further, the UE may store one or more mapped S-NSSAI of S-NSSAI included in rejected NSSAI.

Rejected NSSAI (also referred to as rejected NSSAI, rejected NSSAI) is information indicating one or more network slices for which the UE is not permitted. In other words, rejected NSSAI is information that identifies network slices that the network does not allow connections to the UE. The rejected NSSAI may be information that includes one or more combinations of the S-NSSAI and the reason for rejection value. Here, the refusal reason value is information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and the network may appropriately store and manage the rejected NSSAI based on the rejection reason value associated with each S-NSSAI. Further, the rejected NSSAI may be included in the NAS message transmitted from the network to the UE, such as the registration acceptance message, the setting update command, the registration refusal message, or the RRC message including the NAS message. S-NSSAI included in rejected NSSAI may be expressed as rejected S-NSSAI. The rejected NSSAI may be either the first to third rejected NSSAI and the pending NSSAI, or may be a combination thereof. S-NSSAI included in rejected NSSAI may be expressed as rejected S-NSSAI. The rejected S-NSSAI may be configured to include S-NSSAI and mapped S-NSSAI.

Here, the first rejected NSSAI is a set of one or more S-NSSAI that cannot be used in the current PLMN among the S-NSSAI included in the requested NSSAI by the UE. The first rejected NSSAI may be a 5GS Rejected NSSAI for the current PLMN, a Rejected S-NSSAI for the current PLMN, or an S-NSSAI included in the Rejected NSSAI for the current PLMN. There may be. The first rejected NSSAI may be a rejected NSSAI stored in the UE or the NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the first rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the first rejected NSSAI may be information that includes one or more combinations of the S-NSSAI and the reason value. The reason for refusal value at this time may be "S-NSSAI (S-NSSAI is not available in the current PLMN) which is not possible in the current PLMN", and the S-NSSAI associated with the reason for refusal value is It may be information indicating that it is not possible in the current PLMN.

Also, the first rejected NSSAI is valid for the entire registered PLMN. In other words, the UE and / or NW may treat the S-NSSAI contained in the first rejected NSSAI and the first rejected NSSAI as information that does not depend on the access type. That is, the first rejected NSSAI may be valid information for 3GPP access and non-3GPP access.

The UE may delete the first rejected NSSAI from the memory when it transitions to the non-registered state with both 3GPP access and non-3GPP access to the current PLMN. In other words, if the UE transitions to the unregistered state with respect to the current PLMN via one access, or if the registration with the new PLMN is successful via one access, or with the registration to the new PLMN via one access. If the UE fails and transitions to the unregistered state, and the UE is not registered via the other access (unregistered state), the UE deletes the first rejected NSSAI.

The second rejected NSSAI is a set of one or more S-NSSAIs that are not available in the current registration area among the S-NSSAIs that the UE has included in the requested NSSAI. The second rejected NSSAI may be a 5GS Rejected NSSAI for the current registration area. The second rejected NSSAI may be a rejected NSSAI stored in the UE or NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the second rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the second rejected NSSAI may be information that includes one or more combinations of the S-NSSAI and the reason value. The reason value at this time may be "S-NSSAI (S-NSSAI is not available in the current registration area), which is not possible in the current registration area", and the S-NSSAI associated with the reason value is It may be information indicating that it is not possible in the current registration area.

Also, the second rejected NSSAI is valid within the current registration area. That is, the UE and / or NW may treat the S-NSSAI included in the second rejected NSSAI and the second rejected NSSAI as information for each access type. That is, the second rejected NSSAI may be valid information for each of 3GPP access or non-3GPP access. That is, the UE may delete the second rejected NSSAI from the memory once it has transitioned to the unregistered state for a certain access.

The third rejected NSSAI is an S-NSSAI that requires NSSAA, and is a set of one or more S-NSSAIs that have failed or canceled NSSAA for that S-NSSAI. The third rejected NSSAI may be an NSSAI stored in the UE and / or the NW, or may be transmitted from the NW to the UE. When the third rejected NSSAI is transmitted from the NW to the UE, the third rejected NSSAI may be information including one or more combinations of the S-NSSAI and the reason for refusal value. The reason for refusal value at this time may be "S-NSSAI (S-NSSAI is not available due to the failed or revoked network slice-specific authorization and authentication), which is impossible due to the failure or cancellation of NSSAA". It may be information indicating that NSSAA for S-NSSAI associated with the reason for refusal value has failed or was canceled.

Also, the third rejected NSSAI is valid for the entire registered PLMN. In other words, the UE and / or NW may treat the S-NSSAI contained in the third rejected NSSAI and the third rejected NSSAI as information that does not depend on the access type. That is, the third rejected NSSAI may be valid information for 3GPP access and non-3GPP access. The third rejected NSSAI may be an NSSAI different from the rejected NSSAI. The third rejected NSSAI may be the first rejected NSSAI.

The third rejected NSSAI is a rejected NSSAI in which the UE identifies slices rejected due to the failure or cancellation of NSSAA from the core network. Specifically, the UE does not initiate the registration request procedure for the S-NSSAI included in the third rejected NSSAI while storing the third rejected NSSAI. The third rejected NSSAI may be identification information including one or more S-NSSAI received from the core network in association with the rejection reason value indicating the failure of NSSAA. The third rejected NSSAI is information that does not depend on the access type. Specifically, if the UE remembers the third rejected NSSAI, the UE attempts to send a registration request message containing the S-NSSAI contained in the third rejected NSSAI to both 3GPP and non-3GPP access. It does not have to be. Alternatively, the UE can send a registration request message including S-NSSAI included in the third rejected NSSAI based on the UE policy. Alternatively, the UE may delete the third rejected NSSAI based on the UE policy and transition to a state in which a registration request message including S-NSSAI included in the third rejected NSSAI can be transmitted. In other words, if the UE sends a registration request message containing the S-NSSAI contained in the third rejected NSSAI based on the UE policy, the UE may remove the S-NSSAI from the third rejected NSSAI. good.

In addition, pending NSSAI (also referred to as pending NSSAI, Pending NSSAI) is an S-NSSAI whose network requires network slice specific authentication, and network slice specific authentication has not been completed and cannot be used in the current PLMN. It is a set of one or more S-NSSAI. The pending NSSAI may be a 5GS Rejected NSSAI due to NSSAA or a pending NSSAI. The pending NSSAI may be an NSSAI stored in the UE or NW, or may be an NSSAI transmitted from the NW to the UE. The pending NSSAI is not limited to the rejected NSSAI, and may be an NSSAI independent of the rejected NSSAI. When the pending NSSAI is an NSSAI transmitted from the NW to the UE, the pending NSSAI may be information that includes one or more combinations of the S-NSSAI and the reason for refusal value. The reason for refusal value at this time may be "S-NSSAI (NSSAA is pending for the S-NSSAI)", and the S-NSSAI associated with the reason for refusal value is the S-. It may be information indicating that the UE is prohibited or pending from being used until the completion of NSSAA for NSSAI.

Also, pending NSSAI is valid for the entire registered PLMN. In other words, the UE and / or NW may treat the S-NSSAI contained in the third rejected NSSAI and pending NSSAI as information that does not depend on the access type. That is, the pending NSSAI may be valid information for 3GPP access and non-3GPP access. The pending NSSAI may be an NSSAI different from the rejected NSSAI. The pending NSSAI may be the first rejected NSSAI.

Also, pending NSSAI is an NSSAI composed of one or more S-NSSAI in which the UE identifies the slice that is pending the procedure. Specifically, the UE does not start the registration request procedure for the S-NSSAI included in the pending NSSAI while storing the pending NSSAI. In other words, the UE will not use the S-NSSAI contained in the pending NSSAI during the registration process until the NSSAA for the S-NSSAI contained in the pending NSSAI is completed. pending NSSAI is identification information including one or more S-NSSAI received from the core network in association with the rejection reason value indicating pending for NSSAA. pending NSSAI is information that does not depend on the access type. Specifically, when the UE remembers the pending NSSAI, the UE does not attempt to send the registration request message containing the S-NSSAI contained in the pending NSSAI to both 3GPP access and non-3GPP access.

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

The registration area (Registration area or registration area) is a set of one or more TAs assigned to the UE by AMF. It should be noted that the UE may be able to move without transmitting and receiving a signal for updating the tracking area while moving within one or a plurality of TAs included in the registration area. In other words, the registration area may be a group of information indicating an area that the UE can move without performing the tracking area update procedure. The registration area may be identified by a TAI list composed of one or more TAIs.

UE ID is information for identifying the 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. Further, the UE ID may be information for identifying the user.

Network Slice-Specific Authentication and Authorization (NSSAA) is a function for realizing authentication and authorization peculiar to network slices. With network slice-specific authentication and authorization, UE authentication and authorization can be performed outside the core network such as 3rd Party. PLMN and network devices equipped with NSSAA function can execute NSSAA procedure for a certain S-NSSAI based on the registration information of UE. In addition, UEs with NSSAA functionality can manage and store rejected NSSAI for pending for NSSAA and / or rejected NSSAI for NSSAA failure. In this paper, NSSAA may be referred to as network slice-specific authentication and authorization procedures and authentication and authorization procedures.

S-NSSAI that requires NSSAA is S-NSSAI that requires NSSAA, which is managed by the core network and / or the core network device. The core network and / or the core network device may store the S-NSSAI that requires NSSAA by associating and storing information indicating whether or not S-NSSAI and NSSAA are required. The core network and / or the core network device further indicates S-NSSAI requiring NSSAA and information indicating whether NSSAA is completed, or indicating that NSSAA has been completed, permitted or succeeded. Information may be associated with and stored. The core network and / or the core network device may manage S-NSSAI requiring NSSAA as information not related to the access network.

Further, the Uu interface (hereinafter, also referred to as Uu) may refer to the interface between the base station device installed in 3GPP access or 3GPP access and the UE. In the present specification, Uu may be used as a synonym for 3GPP access. Further, the NWu interface (hereinafter, also simply referred to as NWu) may refer to the interface between the N3 IWF and the UE. NWu may be used herein as synonymous with non-3GPP access.

Next, in the present embodiment, the identification information transmitted / received and stored and managed by each device will be described.

First, the first identification information is UE ability information. The first identification information may be 5 GMM capability. In addition, the first identification information may indicate whether or not the UE supports a certain function. The first identification information may also indicate whether the UE supports connecting to the PLMN service via the SNPN. The first identification information may also indicate whether the UE supports connecting to the SNPN service via the PLMN.

The second identification information is Requested NSSAI. The second identification information may consist of one or more requested S-NSSAIs. Further, the second identification information may indicate S-NSSAI that can be connected to the SNPN. Further, the second identification information may indicate an S-NSSAI that can be connected to the PLMN. The second identification information may also indicate an S-NSSAI that can connect to the SNPN service via the PLMN. The second identification information may also indicate an S-NSSAI that can connect to the PLMN service via the SNPN.

Also, the third identification information is the type of registration required. The third identification information may be 5GS registration type. The third identification information is initial registration, mobility registration updating, periodic registration updating, emergency registration, or SNPN. It may indicate registration with the PLMN via.

Further, the fourth identification information is identification information including at least two of the first to third identification information.

The eleventh identification information is network capability information. The eleventh identification information may be 5GS network feature support. In addition, the eleventh identification information may indicate whether or not the network supports a certain function. The first identification information may also indicate whether the network supports connecting to the PLMN service via the SNPN. The first identification information may also indicate whether the network supports connecting to the SNPN service via the PLMN.

The twelfth identification information is Allowed NSSAI. The twelfth identification information may be composed of one or more S-NSSAI.

The thirteenth identification information is Rejected NSSAI. The thirteenth identification information may be composed of one or more S-NSSAI.

The 14th identification information is Configured NSSAI. The fourteenth identification information may be composed of one or more S-NSSAI.

Also, the 15th identification information is Pending NSSAI. The fifteenth identification information may be composed of one or more S-NSSAI.

Further, the 16th identification information is identification information including at least 2 of the 11th to 15th identification information.

The 21st identification information is the PDU session ID that identifies the PDU session. Further, the 21st identification information may be a PDU session ID that identifies the PDU session requesting establishment. When requesting the establishment of a first PDU session, the 21st identification information may be a PDU session ID that identifies the first PDU session. Further, when requesting the establishment of the second PDU session, the 21st identification information may be the PDU session ID that identifies the second PDU session. Further, when requesting the establishment of the third PDU session, the 21st identification information may be the PDU session ID that identifies the third PDU session. Further, when requesting the establishment of the fourth PDU session, the 21st identification information may be the PDU session ID that identifies the fourth PDU session. Further, when requesting the establishment of the fifth PDU session, the 21st identification information may be the PDU session ID that identifies the fifth PDU session.

The 22nd identification information is the PDU session type that identifies the type of PDU session. Further, the 22nd identification information may be the PDU session type requested by the UE for the PDU session. Further, the 22nd identification information may indicate any one of IPv4, IPv6, IPv4v6, Unstructured, and Ethernet (registered trademark).

The 23rd identification information is in SSC mode. Further, the 23rd identification information may be the SSC mode requested by the UE for the PDU session. Further, the 23rd identification information may indicate any one of SSC mode 1, SSC mode 2, and SSC mode 3.

The 24th identification information is UE ability information. The 24th identification information may be 5GSM capability. Further, the 24th identification information may indicate whether or not the UE supports a certain function. The 24th identification information may also indicate whether the UE supports connecting to the SNPN service via the PLMN. The 24th identification information may also indicate whether the UE supports the ability to establish a PDU session for the SNPN via the PLMN. The 24th identification information may also indicate whether the UE supports connecting to the PLMN service via the SNPN. The 24th identification information may also indicate whether the UE supports the ability to establish a PDU session for the PLMN via the SNPN.

Also, the 25th identification information is 1 or more S-NSSAI. Further, the 25th identification information may be one or more S-NSSAI required by the UE for the PDU session to be established. Further, the 25th identification information may be one or more S-NSSAI selected from Allowed NSSAI for the current access type. Specifically, the 25th identification information is at least one access (3GPP access or non-3GPP) permitted by the network as Allowed NSSAI contained in the Registration Accept message in the Registration procedure. It can be one or more S-NSSAI for access).

The 26th identification information is DNN. Further, the 26th identification information may be a DNN that identifies the DN to which the PDU session requested to be established by the UE is connected.

Further, the 27th identification information may be a PDU session ID that identifies an already established PDU session. For example, when requesting the establishment of a third PDU session, the 27th identification information may be a PDU session ID that identifies the PDU session (second PDU session) established in PLMN. Further, when requesting the establishment of the fifth PDU session, the 27th identification information may be a PDU session ID that identifies the PDU session (fourth PDU session) established in the SNPN.

Further, the 28th identification information is identification information including at least two of the 21st to 27th identification information.

The 31st identification information is the PDU session ID that identifies the PDU session. It may be a PDU session ID that identifies the PDU session that is allowed to be established by the network. The 31st identification information may be the same as the 21st identification information.

The 32nd identification information is the PDU session type that identifies the type of PDU session. Also, the 32nd identification information may be the PDU session type selected by the network. Further, the 32nd identification information may indicate any one of IPv4, IPv6, IPv4v6, Unstructured, and Ethernet (registered trademark).

Also, the 33rd identification information is in SSC mode. Also, the 33rd identification information may be the SSC mode selected by the network for the PDU session. Further, the 33rd identification information may indicate any one of SSC mode 1, SSC mode 2, and SSC mode 3.

The 34th identification information is network UE capability information. The 34th identification information may be 5GSM network feature support. In addition, the 34th identification information may indicate whether or not the network supports a certain function. The 24th identification information may also indicate whether the network supports connecting to the SNPN service via the PLMN. The 24th identification may also indicate whether the network supports the ability to establish a PDU session for the SNPN via the PLMN. The 24th identification information may also indicate whether the network supports connecting to the PLMN service via the SNPN. The 24th identification may also indicate whether the network supports the ability to establish a PDU session for the PLMN via the SNPN.

Also, the 35th identification information is 1 or more S-NSSAI.

The 36th identification information is DNN. Further, the 36th identification information may be a DNN that identifies the DN to which the PDU session is connected.

Further, the 37th identification information is identification information including at least 2 of the 31st to 36th identification information.

[3. Registration procedure]
This chapter describes the registration procedure shown in Figure 12. In this chapter, the registration procedure is also referred to as this procedure.

The registration procedure is a procedure for the UE to register in the access network and / or the core network and / or the DN, and is a UE-led procedure. The UE can execute this procedure at any time, for example, when the power is turned on, as long as it is not registered in the network. In other words, the UE can start this procedure at any time if it is in the unregistered state (5GMM-DEREGISTERED state). In addition, each device (especially UE and AMF) can transition to the registration state (5GMM-REGISTEDED state) based on the completion of the registration procedure. It should be noted that each registration state may be managed by each device for each access. Specifically, each device may independently manage the registration status (registered or unregistered status) for 3GPP access and the registration status for non-3GPP access.

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

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

The procedure for transitioning from the above-mentioned UE not registered in the network (unregistered state) to the registered state (registered state) is the initial registration procedure or registration for initial registration. It may be a procedure (registration procedure for initial registration). In addition, the registration procedure executed while the UE is registered in the network (registration state) is the registration procedure (registration procedure for mobility and periodic registration update) for movement and periodic registration renewal, or movement and regular registration. It may be a registration procedure (mobility and periodic registration procedure).

First, the UE starts the registration procedure by sending a registration request message to the AMF via the access network (S600) (S602) (S604). Here, the access network may include a base station device or an access point. That is, the UE sends an RRC message including a registration request message to the base station device or the access point (S600). The registration request message is a NAS message sent and received on the N1 interface. Further, the RRC message may be a control message transmitted / received between the UE and the base station device or the access point. If the access network is non-3GPP access, an IKE message or an EAP message may be used instead of the RRC message. Hereinafter, for the sake of simplicity of explanation, the IKE message or the EAP message is also expressed as an RRC message. That is, the RRC message in this chapter can be regarded as a concept including an RRC message, an IKE message, and an EAP message. In addition, NAS messages are processed in the NAS layer, and RRC messages are processed in the RRC layer lower than the NAS layer.

Here, the UE can send at least one of the identification information 1 to 4 by including it in the registration request message and / or the RRC message.

The UE uses at least one of these identification information for a control message different from these, for example, a layer below the RRC layer (for example, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, etc. It may be included in the control message of PDCP (Packet Data Convergence Protocol) layer, SDAP (Service Data Adaptation Protocol) layer, etc.) and transmitted. By transmitting these identification information, the UE may indicate that the UE supports each function, may indicate a request of the UE, or may indicate both of them.

It should be noted that the UE determines whether or not to transmit at least one of these identification information, the ability information of the UE and / or the UE policy, and / or the state of the UE, and / or the registration information of the user. / Or may be selected and determined based on the context held by the UE.

The UE may include information other than these identification information in the registration request message and / or RRC message, and may transmit, for example, the UE ID and / or PLMN ID and / or AMF identification information. Here, the AMF identification information may be AMF or information that identifies a set of AMF, for example, 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) or GUAMI (Globally Unique AMF Identifier). It's okay.

When the base station device receives the RRC message including the registration request message, it selects the AMF to which the registration request message is forwarded (S602). The base station device can select AMF based on the received message and / or information. The base station device may select AMF based on other conditions.

The base station device extracts the registration request message from the received RRC message and transfers the registration request message to the selected AMF (S604). If at least one of the identification information 1 to 4 is not included in the registration request message but is included in the RRC message, the identification information included in the RRC message is sent to the selected AMF together with the registration request message. It may be transferred (S604).

When the AMF receives the registration request message, it can execute the first condition determination. The first condition determination is for determining whether or not the network accepts the UE's request. If the AMF determines that the first condition determination is true, the procedure from S610 to S612 may be executed. Further, if the AMF determines that the first condition determination is false, the AMF may execute the procedure of S610.

If the first condition determination is true, the control message sent / received by the S610 may be a registration acceptance message, and if the first condition determination is false, the control message sent / received by the S610 may be used. The message may be a Registration reject message.

The first condition determination is the reception of the registration request message and / or each identification information contained in the registration request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and It may be executed based on / or the state of the network and / or the user's registration information and / or the context held by AMF.

For example, if the network permits the UE request, the first condition determination may be determined to be true, and if the network does not allow the UE request, the first condition determination may be determined to be false. Also, if the network to which the UE is registered and / or the devices in the network support the functions required by the UE, the first condition determination may be determined to be true, and the functions required by the UE are supported. If not, the first condition determination may be determined to be false. Further, if the transmitted / received identification information is permitted, the first conditional determination may be determined to be true, and if the transmitted / received identification information is not permitted, the first conditional determination may be determined to be false.

Here, assuming that the first condition discrimination is determined to be true, the following explanation will be continued.

AMF may send the control message including one or more identification information among the 11th to 16th identification information. Further, the eleventh identification information may be information sent only when the first identification information is received, or may be information transmitted even if the first identification information is not received. good. It should be noted that the AMF may indicate that the network supports each function by transmitting these identification information and / or a control message, or may indicate that the request of the UE has been accepted. However, it may indicate that the request from the UE is not permitted, or it may indicate information that combines these. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.

When AMF does not allow S-NSSAI (allowed NSSAI) to the UE when sending a control message (registration acceptance message), but plans to execute the NSSAA procedure after completing this procedure or in parallel with this procedure. Or, if the NSSAA procedure is being executed between the UE and the network, or if the pending NSSAI is included in the control message and sent, an empty value may be included in the allowed NSSAI and sent.

It should be noted that the AMF determines which of the 11th to 16th identification information is included in the control message, each of the received identification information and / or the subscriber information, and / or the network capability information, and / or. It may be determined based on the operator policy and / or the state of the network and / or the user's registration information and / or the context held by the AMF.

AMF also receives each identification information and / or subscriber information and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or. It may be shown that the request of the UE has been accepted by sending the registration acceptance message based on the context held by the AMF.

The UE receives a control message (registration acceptance message) via the base station device (S610). By receiving the registration acceptance message, the UE can recognize that the UE's request by the registration request message has been accepted and the contents of various identification information contained in the registration acceptance message.

The UE can further send a registration completion message to the AMF via the base station device as a response message to the registration acceptance message (S612). Here, the registration completion message is a NAS message transmitted / received on the N1 interface, but may be included in the RRC message and transmitted / received between the UE and the base station device.

AMF receives the registration completion message via the base station device (S612). In addition, each device completes this procedure based on the transmission / reception of the registration acceptance message and / or the registration completion message.

In addition, each device transitions or maintains the state in which the UE is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission / reception of the registration acceptance message and / or the registration completion message, or the completion of the registration procedure. You may do.

Further, each device may store the information transmitted / received in this procedure in association with each other.

It should be noted that these states may be maintained or transitioned based on the information and control messages sent and received in this procedure, and may be maintained or transitioned based on the information and control messages sent and received in the procedure executed prior to this procedure. It may be maintained or transitioned.

[4. PDU session establishment procedure]
This chapter describes the PDU session establishment procedure described in FIG. In this chapter, the procedure for establishing a PDU session is also referred to as this procedure.

The PDU session establishment procedure is a procedure executed by the UE to establish a PDU session, and is a UE-led procedure.

First, the UE starts the PDU session establishment procedure by sending a NAS message including the N1SM container including the PDU session establishment request message to the AMF via the access network (S800). Here, the access network may include a base station device or an access point. That is, the UE sends a NAS message to the AMF via the base station device or the access point. The NAS message is, for example, a message transmitted via the N1 interface and may be an uplink NAS transport (UL NAS TRANSPORT) message.

The UE also requests the PDU session establishment request message and / or the N1SM container and / or the NAS message by including at least one of the identification information of the 21st to 28th. This can be notified to the network side.

It should be noted that the UE determines which of the 21st to 28th identification information is transmitted to the network, the UE capability information and / or the UE policy, and / or the UE status, and / or the user. It may be decided based on the registration information of the above and / or the context held by the UE.

In addition, the UE uses these identification information as a control message different from these, for example, a control message in a layer lower than the NAS layer (for example, RRC layer, MAC layer, RLC layer, PDCP layer, SDAP layer, etc.). It may be included in a control message of a layer higher than the NAS layer (for example, a transport layer, a session layer, a presentation layer, an application layer, etc.) and transmitted.

Next, when the AMF receives the NAS message, it can recognize what the UE is requesting and / or the content of the information (message, container, information) contained in the NAS message.

Next, AMF selects SMF as the transfer destination of at least a part of the information (message, container, information) contained in the NAS message received from the UE (S802). In addition, AMF may include information (messages, containers, information) contained in NAS messages, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or. The transfer destination SMF may be selected based on the network status and / or the user's registration information and / or the context held by the AMF.

Next, the AMF sends at least a part of the information (message, container, information) contained in the NAS message received from the UE to the selected SMF, for example, via the N11 interface (S804).

Next, when the SMF receives the information etc. (message, container, information) transmitted from the AMF, what the UE requests and / or the content of the information etc. (message, container, information) received from the AMF. Can be recognized.

Here, the SMF may determine the second condition. Further, the second condition determination may be for determining whether or not the network accepts the UE request. If the SMF determines that the second condition determination is true, the procedure (A) in FIG. 9 may be started, and if the second condition determination is determined to be false, the procedure (B) in FIG. 9 may be started. You may start.

The second condition determination is information received from AMF (message, container, information) and / or subscriber information (subscription information) and / or network capability information, and / or UE policy, and /. Alternatively, it may be executed based on the operator policy and / or the state of the network and / or the user's registration information and / or the context held by the SMF.

For example, if the network permits the UE request, the second condition determination may be determined to be true, and if the network does not allow the UE request, the second condition determination may be determined to be false. Also, if the network to which the UE is connected and / or the devices in the network support the functions required by the UE, the second condition determination may be determined to be true, and the functions required by the UE are supported. If not, the second condition determination may be determined to be false. Further, if the transmitted / received identification information is permitted, the second condition determination may be determined to be true, and if the transmitted / received identification information is not permitted, the second condition determination may be determined to be false. The condition for determining the truth of the second condition determination is not limited to the above-mentioned condition.

Next, each step of the procedure (A) in Fig. 9 will be explained.

Next, the SMF may select the UPF for the PDU session to be established and send an N4 session establishment request message to the selected UPF, for example, via the N4 interface (S808). The N4 session establishment request message may contain at least some of the PCC rules received from the PCF.

Here, the SMF is the information received from the AMF (messages, containers, information) and / or the information such as the PCC rules received from the PCF, and / or the subscriber information, and / or the network capability information, and /. Alternatively, one or more UPFs may be selected based on the UE policy and / or the operator policy and / or the network status and / or the user's registration information and / or the context held by the SMF. Also, if multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF. Here, it is assumed that UPF_232 (hereinafter, also referred to as UPF) is selected.

Next, when the UPF receives the N4 session establishment request message (S808), the UPF can recognize the content of the information received from the SMF. The UPF may also send an N4 session establishment response message to the SMF, eg, via the N4 interface, based on the receipt of the N4 session establishment request message (S810).

Next, when the SMF receives the N4 session establishment response message as the response message to the N4 session establishment request message, the SMF can recognize the content of the information received from the UPF.

The SMF then receives the PDU session establishment request message and / or the UPF selection and / or the N1 SM container and / or the N1 SM container and / or based on the reception of the N4 session establishment response message, for example, via the N11 interface. Send N2SM information and / or PDU session ID to AMF (S812). Here, the N1SM container may contain a PDU session establishment acceptance message.

Next, the AMF that receives the N1SM container and / or the N2SM information and / or the PDU session ID sends a NAS message to the UE via the base station device included in the access network (S814) (S816). ). Here, the NAS message is transmitted, for example, via the N1 interface. Further, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

Specifically, when the AMF sends an N2 PDU session request message to the base station device included in the access network (S814), the base station device that receives the N2 PDU session request message sends the N2 PDU session request message to the UE. Send a NAS message (S816). Here, the N2 PDU session request message may include a NAS message and / or N2 SM information. The NAS message may also include a PDU session ID and / or an N1SM container.

Further, the PDU session establishment acceptance message may be a response message to the PDU session establishment request. Also, the PDU session establishment acceptance message may indicate that the PDU session establishment has been accepted.

Here, the SMF and / or AMF are the PDU session establishment acceptance message and / or the N1 SM container and / or the PDU session ID and / or the NAS message, and / or the N2 SM information and / or the N2 PDU session request. By sending a message, it may indicate that at least a part of the UE's request by the PDU session establishment request message has been accepted.

Here, the SMF and / or AMF are used in the PDU session establishment acceptance message and / or the N1 SM container and / or NAS message, and / or the N2 SM information and / or the N2 PDU session request message from the 31st to the 37th. It may be transmitted including at least one of the identification information of. Here, the 31st identification information shall be the same as the 21st identification information of this procedure.

Note that the SMF may indicate that the network supports each function by sending these identification information and / or the PDU session establishment acceptance message, and indicate that the UE request has been accepted. It may indicate that the request from the UE is not permitted, or it may indicate information that combines these. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.

SMF and / or AMF can notify the UE of the contents of these identification information by transmitting at least one of these identification information.

Which identification information should SMF and / or AMF include in the PDU session establishment acceptance message and / or the N1 SM container and / or NAS message, and / or the N2 SM information and / or the N2 PDU session request message? Each received identification information and / or subscriber information and / or network capability information and / or UE policy and / or operator policy and / or network status and / or user registration information, And / or the decision may be made based on the context held by SMF and / or AMF.

Next, when the UE receives the NAS message via, for example, the N1 interface (S816), the UE's request by the PDU session establishment request message is accepted, and / or the information contained in the NAS message, etc. (message,). Can recognize the contents of the container (information). For example, the UE may recognize the PDU session type and SSC mode set for the PDU session identified by the 31st identification information based on the received 31st, 32nd, and 33rd identification information. The UE may also recognize the functions supported by the network based on the received 34th identification information.

Next, each step of the procedure (B) in Fig. 9 will be explained.

First, the SMF sends the N1 SM container and / or the PDU session ID to the AMF based on the reception of the PDU session establishment request message, for example, via the N11 interface (S818). Here, the N1SM container may contain a PDU session establishment refusal message.

Next, the AMF that received the N1SM container and / or the PDU session ID sends a NAS message to the UE via the first base station device included in the access network (S820) (S822). Here, the NAS message is transmitted, for example, via the N1 interface. Further, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. The NAS message may also include a PDU session ID and / or an N1SM container.

Further, the PDU session establishment refusal message may be a response message to the PDU session establishment request. Also, the PDU session establishment refusal message may indicate that the establishment of the PDU session has been rejected.

Here, the SMF and / or AMF sends a PDU session establishment refusal message and / or an N1SM container and / or a PDU session ID and / or a NAS message to request the UE by the PDU session establishment request message. May indicate that was rejected.

The SMF may indicate that the network does not support each function by sending a PDU session establishment refusal message, or may indicate that the UE request has been rejected, or the UE may indicate that the request has been rejected. It may indicate that the request is not permitted, or it may indicate information that combines these. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.

SMF and / or AMF can notify the UE of the contents of these identification information by transmitting at least one of these identification information.

Next, when the UE receives the NAS message via, for example, the N1 interface (S822), the UE's request by the PDU session establishment request message is rejected, and / or the information contained in the NAS message, etc. (message,). Can recognize the contents of the container (information).

Each device may complete this procedure based on the transmission and reception of the PDU session establishment acceptance message. At this time, each device may transition to a state in which it can communicate with the DN using the established PDU session.

Each device may complete this procedure based on the transmission and reception of the PDU session establishment refusal message. At this time, since each device cannot establish a PDU session, it cannot communicate with the DN if there is no PDU session already established.

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

Further, each device may store the information transmitted / received in this procedure in association with each other.

It should be noted that these states may be maintained or transitioned based on the information and control messages sent and received in this procedure, and may be maintained or transitioned based on the information and control messages sent and received in the procedure executed prior to this procedure. It may be maintained or transitioned.

Here, it is assumed that the PDU session establishment acceptance message is received and the PDU session is established.

[5. First Embodiment]
In this embodiment, the UE executes the registration procedure of Chapter 5.1 for the core network_200 via non-3GPP access (access network_100) in the SNPN in order to connect directly to the SNPN service. After the registration status is established, the PDU session (first PDU session) is established by executing the PDU session establishment procedure in Chapter 5.2, and the established PDU session can be used to communicate with DN_250. It becomes. In this embodiment, these series of procedures will be described with reference to FIGS. 1, 2, 12, and 13.

[5.1. Registration procedure for SNPN]
First, the registration procedure for SNPN will be described with reference to FIG. In this chapter, the registration procedure for SNPN is also referred to as this procedure. Since the registration procedure in Chapter 3 can be applied to this procedure, the details of the procedure are omitted here.

Note that this procedure may be executed by the UE in the second state, the fourth state, the sixth state, or the seventh state. Specifically, a UE in any of these states can perform an SNPN selection procedure to select a SNPN, and for the selected SNPN via non-3GPP access, the book. You may carry out the procedure. Here, the PLMN ID and NID used to identify and select the SNPN may be, for example, originally possessed by the UE, or may be broadcast from the SNPN base station device or access point. It may be included in the system information.

In addition, if this procedure is completed based on the transmission / reception of the registration acceptance message and / or the registration completion message, the UE may be in the registration state with respect to the SNPN, and the UE may be in the second state or the fourth state or the sixth state. Or the seventh state. At this time, the UE may be in a state where it can receive the SNPN service.

[5.2. PDU session establishment procedure for SNPN]
Next, the procedure for establishing a PDU session for SNPN will be described with reference to FIG. In this chapter, the procedure for establishing a PDU session for SNPN is also referred to as this procedure. Since this procedure can apply the PDU session establishment procedure in Chapter 4, the details of the procedure are omitted here.

In addition, the procedure in Chapter 5.1 is executed one or more times, and the UE in the second state, the fourth state, the sixth state, or the seventh state executes this procedure via non-3GPP access. You can do it. Specifically, when a UE in any of these states is in a registered state with respect to the SNPN, this procedure may be executed to establish a PDU session.

In addition, if this procedure is completed based on the transmission / reception of the PDU session establishment acceptance message, the UE may be in a state where it can communicate with the DN using the established PDU session (first PDU session). It may be in the 2nd state or the 4th state or the 6th state or the 7th state. At this time, the UE may be in a state where it can receive the SNPN service.

[6. Second Embodiment]
In this embodiment, in order for the UE to connect to the SNPN service via the PLMN, the registration procedure in Chapter 6.1 is performed for the core network_202 via the non-3GPP access (access network_102) in the PLMN. After the registration status is established by executing, the PDU session established by executing the PDU session establishment procedure in Chapter 6.2 (second PDU session) is used to enable communication with DN_252. Then, the UE further performs the registration procedure of Chapter 6.3 for the core network_200 via non-3GPP access (access network_100) to enter the registration state, and then the PDU session of Chapter 6.4. Using the PDU session established by executing the establishment procedure (third PDU session), it becomes possible to communicate with DN_250. In this embodiment, these series of procedures will be described with reference to FIGS. 3, 4, 12, and 13.

[6.1. Registration procedure for PLMN]
First, the registration procedure for PLMN will be described with reference to FIG. In this chapter, the registration procedure for PLMN is also referred to as this procedure. Since the registration procedure in Chapter 3 can be applied to this procedure, the details of the procedure are omitted here.

Note that this procedure may be executed by the UE in the 1st state, the 3rd state, the 5th state, or the 7th state. Specifically, a UE in any of these states can perform a PLMN selection procedure to select a PLMN, and the selected PLMN can be accessed via non-3GPP access. You may carry out the procedure. Here, the PLMN ID used to identify and select the PLMN may be, for example, the one originally possessed by the UE, or a system broadcast from the PLMN base station device or access point. It may have been included in the information.

In addition, if this procedure is completed based on the transmission / reception of the registration acceptance message and / or the registration completion message, the UE may be in the registration state with respect to the PLMN, and the UE may be in the first state, the third state, or the fifth state. Or the seventh state. At this time, the UE may be in a state where it can receive the PLMN service.

[6.2. Procedure for establishing PDU session for PLMN]
Next, the procedure for establishing a PDU session for PLMN will be described with reference to FIG. In this chapter, the procedure for establishing a PDU session for PLMN is also referred to as this procedure. Since this procedure can apply the PDU session establishment procedure in Chapter 4, the details of the procedure are omitted here.

In addition, the procedure in Chapter 6.1 is executed one or more times, and the UE in the 1st state, the 3rd state, the 5th state, or the 7th state executes this procedure via non-3GPP access. You can do it. Specifically, when a UE in any of these states is registered with the PLMN, this procedure may be executed to establish a PDU session.

In addition, if this procedure is completed based on the transmission / reception of the PDU session establishment acceptance message, the UE may be in a state where it can communicate with the DN using the established PDU session (second PDU session). It may be in the 1st or 3rd state or the 5th state or the 7th state or the 9th state. At this time, the UE may be in a state where it can receive the PLMN service.

[6.3. Registration procedure for SNPN (via PLMN)]
Next, the registration procedure for the SNPN, which is executed via the PLMN, will be described with reference to FIG. In this chapter, the registration procedure for SNPN performed via PLMN is also referred to as this procedure. Since the registration procedure in Chapter 3 can be applied to this procedure, the details of the procedure are omitted here.

Note that this procedure may be executed by the UE in the 7th state or the 9th state. Specifically, a UE in the 7th or 9th state can perform an SNPN selection procedure to select a SNPN and access the selected SNPN via non-3GPP access. You may carry out this procedure. Here, the PLMN ID and NID used to identify and select the SNPN may be, for example, originally possessed by the UE, or may be broadcast from the SNPN or PLMN base station device or access point. ) May be included in the system information.

The registration request message, registration acceptance message, registration refusal message, and registration completion message in this procedure are sent and received between the UE and the core network device such as AMF (AMF_210) via N3IWF_240.

In addition, when this procedure is completed based on the transmission / reception of the registration acceptance message and / or the registration completion message, the UE may be in the registration state not only for the PLMN but also for the SNPN, and the seventh state or It may be in the ninth state. At this time, the UE may be in a state where it can receive the SNPN service. That is, the UE may be in a state where it can receive the SNPN service via the PLMN.

[6.4. Procedure for establishing a PDU session for SNPN (via PLMN)]
Next, the procedure for establishing a PDU session for the SNPN, which is executed via the PLMN, will be described with reference to FIG. In this chapter, the procedure for establishing a PDU session for SNPN, which is performed via PLMN, is also referred to as this procedure. Since this procedure can apply the PDU session establishment procedure in Chapter 4, the details of the procedure are omitted here.

Note that the procedure in Chapter 6.3 may be executed one or more times, and the UE in the 7th state or the 9th state may execute this procedure via 3GPP access. Specifically, this procedure may be performed to establish a PDU session when the UE in the 7th state or the 9th state is in the registration state for the PLMN and SNPN.

The PDU session establishment request message, PDU session establishment acceptance message, and PDU session establishment rejection message in this procedure are transmitted and received between the UE and the core network device such as SMF (SMF_220) via N3IWF_240.

In addition, if this procedure is completed based on the transmission / reception of the PDU session establishment acceptance message, the UE may be in a state where it can communicate with the DN using the established PDU session (third PDU session). It may be in the 7th state or the 9th state. At this time, the UE may be in a state where it can receive the SNPN service. That is, the UE may be in a state where it can receive the SNPN service via the PLMN.

[7. Third Embodiment]
In this embodiment, in order for the UE to connect to the SNPN service via the PLMN, the registration procedure in Chapter 7.1 is performed for the core network_202 via the non-3GPP access (access network_102) in the PLMN. After the registration status is established by executing, the PDU session established by executing the PDU session establishment procedure in Chapter 7.2 (second PDU session) is used to enable communication with DN_252. Then, the UE further executes the registration procedure in Chapter 7.3 for the core network_200 via 3GPP access (access network_100) to enter the registration state, and then the PDU session establishment procedure in Chapter 7.4. The PDU session established by executing (3rd PDU session) is used, and it becomes possible to communicate with DN_250. In this embodiment, these series of procedures will be described with reference to FIGS. 3, 5, 12, and 13.

[7.1. Registration procedure for PLMN]
First, the registration procedure for PLMN will be described with reference to FIG. In this chapter, the registration procedure for PLMN is also referred to as this procedure. Since the registration procedure in Chapter 3 can be applied to this procedure, the details of the procedure are omitted here.

Note that this procedure may be executed by the UE in the 1st state, the 3rd state, the 5th state, or the 7th state. Specifically, a UE in any of these states can perform a PLMN selection procedure to select a PLMN, and the selected PLMN can be accessed via non-3GPP access. You may carry out the procedure. Here, the PLMN ID used to identify and select the PLMN may be, for example, the one originally possessed by the UE, or a system broadcast from the PLMN base station device or access point. It may have been included in the information.

In addition, if this procedure is completed based on the transmission / reception of the registration acceptance message and / or the registration completion message, the UE may be in the registration state with respect to the PLMN, and the UE may be in the first state, the third state, or the fifth state. Or the seventh state. At this time, the UE may be in a state where it can receive the PLMN service.

[7.2. Procedure for establishing PDU session for PLMN]
Next, the procedure for establishing a PDU session for PLMN will be described with reference to FIG. In this chapter, the procedure for establishing a PDU session for PLMN is also referred to as this procedure. Since this procedure can apply the PDU session establishment procedure in Chapter 4, the details of the procedure are omitted here.

In addition, the procedure in Chapter 7.1 is executed one or more times, and the UE in the 1st state, the 3rd state, the 5th state, or the 7th state executes this procedure via non-3GPP access. You can do it. Specifically, when a UE in any of these states is registered with the PLMN, this procedure may be executed to establish a PDU session.

In addition, if this procedure is completed based on the transmission / reception of the PDU session establishment acceptance message, the UE may be in a state where it can communicate with the DN using the established PDU session (second PDU session). It may be in the 1st state or the 3rd state or the 5th state or the 7th state. At this time, the UE may be in a state where it can receive the PLMN service.

[7.3. Registration procedure for SNPN (via PLMN)]
Next, the registration procedure for the SNPN, which is executed via the PLMN, will be described with reference to FIG. In this chapter, the registration procedure for SNPN performed via PLMN is also referred to as this procedure. Since the registration procedure in Chapter 3 can be applied to this procedure, the details of the procedure are omitted here.

Note that this procedure may be executed by the UE in the fifth state. Specifically, the UE in the fifth state can execute the SNPN selection procedure to select a certain SNPN, and execute this procedure for the selected SNPN via 3GPP access. It's okay. Here, the PLMN ID and NID used to identify and select the SNPN may be, for example, originally possessed by the UE, or may be broadcast from the SNPN or PLMN base station device or access point. ) May be included in the system information.

The registration request message, registration acceptance message, registration refusal message, and registration completion message in this procedure are transmitted and received between the UE and the core network device such as AMF (AMF_210) via NF_260.

In addition, when this procedure is completed based on the transmission / reception of the registration acceptance message and / or the registration completion message, the UE may be in the registration state not only for the PLMN but also for the SNPN, and is in the fifth state. You can be. At this time, the UE may be in a state where it can receive the SNPN service. That is, the UE may be in a state where it can receive the SNPN service via the PLMN.

[7.4. PDU session establishment procedure for SNPN (via PLMN)]
Next, the procedure for establishing a PDU session for the SNPN, which is executed via the PLMN, will be described with reference to FIG. In this chapter, the procedure for establishing a PDU session for SNPN, which is performed via PLMN, is also referred to as this procedure. Since this procedure can apply the PDU session establishment procedure in Chapter 4, the details of the procedure are omitted here.

Note that the procedure in Chapter 7.3 may be executed at least once, and the UE in the fifth state may execute this procedure via 3GPP access. Specifically, this procedure may be executed in order to establish a PDU session when the UE in the fifth state is in the registered state with respect to PLMN and SNPN.

The PDU session establishment request message, PDU session establishment acceptance message, and PDU session establishment rejection message in this procedure are transmitted and received between the UE and the core network device such as SMF (SMF_220) via NF_260.

In addition, if this procedure is completed based on the transmission / reception of the PDU session establishment acceptance message, the UE may be in a state where it can communicate with the DN using the established PDU session (third PDU session). It may be in the state of 5. At this time, the UE may be in a state where it can receive the SNPN service. That is, the UE may be in a state where it can receive the SNPN service via the PLMN.

[8. Fourth Embodiment]
In this embodiment, in order for the UE to connect to the PLMN service via the SNPN, the registration procedure in Chapter 8.1 is performed for the core network_200 via the non-3GPP access (access network_100) in the SNPN. After the registration status is entered, the PDU session established by executing the PDU session establishment procedure in Chapter 8.2 (fourth PDU session) is used to enable communication with DN_250. Then, the UE further performs the registration procedure of Chapter 8.3 for the core network_202 via non-3GPP access (access network_102) to enter the registration state, and then the PDU session of Chapter 8.4. Using the PDU session established by executing the establishment procedure (fifth PDU session), it becomes possible to communicate with DN_252. In this embodiment, these series of procedures will be described with reference to FIGS. 6, 7, 12, and 13.

[8.1. Registration procedure for SNPN]
First, the registration procedure for SNPN will be described with reference to FIG. In this chapter, the registration procedure for SNPN is also referred to as this procedure. Since the registration procedure in Chapter 3 can be applied to this procedure, the details of the procedure are omitted here.

Note that this procedure may be executed by the UE in the second state, the fourth state, the sixth state, or the seventh state. Specifically, a UE in any of these states can perform an SNPN selection procedure to select a SNPN, and for the selected SNPN via non-3GPP access, the book. You may carry out the procedure. Here, the PLMN ID and NID used to identify and select the SNPN may be, for example, originally possessed by the UE, or may be broadcast from the SNPN base station device or access point. It may be included in the system information.

In addition, if this procedure is completed based on the transmission / reception of the registration acceptance message and / or the registration completion message, the UE may be in the registration state with respect to the SNPN, and the UE may be in the second state or the fourth state or the sixth state. Or the seventh state. At this time, the UE may be in a state where it can receive the SNPN service.

[8.2. Procedure for establishing a PDU session for SNPN]
Next, the procedure for establishing a PDU session for SNPN will be described with reference to FIG. In this chapter, the procedure for establishing a PDU session for SNPN is also referred to as this procedure. Since this procedure can apply the PDU session establishment procedure in Chapter 4, the details of the procedure are omitted here.

In addition, the procedure in Chapter 8.1 is executed one or more times, and the UE in the second state, the fourth state, the sixth state, or the seventh state executes this procedure via non-3GPP access. You can do it. Specifically, when a UE in any of these states is in a registered state with respect to the SNPN, this procedure may be executed to establish a PDU session.

In addition, if this procedure is completed based on the transmission / reception of the PDU session establishment acceptance message, the UE may be in a state where it can communicate with the DN using the established PDU session (fourth PDU session). It may be in the 2nd or 4th state or the 6th state or the 7th state or the 8th state. At this time, the UE may be in a state where it can receive the SNPN service.

[8.3. Registration procedure for PLMN (via SNPN)]
Next, the registration procedure for PLMN executed via the SNPN will be described with reference to FIG. In this chapter, the registration procedure for PLMN performed via SNPN is also referred to as this procedure. Since the registration procedure in Chapter 3 can be applied to this procedure, the details of the procedure are omitted here.

Note that this procedure may be executed by the UE in the 7th state or the 8th state. Specifically, a UE in the 7th or 8th state can execute the PLMN selection procedure to select a PLMN, and the selected PLMN can be accessed via non-3GPP access. You may carry out this procedure. Here, the PLMN ID used to identify and select the PLMN may be, for example, the one originally possessed by the UE, or may be broadcast from the PLMN or SNPN base station device or access point. It may be included in the system information.

The registration request message, registration acceptance message, registration refusal message, and registration completion message in this procedure are transmitted and received between the UE and the core network device such as AMF (AMF_212) via N3IWF_242.

In addition, when this procedure is completed based on the transmission / reception of the registration acceptance message and / or the registration completion message, the UE may be in the registration state not only for the SNPN but also for the PLMN, and the seventh state or It may be in the eighth state. At this time, the UE may be in a state where it can receive the PLMN service. That is, the UE may be in a state where it can receive the PLMN service via the SNPN.

[8.4. Procedure for establishing a PDU session for PLMN (via SNPN)]
Next, the procedure for establishing a PDU session for PLMN, which is executed via the SNPN, will be described with reference to FIG. In this chapter, the procedure for establishing a PDU session for PLMN, which is performed via SNPN, is also referred to as this procedure. Since this procedure can apply the PDU session establishment procedure in Chapter 4, the details of the procedure are omitted here.

Note that the procedure in Chapter 8.3 may be executed one or more times, and the UE in the 7th state or the 8th state may execute this procedure via non-3GPP access. Specifically, this procedure may be performed to establish a PDU session when the UE in the 7th state or the 8th state is in the registration state for the PLMN and SNPN.

The PDU session establishment request message, PDU session establishment acceptance message, and PDU session establishment rejection message in this procedure are transmitted and received between the UE and the core network device such as SMF (SMF_222) via N3IWF_242.

In addition, if this procedure is completed based on the transmission / reception of the PDU session establishment acceptance message, the UE may be in a state where it can communicate with the DN using the established PDU session (fifth PDU session). It may be in the 7th state or the 8th state. At this time, the UE may be in a state where it can receive the PLMN service. That is, the UE may be in a state where it can receive the PLMN service via the SNPN.

[9. Fifth Embodiment]
In this embodiment, in order for the UE to connect to the PLMN service via the SNPN, the registration procedure in Chapter 9.1 is performed for the core network_200 via the non-3GPP access (access network_100) in the SNPN. After the registration status is established by executing, the PDU session established by executing the PDU session establishment procedure in Chapter 9.2 (fourth PDU session) can be used to communicate with DN_250. Then, the UE further executes the registration procedure of Chapter 9.3 for the core network_202 via 3GPP access (access network_102) to enter the registration state, and then the PDU session establishment procedure of Chapter 9.4. The PDU session established by executing (fifth PDU session) is used, and it becomes possible to communicate with DN_252. In this embodiment, these series of procedures will be described with reference to FIGS. 6, 8, 12, and 13.

[9.1. Registration procedure for SNPN]
First, the registration procedure for SNPN will be described with reference to FIG. In this chapter, the registration procedure for SNPN is also referred to as this procedure. Since the registration procedure in Chapter 3 can be applied to this procedure, the details of the procedure are omitted here.

Note that this procedure may be executed by the UE in the second state, the fourth state, the sixth state, or the seventh state. Specifically, a UE in any of these states can perform an SNPN selection procedure to select a SNPN, and for the selected SNPN via non-3GPP access, the book. You may carry out the procedure. Here, the PLMN ID and NID used to identify and select the SNPN may be, for example, originally possessed by the UE, or may be broadcast from the SNPN base station device or access point. It may be included in the system information.

In addition, if this procedure is completed based on the transmission / reception of the registration acceptance message and / or the registration completion message, the UE may be in the registration state with respect to the SNPN, and the UE may be in the second state or the fourth state or the sixth state. Or the seventh state. At this time, the UE may be in a state where it can receive the SNPN service.

[9.2. PDU session establishment procedure for SNPN]
Next, the procedure for establishing a PDU session for SNPN will be described with reference to FIG. In this chapter, the procedure for establishing a PDU session for SNPN is also referred to as this procedure. Since this procedure can apply the PDU session establishment procedure in Chapter 4, the details of the procedure are omitted here.

In addition, the procedure in Chapter 9.1 is executed one or more times, and the UE in the second state, the fourth state, the sixth state, or the seventh state executes this procedure via non-3GPP access. You can do it. Specifically, when a UE in any of these states is in a registered state with respect to the SNPN, this procedure may be executed to establish a PDU session.

In addition, if this procedure is completed based on the transmission / reception of the PDU session establishment acceptance message, the UE may be in a state where it can communicate with the DN using the established PDU session (fourth PDU session). It may be in the 2nd state or the 4th state or the 6th state or the 7th state. At this time, the UE may be in a state where it can receive the SNPN service.

[9.3. Registration procedure for PLMN (via SNPN)]
Next, the registration procedure for PLMN executed via the SNPN will be described with reference to FIG. In this chapter, the registration procedure for PLMN performed via SNPN is also referred to as this procedure. Since the registration procedure in Chapter 3 can be applied to this procedure, the details of the procedure are omitted here.

Note that this procedure may be executed by the UE in the 4th state. Specifically, the UE in the fourth state can execute the PLMN selection procedure to select a certain PLMN, and execute this procedure for the selected PLMN via 3GPP access. It's okay. Here, the PLMN ID used to identify and select the PLMN may be, for example, the one originally possessed by the UE, or may be broadcast from the PLMN or SNPN base station device or access point. It may be included in the system information.

The registration request message, registration acceptance message, registration refusal message, and registration completion message in this procedure are transmitted and received between the UE and the core network device such as AMF (AMF_212) via NF_262.

In addition, when this procedure is completed based on the transmission / reception of the registration acceptance message and / or the registration completion message, the UE may be in the registration state not only for the SNPN but also for the PLMN, and is in the fourth state. You can be. At this time, the UE may be in a state where it can receive the PLMN service. That is, the UE may be in a state where it can receive the PLMN service via the SNPN.

[9.4. Procedure for establishing a PDU session for PLMN (via SNPN)]
Next, the procedure for establishing a PDU session for PLMN, which is executed via the SNPN, will be described with reference to FIG. In this chapter, the procedure for establishing a PDU session for PLMN, which is performed via SNPN, is also referred to as this procedure. Since this procedure can apply the PDU session establishment procedure in Chapter 4, the details of the procedure are omitted here.

Note that the procedure in Chapter 9.3 may be executed at least once, and the UE in the 4th state may execute this procedure via 3GPP access. Specifically, this procedure may be executed in order to establish a PDU session when the UE in the fourth state is in the registered state with respect to PLMN and SNPN.

The PDU session establishment request message, PDU session establishment acceptance message, and PDU session establishment rejection message in this procedure are transmitted and received between the UE and the core network device such as SMF (SMF_222) via NF_262.

In addition, if this procedure is completed based on the transmission / reception of the PDU session establishment acceptance message, the UE may be in a state where it can communicate with the DN using the established PDU session (fifth PDU session). It may be in the state of 4. At this time, the UE may be in a state where it can receive the PLMN service. That is, the UE may be in a state where it can receive the PLMN service via the SNPN.

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

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

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

The invention of the present application is not limited to the above-described embodiment. In the embodiment, one example of the device has been described, but one aspect of the present invention is not limited to this, and is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device. , Kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices such as living equipment.

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment and includes design changes and the like within a range not deviating from the gist of the present invention. Further, one aspect of the present invention can be variously modified within the scope of the claims, and the technical aspects of the present invention can also be obtained by appropriately combining the technical means disclosed in the different embodiments. Included in the range. Further, the elements described in each of the above-described embodiments are included, and a configuration in which elements having the same effect are replaced with each other is also included.

Claims (1)

1. UE (User Equipment) equipped with a control unit
   When connecting to the SNPN (Stand-alone Non-Public Network) service using 3GPP access via PLMN (Public Land Mobile Network) using non-3GPP access, the control unit
   On non-3GPP access, it does not work in SNPN access mode,
   On 3GPP access, it works in SNPN access mode,
   UE characterized by that.
   
   

Images