WO2020204092A1 - User device, control device, and communication control method - Google Patents

Abstract

An embodiment of the present invention provides a communication means for implementing a Vertical LAN and a Non-Public Network (NPN) for 5GS. Provided are UE registration and session establishing procedures and a communication means for implementing a Vertical LAN and a Non-Public Network (NPN) for 5GS. Further provided are: a procedure for modifying the setting of a UE registered in a network; a procedure for managing an established session on the basis of information about a UE which is registered, stored, or set in a network; a procedure for deleting an established session; and a communication means.

Description

User device, control device, and communication control method

This application relates to a user device, a control device, and a communication control method. This application claims the benefit of priority to Japanese Patent Application No. 2019-70073, which is a Japanese patent application filed on April 1, 2019, and by referring to it, the content of the application is claimed. All are included in this application.

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

In recent years, 3GPP has also been studying the next-generation communication technology and system architecture of 5G (5th Generation) mobile communication systems, which are next-generation mobile communication systems. In particular, 5GS (5G) is a system that realizes 5G mobile communication systems. 5G System) is being specified (see Non-Patent Document 1 and Non-Patent Document 2). 5GS extracts technical issues for connecting a wide variety of terminals to cellular networks and specifies solutions.

In 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered in order to provide a wide variety of services. In addition, 5GS is considering Vertical LAN as a new function.

Furthermore, support for NPN (Non-public network) is being considered as a key item for Vertical LAN. NPN is a private network that is not intended for general use but for private use by companies. NPN is a private network used by specific users for specific purposes.

Two types of NPN are being considered: Stand-alone Non-Public Network (SNPN) and Public network integrated NPN. In 3GPP, it is specified that Public network integrated NPN supports NPN by using the function of network slice.

Also, in 5GS, there is a UE (UE configured for high priority access in selected PLMN) that is set as a UE that connects with high priority in PLMN (Public Land Mobile Network). The UE identification method set as the UE to connect with high priority in PLMN is identified based on one or more access identification information stored in each device of the UE and the device in the core network.

However, the specific means and method for supporting UEs set as UEs that connect with high priority in NPN have not been clarified.

The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a method for realizing a function for NPN in 5GS.

The user device according to the embodiment of the present invention is a user device that can be connected to an NPN (Non Public Network), and receives the value of the backoff timer from the storage unit that stores the first information and the NPN. Based on the first information, the back-off timer is provided with a transmitter / receiver for transmitting a request message while the backoff timer is being executed, and the first information has a high priority within the NPN by the user device. It is information indicating that the connection is possible, and the NPN is a network slice.

The control device according to the embodiment of the present invention is a control device in PLMN (Public land mobile network) including a network slice created as an NPN (Non Public Network), and is a memory for storing the first identification information. A reason value that indicates congestion as a response to the request message even if the request message is received from the unit, the control unit that detects congestion, and the user device is performing detection based on the first identification information. It is characterized in that it does not transmit a rejection message including, and includes a transmission / reception unit.

The control device of the embodiment of the present invention is a control device in the PLMN including a network slice created as a Non Public Network (NPN), and is backed to a user device that can be connected with a high priority in the NPN. It is characterized by having a transmission / reception unit for transmitting a PDU (Protocol Data Unit or Packet Data Unit) session deletion command message or a PDU session establishment rejection message or a PDU session change rejection message that does not include an off-timer.

According to one aspect of the present invention, in 5GS, NPN support is possible, and UE registration, session establishment, session management, and UE support for UEs that connect with high priority within the NPN. Settings can be changed / updated.

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

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

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

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

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

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

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

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

UE is a device that can connect to network services via 3GPP access (3GPP access network, also called 3GPP AN) and / or non-3GPP access (non-3GPP access network, also called non-3GPP AN). is there. The UE may be a terminal device capable of wireless communication such as a mobile phone or a smartphone, and may be a terminal device capable of connecting to EPS or 5GS. The UE may be provided with UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). The UE may be expressed as a user device or a terminal device.

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

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

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

In the following, the devices included in the access network_A and / or the access network_B and / or the access network_A, and / or the devices included in the access network_B are the access network or the access network device. It may be called.

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

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

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

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

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

In addition, in the following, at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included in these are referred to as a network or network device. It may be called. That is, the fact that the network and / or the network device sends and receives messages and / or executes the procedure means that the access network_A, core network_A, PDN, access network_B, core network_B, and DN It means that at least a part and / or one or more devices included therein send and receive messages and / or perform procedures.

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

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

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

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

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

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

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

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

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

[2.2. GNB device configuration]
Next, an example of the device configuration of gNB will be described with reference to FIG. The gNB is composed of a control unit_B500, an antenna 510, a network connection unit_B520, a transmission / reception unit_B530, and a storage unit_B540. The control unit_B500, network connection unit_B520, transmission / reception unit_B530, and storage unit_B540 are connected via a bus. The transmitter / receiver_B530 is connected to the antenna 510.

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

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

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

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

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

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

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

The network connection part_B720 is a functional part for AMF to connect to the base station device (gNB) in 5GAN and / or SMF, and / or PCF, and / or UDM, and / or SCEF. That is, the AMF uses the network connection_B720 to communicate with the base station equipment (gNB) in 5GAN and / or SMF and / or PCF, and / or UDM, and / or SCEF. Data and / or control information can be sent and received.

Explained in detail with reference to FIG. 2, the AMF within the 5GCN can communicate with the gNB via the N2 interface by using the network connection_A620 and with the UDM via the N8 interface. It can communicate, it can communicate with the SMF via the N11 interface, and it can communicate with the PCF via the N15 interface. In addition, AMF can send and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN. In addition, when AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection part_A620.

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

AMF has a function to exchange control messages with RAN using the N2 interface, a function to exchange NAS messages with UE using the 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 Message forwarding function, access authentication (Access Authorization) function, security anchor function (SEA; Security Anchor Functionality), security context management (SCM; Security Context Management) function, N2 for 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, so 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 (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 PDU session context. When each device is 5GMM-REGISTERED, UE_A10 may start sending and receiving user data and control messages, or may respond to paging. Further, when each device is 5GMM-REGISTERED, UE_A10 may execute a registration procedure other than the registration procedure for initial registration and / or a service request procedure.

Furthermore, in 5GMM-DEREGISTERED, each device may be in a state where the 5GMM context has not been established, the position information of UE_A10 may not be known to the network, or the network reaches UE_A10. It may be in an impossible state. If each device is 5GMM-DEREGISTERED, UE_A10 may start the registration procedure or establish 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) and an N3 interface connection (N3 connection). On the other hand, in the CM-CONNECTED state, it has a NAS signaling connection (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-connection 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. ) May be there. 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). Furthermore, the disconnected state in 3GPP access may be expressed as 5GMM non-connection mode (5GMM-IDLE mode over 3GPP access) in 3GPP access, and the connection state in 3GPP access is 5GMM connection mode (5GMM-) in 3GPP access. It may be expressed as CONNECTED mode over 3GPP access). Further, the non-connection state in non-3GPP access may be expressed as 5GMM non-connection mode (5GMM-IDLE mode over non-3GPP access) in non-3GPP access, and the connection state in non-3GPP access is non. It may be expressed as 5GMM connection mode (5GMM-CONNECTED mode over non-3GPP access) in -3GPP access. The 5GMM non-connection mode may be expressed as an idle mode, and the 5GMM connection mode may be expressed as a connected mode.

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

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

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

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

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

Explained in detail with reference to FIG. 2, the SMF in the 5GCN can communicate with the AMF via the N11 interface by using the network connection_A620 and with the UPF via the N4 interface. It can communicate, it can communicate with the PCF via the N7 interface, and it can communicate with the UDM via the N10 interface.

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

SMF has session management functions such as establishment / modification / release of PDU sessions, IP address allocation and management functions for UEs, UPF selection and control functions, and appropriate destinations (destination). ), UPF setting function for routing traffic 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) sent to, a function to determine the SSC mode (Session and Service Continuity mode) for the session, a roaming function, and the like.

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

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

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

Explained in detail with reference to FIG. 2, the UPF in the 5GCN can communicate with the gNB via the N3 interface by using the network connection_A620 and with the SMF via the N4 interface. It can communicate, can communicate with DN via N6 interface, and can communicate with other UPFs via N9 interface.

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

The UPF acts as an anchor point for intra-RAT mobility or inter-RAT mobility, as an external PDU session point for interconnecting the DN (ie, as a gateway between the DN and the core network_B). Data transfer function), packet routing and transfer function, UL CL (Uplink Classifier) function that supports routing of multiple traffic flows to one DN, and multi-homed PDU session support. It has a branching point function, a QoS (Quality of Service) processing function for the user plane, 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 non-IP communication and IP communication. Further, the plurality of gateways to be arranged may be a gateway connecting the core network_B and a single DN. The UPF may have connectivity with other NFs, or may be connected to each device via the other NFs.

The user plane is user data sent 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 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 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. Furthermore, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and NG RAN and the N2 interface. Hereinafter, the control plane may be 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. Description of other devices and / or functions]
Next, other devices and / or functions will be described.

