JP2019216292A - Terminal device, mme (mobility management entity), cpf (control plane function) and communication control method - Google Patents

Abstract

To provide a terminal device capable of supporting switching of connection between a plurality of core networks and to provide communication control means suitable for apparatuses of a network connectable with the terminal device.SOLUTION: The present invention provides: a terminal device capable of being connected with various types of core networks; communication control means suitable for apparatuses of a network connectable with the terminal device; communication control means for changing a core network connected with the terminal device; and communication control means for switching a session established by the terminal device to another core network.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a terminal device, an MME (Mobility Management Entity), a CPF (Control Plane Function), and a communication control method.

  In recent years, 3GPP (3rd Generation Partnership Project), which carries out standardization activities of mobile communication systems, is studying SAE (System Architecture Evolution), which is a system architecture of LTE (Long Term Evolution). 3GPP specifies an EPS (Evolved Packet System) as a communication system that realizes all-IP (Internet Protocol). Note that the core network configuring the EPS is called an EPC (Evolved Packet Core).

  In recent years, 3GPP has been studying next-generation communication technologies and system architectures of 5G (5th Generation) mobile communication systems, which are next-generation mobile communication systems. Next-generation communication technologies include NextGen (Architecture and Security for Next Generation). System). NextGen extracts the technical challenges for connecting a wide variety of terminals to a cellular network and specifies solutions.

  For example, in order to introduce the connection system newly specified by NextGen into the existing environment, it is necessary to transfer connections between the existing core network such as EPC and the core network supporting the connection system specified by NextGen. Optimization of a system architecture for realizing system coordination between core networks is mentioned as a requirement.

  In addition, to support diversifying services and the transmission and reception of a wide variety of user data, a network slice that virtually configures a set of devices in the network, specializing in specific services, objectives, and connection requests is realized. Optimization of the system architecture to perform this is also a requirement.

3GPP TR 23.799; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System; (Release 14)

  NextGen is examining the optimization of the connection switching means between the existing core network and the core network specified by NextGen. More specifically, studies are being made to switch the core network connected to the terminal device between the EPC and the core network defined by NextGen.

  However, in NextGen, means for realizing connection switching between different core networks and access networks and means for realizing transmission and reception of various types of user data have not been clarified.

  The present invention has been made in view of such circumstances, and has as its object to realize means for switching connection between different core networks and access networks, and to realize transmission and reception of various user data. Communication control means and the like.

  The terminal device according to an embodiment of the present invention performs a detach procedure on a first core network, and after the detach procedure, performs a detach procedure on an attach procedure on a second core network; Based on the completion of the procedure, to change the connection destination from the first core network to the second core network, comprising a control unit, the transmitting and receiving unit, in the detach procedure, the detach request message MME (Mobility Management Entity), and in the attach procedure, sends an attach request message to a CPF (Control Plane Function), the detach request message includes information indicating that a connection destination is to be changed, and the attach request message is And information indicating over.

  An MME (Mobility Management Entity) of an embodiment of the present invention includes a transmitting / receiving unit that executes a detach procedure, and a connection destination of a terminal device, based on the completion of the detach procedure, the second core being connected to the second core network from the first core network. In order to change to the core network of, the control unit disconnects the connection with the terminal device, the transmitting and receiving unit transmits a detach request message to the terminal device in the detach procedure, the detach request message is And information indicating that a connection destination of the terminal device is to be changed.

  A CPF (Control Plane Function) of one embodiment of the present invention is a transmitting / receiving unit that executes an attach procedure, and based on the completion of the attach procedure, a connection destination of a terminal device, the second core network from the first core network. In order to change to the core network, the control unit is connected to the terminal device, the transmitting / receiving unit receives an attach request message from the terminal device in the attach procedure, and the attach request message is a handover message. Is included.

  A communication control method for a terminal device according to an embodiment of the present invention includes the steps of: performing a detach procedure on a first core network; and performing an attach procedure on a second core network after the detach procedure. And changing the connection destination from the first core network to the second core network based on the completion of the detach procedure.In the detach procedure, an MME (Mobility) Management Entity), further comprising, in the attach procedure, transmitting an attach request message to a CPF (Control Plane Function), wherein the detach request message changes a connection destination. The attach request message includes information indicating handover. It includes, characterized in that.

  The communication control method of MME (Mobility Management Entity) of one embodiment of the present invention, the step of executing a detach procedure, based on the completion of the detach procedure, the connection destination of the terminal device, the first core network from the first core network In order to change to the second core network, disconnecting the connection with the terminal device, comprising, the transmitting and receiving unit, in the detachment procedure, transmitting a detach request message to the terminal device, In addition, the detach request message includes information indicating that a connection destination is to be changed.

  The communication control method of the CPF (Control Plane Function) of one embodiment of the present invention, the step of executing an attach procedure, based on the completion of the attach procedure, the connection destination of the terminal device, from the first core network Connecting to the terminal device to change to the second core network, comprising: receiving an attach request message from the terminal device in the attach procedure, further comprising: The request message includes information indicating handover.

  According to the present invention, a terminal can be simultaneously connected to a core network via a plurality of access networks, and further, it is possible to realize communication of various user data. The core network can accommodate terminal devices connected to various access networks, and can also provide mobile communication services.

FIG. 2 is a diagram for describing an outline of a mobile communication system. FIG. 3 is a diagram for explaining an example of a configuration of a core network_A and an access network in a mobile communication system. FIG. 3 is a diagram for describing an example of a configuration of a core network_B and an access network in a mobile communication system, and the like. FIG. 3 is a diagram for explaining a device configuration of a UE. FIG. 3 is a diagram for explaining a storage unit of the UE. FIG. 3 is a diagram for explaining an eNB / NR node / WAG device configuration. FIG. 3 is a diagram for explaining an MME / CPF device configuration. FIG. 3 is a diagram for explaining a storage unit of the MME / CPF. FIG. 3 is a diagram for explaining a storage unit of the MME / CPF. FIG. 3 is a diagram for explaining a device configuration of SGW / PGW / UPGW / SCEF. FIG. 4 is a diagram for explaining a storage unit of the SGW. FIG. 3 is a diagram for explaining a storage unit of a PGW / UPGW. FIG. 3 is a diagram for explaining a storage unit of SCEF. FIG. 9 is a diagram for describing an initial procedure for a core network_A. FIG. 4 is a diagram for explaining an outline of a PDN connection procedure. FIG. 9 is a diagram for explaining an attach procedure to a core network_A. It is a figure for explaining a tracking area update procedure. FIG. 9 is a diagram for explaining a first reconnection procedure. It is a figure for explaining a detachment procedure. FIG. 11 is a diagram for explaining a PDU session establishment procedure. FIG. 9 is a diagram for explaining an attach procedure to a core network_B. FIG. 10 is a diagram for explaining a second reconnection procedure. FIG. 9 is a diagram for explaining a PDN connection disconnection procedure.

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

[1. System Overview]
FIG. 1 is a diagram illustrating an outline of a mobile communication system according to the present embodiment. As shown in the figure, the mobile communication system 1 includes a mobile terminal device UE_A10, an access network_A, an access network_B, a core network_A90, a core network_B190, and a PDN (Packet Data Network) _A5. . Here, UE_A10 may be a terminal device capable of wireless connection, and may be a UE (User Equipment), an ME (Mobile Equipment), an MS (Mobile Station), or a CIoT (Cellular Internet of Things) terminal (CIoT UE) or the like. . Further, the core network may be a core network_A90 and / or a core network_B190, and the access network may be an access network_A and / or an access network_B.

  Also, UE_A10 can be connected to an access network and / or a core network. Further, UE_A10 can be connected to PDN_A5 via an access network and / or a core network, and further transmits / receives user data to / from PDN_A5. Note that the user data may be data transmitted and received between UE_A10 and PDN_A5. Further, transmission / reception (communication) of user data may be performed using a PDU (Protocol Data Unit or Packet Data Unit) session, or may be performed using a PDN connection (Packet Data Network Connection). Further, communication of user data is not limited to IP (Internet Protocol) communication, but may be non-IP communication.

  Here, a PDU session or PDN connection (hereinafter, also referred to as PDN connection) is established between UE_A10 and PDN_A5 to provide a PDU connection service for transmitting and receiving user data between UE_A10 and PDN_A5. Connectivity. More specifically, the PDU session or PDN connection may be the connectivity established between UE_A10 and the external gateway. Here, the external gateway may be a device that connects the PDN_A5 with a core network such as a PGW (Packet Data Network Gateway) _A30, a UPGW (User Plane Gateway) _A130, or a SCEF (Service Capability Exposure Function) _A46.

  Further, the PDU session or PDN connection may be a communication path established for transmitting and receiving user data between UE_A10 and the core network and / or PDN_A5, or may be a communication path for transmitting and receiving PDUs. Further, the PDU session or PDN connection may be a session established between UE_A10 and the core network and / or PDN_A5, and is configured with a transfer path such as one or more bearers between devices in the mobile communication system 1. A logical communication path may be used. More specifically, the PDN connection may be a connection established by UE_A10 between core network_A90 and an external gateway, or a connection established between UE_A10 and PGW_A30 and / or SCEF_A46. Further, the PDU session, UE_A10, may be a connection established between the core network _B190 and the external gateway, UE_A10, may be a connection established between the UPGW_A130, PDN connection (Packet Data Network Connection) and the like Connection.

  The PDN connection may be a connection and / or connection between UE_A10 and PGW_A30 via eNB (evolved Node B) _A45 and / or SGW (Serving Gateway) _A35, or via eNB_A45 and / or MME_A40. It may be the connectivity and / or connection between UE_A10 and SCEF_A46. Further, the PDU session may be the connectivity and / or connection between UE_A10 and UPGW_A130 via NR node_A122.

  Note that UE_A10 can transmit and receive user data to and from a device such as an application server arranged in PDN_A5 using a PDU session or PDN connection. In other words, the PDU session or PDN connection can transfer user data transmitted and received between the UE_A10 and a device such as an application server arranged in the PDN_A5. Further, each device (UE_A10, device in the access network, and / or device in the core network) may manage one or a plurality of pieces of identification information in association with a PDU session or a PDN connection. These identification information include APN (Access Point Name), TFT (Traffic Flow Template), session type, application identification information, PDN_A5 identification information, NSI (Network Slice Instance) identification information, and DCN (Dedicated Core Network ) At least one of the identification information and the access network identification information may be included, and other information may be further included. Further, when a plurality of PDU sessions or PDN connections are established, each piece of identification information associated with the PDU session or PDN connection may have the same content or different content.

  IP communication is data communication using IP, and is data communication realized by transmission and reception of an IP packet to which an IP header is added. It should be noted that the payload portion forming the IP packet may include user data transmitted and received by UE_A10. The non-IP communication is data communication that does not use IP, and is data communication that is realized by transmitting and receiving data to which an IP header is not added. For example, the non-IP communication may be data communication realized by transmission and reception of application data to which an IP packet has not been added, or UE_A10 may have another header such as a Mac header or an Ethernet (registered trademark) frame header. User data to be transmitted and received may be transmitted and received.

  Furthermore, PDN_A5 may be a DN (Data Network) that provides a communication service to UE_A10. Note that the DN may be configured as a packet data service network or may be configured for each service. Further, PDN_A5 may include a connected communication terminal. Therefore, connecting to PDN_A5 may be connecting to a communication terminal or server device arranged in PDN_A5. Further, transmitting / receiving user data to / from the PDN_A5 may be transmitting / receiving user data to / from a communication terminal or a server device arranged in the PDN_A5. Note that PDN_A5 may be expressed as DN, or DN may be expressed as PDN_A5.

  Further, the access network is a wireless network connected to UE_A10 and / or the core network. The access network may be a 3GPP access network or a non-3GPP access network. The 3GPP access network includes E-UTRAN (Evolved Universal Terrestrial Radio Access Network) _A80, UTRAN (Universal Terrestrial Radio Access Network) _A20, GERAN (GSM (registered trademark) EDGE Radio Access Network) _A25, and NextGen RAN (Next Generation Radio Access Network) _A120, and the non-3GPP access network may be WLAN ANb75, WLAN ANa70, WLAN ANc125. Note that UE_A10 may be connected to an access network to connect to the core network, or may be connected to the core network via the access network.

  Further, the core network is an IP mobile communication network operated by a mobile communication operator (Mobile Network Operator) connected to the access network and / or PDN_A5. The core network may be a core network for a mobile communication carrier that operates and manages the mobile communication system 1, or a virtual mobile communication carrier such as MVNO (Mobile Virtual Network Operator), MVNE (Mobile Virtual Network Enabler), or a virtual mobile communication carrier. It may be a core network for a mobile communication service provider. The core network _A90 may be an EPC (Evolved Packet Core) constituting an EPS (Evolved Packet System), and the core network _B190 may be an NGC (Next Generation (Next Generation System) constituting an NGS (NextGen System (Next Generation System)). NextGen) Core). Conversely, the EPC may be the core network_A90 and the NGC may be the core network_B190. Further, the core network_B190 may be a core network of a system that provides a 5G communication service. The core network_B190 is not limited to this, and may be a network for providing mobile communication services.

  Next, a configuration example of the core network will be described. In the present embodiment, a configuration example of the core network_A90 and the core network_B190 will be described. Note that the core network may be the core network_A90, the core network_B190, or a combination thereof. Further, core network_A90 may be EPC, and core network_B190 may be NGC (NextGen Core).

    First, FIG. 2 shows an example of a configuration of the core network_A90. The core network _A90 in FIG. 2 (a) is HSS (Home Subscriber Server) _A50, AAA (Authentication Authorization Accounting) _A55, PCRF (Policy and Charging Rules Function) _A60, PGW_A30, ePDG (enhanced Packet Data Gateway) _A65, SGW_A35. , MME (Mobility Management Entity) _A40, SGSN (Serving GPRS Support Node) _A42, and SCEF_A46. In addition, the core network_A90 can be connected to a plurality of radio access networks (E-UTRAN_A80, WLAN ANb75, WLAN ANa70, UTRAN_A20, GERAN_A25).

  The wireless access network may have a configuration connected to a plurality of different access networks or a configuration connected to any one access network. Further, UE_A10 can wirelessly connect to the wireless access network. Further, the access network connectable by the WLAN access system is a WLAN access network b (WLAN ANb75) connected to the core network via ePDG_A65, or a WLAN access network a (WLAN ANa70) connected to PGW_A30, PCRF_A60 and AAA_A55. It is possible to configure by. Since each device is configured in the same manner as a conventional device in a mobile communication system using EPS, detailed description is omitted. Hereinafter, each device will be briefly described.

  The PGW_A30 is connected to PDN_A5, SGW_A35, ePDG_A65, WLAN ANa70, PCRF_A60, and AAA_A55, and is a relay device that transfers user data as a gateway between PDN_A5 and / or DN and core network_A90. Note that PGW_A30 may be a gateway for IP communication and / or non-IP communication. Further, the PGW_A30 may have a function of transferring IP communication, or may have a function of converting non-IP communication and IP communication. Note that a plurality of such gateways may be arranged in the core network_A90. Further, a plurality of arranged gateways may be gateways connecting the core network_A90 and a single DN.

  The U-Plane (User Plane) may be a communication path for transmitting and receiving user data, or may be configured with a plurality of bearers. Further, the C-Plane (Control Plane) may be a communication path for transmitting and receiving a control message, or may be configured by a plurality of bearers.

  Furthermore, PGW_A30 may be connected to the UP function and the Policy function, or may be connected to UE_A10 via U-Plane. Further, PGW_A30 may be configured together with UPGW_A130.

  The SGW_A35 is connected to the PGW_A30, the MME_A40, the E-UTRAN_A80, the SGSN_A42, and the UTRAN_A20, and relays user data as a gateway between the core network_A90 and the 3GPP access network (UTRAN_A20, GERAN_A25, E-UTRAN_A80). Device.

  Further, the SGW_A35 may be an UP function for transferring user data having a contact point with the access network, and may be a UPGW (User Plane Gateway) _A130 which is a gateway for transferring user data between the access network and the core network. May be.

  The MME_A40 is connected to the SGW_A35, the access network, the HSS_A50, and the SCEF_A46, and is a control device that performs location information management including mobility management of the UE_A10 and access control via the access network. Further, MME_A40 may include a function as a session management device that manages a session established by UE_A10. Further, a plurality of such control devices may be arranged in the core network_A90. For example, a location management device different from the MME_A40 may be configured. A location management device different from MME_A40 may be connected to SGW_A35, an access network, SCEF_A46, and HSS_A50, similarly to MME_A40.

  When a plurality of MMEs are included in the core network_A90, the MMEs may be connected to each other. Thereby, transmission and reception of the context of UE_A10 may be performed between MMEs. As described above, the MME_A40 is a management device that transmits and receives the control information related to the mobility management and the session management to and from the UE_A10. In other words, the MME_A40 may be a control device of a control plane (Control Plane; C-Plane; CP).

  Furthermore, the example in which the MME_A40 is configured to be included in the core network_A90 has been described, but the MME_A40 may be a management device configured in one or more core networks or DCNs or NSIs, or may include one or more core networks It may be a management device connected to DCN or NSI. Here, the plurality of DCNs or NSIs may be operated by a single communication carrier or may be operated by different communication carriers.

  Also, the MME_A40 may be a relay device that transfers user data as a gateway between the core network_A90 and the access network. The user data transmitted and received by the MME_A40 as a gateway may be small data.

  Further, MME_A40 may be an NF that plays a role of mobility management such as UE_A10, an NF that plays a role of session management such as a PDU session, or an NF that manages one or a plurality of NSIs. MME_A40 may be an NF that plays one or more of these roles. The NF may be one or a plurality of devices arranged in the core network_A90, and may be a CP function for control information and / or a control message (hereinafter, also referred to as a CPF (Control Plane Function) or a Control Plane Network Function). ) Or a shared CP function shared between a plurality of network slices.

  Here, the NF is a processing function configured in the network. That is, the NF may be a functional device such as an MME, an SGW, a PGW, a CPF, or an UPGW, or a function such as an MM (Mobility Management) or an SM (Session Management), or capability capability information. Further, the NF may be a functional device for realizing a single function or a functional device for realizing a plurality of functions. For example, the NF for realizing the MM function and the NF for realizing the SM function may exist separately, or the NF for realizing both the MM function and the SM function exists. You may.

  HSS_A50 is connected to MME_A40, AAA_A55, and SCEF_A46, and is a management node that manages subscriber information. The subscriber information of HSS_A50 is referred to, for example, at the time of access control of MME_A40. Furthermore, HSS_A50 may be connected to a location management device different from MME_A40. For example, HSS_A50 may be connected to CPF_A140.

  AAA_A55 is connected to PGW30, HSS_A50, PCRF_A60, and WLAN ANa70, and performs access control of UE_A10 connected via WLAN ANa70.

  PCRF_A60 is connected to PGW_A30, WLAN ANa75, AAA_A55, and PDN_A5, and performs QoS management for data delivery. For example, it manages the QoS of the communication path between UE_A10 and PDN_A5. Furthermore, the PCRF_A60 may be a device that creates and / or manages a PCC (Policy and Charging Control) rule and / or a routing rule used when each device transmits and receives user data.

  Further, the PCRF_A60 may be a Policy function for creating and / or managing a policy. More specifically, PCRF_A60 may be connected to the UP function.

  The ePDG_A65 is connected to the PGW 30 and the WLAN ANb75, and performs delivery of user data as a gateway between the core network_A90 and the WLAN ANb75.

  SGSN_A42 is connected to UTRAN_A20, GERAN_A25, and SGW_A35, and is a control device for position management between a 3G / 2G access network (UTRAN / GERAN) and an LTE access network (E-UTRAN). Furthermore, SGSN_A42 has a function of selecting PGW and SGW, a function of managing the time zone of UE_A10, and a function of selecting MME_A40 at the time of handover to E-UTRAN.

  SCEF_A46 is a relay device that is connected to PDN_A5, MME_A40, and HSS_A50, and that transfers user data as a gateway that connects PDN_A5 and / or DN with core network_A90. Note that SCEF_A46 may be a gateway for non-IP communication. Further, SCEF_A46 may have a function of converting non-IP communication and IP communication. Further, a plurality of such gateways may be arranged in the core network_A90. Further, a plurality of gateways connecting the core network_A90 with a single PDN_A5 and / or DN may be arranged. Note that SCEF_A46 may be configured outside the core network, or may be configured inside the core network.

  Also, as shown in FIG. 2 (b), each wireless access network includes a device (eg, a base station device or an access point device) to which UE_A10 is actually connected. The device used for the connection may be a device adapted to the wireless access network.

  In the present embodiment, E-UTRAN_A80 is an LTE (Long Term Evolution) access network and includes eNB_A45. eNB_A45 is a radio base station to which UE_A10 is connected by E-UTRA (Evolved Universal Terrestrial Radio Access), and E-UTRAN_A80 may include one or more eNB_A45. Further, a plurality of eNBs may be connected to each other.

  UTRAN_A20 is a 3G access network, and includes an RNC (Radio Network Controller) _A24 and an NB (Node B) _A22. NB_A22 is a radio base station to which UE_A10 connects by UTRA (Universal Terrestrial Radio Access), and UTRAN_A20 may include one or more radio base stations. The RNC_A24 is a control unit that connects the core network_A90 and the NB_A22, and the UTRAN_A20 may include one or more RNCs. Also, the RNC_A24 may be connected to one or more NB_A22. Further, the RNC_A24 may be connected to a radio base station (BSS (Base Station Subsystem) _A26) included in the GERAN_A25.

  GERAN_A25 is a 2G access network and includes BSS_A26. BSS_A26 is a radio base station to which UE_A10 is connected by GERA (GSM (registered trademark) / EDGE Radio Access), and GERAN_A25 may be configured by one or a plurality of BSS_A26. Further, the plurality of BSS_A26 may be connected to each other. Also, BSS_A26 may be connected to RNC_A24.

  The WLAN ANa 70 is a wireless LAN access network, and includes a WLAN AP (Wireless Local Area Network Access Point) a72 and a TWAG (Trusted WLAN Access Gateway) _A74. WLAN APa72 is a wireless base station to which UE_A10 connects with a reliable WLAN access system for the operator that operates core network_A90, and WLAN ANa70 includes one or more wireless base stations. May be. TWAG_A74 is a gateway between core network_A90 and WLAN ANa70. Further, WLAN APa72 and TWAG_A74 may be configured by a single device. Even when the operator that operates the core network_A90 and the operator that operates the WLAN ANa70 are different, it is possible to realize such a configuration by contracts and rules between the operators.

  WLAN ANb75 is a wireless LAN access network and includes WLAN APb76. WLAN APb76 is a wireless base station to which UE_A10 connects in a WLAN access system when a trust relationship is not established with a company operating core network_A90, and WLAN ANb75 includes one or more wireless base stations. Stations may be included and configured. Thus, WLAN ANb 75 is connected to core network_A90 using ePDG_A65, which is a device included in core network_A90, as a gateway. ePDG_A65 has a security function to ensure security.

  Next, an example of the configuration of the core network_B190 will be described. FIG. 3 shows an example of the configuration of the core network_B190. The core network_B190 in FIG. 3A includes an HSS_A50, a PCRF_A60, a UPGW (User Plane Gateway) _A130, a CPF (Control Plane Function) _A140, and a SCEF_A46.

  Further, the core network_B190 can be connected to a plurality of radio access networks (E-UTRAN_A80, NextGen RAN_A120, WLAN ANc125). The wireless access network may have a configuration connected to a plurality of different access networks or a configuration connected to any one access network. Further, UE_A10 can wirelessly connect to the wireless access network.

  Further, an access network connectable by the 3GPP access system can be configured by E-UTRAN_A80 and NextGen RAN_A120. Further, an access network connectable by the WLAN access system can be configured as a WLAN access network c (WLAN ANc125) connected to CPF_A140 and UPGW_A130. Hereinafter, each device will be briefly described.

  UPGW_A130 is a device connected to PDN_A5, PCRF_A60, CPF_A140, E-UTRAN80, NextGen RAN_A120, and WLAN ANc125, and is a relay device that transfers user data as a gateway between PDN_A5 and / or DN and core network_B190. is there. UPGW_A130 may be a gateway for IP communication and / or non-IP communication. Further, UPGW_A130 may have a function of transferring IP communication, or may have a function of converting non-IP communication and IP communication. Note that a plurality of such gateways may be arranged in the core network_B190. Further, a plurality of arranged gateways may be gateways connecting the core network_B190 and a single DN. The UPGW_A 130 may have connectivity to another NF, and may connect to each device via another NF.

  Further, CPF_A140 is a device connected to UPGW_A130, E-UTRAN_A80, NextGen RAN_A120, WLAN ANc125, HSS_A50, and SCEF_A46. The CPF_140 may be an NF that plays a role of mobility management such as UE_A10, an NF that plays a role of session management such as a PDU session, or an NF that manages one or a plurality of NSIs. Further, CPF_140 may be an NF that plays one or more of these roles. Note that the NF may be one or more devices arranged in the core network_B190, a CP function for control information and / or a control message (Control Plane Function, or Control Plane Network Function), and a plurality of networks. A shared CP function shared between slices may be used. Note that the CPF_A140 may have connectivity with another NF, or may be connected to each device via another NF.

  Note that each device may be configured in the same manner as the device of the core network_B190, and the configuration and role of the SCEF_A46, HSS_A50, and PCRF_A60 may be the same devices as those described in the core network_A90.

  Further, as shown in FIG. 3 (b), each radio access network includes a device (eg, a base station device or an access point device) to which UE_A10 is actually connected. The device used for the connection may be a device adapted to the wireless access network.

  In the present embodiment, NextGen RAN_A120 is a 5G access network and includes an NR node (New Radio Access Technology node) _A122. The NR node_A 122 is a radio base station to which the UE_A 10 connects by NextGen RA (Next Generation Radio Access), and the NextGen RAN_A 120 may include one or more NR node_A 122.

  Further, NextGen RAN_A120 may be an access network including E-UTRA_A80 and / or NextGen RA_A120. In other words, NextGen RAN_A120 may include eNB_A45, NR node_A122, or both. In this case, eNB_A45 and NR node_A122 may be the same device. Therefore, NR node_A122 can be replaced with eNB_A45.

  WLAN ANc125 is a wireless LAN access network, and includes WAG_A126. WAG (WLAN Access Gateway) _A126 is a wireless base station to which UE_A10 is connected for wireless LAN access, and WLAN ANc125 may include one or more WAG_A126. Further, WAG_A126 may be a gateway between core network_B190 and WLAN ANc125. In WAG_A126, the functional unit of the wireless base station and the functional unit of the gateway may be configured by different devices. The WLAN ANc125 may have the same configuration as the WLAN ANa70 and / or the WLAN ANb75, or may have a different configuration.

  In this specification, UE_A10 being connected to each radio access network means being connected to a base station device, an access point, or the like included in each radio access network, and transmitting and receiving data and signals. Also goes through a base station device and an access point. Note that the control message transmitted and received between UE_A10 and core network_B190 may be the same control message regardless of the type of access network. Therefore, that UE_A10 and the core network _B190 transmit and receive messages via the NR node_A122 is the same as UE_A10 and the core network _B190 transmit messages via the eNB_A45, and / or WAG_A126. Good.

