WO2010146815A1 - Procédé de sélection de protocole de gestion de la mobilité, système de sélection de protocole de gestion de la mobilité, nœud mobile, agent local, et nœud de serveur mandataire - Google Patents

Procédé de sélection de protocole de gestion de la mobilité, système de sélection de protocole de gestion de la mobilité, nœud mobile, agent local, et nœud de serveur mandataire Download PDF

Info

Publication number
WO2010146815A1
WO2010146815A1 PCT/JP2010/003905 JP2010003905W WO2010146815A1 WO 2010146815 A1 WO2010146815 A1 WO 2010146815A1 JP 2010003905 W JP2010003905 W JP 2010003905W WO 2010146815 A1 WO2010146815 A1 WO 2010146815A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
mobility management
management protocol
connection
mobile node
Prior art date
Application number
PCT/JP2010/003905
Other languages
English (en)
Japanese (ja)
Inventor
啓吾 阿相
新吉 池田
純 平野
隆二 杉崎
Original Assignee
パナソニック株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by パナソニック株式会社 filed Critical パナソニック株式会社
Publication of WO2010146815A1 publication Critical patent/WO2010146815A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0027—Control or signalling for completing the hand-off for data sessions of end-to-end connection for a plurality of data sessions of end-to-end connections, e.g. multi-call or multi-bearer end-to-end data connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H04W80/045—Network layer protocols, e.g. mobile IP [Internet Protocol] involving different protocol versions, e.g. MIPv4 and MIPv6
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy

Definitions

  • the present invention relates to a mobility management protocol selection method and a mobility management protocol selection system for selecting a type of protocol for managing movement of a mobile node.
  • the present invention also relates to a mobile node, a home agent, and a proxy node in a mobility management protocol selection system.
  • the present invention particularly relates to a mobility management protocol for each connection when the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network.
  • the present invention relates to a method for selecting a type.
  • Non-Patent Document 1 mobile IP
  • CMIP Client Mobile IP
  • DSMIPv6 mobile IPv6
  • MN mobile node
  • CoA care-of address
  • HoA Home Address
  • HoA Home Address
  • HA home address
  • CN CorrespondentpondNode
  • Non-Patent Document 2 describes a method in which the MN associates a plurality of CoAs with one HoA and registers them with the HA.
  • proxy mobile IP (refer to Non-Patent Document 3 below, referred to as PMIP (Proxy Mobile IP)) and GTP (General packet wireless service Tunnelling Protocol) are known.
  • PMIP Proxy Mobile IP
  • GTP General packet wireless service Tunnelling Protocol
  • a MAG Mobility Anchor Gateway
  • PMIP / GTP a MAG (Mobility Anchor Gateway) serving as a proxy node of the MN updates the location information of the MN as a proxy, so the MN does not need to perform mobility management.
  • PMIP Mobility Anchor Gateway
  • 3GPP Third Generation Partnership Project
  • UE User Equipment
  • Non3GPP interface connected to a Non3GPP network
  • WLAN Wireless Local Area Network
  • WiMAX WiMAX
  • the UE can connect to the 3GPP core network (EPC: Evolved Packet Core) from either the 3GPP interface or the Non3GPP interface. For this reason, the UE can perform handover between the two interfaces, or can connect to the EPC from both interfaces simultaneously.
  • EPC Evolved Packet Core
  • P-GW PDN gateway
  • PDN Packet Data Network
  • S-GW Serving gateway
  • the UE generates an IP address from a home network prefix (HNP) assigned from the P-GW and uses it as a home address (HoA).
  • HNP home network prefix
  • HoA home address
  • the Non3GPP network is a trusted network (Trusted Non-3GPP network)
  • the UE and the P-GW may communicate with each other via PMIP or Access Gateway (AGW).
  • AGW Access Gateway
  • the PMIP or GTP When connected by a PDN connection established by GTP, CMIP, or MIPv4, and the Non3GPP network is an untrusted network (Untrusted Non-3GPP network), the PMIP or GTP via ePDG (evolved Packet Data Gateway) Or a PDN connection constructed by CMIP.
  • ePDG evolved Packet Data Gateway
  • the UE can present the mobility management protocol type used by the UE in the Non3GPP network in a connection procedure (Attach Procedure) performed when connecting to the Non3GPP network.
  • Attach Procedure For example, when the UE presents use of CMIP when connected to the Trusted Non-3GPP network, and the presentation is accepted by the network side, a local prefix is assigned from the AGW. The UE generates an address from the acquired local prefix, and uses the address as a care-of address (CoA).
  • the UE connects to the Trusted Non-3GPP network, it presents the use of PMIP or GTP, and if the presentation is accepted by the network side, the HNP is assigned from the AGW, and the UE The generated address is used as HoA.
  • the UE 10 is connected to the 3GPP network 11 or the Non3GPP network 14 .
  • the UE 10 is connected to the 3GPP network 11 using the 3GPP interface IF1 and has established two different PDN connections Conn1 and Conn2 for the P-GW 13.
  • These PDN connections Conn1 and Conn2 are established using PMIP (or GTP), and different prefixes P1 and P2 are assigned (HoA is HoA1 and HoA2, respectively).
  • the S-GW 12 functions as the MAG of the UE 10 and registers the location information of the UE 10 to the P-GW 13 on behalf of the UE 10.
  • the UE 10 is further connected to the Non3GPP network 14, it is necessary to determine a PDN connection to be established on the Non3GPP network 14 side.
  • a PDN connection established on the Non3GPP network 14 side (1) A method of establishing a new PDN connection on the Non3GPP network 14 side, or (2) a method of moving the PDN connections Conn1 and Conn2 established on the 3GPP network 11 side to the Non3GPP network 14 side, (3) A method of generating a connection from the Non3GPP network 14 side for the PDN connections Conn1 and Conn2 established on the 3GPP network 11 side, There are three options.
  • the assigned prefix is also different.
  • the prefixes P1 and P2 used on the 3GPP network 11 side are also assigned on the Non3GPP network 14 side, and the same home addresses (HoA1 and HoA2) are used.
  • the communication flow using the HoA1 and HoA2 is the 3GPP network 11 side and the Non3GPP network 14 side. Data can be transferred using either side.
  • CMIP-based connection When generating the connection of (3), there are two types, a CMIP-based connection and a PMIP-based connection.
  • CMIP-based connection the UE 10 acquires CoA on the Non3GPP network 14 side, and performs communication using HoA through a tunnel between the P-GW 13 and the CoA. At this time, communication using the HoA itself is performed in the 3GPP interface IF1 connected to the 3GPP network 11 side.
  • PMIP-based connection since the same HoA is allocated to both the 3GPP interface IF1 and the Non3GPP interface IF2, the UE 10 uses a new address for using the same address (HoA) on different interfaces IF1 and IF2. A management mechanism is required.
  • the UE 10 registers a routing rule (also referred to as a filtering rule) indicating a transfer destination of a specific flow with the P-GW 13, if the connection is a CMIP-based connection, the information indicating the transfer destination is 3GPP
  • the interface IF1 side can use HoA
  • the Non3GPP interface IF2 side can use CoA.
  • the addresses assigned to both interfaces IF1 and IF2 are the same HoA. Cannot be used to indicate the destination interface. For this reason, the UE 10 has an advantage of using a CMIP-based connection as a method for generating the connection (3).
  • the UE 10 it is reasonable for the UE 10 to retain such a policy as a criterion for determining the mobility management protocol type of the PDN connection established on the Non3GPP network 14 side.
  • the type of the PDN connection used on the Non3GPP network 14 side is determined as one of the connection procedures (Attach Procedure) when the UE 10 connects to the Non3GPP network 14 side.
  • the CMIP-based method when the CMIP-based method is selected in order to connect to the PDN connection Conn1 of the two PDN connections Conn1 and Conn2 established on the 3GPP network 11 side also from the Non3GPP network 14 side, Also, when it is desired to move the other PDN connection Conn2 to the Non3GPP network 14 side or to establish a new PDN connection, it is necessary to use a CMIP-based method, which increases the processing load on the UE 10. In other words, by applying the above-described policy, the UE 10 cannot select such that the CMIP-based method is used for one PDN connection Conn1 and the PMIP-based method is used for the other PDN connection Conn2.
  • the present invention provides a network base when a second interface of a mobile node is connected to a second network from a state in which the first interface of the mobile node has a plurality of connections in the first network. It is an object of the present invention to provide a mobility management protocol selection method, a mobility management protocol selection system, a mobile node, a home agent, and a proxy node that can reduce the processing load on a mobile node by selecting a mobility management protocol. The present invention also provides that the second interface of the mobile node is changed from the state in which the first interface of the mobile node has a plurality of connections in the first network without increasing the processing load of the mobile node.
  • a mobility management protocol selection method a mobility management protocol selection system, a mobile node, a home agent, and a proxy node capable of selecting a network-based or client-based mobility management protocol as a mobility management protocol type used by each connection when connected
  • the purpose is to provide.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network.
  • a mobility management protocol selection method for selecting a mobility management protocol type for each connection When the first interface has a plurality of connections in the first network, the second interface is a client-based mobility management protocol to the second network from the mobile node to the home agent of the mobile node.
  • the second interface connects to a second network with a client-based mobility management protocol, between the home agent and the proxy node of the mobile node in the second network based on the protocol indication step
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network. And a mobility management protocol selection system for selecting a mobility management protocol type for each connection, When the first interface has a plurality of connections in the first network, the second interface is a client-based mobility management protocol to the second network from the mobile node to the home agent of the mobile node.
  • Protocol instruction means for instructing a network-based mobility management protocol as a mobility management protocol type used by the first connection that is connected simultaneously with the other second connection when connected to
  • a tunnel establishing means for establishing a tunnel for the first connection using the network-based mobility management protocol; It was set as the structure which has.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network.
  • the mobile node in the mobility management protocol selection system for selecting the mobility management protocol type for each connection, When the first interface has a plurality of connections in the first network and the second interface connects to the second network with a client-based mobility management protocol for the home agent of the mobile node And a protocol instruction means for instructing a network-based mobility management protocol as a mobility management protocol type used by the first connection that is connected simultaneously with another second connection.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network. And a mobile agent home agent in a mobility management protocol selection system for selecting a mobility management protocol type for each connection, When the first interface has a plurality of connections in the first network, the second interface is connected to the second network by the client-based mobility management protocol from the mobile node to the home agent.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network. And a proxy node of the mobile node in the second network in a mobility management protocol selection system for selecting a mobility management protocol type for each connection,
  • a tunnel for the first connection that is connected to the home agent simultaneously with another second connection is network-based.
  • the tunnel establishment means is established with the mobility management protocol.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network.
  • a mobility management protocol selection method for selecting a mobility management protocol type for each connection When the second interface is connected to the second network by a client-based mobility management protocol, the mobile node transmits another second connection to the proxy node of the mobile node in the second network.
  • a tunnel establishment request step for requesting that a tunnel for a first connection to be simultaneously connected is established by a network-based mobility management protocol; Tunnel establishment for establishing a tunnel for the first connection by the network-based mobility management protocol between the home agent and the proxy node of the mobile node in the second network based on the tunnel establishment request step Step and It was set as the structure which has.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network. And a mobility management protocol selection system for selecting a mobility management protocol type for each connection, When the second interface is connected to the second network by a client-based mobility management protocol, the mobile node transmits another second connection to the proxy node of the mobile node in the second network.
  • Tunnel establishment request means for requesting to establish a tunnel for the first connection to be simultaneously connected by a network-based mobility management protocol; Tunnel establishment for establishing a tunnel for the first connection by the network-based mobility management protocol between the home agent and the proxy node of the mobile node in the second network based on the tunnel establishment request step Means, It was set as the structure which has.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network.
  • the mobile node in the mobility management protocol selection system for selecting the mobility management protocol type for each connection Means for obtaining an address of a proxy node of the mobile node in the second network when the second interface connects to a second network with a client-based mobility management protocol; Requesting the proxy node to establish a tunnel between the mobile node and the proxy node, and network-based movement of the tunnel for the first connection connected simultaneously with the other second connection
  • a tunnel establishment request means for requesting establishment by a management protocol; It was set as the structure which has.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network. And a mobile agent home agent in a mobility management protocol selection system for selecting a mobility management protocol type for each connection, When the second interface is connected to the second network by a client-based mobility management protocol, the second interface is connected to the proxy node of the mobile node in the second network simultaneously with another second connection. One tunnel for connection is established using a network-based mobility management protocol.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network.
  • a proxy node of the mobile node in the second network in a mobility management protocol selection system for selecting a mobility management protocol type for each connection, Establishing a tunnel from the mobile node between the mobile node and the proxy node when the second interface connects to a second network with a client-based mobility management protocol; Means for accepting the request when it is requested to establish a tunnel for the first connection to be connected simultaneously with the connection of the network-based mobility management protocol; Tunnel establishment means for establishing a tunnel with the mobile node based on the request and establishing a tunnel for the first connection with the home agent by the network-based mobility management protocol; It was set as the structure which has.
  • This configuration selects a network-based mobility management protocol when the first interface of the mobile node has multiple connections in the first network and the second interface of the mobile node connects to the second network. Therefore, the processing load on the mobile node can be reduced.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network.
  • a mobility management protocol selection method for selecting a mobility management protocol type for each connection, When the second interface connects to the second network with a client-based mobility management protocol from the mobile node to a home agent of the mobile node or a proxy node of the mobile node in the second network;
  • a protocol instruction step for selectively instructing a network-based or client-based mobility management protocol as a mobility management protocol type used by each connection; Based on the protocol instruction step, a tunnel for each connection is established between the home agent and the proxy node of the mobile node in the second network by the instructed network-based or client-based mobility management protocol Tunnel establishment step to It was set as the structure which has.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network.
  • a mobility management protocol selection system for selecting a mobility management protocol type for each connection, When the second interface connects to the second network with a client-based mobility management protocol from the mobile node to a home agent of the mobile node or a proxy node of the mobile node in the second network;
  • a protocol instruction means for selectively instructing a network-based or client-based mobility management protocol as a mobility management protocol type used by each connection;
  • a tunnel for each connection is established between the home agent and the proxy node of the mobile node in the second network by the instructed network-based or client-based mobility management protocol Tunnel establishment means to It was set as the structure which has.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network.
  • the mobile node in the mobility management protocol selection system for selecting the mobility management protocol type for each connection, A network as a mobility management protocol type used by each connection when the second interface is connected to a second network with respect to a home agent of the mobile node or a proxy node of the mobile node in the second network
  • a protocol instruction means for selectively instructing a base or client-based mobility management protocol is provided.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network.
  • a mobile agent home agent in a mobility management protocol selection system for selecting a mobility management protocol type for each connection A network-based or client-based mobility management protocol is selectively selected from the mobile node as a mobility management protocol type used by each connection when the second interface is connected to a second network using a client-based mobility management protocol.
  • Tunnel establishment means for establishing a tunnel for each connection with the proxy node of the mobile node in the second network by the designated network-based or client-based mobility management protocol based on the protocol instruction step And It was set as the structure which has.
  • the present invention provides a case where the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network.
  • a proxy node of the mobile node in the second network in a mobility management protocol selection system for selecting a mobility management protocol type for each connection,
  • a network-based or client-based mobility management protocol is selectively selected from the mobile node as a mobility management protocol type used by each connection when the second interface is connected to a second network using a client-based mobility management protocol.
  • the second interface of the mobile node is connected to the second network from the state where the first interface of the mobile node has a plurality of connections in the first network without increasing the processing load of the mobile node.
  • a network-based or client-based mobility management protocol can be selected as the mobility management protocol type for each connection.
  • a network-based mobility management protocol when a second interface of a mobile node is connected to a second network from a state in which the first interface of the mobile node has a plurality of connections in the first network Can be selected to reduce the processing load on the mobile node. Further, according to the present invention, the second interface of the mobile node is changed from the state in which the first interface of the mobile node has a plurality of connections in the first network without increasing the processing load of the mobile node.
  • a network-based or client-based mobility management protocol can be selected as the mobility management protocol type of each connection.
  • FIG. 1 shows a network configuration diagram according to the first embodiment of the present invention.
  • the UE 10 which is a mobile node includes a 3GPP interface (cellular interface) IF1 and a WLAN interface IF2 as a Non3GPP interface.
  • the Non3GPP interface may be a WiMAX interface, an HRPD interface, or the like.
  • the 3GPP interface IF1 is connected to the 3GPP network 11 which is an HPLMN (Home Public Land Mobile Network) for the UE 10, and is connected to the P-GW 13 which is the home agent of the UE 10 via the S-GW 12 which is the proxy node of the UE 10.
  • HPLMN Home Public Land Mobile Network
  • a PMIP (or GTP) connection is established and HoA is used in this connection. Furthermore, the UE 10 establishes two PDN connections Conn1 and Conn2 with the P-GW 13, and uses different prefixes P1 and P2 and uses HoA1 and HoA2 as addresses.
  • the PDN connection Conn1 is connected from the Non3GPP network 14 side. It is assumed that the PDN connection Conn2 is simultaneously connected to the P-GW 13 from the Non3GPP network 14 side while maintaining the connection from the 3GPP network 11 side.
  • the term “simultaneous connection” here refers to a connection in the case where PDN connections are simultaneously established from different interfaces IF1 and IF2 to the same P-GW 13 and the home prefixes assigned by the respective PDN connections are the same. .
  • FIG. 2 shows a communication sequence when the UE 10 is connected to the Non-3GPP network 14 when the UE 10 is connected to the 3GPP network 11 in the first embodiment.
  • the UE 10 is connected only to the 3GPP network 11 (the PMIP / GTP tunnel T0 between the S-GW 12 and the P-GW 13), the UE 10 PDN connections Conn1 and Conn2 are established at the same time, and different prefixes P1 and P2 are assigned to each other, and HoA1 and HoA2 are used as addresses.
  • the UE 10 when connected to only the 3GPP network 11, the UE 10 communicates with the P-GW 13 to which the PDN connection Conn2 is connected before connecting to the Non3GPP network 14 side.
  • SA Security Association
  • the UE 10 uses the PMIP-based (or GTP-based) method for the PDN connection Conn1 when connecting to the Non3GPP network 14 in the SA establishment procedure executed on the 3GPP network 11 side.
  • the P-GW 13 is notified of the establishment. Instead of specifying either PMIP base or GTP base, network base may be specified.
  • the UE 10 requests the P-GW 13 in advance to advertise the prefix P1 on the Non3GPP network 14 side.
  • the P-GW 13 declares that the UE 10 uses the CMIP-based method when connecting to the Non3GPP network 14, it generates a CoA to be used when establishing the PDN connection Conn2. It recognizes that it is necessary to advertise the prefix P1 for the PDN connection Conn1 together with the local prefix.
  • the P-GW 13 receives a BU message (via the AGW 15) requesting generation of a connection using the CMIP-based method for establishing the PDN connection Conn2 from the UE 13, Based on the fact that the request is received in (2), it is determined that the prefix P1 is advertised to the UE 10. As a method in which the P-GW 13 notifies the UE 10 that the handover of the PDN connection Conn1 to the Non3GPP network 14 is completed, that is, the PDN connection Conn1 is established on the Non3GPP network 14 by a PMIP-based method.
  • binding confirmation (BA) message which is a response (11) to the binding update (BU) message received from the UE 10
  • information indicating that the PMIP connection has been established may be included. For example, it can be indicated by the value of the status field of the BA message.
  • P-GW 13 In order to further advertise prefix P1 from AGW 15 to UE 10, P-GW 13 notifies prefix P1 to AGW 15, and advertises prefix P1 to UE 10 together with prefix P3, which is a local prefix for CoA generation. Instruct them to do so. Instead of recognizing that the PMIP connection has been established by the BA message in (11), the UE 10 may recognize that the PMIP connection has been established when the prefix P1 is advertised from the AGW 15. Further, the P-GW 13 may transmit the BA message, which is a response to the BU message received from the UE 10, including the prefix P1, or advertise the prefix P1 together with the prefix P3 in the RA message to the AGW 15. You may instruct. Although not shown in FIG.
  • the AGW 15 when the AGW 15 receives an instruction from the P-GW 13 to advertise the prefix P1, the AGW 15 uses the PDN connection Conn1 together with the prefix 3, which is a local prefix for generating the CoA for CMIP connection.
  • the prefix P1 which is a home prefix, is advertised.
  • the UE 10 connected to the Non3GPP network 14 only needs to declare connection to the AGW 15 by a CMIP-based method, even if there are a plurality of PDN connections, the UE 10 is used for each PDN connection in the Non3GPP network 14. It is not necessary to notify the protocol type (PMIP or CMIP), and the message size can be reduced.
  • FIG. 3 shows a block diagram of the UE 10.
  • the UE 10 includes a 3GPP interface IF1, a Non3GPP interface (WLAN interface) IF2, a CMIP connection unit 101, a Non3GPP network connection processing unit 102, a simultaneous connection determination unit 103, a PDN connection information holding unit 104, an SA generation unit 105, including.
  • the simultaneous connection determination unit 103 refers to the PDN connection information holding unit 104 and simultaneously connects from the Non3GPP network 14 side to the same HoA in the PDN connections Conn1 and Conn2 established on the 3GPP network 11. On the other hand, it is confirmed whether or not there is a PDN connection that needs to establish a connection by a CMIP-based method. If there is a corresponding PDN connection (Conn1), information indicating that the PDN connection requires simultaneous connection is added to the PDN connection information holding unit 104 in the corresponding PDN connection information. The simultaneous connection determination unit 103 further instructs the SA generation unit 105 to establish an SA with the P-GW 13 to which the PDN connection is connected.
  • a criterion for determining whether or not simultaneous connection is required it is possible to determine based on the type and state of a flow when communicating on the 3GPP interface IF1.
  • a PDN connection that flows a communication flow requiring a large bandwidth a PDN connection whose resource type is Non-GBR (Non-Guaranteed Bitrate Resources), and the like are selected as targets for simultaneous connection.
  • the determination may be based on the QCI value or priority instead of the resource type.
  • information indicating whether or not simultaneous connection may be included in the routing rule held by the UE. Further, information regarding this routing rule may be obtained from an ANDSF (Access Network Discovery and Selection Function) server.
  • ANDSF Access Network Discovery and Selection Function
  • the SA generation unit 105 Upon receiving an instruction from the simultaneous connection determination unit 103, the SA generation unit 105 starts connection processing using IKEv2 for the P-GW 13 that establishes the simultaneous connection. Further, the SA generation unit 105 causes the PDN connection Conn1 to be handed over to the Non3GPP network 14 when the P-GW 13 is connected to the Non3GPP network 14 in the IKEv2 connection process, and establishes the PDN connection by a PMIP-based method. (PMIP connection request) is notified to the P-GW 13.
  • PMIP connection request PMIP connection request
  • the EPS bearer ID (eg, EPS bearer ID of the default bearer) of the PDN connection Conn1, APN (Access Point Name), HoA1, home Notify the prefix P1 and the like.
  • IKEv2 message for example, IKE_SA_INIT, IKE_AUTH, CREATE_CHILD_SA, INFORMATIONAL transmitted to the P-GW 13, but is not limited thereto.
  • the CMIP connection unit 101 described later may transmit a BU message including a PMIP connection request to the P-GW 13.
  • a payload included in the IKEv2 message a payload such as Identification_Payload or Configuration_Payload can be used, but another type of payload or a new payload may be used.
  • the SA generation unit 105 may generate the SA from the Non3GPP interface 14 after the UE 10 connects to the Non3GPP network 14 side, not from the 3GPP network 11 side.
  • the Non3GPP network connection processing unit 102 performs processing necessary for the Non3GPP interface (WLAN interface IF2) of the UE 10 to connect to the Non3GPP network 14, and notifies the CMIP connection unit 101 of the completion.
  • This connection processing includes authentication with the Non3GPP network 14 and assignment of an IP address.
  • the Non3GPP network connection processing unit 102 refers to the PDN connection information holding unit 104 and is shown to simultaneously connect from the Non3GPP network 14 in the PDN connections Conn1 and Conn2 established on the 3GPP network 11. It is confirmed whether there is a PDN connection (Conn1). When there is a corresponding PDN connection Conn1, notification of connection using a CMIP-based method is made in the connection procedure to the Non3GPP network 14 side.
  • the Non3GPP network connection processing unit 102 acquires the prefix P3, which is a local prefix for generating CoA, from the AGW 15, and instructs the PDN connection information holding unit 104 to hold the address generated using the prefix P3 as CoA.
  • the AGW 15 is an ePDG
  • the Non3GPP network connection processing unit 102 establishes an IPSec tunnel for the ePDG after connecting to the access network (Non3GPP network) and acquiring a local address. While establishing an IPSec tunnel with the ePDG, a notification is made that a connection is made using a CMIP-based method.
  • the Non3GPP network connection processing unit 102 acquires the prefix P3, which is a CoA generation prefix, from the ePDG, and instructs the PDN connection information holding unit 104 to hold the address generated using the prefix P3 as CoA.
  • the CMIP connection unit 101 refers to the PDN connection information holding unit 104, and if there is a PDN connection Conn2 that requires simultaneous connection, associates the CoA with the HoA 2 to the P-GW 13 to which the PDN connection Conn 2 is connected. For this purpose, a BU message is transmitted.
  • a BU message is transmitted.
  • the prefix P1, HoA1, or EPS bearer ID indicating the PDN connection Conn1 may be explicitly included in the BU message.
  • the BU message may be included in another BU message and transmitted.
  • HoA1 in the field for setting the CoA of the BU message, it may indicate that the advertisement for the prefix P1 is requested.
  • the BU message for associating CoA with HoA2 may be transmitted.
  • the prefix P1 is advertised based on the PMIP connection request notified by the SA generation unit 105 described above.
  • the IKEv2 message transmitted from the Non3GPP network connection processing unit 102 to the ePDG may be used as means for requesting the advertisement of the prefix P1 related to the PDN connection Conn1.
  • Conn1 is notified that PMIP (or GTP) is used. This means may be used in place of the IKEv2 message including the PMIP connection request transmitted from the SA generation unit 105 to the P-GW 13.
  • FIG. 4 is an example of an IKEv2 message 20 including a PMIP connection request.
  • the IKEv2 message 20 includes a PMIP connection request indicating that a handover connection is made to the PDN connection Conn1 by a PMIP-based method.
  • the PMIP connection request includes at least one of EPS bearer ID, APN, HoA1, and prefix P1 as information for specifying the PDN connection Conn1.
  • APN is used as information for specifying these PDN connections.
  • an EPS bearer ID, HoA1, prefix P1, etc. are included.
  • the field indicated by IKE_SA_INIT / IKE_AUTH in FIG. 4 is replaced with a mobility header indicating a BU message.
  • the PDN connection information holding unit 104 holds information regarding the PDN connection established on the 3GPP network 11 and the Non3GPP network 14.
  • the PDN connection information further includes the non 3GPP network 14 determined by the simultaneous connection determination unit 103. It also includes information indicating whether or not to make a simultaneous connection.
  • the PDN connection information is included in a UE context (UEtextcontext) held by the UE 10.
  • FIG. 5 is a block diagram showing an example of the configuration of the P-GW 13.
  • the P-GW 13 includes an interface 130, a location information registration processing unit 131, an SA generation unit 132, and a PDN connection information holding unit 133.
  • the location information registration processing unit 131 receives a location information registration message (GTP message or PBU message) from the S-GW 12 and generates location information regarding the UE 10.
  • the location information of the UE 10 is information (binding cache) in which the address of the S-GW 12 is associated as CoA with respect to the home prefix P1, P2 / home address (HoA1, HoA2). (BC)).
  • the location information of the UE 10 includes information (binding cache) in which the CoA of the UE 10 is associated with the home prefix P1, P2 / home address (HoA1, HoA2). Become.
  • the location information registration processing unit 131 refers to the PDN connection information holding unit 133 when receiving the BU message from the UE 10, and includes the PDN connection information (Conn1) corresponding to the HoA1 included in the BU message.
  • PDN connection information Conn1
  • the BA message to be transmitted to the UE 10 is transmitted including the prefix P1.
  • the BU message received from UE10 contains only the information regarding HoA2 (Conn2), you may interpret that the positional information registration process part 131 is requesting PMIP connection regarding HoA1 (Conn1).
  • the SA generation unit 132 performs a process of generating an SA with the UE 10 in accordance with the IKEv2 protocol started by the UE 10. If the prefix P1, HoA1, or EPS bearer ID is included as information regarding the PDN connection Conn1 to be handed over from the 3GPP network 11 to the Non3GPP network 14 in the IKEv2 message, the PDN of the UE 10 corresponding to those values
  • the connection Conn1 is specified, and information indicating that it is a PDN connection that is handed over from the 3GPP network 11 to the Non3GPP network 14 and PMIP-connected from the Non3GPP network 14 side is added to the PDN connection information.
  • the PDN connection information holding unit 133 holds information related to the PDN connection established with the UE 10 on the 3GPP network 11 and the Non3GPP network 14.
  • information on the PDN connections Conn 1 and Conn 2 is held, and each PDN connection information further includes the non 3GPP network 14 determined by the simultaneous connection determination unit 103. Also included is information indicating whether to hand over to (using a PMIP connection) or to connect simultaneously from the Non3GPP network 14 (using a CMIP connection). Further, when the UE 10 is further connected to the Non3GPP network 14, information on the PDN connection established on the Non3GPP network 14 is also held.
  • the PDN connection information is included in the P-GW context (P-GW context) held by the P-GW 13.
  • FIG. 6 is a block diagram illustrating an example of the configuration of the AGW 15.
  • the AGW 15 includes a UE connection processing unit 151, a UE information holding unit 152, and an RA generation unit 153.
  • the UE connection processing unit 151 performs a procedure when the UE 10 establishes a connection with the Non3GPP network 14 side.
  • the procedure includes authentication of the UE 10, layer 2 connection, layer 3 connection, and the like.
  • the message requesting the layer 3 connection received from the UE 10 includes the protocol type (CMIP / PMIP) used in the Non3GPP network 14.
  • CMIP protocol type
  • the RA generation unit 153 is instructed to advertise the prefix P3 to the UE 10 as a local prefix for generating CoA.
  • the PMIP tunnel generation process is started for the P-GW 13.
  • the prefix local prefix, prefix P3
  • IKEv2 IKEv2
  • the UE 10 uses a network-based protocol for a specific PDN connection in advance. By notifying that it is used, the PDN connection established in the 3GPP network 11 can be handed over to the Non3GPP network 14 and a PDN connection by PMIP can be established.
  • a PDN connection obtained by handing over a PDN connection established on the 3GPP network 11 to the Non3GPP network 14 is assumed as a PDN connection using a PMIP connection on the Non3GPP network 14. However, it may be a PDN connection newly established on the Non3GPP network 14.
  • FIG. 7 shows a network configuration diagram according to the second embodiment of the present invention, in which a MAG 17 serving as a proxy node for generating the PDN connection Conn1 is added to the Non3GPP network 14.
  • the UE 10 includes a 3GPP interface (cellular interface) IF1 and a WLAN interface IF2 as a Non3GPP interface.
  • the Non3GPP interface may be a WiMAX interface, an HRPD interface, or the like.
  • the 3GPP interface IF1 is connected to the 3GPP network 11 side, establishes two PDN connections Conn1 and Conn2 with the P-GW 13 via the S-GW 12, and is assigned different prefixes P1 and P2, respectively. .
  • the PDN connection Conn1 is switched to the connection from the Non3GPP network 14 side (handover), and the PDN connection Conn2 is connected to the 3GPP network 11 P-GW13 In contrast, it has a policy of connection (simultaneous connection) from the Non3GPP network 14 side.
  • FIG. 8 shows a sequence when the UE 10 is connected to the Non-3GPP network 14 when the UE 10 is connected to the 3GPP network 11 in the second embodiment.
  • the UE 10 connects to the Non3GPP network 14, (2) When the Non3GPP network 14 is discovered, (3) Perform access authentication with AGW15, (4) Perform layer 3 connection with AGW15 and receive local prefix assignment, (5) Generate / acquire CoA. In (4), the CoA itself may be acquired from the AGW 15.
  • the UE 10 When connecting to the AGW 15, the UE 10 detects that there is a PDN connection Conn 2 that is simultaneously connected from both the 3GPP network 11 and the Non3GPP network 14 among the PDN connections generated on the connection to the 3GPP network 11. Declare to use the CMIP based method. As a result, the prefix P3, which is a local prefix for generating CoA, is acquired from the AGW 15. (6) The UE 10 generates an SA (Security Association) necessary for establishing a PDN connection from the Non3GPP network 14 by a CMIP-based method with the PGW 13 using IKEv2. Furthermore, the UE 10 transmits a BU message to the P-GW 13 in order to register the address generated from the prefix P3 as the CoA for the home address (HoA2) of the PDN connection Conn2.
  • SA Security Association
  • the UE 10 detects that there is a PDN connection Conn1 to be handed over from the 3GPP network 11 to the Non3GPP network 14 in the PDN connection generated on the connection to the 3GPP network 11, and the Non3GPP The address of the MAG 17 existing in the network 14 is acquired.
  • This MAG 17 is an MAG that creates an IP tunnel T1b with the UE 10 in (11) and provides a PMIP connection (PMIP tunnel T1a) with the P-GW 13 via the IP tunnel T1b.
  • PMIP tunnel T1a PMIP tunnel T1a
  • As a method for acquiring the address of MAG17 there is a method of requesting / acquiring using DNS (Domain Name System) after acquiring CoA as in (5) (7) (8).
  • the request / acquisition may be performed using DNS from the 3GPP interface IF1. Further, it may be requested / acquired in the connection procedure (3), (4) to the Non3GPP network 14 or in the IKEv2 or BU / BA message (6) performed with the P-GW 13.
  • DNS FQDN (Fully Qualified Domain Name) indicating MAG 17 that provides a PMIP connection by the IP tunnel T1b is used as information indicating a requested node.
  • the EPS bearer ID or PCID (PDN connection ID) of the PDN connection Conn1 may be included in the IKEv2 message or the BU / BA message as information indicating that the address of the MAG 17 is requested.
  • the UE 10 that has acquired the address of the MAG 17 requests the MAG 17 to generate the IP tunnel T1b and the PMIP connection to the P-GW 13 (IP tunnel generation request & PMIP connection request message). Send.
  • the UE 10 notifies the handover of the PDN connection Conn1 to the Non3GPP network 14 side (handover connection) by including the HoA1 and prefix P1 used for the PDN connection Conn1 on the 3GPP network 11 in this message. Requests continued use of HoA1 and prefix P1.
  • a handover indicator (Attach Type or Handover Indicator)
  • an EPS bearer ID or PCID of Conn1 may be used as information indicating handover connection.
  • the address on the UE 10 side of the IP tunnel T1b established between the UE 10 and the MAG 17 is the CoA generated from the prefix P3.
  • the UE 10 includes an APN (Access Point Name) corresponding to the PDN connection Conn1 in this message.
  • the APN is information indicating a PDN (Packet Data Network) to which the PDN connection Conn1 is connected, and is used as information for specifying the P-GW 13 to which the UE 10 desires to connect.
  • the MAG 17 acquires the address of the P-GW 13 from the DNS server 18 using the FQDN configured from the APN, and specifies the P-GW 13 that establishes the PMIP connection (PMIP tunnel T1a).
  • the UE 10 When the UE 10 has already obtained the address or FQDN of the P-GW 13 when simultaneously connecting the PDN connection Conn 2 from the Non 3GPP network 14 side, the UE 10 includes such information in this message instead of the APN. May be.
  • the MAG 17 acquires the address of the P-GW 13 using the DNS. That is, the IP tunnel creation request & PMIP connection request message from the UE 10 is addressed to the address of the MAG 17, and the message includes information on the P-GW 13 (PDN) to which the UE 10 wants to connect and 3GPP for the P-GW 13.
  • Information (HoA1, P1 or Handover Indicator) indicating that the PDN connection Conn1 established on the network 11 is to be handed over (handover connection) is included.
  • the PMIP connection request message a message of the same type as the message transmitted to the AGW 15 in order to establish the layer 3 connection in (4) may be used, or a new message may be used.
  • information necessary for requesting a PMIP connection request is included in the payload ( For example, it may be included as Identification_Payload or Configuration_Payload).
  • the MAG 17 Upon receiving this PMIP connection request message, the MAG 17 requests that the PDN connection Conn1 established with the P-GW 13 is handed over to the P-GW 13 to which the UE 10 requests connection. To send a PBU message.
  • This PBU message also includes information (HoA1, prefix P1, EPS bearer ID or Handover Indicator) indicating that it is a handover connection of the PDN connection Conn1, and it is to the P-GW 13 that it is a handover connection of the PDN connection Conn1. Be notified.
  • the P-GW 13 processes the PBU message received from the MAG 17, updates the binding cache (BC) necessary for handing over the PDN connection Conn1, and updates policy information with the policy server (PCRF).
  • BC binding cache
  • PCRF policy information with the policy server
  • the PBA message includes the prefix P1 or HoA1 used by the UE 10 in the 3GPP network 11 for the PDN connection Conn1, and the MAG 17 that has received the PBA message receives the handover connection (PMIP tunnel T1a to the PDN connection Conn1). Recognize that construction is complete.
  • the MAG 17 notifies the UE 10 of the prefix P1 or HoA1 of the UE 10 included in the PBA message using the IP tunnel T1b.
  • An RA (Router Advertisement) message can be used as a message used for notification, but is not limited to this.
  • the UE 10 that receives the prefix P1 or HoA1 from the MAG 17 recognizes that the PDN connection with the P-GW 13 is established and the handover connection of the PDN connection Conn1 is completed, and starts communication using the HoA1 via the IP tunnel T1b. .
  • the UE 10 can establish the PDN connection to be handed over using the PMIP-based method.
  • the UE 10 is implemented after connecting the SA (Security Association) necessary for establishing the PDN connection from the Non3GPP network 14 by the CMIP-based method to the Non3GPP network 14 side.
  • SA Security Association
  • SA is unnecessary between UE10 and MAG17.
  • FIG. 9 is a block diagram illustrating a configuration of the UE 10 according to the second embodiment
  • FIG. 10 is a flowchart illustrating a Non3GPP network connection process of the UE 10.
  • the UE 10 includes interfaces IF1 and IF2, a simultaneous connection determination unit 103, a Non3GPP network connection processing unit 102, a CMIP connection unit (SA generation unit) 101 (105), a PDN connection information holding unit 104, and a packet transfer unit 106.
  • SA generation unit CMIP connection unit
  • PDN connection information holding unit 104 a packet transfer unit 106.
  • a DNS processing unit 107 and a PMIP connection unit 108 are examples of the PMIP connection unit 108.
  • the simultaneous connection determination unit 103 refers to the PDN connection information holding unit 104, and among the PDN connections Conn1 and Conn2 established on the 3GPP network 11, a PDN connection (Conn2) that needs to be simultaneously connected from the Non3GPP network 14 as well. ).
  • a PDN connection Conn2
  • information indicating that the PDN connection requires simultaneous connection is added to the PDN connection information holding unit 104 in the corresponding PDN connection information.
  • a criterion for determining whether or not simultaneous connection is required for example, it can be determined based on the type and state of a flow when transmission / reception is performed through a PDN connection established on the 3GPP interface IF1.
  • a PDN connection that flows a communication flow requiring a large bandwidth a PDN connection whose resource type is Non-GBR (Non-Guaranteed bitrate resources), and the like are selected as targets for simultaneous connection.
  • the determination may be based on the QCI value or priority, not the resource type.
  • the information which shows whether a specific flow requires simultaneous connection may be contained in the routing rule which UE hold
  • the PDN connection that is flowing through the flow is selected as the PDN connection to be simultaneously connected. Further, information regarding this routing rule may be obtained from an ANDSF (Access Network Discovery and Selection Function) server.
  • ANDSF Access Network Discovery and Selection Function
  • the Non3GPP network connection processing unit 102 performs processing necessary for the Non3GPP interface IF2 of the UE 10 to connect to the Non3GPP network 14. This connection processing includes authentication with the Non3GPP network 14 and assignment of an IP address. As shown in FIG. 10, when connecting to the Non3GPP network 14, the Non3GPP network connection processing unit 102 refers to the PDN connection information holding unit 104, and establishes the PDN connections Conn 1 and Conn 2 established on the 3GPP network 11. It is confirmed whether or not there is a PDN connection (Conn2) indicated to be simultaneously connected from the Non3GPP network 14 side (steps S1 and S2).
  • step S3 If there is a corresponding PDN connection Conn2, it is determined that the CMIP-based method is used in the connection procedure to the Non3GPP network 14, and the CMIP-based method is used in the connection procedure to the Non3GPP network 14. It is requested to connect (step S3).
  • the Non3GPP network connection processing unit 102 acquires the prefix P3, which is a local prefix for CoA generation, from the AGW 15, and sends it to the PDN connection information holding unit 104 so as to hold the address generated using the prefix P3 as CoA. Instruct.
  • the Non3GPP network connection processing unit 102 further requests the CMIP connection unit (SA generation unit) 101 (105) to establish a CMIP connection with the P-GW 13 that manages the PDN connection Conn2.
  • SA generation unit CMIP connection unit
  • the Non3GPP network connection processing unit 102 refers to the PDN connection information holding unit 104 when connecting to the Non3GPP network 14, and establishes the PDN connection established on the 3GPP network 11. It is confirmed whether there is a PDN connection (Conn1) to be handed over to the Non3GPP network 14 in Conn1 and Conn2 (step S4). If there is a corresponding PDN connection Conn1, the PMIP connection unit 108 is instructed to acquire the address of the MAG 17 (step S5).
  • step S6 If the address of the MAG 17 can be acquired (YES in step S6), the 3GPP network 11 In order to hand over the PDN connection Conn1, an IP tunnel is generated with the MAG 17, and a request is made to establish a PMIP connection via the IP tunnel (step S7).
  • the Non3GPP network connection processing unit 102 detects a PDN connection (Conn1) to be handed over to the Non3GPP network 14, it determines that a CMIP-based method is used in the connection procedure to the Non3GPP network 14, In the connection procedure (3) (4) to the Non3GPP network 14, an MAG address for IP connection may be requested. Furthermore, an instruction to acquire the address of MAG 17 may be given to the CMIP connection unit.
  • the CMIP connection unit (SA generation unit) 101 receives an instruction from the Non3GPP network connection processing unit 102 and refers to the PDN connection information holding unit 104 to obtain information on the PDN connection Conn2 that requires simultaneous connection. get.
  • the address of the P-GW 13 can be acquired while connected to the 3GPP network 11, or an FQDN is generated using the APN included in the PDN connection information, and the address of the P-GW 13 corresponding to the FQDN is DNS It can also be acquired from the server 18. If the SA has not yet been established for the P-GW 13 that is the connection destination of the PDN connection Conn2, the generation of the SA is started.
  • the CMIP connection unit receives an instruction from the Non3GPP network connection processing unit 102, and generates an SA with the P-GW 13 for information requesting the address of the MAG 17 (such as a new attribute (Attribute) or an identifier of Conn1). It may be included in the IKEv2 message that is transmitted at the time.
  • an instruction from the Non3GPP network connection processing unit 102, and generates an SA with the P-GW 13 for information requesting the address of the MAG 17 (such as a new attribute (Attribute) or an identifier of Conn1). It may be included in the IKEv2 message that is transmitted at the time.
  • the CMIP connection unit (SA generation unit) 101 (105) transmits a BU message for associating the CoA to the HoA 2 to the P-GW 13.
  • the CMIP connection unit (SA generation unit) 101 (105) does not hand over the PDN connection Conn2 established on the 3GPP network 11 in this BU message, but also from the Non3GPP network 14 side, the same P-GW13.
  • a BID for identifying a BC indicating a PDN connection Conn2 on the 3GPP network 11 side, together with a BID for identifying a BC corresponding to a PDN connection newly generated on the Non3GPP network 14 side, is included. , Indicating that the UE 10 is requesting simultaneous connection to the P-GW 13.
  • the BID indicating the PDN connection Conn2 on the 3GPP network 11 side is not included, it means that the connection is established only from the Non3GPP network 14 as in the conventional case, and if the BID is included, the 3GPP network 11 and It means establishing a connection from both network 14 Non3GPP.
  • a flag indicating simultaneous connection may be set in the BU message. By transmitting this message, two BCs are generated in the P-GW 13, and the UE 10 can be simultaneously connected from both the 3GPP network 11 side and the Non3GPP network 14 side. Note that the UE 10 can also generate an SA in advance on the 3GPP network 11 before connecting to the Non3GPP network 14.
  • the BC may be held by the CMIP connection unit (SA generation unit) 101 (105) or may be held by the PDN connection information holding unit 101.
  • the CMIP connection unit receives an instruction from the Non3GPP network connection processing unit 102 and includes information requesting the address of the MAG 17 (such as a new flag, an option, or an identifier of Conn1) in the BU message to be transmitted to the P-GW 13. Also good.
  • the PDN connection information holding unit 104 holds information related to the PDN connection established on the 3GPP network 11 and the Non3GPP network 14.
  • information on the PDN connections Conn1 and Conn2 is held, and each PDN connection information also includes information indicating whether or not simultaneous connection from the Non3GPP network 14 is performed. include.
  • information indicating simultaneous connection is held in the PDN connection Conn2, and information indicating handover connection is held in the PDN connection Conn1.
  • Other information included includes APN, P-GW 13 address, home prefixes P1 and P2, home addresses HoA1 and HoA2.
  • the PDN connection Conn1 is replaced with the PDN connection information connected from the Non3GPP network 14, and the PDN connection Conn2 is connected from both the 3GPP network 11 and the Non3GPP network. It is replaced with information indicating that Note that the PDN connection information is included in a UE context (UEtextcontext) held by the UE 10.
  • UE context UEtextcontext
  • the PMIP connection unit 108 receives an instruction from the Non3GPP network connection processing unit 102, refers to the PDN connection information holding unit 104, and performs handover to the Non3GPP network 14 among the PDN connections Conn1 and Conn2 established on the 3GPP network 11. Information on the PDN connection Conn1 is acquired. Then, in order to make the PDN connection Conn1 connect by PMIP, the DNS processing unit 107 is instructed to acquire an address of a MAG that can be connected using an IP tunnel. If the acquisition of the MAG 17 address has already been completed, there is no need to acquire it here.
  • the PMIP connection unit 108 that has acquired the address of the MAG 17 transmits a message requesting the generation of an IP tunnel and the PMIP connection to the P-GW 13 (hereinafter referred to as PMIP connection request message) to the MAG 17 (step in FIG. 10).
  • PMIP connection request message a message requesting the generation of an IP tunnel and the PMIP connection to the P-GW 13 (hereinafter referred to as PMIP connection request message) to the MAG 17 (step in FIG. 10).
  • PMIP connection request message a message requesting the generation of an IP tunnel and the PMIP connection to the P-GW 13
  • FIG. 11 shows a packet 30 including a PMIP connection request message 31.
  • the prefix P1 or HoA1 or EPS bearer used by the UE 10 in the PDN connection Conn1 is used as information indicating a handover connection.
  • ID or Handover Indicator 32 is included.
  • the PMIP connection request message 31 includes an APN 33 corresponding to the PDN connection Conn1.
  • the MAG 17 can acquire the address of the P-GW 13 that has constructed the PDN connection Conn1 to be handed over from the DNS server 18 by using the APN 33.
  • the PDN connection Conn2 is simultaneously connected from the Non3GPP network 14, when the address or FQDN of the P-GW 13 has already been acquired, such information may be included in this message instead of the APN 32.
  • the PMIP connection unit 108 receives a response message for the PMIP connection request message 31 transmitted to the MAG 17 from the MAG 17 and recognizes that the IP tunnel T1b is generated between the MAG 17 and the PMIP connection request message 31.
  • the end points of this IP tunnel T1b are the addresses of the CoA and MAG 17 of the UE 10.
  • the PMIP connection unit 108 performs the handover process to the Non3GPP network 14 related to the PDN connection Conn1. It recognizes that it has completed, and recognizes that communication using HoA1 is now possible.
  • an IPSec tunnel may be used between the UE 10 and the MAG 17, but the establishment of the SA may be omitted if the connection can be made as a Trusted-Non3GPP network.
  • the DNS processing unit 107 transmits a DNS query to the DNS server 18 for acquiring the address of the MAG 17 that can construct the IP tunnel T1b.
  • the address acquired from the DNS server 18 is passed to the PMIP connection unit 108.
  • the DNS query includes an FQDN generated based on the APN corresponding to Conn1.
  • the packet transfer unit 106 performs processing for transferring a packet addressed to a communication partner (CN) acquired from an upper layer.
  • CN communication partner
  • the transmission source address of the packet to be transferred is HoA2
  • the packet is encapsulated and transmitted to the P-GW 13 using the CMIP tunnel.
  • the source address is HoA1
  • it is encapsulated to MAG 17 and transmitted using an IP tunnel.
  • FIG. 12 is a block diagram showing the configuration of the MAG 17.
  • the MAG 17 includes an interface 170, a packet transfer unit 171, an IP tunnel generation processing unit 172, a PMIP connection processing unit 173, and a UE information holding unit 174.
  • the MAG may be ePDG.
  • the IP tunnel generation processing unit 172 processes the PMIP connection request message (including the IP tunnel generation request) received from the UE 10, and determines the CoA set in the source address of the message or the CoA included in the message.
  • An IP tunnel T1b as an end point is generated, the HoA1 of the UE 10 included in the message is acquired, and the UE information holding unit 174 is instructed to hold information on the IP tunnel T1b.
  • the UE 10 interprets that the handover of the PDN connection Conn1 is requested, and sends it to the PMIP connection processing unit 173. And instruct to start the PMIP connection (PMIP tunnel T1a) for establishing the PDN connection Conn1 related to HoA1.
  • the PMIP connection processing unit 173 receives an instruction from the IP tunnel generation processing unit 172, and transmits a PBU message for establishing the PMIP tunnel T1a to the P-GW 13.
  • This PBU message includes the prefix P1, HoA1, or EPS bearer ID notified from the UE 10 as information indicating the PDN connection Conn1 to be handed over, and further, in the field (Handover Indicator) indicating the type of connection, handoff A value indicating is set. By setting a value indicating handoff, it is notified that the PDN connection moves from the 3GPP network 11.
  • a value indicating initial connection is also set in the PBU message. If necessary, when receiving an IP tunnel generation request message from the UE 10, the UE 10 may be authenticated by inquiring of an HSS server or an AAA server (not shown).
  • the packet transfer unit 171 transfers the uplink packet transmitted from the UE 10 and the downlink packet reached to the UE 10. Since the uplink packet transmitted from the UE 10 using HoA1 is encapsulated to the MAG 17 by the IP tunnel T1b, it is decapsulated and an internal packet is obtained. In order to use the PMIP tunnel T1a, the internal packet is encapsulated to the P-GW 13 and transferred. On the other hand, since the downlink packet transferred from the P-GW 13 is encapsulated to the MAG 17 by the PMIP tunnel T1a, it is decapsulated and an internal packet is obtained. In order to use the IP tunnel T1b, the internal packet is encapsulated and transferred to the CoA of the UE 10.
  • the UE information holding unit 174 holds information related to the UE 10 that forms the IP tunnel T1b and establishes the PMIP connection.
  • the UE 10 can establish the PDN connection to be handed over using the PMIP-based method even when connected to the Non3GPP network 14 by the CMIP-based method in order to establish the PDN connection to be connected simultaneously. it can.
  • FIG. 13 is a flowchart for explaining processing of the UE 10 in the third embodiment, in particular, the processing of the Non3GPP network connection processing unit 102 (see FIG. 9).
  • the Non 3GPP network connection processing unit 102 starts processing in Step S 11 and refers to the PDN connection information holding unit 104, so that both the PDN connection for simultaneous connection and the PDN connection for handover connection are used. If there is any (YES in steps S12 and S13), the PDN connection is notified of whether to use PMIP or CMIP (step S16).
  • a notification method a message in the connection procedure to the Non3GPP network 14 can be used.
  • step S12 PMIP use is notified (step S14), but there is no need to notify for each PDN connection. If there is a PDN connection for simultaneous connection (YES in step S12), but there is no PDN connection for handover connection (NO in step S13), the use of CMIP is notified (step S15). Also in this case, it is not necessary to notify for each PDN connection.
  • the type of mobility management protocol to be notified when connected to the Non3GPP network 14 can be flexibly changed.
  • Each functional block used in the description of the above embodiment is typically realized as an LSI that is an integrated circuit. These may be individually made into one chip, or may be made into one chip so as to include a part or all of them.
  • the name used here is LSI, but it may also be called IC, system LSI, super LSI, or ultra LSI depending on the degree of integration.
  • the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible.
  • An FPGA Field Programmable Gate Array
  • a reconfigurable processor that can reconfigure the connection and setting of circuit cells inside the LSI may be used.
  • integrated circuit technology comes out to replace LSI's as a result of the advancement of semiconductor technology or a derivative other technology, it is naturally also possible to carry out function block integration using this technology. For example, biotechnology can be applied.
  • the present invention selects a network-based mobility management protocol when a second interface of a mobile node is connected to a second network from a state in which the first interface of the mobile node has a plurality of connections in the first network. This has the effect of reducing the processing load of the mobile node, and can be used when the first network is a 3GPP network and the second network is not a 3GPP network.
  • the present invention also provides that the second interface of the mobile node is changed from the state in which the first interface of the mobile node has a plurality of connections in the first network without increasing the processing load of the mobile node.
  • the network management or client-based mobility management protocol can be selected as the mobility management protocol type of each connection.
  • the first network is a 3GPP network and the second network is 3GPP. It can be used when not in a network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne une technique pour sélectionner un protocole de gestion de la mobilité basé sur le réseau lorsqu'une seconde interface d'un noeud mobile se connecte à un second réseau dans un état dans lequel une première interface du noeud mobile présente plusieurs connexions sur un premier réseau, réduisant de ce fait la charge de traitement du noeud mobile. Selon cette technique, lorsque l'interface (IF1) du noeud mobile MN (10) présente plusieurs connexions (Conn 1, Conn 2) sur un réseau 3GPP (11), le noeud mobile MN (10) donnes des instructions à une passerelle P-GW (13), qui est l'agent local du noeud mobile MN (10), de telle sorte que, lorsque l'interface (IF2) est connectée à un réseau non 3GPP (14) par un protocole de gestion de la mobilité basé sur le client, un protocole de gestion de la mobilité basé sur le réseau sera utilisé comme type de protocole de gestion de la mobilité pour la connexion (Conn 1) qui se connecte en même temps comme la connexion (Conn 2).
