JP2020036053A - Terminal device, network function unit, base station, communication system, and communication control method - Google Patents

Abstract

To provide a communication system that supports configurations of a variety of core networks and communication control means suitable for a terminal device.SOLUTION: Provided are a terminal device capable of connecting to a variety of core networks, device communication control means of a network capable of connecting to the terminal device, setting means of control information relating to communication of each device, and a communication control method for the network and the terminal device to optimally manage control information on the communication control means or the like for updating setting information relating to communication stored by each device.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a terminal device, a network function unit, a base station, a communication system, 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). The 3GPP specifies an Evolved Packet System (EPS) 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 technology and system architecture of 5G (5th Generation) mobile communication system, which is the next generation mobile communication system, and NextGen (Architecture and Security for Next Generation) System). NextGen extracts the technical challenges for connecting a wide variety of terminals to cellular networks and specifies solutions. For example, network slicing technology is being considered as a function that allows an operator to fine-tune the network in scenarios in various markets that require various requirements. Network slicing techniques are being considered for configuring one or more network slices in one PLMN. Further, each network slice is associated with a network slice type according to a requirement, a market, and a type of a terminal connected to the network slice.

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

  As described above, NextGen is studying a network slice technique for virtually dividing a core network. Further, in the network slice technology, one or a plurality of network slices are configured in a core network, and it is considered that each network slice is managed by being associated with at least one network slice type. Furthermore, it is considered that one network slice type can support connection to a plurality of PDNs or DNs.

  However, the means for establishing a connection to the optimal PDN and / or DN has not been clarified in the attach procedure and the PDU session establishment procedure.

  The present invention has been made in view of such circumstances, and an object of the present invention is to provide communication control means and the like for realizing management of each setting related to communication.

  The terminal device according to the present invention transmits an attach request message including the first identification information and the second identification information to the network function unit configured in the core network. Receiving an attach acceptance message including the identification information of 3, receiving unit, based on the third identification information, PDN (Packet Data Network) indicated by the third identification information via the core network and a session between the terminal device Establishing, a control unit, the transmission unit and the reception unit start transmission and reception of user data with the PDN using the session, wherein the first identification information is one or more PDNs requested by the terminal device The second identification information is information indicating a PDN requested by the terminal device with priority, and the first identification information and the second identification information are information indicating that the network function unit has a connection destination of the terminal device. Determine the PDN And the third identification information is information indicating a PDN to which the core network has permitted connection to the terminal device.

  In the present invention, a network function unit configured in a core network receives an attach request message including first identification information and second identification information from a terminal device, a receiving unit, and a first identification unit. Based on the information and the reception of the second identification information, determine the PDN (Packet Data Network) of the connection destination of the terminal device, establish a session with the gateway device of the determined PDN, a control unit, to the terminal device, Transmitting an attach acceptance message including the identification information of (3), wherein the first identification information is information indicating one or more PDNs requested by the terminal device, the second identification information Is information indicating the PDN requested by the terminal device with priority, and the third identification information is information indicating the PDN that the core network has permitted the terminal device to connect to.

  In the present invention, the base station apparatus receives the RRC message including the attach request message including the first identification information and the second identification information, a receiving unit, the first identification information and the second identification information A control unit, and a transmission / reception unit that transmits an attach request message to the network function unit, based on the first identification information, the first identification information is requested by the terminal device. It is information indicating one or a plurality of PDNs, and the second identification information is information indicating a PDN requested by the terminal device with priority.

  A communication control method for a terminal device according to the present invention, comprising: transmitting an attach request message including first identification information and second identification information to a network function unit configured in a core network; From, based on the step of receiving an attach acceptance message including the third identification information and the third identification information, a session between the terminal device and PDN (Packet Data Network) indicated by the third identification information via the core network Establishing, and starting the transmission and reception of user data with the PDN using the session, wherein the first identification information is information indicating one or more PDNs requested by the terminal device, the second The identification information is information indicating the PDN requested by the terminal device with priority, and the first identification information and the second identification information indicate the PDN to which the terminal device is connected by the network function unit. The third identification information used for the determination is information indicating a PDN to which the core network has permitted the terminal device to connect.

  In the present invention, the communication control method of the network function unit configured in the core network, from the terminal device, receiving an attach request message including the first identification information and the second identification information, the first, Determining the PDN (Packet Data Network) to which the terminal device is connected based on the identification information and the reception of the second identification information; establishing a session with the gateway device of the determined PDN; and Transmitting an attach acceptance message including third identification information, wherein the first identification information is information indicating one or more PDNs requested by the terminal device, and the second identification information Is information indicating the PDN requested by the terminal device with priority, and the third identification information is information indicating the PDN that the core network has permitted the terminal device to connect to.

  In the present invention, the communication control method of the base station device, from the terminal device, receiving the RRC message including the attach request message including the first identification information and the second identification information, receiving the first identification information, Determining a destination network function unit of the attach request message based on the second identification information, and transmitting the attach request message to the network function unit, wherein the first identification information is a terminal device. Is information indicating one or a plurality of PDNs requested, and the second identification information is information indicating a PDN requested by the terminal device with priority.

  According to the present invention, the terminal device and each device in the core network can manage identifiers and / or parameters required for communication. Further, each device can execute communication control based on the set identifier and / or parameter.

FIG. 2 is a diagram for describing an outline of a mobile communication system. FIG. 2 is a diagram for explaining an example of a configuration of a core network and an access network in a mobile communication system. FIG. 3 is a diagram for describing details of a mobile communication system. 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. 4 is a diagram for explaining a storage unit of the MME / CPF. FIG. 4 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. 4 is a diagram for explaining a storage unit of SCEF. It is a figure for explaining an initial procedure. FIG. 8 is a diagram for explaining a PDU session establishment procedure. It is a figure for explaining an attachment procedure. It is a figure for explaining a tracking area update procedure.

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

[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_B, a core network_B190, a PDN (Packet Data Network) _A5, and a PDN_B6. Here, UE_A10 may be any terminal device capable of wireless connection, and may be UE (User Equipment), ME (Mobile Equipment), MS (Mobile Station), or CIoT (Cellular Internet of Things) terminal (CIoT UE) or the like. . Further, the core network may be a core network_B190, and the access network may be an access network_B. Further, the core network may be a core network device. Alternatively, in the present embodiment, the core network device may be each device included in the core network_B190 and / or a device that executes some or all of the processes or functions of each device. Access network_B may be NextGen RAN_A120 and / or E-UTRAN_A80 and / or WLAN ANc125.

  Further, the core network_B190 includes NSI (Network Slice Instance) _A191 and NSI_B192. The core network B190 is not limited to this, and may be configured to include one or more NSIs.

  Here, an NSI (Network Slice Instance) in the present embodiment is an entity of a network slice (Network Slice) configured in the core network_B190 or one or more. That is, the NSI may be a network slice. Further, the NSI in the present embodiment may be configured by a virtual NF (Network Function: network function unit) 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 NFs (Network Functions).

  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.

  A UE is 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.

  Also, UE_A10 can be connected to an access network and / or a core network. Further, UE_A10 can be connected to PDN_A5 and / or PDN_B6 via an access network and / or a core network, and further transmits and receives user data to and from PDN_A5 and / or PDN_B6. Note that the user data may be data transmitted and received between UE_A10 and PDN_A5. Further, transmission and 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.

  Although PDN_A5 and PDN_B6 are described as having connectivity with core network_B190 here, other PDNs may have connectivity with core network_B190.

  Here, the PDU session or PDN connection (hereinafter, also referred to as PDN connection), UE_A10 and PDN_A5 and / or to provide a PDU connection service for transmitting and receiving user data between PDN_A5 and / or PDN_B6, UE_A10 and PDN_A5 and / or This is the connectivity established with PDN_B6. 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 an apparatus that connects the core network such as PGW (Packet Data Network Gateway) _A30, UPGW (User Plane Gateway) _A130, UPGW_B131, SCEF (Service Capability Exposure Function) _A46, and PDN_A5.

  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. Furthermore, the PDU session or PDN connection may be a session established between UE_A10 and the core network and / or PDN_A5 and / or PDN_B6, such as one or more bearers between each device in the mobile communication system 1. A logical communication path composed of a transfer path may be used. More specifically, the PDU session, UE_A10 may be a connection established between the core network_B190 and the external gateway, or UE_A10, or a connection established between the UPGW_A130 and / or UPGW_B131, A connection such as a PDN connection (Packet Data Network Connection) may be used.

  Note that the PDN connection may be a connectivity and / or connection between UE_A10 and PGW_A30 via eNB (evolved Node B) _A45 and / or SGW (Serving Gateway) _A35, or eNB_A45 and / or MME (Mobility Management Entity) _A40 and / or connectivity 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 the UE_A10 can execute transmission / reception of user data with a device such as an application server arranged in the PDN_A5 and / or PDN_B6 using a PDU session or a PDN connection. In other words, the PDU session or PDN connection can transfer user data transmitted and received between UE_A10 and a device such as an application server arranged in PDN_A5. Further, each device (UE_A10, device in the access network, and / or device in the core network) may manage one or more 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 identification information, access network identification information, DNN (Domain Network Name), service type, and network slice type 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. Further, the NSI identification information is information for identifying the NSI, and may be an NSI ID or a Slice Instance ID hereinafter.

  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 without using IP, and is data communication realized by transmission and reception of 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 having 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.

  Further, PDN_A5 and PDN_B6 may be DNs (Data Networks) that provide communication services to UE_A10. The DN may be configured as a packet data service network or may be configured for each service. Furthermore, PDN_A5 and PDN_B6 may include connected communication terminals. Therefore, connecting to PDN_A5 and / or PDN_B6 may be connecting to a communication terminal or server device arranged in PDN_A5 and / or PDN_B6. Further, transmitting / receiving user data to / from PDN_A5 and / or PDN_B6 may be transmitting / receiving user data to / from a communication terminal or server device arranged in PDN_A5 and / or PDN_B6. Note that PDN_A5 and / or PDN_B6 may be expressed as DN, or DN may be expressed as PDN_A5 and / or PDN_B6.

  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 may be E-UTRAN (Evolved Universal Terrestrial Radio Access Network) _A80 or NextGen RAN (Next Generation Radio Access Network) _A120, and the non-3GPP access network may be WLAN ANc125. Note that UE_A10 may connect to the access network to connect to the core network, or may connect 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 operator that operates and manages the mobile communication system 1, or a virtual mobile communication operator such as MVNO (Mobile Virtual Network Operator), MVNE (Mobile Virtual Network Enabler), or a virtual mobile communication operator. A core network for a mobile communication service provider may be used. The core network _B190 may be an EPC (Evolved Packet Core) constituting an EPS (Evolved Packet System) or an NGC (Next Generation (NextGen) Core) constituting an NGS (NextGen System (Next Generation System)). . Further, 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 a mobile communication service.

  Next, a configuration example of the core network_B190 will be described. An example of the configuration of the core network_B190 will be described. FIG. 2 shows an example of the configuration of the core network_B190. The core network_B190 in FIG. 2A 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 that is 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, and 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, the plurality of gateways may be a gateway that connects the core network_B190 and a single DN. The UPGW_A 130 may have connectivity with another NF, and may connect to each device via another NF. Note that UPGW_A130 may be SGW_A35 and / or PGW_A30.

  PGW_A30 is connected to PDN_A5, SGW_A35, and PCRF_A60, and is a relay device that transfers user data as a gateway between PDN_A5 and / or DN and core network_B190. 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_B190. Further, the plurality of gateways may be a gateway that connects the core network_B190 and a single DN.

  The U-Plane (User Plane) may be a communication path for transmitting and receiving user data, or may be configured by 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, and the E-UTRAN_A80, and is a relay device that transfers user data as a gateway between the core network_B190 and the 3GPP access network (E-UTRAN_A80, NextGen RAN_A120).

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

  Further, CPF_A140 is a device connected to UPGW_A130, E-UTRAN_A80, NextGen RAN_A120, WLAN ANc125, HSS_A50, and SCEF_A46. CPF_140 may be an NF that plays a role of mobility management such as UE_A10, may be an NF that plays a role of session management such as a PDU session, or may be an NF that manages one or a plurality of NSIs. Also, 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 NSIs. A common CPNF (Common CPNF (Control Plane Network Function)) shared between the devices 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 CPF_A140 may be MME_A40.

  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 via the access network, and performs access control. 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_B190, and 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.

  Further, when a plurality of MMEs are included in core network_B190, 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 control information related to mobility management and 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, although the example in which the MME_A40 is configured to be included in the core network_B190 has been described, the MME_A40 may be a management device configured in one or a plurality of core networks or a DCN or an NSI, or may include one or a plurality of core networks or 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.

  Further, the MME_A40 may be a relay device that transfers user data as a gateway between the core network_B190 and the access network. Note that the user data transmitted and received by the MME_A40 acting as a gateway may be small data.

  Furthermore, the 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_B190, 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 among a plurality of NSIs.

  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. The NF may be a functional device for implementing a single function or a functional device for implementing 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.

  SCEF_A46 is a relay device that is connected to PDN_A5 and CPF_A140 or MME_A40 and HSS_A50, and that transfers user data as a gateway that connects PDN_A5 and / or DN and core network_B190. 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. Also, a plurality of such gateways may be arranged in the core network_B190. Further, a plurality of gateways for connecting the core network_B190 with a single PDN_A5 and / or DN may be provided. Note that SCEF_A46 may be configured outside the core network or may be configured inside the core network.

  HSS_A50 is connected to MME_A40 and SCEF_A46, and is a management node that manages subscriber information. The subscriber information of the HSS_A50 is referred to when, for example, controlling access to the 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. Further, HSS_A50 may be a Subscriber Repsitory that stores subscriber information.

  PCRF_A60 is connected to UPGW_A130 or PGW_A30 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.

  Further, 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.

  Further, 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 configured with E-UTRA and / or NextGen RA. 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.

  The WLAN ANc125 is a wireless LAN access network, and includes the 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.

  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 or 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 the WAG_A126. Good.

  Further, details of the mobile communication system and NSI_A191 and NSI_B192 in the present embodiment will be described with reference to FIG. As shown in the figure, in the present embodiment, UPG_A130, UPGW_B131, and CPF_A140 are configured in NSI_A191.

  Also, in the present embodiment, UPG_C132 and CPF_B141 are configured in NSI_B192. Further, CPF_A140 and CPF_B141 may have connectivity with HSS_A50. That is, one or more NSIs may share one HSS.

  UPGW_A130 is a GW device between PDN_A5 and NSI_A191 and core network_B190, and UPGW_B131 is a GW device between PDN_B6 and NSI_A191 and core network_B190. Further, UPGW_C132 is a GW device between PDN_C7 and NSI_B192 and core network_B190, and in this embodiment, UE_A10 has direct connectivity with UPGW_A130 and / or UPGW_B131 and / or UPGW_C132, but core network_B190 has In addition to UPGW_A130, UPGW_B131, UPGW_C132 may be provided with a UPF (User-Plane Function: UP function) with a user data transmission and reception function, in which case UE_A10 1 or UPF included in these core network _B190 A plurality may be connected to UPGW_A130 and / or UPGW_B131 and / or UPGW_C132.

[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 in UE_A10, MME_A40 / CPF_A140, and SGW_A35 may be equal to the IMSI stored in 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 (registered state) in which UE_A10 is registered in the network and / or an EMM-DEREGISTERD state (non-registered state) in which UE_A10 is not registered in the network. 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 the state in which the UE_A10 is registered in the EPC and the state in which the UE_A10 is registered in the NGC.

  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.

  SGW F-TEID is information for identifying SGW_A35. The SGW F-TEID may include the IP address of the SGW_A35, may include the TEID of the 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 selectable by the APN. Further, one gateway may be selected from among 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 of the establishment destination of the PDU session, DNN (Domain Network Name).

  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. Further, 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, the IP Address is the 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 IP Address element may not be included.

  SCEF ID is the IP address of SCEF_A46 used in the PDU session. Default Bearer is information acquired 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. Further, 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 / receives the user data identified by the TFT using an RB (Radio Bearer) associated with the TFT. The TFT may be one that associates 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, the 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 WAG_A126.

  Hereinafter, the configuration of each device will be described. In addition, 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 drawing, UE_A10 includes a transmission / reception unit_A420, a control unit_A400, and a storage unit_A440. The transmitting / receiving 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 a base station and / or an access point in the access network. Further, the transmission / reception unit_A420 is a transmission / reception function unit that allows the UE_A10 to transmit / receive user data and / or control information from a base station and / or an access point in an access network.

  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, 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_B190 and a UE context used when connecting to the core network_B190. Furthermore, the UE context used for connecting to the core network_B190 and the UE context used for connecting to the core network_B190 may be stored together or separately.

  First, FIG. 5B shows information elements included in the 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 the 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, 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 the eNB_A45, the NR node_A122, and the WAG_A126 to connect 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 and 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. Configuration of MME / CPF]
Hereinafter, the configurations of the MME_A40 and the CPF_A140 will be described. Hereinafter, each device means MME_A40 and CPF_A140. FIG. 7 shows the device configuration of each device. As shown in the drawing, each device includes 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 each device. 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 functional 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 SCEF_A46, and / or HSS_A50, and / or 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 programs, 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 the 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. 9 (c) 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. 9D 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 element 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 the device configuration of the SGW_A35. As shown in the figure, 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 programs, 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 the device configuration of PGW_A30, UPGW_A130, UPGW_B131, and UPGW_C132. Hereinafter, each device means PGW_A30, UPGW_A130, UPGW_B131, and UPGW_C132. As shown in the figure, each device 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 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 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. In addition, the network connection unit_D1020, the PGW_A30 transmits and receives user data and / or control information from the SGW_A35, and / or PCRF_A60, and / or ePDG_A65, and / or AAA_A55, and / or TWAG_A74, and / or PDN_A5. 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 CPF_A140, and / or the PDN_A5. The network connection unit_D1020 is a functional unit for the UPGW_B131 to connect to the PCRF_A60 and / or the CPF_A140 and / or the PDN_B6. The network connection unit_D1020 is a functional unit for the UPGW_C132 to connect to the PCRF_A60 and / or the CPF_A140 and / or the PDN_B6. In addition, the network connection unit_D1020, the PGW_A30 transmits and receives user data and / or control information from the SGW_A35, and / or PCRF_A60, and / or ePDG_A65, and / or AAA_A55, and / or TWAG_A74, and / or PDN_A5. 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 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 stored for each UE, those stored for each APN, those stored for each PDU session or PDN connection, and those 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. Note that 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 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.

  Control unit_D1000 is a functional unit for controlling 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_B190. 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 in which 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]