[1.2. Device configuration]
First, the identification information stored in each device will be described. IMSI (International Mobile Subscriber Identity) is permanent identification information of a subscriber (user), and is identification information assigned to a user who uses the UE. The IMSI stored by UE_A10, MME_A40 / CPF_A140, and SGW_A35 may be equal to the IMSI stored by HSS_A50.

  EMM State / MM State indicates the mobility management state of UE_A10 or MME_A40 / CPF_A140. For example, the EMM State / MM State may be an EMM-REGISTERED state where UE_A10 is registered in the network (registered state) and / or an EMM-DEREGISTERD state where UE_A10 is not registered in the network (non-registered state). Further, the EMM State / MM State may be an ECM-CONNECTED state in which the connection between the UE_A10 and the core network is maintained, and / or an ECM-IDLE state in which the connection is released. Note that the EMM State / MM State may be information that can distinguish between a state in which UE_A10 is registered in core network_A90 and a state in which UE_A10 is registered in core network_B190.

  GUTI (Globally Unique Temporary Identity) is temporary identification information of UE_A10. GUTI is composed of identification information of MME_A40 / CPF_A140 (GUMMEI (Globally Unique MME Identifier)) and identification information of UE_A10 in specific MME_A40 / CPF_A140 (M-TMSI (M-Temporary Mobile Subscriber Identity)). ME Identity is the ID of UE_A10 or ME, and may be, for example, IMEI (International Mobile Equipment Identity) or IMEISV (IMEI Software Version). MSISDN represents the basic telephone number of UE_A10. MSISDN stored in MME_A40 / CPF_A140 may be the information indicated by the storage unit of HSS_A50. Note that GUTI may include information for identifying CPF_140.

  MME F-TEID is information for identifying MME_A40 / CPF_A140. The MME F-TEID may include the IP address of MME_A40 / CPF_A140, may include the TME (Tunnel Endpoint Identifier) of MME_A40 / CPF_A140, or may include both of them. Further, the IP address of MME_A40 / CPF_A140 and the TEID of MME_A40 / CPF_A140 may be stored independently. Further, the MME F-TEID may be identification information for user data or identification information for control information.

  The SGW F-TEID is information for identifying the SGW_A35. The SGW F-TEID may include the IP address of SGW_A35, may include the TEID of SGW_A35, or may include both of them. Further, the IP address of SGW_A35 and the TEID of SGW_A35 may be stored independently. Further, the SGW F-TEID may be identification information for user data or identification information for control information.

  PGW F-TEID is information for identifying PGW_A30 / UPGW_A130. The PGW F-TEID may include the IP address of PGW_A30 / UPGW_A130, may include the TEID of PGW_A30 / UPGW_A130, or may include both of them. Further, the IP address of PGW_A30 / UPGW_A130 and the TEID of PGW_A30 / UPGW_A130 may be stored independently. Further, the PGW F-TEID may be identification information for user data or identification information for control information.

  eNB F-TEID is information for identifying eNB_A45. The eNB F-TEID may include the IP address of eNB_A45, may include the TEID of eNB_A45, or may include both of them. Further, the IP address of eNB_A45 and the TEID of SGW_A35 may be stored independently. Further, the eNB F-TEID may be identification information for user data or identification information for control information.

  The APN may be identification information for identifying a core network and an external network such as a DN. Further, the APN can be used as information for selecting a gateway such as PGW_A30 / UPGW_A130 that connects the core network A_90.

  The APN may be identification information for identifying such a gateway, or identification information for identifying an external network such as a DN. When a plurality of gateways connecting the core network and the DN are arranged, there may be a plurality of gateways that can be selected by the APN. Further, one gateway may be selected from the plurality of gateways by another method using identification information other than the APN.

  UE Radio Access Capability is identification information indicating the radio access capability of UE_A10. UE Network Capability includes security algorithms and key derivation functions supported by UE_A10. MS Network Capability is information including one or more pieces of information necessary for SGSN_A42 for UE_A10 having GERAN_A25 and / or UTRAN_A20 functions. Access Restriction is access restriction registration information. eNB Address is the IP address of eNB_A45. The MME UE S1AP ID is information for identifying UE_A10 in MME_A40 / CPF_A140. The eNB UE S1AP ID is information for identifying UE_A10 in eNB_A45.

  APN in Use is a recently used APN. APN in Use may be a Data Network Identifier. This APN may be composed of network identification information and default operator identification information. Further, the APN in Use may be information for identifying the DN at which the PDU session is established.

  Assigned Session Type is information indicating the type of the PDU session. Assigned Session Type may be Assigned PDN Type. The type of the PDU session may be IP or non-IP. Furthermore, when the type of the PDU session is IP, it may further include information indicating the type of PDN allocated from the network. The Assigned Session Type may be IPv4, IPv6, or IPv4v6.

  Unless otherwise specified, IP Address is an IP address assigned to the UE. The IP address may be an IPv4 address, an IPv6 address, or an IPv6 prefix. When the Assigned Session Type indicates non-IP, the element of IP Address may not be included.

  SCEF ID is the IP address of SCEF_A46 used in the PDU session. Default Bearer is information obtained and / or generated when a PDU session is established, and is EPS bearer identification information for identifying a default bearer (default bearer) associated with the PDU session.

  EPS Bearer ID is identification information of the EPS bearer. The EPS Bearer ID may be identification information for identifying a SRB (Signalling Radio Bearer) and / or a CRB (Control-plane Radio bearer) or identification information for identifying a DRB (Data Radio Bearer). TI (Transaction Identifier) is identification information for identifying a bidirectional message flow (Transaction). Note that the EPS Bearer ID may be EPS bearer identification information for identifying a dedicated bearer. Therefore, identification information for identifying an EPS bearer different from the default bearer may be used. TFT indicates all packet filters associated with the EPS bearer. The TFT is information for identifying a part of user data to be transmitted and received, and the UE_A10 transmits and receives the user data identified by the TFT using an EPS bearer associated with the TFT. In other words, UE_A10 transmits and receives the user data identified by the TFT using an RB (Radio Bearer) associated with the TFT. In addition, the TFT may associate user data such as application data to be transmitted and received with an appropriate transfer path, or may be identification information for identifying application data. Also, UE_A10 may transmit and receive user data that cannot be identified by TFT using a default bearer. UE_A10 may store in advance a TFT associated with the default bearer.

  Default Bearer is EPS bearer identification information for identifying a default bearer associated with the PDU session. Note that the EPS bearer may be a logical communication path established between UE_A10 and PGW_A30 / UPGW_A130. Further, the EPS bearer may be a default bearer or a dedicated bearer. Further, the EPS bearer may be configured to include an RB established between UE_A10 and a base station and / or an access point in the access network. Further, the RB and the EPS bearer may be associated one-to-one. Therefore, the identification information of the RB may be associated one-to-one with the identification information of the EPS bearer, or may be the same identification information. Note that the RB may be an SRB and / or a CRB or a DRB. The Default Bearer may be information that UE_A10 and / or SGW_A35 and / or PGW_A30 / UPGW_A130 acquire from the core network when a PDU session is established.

  User Identity is information for identifying a subscriber. User Identity may be IMSI or MSISDN. Further, User Identity may be identification information other than IMSI and MSISDN. Serving Node Information is information for identifying MME_A40 / CPF_A140 used in the PDU session, and may be the IP address of MME_A40 / CPF_A140.

  eNB Address is the IP address of eNB_A45. The eNB ID is information for identifying the UE in eNB_A45. MME Address is the IP address of MME_A40 / CPF_A140. The MME ID is information for identifying MME_A40 / CPF_A140. NR node Address is the IP address of NR node_A122. The NR node ID is information for identifying NR node_A122. WAG Address is the IP address of WAG_A126. The WAG ID is information for identifying the WAG_A126.

  Hereinafter, the configuration of each device will be described. Note that some or all of the functions of each device and each unit of each device described below may operate on physical hardware, or may be logically configured on virtual general-purpose hardware. It may operate on hardware.

[1.2.1. UE configuration]
FIG. 4 shows a device configuration of UE_A10. As shown in the figure, UE_A10 includes a transmission / reception unit_A420, a control unit_A400, and a storage unit_A440. The transmission / reception unit_A420 and the storage unit_A440 are connected to the control unit_A400 via a bus.

  Control unit_A400 is a functional unit for controlling UE_A10. The control unit_A400 realizes various processes by reading and executing various programs stored in the storage unit_A440.

  The transmission / reception unit_A420 is a functional unit for the UE_A10 to connect to a base station and / or an access point in the access network and to connect to the access network. Further, an external antenna_A410 is connected to the transmitting / receiving unit_A420. In other words, the transmission / reception unit_A420 is a functional unit for the UE_A10 to connect to the base station and / or the access point in the access network. Further, the transmission / reception unit_A420 is a transmission / reception function unit for transmitting / receiving user data and / or control information from the base station and / or the access point in the access network by the UE_A10.

  The storage unit_A440 is a functional unit that stores programs, data, and the like necessary for each operation of the UE_A10. The storage unit_A440 is configured by, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like. The storage unit_A440 may store at least identification information and / or control information, and / or flags, and / or parameters included in a control message transmitted and received in a communication procedure described below. The storage unit_A440 stores the UE context 442 as shown in the figure. Hereinafter, the information elements stored in the storage unit_A440 will be described. Note that the UE context 442 may include a UE context used when connecting to the core network_A90 and a UE context used when connecting to the core network_B190. Further, the UE context used when connecting to the core network_A90 and the UE context used when connecting to the core network_B190 may be stored together or separately.

  First, FIG. 5B shows information elements included in a UE context stored for each UE. As shown in the figure, the UE context stored for each UE includes IMSI, EMM State, GUTI, and ME Identity.

  Next, FIG. 5 (c) shows a UE context for each PDU session or PDN connection stored for each PDU session or PDN connection. As shown in the figure, the UE context for each PDU session includes APN in Use, Assigned Session Type, IP Address (es), and Default Bearer.

  FIG. 5D shows a UE context for each bearer stored in the storage unit of the UE. As shown in the figure, the UE context for each bearer includes an EPS Bearer ID, TI, and TFT.

[1.2.2.Configuration of eNB / NR node / WAG]
Hereinafter, the configurations of eNB_A45, NR node_A122, and WAG_A126 will be described. FIG. 6 shows a device configuration of the eNB_A45, the NR node_A122, and the WAG_A126. As illustrated, the eNB_A45, the NR node_A122, and the WAG_A126 are configured by a network connection unit_B620, a transmission / reception unit_B630, a control unit_B600, and a storage unit_B640. The network connection unit_B620, the transmission / reception unit_B630, and the storage unit_B640 are connected to the control unit_B600 via a bus.

  Control unit_B600 is a functional unit for controlling eNB_A45. The control unit_B600 implements various processes by reading and executing various programs stored in the storage unit_B640.

  The network connection unit_B620 is a functional unit for connecting the eNB_A45, the NR node_A122, and the WAG_A126 to the MME_A40 and / or the SGW_A35. Further, the network connection unit_B620 is a transmission / reception unit in which the eNB_A45, the NR node_A122, and the WAG_A126 transmit / receive user data and / or control information from the MME_A40 and / or the SGW_A35.

  The transmission / reception unit_B630 is a functional unit for connecting the eNB_A45, the NR node_A122, and the WAG_A126 to the UE_A10. Further, the transmission / reception unit_B630 is a transmission / reception function unit that transmits / receives user data and / or control information from UE_A10. Further, an external antenna_B610 is connected to the transmitting / receiving unit_B630.

  The storage unit_B640 is a functional unit that stores programs, data, and the like necessary for each operation of the eNB_A45, the NR node_A122, and the WAG_A126. The storage unit_B640 includes, for example, a semiconductor memory, an HDD, and the like. The storage unit_B640 may store at least identification information and / or control information and / or flags and / or parameters included in a control message transmitted and received in a communication procedure described below. The storage unit_B640 may store such information as a context for each UE_A10.

[1.2.3. MME / CPF configuration]
Hereinafter, configurations of MME_A40 and CPF_140 will be described. FIG. 7 shows a device configuration of the MME_A40 and the CPF_140. As shown in the figure, the MME_A40 and the CPF_140 are configured by a network connection unit_C720, a control unit_C700, and a storage unit_C740. The network connection unit_C720 and the storage unit_C740 are connected to the control unit_C700 via a bus. The functions of these units may operate on physical hardware, or may operate on logical hardware configured on virtually general-purpose hardware.

  The control unit_C700 is a functional unit for controlling the MME_A40 and the CPF_140. The control unit_C700 realizes various processes by reading and executing various programs stored in the storage unit_C740.

  The network connection unit_C720 is a function unit for the MME_A40 to connect to a base station in the access network and / or an access point in the access network, and / or SCEF_A46, and / or HSS_A50 and / or SGW_A35. Further, the network connection unit_C720, the MME_A40 is a base station in the access network, and / or an access point in the access network, and / or SCEF_A46, and / or HSS_A50, and / or SGW_A35, and user data and / or It is a transmission / reception unit for transmitting / receiving control information.

  Further, the network connection unit_C720 is a functional unit for the CPF_140 to connect to the base station in the access network, and / or the access point in the access network, and / or the SCEF_A46, and / or the HSS_A50, and / or the UPGW_A130. is there. Further, the network connection unit_C720, the MME_A40 is a base station in the access network, and / or an access point in the access network, and / or SCEF_A46, and / or HSS_A50, and / or UPGW_A130, and user data and / or It is a transmission / reception unit for transmitting / receiving control information.

  The storage unit_C740 is a functional unit that stores a program, data, and the like necessary for each operation of the MME_A40 and the CPF_140. The storage unit_C740 includes, for example, a semiconductor memory, an HDD, and the like. The storage unit_C740 may store at least identification information and / or control information, and / or flags, and / or parameters included in a control message transmitted and received in a communication procedure described below.

  The storage unit_C740 stores the MME context 742 as shown in the figure. Hereinafter, information elements stored in the storage unit_C740 will be described. In the MME context, CPF_140 may be a storage context. First, FIG. 8 (b) shows information elements included in a UE context stored for each UE. As shown in the figure, the MME context stored for each UE is IMSI, MSISDN, MM State, GUTI, ME Identity, UE Radio Access Capability, UE Network Capability, MS Network Capability, Access Restriction, MME F-TEID, SGW It includes one or more of F-TEID, eNB Address, MME UE S1AP ID, eNB UE S1AP ID, NR node Address, NR node ID, WAG Address, and WAG ID.

  Next, FIG. 9C shows an MME context for each PDU session or PDN connection stored for each PDU session or PDN connection. As shown in the figure, the MME context for each PDU session includes APN in Use, Assigned Session Type, IP Address (es), PGW F-TEID, SCEF ID, and Default bearer.

  FIG. 9 (d) shows an MME context for each bearer stored for each bearer. As shown in the figure, the MME context stored for each bearer is EPS Bearer ID, TI, TFT, SGW F-TEID, PGW F-TEID, MME F-TEID, eNB Address, NR node Address, WAG Address, eNB Contains one or more of ID, NR node ID, and WAG ID. Here, the information elements included in the MME context shown in FIGS. 8 and 9 may be included and stored in either the MM context or the EPS bearer context.

[1.2.4. SGW configuration]
FIG. 10 shows a device configuration of the SGW_A35. As shown in the drawing, the SGW_A35 includes a network connection unit_D1020, a control unit_D1000, and a storage unit_D1040. The network connection unit_D1020 and the storage unit_D1040 are connected to the control unit_D1000 via a bus.

  The control unit_D1000 is a functional unit for controlling the SGW_A35. The control unit_D1000 implements various processes by reading and executing various programs stored in the storage unit_D1040.

  The network connection unit_D1020 is a functional unit for connecting the SGW_A35 to a base station and / or an access point in the access network, and / or the MME_A40, and / or the PGW_A30, and / or the SGSN_A42. Further, the network connection unit_D1020 transmits and receives user data and / or control information from the SGW_A35 to the base station and / or the access point in the access network, and / or the MME_A40, and / or the PGW_A30, and / or the SGSN_A42. It is a transmitting / receiving unit.

  The storage unit_D1040 is a functional unit that stores a program, data, and the like necessary for each operation of the SGW_A35. The storage unit_D1040 includes, for example, a semiconductor memory, an HDD, and the like. The storage unit_D1040 may store at least identification information and / or control information, and / or flags, and / or parameters included in a control message transmitted and received in a communication procedure described below.

  The storage unit_D1040 stores the EPS bearer context 1042 as shown in the figure. The EPS bearer context 1042 includes one stored for each UE, one stored for each PDU session, and one stored for each bearer.

  First, FIG. 11 (b) shows information elements of the EPS bearer context stored for each UE. As shown in the figure, the EPS bearer context stored for each UE includes IMSI, ME Identity, MSISDN, MME F-TEID, and SGW F-TEID.

  Further, the EPS bearer context includes an EPS bearer context for each PDU session stored for each PDU session. FIG. 11 (c) shows an EPS bearer context for each PDU session. As shown in the figure, the EPS bearer context for each PDU session includes APN in Use, Assigned Session Type, SGW F-TEID, PGW F-TEID, Default Bearer, and IP Address (es).

  Further, the EPS bearer context includes an EPS bearer context for each bearer. FIG. 11D shows an EPS bearer context for each bearer. As shown in the figure, the EPS bearer context for each bearer is: EPS Bearer ID, TFT, PGW F-TEID, SGW F-TEID, eNB F-TEID, MME Address, NR node Address, WAG Address, MME ID, NR node Contains one or more of ID and WAG ID.

[1.2.5. PGW / UPGW configuration]
FIG. 10 shows a device configuration of PGW_A30 and UPGW_A130. As shown in the figure, PGW_A30 and UPGW_A130 are configured by a network connection unit_D1020, a control unit_D1000, and a storage unit_D1040. The network connection unit_D1020 and the storage unit_D1040 are connected to the control unit_D1000 via a bus. The functions of these units may operate on physical hardware, or may operate on logical hardware configured on virtually general-purpose hardware.

  The control unit_D1000 is a functional unit for controlling the PGW_A30. The control unit_D1000 implements various processes by reading and executing various programs stored in the storage unit_D1040.

  The network connection unit_D1020 is a functional unit for connecting the PGW_A30 to the SGW_A35, and / or the PCRF_A60, and / or the ePDG_A65, and / or the AAA_A55, and / or the TWAG_A74, and / or the PDN_A5. Further, the network connection unit_D1020, the PGW_A30, SGW_A35, and / or PCRF_A60, and / or ePDG_A65, and / or AAA_A55, and / or TWAG_A74, and / or TWAG_A74, and / or PDN_A5, from the user data and / or control information is transmitted and received It is a transmitting / receiving unit.

  Further, the network connection unit_D1020 is a functional unit for the UPGW_A130 to connect to the PCRF_A60 and / or the UPGW_A130 and / or the PDN_A5. Further, the network connection unit_D1020, the PGW_A30, SGW_A35, and / or PCRF_A60, and / or ePDG_A65, and / or AAA_A55, and / or TWAG_A74, and / or TWAG_A74, and / or PDN_A5, from the user data and / or control information is transmitted and received It is a transmitting / receiving unit.

  The storage unit_D1040 is a functional unit that stores programs, data, and the like necessary for each operation of the PGW_A30. The storage unit_D1040 includes, for example, a semiconductor memory, an HDD, and the like. The storage unit_D1040 may store at least identification information and / or control information, and / or flags, and / or parameters included in a control message transmitted and received in a communication procedure described below.

  The storage unit_D1040 stores the EPS bearer context 1042 as shown in the figure. In the EPS bearer context 1042, those that are stored for each UE, those that are stored for each APN, those that are stored for each PDU session or PDN connection, and those that are stored for each bearer May be stored separately. Further, the EPS bearer context may be a context stored in UPGW_A130.

  FIG. 12 (b) shows information elements included in the EPS bearer context stored for each UE. As shown in the figure, the EPS bearer context stored for each UE includes IMSI, ME Identity, MSISDN, and RAT type.

  Next, FIG. 12C shows the EPS bearer context stored for each APN. As shown in the figure, the EPS bearer context stored for each APN in the PGW storage unit includes APN in use. The EPS bearer context stored for each APN may be stored for each Data Network Identifier.

  FIG. 12D shows an EPS bearer context for each PDU session or PDN connection stored for each PDU session or PDN connection. As shown in the figure, the EPS bearer context for each PDU session or PDN connection includes an Assigned Session Type, IP Address (es), SGW F-TEID, PGW F-TEID, and Default Bearer.

  FIG. 12E shows an EPS bearer context stored for each EPS bearer. As shown in the figure, the EPS bearer context includes an EPS Bearer ID, TFT, SGW F-TEID, and PGW F-TEID.

[1.2.6.SCEF configuration]
FIG. 10 shows the device configuration of SCEF_A46. As shown in the drawing, the SCEF_A46 is configured by a network connection unit_D1020, a control unit_D1000, and a storage unit_D1040. The network connection unit_D1020 and the storage unit_D1040 are connected to the control unit_D1000 via a bus.

  The control unit_D1000 is a functional unit for controlling the SCEF_A46. The control unit_D1000 implements various processes by reading and executing various programs stored in the storage unit_D1040. Network connection unit_D1020 is a functional unit for SCEF_A46 to connect to core network_A90. In other words, the network connection unit_D1020 is a functional unit for connecting the SCEF_A46 to the MME_A40. Further, the network connection unit_D1020 is a transmission / reception unit where the SCEF_A46 transmits / receives user data and / or control information from the MME_A40.

  The storage unit_D1040 is a functional unit that stores programs, data, and the like necessary for each operation of the SCEF_A46. The storage unit_D1040 includes, for example, a semiconductor memory, an HDD, and the like. The storage unit_D1040 may store at least identification information and / or control information, and / or flags, and / or parameters included in a control message transmitted and received in a communication procedure described below.

  The storage unit_D1040 stores the EPS bearer context 1042 as shown in the figure. Hereinafter, information elements stored in the storage unit_D1040 will be described. FIG. 13B shows information elements included in the EPS bearer context. As shown in the figure, the EPS bearer context includes User Identity, APN in Use, EPS Bearer ID, and Serving Node Information.

[1.3. Explanation of Initial Procedure for Core Network_A]
Next, before describing the detailed procedure of the initial procedure for the core network_A90 in the present embodiment, terms specific to the present embodiment and main identification information used in the present embodiment will be described in advance to avoid duplication. .

  The first state in the present embodiment is a state in which the procedure for connecting and registering the UE_A10 to the core network_A90 has been completed, and further, each apparatus has established a PDN connection, and / or an EPS bearer. is there. Incidentally, each device, the procedure for registering UE_A10 in the core network_A90, the procedure for establishing a PDN connection, and / or EPS bearer may be executed simultaneously or may be executed separately. Good. Further, the first state may be a state in which a procedure for updating the location registration information of UE_A10 has been completed.

  Further, the first state in the present embodiment may be a state in which each device has established a PDN connection and / or an EPS bearer with the core network_A90. More specifically, the first state may be a state in which each device has established a PDN connection and / or an EPS bearer between UE_A10 and PGW_A30 via eNB_A45 and SGW_A35. Note that the first state is not limited to these states.

  Further, the EPS service in the present embodiment may be a service provided by the PS domain or a connection service provided by using the EPC.

  Further, the non-EPS service in the present embodiment may be a service provided by the CS domain or a service other than the EPS service.

  Further, the NGS service in the present embodiment may be a connection service provided using the core network_B190. Further, the NGS service may be a service different from the EPS service or a service similar to the EPS service. The NGS service is not limited to this, and may be any system for providing a mobile communication service.

  Further, the non NGS service in the present embodiment may be a service other than the NGS service, and may include an EPS service and / or a non EPS service.

  Further, the session in the present embodiment may be a PDU session, a PDN connection, or an EPS bearer. Further, the session establishment procedure may be a PDU session establishment procedure or a PDN connection procedure. The session disconnection procedure may be a PDU session disconnection procedure or a PDN connection disconnection procedure. Further, the information for identifying a session may be a PDU session ID, a PDN connection ID, or an EPS bearer ID. The information for identifying the session may be other identification information.

  Further, the EPS bearer in the present embodiment is a logical communication path established between UE_A10 and PGW_A30. The EPS bearer may be a communication path configuring a PDN connection. Further, the EPS bearer may be a logical communication path established between UE_A10 and UPGW_A130, or may be a communication path configuring a PDU session.

  An NSI (Network Slice Instance) in the present embodiment is an entity of a network slice (Network Slice) configured in the core network_B190, one or more. Further, the NSI in the present embodiment may be configured by a virtual NF (Network Function) generated using an NST (Network Slice Template). Here, the NST is associated with a resource request for providing a required communication service or capability, and is a logical expression of one or a plurality of Network Functions (NFs).

  That is, the NSI may be an aggregate in the core network_B190 configured by a plurality of NFs. The NSI may be a logical network configured to separate user data delivered by a service or the like. At least one NF may be configured in the network slice. The NF configured in the network slice may or may not be a device shared with another network slice.

 The UE may be assigned to one or more network slices based on UE usage type and / or registration information such as one or more network slice type IDs and / or one or more NS IDs and / or APN. Can be.

  A DCN (Dedicated Core Network) in the present embodiment is a core network dedicated to a specific subscriber type and configured in the core network_A90. Specifically, for example, a DCN for a UE registered as an M2M function user may be configured in core network_A90. In addition, a default DCN for a UE without an appropriate DCN may be configured in the core network_A90.

  At least one MME_40 or SGSN_A42 may be arranged in the DCN, and at least one or more SGW_A35 or PGW_A30 or PCRF_A60 may be arranged. A UE can be assigned to one DCN based on registration information such as UE usage type and / or DCN ID.

  The UE usage type in the present embodiment is a parameter value included in UE registration information used for identifying DCN and / or NSI. The UE usage type may be stored in HSS_50. MME_A40 and / or SGSN_A42 may select SGW_A35 and PGW_A30 based on the UE usage type. Further, CPF_A140 may select UPGW_A130 based on the UE usage type.

  Further, the DN ID in the present embodiment is identification information for identifying the core network_B190 and an external network such as a DN. Further, the DN ID can be used as information for selecting a gateway such as the UPGW_A130 connecting the core network_B190.

  Note that the DN ID may be identification information for identifying such a gateway, or identification information for identifying an external network such as a DN. If a plurality of gateways connecting core network_B190 and the DN are arranged, there may be a plurality of gateways that can be selected by the DN ID. Further, one gateway may be selected from the plurality of gateways by another method using identification information other than the DN ID.

  Further, the DN ID may be information equal to the APN or information different from the APN. If the DN ID and the APN are different information, each device may manage information indicating the correspondence between the DN ID and the APN, or may perform a procedure for inquiring the APN using the DN ID. Alternatively, a procedure for inquiring the DN ID using the APN may be performed.

  Furthermore, the tracking area in the present embodiment is one or more ranges that can be represented by the location information of the 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 may be 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 any similar area.

  The SSC (Session and Service Continuity) mode indicates a service session continuity (Session and Service Continuity) mode supported by the system and / or each device in the NextGen system (NGS). More specifically, the mode may indicate the type of service session continuation supported by the PDU session established between UE_A10 and a TUPF (Terminating User-Plane Function). Here, the TUPF may be UPGW_A130. The SSC mode may be a mode indicating the type of service session continuation set for each PDU session. Further, the SSC mode may include three modes, SSC mode 1, SSC mode 2, and SSC mode 3.

  Here, TUPF may be NF (Network Function) for U-Plane (User Plane). Further, the TUPF may be located in the core network or may be located in the access network.

  Furthermore, SSC mode 1 in the present embodiment is a service session continuation mode in which the same TUPF is maintained regardless of an access technology such as a RAT (Radio Access Technology) or a cell used when the UE_A10 connects to a network. More specifically, SSC mode 1 may be a mode for realizing a service session continuation without changing the TUPF used by the established PDU session even when mobility of UE_A10 occurs.

  Further, SSC mode 2 in the present embodiment is a service session continuation mode in which the same TUPF is maintained only in the TUPF serving area. More specifically, SSC mode 2 may be a mode for realizing service session continuation without changing the TUPF used by the established PDU session as long as UE_A 10 is in the TUPF serving area. Furthermore, SSC mode 2, such as exiting from the TUPF serving area, when the mobility of UE_A10 occurs, by changing the TUPF used by the established PDU session, even in the mode to realize the service session continuation Good.

  Here, the TUPF serving area may be an area in which one TUPF can provide a service session continuation function, or a subset of an access network such as a RAT or a cell used when UE_A10 connects to the network. It may be. Further, the subset of the access network may be a network composed of one or more RATs and / or cells.

  Further, SSC mode 3 in the present embodiment, PDU session established between UE_A10 and TUPF, and / or before disconnecting the communication path, for the same DN, a new PDU via a new TUPF This is a service session continuation mode that permits establishing a session and / or a communication path. Furthermore, SSC mode 3 may be a service session continuation mode that permits UE_A10 to enter multihoming.

  And / or SSC mode 3 may be a mode in which service session continuation using a plurality of PDU sessions and / or a TUPF associated with the PDU sessions is permitted. In other words, in the case of SSC mode 3, each device may implement service session continuation using a plurality of PDU sessions, or may implement service session continuation using a plurality of TUPFs.

  Here, when each device establishes a new PDU session, and / or a communication path, the selection of a new TUPF may be performed by the network, and the new TUPF may be a location where UE_A10 is connected to the network. May be the most suitable TUPF. In addition, if multiple PDU sessions and / or the TUPF used by the PDU sessions are valid, UE_A10 immediately performs the correspondence of the application and / or communication of the flow to the newly established PDU session. Or may be performed based on the completion of communication.

  The Default SSC mode is an SSC mode used by the UE_A10 and / or the network when a specific SSC mode is not determined. Specifically, Default SSC mode is the SSC mode used by UE_A10 when there is no SSC mode request from the application and / or when there is no UE_A10 policy for determining the SSC mode for the application. Is also good. If there is no SSC mode request from UE_A10, the SSC mode used by the network may be used.

  The Default SSC mode may be set for each PDN_A5 based on subscriber information, and / or an operator policy, and / or a policy of UE_A10, or may be set for each UE_A10 and / or a subscriber. You may. Furthermore, Default SSC mode may be information indicating SSC mode 1, SSC mode 2, or SSC mode 3. Next, the identification information in the present embodiment will be described.

  The first identification information in the present embodiment is information for identifying an external network, such as PDN_A5 or a DN, from which UE_A10 requests connection to core network_A90. Further, the first identification information may be an APN. Further, the first identification information may be information composed of a plurality of APNs, or may be information composed of an APN and a DN ID.

  The second identification information in the present embodiment is information indicating the type of connection service that UE_A10 requests the core network_90 to use. The second identification information may be information indicating that UE_A10 requests use of only the EPS service, or may be information indicating that UE_A10 requests use of both the EPS service and the non-EPS service. . In other words, the second identification information may be information indicating that UE_A10 requests the use of the EPS service and the NGS service, or that the UE_A10 requests the use of the EPS service, the NGS service, and the non-EPS service. The information may be indicated.

  Further, the second identification information may be information indicating a type of an attach procedure requested by UE_A10, or may be an attach type. In other words, the second identification information may be registration of only the core network _A90, and / or information indicating that a connection is requested, registration to both the core network _A90 and the core network_B190, and / or The information may indicate that a connection is requested.

  The third identification information in the present embodiment is information indicating the type of connection service supported by UE_A10 for use. Note that the third identification information may be information indicating that UE_A10 supports use of only the EPS service, or may be information indicating that UE_A10 supports use of both EPS service and non-EPS service. . In other words, the third identification information may be information indicating that UE_A10 supports the use of the EPS service and the NGS service, or that the UE_A10 supports the use of the EPS service, the NGS service, and the non-EPS service. The information may be indicated.

  Further, the third identification information may be capability information of UE_A10 indicating a type of an attach procedure supported by UE_A10. In other words, the third identification information may be registered only in the core network _A90, and / or capability information of the UE_A10 that supports connecting, registered in both the core network _A90 and the core network _B190, and / or Alternatively, it may be capability information of UE_A10 that supports connection.

  The fourth identification information in the present embodiment is information indicating the SSC mode requested by the UE_A10 to the core network_A90. Further, the fourth identification information may be information indicating an SSC mode used when switching a session from the EPS service to the NGS service. In other words, the fourth identification information may be information indicating an SSC mode used when switching and / or reattaching a session from the core network_A90 to the core network_B190. Specifically, the fourth identification information may be information indicating SSC mode 1, information indicating SSC mode 2, or information indicating SSC mode 3.

  The fifth identification information in the present embodiment is information indicating the SSC mode supported by UE_A10. Further, the fifth identification information may be information indicating an SSC mode supported when a session is switched from the EPS service to the NGS service. In other words, the fifth identification information may be information indicating an SSC mode supported when switching and / or reattaching a session from the core network_A90 to the core network_B190. Specifically, the fifth identification information may be information indicating SSC mode 1, information indicating SSC mode 2, or information indicating SSC mode 3.

  The sixth identification information in the present embodiment is information for identifying an external network such as a PDN_A5 or a DN to which the UE_A10 can connect. Further, the sixth identification information may be a DN ID. Further, the sixth identification information may be information composed of a plurality of DN IDs or information composed of a DN ID and an APN. Further, the sixth identification information may be information equal to the first identification information, or may be transmitted and received while being included in the first identification information.

  The seventh identification information in the present embodiment is information for identifying MME_40, for which UE_A10 requests connection to core network_A90. Furthermore, the seventh identification information may be information indicating the MME_40 to which the UE_A10 can connect, or information identifying the MME_40 to which the UE_A10 has previously connected. Further, the seventh identification information may be information for identifying UE_A10. For example, the seventh identification information may be GUTI, IMSI, EPS mobile identity, or other information.

  The eighth identification information in the present embodiment may include information for identifying the CPF_140 to which the UE_A10 can connect, or may include information for identifying the CPF_140 to which the UE_A10 has previously connected. Further, the eighth identification information may be information for identifying UE_A10. For example, the eighth identification information may be a CPF ID, GUTI, IMSI, NGS mobile identity, or other information. When a plurality of CPFs 140 exist in the core network_B190, the CPF_140 may be a common CPF that connects the core network_B190 to the UE_A10 and transmits / receives a control message to / from the UE_A10. In that case, the eighth identification information may include a common CPF ID.

  The ninth identification information in the present embodiment is information for identifying a DCN requested by the UE_A10 to the core network_A90. Further, the ninth identification information may be a UE usage type or a part of the UE usage type. Further, the ninth identification information may be an APN. Further, the ninth identification information may be configured to include information for identifying a device in the core network_A90 configured in the DCN requested by the UE_A10.

  The eleventh identification information in the present embodiment is information for identifying an external network such as a DN to which the core network_A90 has permitted the connection to the UE_A10 and / or a DN to which the UE_A10 has connected. Further, the eleventh identification information may be an APN. Further, the eleventh identification information may be information composed of a plurality of APNs or information composed of an APN and a DN ID.

  The twelfth identification information in the present embodiment is information indicating the type of connection service that the core network_A90 has permitted the UE_A10 to use. Note that the twelfth identification information may be information indicating that the core network _A90 has permitted the use of only the EPS service to the UE_A10, or the use of both the EPS service and the non-EPS service as the core network _A90. May be information indicating that the permission has been granted. In other words, the twelfth identification information may be information indicating that the use of the EPS service and the NGS service is permitted by the core network _A90, or the use of the EPS service, the NGS service and the non-EPS service Information indicating that A90 has permitted the information may be used.

  Further, the twelfth identification information may be information indicating the type of the attach procedure permitted to UE_A10 by core network_A90, or may be an attach result. In other words, the twelfth identification information may be information indicating that UE_A10 is registered only in the core network _A90, and / or that the connection is permitted, and registered in both the core network _A90 and the core network _B190, And / or information indicating that the connection is permitted.

  The thirteenth identification information in the present embodiment is information indicating the type of connection service supported by the core network_A90 for use. The thirteenth identification information may be information indicating that the core network_A90 supports use of only the EPS service, or the core network_A90 supports use of both the EPS service and the non-EPS service. Information indicating the fact. In other words, the thirteenth identification information may be information indicating that the use of the EPS service and the NGS service is supported by the core network_A90, or the use of the EPS service, the NGS service and the non-EPS service Information indicating that the A90 supports it may be used.

  Further, the thirteenth identification information may be capability information of the core network_A90 indicating the type of the attach procedure supported by the core network_A90. In other words, the thirteenth identification information may be registered in only the core network _A90 and / or capability information of the core network _A90 that supports connection, and may be registered in both the core network _A90 and the core network _B190. And / or capability information of the core network_A90 that supports connecting.

  The fourteenth identification information in the present embodiment is information indicating the SSC mode that the core network_A90 has granted to the UE_A10. Further, the fourteenth identification information may be information indicating an SSC mode permitted to be used when switching a session from the EPS service to the NGS service. In other words, the fourteenth identification information may be information indicating the SSC mode permitted to be used when switching sessions and / or reattaching from the core network_A90 to the core network_B190. Specifically, the fourteenth identification information may be information indicating that SSC mode 1 is permitted, information indicating that SSC mode 2 is permitted, or that SSC mode 3 is permitted. May be indicated.

  The fifteenth identification information in the present embodiment is information indicating the SSC mode supported by the core network A90. Further, the fifteenth identification information may be information indicating an SSC mode supported when a session is switched from the EPS service to the NGS service. In other words, the fifteenth identification information may be information indicating an SSC mode supported when switching and / or reattaching a session from the core network_A90 to the core network_B190. Specifically, the fifteenth identification information may be information indicating that the core network _A90 supports SSC mode 1, information indicating that SSC mode 2 is supported, or SSC mode 3. Information indicating support may be used.

  The sixteenth identification information in the present embodiment is information for identifying an external network such as a DN to which the UE_A10 can connect when the core network_A90 connects to the core network_B190 and is permitted to the UE_A10. Further, the sixteenth identification information may be a DN ID. Further, the sixteenth identification information may be information composed of a plurality of DN IDs or information composed of a DN ID and an APN. Further, the sixteenth identification information may be information equal to the eleventh identification information, or may be transmitted and received while being included in the eleventh identification information.

  The seventeenth identification information in the present embodiment is information for identifying the MME_40 that the core network_A90 has permitted the UE_A10 to connect to. Further, the seventeenth identification information may be information indicating MME_A40 connected to UE_A10, or information indicating MME_40 to which UE_A10 can be connected. Further, the seventeenth identification information may be information for identifying UE_A10. For example, the seventeenth identification information may be GUTI, IMSI, EPS mobile identity, or other information.

  The eighteenth identification information in the present embodiment is information for identifying the CPF_140 that the core network_A90 has permitted the UE_A10 to connect to. Further, the eighteenth identification information may be information indicating CPF_140 to which UE_A10 can connect. Further, the eighteenth identification information may be information for identifying UE_A10. For example, the eighteenth identification information may be a CPF ID, GUTI, NGS mobile identity, or other information. When a plurality of CPFs 140 exist in the core network_B190, the CPF_140 may be a common CPF that connects the core network_B190 to the UE_A10 and transmits / receives a control message to / from the UE_A10. In that case, the eighteenth identification information may be a common CPF ID.

  The nineteenth identification information in the present embodiment is information for identifying a DCN for which the core network_A90 has permitted the UE_A10 to connect. Furthermore, the nineteenth identification information may be a UE usage type or a part of the UE usage type. Further, the nineteenth identification information may be an APN. Further, the nineteenth identification information may be configured to include information for identifying a device configured in the DCN.

  The 21st identification information in the present embodiment is information indicating that the request of UE_A10 is not permitted to the core network_A90. Further, the 21st identification information may be reason information (Reject Cause) indicating the reason why the request of UE_A10 was rejected.

  For example, the 21st identification information may be information indicating that connection to UE_A10's core network_A90, and / or DN is not permitted, or connection of UE_A10 to core network_A90, and / or DN fails. It may be information indicating that the operation has been performed. Furthermore, the 21st identification information, UE_A10 may be information indicating that connection and / or registration to MME_A40 requesting connection is not permitted, or information for identifying UE_A10 is not normal, and / or Information indicating that the user is not permitted may be used. Furthermore, the 21st identification information may be information indicating that the connection of UE_A10 is not appropriate due to network congestion, authentication, or the like.

  Further, the 21st identification information may be information indicating that UE_A10 is not permitted to use both the EPS service and the non-EPS service, or may be information indicating that use of the EPS service is not permitted. Further, the 21st identification information may be information indicating that the use of both the EPS service and the NGS service is not permitted for UE_A10, and the use of all of the EPS service, the NGS service, and the non-EPS service may not be permitted. May be indicated.

  Furthermore, the 21st identification information may be information indicating that UE_A10 is connected to a PLMN (Public Land Mobile Network) that is not permitted, or the service requested by UE_A10 is not permitted in the current PLMN. This may be information indicating that a suitable cell does not exist in the current PLMN.

  Furthermore, the 21st identification information may be information indicating that UE_A10 is connected to a tracking area that is not permitted, or information indicating that the service requested by UE_A10 is not permitted in the current tracking area. May be. Further, the 21st identification information may be information indicating that no appropriate cell is present in the current tracking area, or information indicating that roaming is not permitted in the current tracking area.

  Furthermore, the 21st identification information may be information indicating that the SSC mode requested by UE_A10 is not permitted, or information indicating that the core network_A90 does not support the SSC mode requested by UE_A10.

  Furthermore, the 21st identification information may be information indicating that the NSI requesting connection by UE_A10 is not permitted, or information indicating that the core network_A90 does not support the network slice type requested by UE_A10. May be.

  The 22nd identification information in the present embodiment is information indicating the type of connection service that the core network_A90 has not permitted to use for the UE_A10. The 22nd identification information may be information indicating that the use of only the EPS service is not permitted by the core network _A90, or the use of both the EPS service and the non-EPS service is performed by the core network _A90. Information indicating that permission has not been granted may be used. In other words, the 22nd identification information may be information indicating that the use of the EPS service and the NGS service is not permitted by the core network _A90, or the use of the EPS service, the NGS service and the non-EPS service The information may indicate that the network_A90 did not permit.

  Further, the 22nd identification information may be information indicating the type of the attach procedure that was not permitted by the core network_A90. In other words, the 22nd identification information may be information indicating that only the core network _A90 is registered, and / or that connection is not permitted, registration with both the core network _A90 and the core network _B190, and / or The information may indicate that connection is not permitted.

  The twenty-third identification information in the present embodiment is information indicating the type of connection service that the core network_A90 does not support use. The 23rd identification information may be information indicating that the use of only the EPS service is not supported by the core network_A90, or the use of both the EPS service and the non-EPS service is not supported by the core network_A90. Information indicating the fact. In other words, the 23rd identification information may be information indicating that the use of the EPS service and the NGS service is not supported by the core network_A90, or the use of the EPS service, the NGS service, and the use of the non-EPS service The information may indicate that the A90 does not support it.

  Further, the twenty-third identification information may be capability information of the core network_A90 indicating a type of an attach procedure not supported by the core network_A90. In other words, the 23rd identification information may be registered in only the core network _A90 and / or capability information of the core network _A90 that does not support connection, and may be registered in both the core network _A90 and the core network _B190. And / or capability information of the core network_A90 that does not support connection.

  The twenty-fourth identification information in the present embodiment is information indicating the SSC mode that the core network_A90 has not permitted to the UE_A10. Further, the twenty-fourth identification information may be information indicating an SSC mode that is not permitted to be used when switching a session from the EPS service to the NGS service. In other words, the twenty-fourth identification information may be information indicating an SSC mode that is not permitted to be used when switching sessions and / or reattaching from the core network_A90 to the core network_B190. Specifically, the 24th identification information may be information indicating that SSC mode 1 is not permitted, information indicating that SSC mode 2 is not permitted, or SSC mode 3 is permitted. Information indicating that there was no information may be used.

  The twenty-fifth identification information in the present embodiment is information indicating the SSC mode, which is not supported by the core network A90. Further, the 25th identification information may be information indicating an SSC mode that is not supported when switching a session from the EPS service to the NGS service. In other words, the 25th identification information may be information indicating an SSC mode that is not supported when switching and / or reattaching a session from the core network_A90 to the core network_B190. Specifically, the 25th identification information may be information indicating that the core network _A90 does not support SSC mode 1, information indicating that SSC mode 2 is not supported, or SSC mode 3. The information may indicate that it is not supported.

  The 26th identification information in this embodiment may be NSI of the network slice type requested by UE_A10, and / or information indicating that connection to the NSI requested by UE_A10 is not permitted, or NSI requested by UE_A10. And / or the network slice type may be information indicating that the core network_B190 does not support it.

  The thirty-first identification information in the present embodiment is information indicating the type of connection service for which UE_A10 requests core network_A90 to update the registration information. Note that the 31st identification information may be information indicating that UE_A10 requests registration information update of only EPS service, or UE_A10 requests update of registration information of both EPS service and non-EPS service. Information indicating the fact. In other words, the 31st identification information may be information indicating that UE_A10 requests the update of the registration information of the EPS service and the NGS service, or the update of the registration information of the EPS service, the NGS service, and the non-EPS service, The information may indicate that UE_A10 requests.

  Further, the 31st identification information may be information indicating the type of the tracking area update procedure requested by UE_A10, or may be an update type. In other words, the thirty-first identification information may be information indicating that the registration information of only the core network _A90 is updated and / or requesting a connection, and the registration information of both the core network _A90 and the core network_B190. And / or information indicating that connection is requested.

  Furthermore, the 31st identification information may be information indicating that only the tracking area in the EPS service is to be updated, or information indicating that the update of the tracking area in the EPS service and the routing area in the non-EPS service are to be requested. . Further, the 31st identification information may be information indicating a request for updating the tracking area in the EPS service and the tracking area in the NGS service, or the tracking area in the EPS service, the tracking area in the NGS service, and the routing in the non-EPS service. The information may indicate that an area update is requested.

  The thirty-second identification information in the present embodiment is the same as the third identification information. The thirty-third identification information in the present embodiment is the same as the seventh identification information. The thirty-fourth identification information in the present embodiment is the same as the eighth identification information. The thirty-fifth identification information in the present embodiment is the same as the fourth identification information. The thirty-sixth identification information in the present embodiment is the same as the fifth identification information. The thirty-seventh identification information in the present embodiment is the same as the ninth identification information.

  The forty-first identification information in the present embodiment is information indicating the type of connection service for which the core network_A90 has permitted the UE_A10 to update the registration information. The 41st identification information may be information indicating that the update of the registration information of only the EPS service is permitted by the core network _A90, or the update of the registration information of both the EPS service and the non-EPS service may be the core information. Information indicating that the network_A90 has permitted the information may be used. In other words, the 41st identification information may be information indicating that the update of the registration information of the EPS service and the NGS service is permitted by the core network _A90, or the information of the registration information of the EPS service, the NGS service, and the non-EPS service. The information may indicate that the core network_A90 has permitted the update.

  Further, the 41st identification information may be information indicating the type of the attach procedure permitted by the core network_A90 to the UE_A10, or may be an attach result. In other words, the 41st identification information may be information indicating that the registration information of only the core network _A90 has been updated, and / or that connection has been permitted, and the registration information for both the core network _A90 and the core network _B190. May be updated and / or information indicating that the connection is permitted.

  Further, the forty-first identification information may be information indicating that the update of only the tracking area in the EPS service is permitted, and information indicating that the update of the tracking area in the EPS service and the routing area in the non-EPS service are permitted. May be. Further, the 41st identification information may be information indicating that the update of the tracking area in the EPS service and the tracking area in the NGS service is permitted, or the tracking area in the EPS service, the tracking area in the NGS service, and the information in the non-EPS service. The information may indicate that the update of the routing area is permitted.

  The forty-second identification information in the present embodiment is the same as the thirteenth identification information. The forty-fourth identification information in the present embodiment is the same as the fifteenth identification information. The forty-fifth identification information in the present embodiment is the same as the seventeenth identification information. The forty-sixth identification information in the present embodiment is the same as the eighteenth identification information. The forty-seventh identification information in the present embodiment is the same as the nineteenth identification information.

  The 51st identification information in the present embodiment is information indicating a detach procedure type requested by the core network_A90 to the UE_A10. The information indicating the type of the detach procedure may be a detach type. Further, the 51st identification information may be information indicating that reattachment of UE_A10 is required or information indicating that reattachment of UE_A10 is not required. Note that the reattachment may be to perform the attach procedure again.

  The 52nd identification information in the present embodiment is information indicating whether transmission / reception of information indicating handover is necessary at the time of reattachment. Furthermore, the 52nd identification information may be information indicating whether an attach procedure to another core network after the detach procedure is required or may be information indicating whether or not the attach procedure is supported.

  Further, the 52nd identification information may be information indicating that the core network_A90 has requested that the UE_A10 perform an attach procedure to another core network after the detach procedure. Furthermore, the 52nd identification information may be information indicating that an attach procedure after a detach procedure is necessary to switch a session from the core network_A90 to another core network. Note that another core network may be the core network_B190 or the core network identified by the 53rd identification information.

  The 53rd identification information in the present embodiment is information indicating a system to be connected when reattaching. The system to be connected may be a system that provides an NGS service, a system that provides an EPS, or a system that provides a non-EPS service. Further, the 53rd identification information may be information indicating a core network connected at the time of reattachment. For example, the 53rd identification information may be information indicating the core network_A90 or information indicating the core network_B190.

  Further, the 53rd identification information may be information indicating a type of a control message used at the time of reattachment. For example, the 53rd identification information may indicate that UE_A10 performs an attach procedure using a control message for EPS after a detach procedure, or performs an attach procedure using a control message for NGS. May be indicated. In other words, the 53rd identification information may indicate that UE_A10 performs an attach procedure to the core network_A90 after the detach procedure, or may indicate that the UE_A10 performs an attach procedure to the core network_B190. Good.

  The 54th identification information in the present embodiment is reason information (Cause) indicating the reason why the detach procedure was started. Further, the 54th identification information may be information indicating the reason that the state of UE_A10 has become inappropriate due to a change in subscriber information or the like.

  For example, the 54th identification information may be information indicating that the connection of UE_A10 to core network_A90 and / or DN is no longer permitted. Further, the 54th identification information may be information indicating that the connection and / or registration of UE_A10 to MME_A40 is no longer permitted, or the information for identifying UE_A10 is no longer normal and / or no longer permitted Information indicating that the information has been transmitted may be used. Further, the 54th identification information may be information indicating that the connection of UE_A10 has become inappropriate due to network congestion, authentication, or the like.

  Furthermore, the 54th identification information may be information indicating that use of both the EPS service and the non-EPS service is no longer permitted for UE_A10, and may be information indicating that use of the EPS service is no longer permitted. Good. Further, the 54th identification information may be information indicating that use of both the EPS service and the NGS service is no longer permitted for UE_A10, and all use of the EPS service, the NGS service, and the non-EPS service is permitted. It may be information indicating that it is no longer being performed.

  Further, the 54th identification information may be information indicating that the service used by the UE_A10 needs to be switched from the EPS service to the NGS service or the non-EPS service. In other words, the 54th identification information may be information indicating that the session needs to be switched from the core network _A90 to another core network, or a handover from the core network _A90 to another core network may be performed. May be information indicating that there is.

  Further, the 54th identification information may be information indicating that the PLMN to which UE_A10 is connected is no longer permitted, or information indicating that the service used by UE_A10 is no longer permitted in the current PLMN. Alternatively, the information may indicate that the appropriate cell is no longer present in the current PLMN.

  Further, the 54th identification information may be information indicating that the tracking area to which UE_A10 is connected is no longer permitted, or that the service used by UE_A10 is no longer permitted in the current tracking area. The information may be indicated. Further, the 54th identification information may be information indicating that an appropriate cell is no longer present in the current tracking area, or may be information indicating that roaming is no longer permitted in the current tracking area. .

  Further, the 54th identification information may be information indicating that the SSC mode used by the UE_A10 is no longer permitted or may be information indicating that the SSC mode is no longer supported. Further, the 54th identification information may be information indicating that the DCN to which UE_A10 is connected is no longer permitted.

  UE_A10 may determine whether to ignore the fifty-fourth identification information based on the fifty-first identification information, or determine whether to reattach based on the fifty-fourth identification information. May be. For example, when UE_A10 receives information indicating switching from core network_A90 to another core network and / or switching from EPS service to NGS service or non-EPS service, reattachment may be performed. In addition, when the UE_A10 receives the 54th identification information indicating that the use of the EPS service is not permitted in a state where the NGS service is available, the UE_A10 may not perform the reattachment. Furthermore, when the UE_A10 receives information indicating that the NGS service cannot be used while the EPS service is available, the UE_A10 may not need to perform the reattachment. Furthermore, when UE_A10 receives information indicating a reason other than these, it is not necessary to perform reattachment.

  The 55th identification information in the present embodiment is information for identifying the DCN to which UE_A10 is connected. Further, the 55th identification information may be a UE usage type or a part of the UE usage type. Further, the 55th identification information may be an APN. Further, the 55th identification information may be configured to include information for identifying a device in the core network_A90 configured in the DCN requested by the UE_A10.

  The 56th identification information in the present embodiment is information for identifying the NSI to which UE_A10 is to connect next and the network slice type. Further, the 56th identification information may be information such as an NSD ID for identifying an NSI and a network slice type ID for identifying a type of a network slice. Further, the 56th identification information may be a UE usage type, may be a part of the UE usage type, or may be other information. Further, the 56th identification information may be an APN or service identification information, or may be information associated with such information. In addition, the 56th identification information may be information indicating the NSI selected by the MME_A40 based on the mapping information of the DCN and the NSI, or may be information indicating the default NSI. The 56th identification information may be transmitted and received in association with the 57th identification information described later. That is, the information for identifying the NSI and the service that can be provided by connecting to the NSI may be transmitted and received in association with each other.

  Further, the 56th identification information may include information for identifying a plurality of NSIs. In this case, information for identifying each NSI may be transmitted and received in association with a service that can be provided by each NSI.

  The 57th identification information in the present embodiment is information indicating whether or not each session can be moved to another system. Further, the 57th identification information may be information for identifying a session that can be switched to another system.

  Further, the 57th identification information may be information identifying a service and / or a session that can move from the DCN to the NSI, and / or an APN, or information indicating a correspondence between the DCN and the NSI. Note that a plurality of pieces of information for identifying a service may be included. That is, the 57th identification information may be an information group for identifying a plurality of services. Further, the identification information of each service may be transmitted and received in association with the NSI included in the 56th identification information for each service. Therefore, information for identifying a service may be transmitted and received in association with a different NSI for each service.

  The 61st identification information in the present embodiment is information indicating the type of session for which UE_A10 requests establishment. Note that the information indicating the type of session for which UE_A10 requests establishment may be a request type. Further, the 61st identification information may be information indicating that the requested session establishment procedure is an initial establishment procedure, or may be information from another service, and / or another access network, and / or another core network. The information may be information indicating a handover procedure or information indicating a procedure for establishing a session for an emergency call.

  Further, the 61st identification information may be information indicating a handover from the core network_A90 to the core network_B190. Further, the 61st identification information may be information indicating that a session is to be established for switching a session from the core network _A90 to the core network_B190, or a session for switching a session from the EPS service to the NGS service. The information may indicate establishment.

  The 62nd identification information in the present embodiment is information for identifying a session moving to another system. Further, the 62nd identification information may be information for identifying a session for switching from the EPS service to the NGS service, or may be information for identifying a session for switching from the core network_A90 to the core network_B190.

  Further, the 62nd identification information may be information indicating that a PDU session requesting establishment and / or a bearer is established for switching a session from the EPS service and / or the core network_A90.

  The 63rd identification information in the present embodiment is information for identifying an external network, such as a DN, to which UE_A10 requests connection. Further, the 63rd identification information may be a DN ID. Further, the 63rd identification information may be information composed of a plurality of DN IDs or information composed of a DN ID and an APN.

  Further, the 63rd identification information may be a DN ID based on information received by UE_A10 during an attach procedure to core network_A90 and / or a PDN connection procedure. In other words, the 63rd identification information may be a DN ID corresponding to the APN indicated by the 11th identification information, or may be a DN ID indicated by the 16th identification information.

  The sixty-fourth identification information in the present embodiment is information for identifying the CPF_140 to which the UE_A10 requests a connection. Further, the sixty-fourth identification information may be information indicating a CPF_140 to which UE_A10 can connect, or may be information for identifying a CPF_140 to which UE_A10 has previously connected. Further, the 64th identification information may be information for identifying UE_A10. For example, the sixty-fourth identification information may be a CPF ID, GUTI, IMSI, NGS mobile identity, or other information. When a plurality of CPFs 140 exist in the core network_B190, the CPF_140 may be a common CPF that connects the core network_B190 and UE_A10 and transmits and receives control messages to and from UE_A10. In that case, the 64th identification information may be a common CPF ID.

  Further, the 65th identification information may include information for identifying MME_A40 to which UE_A10 can connect, or may include information for identifying MME_A40 to which UE_A10 has previously connected. Further, the sixty-fifth identification information may be information for identifying UE_A10. For example, the 65th identification information may be GUTI, IMSI, EPS mobile identity, or other information.

  The 66th identification information in the present embodiment is information indicating the type of connection service that UE_A10 requests to use. The 66th identification information may be information indicating that UE_A10 requests use of only the NGS service, or may be information indicating that UE_A10 requests use of both NGS service and non-NGS service. . In other words, the 66th identification information may be information indicating that UE_A10 requests the use of the NGS service and the EPS service, or that the UE_A10 requests the use of the NGS service, the EPS service, and the non-EPS service. The information may be indicated.

  Further, the 66th identification information may be information indicating a type of an attach procedure requested by UE_A10, or may be an attach type. In other words, the 66th identification information may be information indicating registration of only the core network _B190, and / or requesting a connection, registration to both the core network _B190 and the core network _A90, and / or The information may indicate that a connection is requested.

  The 67th identification information in the present embodiment is information indicating the type of connection service supported by the UE_A10 for use. The 67th identification information may be information indicating that UE_A10 supports use of only the NGS service, or may be information indicating that UE_A10 supports use of both the NGS service and the non-NGS service. . In other words, the 67th identification information may be information indicating that UE_A10 supports the use of the NGS service and the EPS service, or that the UE_A10 supports the use of the NGS service, the EPS service, and the non-EPS service. The information may be indicated.

  Further, the 67th identification information may be capability information of UE_A10 indicating a type of an attach procedure supported by UE_A10. In other words, the 67th identification information may be registered only in the core network_B190, and / or capability information of the UE_A10 that supports connection, and may be registered in both the core network_B190 and the core network_A90, and / or Alternatively, it may be capability information of UE_A10 that supports connection.

  The 68th identification information in the present embodiment is information that UE_A10 requests from core network_B190 to identify and / or indicate a network slice type. Further, the 68th identification information may be information such as an NSD ID for identifying an NSI and a network slice type ID for identifying a type of a network slice. Further, the 68th identification information may be a UE usage type or a part of the UE usage type. Also, the 68th identification information may be an APN or service identification information, or may be information associated with such information. Note that the 68th identification information may be constituted by information for identifying a plurality of NSIs. Also, the 68th identification information may be configured to include information for identifying an NF (Network Fuction) in the core network_B190. Further, the 68th identification information may be registration information of the UE.

  The 72nd identification information in the present embodiment is reason information (Cause) indicating the reason why the session disconnection procedure was started. Further, the 72nd identification information may be information indicating the reason why the state of the established session has become inappropriate due to a change in the subscriber information or the like.

  For example, the 72nd identification information may be information indicating that a service used by UE_A10 has been disabled by an operator policy, or a service used by UE_A10 cannot be provided due to a lack of network resources. It may be information indicating that it has become. Further, the 72nd identification information may be information indicating that an error has occurred in the network, or may be information indicating that the resource is periodically released.

  Further, the 72nd identification information may be information indicating that session reestablishment and / or session revalidation is necessary. Further, the 72nd identification information may be information indicating that it is necessary to switch the service used by UE_A10 from the EPS service to the NGS service or the non-EPS service. In other words, the 72nd identification information may be information indicating that the session needs to be switched from the core network _A90 to another core network, or a handover from the core network _A90 to another core network may be performed. May be information indicating that there is. Note that another core network may be the core network_A90 or the core network identified by the 73rd identification information.

  Further, the 72nd identification information may be information indicating that the SSC mode used by UE_A10 is no longer permitted or may be information indicating that the SSC mode is no longer supported. Further, the 72nd identification information may be information indicating that the DCN to which UE_A10 is connected is no longer permitted.

  Note that UE_A10 may determine whether to re-establish a session based on the 72nd identification information. For example, UE_A10 switches from the core network_A90 to another core network, and / or receives information indicating the switch from the EPS service to the NGS service or the non-EPS service. Good. Further, when UE_A10 receives information indicating that session reestablishment and / or session revalidation is necessary, UE_A10 may perform session reestablishment. When UE_A10 receives information indicating a reason other than the above, UE_A10 may not have to reestablish a session.

  The 73rd identification information in the present embodiment is information indicating a system to be connected when a session is re-established. The system to be connected may be a system that provides an NGS service, a system that provides an EPS, or a system that provides a non-EPS service. Further, the 73rd identification information may be information indicating a core network to be connected when a session is reestablished. For example, the 73rd identification information may be information indicating the core network_A90 or information indicating the core network_B190.

  Further, the 73rd identification information may be information indicating a type of a control message used at the time of reestablishing a session. For example, the 73rd identification information may indicate that the session establishment procedure is performed using the EPS control message after the session disconnection procedure, or the session establishment procedure is performed using the NGS control message. May be indicated.

  The seventy-fourth identification information in the present embodiment is information indicating whether transmission / reception of information indicating handover is necessary when a session is reestablished. Further, the 74th identification information may be information indicating whether or not a session establishment procedure for another core network after the session disconnection procedure is required, or may be information indicating whether or not it is supported.

  Further, the 74th identification information may be information indicating that the core network_B190 requests that the UE_A10 perform a session establishment procedure for another core network after the session disconnection procedure. Further, the 74th identification information may be information indicating that a session establishment procedure after a session disconnection procedure is necessary to switch a session from core network_B190 to another core network.

  The 75th identification information in the present embodiment is information for identifying and / or indicating a DCN to which UE_A10 is connected and a session requiring deletion or change is configured. Further, the 75th identification information may be a UE usage type or a part of the UE usage type. Further, the 75th identification information may be an APN. Furthermore, the seventy-fifth identification information may be configured to include information for identifying a device in the core network_A90 configured in the DCN requested by the UE_A10.

  The 76th identification information in the present embodiment is information for identifying the NSI or network slice type to which UE_A10 is to connect next. The 76th identification information may be information such as an NSD ID for identifying the NSI and a network slice type ID for identifying the type of the network slice. The 76th identification information may be a UE usage type, a part of the UE usage type, or other information. Further, the 76th identification information may be an APN or service identification information, or may be information associated with such information. The 76th identification information may be information indicating a selected NSI based on DCN, NSI and service identification information or APN mapping information, or information indicating a default NSI. Note that the seventy-sixth identification information may include information for identifying a plurality of NSIs.

  Next, in the present embodiment, an initial procedure for the core network_A90 will be described with reference to FIG. In the present embodiment, each device executes the initial procedure for the core network_A90, thereby transitioning to the first state, and the UE_A10 establishes a session via the core network_A90.

  Hereinafter, this procedure refers to an initial procedure for the core network_A90, and each procedure includes an attach procedure, a PDN connection procedure, and a tracking area update procedure. Details of each procedure will be described later.

  In this procedure, each device first executes a procedure for attaching to the core network_A90 (S1400), and transitions to a state where the UE_A10 is connected to the network. Next, each device executes the PDN connection procedure (S1402), and transitions to the first state (S1406). Further, after the PDN connection is established, a tracking area update procedure (S1404) may be further executed before transition to the first state. Note that each device may exchange various capability information and / or various request information of each device in the attach procedure to the core network_A90 and / or the PDN connection procedure and / or the tracking area update procedure.

  If each device exchanges various information and / or negotiates various requests by attaching to core network_A90, it does not perform exchange of various information and / or negotiation of various requests by PDN connection procedure. May be. Conversely, if each device does not exchange various information and / or negotiate various requests in the attach procedure to the core network_A90, it exchanges various information and / or negotiates various requests in the PDN connection procedure. May be implemented. Not limited to this, each device exchanges various information and / or negotiates various requests through the attach procedure to the core network_A90, but exchanges various information and / or negotiates various requests with the PDN connection procedure. May be implemented.

  For example, in the attach procedure to the core network_A90, and in the PDN connection procedure, UE_A10 may transmit one or more pieces of identification information among the first to ninth pieces of identification information to the core network_A90, or the core network _A90 may receive one or more pieces of identification information among the first to ninth pieces of identification information from UE_A10, and may further transmit one or more pieces of identification information among the eleventh to twenty-sixth pieces of identification information to UE_A10.

  Also, UE_A10 may transmit one or more pieces of identification information among the first to ninth pieces of identification information to core network_A90 in the procedure of attaching to core network_A90, and may not transmit the information in the PDN connection procedure. Similarly, the core network_A90 transmits one or more pieces of identification information among the eleventh to twenty-sixth identification information to the UE_A10 in the procedure for attaching to the network_A90, and may not transmit the identification information in the PDN connection procedure.

  Conversely, UE_A10 may be transmitted to the core network_A90 by the PDN connection procedure without transmitting one or more pieces of identification information among the first to ninth identification information by the attach procedure to the core network_A90. . Similarly, the core network_A90 may transmit to UE_A10 the PDN connection procedure without transmitting one or more pieces of identification information among the eleventh to twenty-sixth pieces of identification information to the core network_A90.

  Further, UE_A10 may transmit, to the core network_A90, the identification information of the first to ninth identification information that has not been transmitted in the procedure for attaching to the core network_A90, in the PDN connection procedure. Similarly, the core network_A90 may transmit to the UE_A10, among the eleventh to twenty-sixth identification information, the identification information that has not been transmitted in the procedure for attaching to the core network_A90 in the PDN connection procedure.

  Further, each device, when managing these identification information in association with UE_A10, may be transmitted and received during the procedure of attaching to the core network _A90, when managing in association with the EPS bearer, during the PDN connection procedure May be sent and received.

  Also, each device may execute the PDN connection procedure in the procedure for attaching to the core network_A90, or may execute the procedure after completing the procedure for attaching to the core network_A90. When the PDN connection procedure is executed in the procedure for attaching to the core network_A90, each device may establish a PDN connection based on the completion of the procedure for attaching to the core network_A90, 1 state.

  Next, each device executes a tracking area update procedure (S1404). Note that the tracking area update procedure may be executed after the PDN connection is established, before the transition to the first state, or at any timing after the transition. In addition, each device may exchange various pieces of request information in the tracking area update procedure. For example, in the tracking area update procedure, UE_A10 may transmit one or more pieces of identification information among the 31st to 37th identification information to the core network_A90. Further, the core network_A90 may transmit one or more pieces of identification information among the 41st to 46th and 21st to 26th identification information to the UE_A10.

  With the above procedure, each device completes this procedure. Each device involved in this procedure transmits and receives one or more pieces of 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. Further, each device may transition to an appropriate state based on completion of this procedure.

[1.3.1. Outline of Procedure for Attaching to Core Network_A]
First, the outline of the procedure for attaching to the core network_A90 will be described. The attach procedure to the core network_A90 is a procedure for the UE_A10 to take the initiative to connect to the network (the access network and / or the core network_A90 and / or the PDN_A5). UE_A10 can execute this procedure at an arbitrary timing, such as when the terminal is powered on, as long as it is not connected to core network_A90. In other words, UE_A10 may start this procedure at an arbitrary timing if it is not registered (EMM-DEREGISTERED). Further, each device may transition to the registration state (EMM-REGISTERED) based on completion of the attach procedure to core network_A90.

[1.3.2. PDN connection procedure example]
Next, an example of the PDN connection procedure will be described. Hereinafter, this procedure refers to the PDN connection procedure. This procedure is for each device to establish a PDN connection. Note that each device may execute this procedure in a state where the procedure for attaching to the core network_A90 is completed, or may be executed during the procedure for attaching to the core network_A90. Also, each device may start this procedure at an arbitrary timing after the procedure for attaching to core network_A90. Further, each device may establish a PDN connection based on the completion of the PDN connection procedure. Furthermore, each device may establish a plurality of PDN connections by executing this procedure a plurality of times.

[1.3.2.1. PDN connection procedure example]
An example of a procedure for executing the PDN connection procedure will be described with reference to FIG. Hereinafter, each step of this procedure will be described. First, UE_A10 transmits a PDN connection request message (PDN Connectivity Request) to MME_A40 via eNB_A45 (S1500), and starts a PDN connection procedure. The PDN connection request message is not limited to this, and may be any message that requests the establishment of a PDN connection.

  Here, UE_A10, in the PDN connection request message, may include at least one of the first to ninth identification information of the identification information, by including these identification information, indicating the request of UE_A10 Is also good.

  Further, each device may indicate the connection service requested and / or supported by UE_A10 by transmitting and receiving the second identification information and / or the third identification information. Further, each device, by transmitting and receiving the fourth identification information, and / or the fifth identification information, UE_A10 supports, and / or request, may indicate the mode of service continuation when switching to the NGS service. Good.

  Further, each device may indicate the type of PDN requested by UE_A10 by transmitting and receiving the first identification information and / or the sixth identification information. Further, each device may indicate the DCN to which UE_A10 requests connection by transmitting and receiving the ninth identification information.

  Furthermore, each device may indicate the MME_A40 or CPF_A140 to which UE_A10 requests connection by including the seventh identification information and / or the eighth identification information.

  Furthermore, each device transmits and receives one or more pieces of identification information among the first to ninth identification information, so that the PDN connection requesting the establishment has the same IP address even when the connection destination of the PDN connection is switched. May be able to be maintained.

  Note that the time of switching the connection destination of the PDN connection may be the time of switching the PDN connection from the EPS service to the NGS service, or the time of switching from the core network_A90 to the core network_B190.

  MME_A40 receives the PDN connection request message, and performs a first condition determination. The first condition determination is for the MME_A40 to determine whether to accept the request of UE_A10. In the first condition determination, the MME_A40 determines whether the first condition is true or false. The MME_A 40 starts the procedure (A) in this procedure if the first condition is true, and starts the procedure (B) in this procedure if the first condition is false. Steps when the first condition is false will be described later.

  Hereinafter, steps when the first condition is true, that is, each step of the procedure (A) in this procedure will be described. The MME_A40 executes the procedure (C) or (E) in this procedure, and starts the procedure (A) in this procedure. MME_A40 may execute procedure (C) in this procedure and start procedure (A) in this procedure when PGW_A30 is selected as the external gateway, or when SCEF_A46 is selected as the external gateway. The procedure of (E) in this procedure may be executed and the procedure of (A) in this procedure may be started. First, each step of the procedure of (C) in this procedure will be described. MME_A40 transmits a session creation request message to SGW_A35, and starts the procedure (C) in this procedure (S1502). Further, the SGW_A35 that has received the session creation request message transmits a session creation request message to the PGW_A30 (S1504).

  Here, the MME_A40 and the SGW_A35 may include at least one or more pieces of identification information among the first to ninth pieces of identification information in the session generation request message, or include information indicating whether or not the request is an initial request. Alternatively, the request of UE_A10 may be transmitted by including these pieces of identification information.

  Further, PGW_A30 receives the session creation request message, and performs a third condition determination. The third condition determination is for determining whether or not PGW_A30 accepts the request of UE_A10. The third condition is true when the request from UE_A10 is accepted, and may be when the request from UE_A10 is permitted. Further, the third condition is false when the request of UE_A10 is rejected, and may be when the third condition is not determined to be true.

  Further, the third condition determination may be performed by another device (for example, PCRF_A60) instead of PGW_A30. In this case, the PGW_A30 performs an IP-CAN session establishment procedure with the PCRF_A60. More specifically, PGW_A30 transmits a request message during the IP-CAN session establishment procedure to PCRF_A60. Further, PCRF_A60 receives the request message during the IP-CAN session establishment procedure, determines the third condition, and transmits a response message during the IP-CAN session establishment procedure to PGW_A30. Further, PGW_A30 receives the response message during the IP-CAN session establishment procedure, and recognizes the result of the third condition determination.

  Here, PGW_A30 may include at least one of the first to ninth identification information in the request message during the IP-CAN session establishment procedure, or by including these identification information, The request of UE_A10 may be transmitted.

  Also, the PCRF_A60 may include at least the result of the third information determination in the response message during the IP-CAN session establishment procedure, or by including this result, notifies the PGW_A30 of the result of the third condition determination. May be.

  Furthermore, the PCRF_A60 may include one or more pieces of identification information among the eleventh to nineteenth identification information in the response message during the IP-CAN session establishment procedure, or by including these identification information, the UE_A10 It may indicate that the request has been granted.

  Further, PCRF_A60, the response message during the IP-CAN session establishment procedure, may include one or more identification information of the 21st to 26th identification information, by including these identification information, UE_A10 It may indicate that the request has been rejected.

  When the PCRF_A60 performs the third condition determination, the PGW_A30 may perform the third condition determination based on the result of the third condition determination received from the PCRF_A60. For example, when the PCRF_A60 accepts the request of UE_A10, the PCRF_A60 and PGW_A30 may set the third condition to true, and when the request of UE_A10 is rejected, the PCRF_A60 and PGW_A30 may set the third condition to false.

  In the third condition determination, PGW_A30 determines whether the third condition is true or false. If the third condition is true, PGW_A30 transmits a session creation response message to SGW_A35 (S1506). Further, the SGW_A35 that has received the session creation response message transmits a session creation response message to the MME_A40 (S1508). Further, MME_A40 receives the session creation response message.

  In addition, the PGW_A30 and the SGW_A35 may include at least one of the eleventh to nineteenth identification information in the session creation response message, may include the IP address, or include these identification information. This may indicate that the request for UE_A10 has been granted.

  If the third condition is false, PGW_A30 transmits a session creation rejection message to SGW_A35 (S1506). Further, the SGW_A35 that has received the session creation rejection message transmits a session creation rejection message to the MME_A40 (S1508). Note that the session creation rejection message may be a session creation response message including a rejection cause (Reject cause).

  Also, the PGW_A30 may include, in the session creation rejection message, one or more pieces of identification information among the 21st to 26th identification information, or by including these pieces of identification information, the UE_A10 request may be rejected. May be indicated.

  Each device completes the procedure (C) in this procedure based on transmission / reception of the session creation response message and / or the session creation rejection message.

  Next, each step of the procedure (E) in this procedure will be described. MME_A40 transmits a session creation request message to _SCEF_A46, and starts the procedure (E) in this procedure (S1510).

  Here, the MME_A40 may include at least one or more pieces of identification information among the first to ninth pieces of identification information in the session generation request message, or may include information indicating whether the request is an initial request. Then, the request of UE_A10 may be transmitted by including these identification information.

  Further, SCEF_A46 receives the session creation request message, and performs a fourth condition determination. Note that the fourth condition determination is for the SCEF_A46 to determine whether to accept the request of the UE_A10. The fourth condition is true when the request from UE_A10 is accepted, and may be when the request from UE_A10 is permitted. The fourth condition is false when the request from UE_A10 is rejected, and may not be determined when the fourth condition is true.

  In the fourth condition determination, SCEF_A46 determines whether the fourth condition is true or false. If the fourth condition is true, SCEF_A46 sends a session creation response message to MME_A40 (S1512). Further, MME_A40 receives the session creation response message.

  Also, SCEF_A46 may include one or more pieces of identification information among the eleventh to nineteenth identification information in the session creation response message, may include an IP address, or may include these identification information. , UE_A10 may be permitted.

  If the fourth condition is false, SCEF_A46 transmits a session creation rejection message to MME_A40 (S1512). Note that the session creation rejection message may be a session creation response message including a rejection cause (Reject cause).

  Also, SCEF_A46 may include one or more pieces of identification information among the 21st to 26th identification information in the session creation rejection message, or by including these identification information, the request of UE_A10 may be rejected. May be indicated.

  Each device completes the procedure (E) in this procedure based on transmission / reception of the session creation response message and / or the session creation rejection message.

  MME_A40 transmits a PDN Connectivity Accept (PDN Connectivity Accept) message to eNB_A45 based on the reception of the session creation response message and / or based on the completion of the procedure (C) or (E) during this procedure ( S1514). When the MME_A 40 receives the session creation rejection message, the MME_A 40 may start the procedure (B) in this procedure without continuing the procedure (A) in this procedure. Further, the PDN connection acceptance message may be an Activate default EPS bearer context request message. Further, the PDN connection acceptance message may be a response message to the PDN connection request message, and is not limited to this, and may be any message that accepts a PDN connection request.

  eNB_A45 receives the PDN connection acceptance message, and transmits an RRC message to UE_A10 (e.g., an RRC Connection Reconfiguration message or an RRC Connection Setup message, or an RRC message such as an RRC Direct Transfer message), and / or transmits a PDN connection acceptance message (S1516). Note that the PDN connection acceptance message may be transmitted and received while being included in the RRC message.

  Here, the MME_A40 may include at least one of the 11th to 19th identification information in the PDN connection acceptance message, may include the IP address, or include these identification information. This may indicate that the request of UE_A10 has been accepted.

  Further, each device may indicate the connection service that the network permits and / or supports by transmitting and receiving the twelfth identification information and / or the thirteenth identification information. Furthermore, each device transmits and receives the fourteenth identification information and / or the fifteenth identification information to indicate a mode of service continuation when switching to an NGS service that the network supports and / or permits. Good.

  Further, each device may indicate the type of DN permitted by the network by transmitting and receiving the eleventh identification information and / or the sixteenth identification information. Further, each device may indicate the DCN to which the network permits connection by transmitting and receiving the nineteenth identification information.

  Further, each device may indicate the MME_A40 or CPF_A140 to which the network permits connection by transmitting and receiving the seventeenth identification information and / or the eighteenth identification information.

  Further, for example, each device may indicate why the request of UE_A10 was accepted by transmitting and receiving one or more pieces of identification information among the eleventh to nineteenth identification information. Furthermore, each device may indicate a process to be performed by each device after this procedure, perform the procedure again, or perform another condition based on the reason that the request of UE_A10 is accepted. This procedure may be performed at. For example, UE_A10 may execute connection to core network_B190 and / or switching of NGS service based on a process to be performed by each device included in the reason that the PDU session establishment procedure is accepted.

  Further, each device transmits and receives one or more pieces of identification information among the eleventh to nineteenth identification information, so that the established PDN connection can use the same IP address even when switching the connection destination of the PDN connection. It may indicate whether or not the connectivity can be maintained.

  When receiving the RRC message, UE_A10 transmits an RRC message (for example, an RRC message such as an RRC Connection Reconfiguration Complete message, an RRC Connection Setup Complete message, or an RRC Direct Transfer message) to eNB_A45 (S1518). eNB_A45 receives the RRC message, and transmits a bearer setup message to MME_A40 (S1520). Further, MME_A40 receives the bearer setting message.

  When receiving the PDN connection acceptance message, UE_A10 transmits a PDN Connectivity complete message to MME_A40 via eNB_A45 (S1522) (S1524). Further, MME_A40 receives the PDN connection completion message, and executes the second condition determination. Note that the PDN connection completion message may be an Activate default EPS bearer context accept message. Further, the PDN connection completion message may be a response message to the PDN connection acceptance message, and is not limited thereto, and may be a message indicating that the PDN connection procedure is completed.

  The second condition determination is for the MME_A40 to determine whether it is necessary to request the SGW_A35 to change the bearer. If the second condition is true, the MME_A40 starts the procedure (D) in this procedure. If the second condition determination is false, MME_A40 does not execute the procedure (D) in this procedure.

  Hereinafter, each step of the procedure (D) in the procedure will be described. MME_A40 transmits a bearer change request message to SGW_A35 (S1526), and starts the procedure (D) in this procedure. Further, the SGW_A35 receives the bearer change request message, and transmits a bearer change response message to the MME_A40 (S1528). Further, the MME_A 40 receives the bearer change response message, and completes the procedure (D) of this procedure. Further, each device performs this procedure based on the transmission and reception of the PDN connection completion message when the second condition determination is false, and based on the completion of the procedure (D) in this procedure when the second condition determination is true. Complete the procedure in (A).

  Next, each step of the procedure (B) in this procedure will be described. MME_A40 transmits a PDN connectivity rejection (PDN Connectivity reject) message to UE_A10 via eNB_A45 (S1530), and starts the procedure of (B) in this procedure. Further, UE_A10 receives the PDN connection rejection message and recognizes that the request of UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission and reception of the PDN connection rejection message. The PDN connection reject message may include an appropriate reason for rejection. Further, the PDN connection rejection message may be a response message to the PDN connection request message, and is not limited to this, and may be a message that rejects the PDN connection request.

  Also, the MME_A40 may include, in the PDN connection rejection message, one or more pieces of identification information among the 21st to 26th identification information, or by including these pieces of identification information, the request of UE_A10 may be rejected. May be indicated.

  Furthermore, each device may indicate the reason why the PDN connection procedure was rejected by transmitting and receiving the 21st identification information, and may perform a process to be performed by each device after the attach procedure to the core network _A90. May be shown.

  Further, each device transmits and receives the 22nd identification information and / or the 23rd identification information, so that the network supports connection to the core network_A90 and / or switching of the EPS service, and / or It may indicate that permission is not granted. Furthermore, each device transmits and receives the 24th identification information, and / or the 25th identification information, which indicates a mode of service continuation when switching to an NGS service that the network does not support and / or permit. Good.

  Further, each device may indicate a DCN whose network does not permit connection by transmitting and receiving the 26th identification information.

  Each device completes this procedure based on the completion of procedure (A) or (B) in this procedure. 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 the present procedure, or may perform transition based on the completion of the procedure (B) in the present procedure. It may recognize that this procedure has been rejected, and may transition to a state where a PDU session has not been established.

  Further, each device may execute processing based on the identification information transmitted and received in this procedure based on completion of this procedure. For example, when each device transmits and receives one or more pieces of identification information among the twenty-first to twenty-sixth identification information, each device may recognize the reason why the request of UE_A10 was rejected. Further, each device may perform this procedure again based on the reason that the request of UE_A10 is rejected, or may perform this procedure under another condition. For example, UE_A10 may execute connection to core network_B190 and / or switching of NGS service based on a process to be performed by each device included in the reason that the PDU session establishment procedure is accepted.

  Further, the above-described first to fourth condition determinations may be executed based on the identification information and / or the subscriber information and / or the operator policy included in the PDN connection request message. The conditions for determining whether the first to fourth conditions are true or false are not limited to the above-described conditions.

  For example, the first condition and / or the third condition and / or the fourth condition may be true if UE_A10 requests establishment of a session and the network grants the request. Further, the first condition and / or the third condition and / or the fourth condition may be false when UE_A10 requests establishment of a session and the network does not permit the request. Further, the first condition, and / or the third condition, and / or the fourth condition are used when the network to which UE_A10 is connected and / or devices in the network support establishment of a session requested by UE_A10. If not, it may be false.

[1.3.3. Example of attaching procedure to core network_A]
An example of a procedure for executing an attach procedure to core network_A90 will be described with reference to FIG. Hereinafter, this procedure refers to the procedure for attaching to the core network_A90. This procedure is for the UE_A10 to be registered in the core network_A90. Hereinafter, each step of this procedure will be described. First, UE_A10 transmits an attach request (Attach request) message to MME_A40 via eNB_A45 (S1600), and starts an attach procedure to core network_A90. UE_A10 may transmit the attach request message including the above-described PDN connection request message, or may include the PDN connection request message to perform the PDN connection procedure during the attach procedure to core network_A90. May be requested.

  Here, UE_A10 may include at least one of the first to ninth identification information in the attach request message, or may include the identification information to indicate the request of UE_A10. Good.

  Further, each device may indicate the connection service requested and / or supported by UE_A10 by transmitting and receiving the second identification information and / or the third identification information. Further, each device, by transmitting and receiving the fourth identification information, and / or the fifth identification information, UE_A10 supports, and / or request, may indicate the mode of service continuation when switching to the NGS service. Good.

  Further, each device may indicate the type of DN requested by UE_A10 by transmitting and receiving the first identification information and / or the sixth identification information. Further, each device may indicate the NSI to which UE_A10 requests connection by transmitting and receiving the ninth identification information.

  Furthermore, each device may indicate the MME_A40 or CPF_A140 to which UE_A10 requests connection by including the seventh identification information and / or the eighth identification information.

  Furthermore, each device transmits and receives one or more pieces of identification information among the first to ninth identification information, so that the PDN connection requesting the establishment has the same IP address even when the connection destination of the PDN connection is switched. May be able to be maintained.

  Note that the UE_A10 may transmit the identification information in a control message (for example, an ESM information request / response message) different from the attach request message (S1602).

  MME_A40 receives the attach request message and / or a control message different from the attach request message, and performs the first condition determination. If the first condition is true, the MME_A 40 starts the procedure (A) in the procedure, and if the first condition is false, the procedure (B) in the procedure starts.

  Hereinafter, each step of the procedure (A) in this procedure will be described. The MME_A 40 executes the fourth condition determination, and starts the procedure (A) in this procedure. In the fourth condition determination, the MME_A40 determines whether the fourth condition is true or false. MME_A40 executes the procedure (C) in the PDN connection procedure by starting it when the fourth condition is true, and omits it when the fourth condition is false (S1604). Further, the MME_A 40 transmits an attach accept (Attach accept) message to the eNB_A 45 based on the completion of the procedure (C) in the attach request message and / or the session creation response message and / or the PDN connection procedure (S1606). ). When the MME_A 40 receives the session creation rejection message, the MME_A 40 may start the procedure (B) in this procedure without continuing the procedure (A) in this procedure.

  eNB_A45 receives the attach acceptance message and transmits an RRC message to UE_A10 (e.g., an RRC message such as an RRC Connection Reconfiguration message or an RRC Connection Setup message, or an RRC Direct Transfer message) and / or an attach acceptance message (S1608). ). The attach acceptance message may be transmitted and received while being included in the RRC message. Further, when the fourth condition is true, the MME_A40 may transmit the attach accept message, including the PDN connection accept message described above, or by including the PDN connect accept message, the PDN connection procedure is accepted. May be shown.

  Here, the MME_A40 may include at least one of the eleventh to nineteenth identification information, the IP address, or these identification information in the attach acceptance message. May indicate that the request of UE_A10 has been accepted.

  Further, each device may indicate the connection service that the network permits and / or supports by transmitting and receiving the twelfth identification information and / or the thirteenth identification information. Furthermore, each device transmits and receives the fourteenth identification information and / or the fifteenth identification information to indicate a mode of service continuation when switching to an NGS service that the network supports and / or permits. Good.

  Further, each device may indicate the type of DN permitted by the network by transmitting and receiving the eleventh identification information and / or the sixteenth identification information. Further, each device may indicate the DCN to which the network permits connection by transmitting and receiving the nineteenth identification information.

  Furthermore, each device may indicate the MME_A40 or CPF_A140 to which the network permits connection by including the seventeenth identification information and / or the eighteenth identification information.

  Furthermore, each device may indicate the reason why the request of UE_A10 was accepted by transmitting and receiving one or more pieces of identification information among the eleventh to nineteenth identification information. Furthermore, each device may indicate a process to be performed by each device after this procedure, perform the procedure again, or perform another condition based on the reason that the request of UE_A10 is accepted. This procedure may be performed at. For example, UE_A10, based on the process to be performed by each device included in the reason why the attach procedure to the core network _A90 has been accepted, based on the connection to the core network _B190, and / or switching the EPS service, Is also good.

  Further, each device transmits and receives one or more pieces of identification information among the eleventh to nineteenth identification information, so that the established PDN connection can use the same IP address even when switching the connection destination of the PDN connection. It may indicate whether or not the connectivity can be maintained.

  Here, the first condition determination may be the same as the first condition determination during the PDN connection procedure. The fourth condition determination is for the MME_A40 to determine whether or not to execute a PDN connection procedure. The fourth condition is true when the PDN connection request message is received, and may be when the PDN connection procedure is also executed during this procedure. Further, the fourth condition is false when the PDN connection request message is not received, the case where the PDN connection procedure is not executed in this procedure, or the case where the fourth condition is not determined to be true. Good.

  When UE_A10 receives an RRC message from eNB_A45, UE_A10 transmits an RRC connection message to eNB_A45 (for example, an RRC message such as an RRC Connection Reconfiguration Complete message or an RRC Connection Setup Complete message, or an RRC Direct Transfer message) ( S1610). eNB_A45 receives the RRC message, and transmits a bearer setup message to MME_A40 (S1612). Further, MME_A40 receives the bearer setting message.

  When UE_A10 receives the attach acceptance message from MME_A40 via eNB_A45, UE_A10 transmits an attach complete message to MME_A40 via eNB_A45 (S1614) (S1616). Further, MME_A40 receives the attach completion message.

  Further, when the fourth condition is true, the MME_A40 executes a second condition determination. The second condition determination is for the MME_A40 to determine whether it is necessary to request the SGW_A35 to change the bearer. If the second condition is true, the MME_A40 starts and executes the procedure (D) in the PDN connection procedure (S1618). Each device completes the procedure (A) in this procedure based on the transmission and reception of the attach completion message and / or the completion of the procedure (D) in the PDN connection procedure.

  Note that, when receiving the PDN connection acceptance message, UE_A10 may complete the PDN connection procedure by transmitting the attach completion message including the above-described PDN connection completion message, or by including the PDN connection completion message. You may show it.

  Next, each step of the procedure (B) in this procedure will be described. MME_A40 transmits an attach rejection (Attach reject) message to UE_A10 via eNB_A45, and starts the procedure (B) in this procedure (S1620). Further, UE_A10 receives the attach reject message and recognizes that the request of UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission and reception of the attach rejection message. When the fourth condition is true, the MME_A40 may transmit the attach rejection message including the above-described PDN connection rejection message, or by including the PDN connection rejection message, the PDN connection procedure is rejected. May be shown. In that case, UE_A10 may further receive a PDN connection rejection message or authenticate that the PDN connection procedure has been rejected.

  Also, MME_A40, the attach rejection message, may include one or more of the identification information of the 21st to 26th identification information, by including these identification information, that the request of UE_A10 was rejected May be shown.

  Furthermore, each device may recognize the reason why the attachment procedure to the core network _A90 was rejected by transmitting and receiving one or more pieces of identification information among the 21st to 26th identification information, After the procedure for attaching to _A90, the process to be performed by each device may be indicated, the procedure may be performed again, or the procedure may be performed under another condition. For example, UE_A10 executes a connection to the core network_B190 and / or a switch to the NGS service based on a process to be performed by each device included in the reason why the attach procedure to the core network_A90 is rejected. May be.

  Furthermore, each device may indicate the reason why the PDN connection procedure was rejected by transmitting and receiving the 21st identification information, and may perform a process to be performed by each device after the attach procedure to the core network _A90. May be shown.

  Further, each device transmits and receives the 22nd identification information and / or the 23rd identification information, so that the network supports connection to the core network_A90 and / or switching of the EPS service, and / or It may indicate that permission is not granted. Further, each device may transmit and receive the 24th identification information and / or the 25th identification information to indicate a service continuation mode when switching to the EPS service, which is not supported and / or permitted by the network. Good.

  Further, each device may indicate a DCN whose network does not permit connection by transmitting and receiving the 26th identification information.

  Each device completes this procedure based on the completion of procedure (A) or (B) in this procedure. Note that each device may transition to the state where UE_A10 is connected to the network and / or the registration state based on the completion of the procedure (A) in this procedure, or the procedure (B) in this procedure. Based on the completion of the process, it may recognize that this procedure has been rejected, or may transition to a state where it cannot be connected to the network. The transition of each device to each state may be performed based on the completion of this procedure, or may be performed based on the establishment of a PDU session.

  Further, each device may execute processing based on the identification information transmitted and received in this procedure based on completion of this procedure. For example, when each device has transmitted and received one or more pieces of identification information among the twenty-first to twenty-fifth identification information, each device may recognize the reason why the request of UE_A10 was rejected. Furthermore, each device may perform the procedure again based on the reason that the request of UE_A10 is rejected, or may perform the procedure of attaching the core network _A90 or the core network _A90 to another cell. May be.

  Further, the above-described first to fourth condition determinations may be executed based on the identification information and / or the subscriber information included in the attach request message, and / or the operator policy. Further, the conditions for determining whether the first to fourth conditions are true or false are not limited to the above-described conditions.

  For example, the first condition determination and / or the third condition determination may be the same as the PDN connection procedure example described above.

[1.3.4. Overview of tracking area update procedure]
An outline of a tracking area update procedure will be described. Hereinafter, this procedure refers to a tracking area update procedure. This procedure updates the location registration information of UE_A10 in the network (access network and / or core network_A90), and / or periodically notifies UE_A10 of the status of UE_A10 to the network, and / or This is a procedure for updating specific parameters related to UE_A10 in the network. UE_A10 can execute this procedure at any timing as long as the PDN connection is established. UE_A10 can periodically execute this procedure.

[1.3.4.1. Tracking area update procedure example]
An example of a procedure for executing the tracking area update procedure will be described with reference to FIG. Hereinafter, each step of this procedure will be described. First, UE_A10 transmits a tracking area update request message (Tracking Area Update request) to MME_A40 via eNB_A45 (S1700), and starts a tracking area update procedure.

  Here, UE_A10, in the tracking area update request message, at least, may include one or more of the identification information of the 31st to 37th identification information, by including these identification information, indicates the request of UE_A10 Is also good.

  Furthermore, each device may indicate the connection service supported by UE_A10 by transmitting and receiving the 32nd identification information. Furthermore, each device transmits and receives the 35th identification information, and / or the 36th identification information, which UE_A10 supports and / or requests, and may indicate a service continuation mode when switching to the NGS service. .

  Further, each device may indicate the DCN to which UE_A10 requests connection by transmitting and receiving the 37th identification information.

  Further, each device may transmit and receive the 31st identification information to indicate the connection service for which UE_A10 requests updating of the registration information.

  Furthermore, each device may indicate the MME_A40 or the CPF_A140 to which the UE_A10 requests a connection by including the 33rd identification information and / or the 34th identification information.

  MME_A40 receives the tracking area update request message and performs the first condition determination. In the first condition determination, the MME_A40 determines whether the first condition is true or false. The MME_A 40 starts the procedure (A) in this procedure if the first condition is true, and starts the procedure (B) in this procedure if the first condition is false. Steps when the first condition is false will be described later.

  Hereinafter, steps when the first condition is true, that is, each step of the procedure (A) in this procedure will be described. The MME_A 40 executes the fourth condition determination, and starts the procedure (A) in this procedure. In the fourth condition determination, the MME_A40 determines whether the fourth condition is true or false. The MME_A40 starts the procedure (C) in this procedure when the fourth condition is true, and omits the procedure when the fourth condition is false (S1703).

  Here, the first condition determination may be the same as the first condition determination during the procedure of attaching to core network_A90. Further, the fourth condition determination is for determining whether a change and / or addition and / or deletion procedure of the PDN connection is necessary.

  Here, the MME_A40 may include at least one or more of the identification information of the 31st to 37th identification information in the message in the procedure of (C) in this procedure, or include these identification information. Thus, the request of UE_A10 may be transmitted to each device.

  Further, the MME_A40 executes the third condition determination after completing the procedure of (C). Here, the third condition determination is for determining whether the MME_A40 accepts the request of UE_A10, and the third condition determination is received from any device during the procedure of (C). It may be determined based on the information obtained. In the third condition determination, MME_A40 determines whether the third condition is true or false.

  MME_A40 transmits the procedure of (C) in this procedure, if the third condition is true, transmits a tracking area update accept (Tracking Area Update accept) message to UE_A10 via eNB_A45 (S1706), If the condition is false, the procedure of (A) in this procedure is stopped and the procedure of (B) in this procedure is started. The tracking area update acknowledgment message may include an appropriate acknowledgment reason. The tracking area update acceptance message may be a response message to the tracking area update request message, and is not limited thereto, and may be a message that accepts the tracking area update request.

  Here, the MME_A40 may include at least one of the 41st to 46th identification information in the tracking area update acceptance message, or by including these identification information, the request of the UE_A10 is accepted. You may indicate that it has been done.

  Further, by transmitting and receiving the 43rd identification information and / or the 44th identification information, each device may indicate the mode of service continuation when switching to the NGS service that the network supports and / or permits. Good. Further, each device may indicate the MME_A40 or the CPF_A140 to which the network permits connection by transmitting and receiving the forty-fifth identification information and / or the forty-sixth identification information.

  Further, each device may transmit and receive the 41st identification information to indicate that the request of UE_A10 has been permitted. Furthermore, each device may indicate a connection service supported by the network by transmitting and receiving the forty-second identification information.

  Further, each device may transmit and receive one or more pieces of identification information among the forty-first to forty-sixth identification information to indicate the reason why the request of the UE was accepted. Furthermore, each device may indicate a process to be performed by each device after this procedure, perform the procedure again, or perform another condition based on the reason that the request of UE_A10 is accepted. This procedure may be performed at. For example, UE_A10 may execute connection to core network_B190 and / or switching of NGS service based on a process to be performed by each device included in the reason that the tracking area update procedure has been accepted.

  When UE_A10 receives the tracking area update acceptance message, UE_A10 transmits a tracking area update complete (Tracking Area Update complete) message to MME_A40 via eNB_A45 (S1710). Each device completes the procedure (A) in this procedure based on the transmission and reception of the tracking area update completion message.

  Next, each step of the procedure (B) in this procedure will be described. MME_A40 transmits a Tracking Area Update reject message to UE_A10 via eNB_A45 (S1720). Further, UE_A10 receives the tracking area update rejection message and recognizes that the request of UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission and reception of the tracking area update rejection message. The tracking area update rejection message may include an appropriate rejection reason. The tracking area update rejection message may be a response message to the tracking area update request message, and is not limited thereto, and may be a message that rejects the tracking area update request.

  Here, MME_A40 may include one or more pieces of identification information among the 21st to 26th identification information in the tracking area update rejection message, or by including these pieces of identification information, the request of UE_A10 is rejected. May be shown.

  Furthermore, each device may indicate the reason why the PDN connection procedure was rejected by transmitting and receiving the 21st identification information, and may perform a process to be performed by each device after the attach procedure to the core network _A90. May be shown.

  Further, each device transmits and receives the 22nd identification information and / or the 23rd identification information, so that the network supports connection to the core network_A90 and / or switching of the EPS service, and / or It may indicate that permission is not granted. Furthermore, each device transmits and receives the 24th identification information, and / or the 25th identification information, which indicates a mode of service continuation when switching to an NGS service that the network does not support and / or permit. Good.

  Further, each device may indicate a DCN whose network does not permit connection by transmitting and receiving the 26th identification information.

  Each device completes this procedure based on the completion of procedure (A) or (B) in this procedure.

  Further, each device may execute processing based on the identification information transmitted and received in this procedure based on completion of this procedure. For example, when each device transmits and receives one or more pieces of identification information among the twenty-first to twenty-sixth pieces of identification information, each device may indicate the reason why the request of UE_A10 was rejected. Furthermore, each device may indicate a process to be performed by each device based on the reason for rejecting the request of UE_A10, may perform the procedure again, or may perform the procedure under another condition. May be implemented. For example, the UE_A10 may execute connection to the core network_B190 and / or switch to the NGS service based on a process to be performed by each device included in the reason why the tracking area update procedure is rejected.

  Further, the above-described first, and / or third, and / or fourth condition determination is performed based on the identification information and / or the subscriber information included in the tracking area update request message, and / or the operator policy. May be done. In addition, the condition for determining whether the first, and / or third, and / or fourth condition is true is not limited to the above-described condition.

  For example, the first condition and / or the third condition and / or the fourth condition may be true if UE_A10 requests a tracking area update and the network grants the request. Further, the first condition and / or the third condition and / or the fourth condition may be false when UE_A10 requests a tracking area update and the network does not permit the request. Furthermore, the first condition, and / or the third condition, and / or the fourth condition are such that the network to which UE_A10 is connected and / or devices in the network support the tracking area update requested by UE_A10. If not, it may be false.

[1.4. Explanation of reconnection procedure]
Next, a reconnection procedure in the present embodiment will be described. Here, the reconnection procedure is a procedure from temporarily disconnecting the connection to establishing the connection again. In the present embodiment, a procedure for switching a PDN connection connected to the core network_A90 to a PDU session connected to the core network_B190 will be described. Further, this procedure may be a procedure for transitioning from a state of connecting to the core network_A90 to a state of connecting to the core network_B190. In this embodiment, two reconnection procedures will be described. Hereinafter, the first reconnection procedure and the second reconnection procedure will be described.

[1.4.1. Explanation of the first reconnection procedure]
The first reconnection procedure in the present embodiment will be described with reference to FIG. Hereinafter, this procedure refers to a first reconnection procedure, and each procedure includes a detach procedure, an attach procedure to the core network_B190, and a PDU session establishment procedure. The details of each procedure will be described later.

  This procedure is performed by the network to transition from a state in which UE_A10 is registered in core network_A90 to a state in which UE_A10 is registered in core network_B190. This is a procedure for changing and / or switching the connection service to be performed. Further, with this procedure, UE_A10 may change the core network to be accessed or the connection service to be used, or may maintain the IP address.

  First, each device transitions to the first state of connection to the core network_A90 (S1800). Note that the procedure for transition to the first state may be the initial procedure described in section 1.3. Next, each device executes a detach procedure (S1802), and transitions to a state where UE_A10 is not connected to core network_A90.

  Subsequently, each device executes an attach procedure to the core network_B190 (S1804), and transitions to a state in which the UE_A10 connects to the core network_B190. Further, each device may execute a PDU session establishment procedure (S1806). Here, attaching to core network_B190 is an attach procedure to core network_B190.

  In addition, each device may exchange various capability information and / or various request information of each device in a detach procedure and / or an attach procedure to the core network_B190 and / or a PDU session establishment procedure. For example, the UE_A10 may transmit at least one of the fifty-first to fifty-seventh identification information to the core network_B190 in the detach procedure.

  When each device exchanges various information and / or negotiates various requests by attaching to core network_B190, it exchanges various information and / or negotiates various requests by establishing a PDU session. It is not necessary. Conversely, when each device does not exchange various information and / or negotiate various requests in the attach procedure to the core network_B190, the various devices exchange the various information and / or negotiate various requests in the PDU session establishment procedure. May be implemented. Not limited to this, even if each device exchanges various information and / or negotiates various requests by attaching to the core network_B190, it establishes a PDU session to exchange various information and / or negotiate various requests. It may be carried out by a procedure.

  For example, in the attach procedure to the core network_B190, and in the PDU session establishment procedure, UE_A10 may transmit at least one of the 61st to 68th identification information to the core network_B190, Core network _B190, from UE_A10, receives at least one or more identification information of the 61st to 68th identification information, further at least 19th, and one or more identification information of the 26th identification information to UE_A10 You may send it.

  Also, UE_A10 may transmit at least one or more pieces of identification information among the 61st to 68th pieces of identification information to core network_B190 through the attach procedure, and may not transmit it through the PDU session establishment procedure. Similarly, the core network_B190 may transmit at least one or more of the 19th and 26th identification information to the UE_A10 in the attach procedure, and may not transmit it in the PDU session establishment procedure.

  Conversely, UE_A10 may transmit at least one of the 61st to 68th identification information to core network_B190 in the PDU session establishment procedure without transmitting it in the attach procedure. Similarly, the core network_B190 may transmit at least the nineteenth and twenty-sixth identification information in the PDU session establishment procedure without transmitting it in the attach procedure.

  Also, UE_A10 may transmit, to the core network_A90, identification information that has not been transmitted in the procedure for attaching to the core network_B190 among the 61st to 68th identification information in the PDU session establishment procedure. Similarly, core network_B190 may transmit, to UE_A10, identification information that has not been transmitted in the attach procedure to core network_B190 among the nineteenth and twenty-sixth identification information in the PDU session establishment procedure.

  By the above procedure, each device completes this procedure. Each device involved in this procedure transmits and receives one or more pieces of 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. You may. Further, each device may transition to an appropriate state based on completion of this procedure.

[1.4.1.1. Explanation of detach procedure]
First, the detach procedure will be described with reference to FIG. Hereinafter, this procedure refers to the detach procedure. In the present embodiment, the detach procedure is a procedure for disconnecting the connection between UE_A10 and the network (access network and / or core network_A90 and / or PDN_A5) under the initiative of the network. That is, if the UE_A10 is in the first state where it is connected to the core network_A90, the core network_A90 can start this procedure at an arbitrary timing. In other words, if UE_A10 is registered in core network_A90 (EMM-REGISTERD), core network_A90 may start this procedure at an arbitrary timing. In addition, each device may transition to a state in which UE_A10 is not registered in core network_A90 (EMM-DEREGISTERD) based on the completion of the detach procedure.

  First, MME_A40 transmits a detach request (Detach Request) message to UE_A10 via eNB_A45 (S1900), and starts a detach procedure. For example, based on the location information of UE_A10, MME_A40 may start the detach procedure based on determining that a device in core network_A90 cannot provide connectivity to UE_A10 in the future. Further, MME_A40 may start the detach procedure based on a change in the operator policy or a change in the subscriber information of UE_A10. Further, the MME_A40 may start the detach procedure based on a request from an upper layer or an application server. Note that the trigger by which the MME_A 40 starts the detach procedure is not limited to these.

  Here, the MME_A40 may include at least one of the 51st to 57th identification information in the detach request message. By including these identification information in the detach request message, MME_A40 may indicate the request to UE_A10. In other words, the MME_A40 may indicate that it requests the UE_A10 for the characteristic or content represented by each of the above-described identification information by including these identification information.

  Note that, in the attach procedure to the core network_A90 and / or the PDN connection procedure, the MME_A40 transmits at least one or more pieces of identification information among the eleventh to eighteenth pieces of identification information to the UE_A10. One or more of the identification information of 51 to 57 may be included in the detach request message.

  And / or MME_A40, at least the 51st to 57th, when allowing the service continuation to continue the communication by the attach procedure to the core network_B190 accompanying the detach procedure, and / or the PDU session establishment procedure accompanying the detach procedure, One or more pieces of identification information may be included in the detach request message. Here, the service continuation permission information may be managed as subscriber information for UE_A10. Therefore, MME_A40 may include these identification information based on the subscriber information of UE_A10.

  And / or the MME_A40 may perform an attach procedure to the core network_B190 associated with the detach procedure and / or a detach procedure for some or all of one or more PDN connections established before the start of the detach procedure. When performing service continuation to continue communication by the PDU session establishment procedure accompanying the above, at least one of the 51st to 57th identification information may be included in the detach request message.

  And / or the MME_A40 may perform an attach procedure to the core network_B190 associated with the detach procedure and / or a detach procedure for some or all of one or more PDN connections established before the start of the detach procedure. When performing service continuation to continue communication by the PDU session establishment procedure associated with and performing service continuation with IP address preservation, the 52nd identification information is included in the detach request message; otherwise, the 52nd identification information is included. It may be determined that the information is not included in the detach request message.

  And / or the MME_A40 may perform an attach procedure to the core network_B190 associated with the detach procedure and / or a detach procedure for some or all of one or more PDN connections established before the start of the detach procedure. Indicates NGC when performing service continuation to continue communication according to the PDU session establishment procedure accompanying with and when performing service continuation to switch the communication path or communication established for EPC to the communication path or communication established for NGC. The 53rd identification information may be included in the detach request message. Otherwise, the 53rd identification information indicating the EPC may be included in the detach request message, or it may be determined that the 53rd identification information is not included in the detach request message.

  For example, the MME_A40 may request the UE_A10 whether or not to start the attach procedure again by transmitting the 51st identification information. Also, UE_A10 may determine whether or not to start the attach procedure again based on the received 51st identification information.

  Note that the MME_A40 may request the reattachment procedure to the NSI indicated by the 55th identification information and / or the PDU session establishment procedure by transmitting the 55th identification information. Further, the UE_A10 may determine to execute the reattachment procedure to the NSI indicated by the 55th identification information and / or the PDU session establishment procedure by receiving the 55th identification information.

  Here, the re-attach procedure may be an attach procedure to the core network_A90 to be started based on completion of the detach procedure. Further, re-attaching may indicate that an attach procedure to the core network_A90 to be started is executed based on completion of the detach procedure.

  Note that the MME_A40 may notify the UE_A10 of the DCN identification information detached by the UE_A10 by transmitting the 56th identification information. Further, UE_A10 may hold the information for identifying the DCN to which UE_A10 is detached by receiving the 56th identification information.

  Note that the MME_A40 may request that one or more services be continued by the reattachment procedure and / or the PDU session establishment procedure by transmitting the 57th identification information. Also, UE_A10 receives the fifty-seventh identification information, and determines that one or more services indicated by the fifty-seventh identification information are to be continued by executing the re-attach procedure and / or the PDU session establishment procedure. May be.

  Here, the service identification information and the NSI performing the re-attach procedure and / or the PDU session establishment procedure may be transmitted and received in association with each other. Furthermore, when a plurality of pieces of service information are transmitted, different NSIs may be transmitted and received in association with each service. Note that these one or more NSIs may be the above-mentioned 56th identification information.

  And / or the MME_A40 may notify that the one or more services cannot be continued by the re-attach procedure and / or the PDU session establishment procedure by transmitting the 57th identification information. Also, the UE_A10 may determine that one or more services cannot be continued by the re-attach procedure and / or the PDU session establishment procedure by receiving the 57th identification information.

  Further, each device transmits and receives the 52nd identification information, and thus determines whether to use a handover flag in the procedure for attaching to the core network_B190 and / or the procedure for establishing a PDU session performed after the detachment procedure is completed. May be indicated.

  When the 52nd identification information indicates that transmission / reception of information indicating handover is necessary, the MME_A 40 transmits the 52nd identification information to start the core based on the completion of the detach procedure. In the procedure for attaching to the network_B 190 and / or the procedure for establishing a PDU session, the UE_A 10 may request that a flag indicating handover be transmitted. Further, UE_A10 receives the 52nd identification information, and in the attach procedure to the core network_B190 and / or the PDU session establishment procedure which starts based on the completion of the detach procedure, UE_A10 transmits a flag indicating handover. You may decide to do so.

  When the 52nd identification information indicates that transmission / reception of information indicating handover is unnecessary, the MME_A40 transmits the 52nd identification information to execute the core based on the completion of the detach procedure. In the procedure for attaching to the network_B 190 and / or the procedure for establishing a PDU session, it may be notified that a flag indicating handover by the UE_A10 is not necessary. Further, UE_A10 receives the 52nd identification information, and in the attach procedure to the core network_B190 and / or the PDU session establishment procedure which starts based on the completion of the detach procedure, UE_A10 transmits a flag indicating handover. You may decide not to.

  Here, the information indicating the handover may be the 61st identification information, or may be the identification information requesting the IP address preservation. Note that the IP address preservation may be to establish the connectivity by the same IP address as the IP address used before the switching, after executing the attach procedure and / or the PDU session establishment procedure again. In other words, the IP address preservation may be such that the IP address used after performing the attach procedure and / or the PDU session establishment procedure again is the same as the IP address used before the switching.

  Further, each device may indicate the core network to which UE_A10 should establish a connection after the detach procedure is completed, by transmitting and receiving the 53rd identification information. Also, the MME_A40 may transmit the 53rd identification information to notify the type of the core network to which the UE_A10 should establish a connection after the detach procedure is completed. UE_A10 may determine the type of core network to which UE_A10 should establish a connection after completion of the detach procedure by receiving the 53rd identification information.

  Furthermore, each device may indicate the reason for execution (Cause) of the detach procedure by transmitting and receiving the 54th identification information. Further, each device transmits and receives the 51st identification information, and / or the 52nd identification information, and / or the 54th identification information, so that when switching the connection destination of the PDN connection, the IP corresponding to the PDN connection is switched. It may indicate that the connectivity by the address can be maintained, or may request that the connectivity be maintained.

  In other words, each device transmits and receives the fifty-first identification information, and / or the fifty-second identification information, and / or the fifty-fourth identification information. It may indicate that a PDU session associated with the same IP address can be established, or may request that it be established. In addition, the 51st to 57th identification information may be transmitted and received as one identification information by combining two or more identification information. In this case, the combined identification information may be identification information having the meaning of each piece of identification information to be combined.

  Next, MME_A40 executes (A) in this procedure when PGW_A30 is selected as the external gateway, and executes (B) in this procedure when selecting SCEF_A46 as the external gateway.

  Hereinafter, each step of the procedure (A) in this procedure will be described. First, the MME_A 40 transmits a session deletion request (Delete Session Request) message to the SGW_A 35 (S1902), and starts the procedure (A) in this procedure.

  The MME_A40 may include at least one or more of the 51st to 57th identification information in the session deletion request message. MME_A40 may transmit the request to UE_A10 by including these identification information in the session deletion request message. Further, the SGW_A35 may transmit a session deletion request message to the PGW_A30 (S1904). The SGW_A35 may include at least one or more pieces of identification information among the identification information included in the received session deletion request message in the session deletion request message.

  PGW_A30, based on the reception of the session deletion request message from SGW_A35, sends a session deletion response (Delete Session Response) message to SGW_A35 (S1906), by deleting the context that constitutes information about the session and / or UE_A10, Release the session.

  Also, the PGW_A30 does not immediately release the session based on the reception of one or more pieces of identification information from the 51st to 57th identification information from the SGW_A35 to hold the context constituting the information on the session and / or UE_A10 for a certain period of time. You may release it afterwards. In this case, the PGW_A30 may manage the maintenance of the context using a timer. The value of the timer may be determined by a policy of the operator, or may be determined by other methods.

  Further, based on the reception of the session deletion response message from the PGW_A30, the SGW_A35 releases the session by transmitting a session deletion response message to the MME_A40 (S1908) and / or deleting a context that constitutes information on UE_A10.

  Each device completes the procedure (A) in this procedure with transmission / reception of the session deletion response message.

  Next, each step of the procedure (B) in this procedure will be described. First, the MME_A 40 may transmit a session deletion request message to the SCEF_A 46 (S1910), and start the procedure (B) in this procedure.

  Here, the MME_A40 may include at least one or more of the 51st to 57th identification information in the session deletion request message. MME_A40 may transmit the request to UE_A10 by including these identification information in the session deletion request message.

  The SCEF_A46 transmits a session deletion response message to the MME_A40 based on the reception of the session deletion request message from the MME_A40 (S1912), and releases the session by deleting the context that configures information on the session and / or UE_A10. Further, MME_A40 receives the session deletion response message. Further, each device completes the procedure (B) in this procedure with transmission / reception of the session deletion response message.

  Further, UE_A10 may receive the detach request message, and transmit a detach accept message to MME_A40 at an arbitrary timing (S1914). Note that the UE_A10 may include identification information such as a detach type for identifying the type of detachment in the detach acceptance message, or may indicate that the request is permitted by including the identification information.

  MME_A40 receives the detach acceptance message from UE_A10, and receives the session deletion response message, and / or based on the completion of the procedure (A) or (B) in this procedure, the signaling connection between UE_A10 and MME_A40. May be executed (S1916). Specifically, the connectivity between MME_A40 and eNB_A45 may be released by deleting the context of UE_A10 stored in MME_A40. Further, the eNB_A45 may release the RRC connection between the UE_A10 and the eNB_A45 by releasing the radio resources to the UE_A10 based on the release of the connection between the MME_A40 and the eNB_A45.

  Each device completes the detach procedure by the procedure of (A) or (B) in this procedure, and / or the transmission / reception of the detach acceptance message, and / or the procedure of deleting the signaling connection, and UE_A10 is connected to the core network_A90. Transition to a state that has not been registered. Each device may perform the following procedure based on completion of the detach procedure. Note that the next procedure may be an attach procedure to the core network_B190 and / or a PDU session establishment procedure.

  More specifically, each device is associated with the PDN connection disconnected in this procedure based on transmission / reception of the 51st identification information, and / or the 52nd identification information, and / or the 54th identification information. When maintaining connectivity by IP address, each device may execute the following procedure to establish a PDU session associated with the same IP address as the PDN connection. In this case, UE_A10 may transmit the 61st identification information indicating the handover procedure to the core network_B190 during the next procedure, or the 62nd identification information corresponding to the 57th identification information. Identification information may be transmitted.

  Further, based on the transmission and reception of the fifty-first identification information, and / or the fifty-second identification information, and / or the fifty-fourth identification information, each device uses the IP address associated with the PDN connection disconnected in this procedure. When establishing a PDU session associated with a new IP address without maintaining connectivity, each device may perform the following procedure. In this case, UE_A10 may transmit the 61st identification information indicating the initial procedure to core network_B190 during the next procedure.

  Further, each device, based on the transmission and reception of the 51st identification information, and / or the 52nd identification information, and / or the 53rd identification information, and / or the 54th identification information, information indicating handover When switching the connection destination from the used core network_A90 to the core network_B190, each device may execute the following procedure. In this case, UE_A10 may transmit the 61st identification information indicating the handover procedure to the core network_B190 during the next procedure, or the 11th identification information, and / or the 16th identification information. 63th identification information corresponding to this identification information may be transmitted.

  Furthermore, UE_A10 may transmit the sixteenth identification information corresponding to the eighteenth identification information and / or the forty-sixth identification information to the core network_A90 in the following procedure, The identification information and / or the sixty-fifth identification information corresponding to the forty-fifth identification information may be transmitted.

  Further, based on the transmission and reception of the fourteenth identification information, and / or the fifteenth identification information, and / or the forty-third identification information, and / or the transmission and reception of the forty-fourth identification information, permitted by the core network_A90, and / or If the supported SSC mode is SSC mode 1 or SSC mode 2, each device may execute the following procedure after the detach procedure. In this case, UE_A10 may transmit the 61st identification information indicating the handover procedure to the core network_B190 during the next procedure, or the 11th identification information, and / or the 16th identification information. 63th identification information corresponding to this identification information may be transmitted.

  Further, based on the transmission and reception of the fourteenth identification information, and / or the fifteenth identification information, and / or the forty-third identification information, and / or the transmission and reception of the forty-fourth identification information, permitted by the core network_A90, and / or If the supported SSC mode is SSC mode 3, each device may execute the following procedure after the detach procedure. In this case, UE_A10 may transmit the 61st identification information indicating the initial procedure to the core network_B190 during the next procedure, or the 11th identification information, and / or the 16th The 63rd identification information different from the identification information may be transmitted.

  Furthermore, based on the twelfth identification information, and / or the thirteenth identification information, and / or the forty-first identification information, and / or the forty-second identification information, the use of only the EPS service is permitted to UE_A10. In the case where the device transmits and receives the 54th identification information indicating that the use of the EPS service is no longer permitted in a supported state, each device may perform an attach procedure to the core network_B190, and / or a PDU. A session establishment procedure may be performed.

  Further, based on the twelfth identification information, and / or the thirteenth identification information, and / or the forty-first identification information, and / or the use of the EPS service and the NGS service based on the forty-second identification information, UE_A10 In the case where the 54th identification information indicating that the use of the EPS service is no longer permitted is transmitted and received in a state in which the use of the EPS service is not permitted in each of the devices, the device does not execute the attach procedure to the core network_B190. Alternatively, a PDU session establishment procedure may be performed.

  When each device executes the next procedure after the completion of the detach procedure, UE_A10 transmits identification information corresponding to the identification information received from core network_A90 to core network_B190 in the next procedure. May be. For example, UE_A10 may transmit the 62nd identification information corresponding to the 57th identification information to the core network_B190 in the following procedure, the 11th identification information, and / or the 16th identification information. The 63rd identification information corresponding to the identification information may be transmitted. Further, UE_A10 may transmit the sixteenth identification information corresponding to the eighteenth identification information and / or the forty-sixth identification information to the core network_B190 in the following procedure, The identification information and / or the sixty-fifth identification information corresponding to the forty-fifth identification information may be transmitted. Further, UE_A10 may transmit the 68th identification information corresponding to the 56th identification information to core network_B190 during the following procedure.

[1.4.1.2. Outline of procedure for attaching to core network_B]
Next, an outline of the procedure for attaching to core network_B190 will be described. In the present embodiment, the procedure for attaching to the core network_B190 is a procedure for connecting to the network (the access network and / or the core network_B190 and / or the PDN_A5) led by the UE_A10.

  UE_A10 may execute this procedure at an arbitrary timing such as when the terminal is powered on, if the UE_A10 is not connected to the core network_B190, or may perform the core based on the detach procedure described in section 1.4.1.1. It may be executed based on the decision to attach to network_B190. In other words, UE_A10 may start this procedure at an arbitrary timing as long as it is not registered in core network_B190 (EMM-DEREGISTERED). Further, each device may transition to the registration state (EMM-REGISTERED) based on the completion of the attach procedure to core network_B190.

  UE_A10 may start the procedure for attaching to core network_B190 based on receiving at least one piece of identification information among the 51st to 57th pieces of identification information in the detachment procedure. Also, UE_A10 may start the procedure of attaching to core network_B190 based on other triggers.

[1.4.1.3. PDU session establishment procedure example]
Next, an example of a PDU session establishment procedure will be described. Hereinafter, this procedure refers to a PDU session establishment procedure. This procedure is for each device to establish a PDU session. Note that each device may execute this procedure in a state where the procedure for attaching to the core network_B190 is completed, or may be executed during the procedure for attaching to the core network_B190. Also, each device may start this procedure at an arbitrary timing after the procedure for attaching to core network_B190. Further, each device may establish a PDU session based on the completion of the PDU session establishment procedure. Furthermore, each device may establish a plurality of PDU sessions by executing this procedure a plurality of times.

  An example of a procedure for executing the PDU session establishment procedure will be described with reference to FIG. Hereinafter, each step of this procedure will be described. First, UE_A10 transmits a PUD session establishment request (PDU Session Establishment Request) message to CPF_A140 via eNB_A45 (S2000), and starts a PDU session establishment procedure.

  Here, UE_A10 may include at least one of the 61st to 68th identification information in the PDU session establishment request message. UE_A10 may include such identification information to indicate that UE_A10 requests the characteristic or content represented by each of the above-described identification information. In other words, by including these identification information, that the UE_A10 is requesting the establishment of a PDU session having the characteristics represented by each identification information described above, or a PDU session reflecting the content represented by each identification information described above. May be shown.

  UE_A10, in the detach procedure, based on the reception of at least one of the identification information of the fifty-first to fifty-seventh, at least one of the sixty-first to sixty-eighth identification information of the PDU session establishment request May be included in the message.

  Further, each device may transmit and receive the 61st identification information to indicate that UE_A10 requests a session to the core network_B190, or that this request is a request by handover from the core network_A90. May be indicated.

  Further, each device may indicate the session in which UE_A10 requests a handover by transmitting and receiving the 62nd identification information.

  Furthermore, each device may indicate the APN requested by UE_A10 by transmitting and receiving the 63rd identification information. Note that the APN may be the same as the APN obtained during the previous PDN connection procedure.

  Further, each device may indicate the previously connected CPF_A140 by transmitting and receiving the 64th identification information, or may indicate that this request is a re-attach procedure.

  Further, each device may indicate information for identifying UE_A10 by transmitting the 65th identification information. The 65th identification information may be GUTI acquired during a previous PDN connection procedure or TAU procedure, or may be IMSI.

  Furthermore, each device may indicate the type of connection service requested by UE_A10 by transmitting and receiving the 66th identification information.

  Furthermore, each device may indicate the type of connection service supported by UE_A10 by transmitting and receiving the 67th identification information.

  Further, each device may indicate the network slice type or NSI requested by UE_A10 by transmitting and receiving the 68th identification information.

  Further, by transmitting and receiving the 61st identification information, each device may request establishment of a PDU session for maintaining connectivity by the IP address associated with the PDN connection before switching, or may perform switching. It may request that the same IP address as the IP address associated with the previous PDN connection be assigned to the PDU session to be established.

  Note that the PDN connection before switching may be a PDN connection established for the EPS service and / or the core network_A90.

  CPF_A140 receives the PUD session establishment request message and performs a first condition determination. The first condition determination is for determining whether CPF_A140 accepts the request of UE_A10. In the first condition determination, the CPF_A140 determines whether the first condition is true or false. CPF_A140 may start the procedure of (A) in this procedure if the first condition determination is true, and may start the procedure of (B) in this procedure if the first condition determination is false. .

  Hereinafter, steps when the first condition determination is true, that is, each step of the procedure (A) in this procedure will be described. CPF_A140 starts the procedure of (C) in this procedure, and starts the procedure of (A) in this procedure. Hereinafter, each step of the procedure (C) in this procedure will be described.

  CPF_A140 transmits a session creation request message to SGW_A35, and starts the procedure (C) in this procedure (S2002).

  Here, the CPF_A140 may include at least one or more pieces of identification information among the 61st to 68th pieces of identification information in the session creation request message, or may include information indicating whether the request is an initial request. Then, the request of UE_A10 may be transmitted by including these identification information.

  Further, UPGW_A130 receives the session creation request message, and performs the second condition determination. The second condition determination is for the UPGW_A130 to determine whether to accept the request of UE_A10. The second condition is true when the request from UE_A10 is accepted, and may be when the request from UE_A10 is permitted. Further, the second condition is false when the request of UE_A10 is rejected, and may be when the second condition is not determined to be true.

  Also, the second condition determination may be performed by another device (for example, PCRF_A60) instead of UPGW_A130. In that case, UPGW_A130 performs an IP-CAN session establishment procedure with PCRF_A60. More specifically, UPGW_A130 transmits a request message during the IP-CAN session establishment procedure to PCRF_A60. Further, PCRF_A60 receives the request message during the IP-CAN session establishment procedure, determines the second condition, and transmits a response message during the IP-CAN session establishment procedure to UPGW_A130. Further, UPGW_A130 receives the response message during the IP-CAN session establishment procedure, and recognizes the result of the second condition determination.

  Here, the UPGW_A130 may include at least one or more of the identification information of the 61st to 68th identification information in the request message during the IP-CAN session establishment procedure, or may include these identification information. , UE_A10 may be transmitted.

  Further, the PCRF_A60 may include at least the result of the second information determination in the response message during the IP-CAN session establishment procedure, or by including this result, notifies the UPGW_A130 of the result of the second condition determination. Alternatively, including this information may indicate that the request of UE_A10 has been permitted or denied.

  Also, if UPGW_A130 is not tied to an external gateway (PGW_A30 or SCEF_A46) and / or is not configured as the same device, UPGW_A130 may send a session creation request message to the external gateway. Further, the external gateway that has received the session creation request message performs the second condition determination, and may transmit a session creation response message to the UPGW_A130, including the second condition determination result, or may include this result. Alternatively, the result of the second condition determination may be notified to UPGW_A130, or by including this information, it may be indicated that the request of UE_A10 has been permitted or rejected.

  When the external gateway performs the second condition determination, UPGW_A130 may perform the second condition determination based on the result of the second condition determination received from the external gateway. For example, if PCRF_A60 or PGW_A30 accepts the request of UE_A10, PCRF_A60 or PGW_A30, and UPGW_A130 may set the second condition to true, and reject the request of UE_A10, if May be false.

  In the second condition determination, the UPGW_A130 determines whether the second condition is true or false. When the second condition is true, UPGW_A130 transmits a session creation response message to CPF_A140 (S2008). Further, CPF_A140 receives the session creation response message.

  Further, UPGW_A130 may include the IP address in the session creation response message, or may include the identification information to indicate that the request of UE_A10 is permitted. Note that the IP address may be the same as the IP address to which UE_A10 was assigned in the previous connection. For example, UPGW_A130 receives the one or more identification information among the 61st to 68th identification information, and / or stores the IP address based on storing the context that constitutes information about the session and / or UE_A10. Alternatively, the value may be the same as the IP address to which UE_A10 was previously assigned.

  If the second condition is false, UPGW_A130 transmits a session creation rejection message to CPF_A140 (S2008). Note that the session creation rejection message may be a session creation response message including a reason for rejection (Reject cause), or may include a reason for rejection to indicate that the request of UE_A10 has been rejected.

  Each device completes the procedure (C) of this procedure based on transmission / reception of the session creation response message and / or the session creation rejection message.

  CPF_A140 transmits a PDU session establishment accept message to NR node_A122 based on the reception of the session creation response message (S2014). When the CPF_A140 receives the session creation rejection message, the CPF_A140 may start the procedure (B) in this procedure without continuing the procedure (A) in this procedure. When the PDU session is a PDN connection, the PDU session establishment acceptance message may be a PDN connection acceptance message or a default EPS bearer context activation request message. Also, the message that CPF_A140 transmits to eNB_A45 may be a response message to the PUD session establishment request message, and is not limited to this, and may be a message that accepts a request for establishing a PDU session.

  eNB_A45 receives the PUD session establishment acceptance message, UE_A10 RRC message (e.g., RRC Connection Reconfiguration message or RRC Connection Setup message, may be an RRC message such as RRC Direct Transfer message), and / or PUD session establishment acceptance message Is transmitted (S2016). Note that the PUD session establishment acceptance message may be transmitted and received while being included in the RRC message.

  Here, CPF_A140 may include the IP address in the PUD session establishment acceptance message, or may indicate that the request of UE_A10 is permitted by including the identification information.

  When receiving the RRC message, UE_A10 transmits an RRC message (for example, an RRC message such as an RRC Connection Reconfiguration Complete message, an RRC Connection Setup Complete message, or an RRC Direct Transfer message) to eNB_A45 (S2018). eNB_A45 receives the RRC message, and transmits a bearer setup message to CPF_A140 (S2020). Further, CPF_A140 receives the bearer setup message.

  When receiving the PUD session establishment acceptance message, UE_A10 transmits a PDU session establishment complete (PDU Session Establishment complete) message to CPF_A140 via eNB_A45 (S2022) (S2024). When the PDU session is a PDN connection, the PDU session establishment completion message may be a PDN connection completion message or an Activate default EPS bearer context accept message.

  Further, the message transmitted by UE_A10 to eNB_A45 and CPF_A140 may be a response message to the PUD session establishment request message, and is not limited to this, and may be a message indicating that the PDU session establishment procedure is completed. Further, CPF_A140 receives the PDU session establishment completion message, and performs the third condition determination.

  The third condition determination is for determining whether the CPF_A140 needs to request the UPGW_A130 to change the bearer. If the third condition is true, CPF_A140 starts the procedure (D) in this procedure. If the third condition determination is false, CPF_A140 does not execute the procedure (D) in this procedure.

  Hereinafter, each step of the procedure (D) in the procedure will be described. First, CPF_A140 transmits a bearer change request message to UPGW_A130 (S2026), and starts the procedure (D) in this procedure. Further, UPGW_A130 receives the bearer change request message, and transmits a bearer change response message to CPF_A140 (S2028). Further, CPF_A140 receives the bearer change response message, and completes the procedure (D) of this procedure. Each device completes the procedure (A) in this procedure based on the transmission and reception of the PDU session establishment completion message and / or the completion of the procedure (D) in this procedure.

  Next, each step of the procedure (B) in this procedure will be described. CPF_A140 transmits a PDU Session establishment reject message to UE_A10 via NR node_A122 (S2030), and starts the procedure of (B) in this procedure. Further, UE_A10 receives the PDU session reject message and recognizes that the request of UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission and reception of the PDU session rejection message. The PDU session reject message may include an appropriate reject reason. Further, the PDU session establishment rejection message may be a response message to the PUD session establishment request message, and is not limited thereto, and may be a message that rejects the request for establishing the PDU session.

  Also, CPF_A140 may include the 26th identification information in the PDU session establishment rejection message, or may indicate that the request of UE_A10 has been rejected by including this identification information.

  Further, each device may indicate the network slice type that UE_A10 requests and the network rejects by transmitting and receiving the 26th identification information.

  Each device completes this procedure based on the completion of procedure (A) or (B) in this procedure. 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 the present procedure, or may perform transition based on the completion of the procedure (B) in the present procedure. It may recognize that this procedure has been rejected, and may transition to a state where a PDU session has not been established.

  Further, each device may execute processing based on the identification information transmitted and received in this procedure based on completion of this procedure. For example, when transmitting and receiving the 26th identification information, each device may recognize the reason why the request of UE_A10 was rejected. Further, each device may perform this procedure again based on the reason that the request of UE_A10 is rejected, or may perform this procedure under another condition.

  Further, the above-described first to third condition determinations may be executed based on identification information and / or subscriber information and / or an operator policy included in the PUD session establishment request message. Further, the conditions for determining whether the first to third conditions are true or false are not limited to the above-described conditions.

  For example, the first condition and / or the second condition may be true if UE_A10 requests a session establishment and the network grants the request. Further, the first condition and / or the second condition may be false when UE_A10 requests establishment of a session and the network does not permit the request. Further, the first condition and / or the second condition may be false if the network to which UE_A10 is connected and / or devices in the network do not support the establishment of the session requested by UE_A10.

[1.4.1.4. Example of procedure for attaching to core network_B]
An example of a procedure for executing an attach procedure to core network_B190 will be described with reference to FIG. Hereinafter, this procedure refers to a procedure for attaching to the core network_B190. This procedure is for the UE_A10 to be registered in the core network_B190. Hereinafter, each step of this procedure will be described. First, UE_A10 transmits an attach request message to CPF_A140 via NR node_A122 (S2100), and starts an attach procedure. UE_A10 may transmit the attach request message including the above-described PUD session establishment request message or include the PUD session establishment request message to request that the PDU session establishment procedure be performed during the attach procedure. May be.

  Here, UE_A10 may include at least one or more of the 61st to 68th identification information in the attach request message. UE_A10 may include these pieces of identification information to indicate that UE_A10 requests the characteristic or content represented by each piece of identification information described above. In other words, by including these identification information, UE_A10 is requesting an attach having the characteristics represented by each of the above-described identification information, or an attachment reflecting the contents represented by each of the above-described identification information, and / or a connection. May be indicated. And / or by including these identification information, UE_A10 requests the establishment of a PDU session having the characteristics represented by each identification information described above, or a PDU session reflecting the content represented by each identification information described above. May be indicated.

  Further, each device may transmit and receive the 61st identification information to indicate that UE_A10 requests a session to the core network_B190, or that this request is a request by handover from the core network_A90. May be indicated.

  Further, each device may indicate the session in which UE_A10 requests a handover by transmitting and receiving the 62nd identification information.

  Furthermore, each device may indicate the APN requested by UE_A10 by transmitting and receiving the 63rd identification information. Note that the APN may be the same as the APN acquired during the PDN connection procedure at the handover source.

  Further, each device may indicate the previously connected CPF_A140 by transmitting and receiving the 64th identification information, or may indicate that this request is a re-attach procedure.

  Further, each device may indicate information for identifying UE_A10 by transmitting the 65th identification information. The 65th identification information may be GUTI acquired during a previous PDN connection procedure or TAU procedure, or may be IMSI.

  Furthermore, each device may indicate the type of connection service requested by UE_A10 by transmitting and receiving the 66th identification information.

  Furthermore, each device may indicate the type of connection service supported by UE_A10 by transmitting and receiving the 67th identification information.

  Further, each device may indicate the network slice type or NSI requested by UE_A10 by transmitting and receiving the 68th identification information.

  Further, by transmitting and receiving the 61st identification information, each device may request establishment of a PDU session for maintaining connectivity by the IP address associated with the PDN connection before switching, or may perform switching. It may request that the same IP address as the IP address associated with the previous PDN connection be assigned to the PDU session to be established.

  Note that the UE_A10 may transmit the identification information included in a control message (for example, an ESM information request / response message or the like) different from the attach request message (S2102).

  CPF_A140 receives the attach request message and / or a control message different from the attach request message, and executes the first condition determination. The first condition determination is for determining whether or not CPF_A140 accepts the request of UE_A10. CPF_A140 starts the procedure of (A) in this procedure when the first condition is true, and starts the procedure of (B) in this procedure when the first condition is false. Details of the procedure (B) in this procedure will be described later.

  Hereinafter, each step of the procedure (A) in this procedure will be described. CPF_A140 executes the second condition determination, and starts the procedure (A) in this procedure. The second condition determination is for determining whether or not CPF_A140 performs a PDN connection procedure. In the second condition determination, the CPF_A140 determines whether the second condition is true or false. The CPF_A 140 starts the procedure (C) in the PDU session establishment procedure when the second condition is true, and omits the procedure when the second condition is false (S2104). Further, CPF_A140 transmits an attach accept (Attach accept) message to NR node_A122 based on the reception of the attach request message and / or the session creation response message (S2106). When the CPF_A140 receives the session creation rejection message, the CPF_A140 may start the procedure (B) in this procedure without continuing the procedure (A) in this procedure.

  Here, CPF_A140 may include an IP address, or may include the identification information to indicate that the request of UE_A10 has been accepted.

  Here, the second condition determination is for the CPF_A140 to determine whether or not to execute a PDU session establishment procedure. The second condition is true when the PUD session establishment request message is received, and the PDU session establishment procedure may be executed during this procedure. Further, the second condition is false when the PUD session establishment request message is not received, the PDU session establishment procedure may not be executed in this procedure, or the second condition is not determined to be true. Is fine.

  Next, the NR node_A122 receives the attach acceptance message, and transmits an RRC message to the UE_A10 (e.g., an RRC message such as an RRC Connection Reconfiguration message or an RRC Connection Setup message, or an RRC Direct Transfer message) and / or an attach acceptance message. It transmits (S2108). The attach acceptance message may be transmitted and received while being included in the RRC message. Further, when the second condition is true, the CPF_A140 may transmit the attach acceptance message including the above-described PUD session establishment acceptance message, or may include the PUD session establishment acceptance message to perform the PDU session establishment procedure. May have been accepted.

  When UE_A10 receives an RRC message from the NR node_A122, UE_A10 transmits an RRC connection message (for example, an RRC message such as an RRC Connection Reconfiguration Complete message or an RRC Connection Setup Complete message, or an RRC Direct Transfer message) to the NR node_A122. Yes (S2110). NR node_A122 receives the RRC message, and transmits a bearer setup message to CPF_A140 (S2112). Further, CPF_A140 receives the bearer setup message.

  When UE_A10 receives an attach acceptance message from CPF_A140 via NR node_A122, UE_A10 transmits an attach complete (Attach complete) message to CPF_A140 via NR node_A122 (S2114) (S2116). Further, CPF_A140 receives the attach completion message. Further, when the second condition is true, the CPF_A 140 starts the (D) procedure in the PDU session establishment procedure (S2118). If the second condition is false, CPF_A140 does not execute the procedure (D) in the PDU session establishment procedure. Each device completes the procedure (A) in this procedure based on the transmission and reception of the attach completion message and / or the completion of the procedure (D) in the PDU session establishment procedure.

  Note that, when receiving the PUD session establishment acceptance message, the UE_A10 may transmit the attach completion message including the PDU session establishment completion message described above, or may include the PDU session establishment completion message to establish the PDU session establishment. It may indicate that the procedure is completed.

  Next, each step of the procedure (B) in this procedure will be described. CPF_A140 transmits an attach rejection (Attach reject) message to UE_A10 via NR node_A122, and starts the procedure (B) in this procedure (S2120). Further, UE_A10 receives the attach reject message and recognizes that the request of UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission and reception of the attach rejection message. If the second condition is true, the CPF_A140 may transmit the attach rejection message including the PDU session establishment rejection message described above, or may include the PDU session establishment rejection message to perform the PDU session establishment procedure. May be rejected. In that case, UE_A10 may further receive a PDU session establishment rejection message or authenticate that the PDU session establishment procedure has been rejected.

  Each device completes this procedure based on the completion of procedure (A) or (B) in this procedure. Note that each device may transition to a state where UE_A10 is connected to the network and / or a state registered in the core network_B190 based on the completion of the procedure (A) in this procedure. Based on the completion of the procedure (B) in the above, it may recognize that this procedure has been rejected, and may transition to a state where it cannot connect to the network and / or a state where it cannot be registered with the core network_B190. Is also good. The transition of each device to each state may be performed based on the completion of this procedure, or may be performed based on the establishment of a PDU session.

  Further, each device may execute processing based on the identification information transmitted and received in this procedure based on completion of this procedure. For example, when transmitting and receiving the 26th identification information, each device may recognize the reason why the request of UE_A10 was rejected. Furthermore, each device may perform this procedure again based on the reason that the request of UE_A10 is rejected, or may perform an attach procedure to core network_A90 or another cell.

  Further, the first and second condition determinations described above may be executed based on identification information and / or subscriber information included in the attach request message, and / or an operator policy. Further, the conditions for determining whether the first and second conditions are true or false may not be limited to the above-described conditions.

[1.4.2. Explanation of the second reconnection procedure]
Next, a second reconnection procedure in the present embodiment will be described with reference to FIG. Hereinafter, this procedure refers to a second reconnection procedure, and each procedure includes a PDN connection disconnection procedure and / or a PDU session establishment procedure. The details of each procedure will be described later.

  This procedure is to move the session led by the network, UE_A10 establishes to the core network_A90 to the core network_B190, and to establish the core network that establishes the session and the connection service used in the session. This is the procedure to change.

  In contrast to the first reconnection procedure, which is a procedure for simultaneously switching the attached sessions, this procedure provides a method for switching at least one session at a time. Note that the attached state may be a state where UE_A10 is connected to the network, and the unattached state may be a state where UE_A10 is not connected to the network.

  First, each device transitions to the first state of connection to the core network_A90 (S2200). Note that the procedure for transition to the first state may be the initial procedure described in section 1.3.

  Next, each device executes the procedure (A) in this procedure. Hereinafter, each step of the procedure (A) in this procedure will be described.

  Each device executes the PDN connection disconnection procedure (S2202), and starts the procedure (A) in this procedure. Each device releases at least one PDU session by performing a PDN disconnection procedure. At this time, if a PDU session other than the PDU session to be released is not established between UE_A10 and the core network_A90, each device explicitly or implicitly sets the UE_A10 in a state where the UE_A10 is not registered in the core network_A90. It may transition. In order to explicitly transition to a state where UE_A10 is not registered in core network_A90, each device may execute the detach procedure described above.

  Subsequently, each device executes a PDU session establishment procedure (S2208). At this time, UE_A10 may be in a state of attaching to core network_B190 and / or in a state of being registered. Or, when UE_A10 is in a state where it is not attached to the core network_B190 and / or in a state where it is not registered, each device executes the above-described attach procedure to the core network_B190, and after transiting to the registration state. , PDU session establishment procedure.

  Each device completes the procedure (A) in this procedure by executing the PDU session establishment procedure. Further, each device may execute the procedure (A) in this procedure again. In other words, in the first state during this procedure, when a plurality of PDN connections are established between UE_A10 and the core network_A90, each device performs (A) in this procedure for each PDN connection. The procedure may be performed. Each device may execute the procedure (A) in this procedure at least once or more.

  Note that UE_A10 may maintain a PDN connection to one or more core networks_A90 except for the PDN connection disconnected based on the PDN connection disconnection procedure, and may continue communication using these PDN connections. .

[1.4.2.1. PDN disconnection procedure description]
The PDN connection disconnection procedure in the present embodiment will be described with reference to FIG. Hereinafter, this procedure refers to the PDN disconnection procedure. This procedure is a procedure for disconnecting and / or releasing the PDN connection established by UE_A10. Note that each device may disconnect or release a plurality of PDN connections by executing this procedure a plurality of times.

  Hereinafter, each step of this procedure will be described. First, each device executes the procedure (A) or (B) in the detach procedure (S2302). In detail, each device starts (A) during the detach procedure when the external gateway of the session requesting disconnection / release is PGW_A30, and when the external gateway of the session requesting disconnection / release is SCEF_A46. Then, the procedure of (B) in the detach procedure is started.

  Based on the completion of the procedure (A) or (B) in the detach procedure, the MME_A40 transmits a Deactivate EPS bearer Context Request message to the UE_A10 via the eNB_A45 (S2304). Further, UE_A10 receives the EPS bearer context deactivation request message.

  Here, the MME_A40 may include at least the 71st to 76th identification information in the EPS bearer context deactivation request message. By including these identification information in the EPS bearer context deactivation request message, MME_A40 may indicate the request to UE_A10. In other words, the MME_A40 may indicate that it requests the UE_A10 for the characteristic or content represented by each of the above-described identification information by including these identification information.

  Note that, in the attach procedure to the core network_A90 and / or the PDN connection procedure, the MME_A40 transmits at least one or more pieces of identification information among the eleventh to eighteenth pieces of identification information to the UE_A10. One or more of the identities 71 to 76 may be included in the EPS bearer context deactivation request message.

  And / or MME_A40, if allowing service continuation to continue communication by the PDU session establishment procedure accompanying the PDN disconnection procedure, at least one of the 71st to 76th identification information, the EPS bearer context It may be included in the deactivation request message. Here, the permission information for the service continuation may be managed as subscriber information for UE_A10. Therefore, MME_A40 may include these identification information based on the subscriber information of UE_A10.

  And / or MME_A40, when performing a service continuation to continue the communication by the PDU session establishment procedure accompanying the PDN disconnection procedure for the PDN connection to be disconnected, at least one of the identification information of the 71st to 76th identification information May be included in the EPS bearer context deactivation request message.

  And / or, MME_A40 performs a service continuation for continuing the communication by the PDU session establishment procedure accompanying the PDN disconnection procedure for the PDN connection to be disconnected, and when performing the service continuation with the IP address preservation, The 74th identification information may be included in the EPS bearer context deactivation request message, and otherwise, it may be determined that the 74th identification information is not included in the EPS bearer context deactivation request message.

  And / or the MME_A40 performs a service continuation for continuing the communication by the PDU session establishment procedure accompanying the PDN disconnection procedure for the PDN connection to be disconnected, and NGC establishes a communication path or communication with the EPC. In the case of performing service continuation to switch to a communication path or communication established with respect to, the 73rd identification information indicating NGC may be included in the EPS bearer context deactivation request message. Otherwise, the 73rd identification information indicating the EPC may be included in the EPS bearer context deactivation request message, or it is determined that the 73rd identification information is not included in the EPS bearer context deactivation request message. Is also good.

  For example, by transmitting the 71st identification information, the MME_A40 disconnects and / or switches the PDN connection and / or the bearer indicated by the 71st identification information, and / or requests the UE_A10 to perform handover. Is also good. Further, the UE_A10 may determine the PDN connection and / or the bearer that performs disconnection and / or switching and / or handover by receiving the 71st identification information.

  Furthermore, each device may indicate the reason for this request by transmitting and receiving the 72nd identification information. The 72nd identification information may be, for example, information indicating a handover request.

  Further, the MME_A40 transmits the 73rd identification information, requests the system indicated by the 73rd identification information to execute a session re-establishment procedure, and perform a session reactivation. May be. UE_A10 receives the 73rd identification information, executes a session re-establishment procedure for the system indicated by the 73rd identification information, and decides to perform session reactivation (reactivation). May be. Note that the session reactivation may be to establish a PDU session by executing a PDU connection procedure.

  Further, each device may transmit and receive the 74th identification information, and thus may be information indicating whether transmission and reception of information indicating handover is necessary during re-establishment of the session.

  If the seventy-fourth identification information indicates that transmission / reception of information indicating handover is necessary, MME_A40 is started based on the completion of the PDN disconnection procedure by transmitting the seventy-fourth identification information. In the PDU session establishment procedure, UE_A10 may request to transmit a flag indicating handover. Further, UE_A10, by receiving the 74th identification information, in the PDU session establishment procedure to be started based on the PDN disconnection procedure completion, in the PDU session establishment procedure, UE_A10 decides to transmit a flag indicating handover UE_A10 Is also good.

  When the 74th identification information indicates that transmission / reception of information indicating handover is unnecessary, MME_A40 is executed based on the completion of the PDN disconnection procedure by transmitting the 74th identification information. In the PDU session establishment procedure, a flag indicating handover by UE_A10 may be notified that transmission is not necessary. Further, UE_A10, by receiving the 74th identification information, in the PDU session establishment procedure to the core network_B190 to be started based on the completion of the detach procedure, determines that UE_A10 does not transmit a flag indicating handover. May be.

  Here, the information indicating the handover may be the 61st identification information, or may be the identification information requesting the IP address preservation. Note that the IP address preservation may be to establish connectivity with the same IP address as the IP address used before the switching after performing the attach procedure and / or the PDU session establishment procedure again. . In other words, the IP address preservation may be that the IP address used after performing the attach procedure and / or the PDU session establishment procedure again is the same as the IP address still used before the switching.

  Further, the MME_A40 may notify the UE_A10 of the DCN in which the PDN connection to be disconnected has been established by transmitting the 75th identification information. Further, by receiving the 75th identification information, the DCN in which the PDN connection to be disconnected has been established may be received.

  Also, MME_A40 may request to execute a PDU session establishment procedure for the NSI indicated by the 76th identification information by transmitting the 76th identification information. Further, UE_A10 may determine to execute the PDU session establishment procedure for the NSI indicated by the 76th identification information by receiving the 76th identification information.

  In other words, MME_A40 may request the NSI indicated by the 76th identification information to establish a PDU session by transmitting the 76th identification information. Also, UE_A10 may determine to establish a PDU session for the NSI indicated by the 76th identification information by receiving the 76th identification information. Further, each device may transmit and receive the 75th and / or 76th identification information to indicate the currently connected DCN and / or the NSI to be connected when switching to the NGS connection service. . Furthermore, each device transmits and receives the 72nd identification information and / or the 74th identification information, so that when the connection destination of the PDN connection is switched, the connectivity by the IP address corresponding to the PDN connection is maintained. May be indicated or may be required to be maintained.

  In other words, each device transmits and receives the 72nd identification information and / or the 74th identification information, and after the completion of the PDN connection disconnection procedure, to the same IP address as the PDN connection disconnected by the PDN connection disconnection procedure. The associated PDU session may indicate that it can be established or may require it to be established.

  Note that the 71st to 76th identification information may be transmitted and received as one identification information by combining two or more identification information. In this case, the combined identification information may be identification information having the meaning of each piece of identification information to be combined.

  UE_A10 that has received the EPS bearer context deactivation request message may transmit an EPS bearer context deactivation acceptance (Deactivate EPS bearer Context Accept) message to MME_A40 via eNB_A45 (S2310). Further, MME_A40 may receive the EPS Bearer Context Deactivation Accept message.

  Each device may complete this procedure based on sending and receiving the EPS bearer context deactivation acceptance message. Upon completion of this procedure, each device may transition to a state where the PDN connection is disconnected.

  Further, each device may execute the following procedure based on the completion of the PDN connection disconnection procedure. Note that the next procedure may be a PDU session establishment procedure. Note that UE_A10 may start the PDU session establishment procedure based on the reception of at least one of the 71st to 76th identification information in the PDN disconnection procedure. More specifically, when each device maintains connectivity by the IP address associated with the PDN connection disconnected in this procedure based on the transmission and reception of the 72nd identification information and / or 74th identification information Each device may perform the following procedure to establish a PDU session associated with the same IP address as the PDN connection. In this case, UE_A10 may transmit the 61st identification information indicating the handover procedure to the core network_B190 to the core network_B190 during the following procedure, or may transmit the 61st identification information to the 71st identification information. The corresponding 62nd identification information may be transmitted.

  Also, based on the transmission and reception of the 72nd identification information and / or 74th identification information, each device does not maintain the connectivity by the IP address associated with the PDN connection disconnected in this procedure, and When establishing a PDU session associated with an IP address, each device may perform the following procedure. In this case, UE_A10 may transmit the 61st identification information indicating the initial procedure to core network_B190 during the next procedure.

  Further, each device is based on the transmission and reception of the 72nd identification information, and / or the 73rd identification information, and / or 74th identification information, from the core network _A90 using information indicating handover to the core network When switching the connection destination to _B190, each device may execute the following procedure. In this case, UE_A10 may transmit the 61st identification information indicating the handover procedure to the core network_B190 during the next procedure, or the 11th identification information, and / or the 16th identification information. 63th identification information corresponding to this identification information may be transmitted. Further, UE_A10 may transmit the sixteenth identification information corresponding to the eighteenth identification information and / or the forty-sixth identification information to the core network_B190 in the following procedure, The identification information and / or the sixty-fifth identification information corresponding to the forty-fifth identification information may be transmitted.

  Further, based on the transmission and reception of the fourteenth identification information, and / or the fifteenth identification information, and / or the forty-third identification information, and / or the transmission and reception of the forty-fourth identification information, permitted by the core network_A90, and / or If the supported SSC mode is SSC mode 1 or SSC mode 2, each device may execute the following procedure after the detach procedure. In this case, UE_A10 may transmit the 61st identification information indicating the handover procedure to the core network_B190 during the next procedure, or the 11th identification information, and / or the 16th identification information. 63th identification information corresponding to this identification information may be transmitted.

  Further, based on the transmission and reception of the fourteenth identification information, and / or the fifteenth identification information, and / or the forty-third identification information, and / or the transmission and reception of the forty-fourth identification information, permitted by the core network_A90, and / or If the supported SSC mode is SSC mode 3, each device may execute the following procedure after the detach procedure. In this case, UE_A10 may transmit the 61st identification information indicating the initial procedure to the core network_B190 during the next procedure, or the 11th identification information, and / or the 16th The 63rd identification information different from the identification information may be transmitted.

  Note that when each device executes the next procedure after the completion of the PDN connection disconnection procedure, the UE_A10 transmits identification information corresponding to the identification information received from the core network_A90 to the core network_B190 during the next procedure. May be sent. For example, UE_A10 may transmit the 62nd identification information corresponding to the 71st identification information to the core network_B190 during the following procedure, or the 11th identification information, and / or the 16th identification information. The 63rd identification information corresponding to the identification information may be transmitted. Further, UE_A10 may transmit the sixteenth identification information corresponding to the eighteenth identification information and / or the forty-sixth identification information to the core network_B190 in the following procedure, The identification information and / or the sixty-fifth identification information corresponding to the forty-fifth identification information may be transmitted. Further, UE_A10 may transmit the 68th identification information corresponding to the 76th identification information to core network_B190 during the following procedure.

[1.4.2.2. PDU session establishment procedure description]
The PDU session establishment procedure in the second reconnection procedure may be the same as the PDU session establishment procedure example described in section 1.4.1.3. Therefore, detailed description here is omitted. In addition, among the 61st to 68th identification information, whether to include at least one or more identification information in the PDU session establishment request message, UE_A10, in the PDN disconnection procedure, among the 71st to 76th identification information, The determination may be based on receiving at least one piece of identification information. In other words, UE_A10, in the PDN disconnection procedure, based on the reception of at least one of the identification information of the 71st to 76th, at least one of the 61st to 68th identification information of the PDU session It may be included in the establishment request message.

[2. Modification]
The program that operates on the device according to the present invention may be a program that controls a Central Processing Unit (CPU) and the like to cause a computer to function so as to realize the functions of the embodiment according to the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a random access memory (RAM), a nonvolatile memory such as a flash memory, a hard disk drive (HDD), or another storage device system.

  A program for realizing the functions of the embodiment according to the present invention may be recorded on a computer-readable recording medium. The program may be realized by causing a computer system to read and execute the program recorded on the recording medium. Here, the “computer system” is a computer system built in the device, and includes an operating system and hardware such as peripheral devices. Further, the “computer-readable recording medium” refers to 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 computer-readable recording medium. Is also good.

  Further, each functional block or various features of the device used in the above-described embodiment may be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein can be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other Logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. A general purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The above-mentioned electric circuit may be constituted by a digital circuit or an analog circuit. In addition, in the case where a technology for forming an integrated circuit that substitutes for a current integrated circuit appears due to the progress of semiconductor technology, one or more aspects of the present invention can use a new integrated circuit based on the technology.

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

  As described above, the embodiments of the present invention have been described in detail with reference to the drawings. However, the specific configuration is not limited to the embodiments, and may include a design change or the like without departing from the gist of the present invention. The present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included in the technical scope of the present invention. It is. Moreover, it is the element described in each said embodiment, and the structure which substituted the element which has the same effect is also contained.

1 Mobile communication systems
5 PDN_A
10 UE_A
20 UTRAN_A
22 NB_A
24 RNC_A
25 GERAN_A
26 BSS_A
30 PGW_A
35 SGW_A
40 MME_A
42 SGSN_A
45 eNB_A
46 SCEF_A
50 HSS_A
55 AAA_A
60 PCRF_A
65 ePDG_A
70 WLAN ANa
72 WLAN APa
74 TWAG_A
75 WLAN ANb
76 WLAN APb
80 E-UTRAN_A
90 core network_A
120 NextGen RAN_A
122 NR node_A
125 WLAN ANc
126 WAG_A
130 UPGW_A
140 CPF_A
190 core network_B

Claims (24)

A terminal device,
The terminal device
Perform a detach procedure for the first core network,
After the detach procedure, perform an attach procedure to the second core network, a transmitting and receiving unit,
Based on the completion of the detach procedure, to change the connection destination from the first core network to the second core network, comprising a control unit,
The transmitting and receiving unit includes:
In the detach procedure, receiving a detach request message from the MME (Mobility Management Entity),
In the attach procedure, send an attach request message to the CPF (Control Plane Function),
The detach request message includes information indicating that a connection destination is changed,
The attach request message includes information indicating handover,
A terminal device characterized by the above-mentioned. The attach request message further includes information identifying the CPF, and / or a PDU session establishment request message,
2. The terminal device according to claim 1, wherein: The transmitting and receiving unit includes:
Before the detachment procedure, receiving a tracking area update acceptance message from the MME, performing a tracking area update procedure,
The tracking area update acceptance message includes information identifying the CPF,
3. The terminal device according to claim 2, wherein: The detach procedure is performed in a state where a session is established with the first core network,
The control unit, based on the completion of the attach procedure, switches the connection destination of the session to the second core network,
The PDU session establishment request message includes information indicating the information for identifying the session, and / or information for identifying the DN (Data Network) to which the session is connected,
3. The terminal device according to claim 2, wherein: The detach request message further includes information identifying the session,
5. The terminal device according to claim 4, wherein: The transmitting and receiving unit includes:
Before the detach procedure, receiving a default EPS bearer context activation request message from the MME, performing a PDN connection procedure,
The control unit establishes the session based on the completion of the PDN connection procedure,
The terminal device according to claim 4, wherein the default EPS bearer context activation request message includes information for identifying the DN. MME (Mobility Management Entity)
The MME is
A transmitting and receiving unit for performing a detachment procedure;
Based on the completion of the detach procedure, the connection destination of the terminal device, in order to change from the first core network to the second core network, disconnecting the connection with the terminal device, comprising a control unit,
The transmitting and receiving unit includes:
In the detach procedure, send a detach request message to the terminal device,
The detach request message includes information indicating that a connection destination of the terminal device is to be changed,
MME characterized by the following. The detach request message further includes information identifying a session to be reestablished by the terminal device,
The MME according to claim 7, characterized in that: The transmitting and receiving unit includes:
Before the detach procedure, send a default EPS bearer context activation request message to the terminal device, perform a PDN connection procedure,
The MME according to claim 8, wherein the default EPS bearer context activation request message includes information identifying a DN (Data Network) to which the session connects. The transmitting and receiving unit includes:
Before the detachment procedure, transmitting a tracking area update acceptance message to the terminal device, performing a tracking area update procedure,
The tracking area update acceptance message includes, in the detachment procedure, information for identifying a CPF (Control Plane Function) to which the terminal device is to be connected,
8. The MME according to claim 7, wherein: CPF (Control Plane Function)
The CPF is
A transmitter / receiver for performing an attach procedure;
Based on the completion of the attach procedure, the connection destination of the terminal device, to change from the first core network to the second core network, to connect with the terminal device, comprising a control unit,
The transmitting and receiving unit includes:
In the attach procedure, receiving an attach request message from the terminal device,
The attach request message includes information indicating handover,
CPF characterized by the following. The attach request message further includes a PDU session establishment request message,
The PDU session establishment request message includes information for identifying a session, and / or information for identifying a DN (Data Network) to which the session is connected,
12. The CPF according to claim 11, wherein: A communication control method for a terminal device,
Performing a detach procedure on the first core network;
Performing an attach procedure on the second core network after the detach procedure;
Changing the connection destination from the first core network to the second core network based on the completion of the detach procedure,
In the detach procedure, receiving a detach request message from the MME (Mobility Management Entity), further comprising,
In the attach procedure, further comprising a step of transmitting an attach request message to the CPF (Control Plane Function),
The detach request message includes information indicating that a connection destination is changed,
The attach request message includes information indicating handover,
A communication control method for a terminal device, comprising: The attach request message further includes information identifying the CPF, and / or a PDU session establishment request message,
14. The communication control method for a terminal device according to claim 13, wherein: Before the detachment procedure, receiving a tracking area update acceptance message from the MME, further comprising the step of performing a tracking area update procedure,
The tracking area update acceptance message includes information identifying the CPF,
15. The communication control method for a terminal device according to claim 14, wherein: The detach procedure is performed in a state where a session is established with the first core network,
Based on the completion of the attach procedure, switching the connection destination of the session to the second core network, further comprising:
The PDU session establishment request message includes information indicating the information for identifying the session, and / or information for identifying the DN (Data Network) to which the session is connected,
15. The communication control method for a terminal device according to claim 14, wherein: The detach request message further includes information identifying the session,
17. The communication control method for a terminal device according to claim 16, wherein: Performing a PDU session establishment procedure, prior to the detach procedure, receiving a default EPS bearer context activation request message from the MME;
Establishing the session based on completion of the PDU session establishment procedure, further comprising:
17. The communication control method for a terminal device according to claim 16, wherein the default EPS bearer context activation request message includes information for identifying the DN. A communication control method of MME (Mobility Management Entity),
Performing a detach procedure;
Based on the completion of the detach procedure, the connection destination of the terminal device, in order to change from the first core network to the second core network, disconnecting the connection with the terminal device, comprising:
In the detaching procedure, further comprising a step of transmitting a detach request message to the terminal device,
The detach request message includes information indicating that a connection destination is changed,
A communication control method for an MME, comprising: The detach request message further includes information identifying a session to be reestablished by the terminal device,
20. The communication control method for an MME according to claim 19, characterized in that: Performing a PDU session establishment procedure of transmitting a default EPS bearer context activation request message to the terminal device before the detach procedure, further comprising:
21. The MME communication control method according to claim 20, wherein the default EPS bearer context activation request message includes information for identifying a DN (Data Network) to which the session connects. Before the detachment procedure, transmitting a tracking area update acceptance message to the terminal device, further comprising the step of executing a tracking area update procedure,
The tracking area update acceptance message includes, in the detachment procedure, information for identifying a CPF (Control Plane Function) to which the terminal device is to be connected,
20. The communication control method for an MME according to claim 19, wherein: A communication control method of CPF (Control Plane Function),
Performing an attach procedure, a step,
Based on the completion of the attach procedure, the connection destination of the terminal device, to change from the first core network to the second core network, connect to the terminal device,
And
In the attach procedure, further comprising a step of receiving an attach request message from the terminal device,
The attach request message includes information indicating handover,
A communication control method for a CPF, comprising: The attach request message further includes a PDU session establishment request message,
The PDU session establishment request message includes information indicating a session, and / or information indicating information for identifying a DN to which the session is connected,
24. The communication control method of the CPF according to claim 23, wherein:

Images