PCT/JP2010/003905 2009-06-15 2010-06-11 Procédé de sélection de protocole de gestion de la mobilité, système de sélection de protocole de gestion de la mobilité, nœud mobile, agent local, et nœud de serveur mandataire WO2010146815A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2009-142629 2009-06-15
JP2009142629 2009-06-15

Publications (1)

Publication Number Publication Date
WO2010146815A1 true WO2010146815A1 (fr) 2010-12-23

Family

ID=43356148

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2010/003905 WO2010146815A1 (fr) 2009-06-15 2010-06-11 Procédé de sélection de protocole de gestion de la mobilité, système de sélection de protocole de gestion de la mobilité, nœud mobile, agent local, et nœud de serveur mandataire

Country Status (1)

Country Link
WO (1) WO2010146815A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015093500A1 (fr) * 2013-12-20 2015-06-25 京セラ株式会社 Procédé de commande de la communication, dispositif passerelle et terminal utilisateur
JP2015532058A (ja) * 2012-09-14 2015-11-05 中興通訊股▲分▼有限公司 アクセスネットワークの位置情報を通知する方法及びシステム

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008099802A1 (fr) * 2007-02-13 2008-08-21 Nec Corporation Système de gestion de terminal mobile, dispositif de réseau, et procédé de commande de fonctionnement de terminal mobile utilisé pour ceux-ci
WO2009057296A1 (fr) * 2007-11-02 2009-05-07 Panasonic Corporation Terminal mobile, nœud de réseau, et nœud de gestion de transfert de paquets

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008099802A1 (fr) * 2007-02-13 2008-08-21 Nec Corporation Système de gestion de terminal mobile, dispositif de réseau, et procédé de commande de fonctionnement de terminal mobile utilisé pour ceux-ci
WO2009057296A1 (fr) * 2007-11-02 2009-05-07 Panasonic Corporation Terminal mobile, nœud de réseau, et nœud de gestion de transfert de paquets

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Architecture enhancements for non-3GPP accesses (Release 9), 3GPP TS 23.402 V9.0.0", 3RD GENERATION PARTNERSHIP PROJECT; TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS, March 2009 (2009-03-01) *
"Multi access PDN connectivity and IP flow mobility(Release 9), 3GPP TR 23.861 V1.1.1", 3RD GENERATION PARTNERSHIP PROJECT; TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS, April 2009 (2009-04-01) *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015532058A (ja) * 2012-09-14 2015-11-05 中興通訊股▲分▼有限公司 アクセスネットワークの位置情報を通知する方法及びシステム
US9854555B2 (en) 2012-09-14 2017-12-26 Zte Corporation Method and system for notifying access network location information
WO2015093500A1 (fr) * 2013-12-20 2015-06-25 京セラ株式会社 Procédé de commande de la communication, dispositif passerelle et terminal utilisateur
JPWO2015093500A1 (ja) * 2013-12-20 2017-03-16 京セラ株式会社 通信制御方法、ゲートウェイ装置及びユーザ端末
EP3086599A4 (fr) * 2013-12-20 2017-06-07 Kyocera Corporation Procédé de commande de la communication, dispositif passerelle et terminal utilisateur
US10277300B2 (en) 2013-12-20 2019-04-30 Kyocera Corporation Communication control method, gateway apparatus, and user terminal