Next, before describing the detailed procedure of the initial procedure in the present embodiment, terms specific to the present embodiment and main identification information used in each procedure will be described in advance to avoid redundant description.

  In the present embodiment, the network refers to the access network and / or the core network_B190 and / or the PDN_A5. Further, the network may indicate any device included in the access network and / or the core network_B190 and / or the PDN_A5. That is, that the network performs transmission / reception and / or procedure of the message means that a device in the network performs transmission / reception and / or procedure of the message.

  The DNN (Domain Network Name) in the present embodiment is information for identifying a DN or a PDN. The DNN may be associated with a service type. Further, the DNN may be an APN.

  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. Hereinafter, the tracking area may be a TA (Tracking Area).

  The TA (Tracking Area) list in the present embodiment may be a group of information indicating a list of tracking areas in which the network can establish a PDU session with UE_A10.

  The network slice type in the present embodiment is a type of network slice assigned to one or a plurality of NSIs, which is classified based on a requirement condition, a market, and a type of a UE connected to the NSI. One or more NSIs or network slices are associated with one network slice type. The UE and each functional unit may store the network slice type and the service in association with each other. The NSI type may be a network slice type.

  In other words, the network slice type may be information for resolving one or more network slice instances associated with the network slice type. Note that the plurality of network slice instances associated with one network slice type may be network slices included in a single PLMN. The network slice included in the PLMN may be a network slice associated with a single PLMN, or a network slice instance provided by a communication provider that manages or operates the PLMN. The multi-parallel DN connection capability in the present embodiment indicates that it has a function of simultaneously connecting to a plurality of DNs in the PLMN. A UE having multi-parallel DN connection capability may connect to a plurality of DNs by establishing a PDU session for each DN. Specifically, the UE performs an attach procedure and / or a PDU session establishment procedure for each connected DN to establish connectivity to a plurality of DNs. Such a connection may be a multi-parallel PDU session or a multi-parallel PDN connection.

  In other words, multi-parallel DN connection capability is, for a single network slice type that UE_A10 requests the establishment of connectivity, is capability information indicating that connectivity to one or more DNs can be established. May be. Note that connectivity to a plurality of DNs may be established by different PDU sessions for each DN. That is, for a single network slice type, the UE and the network may establish multiple PDU sessions. Further, an IP address or an IPv6 network prefix may be assigned for each PDU session by a GW serving as an IP anchor point connecting to a different DN.

  Also, when there are a plurality of network slice instances associated with a single network slice type, the connectivity for a plurality of DNs described above may be associated with a single network slice instance, May be different. Note that associating connectivity with a network instance may mean that connectivity is established via a communication path via one or a plurality of gateways configured in association with a network slice instance. In other words, associating connectivity with a network instance may indicate that connectivity is established via the network instance.

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

  The first identification information in the present embodiment is information for identifying a network slice type and / or a service type. Further, the first identification information may be NSSAI (Network Slice selection Assistance Information).

  The second identification information in the present embodiment is an information group indicating a list of PDNs or DNs. The second identification information may include information for identifying one or a plurality of PDNs or DNs. For example, the second identification information may include one or more DNNs or APNs (Access Point Names).

  Note that the second identification information may be managed for each network slice type. Therefore, if UE_A10 can establish connectivity to a plurality of network slice types, it may have a DNN list that can establish connectivity for each network slice type, and each DNN list has a different DNN It may be composed of groups. In other words, the second identification information may be information managed in association with the first identification information.

  In the present embodiment, the third identification information is identification information indicating a PDN. The third identification information may be information indicating any one of one or a plurality of PDNs indicated by the second identification information. Further, the third identification information may be a DNN or an APN. In other words, the third identification information may be information indicating a DNN or APN requested by the UE_A10 to preferentially connect, among one or a plurality of DNNs or APNs indicated by the second identification information.

  The fourth identification information in the present embodiment is identification information indicating that the terminal has multi-home DN connection capability. Further, the fourth identification information may be UE capability information. Further, the fourth identification information may be information obtained by combining the fourth identification information with the fifth identification information. In this case, the fourth identification information may be identification information having both meanings of the fourth identification information and the fifth identification information.

  The fifth identification information in the present embodiment is identification information indicating that the terminal has multi-parallel DN connection capability. Further, the fifth identification information may be UE capability information. Further, the fifth identification information may be information obtained by combining the fourth identification information with the fifth identification information. In this case, the fourth identification information may be identification information having both meanings of the fourth identification information and the fifth identification information.

  In the present embodiment, the sixth identification information may be identification information indicating a request for connection to a new DN. Alternatively, the sixth identification information may be information indicating that a PDU session or a PDN connection has already been established in the same PLMN. The sixth identification information may be information indicating an already established PDU session. Furthermore, the sixth identification information may be an identification information group configured by information indicating one or more PDU sessions, or may indicate one or more PDU sessions by the sixth identification information. Good.

  In other words, the sixth identification information may be information indicating that the multi-home DN connection or the multi-parallel DN connection is requested to request an additional connection to a new DN. The sixth identification information may be identification information for identifying a PDU session already established for a multihome DN connection or a multi-parallel DN connection. Alternatively, the sixth identification information may be information identifying a network slice type or a network slice type associated with a multihome DN connection or a multi-parallel DN connection already established.

  Therefore, if the sixth identification information is not included in the attach request message or the PDU session establishment request message, the network shall not have any DN connected for multi-home DN connection or multi-parallel DN connection. , The network may recognize that a new connection is required for any one or more of the DNs allowed for multi-homed or multi-parallel DN connections.

  That is, by not including the sixth identification information in the attach request message or the PDU session establishment request message, the network has never been connected to a multi-home DN connection or a multi-parallel DN connection, and UE_A10 May be required to newly connect to one or a plurality of DNs permitted for multi-home DN connection or multi-parallel DN connection.

  In other words, if the sixth identification information is included in the attach request message or the PDU session establishment request message, the network is already connected to one or more DNs for the multi-home DN connection or the multi-parallel DN connection. And the network may recognize that it is required to make further connections to either one or more DNs allowed for multi-homed DN connections or multi-parallel DN connections.

  In other words, by including the sixth identification information in the attach request message or the PDU session establishment request message, UE_A10 has already connected to the network one or more DNs for multi-home DN connection or multi-parallel DN connection. In a given situation, it may be required to make further connections to either one or more DNs allowed for multi-homed DN connections or multi-parallel DN connections.

  In the present embodiment, the tenth identification information is identification information indicating a network slice type permitted to be established. The tenth identification information may be an information group including identification information indicating a plurality of network slice types. Further, the tenth identification information may be information indicating that the request from the UE has been permitted.

  In other words, the tenth identification information may be information indicating that UE_A10 has connected to a network slice instance corresponding to the network slice type requesting connection, and / or has permitted connection.

  In the present embodiment, the eleventh identification information is identification information indicating a DN to which the UE connects by a PDU session permitted to be established. The eleventh identification information may be a DNN or an APN. Further, the eleventh identification information may be identification information indicating a plurality of DNs, or may be a set of identification information indicating a plurality of DNs. That is, the eleventh identification information may be composed of a plurality of DNNs and / or APNs. Further, the eleventh identification information may be information indicating that the request from the UE has been permitted.

  For example, in the DNN list indicated by the second identification information transmitted by the UE_A10, the information may be information indicating a DN for which connectivity has been established and / or a connection has been permitted. In other words, the information may indicate the DN for which the connection has been established and / or the connection has been permitted for the network slice type for which UE_A10 requires the connection. Therefore, the eleventh identification information may be information managed in association with the network slice type.

  In the present embodiment, the twelfth identification information is a list of network slice types. The twelfth identification information is an identification information group indicating a list of NSI types that allow the network to connect to the UE. In other words, the twelfth identification information is an identification information group including identification information indicating a network slice type to which the UE can connect. The twelfth identification information may be constituted by identification information indicating one or a plurality of NSI types.

  In the present embodiment, the thirteenth identification information is identification information for identifying a DN for which the network permits the UE to connect. The network may allow the UE to connect to a plurality of DNs, and the thirteenth identification may be constituted by one or more DNNs. Here, among the DNs permitted to connect, the connectable DN may change according to the position of UE_A10. In other words, the connectable DN may be managed according to the position of the tracking area or the like. In this way, the thirteenth identification information may be identification information including a list of DNs permitted to connect and a list of connectable DNs. Note that the thirteenth identification information may be information associated with a network slice type. Therefore, when the UE_A10 establishes connectivity to a plurality of network slice types, the UE_A10 manages a list of DNs permitted to be connected and a list of connectable DNs in association with each network slice, and notifies the UE_A10. May be.

  In the present embodiment, the fourteenth identification information is identification information indicating a multi-home DN connection capability of the network. Further, the fourteenth identification information may be NW capability information.

  In the present embodiment, the fifteenth identification information is information indicating permission for multihome DN connection. Alternatively, the fifteenth identification information may be information indicating that multi-DN connection is not permitted.

  Note that the fourteenth identification information and the fifteenth identification information may be single identification information including the meaning of each identification information. Therefore, in the present embodiment, when it is described that the fourteenth identification information and the fifteenth identification information are transmitted or included in the control message, the two identification information are transmitted as a single identification information having their respective meanings. Or included in a control message.

  In the present embodiment, the sixteenth identification information is information indicating that the UE is located in an area where the network restricts multi-home DN connection. Further, the sixteenth identification information may be information indicating an area where the network restricts multi-home DN connection.

  In the present embodiment, the seventeenth identification information is information indicating that the UE is located in an area where the network permits multihomed DN connection. Further, the seventeenth identification information may be information indicating an area where the network permits a multihome DN connection.

  The eighteenth identification information in the present embodiment is identification information indicating the multi-parallel DN connection capability of the network. Further, the fourteenth identification information may be NW capability information.

  The nineteenth identification information in the present embodiment is information indicating permission for multi-parallel DN connection. Alternatively, the nineteenth identification information may be information indicating that multi-parallel DN connection is not permitted. The nineteenth identification information may be eighteenth identification information.

  Note that the eighteenth identification information and the nineteenth identification information may be single identification information including the meaning of each identification information. Therefore, in the present embodiment, when it is described that the eighteenth identification information and the nineteenth identification information are transmitted or included in the control message, the two identification information are transmitted as single identification information having their respective meanings. Or included in a control message.

  In the present embodiment, the twentieth identification information is information indicating that the UE is located in an area where the network restricts multi-parallel DN connection. Further, the twentieth identification information may be information indicating an area where the network restricts multiple parallel DN connections.

  In the present embodiment, the 21st identification information is information indicating that the UE is located in an area where the network permits multi-parallel DN connection. Further, the twenty-first identification information may be information indicating an area where the network permits a multi-parallel DN connection.

  In the present embodiment, the 22nd identification information may be information indicating that session switching has occurred. The 22nd identification information may be an IP address updated by session switching. Further, the twenty-second identification information may be associated with the eleventh identification information.

  In the present embodiment, the thirtieth identification information may be information indicating a reason for rejecting the request of UE_A10. The thirtieth identification information may be a reject cause value. Further, the thirtieth identification information may be information indicating that the network does not support connection to the NSI type and / or PDN requested by UE_A10. Alternatively, the thirtieth identification information may be information indicating that the user is in an area that cannot be connected to the NSI specified by UE_A10.

  Next, an initial procedure in the present embodiment will be described with reference to FIG. In this embodiment, each device executes an initial procedure, so that UE_A10 establishes a PDU session via core network_B190. Hereinafter, this procedure refers to an initial procedure, and each procedure includes an attach procedure to PDN_A5, a PDU session establishment procedure to PDN_A5, and a tracking area update procedure to PDN_A5. Details of each procedure will be described later.

  In this procedure, each device first executes an attach procedure to PDN_A5 (S1400), and transitions to a state in which UE_A10 is connected to the network. Next, each device executes a PDU session establishment procedure for PDN_A5 (S1402) to establish a session for PDN_A5.

  Furthermore, when UE_A10 additionally requests establishment of a PDU session to PDN_B6, each device may execute an attach procedure to PDN_B6, and transition to a state where UE_A10 is connected to a network. Next, each device may execute a PDU session establishment procedure for PDN_B6 to establish a session for PDN_B6. The procedure for attaching to PDN_B6 and the procedure for establishing a PDU session to PDN_B6 can be explained by using UPGW_B131 instead of the procedure for attaching to PDN_A5 and the procedure for establishing a PDU session to PDN_A5.

  Further, after the PDU session to PDN_A5 is established, a tracking area update procedure to PDN_A5 (S1408) may be further executed. Similarly, after establishing a PDU session to PDN_B6, a tracking area update procedure to PDN_B6 may be executed.

  Hereinafter, the attach procedure refers to an attach procedure to PDN_A5, the PDU session establishment procedure refers to a PDU session establishment procedure to PDN_A5, and the tracking area update procedure refers to a tracking area update procedure to PDN_A5.

  Each device may exchange various capability information and / or various request information of each device in the attach procedure and / or the PDU session establishment procedure and / or the tracking area update procedure.

  When each device exchanges various information and / or negotiates various requests by the attach procedure, it is not necessary to exchange various information and / or negotiate various requests by the PDU session establishment procedure. Conversely, when each device does not perform exchange of various information and / or negotiation of various requests in the attach procedure, it may perform exchange of various information and / or negotiation of various requests in the PDU session establishment procedure. . Not limited to this, even if each device exchanges various information and / or negotiates various requests in the attach procedure, even if it exchanges various information and / or negotiates various requests in the PDU session establishment procedure Good.

  For example, in the attach procedure to PDN_A5, and in the PDU session establishment procedure to PDN_A5, UE_A10 may transmit one or more pieces of identification information among the first to sixth pieces of identification information to the core network_B190. The core network_B190 receives at least one of the first to sixth identification information from UE_A10, and further transmits at least one of the tenth to twenty-first identification information to UE_A10. You may.

  Also, UE_A10 may transmit one or more pieces of identification information among the first to sixth pieces of identification information to core network_B190 by an attach procedure, and may not transmit it by a PDU session establishment procedure. Similarly, the core network_B190 may transmit one or more pieces of identification information among the tenth to twenty-first identification information to the UE_A10 in the attach procedure, and may not transmit it in the PDU session establishment procedure.

  Conversely, for each device, UE_A10 may transmit to the core network_B190 in the PDU session establishment procedure without transmitting at least one of the first to sixth identification information in the attach procedure. . Similarly, the core network_B190 may transmit one or more pieces of identification information among the first to sixth pieces of identification information to the UE_A10 in the PDU session establishment procedure without transmitting the identification information in the attach procedure.

  Also, UE_A10 may transmit, in the PDU session establishment procedure, the core network_B190, of the first to sixth identification information, which has not been transmitted in the attach procedure. Similarly, core network_B190 may transmit, to UE_A10, identification information that has not been transmitted in the attach procedure among the tenth to twenty-first identification information in the PDU session establishment procedure.

  Further, each device, when managing these identification information in association with UE_A10, may be transmitted and received during the attach procedure, when managing in association with the PDU session and / or EPS bearer, during the PDU session establishment procedure May be sent and received.

  In addition, each device may execute the PDU session establishment procedure in the attach procedure, or may execute the procedure after the attach procedure is completed. When the PDU session establishment procedure is executed in the attach procedure, each device may establish the PDU session based on the completion of the attach procedure.

  Next, each device executes a tracking area update procedure (S1408). Note that the tracking area update procedure may be executed at an arbitrary timing after the PDU session is established. In addition, each device may exchange various kinds of request information in the tracking area update procedure. For example, in the tracking area update procedure for PDN_A5, UE_A10 may transmit one or more pieces of identification information among the first to sixth pieces of identification information to core network_B190. Furthermore, the core network_B190 may transmit one or more pieces of identification information among the tenth to twenty-first 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. You may. Further, each device may transition to an appropriate state based on completion of this procedure.

[1.3.1. Overview of Attach Procedure]
First, the outline of the attach procedure will be described. In the following, the attach procedure refers to the attach procedure to PDN_A5. The attach procedure is a procedure for connecting UE_A10 to a network (access network and / or core network_B190, and / or NSI and / or PDN) led by UE_A10. UE_A10 can execute this procedure at an arbitrary timing such as when the terminal is powered on, as long as UE_A10 is not connected to core network_B190 and / or NSI_A191. In other words, UE_A10 may start this procedure at any timing as long as it is not registered in core network_B190 and / or NSI_A191 (EMM-DEREGISTERED). Also, each device may transition to the registration state (EMM-REGISTERED) based on the completion of the attach procedure.

  Alternatively, the attach procedure is performed at an arbitrary timing, even if the UE_A10 is registered in the core network_B190 and / or the NSI_A191, as long as the multi-home DN connection or the multi-parallel DN connection is permitted from the network. You may.

[1.3.2. PDU session establishment procedure example]
Next, an example of a PDU session establishment procedure will be described. Hereinafter, the PDU session establishment procedure refers to a PDU session establishment procedure for PDN_A5. Further below, this procedure refers to the PDU session 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 attach procedure is completed, or may execute the procedure in the attach procedure. Further, each device may start this procedure at an arbitrary timing after the attach procedure. 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.

[1.3.2.1. PDU session establishment procedure example]
An example of a procedure for executing the PDU session establishment procedure will be described with reference to FIG. In the following, a case will be described in which a PDU session establishment procedure to PDN_A5 is described. However, by using UGPW_A131 instead of UGW_A130, a PDU session establishment procedure to PDN_B6 can be described. Alternatively, by using CPF_B141 instead of CPF_A140 and UPGW_C132 instead of UPGW_A130, a PDU session establishment procedure to PDN_C7 can be described. Hereinafter, each step of this procedure will be described. First, UE_A10 transmits a PDU Session Establishment Request message (PDU Session Establishment Request) to CPF_A140 via NR node_A122 (S1500), and starts a PDU session establishment procedure. When the PDU session is a PDN connection, the PDU session establishment request message may be a PDN connectivity request message. The PDU session establishment request message is not limited to this, and may be any message that requests the establishment of a PDU session.

  Specifically, UE_A10 transmits an RRC (Radio Resource Control) message including a NAS (Non-Access-Stratum) message including a PDU session establishment request message to the NR node_A122, and transmits a NAS message including a PDU session establishment request message. The NR node_A 122 that has received the RRC message including the PDU selects the CPF_A 140 as the NF or the shared CP function of the routing destination of the NAS message including the PDU session establishment request message, and transmits the NAS message including the PDU session establishment request message to the CPF_A 140.

  Here, the NR node_A 122 may select a routing destination NF or a shared CP function based on the first identification information and / or the second identification information and / or the third identification included in the RRC message. For example, the NR nod_A 122 may select an NSI that supports the network slice type or the service type indicated by the received first identification information, and may select an NF or a shared CP function included in the NSI. Further / or, NR nod_A122, from the PDN list indicated by the received second identification information, select a PDN to connect, select the NF or shared CP function included in the NSI supporting the connection to the selected PDN Is also good. Further / or NR nod_A122 may select an NF or a shared CP function included in the NSI that supports connection to the PDN indicated by the received second identification information. In addition, the NF or the shared CP function may be selected according to the operator policy or the network policy without depending on the NR node_A122. Also, the NR node_A 122 may select an appropriate NF or CP function in consideration of the plurality of pieces of information.

  Specifically, for example, if the NSI belonging to the network slice type indicated by the first identification information is NSI_A191, the NR node_A122 selects CPF_A140 as the routing destination NF or shared CP function based on the first identification information. You may. Or, if the PDN indicated by the third identification information is PDN_C7, the NR node_A122 is based on the third identification information, the NSI connected to the PDN_C7 NSI_B192 included CPF_B141 included in the routing destination NF or shared CP function May be selected.

  Further, even when the PDN indicated by the third identification information is PDN_C7, the NR node_A122 may select the CPF_A140 included in the NSI_A191 as the routing destination NF or the shared CP function based on the operator policy.

  Note that the selection of the NF or the shared CP function of the routing destination may be performed not by the NR node_A 122 but by a functional unit adjacent to or collocated with the NR node_A 122. Specifically, for example, the NR node_A122 and / or the NSSF (Network Slice Selection Function) adjacent to the access network may select the NF or the shared CP function of the routing destination.

  Here, UE_A10 transmits at least one of the first to sixth identification information to the NAS message including the PDU session establishment request message and / or the RRC message including the NAS message including the PDU session establishment request message. The request of UE_A10 may be indicated by including the identification information.

  Each device may indicate the network slice type and / or service type requested by UE_A10 by transmitting and receiving the first identification information. Alternatively, each device may transmit and receive the first identification information to indicate that UE_A10 requests a connection that supports a specific network slice type and / or service type. Also, each device may indicate that UE_A10 does not request connection to a specific network slice by leaving the first identification information empty.

  Furthermore, each device may transmit and receive the second identification information to indicate the PDN for which UE_A10 requests connection. Further, the second identification information may be a list of DNNs, and may be information indicating that connection to at least one of the DNNs is requested.

  By transmitting and receiving the third identification information, each device may indicate the desired DNN by giving priority to the connection by the UE_A10. Alternatively, each device transmits and receives the third identification information, so that UE_A10 prioritizes connection to at least one of one or more DNs indicated by the DNN list indicated in the second identification information. You may indicate that you are requesting Furthermore, each device may indicate that UE_A10 does not give priority to the connection of a specific PDN by emptying the third identification information.

  Further, each device may transmit and receive the fourth identification information to indicate that UE_A10 has multi-home DN connection capability (Capability). Furthermore, each device may indicate that UE_A10 requests to establish a PDU session as a multi-home DN connection by transmitting and receiving the fourth identification information.

  Further, each device may transmit and receive the fifth identification information to indicate that UE_A10 has multi-parallel DN connection capability (Capability). Furthermore, each device may indicate that UE_A10 requests to establish a PDU session as a multi-parallel DN connection by transmitting and receiving the fifth identification information.

  In addition, each device may transmit and receive the sixth identification information to indicate that UE_A10 requests connectivity to a new PDN. Each device may request the execution of the PDU session establishment request procedure and / or the attach procedure by transmitting and receiving the sixth identification information even when UE_A10 is registered in core network_B190.

  CPF_A140 receives the PDU session establishment request message, and performs a first condition determination. The first condition determination is for the CPF_A140 to determine whether to accept the request of UE_A10. In the first condition determination, the CPF_A140 determines whether the first condition is true or false. CPF_A140 starts the procedure of (A) in this procedure if the first condition is true, and starts the procedure of (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. CPF_A140 selects the PDN and / or UPGW_A130 to be connected based on the received first identification information and / or second identification information and / or third identification information, and performs the procedure (C) in this procedure. Execute and start the procedure of (A) in this procedure. For example, when CPF_A140 receives the third identification information, CPF_A140 may select an UPGW that is a GW device to the PDN indicated by the third identification information. However, CPF_A140 may select the UPGW and PDN according to the location information of the UE or the network policy without receiving the third identification information. Specifically, even when the second identification information indicating PDN_A5 is received, the UPGW_B131 connected to PDN_B6 may be selected based on the network policy.

  Further, each step of the procedure (C) in this procedure will be described. The CPF_A 140 transmits a session creation request message to the selected UPGW_A 130 or the UPGW_A 130 associated with the selected PDN, and starts the procedure (C) in this procedure (S1502).

  Here, CPF_A140 may include at least one or more pieces of identification information among the first to sixth pieces of identification information in the session creation request message, or may include information indicating whether or not 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 third condition determination. Note that the third condition determination is for the UPGW_A130 to determine whether to accept 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 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 third 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 third condition determination.

  Here, the UPGW_A130 may include at least one or more of the first to sixth 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.

  In addition, the PCRF_A60 may include at least the result of the third condition 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 third condition determination. May be.

  When the PCRF_A60 has performed the third condition determination, the UPGW_A130 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 the UPGW_A130 may set the third condition to true, and when the request of the UE_A10 is rejected, the PCRF_A60 and the UPGW_A130 may set the third condition to false.

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

  If the third condition is false, UPGW_A130 transmits a session creation rejection message to CPF_A140 (S1508). Note that the session generation rejection message may be a session generation response message including a rejection cause (Reject cause).

  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.

  CPF_A140 transmits a PDU session establishment accept message to NR node_A122 based on the reception of the session creation response message (S1514). Note that, upon receiving 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 Connectivity Accept (PDN Connectivity Accept) message or a Activate default EPS bearer context request message. Further, the PDU session establishment acceptance message may be a response message to the PDU session establishment request message, and is not limited thereto, and may be a message that accepts the PDU session establishment request.

  NR node_A122 receives the PDU 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 PDU session establishment acceptance The message is transmitted (S1516). Note that the PDU session establishment acceptance message may be transmitted and received while being included in the RRC message.

  Here, the CPF_A140 may include at least one or a plurality of pieces of identification information among the tenth to twenty-first identification information in the PDU session establishment acceptance message, may include an IP address, and may include these identification information. By including the information, it may be indicated that the request of UE_A10 has been accepted.

  Each device may indicate the NSI type to which the PDU session established by this procedure connects by transmitting and receiving the tenth identification information. Further, each device may indicate the information for identifying the PDN to which the PDU session established by this procedure is connected by transmitting and receiving the eleventh identification information. Each device may transmit and receive the eleventh identification information to indicate that the request of UE_A10 has been permitted.

  Further, by transmitting and receiving the twelfth identification information, each device indicates, besides the NSI type to which the PDU session established in this procedure is connected, the NSI type to which UE_A10 is permitted to connect. Alternatively, each device indicates the NSI type to which UE_A10 can connect by transmitting and receiving the twelfth identification information. The NSI type indicated by the twelfth identification information may be one or more NSI types.

  Further, by transmitting and receiving the thirteenth identification information, each device indicates a PDN to which UE_A10 is permitted to connect, in addition to the PDN to which the PDU session established in this procedure is connected. Alternatively, each device may indicate the PDN to which UE_A10 can connect by transmitting and receiving the thirteenth identification information. The thirteenth identification information may be associated with the twelfth identification information. Further, a plurality of thirteenth identification information may be associated with one twelfth identification information.

  Further, each device may transmit and receive the fourteenth identification information to indicate that the network has multi-home DN connection capability in this procedure. Each device may transmit and receive the fourteenth identification information based on the transmission and reception of the fourth identification information.

  Further, each device may transmit and receive the fifteenth identification information to indicate that the multihome DN connection requested by UE_A10 has been permitted. Further, each device may transmit and receive the fifteenth identification information to indicate that the network supports multi-homed DN connection. The fifteenth identification information may be the fourteenth identification information.

  Alternatively, each device may indicate that multihome DN connection is not permitted by transmitting and receiving the fifteenth identification information. Further, each device may transmit and receive the fifteenth identification information to indicate that the network does not support multi-home DN connection.

  Furthermore, each device may transmit and receive the sixteenth identification information to indicate that UE_A10 is located in an area where the network restricts multi-home DN connection. That is, each device may transmit and receive the sixteenth identification information to indicate that UE_A10 is not located in an area where the network permits multihomed DN connection. And / or each device may indicate the area where multi-home DN connection is restricted by transmitting and receiving the 16th identification information. UE_A10 that has received the information indicating the area where the multihome DN connection is restricted may store this information. Further, when UE_A10 already stores an area in which the multihome DN connection is restricted by the network, the UE_A10 may update the area based on the reception of the sixteenth identification information.

  Further, each device may transmit and receive the seventeenth identification information to indicate that UE_A10 is located in an area where the network permits multihomed DN connection. And / or each device may indicate the area where the multi-home DN connection is permitted by transmitting and receiving the seventeenth identification information. UE_A10 that has received the information indicating the area where the multihome DN connection is permitted may store this information. Furthermore, when UE_A10 already stores an area where multihome DN connection is permitted by the network, the UE_A10 may update the area based on reception of the seventeenth identification information.

  Further, each device may transmit and receive the eighteenth identification information to indicate that the network has multi-parallel DN connection capability in this procedure. Each device may transmit and receive the eighteenth identification information based on the transmission and reception of the fifth identification information.

  Further, each device may transmit and receive the nineteenth identification information to indicate that the multi-parallel DN connection requested by UE_A10 has been permitted. Further, each device may transmit and receive the nineteenth identification information to indicate that the network supports multi-parallel DN connections. The nineteenth identification information may be eighteenth identification information.

  Alternatively, each device may transmit and receive the nineteenth identification information to indicate that the multi-parallel DN connection is not permitted. Further, each device may send and receive the nineteenth identification information to indicate that the network does not support multi-parallel DN connections.

  Furthermore, each device may transmit and receive the twentieth identification information to indicate that the UE_A10 is located in an area where the network restricts multi-parallel DN connection. That is, each device may transmit and receive the twentieth identification information to indicate that the UE_A10 is not located in an area where the network permits multi-parallel DN connection. And / or each device may indicate the area where the multi-parallel DN connection is restricted by transmitting and receiving the twentieth identification information. UE_A10 that has received the information indicating the area where the multi-parallel DN connection is restricted may store this information. Further, when UE_A10 already stores an area in which multihome DN connection is restricted by the network, the UE_A10 may update the area based on the reception of the twentieth identification information.

  Further, each device may transmit and receive the 21st identification information, thereby indicating that UE_A10 is located in an area where the network permits multi-parallel DN connection. And / or each device may indicate the area where multi-parallel DN connection is permitted by transmitting and receiving the 21st identification information. UE_A10 that has received the information indicating the area where the multi-parallel DN connection is permitted may store this information. Furthermore, when UE_A10 already stores an area in which multi-parallel DN connection is permitted by the network, the UE_A10 may update the area based on the reception of the 21st 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 NR node_A 122 (S1518). NR node_A122 receives the RRC message, and transmits a bearer setup message to CPF_A140 (S1520). Further, CPF_A140 receives the bearer setup message.

  When receiving the PDU session establishment acceptance message, UE_A10 transmits a PDU session establishment complete (PDU session establishment complete) message to CPF_A140 via NR node_A122 (S1522) (S1524). Further, CPF_A140 receives the PDU session establishment completion message, and performs the second condition determination. When the PDU session is a PDN connection, the PDU session establishment complete message may be a PDN Connectivity complete message or a Activate default EPS bearer context accept message. Further, the PDU session establishment completion message may be a response message to the PDU session establishment acceptance message, and is not limited thereto, and may be a message indicating that the PDU session establishment procedure is completed.

  The second condition determination is for the CPF_A140 to determine whether it is necessary to request the UPGW_A130 to change the bearer. If the second condition is true, the CPF_A140 starts the procedure (D) in this procedure. If the second condition determination is false, CPF_A140 does not execute the procedure (D) in this procedure. Hereinafter, each step of the procedure (D) in this procedure will be described. If the second condition is true, CPF_A140 transmits a bearer change request message to UPGW_A130 (S1526), 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 (S1528). Further, CPF_A140 receives the bearer change response message, and completes the procedure (D) of this procedure. In addition, each device is based on the transmission and reception of the PDU session establishment completion message when the second condition determination is false, and / or when the second condition determination is true, completes the procedure (D) in this procedure. Based on this procedure, complete the procedure of (A).

  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 (S1530), and starts the procedure of (B) in this procedure. Further, UE_A10 receives the PDU session establishment 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 PDU session establishment rejection message. The PDU session establishment rejection message may include information indicating an appropriate reason for rejection. When the PDU session is a PDN connection, the PDU session establishment rejection message may be a PDN connectivity rejection message. The PDU session establishment rejection message may be a response message to the PDU session establishment request message, and is not limited thereto, and may be a message that rejects the PDU session establishment request.

  Here, the information indicating the appropriate reason for refusal may be the thirtieth identification information. Specifically, by transmitting and receiving the 30th identification information, each device may indicate that it does not support connection to the NSI and / or PDN included in the NSI type requested by UE_A10, The information may indicate that connection to the NSI and / or PDN included in the NSI type requested by UE_A10 is not permitted.

  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 this procedure, or based on the completion of the procedure (B) in this 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 UE_A10 receives the tenth identification information and / or, UE_A10 determines that the connection to the requested PDN has been established, and starts transmitting and receiving user data between UE_A10 and PDN_A5 using the established PDU session. I do.

  Further, for example, when the UE_A10 receives the twelfth identification information and / or the thirteenth identification information, the UE_A10 stores the received twelfth identification information and / or the thirteenth identification information in the storage unit. If the same information has already been stored, the stored information is updated to the received information. Further, when the UE_A 10 performs the attach procedure and the PDU session establishment procedure, the requested NSI type and DNN may be selected from the stored twelfth identification information and / or thirteenth identification information.

  Further, for example, if UE_A10 receives the fourteenth identity, and / or UE_A10 receives the fifteenth identity, the fifteenth identity indicates that the network supports multi-homed DN connection If it is information, UE_A10 may continue to perform a procedure for adding a session to PDN_B6.

  Further, for example, when UE_A10 receives the sixteenth identification information, UE_A10 stores the received sixteenth identification information, and when UE_A10 moves from the area indicated by the sixteenth identification information, the attach procedure or the tracking area again. An update procedure may be performed.

  Furthermore, for example, when UE_A10 receives the seventeenth identification information, UE_A10 stores the received seventeenth identification information, and when UE_A10 moves from the area indicated by the seventeenth identification information, the attach procedure or the tracking area again. An update procedure may be performed.

  Further, for example, if UE_A10 receives the eighteenth identification information, and / or UE_A10 receives the nineteenth identification information, the nineteenth identification information indicates that the network supports multi-parallel DN connection. If it is information, UE_A10 may continue to perform an attach procedure to PDN_B6 and / or a PDU session establishment procedure.

  Furthermore, for example, when UE_A10 receives the 20th identification information, UE_A10 stores the received 20th identification information, and when UE_A10 moves out of the area indicated by the 20th identification information, the attach procedure or the tracking area again. An update procedure may be performed.

  Furthermore, for example, when UE_A10 receives the 21st identification information, UE_A10 stores the received 21st identification information, and when UE_A10 moves out of the area indicated by the 21st identification information, the attach procedure or the tracking area again. An update procedure may be performed.

  Further, the above-described first to third condition determinations may be executed based on identification information and / or subscriber information included in the PDU session establishment request message and / or operator policy. Further, based on the sixth identification information included in the PDU session establishment request message, the first condition determination and the third condition determination may be performed regardless of the registration state of the UE in the network. Also, 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 third 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 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 may be false when 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.3.3. Attach procedure example]
An example of a procedure for executing the attach procedure will be described with reference to FIG. Hereinafter, this procedure refers to the attach procedure, and refers to the attach procedure to PDN_A5. 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 (Attach request) message to CPF_A140 via NR node_A122 (S1600), and starts an attach procedure. UE_A10 may transmit the attach request message including the PDU session establishment request message described above, or may include the PDU session establishment request message to request that the PDU session establishment procedure be performed during the attach procedure. You may.

  Specifically, UE_A10 transmits an RRC message including an attach request message to the NR node_A122, and receives an RRC message including the attach request message.The NR node_A122 is a CPF_A140 as a routing destination NF or a shared CP function of the attach request message. And sends an attach request message to CPF_A140. Here, the NR node_A 122 may select a routing destination NF or a shared CP function based on the tenth identification information included in the RRC message. Also, the attach request message may be a NAS message. Here, the method of selecting the routing destination NF or shared CP function by the NR node_A 122 may be the same as the method during the PDU session establishment procedure.

  Note that the UE_A10 may transmit one or more attach request messages for each network slice requesting connection in one RRC message, and may transmit a plurality of attach request messages collectively as an attach request message. Alternatively, UE_A10 may include an attach request message in an RRC message for each NSI requesting a connection and transmit the message.

  Here, UE_A10 may include at least one of the first to sixth identification information in the attach request message and / or the RRC message, or by including these identification information, the UE_A10 A request may be indicated.

  Each device may indicate the network slice type and / or service type requested by UE_A10 by transmitting and receiving the first identification information. Alternatively, each device may transmit and receive the first identification information to indicate that UE_A10 requests a connection that supports a specific network slice type and / or service type. Also, each device may indicate that UE_A10 does not request connection to a specific network slice by leaving the first identification information empty.

  Furthermore, each device may transmit and receive the second identification information to indicate the PDN for which UE_A10 requests connection. Further, the second identification information may be a list of DNNs, and may be information indicating that connection to at least one of the DNNs is requested.

  By transmitting and receiving the third identification information, each device may indicate the desired DNN by giving priority to the connection by the UE_A10. Alternatively, each device transmits and receives the third identification information, so that UE_A10 prioritizes connection to at least one of one or more DNs indicated by the DNN list indicated in the second identification information. You may indicate that you are requesting Furthermore, each device may indicate that UE_A10 does not give priority to the connection of a specific PDN by emptying the third identification information.

  Further, each device may transmit and receive the fourth identification information to indicate that UE_A10 has multi-home DN connection capability (Capability). Furthermore, each device may indicate that UE_A10 requests to establish a PDU session as a multi-home DN connection by transmitting and receiving the fourth identification information.

  Further, each device may transmit and receive the fifth identification information to indicate that UE_A10 has multi-parallel DN connection capability (Capability). Furthermore, each device may indicate that UE_A10 requests to establish a PDU session as a multi-parallel DN connection by transmitting and receiving the fifth identification information.

  In addition, each device may transmit and receive the sixth identification information to indicate that UE_A10 requests connectivity to a new PDN. Each device may request the execution of the PDU session establishment request procedure and / or the attach procedure by transmitting and receiving the sixth identification information even when UE_A10 is registered in core network_B190.

  Note that the UE_A10 may transmit these identification information in a control message different from the attach request message.

  CPF_A140 receives the attach request message and / or a control message different from the attach request message, and executes the first condition determination. CPF_A140 starts the procedure (A) in this procedure when the first condition is true, and starts the procedure (B) in this procedure when the first condition is false.

  Hereinafter, each step of the procedure (A) in this procedure will be described. CPF_A140 executes the fourth condition determination, and starts the procedure (A) in this procedure. In the fourth condition determination, the CPF_A140 determines whether the fourth condition is true or false. If the fourth condition is true, the CPF_A140 selects the NSI and / or UPGW_A130 to be connected based on the received first identification information and / or second identification information and / or third identification information. Then, the procedure of (C) in the PDU session establishment procedure is executed, and when the fourth condition is false, these procedures are omitted (S1604).

  Specifically, CPF_A140 may select an NSI corresponding to the NSI type requested by UE_A10 based on the first identification information. Further, the CPF_A140 may select the UPGW_A130 to be connected from the selected NSI to the PDN indicated by the second identification information and the third identification information based on the second identification information and the third identification information. Alternatively, the CPF_A 140 may comprehensively determine the first to third identification information and select an appropriate NSI and UPGW_A 130.

  Further, the CPF_A 140 transmits an attach accept (Attach accept) message to the NR node_A 122 based on the completion of the procedure (C) in the PDN connection procedure, and / or receiving the attach request message and / or the session creation response message. (S1606). Note that, upon receiving 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 the attach acceptance message in an S1AP message (for example, Initial context setup request or Downlink NAS Transport) and transmit it to NR node_A122. Further, the attach accept message may be a NAS message.

  NR node_A122 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, 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 CPF_A140 may transmit the attach acknowledgment message including the PDU session establishment acknowledgment message described above, or may include the PDU session establishment acknowledgment message to perform the PDU session establishment procedure. May have been accepted.

  Here, the CPF_A140 may include at least one or more of the tenth to twenty-first identification information in the attach acceptance message and / or the S1AP message, or may include an IP address. By including the identification information, it may be indicated that the request of UE_A10 has been accepted. Further, the NR node_A122 may include one or more pieces of identification information among the tenth to twenty-first identification information in the RRC message, and by including these pieces of identification information, indicates that the request of UE_A10 has been accepted. You may.

  Each device may indicate the NSI type to which the NSI to which UE_A10 connects by this procedure belongs by transmitting and receiving the tenth identification information. Furthermore, each device may indicate information for identifying the connection destination PDN by transmitting and receiving the eleventh identification information. Each device may transmit and receive the eleventh identification information to indicate that the request of UE_A10 has been permitted.

  Further, by transmitting and receiving the twelfth identification information, each device indicates a list of NSI types to which UE_A10 is permitted to connect in addition to the NSI types to be connected in this procedure. Alternatively, each device indicates the NSI type to which UE_A10 can connect by transmitting and receiving the twelfth identification information. The NSI type indicated by the twelfth identification information may be constituted by one or more NSI types.

  Further, by transmitting and receiving the thirteenth identification information, each device indicates a PDN to which UE_A10 is permitted to connect in addition to the PDN connected in this procedure. Alternatively, each device may indicate the PDN to which UE_A10 can connect by transmitting and receiving the thirteenth identification information. The thirteenth identification information may be associated with the twelfth identification information. Further, a plurality of thirteenth identification information may be associated with one twelfth identification information.

  Further, each device may transmit and receive the fourteenth identification information to indicate that the network has multi-home DN connection capability. Further, each device may indicate that the network supports establishment of a multi-parallel PDU session by transmitting and receiving the fourteenth identification information. Each device may transmit and receive the fourteenth identification information to indicate that the request for UE_A10 has been permitted.

  Further, each device may transmit and receive the fifteenth identification information to indicate that the multihome DN connection requested by UE_A10 has been permitted. Further, each device may transmit and receive the fifteenth identification information to indicate that the network supports multi-homed DN connection.

  Alternatively, each device may indicate that multihome DN connection is not permitted by transmitting and receiving the fifteenth identification information. Further, each device may transmit and receive the fifteenth identification information to indicate that the network does not support multi-home DN connection.

  Further, each device may transmit and receive the sixteenth identification information to indicate that UE_A10 is located in an area where the network restricts multihome DN connection. That is, each device may transmit and receive the sixteenth identification information to indicate that UE_A10 is not located in an area where the network permits multihomed DN connection. And / or each device may indicate the area where multi-home DN connection is restricted by transmitting and receiving the 16th identification information. UE_A10 that has received the information indicating the area where the multihome DN connection is restricted may store this information. Further, when UE_A10 already stores an area in which the multihome DN connection is restricted by the network, the UE_A10 may update the area based on the reception of the sixteenth identification information.

  Further, each device may transmit and receive the seventeenth identification information to indicate that UE_A10 is located in an area where the network permits multihomed DN connection. And / or each device may indicate the area where the multi-home DN connection is permitted by transmitting and receiving the seventeenth identification information. UE_A10 that has received the information indicating the area where the multihome DN connection is permitted may store this information. Furthermore, when UE_A10 already stores an area where multihome DN connection is permitted by the network, the UE_A10 may update the area based on reception of the seventeenth identification information.

  Further, each device may transmit and receive the eighteenth identification information to indicate that the network has multi-parallel DN connection capability in this procedure. Each device may transmit and receive the eighteenth identification information based on the transmission and reception of the fifth identification information.

  Further, each device may transmit and receive the nineteenth identification information to indicate that the multi-parallel DN connection requested by UE_A10 has been permitted. Further, each device may transmit and receive the nineteenth identification information to indicate that the network supports multi-parallel DN connections. The nineteenth identification information may be eighteenth identification information.

  Alternatively, each device may transmit and receive the nineteenth identification information to indicate that the multi-parallel DN connection is not permitted. Further, each device may send and receive the nineteenth identification information to indicate that the network does not support multi-parallel DN connections.

  Furthermore, each device may transmit and receive the twentieth identification information to indicate that the UE_A10 is located in an area where the network restricts multi-parallel DN connection. That is, each device may transmit and receive the twentieth identification information to indicate that the UE_A10 is not located in an area where the network permits multi-parallel DN connection. And / or each device may indicate the area where the multi-parallel DN connection is restricted by transmitting and receiving the twentieth identification information. UE_A10 that has received the information indicating the area where the multi-parallel DN connection is restricted may store this information. Further, when UE_A10 already stores an area in which multihome DN connection is restricted by the network, the UE_A10 may update the area based on the reception of the twentieth identification information.

  Further, each device may transmit and receive the 21st identification information, thereby indicating that UE_A10 is located in an area where the network permits multi-parallel DN connection. And / or each device may indicate the area where multi-parallel DN connection is permitted by transmitting and receiving the 21st identification information. UE_A10 that has received the information indicating the area where the multi-parallel DN connection is permitted may store this information. Furthermore, when UE_A10 already stores an area in which multi-parallel DN connection is permitted by the network, the UE_A10 may update the area based on the reception of the 21st identification information.

  Here, the first condition determination may be the same as the first condition determination during the PDU session establishment procedure. The fourth condition determination is for the CPF_A140 to determine whether or not to execute a PDU session establishment procedure. The fourth condition is true when the PDU session establishment request message is received, and may be when the PDU session establishment procedure is also executed during this procedure. Further, the fourth condition is false when the PDU session establishment request message is not received, the PDU session establishment procedure may not be performed in this procedure, and the fourth condition is not determined to be true. Case is fine.

  When UE_A10 receives the RRC message from the NR node_A122, UE_A10 transmits an RRC connection message to the NR node_A122 (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). NR node_A122 receives the RRC message, and transmits a bearer setup message to CPF_A140 (S1612). Further, CPF_A140 receives the bearer setup message.

  When UE_A10 receives the attach acceptance message from CPF_A140 via NR node_A122, UE_A10 transmits an attach complete message to CPF_A140 via NR node_A122 (S1614) (S1616). Further, CPF_A140 receives the attach completion message. Further, when the fourth condition is true, CPF_A140 performs a second condition determination. The second condition determination is for the CPF_A140 to determine whether it is necessary to request the UPGW_A130 to change the bearer. If the second condition is true, the CPF_A 140 starts and executes the procedure (D) in the PDU session establishment 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 PDU session establishment procedure.

  Note that, when receiving the PDU session establishment acceptance message, the UE_A10 may transmit the attach completion message including the above-described PDU session establishment completion message, 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 reject message to UE_A10 via NR node_A122, 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 reject message. If the fourth 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.

  Alternatively, the attach rejection message may include information indicating an appropriate reason for rejection. Here, the information indicating the appropriate reason for refusal may be the thirtieth identification information. Specifically, by transmitting and receiving the 30th identification information, each device may indicate that it does not support connection to the NSI and / or PDN included in the NSI type requested by UE_A10, The information may indicate that connection to the NSI and / or PDN included in the NSI type requested by UE_A10 is not permitted.

  Each device completes this procedure based on the completion of procedure (A) or (B) in this procedure. In addition, 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 of (A) in this procedure, or the procedure of (B) in this procedure. 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 UE_A10 receives the tenth identification information and / or, UE_A10 determines that the connection to the requested PDN has been established, and starts transmitting and receiving user data between UE_A10 and PDN_A5 using the established PDU session. I do.

  Further, for example, when the UE_A10 receives the twelfth identification information and / or the thirteenth identification information, the UE_A10 stores the received twelfth identification information and / or the thirteenth identification information in the storage unit. If the same information has already been stored, the stored information is updated to the received information. Further, when the UE_A 10 performs the attach procedure and the PDU session establishment procedure, the requested NSI type and DNN may be selected from the stored twelfth identification information and / or thirteenth identification information.

  Further, for example, if UE_A10 receives the fourteenth identity, and / or UE_A10 receives the fifteenth identity, the fifteenth identity indicates that the network supports multi-homed DN connection If it is information, UE_A10 may continue to perform a procedure for adding a session to PDN_B6.

  Further, for example, when UE_A10 receives the sixteenth identification information, UE_A10 stores the received sixteenth identification information, and when UE_A10 moves from the area indicated by the sixteenth identification information, the attach procedure or the tracking area again. An update procedure may be performed.

  Furthermore, for example, when UE_A10 receives the seventeenth identification information, UE_A10 stores the received seventeenth identification information, and when UE_A10 moves from the area indicated by the seventeenth identification information, the attach procedure or the tracking area again. An update procedure may be performed.

  Further, for example, if UE_A10 receives the eighteenth identification information, and / or UE_A10 receives the nineteenth identification information, the nineteenth identification information indicates that the network supports multi-parallel DN connection. If so, UE_A10 may continue to perform a first attach procedure to PDN_B6 and / or a PDU session establishment procedure.

  Furthermore, for example, when UE_A10 receives the 20th identification information, UE_A10 stores the received 20th identification information, and when UE_A10 moves out of the area indicated by the 20th identification information, the attach procedure or the tracking area again. An update procedure may be performed.

  Furthermore, for example, when UE_A10 receives the 21st identification information, UE_A10 stores the received 21st identification information, and when UE_A10 moves out of the area indicated by the 21st identification information, the attach procedure or the tracking area again. An update procedure may be performed.

  Note that the UE_A10 is not limited to this and may start the tracking area update procedure after the completion of this procedure. For example, UE_A10 may start the tracking area update procedure based on expiration of the first timer.

  In addition, the above-described first to fourth condition determinations may be performed based on identification information and / or subscriber information included in the attach request message and / or an operator policy. For example, based on the sixth identification information included in the attach request message, the first condition determination and the third condition determination may be performed regardless of the registration state of the UE. 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 similar to the above-described PDU session establishment procedure example.

[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, and refers to a tracking area update procedure for PDN_A5. This procedure updates the location registration information of UE_A10 in the network (access network and / or core network_B190), 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 an arbitrary timing as long as the PDU session is established. UE_A10 can execute this procedure periodically.

[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 CPF_A140 via NR node_A122 (S1700), and starts a tracking area update procedure.

  Specifically, UE_A10 transmits an RRC message including the tracking area update request message to the NR node_A122, receives the RRC message including the tracking area update request message, and the NR node_A122 routes the tracking area update request message to the NF. Alternatively, CPF_A140 is selected as a shared CP function, and an attach request message is transmitted to CPF_A140. Here, the NR node_A 122 may select a routing destination NF or a shared CP function based on the tenth identification information included in the RRC message. Further, the tracking area update request message may be a NAS (Non-Access-Stratum) message.

  Here, UE_A10 may include at least one or more pieces of identification information of the second and third identification information in the tracking area update request message and / or the RRC message, or by including these pieces of identification information. , UE_A10. Further, UE_A10 may include identification information of the PDU session in the tracking area update request message and / or the RRC message.

  Each device transmits and receives the second identification information to indicate a list of PDNs to which UE_A10 requests connection. The second identification information may be an identification information group including a plurality of DNNs. Also, the list of PDNs indicated by the second identification information may or may not include PDNs for which a session has already been established. Furthermore, when the already-established PDN is included in the list of PDNs indicated by the second identification information, each device may transmit and receive the information in association with the already-identified PDN. Further, the second information may be associated with the third information.

  Further, each device transmits and receives the third identification information, thereby indicating a PDU session in which UE_A10 gives priority to connection. Further, the third identification information may indicate a PDN to which UE_A10 requests connection.

  CPF_A140 receives the tracking area update request message and performs a first condition determination. In the first condition determination, the CPF_A140 determines whether the first condition is true or false. CPF_A140 starts the procedure of (A) in this procedure if the first condition is true, and starts the procedure of (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. CPF_A140 executes the fourth condition determination, and starts the procedure (A) in this procedure. In the fourth condition determination, the CPF_A140 determines whether the fourth condition is true or false. If the fourth condition is true, the CPF_A140 selects the NSI and / or UPGW_A130 to be connected based on the received first identification information and / or tenth identification information, and Or the procedure of (D) in this procedure is started, and when the fourth condition is false, these procedures are omitted (S1703) (S1704).

  Here, the first condition determination may be the same as the first condition determination during the attach procedure. The fourth condition determination is for determining whether a change and / or addition and / or deletion procedure of the PDU session is necessary.

  CPF_A140 may determine the switching of the session based on the second identification information and / or the third identification information. Specifically, if the PDN indicated by the second identification information and / or the third identification information is PDN_B6, it is possible to establish a session to PDN_B6 by further moving UE_A10 and / or changing the operator policy. In some cases, CPF_A140 may decide to switch the session from a connection to PDN_A5 to a connection to PDN_B6.

  Alternatively, CPF_A140 may determine to switch from a PDU session to PDN_A5 to a PDU session to PDN_B6 based on the state of the network without depending on the message included in the tracking area update request message.

  If the session is not switched, each device executes the procedure (C) in this procedure. Here, the CPF_A140 may include at least one or more of the second and third identification information in the message to the UPGW_A130 during the procedure (C) in this procedure, or By including the information, the request of UE_A10 may be transmitted to each device.

  When switching sessions, each device executes the procedure (D) in this procedure. Here, CPF_A140 may select UPGW_B131 as the GW to which the session is switched. The selection of the GW may be performed based on information obtained from the HSS. Further, the CPF_A140 transmits, to the selected UPGW_B131, at least one or more of the second identification information and the third identification information, and the identification information of the UPGW_A130, and the identification information of the PDU session, in the message. May do it.

  The UPGW_B 131 may approve the switching of the PDU session based on at least one of the received identification information, and may further execute a procedure for requesting information regarding the session to the UPGW_A 130 that is a GW during the switching. In addition, each device may execute a procedure for switching the PDU session.

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

  If the third condition is true, the CPF_A140 sends a Tracking Area Update accept message to the UE_A10 via the NR node_A122 (S1706), and if the third condition is false, this procedure Start the procedure in (B). The tracking area update acknowledgment message may include an appropriate acknowledgment reason. Note that the tracking area update acceptance message may be a response message to the tracking area update request message, and is not limited to this, and may be a message that accepts the tracking area update request.

  Here, CPF_A140 may include the tracking area update acceptance message in an S1AP message (for example, UE Context Modification Request or Downlink NAS Transport) and transmit it to NR node_A122. Further, the tracking area update acceptance message may be a NAS message. Further, NR node_A122 may transmit the tracking area update acceptance message received by UE_A10 in the RRC message.

  Here, the CPF_A140 may include at least one or more of the tenth to thirteenth and twenty-second identification information in the tracking area update acceptance message and / or the S1AP message, or include these identification information. This may indicate that the request of UE_A10 has been accepted. Further, the NR node_A122 may include one or more identification information of the tenth to thirteenth and twenty-second identification information in the RRC message, or by including these identification information, the request of UE_A10 is accepted. You may show it.

  Each device may indicate the NSI type to which the PDU session established by this procedure connects by transmitting and receiving the tenth identification information. Further, each device may indicate the information for identifying the PDN to which the PDU session established by this procedure is connected by transmitting and receiving the eleventh identification information. Each device may transmit and receive the eleventh identification information to indicate that the request of UE_A10 has been permitted.

  Further, by transmitting and receiving the twelfth identification information, each device indicates the NSI type to which UE_A10 is permitted to connect, in addition to the NSI type to which the PDU session established in this procedure connects. Alternatively, each device indicates the NSI type to which UE_A10 can connect by transmitting and receiving the twelfth identification information. The NSI type indicated by the twelfth identification information may be one or more NSI types.

  Further, by transmitting and receiving the thirteenth identification information, each device indicates a PDN to which UE_A10 is permitted to connect, in addition to the PDN to which the PDU session established in this procedure is connected. Alternatively, each device may indicate the PDN to which UE_A10 can connect by transmitting and receiving the thirteenth identification information. The thirteenth identification information may be associated with the twelfth identification information. Further, a plurality of thirteenth identification information may be associated with one twelfth identification information. Further, each device may transmit and receive the 22nd identification information to instruct the switching of the session in this procedure. The 22nd identification information may be an IP address indicating a switching destination.

  When receiving the tracking area update acceptance message, UE_A10 transmits a tracking area update complete (Tracking Area Update complete) message to CPF_A140 via NR node_A122 (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. CPF_A140 transmits a Tracking Area Update reject message to UE_A10 via NR node_A122. 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 information indicating an appropriate reason for rejection. In addition, 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, the information indicating the appropriate reason for refusal may be the thirtieth identification information. Specifically, by transmitting and receiving the 30th identification information, each device may indicate that it does not support connection to the NSI and / or PDN included in the NSI type requested by UE_A10, The information may indicate that connection to the NSI and / or PDN included in the NSI type requested by UE_A10 is not permitted.

  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 UE_A10 receives at least one piece of information from the tenth to thirteenth identification information, UE_A10 stores and / or updates the received identification information, and may be used in the next tracking area update procedure. .

  When UE_A10 receives the 22nd identification information, UE_A10 may authenticate the switching of the session. Further, when the 22nd identification information is an IP address, UE_A10 may store the received IP address.

  Note that UE_A10 may start the tracking area update procedure after completing this procedure. For example, UE_A10 may start the tracking area update procedure based on expiration of the first timer.

  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 may not be 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. Further, the first condition, and / or the second condition, and / or the third 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.

[2. Modifications]
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.

  Note that a program for implementing 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. In addition, the “computer-readable recording medium” is a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another 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 may 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 may be a conventional processor, controller, microcontroller, or state machine. The above-described electric circuit may be configured 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 includes a design change or the like without departing from the gist of the present invention. Further, the present invention can be variously modified within the scope shown in the claims, and the technical scope of the present invention includes embodiments obtained by appropriately combining technical means disclosed in different embodiments. It is. The elements described in each of the above embodiments also include a configuration in which elements having the same effects are replaced with each other.

1 Mobile communication systems
5 PDN_A
6 PDN_B
7 PDN_C
10 UE_A
30 PGW_A
35 SGW_A
40 MME_A
42 SGSN_A
45 eNB_A
46 SCEF_A
50 HSS_A
60 PCRF_A
80 E-UTRAN_A
120 NextGen RAN_A
122 NR node_A
125 WLAN ANc
126 WAG_A
130 UPGW_A
131 UPGW_B
132 UPGW_C
140 CPF_A
141 CPF_B
190 Core Network_B

Claims (19)

A terminal device,
To a network function unit configured in the core network, the first identification information and the second identification information, to transmit an attach request message including, a transmission unit,
From the network function unit, receiving an attach acceptance message including third identification information, a receiving unit,
Based on the third identification information, PDN (Packet Data Network) indicated by the third identification information via the core network and establishes a session between the terminal device, comprising a control unit,
The transmitting unit and the receiving unit start transmitting and receiving the user data with the PDN using the session,
here,
The first identification information is information indicating one or more PDNs requested by the terminal device,
The second identification information is information indicating a PDN requested by the terminal device with priority,
The first identification information and the second identification information, the network function unit is used to determine the connection destination PDN of the terminal device,
The third identification information is information indicating a PDN that the core network has permitted the terminal device to connect to,
A terminal device characterized by the above-mentioned. The core network constitutes at least a network slice instance,
The network function unit includes:
It is a functional unit of control information having a mobility management function of the terminal device,
Configured in the network slice instance,
The transmitting unit transmits the attach request message including the fourth identification information,
The fourth identification information is information indicating a network slice type to which the network slice belongs.
The terminal device according to claim 1, wherein: The transmission unit,
The first identification information and the second identification information in the RRC message including the attach request message, including the transmission to the base station,
The first identification information and the second identification information are used by the base station to determine the network function unit to which the attach request message is transferred,
2. The terminal device according to claim 1, wherein: The receiving unit,
The attach acceptance message includes the fifth identification information and receives,
The control unit includes:
Based on the reception of the fifth identification information, start a procedure for establishing an additional session,
The fifth identification information is information indicating that the core network permits establishment of an additional session by the terminal device.
3. The terminal device according to claim 1, wherein: By leaving the second identification information empty, indicating that priority is not given to connection to a specific PDN,
4. The terminal device according to claim 1, wherein: A network function unit configured in the core network,
From the terminal device, receiving the attach request message including the first identification information and the second identification information, a receiving unit,
Based on the reception of the first identification information and the second identification information, determine the PDN (Packet Data Network) of the connection destination of the terminal device,
A control unit for establishing a session with the gateway device of the determined PDN,
To the terminal device, to transmit an attach acceptance message including third identification information, comprising a transmitting unit,
here,
The first identification information is information indicating one or more PDNs requested by the terminal device,
The second identification information is information indicating a PDN requested by the terminal device with priority,
The third identification information is information indicating a PDN that the core network has permitted the terminal device to connect to,
A network function unit characterized by the following. The core network constitutes at least a network slice,
The network function unit includes:
It is a functional unit of control information having a mobility management function of the terminal device,
Configured in the network slice,
The receiving unit receives the attach request message including fourth identification information,
The fourth identification information is information indicating a network slice type to which the network slice belongs.
7. The network function unit according to claim 6, wherein: A base station device,
From the terminal device, to receive including the first identification information and the second identification information in the RRC message including the attach request message, a receiving unit,
Based on the first identification information and the second identification information, determine a network function unit of the transfer destination of the attach request message, a control unit,
And transmitting and receiving the attach request message to the network function unit,
The first identification information is information indicating one or more PDNs requested by the terminal device,
The second identification information is information indicating a PDN requested by the terminal device with priority,
A base station device, characterized in that: The transmission unit,
The attachment acceptance message, including the fifth identification information and transmitting,
The fifth identification information is information indicating that the core network permits establishment of an additional session by the terminal device.
8. The network function unit according to claim 6, wherein: A communication control method for a terminal device,
Transmitting an attach request message including first identification information and second identification information to a network function unit configured in the core network;
From the network function unit, receiving an attach acceptance message including third identification information,
Based on the third identification information, through the core network PDN (Packet Data Network) indicated by the third identification information and establishing a session between the terminal device,
Starting transmission and reception of the PDN and user data using the session,
here,
The first identification information is information indicating one or more PDNs requested by the terminal device,
The second identification information is information indicating a PDN requested by the terminal device with priority,
The first identification information and the second identification information, the network function unit is used to determine the connection destination PDN of the terminal device,
The third identification information is information indicating a PDN that the core network has permitted the terminal device to connect to,
A communication control method for a terminal device, comprising: The core network constitutes at least a network slice instance,
The network function unit includes:
It is a functional unit of control information having a mobility management function of the terminal device,
Configured in the network slice instance,
Transmitting the attach request message including fourth identification information, further comprising:
The fourth identification information is information indicating a network slice type to which the network slice belongs.
11. The communication control method for a terminal device according to claim 10, wherein: Transmitting the first identification information and the second identification information to the base station including the RRC message including the attach request message, further comprising:
The first identification information and the second identification information are used by the base station to determine the network function unit to which the attach request message is transferred,
11. The communication control method for a terminal device according to claim 10, wherein: Receiving the attachment acceptance message including fifth identification information;
Starting a procedure for establishing an additional session based on receiving the fifth identification information, further comprising:
The fifth identification information is information indicating that the core network permits establishment of an additional session by the terminal device.
12. The communication control method for a terminal device according to claim 10, wherein: By leaving the second identification information empty, indicating that priority is not given to connection to a specific PDN,
13. The communication control method for a terminal device according to claim 10. A communication control method of a network function unit configured in a core network,
From the terminal device, receiving an attach request message including the first identification information and the second identification information,
Based on the reception of the first identification information and the second identification information, determining the PDN (Packet Data Network) of the connection destination of the terminal device,
Establishing a session with the gateway device of the determined PDN,
Transmitting an attach acceptance message including third identification information to the terminal device,
here,
The first identification information is information indicating one or more PDNs requested by the terminal device,
The second identification information is information indicating a PDN requested by the terminal device with priority,
The third identification information is information indicating a PDN that the core network has permitted the terminal device to connect to,
A communication control method for a network function unit, comprising: The core network constitutes at least a network slice,
The network function unit includes:
It is a functional unit of control information having a mobility management function of the terminal device,
Configured in the network slice,
Receiving the attach request message including the fourth identification information,
The fourth identification information is information indicating a network slice type to which the network slice belongs.
16. The communication control method for a network function unit according to claim 15, wherein: A communication control method for a base station device,
From the terminal device, receiving including the first identification information and the second identification information in the RRC message including the attach request message,
Based on the first identification information and the second identification information, determining a network function unit of the transfer destination of the attach request message,
Transmitting the attach request message to the network function unit,
The first identification information is information indicating one or more PDNs requested by the terminal device,
The second identification information is information indicating a PDN requested by the terminal device with priority,
A communication control method for a base station device, comprising: Transmitting the attachment acceptance message including fifth identification information,
The fifth identification information is information indicating that the core network permits establishment of an additional session by the terminal device.
15. The communication control method for a network function unit according to claim 15, wherein: A communication system,
The communication system includes a terminal device and / or a network function unit and / or a base station device,
The terminal device,
To the network function unit configured in the core network, the first identification information and the second identification information, send an attach request message including,
From the network function unit, receiving an attach acceptance message including third identification information,
Based on the third identification information, establish a session between the PDN (Packet Data Network) and the terminal device indicated by the third identification information via the core network,
Starting transmission and reception of user data with the PDN using the session,
here,
The first identification information is information indicating one or more PDNs requested by the terminal device,
The second identification information is information indicating a PDN requested by the terminal device with priority,
The first identification information and the second identification information, the network function unit is used to determine the connection destination PDN of the terminal device,
The third identification information is information indicating a PDN that the core network has permitted the terminal device to connect to,
A communication system, characterized in that:

Images