PCF has a function to provide policy rules.

In addition, UDM has authentication information processing (Authentication credential processing) function, user identification processing function, access authentication function, registration / mobility management function, subscriber information management (subscription management) function, and the like.

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

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

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

[3. Explanation of various procedures and terms / identification information in each embodiment]
Next, before explaining the detailed procedures of the various procedures in each of the embodiments in the present embodiment, in order to avoid duplicate explanations, terms specific to the present embodiment and main identification information used in each procedure will be described in advance. Hereinafter, various procedures in each embodiment are also referred to as this procedure.

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

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 are sent and received between UE_A10 and SMF_A230 via AMF_A240. It may be a control message to be executed. In addition, SM messages include PDU session establishment request messages, PDU session establishment acceptance messages, PDU session completion messages, PDU session rejection messages, PDU session change request messages, PDU session change acceptance messages, PDU session change response messages, and the like. You may. In addition, the procedure for SM may include a PDU session establishment procedure.

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

In addition, the non 5GS 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 the relationship between the DN that provides the PDU connectivity service and the UE, but it is established between the UE and the external gateway. It may be connectivity. By establishing a PDU session via the access network_B and the core network_B in 5GS, the UE can send and receive user data to and from the DN using the PDU session. Here, the external gateway may be UPF, SCEF, or the like. The UE can use the PDU session to send and receive user data to and from devices such as application servers located in 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 other for the PDU session. Note that these identification information may include one or more of DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and other information. It may be further included. Further, when a plurality of PDU sessions are established, the identification information associated with the PDU session may have the same content or different contents.

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

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

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

In addition, 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 a network and is adopted or defined in 3GPP. NSI is an entity of NS that consists of one or more in core network_B. Further, NSI may be composed of a virtual NF (Network Function) generated by using NST (Network Slice Template). Here, NST is a logical representation of one or more NFs associated with a resource request to provide the required communication service or capability. In other words, the NSI may be an aggregate in the core network_B190 composed of a plurality of NFs. In addition, NSI may be a logical network configured to divide user data delivered by services or 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 the NS of. 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, SD may be information for interpolating SST when selecting one NSI from a plurality of NSIs represented by SST. S-NSSAI may be information peculiar to each PLMN, or may be standard information shared among PLMNs. In addition, the network may store one or more S-NSSAI in the UE registration information 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 included in NSSAI is information that assists the access network or core network in selecting NSI. The UE may memorize the NSSAI permitted from the network for each PLMN. Also, NSSAI may be the information used to select AMF.

Also, requested NSSAI is information including one or more S-NSSAI indicating one or more network slices that the UE wants to register. S-NSSAI included in requested NSSAI may be expressed as requested S-NSSAI.

Also, allowed NSSAI is information that includes one or more S-NSSAIs indicating one or more network slices allowed by the UE. The UE and the network each store and manage allowed NSSAI as UE information. S-NSSAI included in allowed NSSAI may be expressed as allowed S-NSSAI.

In addition, rejected NSSAI includes one or more S-NSSAI indicating one or more network slices that the network does not allow among S-NSSAI (s) included in requested NSSAI transmitted from the UE to the network. Further, for each S-NSSAI included in the rejected NSSAI, a reason value (cause) indicating the reason for refusal may be included in the rejected NSSAI. S-NSSAI included in rejected NSSAI may be expressed as rejected S-NSSAI.

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

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

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

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

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 IME ISV (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.

In addition, Non-Public Network (NPN) is a private network that is used by specific users for specific purposes, such as private use such as companies, not for general use. There are two types of NPN: Stand-alone Non-Public Network (SNPN) and Public network integrated NPN. When NPN is described below, it may mean both SNPN and Public network integrated NPN. The SNPN is operated by the NPN operator and is unaffected by the functional parts provided by PLMN. In other words, SNPN is an NPN-only network that is independent of PLMN, which is open to the public. In addition, Public network integrated NPN is executed by using the functional part of PLMN. In other words, the Public network integrated NPN is an NPN that is virtually realized within PLMN.

Furthermore, a detailed explanation of Public network integrated NPN will be given. Public network integrated NPN is an NPN that can be created via PLMN. The public network integrated NPN may be realized by using, for example, the network slice function. Specifically, this can be achieved by using the network slices assigned for the NPN. The public network integrated NPN may be identified by S-NSSAI or by a combination of S-NSSAI and CAG ID.

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

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

Here, the information indicating NPN is information identified by one or more of S-NSSAI and / or NID, and / or CAGID, and / or NID, and / or DNN, and / or PLMNID. It may be. Specifically, for example, the information indicating NPN may be information identified by S-NSSAI and CAGID, information identified by PLMNID and NID, or S-. The information may be identified by NSSAI and NID, or may be information identified by S-NSSAI and DNN. Alternatively, the information indicating the NPN may be S-NSSAI. In addition, "when the information indicating NPN includes the above information" includes "when the information indicating NPN is the above information". For example, "when the information indicating NPN includes S-NSSAI" includes "when the information indicating NPN is S-NSSAI".

A UE that can be connected with a high priority within the NPN is a UE that can preferentially request a connection within a specific NPN as a target of access control and is not restricted in sending and receiving control messages. Specifically, for example, UEs that can be connected with high priority within the NPN are AMF and / or SMF based on MM (Mobility Management) signal congestion or DNN (Data Network Name) -based congestion and / or network slice-based. Even in the state where congestion is detected and the congestion control procedure is started, the UE may be a UE whose request is not rejected because of congestion.

In this paper, UEs that can be connected with high priority in NPN are UEs that are allowed to connect with high priority in NPN, UEs that can be connected with high priority in NPN, and UEs in NPN. UE set with high priority in, UE registered with high priority in NPN, UE set as high priority UE in NPN, UE with high priority in NPN It may be expressed as UE, which is registered as. In addition, this NPN may be referred to as an NPN where the UE is allowed to connect with a higher priority.

Next, the identification information in this embodiment will be described.

The first information may be information indicating one or more required NPNs. The first information is identified by one or more of S-NSSAI and / or S-NSSAI and / or NID contained in requested NSSAI, and / or CAGID and / or NID, and / or DNN. Information may be used. Further, the first identification information may be an information group including a plurality of sets of combinations of a plurality of identification information. Specifically, for example, the first identification information may be a combination of a plurality of S-NSSAI and CAG ID. It may be a group of information including. The first information may be information indicating that the S-NSSAI requested by the UE is a slice for NPN.

The second information requires information indicating that the UE is a high priority UE within the NPN required by the UE and / or being registered as a high priority UE within the NPN required by the UE. It may be information indicating that. Alternatively, the second identification information is registered as information indicating whether or not the UE has a higher priority in the NPN required by the UE, and / or as a UE with a higher priority in the NPN requested by the UE. It may be information indicating whether or not to request that. The second information may be associated with the first information. When the first information is information indicating a plurality of NPNs, the second identification information may be associated with each NPN included in the first identification information. For example, when a plurality of S-NSSAIs are included in the first identification information, each S-NSSAI may indicate whether or not the UE is allowed to connect within the S-NSSAI with a high priority. Here, a UE having a high priority in the NPN may be synonymous with a UE that can be connected with a high priority in the NPN. The third identification information may be information indicating that the UE requests an NPN connection. The third identification information may be information indicating the NPN required by the UE, and may be, for example, the first identification information. Specifically, the third identification information may be information indicating a network slice for the NPN for which the UE requests a connection, and may be S-NSSAI included in requested NSSAI. Further, the third identification information may be information indicating that the UE is permitted to connect to the NPN, and may be, for example, the fourth identification information. The third identification information may also be a flag indicating that the UE requests a connection to the NPN. Further, the third identification information may be information obtained by combining a plurality of these pieces of information.

The fourth identification information may be UE capability information (UE capability). The fourth identification information may be information indicating that the UE is permitted to connect to the NPN, and may be information indicating one or more NPNs to which the UE is permitted to connect. Further, the fourth identification information may be information indicating that the UE can operate as a UE that is allowed to connect with a high priority within the requested NPN. The fourteenth identification information may be information indicating that the UE supports functions related to NPN.

The eleventh identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the eleventh identification information may be a list composed of information indicating one or more NPNs. The eleventh identification may be the information contained in the UE context. The eleventh identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The eleventh identification information may be information indicating that the connection is permitted with a high priority within the NPN requested by the UE.

The twelfth identification information may be information indicating rejected NSSAI and a reason value (cause value) indicating rejection due to congestion. The twelfth identification information may be identification information different from the information indicating rejected NSSAI, in which case the twelfth identification information may be a reason value (cause) indicating rejection due to congestion, and is rejected. It may be associated with S-NSSAI included in NSSAI.

The thirteenth identification information is information indicating the value of the back off timer. The AMF may store the thirteenth identification information in association with the UE and the network slice. The thirteenth identification information may be stored in association with rejected NSSAI.

The 14th identification information is information indicating that the UE is permitted to connect to the NPN. The fourteenth identification information may be information indicating the NPN for which the UE is permitted. When S-NSSAI is included in the information indicating NPN, the 14th identification information may be further information indicating that S-NSSAI contained in allowed NSSAI is S-NSSAI for NPN. The 14th identification information may be SST or SD included in S-NSSAI, or may be S-NSSAI included in allowed NSSAI. The 14th identification information may be information associated with S-NSSAI included in allowed NSSAI.

The fifteenth identification information may be network capability information (UE capability). The fifteenth identification information may be information indicating that the network supports the connection to the NPN. For example, if the NPN is identified by S-NSSAI, the fifteenth identification information indicates that the network does not support connecting to S-NSSAI for NPN. The fifteenth identification information may be a reason value (cause) included in rejected NSSAI.

The 21st identification information is information indicating that the UE is not a UE that can be connected with a high priority in the NPN requested by the UE. The 21st identification information may be a reason value (Cause value) indicating the reason for refusal. The 21st identification information may include information indicating the NPN to be rejected.

The 22nd identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the 22nd identification information may be a list composed of information indicating one or more NPNs. The 22nd identification may be the information contained in the UE context. The 22nd identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The 22nd identification information may be information indicating that the connection with high priority is refused within the NPN requested by the UE.

The 31st identification information is the NPN requested by the UE and is information indicating that the UE can be connected with a high priority. The thirty-first identification information may include information indicating one or more required NPNs. The thirty-first identification information may be information indicating a service type. Specifically, the 31st identification information may be a service type meaning that the UE is a UE that can be connected with a high priority.

The 41st identification information is information indicating the required NPN. The 41st identification information may be information indicating that the UE requests the establishment of a PDU session to the NPN. The 41st identification information may be information for requesting the network to perform an additional authentication / approval procedure for the NPN for each requested NPN. For the 41st identification information, the information indicating the required NPN and the information for requesting the network to execute an additional authentication / approval procedure for the NPN for each requested NPN are used as different information. May be good.

The 42nd identification information is information indicating that the UE is a UE set and / or registered as a UE that can be connected with a high priority within the requested NPN. The 42nd identification information may be associated with the 41st identification information. The 42nd identification information may be information for requesting the network to execute an authentication / approval procedure for NPN.

The 51st identification information is information indicating the NPN for which the establishment of a PDU session is permitted. The 51st identification information may be information indicating that the established PDU session is a PDU session established to the NPN and / or a PDU session established via the NPN. The 51st identification information may be information indicating NPN.

The 52nd identification information may be the result of performing additional authentication / approval procedures for NPN. The 52nd identification information may be information indicating that the connection to the NPN has been permitted as a result of the additional authentication / approval procedure for the NPN requested by the UE.

The 61st identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the 61st identification information may be a list composed of information indicating one or more NPNs. The 61st identification may be the information contained in the UE context. The 61st identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The 61st identification information may be information indicating that the UE is not a UE that can be connected with a high priority within the NPN requested by the UE. The 61st identification information may be a reason value (Cause value) indicating the reason for refusal.

The 62nd identification information indicates that the additional authentication / approval procedure for the NPN required by the UE does not allow the connection to the NPN as a result of the additional authentication / approval procedure for the NPN requested by the UE. Information. The 62nd identification information may be a cause value indicating that the UE's request is rejected because the connection to the NPN is not permitted.

The 71st identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the 71st identification information may be a list composed of information indicating one or more NPNs. The 71st identification may be the information contained in the UE context. The 61st identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The 71st identification information may be information notifying that an addition and / or deletion and / or change has occurred to the list of NPNs set as UEs to which the UE connects to the UE with high priority.

In addition, each device exchanges various capability information and / or various request information of each device in the notification information and / or RRC procedure and / or the registration procedure in the core network and / or the service request procedure for emergency call. / Or may be obtained.

In addition, each device involved in this procedure sends and receives one or more identification information included in each control message by transmitting and receiving each control message described in this procedure, and stores each transmitted and received identification information as a context. May be good.

For simplification, the service request procedure and / or the PDU session establishment procedure and / or the IMS registration procedure and / or the IMS emergency call connection procedure may be referred to as the emergency call connection process.

[3.1. Explanation of procedures used in each embodiment]
Next, the procedure used in each embodiment will be described. The procedures used in each embodiment include a registration procedure, a service request procedure, a PDU session establishment procedure, a PDU session management procedure, and a PDU session management procedure. Includes the Generic UE configuration update procedure. Each procedure will be explained below.

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

[3.2. Registration procedure]
First, the registration procedure will be described with reference to FIG. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering with the access network_B and / or the core network_B and / or the DN. The UE can execute this procedure at any time, for example, when the power is turned on, as long as it is not registered in the network. In other words, the UE can start this procedure at any time if it is in the unregistered state (RM-DEREGISTERED state). In addition, each device (particularly UE and AMF) can transition to the registration state (RM-REGISTERED state) based on the completion of the registration procedure.

In addition, the registration procedure is to update the UE location registration information in the network and / or to periodically notify the network of the UE status from the UE and / or to update 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 start this procedure when the running timer expires. In addition, the UE may initiate the registration process when the context of each device needs to be updated due to disconnection or invalidation of the PDU session. In addition, the UE may initiate the registration process if there is a change in the ability 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 be based on the completion of the UE configuration update procedure, or on the basis of the completion of the registration procedure, or on the basis of the completion of the PDU session establishment procedure, or on the basis of the completion of the PDU session management procedure, or in each procedure. The registration procedure may be initiated based on the information received from the network. The UE is not limited to these, and can execute the registration procedure at any timing.

First, before UE_A10 starts the registration procedure, 5GAN120 (or gNB_A122) sends broadcast information to neighboring UEs (S601). The broadcast information may be SIB (System Information Block). 5GAN120 (or gNB_A122) may transmit the broadcast information including PLMNID and / or CAGID and / or NID. The CAG ID and NID may be associated with the PLMN ID. Specifically, for example, if 5GAN120 (or gNB_A122) is a device in the access network for SNPN, 5GAN120 (or gNB_A122) includes the PLMN ID for NPN and one or more NIDs in the broadcast information. , 5GAN120 (or gNB_A122) may be sent to the UE in the cell.

Or, if 5GAN120 (or gNB_A122) is a device in the access network for Public network integrated NPN, gNB_A122 or eNB_B145 broadcasts PLMN ID indicating PLMN including Public network integrated NPN and one or more CAG IDs. May be sent to the UE in the cell of 5GAN120 (or gNB_A122) included in.

Also, if the 5GAN120 (or gNB_A122) is not an NPN-only access network, that is, if the NPN and another PLMN share an access network, the 5GAN120 (or gNB_A122) will include the CAG ID and / in the broadcast information. Alternatively, it may be sent to the UE in the cell of 5GAN120 (or gNB_A122) without including the NID.

UE_A10 may decide to request registration with NPN and / or PLMN based on the received broadcast information and / or one or more pieces of information contained in the broadcast information, and may start the following registration procedure.

First, the UE starts the registration procedure by sending a registration request message to AMF (S600) (S602) (S604). Specifically, the UE sends an RRC message including a registration request message to 5GAN (or gNB) (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 5GAN (or gNB). In addition, NAS messages are processed at the NAS layer, and RRC messages are processed at the RRC layer. The NAS layer is a higher layer than the RRC layer.

Here, the UE can transmit at least one of the identification information of the first to the fourth identification information by including it in the registration request message and / or the RRC message, but a control message different from these. For example, it may be included in a control message of a layer lower than the RRC layer (for example, MAC layer, RLC layer, PDCP layer) and transmitted. By transmitting these identification information, the UE may indicate that the UE supports each function, may indicate a request of the UE, or may indicate both of them. .. 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 the UE requests a connection to the NPN and / or decides to request a connection to the NPN and / or selects the connection destination as the NPN based on a request from a higher layer such as the application layer, the first You may send 1 request. The UE may send the first identification information to the network without recognizing that the requesting network is NPN. By transmitting the first identification information, the UE can initiate the authentication / approval procedure for the connection to the NPN shown in the first identification information by using the UE ID included in the registration request message to AMF. Good. Further, by transmitting the first identification information, the UE may have the AMF confirm the setting information of the UE. Specifically, the AMF may confirm whether or not the connection is permitted with a high priority in association with the UE and the requested NPN based on the reception of the first identification information.

In addition, if the UE requests a connection to an NPN and / or is configured as a UE that is allowed to connect with a higher priority within the NPN requested by the UE, and / or within the NPN requested by the UE. If you request to be registered as a UE that allows connections with high priority, you may send a second identification. If the UE requests connection to the NPN but does not require registration as a UE that connects with a high priority within the requested NPN, it is not necessary to transmit the second identification information. By transmitting the second identification information, the UE may have the AMF confirm whether the connection is permitted with a high priority within the NPN requested by the UE.

Furthermore, the UE may send a third identification information when requesting an NPN connection. The UE may indicate to the network that the network requested by the UE is an NPN by transmitting a third identification information. By transmitting the third identification information, the UE may have the AMF confirm that the network slice requested by the UE is a network slice for NPN.

Furthermore, the UE may send a fourth identification information if it requests a connection to the NPN and / or if the UE supports the ability to connect to the NPN. By transmitting the fourth identification information, the UE may have the AMF confirm the network capability information (Network capability).

The first to fourth identification information stored by the UE is the information acquired by the UE in the procedure before this procedure and / or the information generated by the UE based on the information acquired in the procedure before this procedure. You can. Specifically, for example, when S-NSSAI is included in the first identification information, the UE has received allowed NSSAI from the network in the procedure before this procedure, and the S-NSSAI included in the first identification information is , It may be S-NSSAI included in allowed NSSAI to be memorized.

The procedure before this procedure is, for example, that this procedure updates the location registration information of the UE and / or periodically notifies the network of the status of the UE from the UE, and / or relates to the UE in the network. If it is a registration procedure for updating a specific parameter, it may be a registration procedure that has occurred before this procedure.

The UE may include other than the identification information 1 to 4 in the registration request message and / or the RRC message including the registration request message, for example, UE ID and / or PLMN ID and / or requested NSSAI and / or CAG ID. And / or NID may be included in the transmission.

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

When 5GAN (or gNB) receives an RRC message including a registration request message, it selects the AMF to which the registration request message is forwarded (S602). Note that 5GAN (or gNB) can select AMF based on the information contained in the registration request message and / or RRC message. Specifically, 5GAN (or gNB) may select the AMF in the NPN required by the UE based on at least one of the identification information of the first to the fourth identification information. For example, 5GAN (or gNB) may select the AMF included in the NPN shown in the first identification information based on the first identification information, or support the NPN shown in the first identification information. You may select the AMF to be used. In that case, the exchange of information on NPN including AMF and / or supported by AMF occurs in advance between 5GAN (or gNB) and AMF, or notification from AMF to 5GAN (or gNB) occurs. There is.

The selection method of AMF is not limited to this, and 5GAN (or gNB) may select AMF based on other conditions. 5GAN (or gNB) extracts the registration request message from the received RRC message and forwards 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 requested to be registered in the selected AMF. It may be forwarded with the message (S604).

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

The first condition determination is the reception of the registration request message and / or each identification information contained in the registration request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and It may be executed based on / or the state of the network and / or the user's registration information and / or the context held by AMF. For example, if the network allows the UE request, the first condition determination is true, and if the network does not allow the UE request, the first condition determination may be false. Also, if the network to which the UE is registered and / or the devices in the network support the functions required by the UE, the first condition determination is true and does not support the functions required by the UE. In this case, the first condition determination may be false. Further, if the transmitted / received identification information is permitted, the first conditional determination may be true, and if the transmitted / received identification information is not permitted, the first conditional determination may be false. In addition, if the AMF restricts the transmission and reception of mobility management messages such as registration procedures based on congestion, the UE will also give higher priority within the network (PLMN and / or NPN) to which the AMF belongs. If the UE is not allowed to connect, the first condition is false and the UE is a UE that is allowed to connect with high priority within the network (PLMN and / or NPN) to which AMF belongs. , The first condition determination may be true. The condition for determining the truth of the first condition determination does not have to be limited to the above-mentioned condition.

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

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

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

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

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

AMF may send the registration acceptance message including at least one or more of the identification information of the 11th to 15th identification information. The AMF may indicate that the network supports each function by sending these identification information and / or the registration acceptance message, or may indicate that the UE request has been accepted. Alternatively, information that combines these may be shown. 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.

The AMF receives at least one of the first to fourth identification information from the UE, and / or when the UE setting information is updated, at least one of the eleventh to fifteenth identification information. May be sent.

The UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the eleventh identification information. The high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority. Here, when S-NSSAI is included in the information indicating the NPN, the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list. Specifically, when the information indicating the NPN includes S-NSSAI, the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority. , Allowed NSSAI or Configured NSSAI or rejected NSSAI, even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.

The UE may update the NSSAI information when it receives the twelfth identification information. Specifically, the UE may manage the S-NSSAI included in the received rejected NSSAI as a congested state based on the reason value. Further, the UE may start counting the backoff timer based on the reception of the twelfth identification information. The backoff timer may be a value received from the network or information held in advance by the UE.

If S-NSSAI is included in the information indicating the NPN, and if the UE is a UE that is allowed to connect with a high priority within the NPN supported by the rejected S-NSSAI, the twelfth It is not necessary to start the back-off timer even if the identification information of is received.

The UE may start counting the backoff timer by receiving the thirteenth identification information. If S-NSSAI is included in the information indicating the NPN, and if the UE is a UE that is allowed to connect with high priority within the NPN supported by the rejected S-NSSAI, the 13th It is not necessary to start the back-off timer even if the identification information of is received.

The UE may update the setting information of the UE by receiving the 14th identification information. Specifically, the UE stores information that identifies the NPN that the UE is authorized to use, based on the 14th identification information. If S-NSSAI is included in the information that identifies the NPN, the memory related to NSSAI may be updated. Specifically, the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN, or the NPN is indicated by the corresponding S-NSSAI in the list of allowed NSSAI, Configured NSSAI, or rejected NSSAI. A flag indicating that it is S-NSSAI may be associated and stored.

The UE may detect and store that the network supports the connection to the NPN based on the reception of the fifteenth identification information. The UE may initiate the registration process with the NPN based on the receipt of the fifteenth identification information, or to transition to a state in which the establishment of a PDU session via (or to the NPN) is permitted via the NPN. You may start the registration procedure.

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

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

For example, the AMF may send the eleventh identity when the UE changes the list of NPNs that are allowed to connect with a high priority, that is, when the context held by the AMF is updated. Good.

For example, when the AMF receives the requested NSSAI from the UE and does not include the S-NSSAI included in the requested NSSAI requested by the UE in the allowed NSSAI, the AMF may transmit the twelfth identification information. For example, the AMF may transmit the fifteenth identification information when it receives the fourth identification information from the UE.

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

In addition, 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 UE request has been accepted by sending the registration acceptance message based on the context held by the AMF.

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

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

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

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

Note that the AMF may indicate that the UE request by the registration request message has been rejected by sending the registration refusal message. The AMF may send at least one of the 21st to 22nd identification information by including it in the registration refusal message and / or NAS message and / or RRC message. The AMF may transmit at least one of the 21st to 22nd identification information based on the reception of at least one of the 1st to 4th identification information.

Furthermore, AMF may include the value of the backoff timer in the registration refusal message and send it. Note that the AMF may send a registration refusal message without including the value of the backoff timer when the UE is allowed to connect with a high priority within the NPN requested by the UE.

The UE may detect that the connection is not permitted within the NPN requested by the UE with a high priority based on the reception of the 21st identification information. Further, the UE may update the memory of the information indicating the NPN based on the reception of the 21st identification information. Specifically, based on the reception of the 21st identification information, the UE may associate the information indicating the rejected NPN with the information indicating that the connection is not permitted with a high priority, or the UE may be rejected. If the information indicating NPN is linked to the information indicating that connection is permitted with high priority, even if the information indicating that connection is permitted with high priority is released from the information indicating NPN. Good.

Furthermore, specifically, if the information indicating the NPN includes S-NSSAI, the UE may delete the rejected S-NSSAI from the list of possible high priority connections and store it. , The flag indicating that the connection is possible with a high priority to be remembered in association with the rejected S-NSSAI may be removed.

The UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the 22nd identification information. The high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority. Here, when S-NSSAI is included in the information indicating the NPN, the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list. Specifically, when the information indicating the NPN includes S-NSSAI, the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority. , Allowed NSSAI or Configured NSSAI or rejected NSSAI, even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.

In addition, each process that the UE shown above executes based on the reception of each identification information may be executed during or after the completion of this procedure, or may be executed based on the completion of this procedure after the completion of this procedure. Good. The UE receives a registration refusal message via 5GAN (gNB) (S612). By receiving the registration refusal message, the UE can recognize that the UE request by the registration request message has been rejected and the contents of various identification information included in the registration refusal message. In addition, the UE may recognize that the request of the UE has been rejected if the registration acceptance message or the registration refusal message is not received within a predetermined period after sending the registration request message. .. Each device completes the procedure (B) during this procedure based on the transmission and reception of the registration refusal message.

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

Each device completes the registration procedure based on the completion of the procedure (A) or (B) in Fig. 6. In addition, each device may transition to the state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure (A) in FIG. 6, or the procedure in (B) in FIG. 6 is completed. The UE may remain unregistered in the network (RM_DEREGISTERED state), or the UE may transition to a state in which it is not registered in the network. Further, the transition of each device to each state may be performed based on the completion of the registration procedure, or may be performed based on the establishment of the PDU session.

Furthermore, each device may perform processing based on the information sent and received in the registration procedure based on the completion of the registration procedure. For example, when sending and receiving information indicating that a part of the UE's request is rejected, the reason why the UE's request is rejected may be recognized. Further, each device may perform this procedure again based on the reason why the UE request is rejected, or may perform the registration procedure for the core network_A or another cell.

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

For example, when the UE receives the twelfth identification information and / or the thirteenth identification information, the rejected S-NSSAI shown in the twelfth identification information is allowed to connect with the UE having a high priority. If it is not included in the information indicating the NPN, the UE may start the backoff timer, and while the backoff timer is counting, the transmission of the registration request message including the rejected S-NSSAI may be stopped. Alternatively, the UE manages the rejected S-NSSAI as the rejected S-NSSAI while counting the backoff timer, and stores the rejected S-NSSAI as the configured NSSAI after the count of the backoff timer ends. May be good.

Further, for example, when the UE receives the twelfth identification information and / or the thirteenth identification information, the rejected S-NSSAI further shown in the twelfth identification information allows the UE to connect with a high priority. If it is included in the information indicating the NPN to be used, the UE does not start counting the backoff timer, but then starts the registration procedure again by sending a registration request message containing the rejected S-NSSAI. May be good. Or, in that case, the UE starts counting the backoff timer, but based on the fact that the UE is a UE that is allowed to connect with high priority in the NPN even while the backoff timer is counting. , You may start the registration procedure.

Also, for example, if the UE receives the eleventh and / or the fourteenth and / or fifteenth identity, the UE will have a PDU session to establish a PDU session to the authorized NPN. The establishment procedure may be initiated.

Further, for example, when the UE receives the registration acceptance message and / or the 11th identification information and / or the 14th identification information and / or the 15th identification information, the UE further transitions from the connected state to the idle state. If so, the service request procedure for resuming the connection to the NPN may be initiated.

[3.3. Outline of service request procedure]
Next, the outline of the service request procedure will be described with reference to FIG. Hereinafter, the service request procedure is also referred to as this procedure. The service request procedure is a procedure for the UE to transition from the idle state (5GMM-IDLE) to the connected state (CONNECTED mode). The UE may initiate a service request triggered by retention of user data or paging or notification from the network.

The UE may be in a state where it has received the registration acceptance message and completed the registration procedure before starting the service request.

First, the UE sends a service request message to AMF (S700). The service request message is a NAS message sent and received on the N1 interface, but it is included in the RRC message and sent and received between the UE and 5GAN (gNB).

Here, the UE may send the 31st identification information by including it in the service request message and / or the RRC message including the service request message. 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.

If the UE is a UE that is allowed to connect with a high priority within the requesting NPN, it will send a service request message and / or the 31st identification information even while the backoff timer is counting. May be good.

The UE may indicate that it requests the AMF to connect to the NPN by sending the 31st identification information, and further, on the UE that is allowed to connect with a high priority within the NPN requested by the UE. It may be shown that there is.

When the AMF receives the service request message, it executes the first process (S702). In the first process, the AMF decides whether to accept the UE's service request. In the first process, the AMF executes the procedure (A) in FIG. 7 when accepting the service request of the UE. On the other hand, when the AMF rejects the UE service request in the first process, it executes the procedure (B) in FIG. 7. The method of determining whether or not to accept the service request from the UE by the first process is to receive the service request message and / or each identification information contained in the service request message and / or the subscriber information and /. Alternatively, it may be determined based on network capability information and / or operator policy and / or network status and / or user registration information and / or context held by AMF.

For example, AMF is performing mobility management congestion control and / or DNN-based congestion control and / or S-NSSAI-based congestion control based on the 31st identification information of the UE. The request does not have to be rejected due to congestion.

In other words, based on the 31st identification information, AMF does not send a rejection message including a backoff timer to the UE even if congestion control is active. The determination of whether or not to accept the UE service request is not limited to the method described above.

First, the case where AMF accepts the UE service request will be described. The AMF receives the service request message and / or sends a service acceptance message to the UE based on the first process (S704).

Next, the case where AMF rejects the UE service request will be described. The AMF receives the service request message and / or sends a service rejection message to the UE based on the first process (S706).

Each device completes the service request procedure based on the completion of the procedure (A) or (B) in Fig. 7. In addition, each device is connected from the state where the N1 interface used for sending and receiving NAS messages is not connected (CM-IDLE) to the state where it is connected (CM-CONNECTED) based on the completion of the procedure (A) in FIG. May transition to.

Alternatively, each device may maintain a state in which the N1 interface used for sending and receiving NAS messages is not connected (CM-IDLE) based on the completion of the procedure (B) in FIG.

Furthermore, each device may perform processing based on the information sent and received in the service request procedure based on the completion of the service procedure. Further, each device may perform this procedure again based on the reason why the UE request is rejected, or may perform the registration procedure for the core network_A or another cell.

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

For example, the UE may start the registration procedure based on the receipt of the service acceptance message.

[3.4. PDU session establishment procedure]
Next, an outline of the PDU session establishment procedure performed to establish a PDU session for a DN will be described with reference to FIG. The PDU session establishment procedure is a procedure in 5GS. Hereinafter, this procedure refers to the procedure for establishing a PDU session. The PDU session establishment procedure is a procedure for each device to establish a PDU session. In addition, each device can start the PDU session establishment procedure at an arbitrary timing when the registration procedure is completed and the registration state is reached. In addition, each device may be able to execute the PDU session establishment procedure in the registration procedure. In addition, each device may establish a PDU session based on the completion of the PDU session establishment procedure. The PDU session establishment procedure may be a procedure initiated by the UE, or may be a procedure requested and initiated by the UE. Each device can establish a plurality of PDU sessions by executing the PDU session establishment procedure a plurality of times. For example, if the UE requires that a PDU session be established through multiple NPNs, the UE may initiate a PDU session establishment procedure for each requested NPN.

Furthermore, the UE may start the PDU session establishment procedure based on the identification information received in the registration procedure. For example, in the registration procedure, if the UE receives information indicating NPN, the UE may start this procedure.

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

Specifically, the UE sends a NAS message including a PDU session establishment request message to AMF via 5GAN (gNB) via the N1 interface (S800).

Here, the UE can transmit one or more of the identification information of at least the 41st to 42nd including the identification information in the PDU session establishment request message and / or the NAS message, but the control is different from these. The message may be included in the control message of a layer lower than the RRC layer (for example, MAC layer, RLC layer, PDCP layer) and transmitted. These identifications may be included in these messages to indicate the UE's request. Further, two or more identification information of these identification information may be configured as one or more identification information.

In addition to the identification information of Nos. 41 to 42, the UE includes the UE ID and / or PLMN ID and / or requested S-NSSAI and / or CAG ID and / or NID in the PDU session establishment request message and / or RRC message. May be sent.

The UE may indicate that it requests a connection to the NPN by transmitting the 41st identification information. The UE may transmit the 41st identification information if it is allowed to connect to the NPN and / or if it remembers that the UE is a UE that is allowed to connect to the NPN. Specifically, for example, if the information indicating NPN includes S-NSSAI, and if the allowed NSSAI stored by the UE includes S-NSSAI for NPN, the UE may send the 41st identification information. Good. Also, for example, if the information indicating the NPN includes a DNN, and the UE requests the establishment of a PDU session to the DNN for the NPN, the UE may transmit the 41st identification information.

AMF receives a NAS message including a PDU session establishment request message (S800). At this time, the AMF may be performing DNN-based and / or S-NSSAI-based congestion control. Note that DNN-based and / or S-NSSAI-based congestion control is control that starts when AMF and / or SMF detects the congestion state of the Session Management message for DNN and / or S-NSSAI. It may be.

Based on the reception of the PDU session establishment request message and / or the NAS message, the AMF determines the fifth condition of whether to transfer the received PDU session establishment request message to the SMF. If the result of the fifth condition determination is true, each device executes the procedure after S802. If the result of the fifth condition determination is false, AMF sends a rejection message to the UE using the NAS message (S801).

The fifth 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.

Specifically, when S-NSSAI is included in the information that identifies the NPN, when the UE requests S-NSSAI for NPN, and when the further required S-NSSAI-based congestion control occurs. , Check if the UE is a UE that can connect with a high priority within the NPN or S-NSSAI associated with the S-NSSAI requested by the UE, and the UE has a high priority within the NPN or S-NSSAI. If it is a UE that can be connected with, the fifth condition determination is true, and if it is not a UE that can be connected with high priority within NPN or S-NSSAI, the fifth condition determination is false.

First, the case where the fifth condition determination is false will be described. If the fifth condition determination is false, AMF sends a rejection message (S801). The AMF includes the received PDU session establishment request message and the reason value (Cause value) indicating the reason for refusal in the rejection message. The AMF may also send the rejection message with the value of the backoff timer included.

However, AMF does not need to include the value of the backoff timer when sending a rejection message when the UE remembers that it is a UE that can be connected with high priority within NPN or S-NSSAI. In other words, the AMF may send a rejection message to the UE containing the value of the backoff timer if the UE is not a UE that can be connected with high priority within NPN or S-NSSAI (S801).

Next, the case where the fifth condition determination is true will be described. AMF executes S802 or later if the fifth condition determination is true.

First, AMF extracts the PDU session establishment request message from the NAS message and selects SMF as the transfer destination of the PDU session establishment request message (S802). In addition, AMF indicates each identification information and / or subscriber information contained in the PDU session establishment request message and / or NAS message, and / or network capability information, and / or operator policy, and / or network status. And / or the transfer destination SMF may be selected based on the user's registration information and / or the context held by the AMF.

For example, the AMF may select an SMF in the NPN requested by the UE or an SMF supporting the NPN requested by the UE based on the received 41st identification information, or the S-NSSAI indicated by the 41st identification information. The SMF contained in may be selected, or the SMF that supports the connection to the DNN indicated by the 41st identification information may be selected.

AMF forwards the PDU session establishment request message to the selected SMF via the N11 interface (S804). When AMF receives one or more of the identification information of Nos. 41 to 42 in the RRC message instead of the PDU session establishment request message, the AMF may transfer the received information to the SMF together with the PDU session establishment request message. ..

When the SMF receives the PDU session establishment request message (S804), it recognizes various identification information included in the PDU session establishment request message. Then, the SMF executes the third condition determination. The third condition determination is for the SMF to determine whether or not to accept the UE request. In the third condition determination, the SMF determines whether the third condition determination is true or false. The SMF starts the procedure (A) in FIG. 7 when the third condition determination is true, and starts the procedure (B) in FIG. 8 when the third condition determination is false.

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

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

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

For example, the SMF may select the UPF in the NPN requested by the UE based on the received 41st identification information. The UPF selection method is not limited to this, and the SMF may select the UPF based on other conditions.

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

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

The SMF may perform additional authentication / approval procedures for the NPN required by the UE based on the receipt of the 41st identification information and / or the 42nd identification information.

The SMF receives the PDU session establishment request message, and / or selects the UPF, and / or receives the session establishment response message, and / or the UE via the AMF based on the completion of the address assignment of the address assigned to the UE. Sends a PDU session establishment accept message to (S810) (S812).

Specifically, when the SMF sends a PDU session establishment acceptance message to the AMF via the N11 interface (S810), the AMF that receives the PDU session establishment request message establishes a PDU session to the UE via the N1 interface. Send a NAS message containing an acceptance message (S812). The PDU session establishment acceptance message may be a NAS message and may be a response message to the PDU session establishment request. In addition, the PDU session establishment acceptance message can indicate that the PDU session establishment has been accepted.

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

The SMF and AMF may send the PDU session establishment acceptance message including at least one of the identification information items 51 to 52. Note that the SMF and AMF may indicate that the network supports each function by sending these identification information and / or the PDU session establishment acceptance message, and the UE request has been accepted. May be indicated. Further, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.

The UE may detect that the PDU session to the NPN requested by the UE has been established by receiving the 51st identification information, and the established PDU session is a PDU session to the NPN. May be detected.

The UE may detect that the PDU session to the NPN requested by the UE has been established by receiving the 52nd identification information, and the established PDU session is a PDU session to the NPN. May be detected, or it may be detected that authentication / authorization for the requested connection to the NPN has been completed.

It should be noted that the SMF and AMF include at least which of the 51st to 52nd identification information is included in the PDU session establishment acceptance message of each of the received identification information and / or subscriber information, and / or the network. Selection and determination may be made based on capability information and / or operator policy and / or network status and / or user registration information and / or context held by AMF.

For example, the SMF may transmit the 52nd identification information based on the reception of the 41st identification information from the UE. Specifically, if the SMF determines that additional authentication / approval is required for the NPN requested by the UE based on the 41st identification information, it executes the authentication / approval procedure, and the 52nd execution result is the execution result. The identification information may be sent to the UE.

The method by which SMF and AMF determine which identification information is included in the PDU session establishment acceptance message is not limited to the above.

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

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

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

When the UE receives the NAS message including the PDU session establishment acceptance message from the AMF via the N1 interface (S812), the UE sends the PDU session establishment completion message to the SMF via the AMF (S814) (S816). By receiving the PDU session establishment acceptance message, the UE can detect that the UE request by the PDU session establishment request has been accepted.

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

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

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

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

Each device sends and receives a PDU session establishment acceptance message and / or sends and receives a PDU session establishment completion message, and / or sends and receives a session change response message, and / or sends and receives a session establishment response message. Complete the procedure (A) inside. When the procedure (A) during this procedure is completed, the UE is in a state where a PDU session for the DN has been established.

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

The PDU session establishment refusal message may be a NAS message. Further, the PDU session establishment refusal message may be any message indicating that the establishment of the PDU session has been rejected.

Here, the SMF may indicate that the UE request by the PDU session establishment request has been rejected by sending the PDU session establishment refusal message. In addition, the SMF may send at least one of the 61st to 62nd identifications in the PDU session establishment refusal message. In addition, the SMF may include the value of the backoff timer in the PDU session establishment rejection message and send it. The SMF may transmit at least one of the 61st to 62nd identification information based on the fact that the SMF has received at least one of the 41st to 42nd identification information.

The UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the 61st identification information. The high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority. Here, when S-NSSAI is included in the information indicating the NPN, the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list. Specifically, when the information indicating the NPN includes S-NSSAI, the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority. , Allowed NSSAI or Configured NSSAI or rejected NSSAI, even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.

The UE may store a setting that does not send a request to establish a PDU session via (or to the NPN) the rejected NPN based on the 61st identification information.

The UE may recognize that the additional authentication / approval procedure for the NPN requested by the UE has not been completed based on the 62nd identification information, and the UE may recognize that the additional authentication / approval procedure for the NPN requested by the UE has not been completed. You may remember the state in which the procedure has not been completed.

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

Further, each device may perform processing based on the information transmitted / received in the PDU session establishment procedure based on the completion of the PDU session establishment procedure and the occurrence of each step in the PDU session establishment procedure.

For example, when each device transmits / receives information indicating that a part of the UE's request is rejected, it may recognize the reason why the UE's request is rejected. Further, each device may perform this procedure again based on the reason why the UE request is rejected, or may perform the PDU session establishment procedure for another cell.

For example, in each device, the SMF sends a PDU session establishment acceptance message and / or sends and receives the 51st identification information, and / or sends and receives the 52nd identification information, and / or completes (A) of FIG. Based on, the management information of the UE (for example, the UE context) may remember that the UE is a UE that is allowed to connect with a high priority in the NPN.

Further, for example, if a device in the core network remembers the UE as a UE that is allowed to connect in the NPN with high priority, the SMF sends a PDU session establishment acceptance message and / or ( Based on the completion of A), the backoff timer value is added to the PDU session modification rejection message (PDU session modification reject message) and / or the PDU session deletion command message (PDU session release command message) for the PDU session established by this procedure. Does not include.

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

For example, the UE may recognize and remember that the established PDU session is an established PDU session via the NPN based on the receipt of the 51st identification information.

For example, the UE may recognize and remember that the authentication / approval procedure for the NPN via the established PDU session has been completed based on the reception of the 52nd identification information.

Furthermore, the UE may store the received identification information, or may execute each procedure after this procedure based on the recognition of the network decision.

For example, if the UE recognizes and remembers that the authentication / approval procedure for the NPN has been completed, or if it wants to establish a PDU session establishment request message via (or to the NPN) the same NPN, No need to require additional certification / approval procedures.

[3.5. UE setting update procedure]
Next, the UE configuration update procedure will be described with reference to FIG. Hereinafter, the UE setting update procedure is also referred to as this procedure. This procedure is a procedure for the core network to update the UE setting information. This procedure may be a procedure for mobility management that the network takes the initiative to execute for the UE registered in the network.

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

Furthermore, the trigger of this procedure may be a change of state of the UE managed by the network, specifically, even if there is a change in the list of NPNs that the UE is allowed to connect to with high priority. Good. Furthermore, the state change of the UE managed by the network may be executed based on the request from the application.

In addition, each device sends and receives a message containing identification information for changing the setting information of the UE and / or identification information for stopping or changing the function executed by the UE during this procedure. May be good. Further, each device may update the setting information to the setting instructed by the network based on the completion of this procedure, or may start the behavior instructed by the network.

The UE may update the setting information of the UE based on the control information transmitted and received by this procedure. Further, the UE may stop the function being executed or start a new function as the setting information of the UE is updated. In other words, the device in the core network leads this procedure, and further, by transmitting the control message and control information of this procedure to the UE, the setting information of the UE that can be identified by using these control information can be obtained. , UE may update. Further, the device in the core network may stop the function executed by the UE or cause the UE to start a new function by updating the setting information of the UE.

First, AMF starts the UE setting update procedure by sending a configuration update command message to the UE via 5GAN (or gNB) (S900).

AMF may send the setting update command message including at least the 71st identification information. The AMF may indicate the new UE setting information by transmitting the 71st identification information, or may request the update of the UE setting 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.

Note that AMF will include at least the 71st identification information in the configuration update command message for each received identification information and / or subscriber information and / or network capability information and / or operator policy and /. Alternatively, it may be selected and determined based on the state of the network and / or the user's registration information and / or the context held by the AMF.

In addition, AMF also receives each identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user registration information and / or A request for updating the setting information of the UE may be indicated by sending a setting update command message based on the context held by the AMF.

The UE receives the setting update command message via 5GAN (gNB) (S900). The UE may update the UE configuration information based on the configuration update command message and / or the identification information contained in the configuration update command message.

The UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the 71st identification information. The high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority. Here, when S-NSSAI is included in the information indicating the NPN, the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list. Specifically, when the information indicating the NPN includes S-NSSAI, the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority. , Allowed NSSAI or Configured NSSAI or rejected NSSAI, even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.

In addition, each process that the UE shown above executes based on the reception of each identification information may be executed during or after the completion of this procedure, or may be executed based on the completion of this procedure after the completion of this procedure. Good. Furthermore, the UE sends a configuration update complete message to the AMF via 5GAN (gNB) as a response message to the configuration update command message based on the identification information contained in the configuration update command message. May (S902).

AMF receives the setting update completion message via 5GAN (gNB) when the UE sends the setting update completion command message (S902). In addition, each device completes this procedure based on the transmission / reception of the setting update command message and / or the setting update completion message.

Furthermore, each device may perform processing based on the information transmitted and received in this procedure based on the completion of this procedure. For example, when the update information for the setting information is transmitted and received, each device may update the setting information. Furthermore, if the UE sends and receives information indicating that the registration procedure needs to be performed, the UE may start the registration procedure based on the completion of this procedure.

Furthermore, the UE may store the identification information received together with the setting information command message based on the completion of this procedure, or may recognize the network decision.

For example, the UE may recognize and remember one or more NPNs that the UE is allowed to connect to at a higher priority based on the completion of this procedure and / or the receipt of the 71st Identification Information. You may.

Further, for example, the UE may perform registration procedures, and / or service request procedures, and / or PDU session establishment request procedures, and / or PDU session establishment request procedures, based on the information of one or more NPNs in which the stored UE is allowed to connect with high priority. / Or the PDU session change procedure may be performed.

Specifically, the UE establishes a registration request message, a service request message, and / or a PDU session, which includes information indicating an NPN to which the UE is allowed to connect with a high priority based on the reception of the 71st identification information. Each procedure may be started by sending a request message and / or a PDU session modification request message (PDU session modification request message).

Also, based on the completion of this procedure, each procedure may be executed based on the stored information. Specifically, the procedure for establishing a PDU session via (or to) an NPN that allows the UE to connect with a high priority, and / or the procedure for changing the PDU session, and / or deleting the PDU session, which the UE remembers. Registration request message, service request even when the backoff timer value is received from the network in the procedure, the backoff timer does not have to start counting, or the backoff timer is being counted. A message and / or a PDU session establishment request message and / or a PDU session change request message (PDU session modification request message) can be transmitted.

In the above procedure, by sending and receiving the setting update command message, the device in the core network can instruct the UE to update the setting information that the UE has already applied, and the UE is executing it. You can instruct to stop or change the function.

[4. Each embodiment]
Each embodiment of the present invention will be described below.

[4.1. First Embodiment]
Next, the first embodiment will be described. Hereinafter, the first embodiment will be referred to as the present embodiment. In this embodiment, an embodiment in which each device completes registration for the NPN requested by the UE even when the AMF is in congestion control or the UE is counting in the backoff timer will be described. ..

The initial state of the communication procedure of the present embodiment may be a state in which the AMF detects a congestion state at the NAS level and starts congestion control.

Each device in the initial state executes the first registration procedure started by the UE. The first registration procedure may be the registration procedure in Chapter 3.2. In the first registration procedure, the UE sends the AMF a first registration request message containing at least one of the first to fourth identifications. In other words, it receives a first registration request message that includes at least one of the first to fourth identifications.

Subsequently, the UE completes the first registration procedure by receiving a registration refusal message containing at least one of the 21st to 22nd identification information from the AMF. In other words, the AMF completes the first registration procedure by sending a registration refusal message containing at least one of the 21st to 22nd identification information. In addition, AMF may include information indicating congestion as a reason value in the registration refusal message. Further, the AMF may include the value of the backoff timer in the registration refusal message, or may not include the value of the backoff timer based on the UE information.

Based on the completion of the first registration procedure and the receipt of the 21st to 22nd identification information, the UE recognizes and remembers that the UE is a UE that is allowed to connect with high priority within the NPN requested by the UE. You may. Furthermore, based on the receipt of the reason value for rejection, the UE recognizes that it has been rejected by AMF for reasons of congestion. Further, the UE may start or execute counting of the backoff timer based on the reception of the value of the backoff timer. Alternatively, the UE may receive the value of the backoff timer or not start counting the backoff timer based on the stored information of the UE.

The UE may start the second registration procedure even while the backoff timer is counting, based on the stored information of the UE. The second registration procedure may be the registration procedure in Chapter 3.2. In the second registration procedure, the UE sends the AMF a first registration request message containing at least one of the first to fourth identifications. In other words, it receives a first registration request message that includes at least one of the first to fourth identifications.

Subsequently, the UE completes the second registration procedure by receiving a registration acceptance message containing at least one of the 11th to 15th identification information from the AMF. In other words, the AMF completes the second registration process by sending a registration acceptance message containing at least one of the 11th to 15th identifications.

By the above procedure, each device completes the UE registration procedure for the NPN required by the UE even if the AMF is in congestion control. In addition, completing the UE registration procedure for the NPN requested by the UE may mean transitioning to the registration state for the NPN requested by the UE, or the NPN required by the UE. You may transition to a state where the establishment of a PDU session via (or to the NPN) is allowed.

In the first embodiment, by executing the first registration procedure and the second registration procedure, each device registers with respect to the NPN requested by the UE even when the AMF is in congestion control. However, each device is not limited to the method of completing the registration for the NPN requested by the UE even when the AMF is in congestion control. For example, each device may complete registration for the NPN requested by the UE, even if the AMF is in congestion control, with only a second registration procedure.

In the first embodiment, after the completion of the second registration procedure, each device performs the service request procedure in Chapter 3.3 and / or the PDU session establishment procedure in Chapter 3.4, and / or the UE in Chapter 3.5 at any time. You may start the setting update procedure.

[4.2. Second Embodiment]
Next, the second embodiment will be described. Hereinafter, the second embodiment will be referred to as the present embodiment. In the present embodiment, each device is allowed to connect with high priority within the NPN, even if the AMF and / or SMF is in congestion control or the UE is counting in the backoff timer. Explain that the PDU session establishment procedure is executed based on the above.

In the communication procedure of this embodiment, the initial state is that each device has completed registration with the NPN. Each device may, or is not limited to, transitioned to the initial state according to the first embodiment.

Furthermore, in the initial state, AMF and / or SMF detects a DNN-based and / or S-NSSAI-based congestion state, and is a DNN-based and / or S-NSSAI-based congestion control state.

From the initial state, each device executes the first PDU session establishment procedure started from the UE. The first PDU session establishment procedure may be the PDU session establishment procedure in Chapter 3.4.

Specifically, the UE sends a first PDU session establishment request containing at least one of the 41st to 42nd identification information to the AMF and / or SMF. In other words, the AMF and / or SMF receives a first PDU session establishment request from the UE that includes at least one of the 41st to 42nd identifiers.

Further, the UE subsequently receives a PDU session establishment refusal message from the AMF and / or SMF containing at least one of the 61st to 62nd identification information. In other words, the AMF and / or SMF sends a PDU session establishment refusal message to the UE that contains at least one of the 61st to 62nd identifications.

Note that AMF and / or SMF may include information indicating congestion as a reason value in the PDU session establishment refusal message. Further, the AMF and / or SMF may include the value of the backoff timer in the registration refusal message, or may not include the value of the backoff timer based on the information of the UE.

Based on the completion of the first registration procedure and the receipt of the identification information of 41st to 42nd, the UE recognizes and remembers that the UE is a UE that is allowed to connect with a high priority within the NPN requested by the UE. You may. In addition, upon receipt of the reason for refusal value, the UE recognizes that the request has been rejected by the AMF and / or SMF for reasons of congestion. Further, the UE may start or execute counting of the backoff timer based on the reception of the value of the backoff timer. Alternatively, the UE may receive the value of the backoff timer or not start counting the backoff timer based on the stored information of the UE.

The UE may start the second PDU session establishment procedure even while the backoff timer is counting, based on the stored information of the UE. The second PDU session establishment procedure may be the PDU session establishment procedure in Chapter 3.4.

Specifically, the UE sends a second PDU session establishment request containing at least one of the 41st to 42nd identification information to the AMF and / or SMF. In other words, the AMF and / or SMF receives a second PDU session establishment request from the UE that contains at least one of the 41st to 42nd identifiers.

Further, the UE subsequently receives a PDU session establishment acceptance message from AMF and / or SMF containing at least one of the 51st to 52nd identification information. In other words, the AMF and / or SMF sends a PDU session establishment acceptance message to the UE that contains at least one of the 51st to 52nd identifications.

With the above procedure, each device can have a PDU session (to NPN) via NPN requested by UE even if AMF and / or SMF is in DNN-based and / or S-NSSAI-based congestion control. Can be established. In addition, each device can manage the UE as a UE that is allowed to connect with a high priority within the NPN, and the PDU via (or to the NPN) the NPN that the UE is allowed to connect to with a high priority. In session-related procedures (PDU session change procedure and / or PDU session release procedure), AMF and / SMF do not send a backoff timer to the UE.

In the second embodiment, by executing the first PDU session establishment procedure and the second PDU session establishment procedure, each device can perform the UE even if the AMF and / or the SMF is in congestion control. A PDU session (to the NPN) via the NPN requested by the UE requested by the UE has completed the establishment, but each device is requested by the UE requested by the UE even if the AMF and / or SMF is in congestion control. This is not the only way a PDU session (to an NPN) through an NPN can complete its establishment. For example, each device only has a second PDU session establishment procedure, and even if the AMF and / or SMF is in congestion control, a PDU session (to the NPN) via the NPN requested by the UE requested by the UE is established. May be completed.

In the second embodiment, after the second PDU session establishment procedure, each device performs the PUD session change procedure and / or the PUD session release procedure and / or the UE setting update procedure in Chapter 3.5 at an arbitrary timing. You may start.

In the PUD session change procedure and / or PUD session release procedure executed after the second PDU session establishment procedure, the AMF and / or SMF sends the backoff timer value to the UE based on the UE information. You don't have to.

[4.3. Third Embodiment]
Next, a third embodiment will be described. Hereinafter, the third embodiment will be referred to as the present embodiment. In the present embodiment, each device is a PDU session when the UE is stored in the network as a UE that is allowed to connect with a high priority in the NPN even when the AMF and / or SMF is in congestion control. The change procedure will be explained.

The initial state of this procedure is that at least one PDU session has been established via (or to) the NPN. In addition, the SMF remembers that the UE is a high priority UE allowed to connect within the NPN. Note that each device may have transitioned to the initial state according to, for example, the second embodiment, and the method of transitioning to the initial state of each device is not limited to this.

In the initial state of this embodiment, the AMF and / or SMF detects a DNN-based and / or S-NSSAI-based congestion state, and is a DNN-based and / or S-NSSAI-based congestion control state.

From the initial state, each device starts the PDU session modification procedure (PDU session modification procedure).

Here, the PDU session change procedure is a procedure for changing an established PDU session under the initiative of the UE or the network, and is a PDU session change request message (PDU Session modification request message) sent from the UE to the SMF. ), And a PDU session modification rejection message (PDU session modification reject message) sent from the SMF to the UE, or a PDU session modification procedure started from the SMF.

In addition, the PDU session change procedure started from SMF is a PDU session change command message (PDU session modification command message) sent from SMF to UE and a PDU session change completion message (PDU session modification complete message) sent from UE to SMF. ).

As explained earlier, the SMF sends a PDU session change command message to the UE within the PDU session change procedure. Here, the SMF does not include the value of the backoff timer in the PDU session change command message based on the fact that the UE is a UE that is allowed to connect with high priority in the NPN.

The UE sends a PDU session change completion message based on receiving a PDU session change command message that does not include the backoff timer value from the SMF, and completes the PDU session change procedure.

According to the above procedure, even if the AMF and / or SMF is in congestion control, if the UE is stored in the network as a UE that is allowed to connect with high priority in the NPN, the device is congested. Execute the PDU session change procedure without doing.

In the second embodiment, each device may start the PUD session change procedure and / or the PUD session release procedure and / or the UE setting update procedure in Chapter 3.5 at any timing.

[4.4. Fourth Embodiment]
Next, a fourth embodiment will be described. Hereinafter, the fourth embodiment will be referred to as the present embodiment. In the present embodiment, each device releases a PDU session when the UE is stored in the network as a UE that is allowed to connect with a high priority in the NPN even when the AMF and / or SMF is in congestion control. The procedure will be explained.

The initial state of this procedure is that at least one PDU session has been established via (or to) the NPN. In addition, the SMF remembers that the UE is a high priority UE allowed to connect within the NPN. Note that each device may have transitioned to the initial state according to, for example, the second embodiment, and the method of transitioning to the initial state of each device is not limited to this.

In the initial state of this embodiment, the AMF and / or SMF detects a DNN-based and / or S-NSSAI-based congestion state, and is a DNN-based and / or S-NSSAI-based congestion control state.

From the initial state, start the PDU session release procedure (PDU session release procedure).

Here, the PDU session release procedure is a procedure for deleting an established PDU session. The PDU session release procedure has a network-led procedure and a UE-led procedure, but in the present embodiment, it means a network-led procedure.

The network-led PDU session release procedure is based on the PDU session release command message (PDU Session release command message) sent from the SMF to the UE and the PDU session release completion message (PDU session release complete message) sent from the UE to the SMF. It is composed.

As shown above, the SMF sends a PDU session release command message within the PDU session release procedure. Here, the SMF does not include the value of the backoff timer in the PDU session release command message based on the fact that the UE is a UE that is allowed to connect with high priority in the NPN.

The UE sends a PDU session release completion message based on receiving a PDU session release command message that does not include the backoff timer value from the SMF, and completes the PDU session release procedure.

According to the above procedure, even if the AMF and / or SMF is in congestion control, if the UE is stored in the network as a UE that is allowed to connect with high priority in the NPN, the device is congested. Execute the PDU session change procedure without doing.

In the second embodiment, each device may start the PUD session change procedure and / or the PUD session release procedure and / or the UE setting update procedure in Chapter 3.5 at any timing.

[5. Modification example]
The program that operates in the apparatus according to the present invention may be a program that controls the Central Processing Unit (CPU) or the like to operate the 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.

Note that the program for realizing the function of the embodiment according to 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 "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 in an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein are 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 a combination thereof may be included. 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 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, an example of the device has been described, but the present invention is not limited to this, and the present invention is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device or a kitchen device. , Cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices such as living equipment.

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

Claims (14)

1. A user device that can be connected to NPN (Non Public Network)
   A storage unit that stores the first information,
   Receive the value of the backoff timer from the NPN and
   Based on the first information, the transmission / reception unit for transmitting a request message while the backoff timer is being executed is provided.
   The first information is information indicating that the user device can be connected within the NPN with high priority.
   The NPN is a network slice,
   A user device characterized by that.
2. The request message is a registration request message, a service request message, or a PDU session establishment request message.
   The user apparatus according to claim 1.
3. If the request message is a service request message
   The transmitting / receiving unit includes the second information in the service request message.
   The second information is information indicating that the NPN is connected with a high priority.
   The user apparatus according to claim 1 or 2.
4. If the request message is a registration request message
   The transmission / reception unit includes the third identification information in the registration request message.
   The third identification information is information indicating that the user device wants to be registered as a user device that connects to the NPN with high priority.
   The user apparatus according to claim 1 or 2.
5. A control device in PLMN (Public land mobile network) that includes a network slice created as an NPN (Non Public Network).
   A storage unit that stores the first identification information,
   A control unit that detects congestion and
   Receive a request message from the user device
   Based on the first identification information, even in the state of performing the detection, as a response to the request message, a transmission / reception unit that does not transmit a rejection message including a reason value indicating congestion is provided.
   A control device characterized by that.
6. The congestion is MM (Mobility Management) signal congestion or DNN (Data Network Name) -based congestion and / or network slice-based congestion.
   5. The control device according to claim 5.
7. A controller within PLMN that contains a network slice created as a Non Public Network (NPN).
   A PDU (Protocol Data Unit or Packet Data Unit) session deletion command message, a PDU session establishment rejection message, or a PDU session change rejection message that does not include a backoff timer is transmitted to a user device that can be connected with high priority in the NPN. , Equipped with a transmitter / receiver
   A control device characterized by that.
8. It is a communication control method of a user device that can be connected to an NPN (Non Public Network) that stores the first information.
   The step of receiving the value of the backoff timer from the NPN and
   Based on the first information, the request message is transmitted while the backoff timer is being executed.
   The first information is information indicating that the user device can be connected within the NPN with high priority.
   The NPN is a network slice,
   A communication control method for a user device, characterized in that.
9. The request message is a registration request message, a service request message, or a PDU session establishment request message.
   The communication control method of the user apparatus according to claim 8.
10. If the request message is a service request message
    Include the second information in the service request message
    The second information is information indicating that the NPN is connected with a high priority.
    The communication control method of the user apparatus according to claim 8 or 9.
11. If the request message is a registration request message
    The registration request message includes the third identification information.
    The third identification information is information indicating that the user device wants to be registered as a user device that connects to the NPN with high priority.
    The communication control method of the user apparatus according to claim 8 or 9, wherein the method is characterized by the above.
12. A communication control method for a control device in a PLMN (Public land mobile network) that stores the first identification information and includes a network slice created as an NPN (Non Public Network).
    Steps to detect congestion and
    With a step to receive a request message from the user device,
    Based on the first identification information, the control device does not send a rejection message including a reason value indicating congestion as a response to the request message even in the state of performing the detection.
    A control device characterized by that.
13. The congestion is MM (Mobility Management) signal congestion or DNN (Data Network Name) -based congestion and / or network slice-based congestion.
    12. The communication control method for the control device according to claim 12.
14. A communication control method for controllers in PLMN, including network slices created as non-public networks (NPNs).
    A PDU (Protocol Data Unit or Packet Data Unit) session deletion command message, a PDU session establishment rejection message, or a PDU session change rejection message that does not include a backoff timer is transmitted to a user device that can be connected with high priority in the NPN. With steps,
    A communication control method for a control device, characterized in that.

Images