Similar Documents

Publication Publication Date Title
US9844082B1 (en) Method and apparatus for supporting multiple connections in 3GPP systems
KR101227455B1 (ko) 핸드오버 동작에서 자원 관리를 위한 방법 및 장치
EP2353271B1 (fr) Établissement sécurisé d'un tunnel lors de l' attachement ou passage à un réseau d'accès
US8457635B2 (en) Non-3GPP to 3GPP network handover optimizations
US8891432B2 (en) Routing method, routing system, mobile node, home agent, and home base station
US8780800B2 (en) Optimized home link detection
US20110103260A1 (en) Binding cache creating method, binding cache creating system, home agent, and mobile node
US20120063428A1 (en) Interface Switching System, Mobile Node, Proxy Node, and Mobile Management Node
WO2011001628A1 (fr) Procédé de gestion de connexion, système de gestion de connexion, terminal mobile, passerelle de données en paquets et passerelle de gestion mobile
WO2009116246A1 (fr) Procédé de communication, système de communication, nœud mobile, routeur d'accès
WO2010073620A1 (fr) Procédé de transfert et terminal mobile et agent domestique utilisés dans ledit procédé
US9148826B2 (en) Handover method and mobile terminal and home agent used in the method
WO2010052919A1 (fr) Procede de transfert, terminal mobile et agent local mis en oeuvre dans ce procede
WO2010146815A1 (fr) Procédé de sélection de protocole de gestion de la mobilité, système de sélection de protocole de gestion de la mobilité, nœud mobile, agent local, et nœud de serveur mandataire
JP2006229831A (ja) 異種網間接続切替方法及び異種網間接続システム
WO2016163411A1 (fr) Dispositif de terminal, pgw et twag
WO2016163410A1 (fr) DISPOSITIF DE TERMINAL, PASSERELLE D'ACCÈS SANS FIL DE CONFIANCE (TWAG), PASSERELLE DE DONNÉES DE PAQUET ÉVOLUÉ (ePDG) ET PASSERELLE DE PAQUET (PGW)
JPWO2016190359A1 (ja) 端末装置及びｐｃｒｆ
WO2010010693A1 (fr) Procédé et système de transfert vertical, agent local et noeud mobile

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10789198

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10789198

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP