JP5685161B2 - Network architecture, local mobility anchor, and mobility anchor gateway - Google Patents

Description

  The present invention relates generally to wireless communications, and more specifically to a network architecture for supporting IP flow mobility based on Proxy Mobile Internet Protocol Version 6 (PMIPv6), a local mobility anchor, and It relates to mobility anchor gateway.

1.1 Significance of IP Flow Mobility In recent years, mobile data traffic has increased rapidly due to the rapid penetration of mobile terminals for the Internet (for example, smartphones, tablet computers, laptops, netbooks, etc.). In addition, as new mobile broadband services emerge and spread more and more, mobile data traffic forms are very diversified according to application requirements. For example, if there is an application (for example, video streaming, file transfer, etc.) that requires a large amount of data traffic for a long period of time in one session, a short period (for example, online news viewing, electronic (Send mail etc.) Some are necessary. On the other hand, there are applications that have high signaling load even with little data traffic (eg, location-based services such as navigation, push technology-based services such as recent social networking, recent instant messaging, etc.).
With this trend, mobile network operators face significant challenges to support emerging mobile services and meet new user demands.

  The most important issue is how to deal with the explosion of mobile data that needs to be resolved urgently. In order to provide a stable wireless access environment and a stable mobile service, for example, an upgrade from a 3G (3rd generation) system to a 4G (4th generation) or a system exceeding 4G, or a base station or a router, etc. Expanding traffic processing capacity by improving mobile network systems, such as the deployment of additional devices, is an important issue to consider. However, although these solutions are certainly essential for mobile network operators, their deployment requires a large amount of investment and takes a long time, which is a burden on the operators.

  On the other hand, various wireless network systems such as W-CDMA (Wideband Code Division Multiple Access), HSPA (High Speed Packet Access), LTE (Long Term Evolution), WiFi, and WiMAX (Worldwide Interoperability for Microwave Access) are constantly evolving. As a result, wireless service areas provided by different wireless access technologies overlap each other. In addition, many mobile terminal devices are equipped with multiple radio interfaces that support different radio access technologies, typically 3G and WiFi. In a heterogeneous network environment, traffic offloading using complementary wireless access technology is a more effective approach to solving the mobile data explosion problem. By using a plurality of radio access technologies, it becomes possible to distribute the traffic load of the radio network, optimally use radio resources, and provide opportunities to connect to various radio networks according to user preferences.

  As heterogeneous network environments are realized and user requests become more diverse, mobile users can only move seamlessly between different radio interfaces of selected IP packet flows (IP flows). Instead, it may be desirable to have simultaneous access to multiple wireless networks. In order to support new user requirements, the Internet Engineering Task Force (IETF) has developed an IP flow mobility technology that can divide IP flows into multiple links according to flow requirements and user preferences. We are developing.

  IP flow mobility is a key technology for improving user experience as well as seamless mobile data offload. For example, a mobile device has two wireless interfaces compatible with two wireless access technologies (for example, 3G and WiFi), and two IP flows used for two purposes such as VoIP streaming and video streaming are 3G networks. And a mobile device. When mobile devices move to areas where both 3G and WiFi are available (eg offices, homes, hotspots, etc.), users will ensure seamless connectivity and guaranteed quality of service (QoS). You may want to maintain existing connections for both VoIP streaming and video streaming in 3G networks. Alternatively, the user may wish to transfer (move) only the video streaming flow from the 3G network to the WiFi network and enjoy the benefits of the best effort network service at low cost.

1.2 IP Mobility Management A mobility management protocol is required to maintain session connectivity without interruption during IP flow movement. Such protocols can be classified as host-based mobility management protocols or network-based mobility management protocols.

1.2.1 Host-based IP Mobility Management Mobile IPv6 (MIPv6) described in RFC 3775 (Non-Patent Document 1) and Dual Stack Mobile IPv6 (DSMIPv6) described in RFC 5555 (Non-Patent Document 2) are interrupted while moving. A host-based mobility management protocol for maintaining session connectivity without. The MIPv6 or DSMIPv6 protocol allows a mobile node to manage its mobility by exchanging signaling messages (eg, binding update message and binding confirmation message) with its home agent (HA). Since MIPv6 supports only one interface for transmitting and receiving packets, the mobile node can bind only one mobile node's care-of address (CoA) with the mobile node's home address at a time.

  RFC5648 (Non-Patent Document 3) proposes an extension of Mobile IPv6, in which a mobile node registers a plurality of care-of addresses in one home address and creates a plurality of binding cache entries. it can. Specifically, in RFC5648, multiple Care of Address Registration (MCoA) has been proposed and registered by a mobile node using a new binding identification number (BID (binding identification) number). Identify multiple bindings. Each binding is a combination of a care-of address and a home address. In MCoA, a mobile node including a plurality of radio interfaces can transmit and receive packets using the plurality of radio interfaces while utilizing the session persistence provided by Mobile IPv6. Can be used to bind multiple care-of addresses to the home address. When the care-of address of the home address is registered by the mobile node, the home agent stores a plurality of binding cache entries by creating individual bindings for the BID.

  RFC 6089 (Non-Patent Document 4) proposes further extension of MIPv6, DSMIPv6 and NEMO (Network Mobility) protocols. RFC 6089 proposes host-based IP flow mobility management, which allows mobile nodes to move (re-create) selected IP flows from one radio technology to a different radio technology without breaking session persistence. Association). That is, the mobile node can associate some flows with one radio interface and other flows with another radio interface. More specifically, this host-based IP flow mobility management provides a flow binding update scheme that binds a specific flow with one or more different CoAs (ie, one or more different BIDs) that use the same home address. .

  An IP flow (that is, an IP packet flow) means a series of IP packets used for, for example, HTTP (Hypertext Transfer Protocol), video, VoIP, and the like. In RFC 6089, an IP flow is defined as a set of IP packets that conform to a traffic selector. The traffic selector is information including one or more parameters (for example, a source IP address, a destination IP address, a source port number, a destination port number and a transport protocol number) used for classifying packets. According to RFC 6089, each flow binding is uniquely identified by a flow identifier (FID) and consists of a traffic selector and one or more binding identifiers (BID). When the IP packet matches the traffic selector, a copy of the IP packet is forwarded to each of a plurality of care-of addresses associated with a plurality of BIDs associated with the traffic selector in flow binding. A mobile node may move (reassociate) a particular flow to one of multiple interfaces based on local policy, link characteristics, the type of application currently running, or user preference. it can. This movement is made possible by transmitting a binding update message indicating information necessary for establishing flow binding, for example, BID, FID, traffic selector and the like.

  However, in any host-based IP flow mobility management, whenever a mobile node moves to another access network, it must perform an exchange of signaling messages with its own HA, and all mobile nodes Must handle the mobility protocol stack. For these reasons, host-based IP flow mobility management has problems such as high power consumption, high consumption of radio resources by using layer 3 signaling over a radio link, and high volume tunneling between a mobile node and its HA. It is accompanied.

1.2.2 Network-based IP mobility management In contrast, in a network-based mobility support scheme, the mobile node (MN) does not need to handle a large amount of mobility protocol stack, and any mobility-related Signaling also need not be exchanged with the network. The Network-based Localized Mobility Management (NETLMMM) IETF Working Group is responsible for the Proxy Mobile IPv6 Protocol (RFIPv6 described in RFC 5213) for network-based mobility support schemes. ) Was standardized. PMIPv6 performs mobility-related signaling and handles mobility management as a proxy for each mobile node to local mobility anchor (LMA) and mobile access gateway (MAG) A special mobility agent in the network including is proposed. The LMA performs HA operation (that is, acts as a home agent) for maintaining the binding information defined in RFC 5213 for each mobile node, and the home network prefix (HNP) of each mobile node. Topological anchor point for The MAG is an access router that manages mobility related signaling on behalf of each mobile node connected to its access link. The MAG is responsible for tracking the movement of each mobile node to and from the access link and signaling to the mobile node's local mobility anchor.

  The basic operation of the PMIPv6 protocol is as follows. When the MN connects to the MAG, the MAG obtains the MN profile including the MN identifier. The MAG then sends a proxy binding update (PBU) message to the LMA for the purpose of updating or registering the current connection point of the MN. When the LMA receives the PBU message, the LMA updates or creates a binding cache entry and establishes a bidirectional tunnel between the LMA and the MAG for the MN's HNP. Then, the LMA transmits a proxy binding acknowledgement (PBA) message including the MN's HNP to the MAG. The MAG emulates the access link to the MN's home network by sending a Router Advertisement (RA) message containing the MN's HNP to the MN. Therefore, the MN always believes that it is in the home network.

  The network-based mobility management approach defined in PMIPv6 is better suited to support MN mobility because it does not exchange mobility-related signaling messages over the radio link. Thus, network-based mobility management can reliably reduce power consumption, signaling costs, and handoff delay compared to host-based mobility management schemes.

1.2.3 Extensions to network-based IP mobility management The PMIPv6 basic specification (RFC 5213) defines additional options that can be used in PBU and PBA messages exchanged between LMA and MAG. This option includes a handoff indicator (HI) option, an access technology type (ATT) option, and a mobile node link layer ID (to enable multi-homing and vertical handover of the mobile node). MN-LL-ID: mobile node link-layer identification) option.

  Nevertheless, the PMIPv6 basic specification does not fully support the use of multiple radio interfaces in mobile nodes due to some limitations. If a mobile node connects to the proxy Mobile IPv6 domain via multiple radio interfaces simultaneously, a set of home network prefixes are assigned to each of the interfaces, and the home network assigned to an interface All prefixes are managed by the LMA under one mobility session. For example, home network prefixes P1 and P2 assigned to interface I1 are managed in one mobility session, and prefixes P3, P4 and P5 assigned to interface I2 of the mobile node are managed in different mobility sessions. This is because in the PMIPv6 basic specification, the LMA can only manage one set of HNPs at a time for the MN, and thus the LMA can only assign one set of HNPs to one interface of the MN at a time. Means no. The PMIPv6 basic specification does not specify in detail how the LMA or MAG can operate when a new set of home network prefixes needs to be assigned to the MN. Furthermore, when the MN performs a vertical handover between different wireless networks using a plurality of wireless interfaces, session persistence cannot be maintained. When trying to move (relocate) all IP flows from a previously used interface by the MN to a new interface, the previously assigned HNP should be changed to the newly assigned HNP. However, according to the PMIPv6 basic specification, the HNP assigned to the MN should not be changed while the session is maintained even if the MN moves to another network. For the reasons described above, network-based IP flow mobility management in the PMIPv6 basic specification is not suitable for simultaneous use of a plurality of radio interfaces or vertical handover in a mobile node.

  Furthermore, in IP flow mobility management, it is preferable to maintain some flows on a previously used radio access network and to allow other flows to be moved or transferred to another radio access network. In this scenario, to avoid session disconnection, the previously used HNP should be maintained during the flow movement while a new HNP should be assigned to the MN.

  In order to overcome the above-mentioned limitations and realize not only IP flow mobility but also vertical handover, as described in Non-Patent Document 6, the IETF Network-based Mobility Extensions (NETEXT: Working Group) A logical interface that supports the simultaneous use of multiple wireless interfaces was introduced. As shown in FIG. 1, the logical interface layer provides an interface view at the IP layer or higher layers by logically grouping different physical interfaces. Since the logical interface layer can hide the actual use of the physical interface (physical radio interface) from the IP layer, the logical interface allows multiple interfaces supporting vertical handover and IP flow mobility to be used sequentially and simultaneously. .

D. Johnson, D. Johnson, “Mobility Support in IPv6”, RFC 3775, the Internet Engineering Task Force, June 2004 H. H. Soliman, “Mobile IPv6 Support for Dual Stack Hosts and Routers”, RFC 5555, the Internet Engineering Task Force, June 2009 Moon R. R. Wakikawa, “Multiple Care-of Addresses Registration”, RFC 5648, the Internet Engineering Task Force, October 2009 G. Outside of G. Tsirtsis, “Flow Bindings in Mobile IPv6 and Network Mobility (NEMO) Basic Support”, RFC 6089, Internet Technical Standards Committee ( the Internet Engineering Task Force), January 2011 S. S. Gundavelli, “Proxy Mobile IPv6”, RFC 5213, the Internet Engineering Task Force, August 2008 T. T. et al. T. Melia, "Logical Interface Support for multi-mode IP Hosts", [online], the Internet Engineering Task Force, 2011 3 14th, Internet (URL: http://tools.ietf.org/html/draft-ietf-netext-logical-interface-support-02)

As described above, network-based mobility management with PMIPv6 can achieve many benefits with regard to power consumption, signaling costs, and handoff delay. Furthermore, the simultaneous use of multiple radio interfaces proposed by the IETF NEXTEXT Working Group is convenient in many respects.
Despite these advantages, PMIPv6 does not allow MNs to intervene in mobility related signaling exchanges performed between MAG and LMA, so network based IP flow mobility based on PMIPv6 There are limitations. Flows used between the MN and the network infrastructure according to the MN's user preferences regarding the wireless environment (eg, wireless signal strength, new detection of visited wireless communication network, etc.) or according to the wireless environment around the MN It is preferable that the routing policy rule can be dynamically changed.

  For example, a mobile node including a 3G interface and a WiFi interface has already established two or more IP flows, for example, a mobile IP TV flow (mobile IPTV flow) and a voice over IP flow (VoIP flow) for a 3G wireless network. Suppose that the MN visits a zone where both WiFi and 3G wireless technologies are available. Because WiFi technology offers better throughput and lower cost, MN users may wish to transfer all existing flows from 3G technology to WiFi technology. Alternatively, it may be desired to transfer only one or part of existing flows (eg, VoIP flows) to WiFi technology and maintain other flows (eg, mobile IPTV flows) with 3G technology. However, due to the lack of mobility-related signaling between the MN and the PMIPv6 network infrastructure, there is no solution to satisfy the user's wishes of the MN.

  Furthermore, the mobile node including the 3G interface and the WiFi interface has already established two or more IP flows to the 3G wireless network and another IP flow to the WiFi network, increasing the strength of the WiFi signal received by the MN. Assume that A MN user may wish to transfer one or a part of an existing flow from 3G technology to WiFi technology. Again, there is no solution to meet the wishes of MN users.

  In addition, the mobile node including the 3G interface and the WiFi interface has already established one IP flow to the 3G wireless network and another IP flow to the WiFi network, and the user is about to leave the WiFi available zone. It is assumed that the strength of the WiFi signal received by the MN has decreased, but the strength of the 3G signal received by the MN is sufficient. The MN user may wish to transfer an existing flow established with the WiFi interface from WiFi technology to 3G technology. Again, there is no solution to meet the wishes of MN users.

  Therefore, the present invention dynamically transfers one or more existing IP packet flows established in a mobile node from a currently used radio access technology to another radio access technology according to an instruction from the mobile node. Provide a network architecture that can do this.

  According to one aspect of the invention, for operating with the Proxy Mobile Internet Protocol Version 6 and communicating with the Internet via a first wireless communication network system using a first wireless access technology A first wireless interface; and a second wireless interface for communicating with the Internet via a second wireless communication network system using a second wireless access technology different from the first wireless access technology. A network architecture for communicating with at least one mobile node, wherein the mobile node is capable of communicating using the first radio access technology, and the mobile node is the first The second wireless access technology different from the wireless access technology of The second wireless communication network system capable of communicating using technology, and the first wireless communication network system connected to the first wireless communication network system via the Internet, and connected to the second wireless communication network system via the Internet. A local mobility anchor capable of communicating with a counterpart node of the mobile node, wherein the mobile node communicates with the counterpart node via the first wireless communication network system and the local mobility anchor A local mobility anchor that is capable of communicating with the counterparty node via the second wireless communication network system and the local mobility anchor; And the first radio A communication network system capable of operating as an access router of the mobile node and at least one established between the mobile node and the local mobility anchor via the first wireless communication network system And the second wireless communication network system can operate as an access router of the mobile node, and the mobile node can manage the IP packet flow of the mobile node. A second mobility anchor gateway capable of managing at least one IP packet flow established between the node and the local mobility anchor via the second wireless communication network system; , The first wireless communication network The first mobility anchor gateway of the network system has at least one IP packet flow routed through the first wireless communication network system between the first radio interface of the mobile node and the local mobility anchor. And the mobile node wishes to transfer at least one already established IP packet flow from the first radio access technology to the second radio access technology. A flow transfer instruction transmitted from a node, wherein the mobile node and the second radio interface of the mobile node used for the IP packet flow to be transferred are specified, and the second radio interface Whether is currently active A flow transfer instruction receiving unit capable of receiving a flow transfer instruction including current state information, and receiving the flow transfer instruction in the flow transfer instruction receiving unit, the second of the second wireless communication network system A flow transfer request transmission unit capable of transmitting a flow transfer request to the mobility anchor gateway, and the flow transfer request is used for the mobile node and the IP packet flow to be transferred Identifying the second radio interface of the mobile node to be transferred and the IP packet flow that the mobile node wishes to transfer from the first radio access technology to the second radio access technology; and Before in the flow transfer indication that the radio interface is not currently activated If the current state information indicates, it includes a first transmission instruction that instructs the second mobility anchor gateway to transmit a new connection request to the local mobility anchor, and If the current state information in the flow transfer indication indicates that a radio interface is currently active, the second mobility anchor to send a flow binding update request to the local mobility anchor The second mobility anchor gateway of the second wireless communication network system includes a proxy care-of address indicating the second mobility anchor gateway; From the first mobility anchor gateway A flow transfer request receiving unit capable of receiving the flow transfer request; and when the flow transfer request received by the flow transfer request receiving unit includes the first transmission instruction, the mobile node and the first A new connection request transmission unit capable of transmitting a new connection request specifying the proxy care-of address of the second mobility anchor gateway to the local mobility anchor, and the local mobility The anchor includes a new connection request receiving unit capable of receiving the new connection request from the second mobility anchor gateway, the second radio interface of the mobile node, and the local mobility anchor. Used for communication via the second wireless communication network system with the mobile station. A new home network prefix of the mobile node can be assigned to the mobile node, and when the new connection request is received by the new connection request receiving unit, the new home network prefix of the mobile node and A new connection request registration unit capable of registering a new binding with the proxy care-of address of the second mobility anchor gateway, a new home network prefix of the mobile node, and the second Based on the proxy care-of address of the second mobility anchor gateway, the mobile node's new Naho A new home network prefix transmission unit for transmitting a network network prefix to the second mobility anchor gateway, wherein the second mobility anchor gateway is a new home of the mobile node. A new home network prefix receiving unit capable of receiving a network prefix from the local mobility anchor, and a new home network prefix receiving unit of the mobile node at the new home network prefix receiving unit Upon receipt, the mobile node's specified in the flow transfer request to prompt establishment of a connection between the second radio interface of the mobile node and the second mobility anchor gateway. It is possible to confirm the establishment of a connection between an interface activation unit capable of activating a second radio interface and the second radio interface of the mobile node and the second mobility anchor gateway When the connection confirmation unit confirms the establishment of the connection, the flow transfer update request can be transmitted to the local mobility anchor, and the flow transfer including the second transmission instruction is performed. When the request is received by the flow transfer request receiving unit, the flow binding update request transmitting unit can further transmit the flow binding update request to the local mobility anchor, and the flow binding update request includes: The mobile node and the second mobility anchor game The proxy care-of address of the gateway and the mobile node wants to transfer from the first radio access technology to the second radio access technology specified in the flow transfer request from the first mobility anchor gateway A flow binding update request receiving unit capable of receiving the flow binding update request from the second mobility anchor gateway; and A flow binding registration capable of registering a binding between the new home network prefix of a node or an existing home network prefix and the IP packet flow specified by the flow binding update request. The existing home network prefix of the mobile node for establishing an existing bidirectional IP tunnel between the second mobility anchor gateway and the local mobility anchor A flow binding registration unit that is already associated with the proxy care-of address of the second mobility anchor gateway by the second mobility anchor gateway and the local mobility anchor; and the flow binding registration unit A flow binding completion report transmission unit capable of transmitting a flow binding completion message indicating that the registration of the binding is completed to the second mobility anchor gateway. The second mobility anchor gateway includes a flow binding completion report receiving unit capable of receiving the flow binding completion message from the local mobility anchor, and the second radio interface of the mobile node; Using the connection between the second mobility anchor gateway and the bidirectional IP tunnel between the second mobility anchor gateway and the local mobility anchor, the mobile node The IP packet flow to be transferred from the first radio access technology to the second radio access technology specified by the flow transfer request from the first mobility anchor gateway. Wireless interface and the Providing a network architecture further comprising a, a flow establishing unit that can be established between the local mobility anchor.

  According to this configuration, one or more existing IP packet flows established in the mobile node are transferred from the currently used radio access technology (service radio access technology) to another radio access technology (target) according to an instruction from the mobile node. Wireless transfer technology). According to the current state information indicating whether the second radio interface of the mobile node is currently activated, the first mobility anchor gateway sends a first transmission indication or a second mobility anchor gateway to the second mobility anchor gateway. A flow transfer request including the second transmission instruction is transmitted. When the second mobility anchor gateway receives the flow transfer request including the first transmission instruction, the second mobility anchor gateway sends a new connection request to the local mobility anchor, so that the local mobility anchor The mobility anchor executes a procedure for a new connection (new connection) of the mobile node to the second wireless communication network system. (I.e., for a new bi-directional IP tunnel, a new home network prefix and a new binding between this new home network prefix and the care-of-address proxy of the second mobility anchor gateway Assign). After verifying the establishment of the connection between the mobile node and the second mobility anchor gateway, the second mobility anchor gateway sends a flow binding update request to the local mobility anchor. When the second mobility anchor gateway receives the flow movement request including the second transmission instruction, the second mobility anchor gateway transmits the local mobility without transmitting a new connection request to the local mobility anchor. -Send a flow binding update request to the anchor. Upon receiving the flow binding update request, the local mobility anchor associates the transferred IP packet flow with a new home network prefix or an existing home network prefix corresponding to the second mobility anchor gateway. Procedure, so that the IP packet flow is associated with a new or existing bi-directional IP tunnel. Thus, based on the current state of the second radio interface of the mobile node, the network side can selectively execute an appropriate procedure for transferring the IP packet flow. The local mobility anchor performs a new connection procedure followed by a procedure for associating the IP packet flow with the bidirectional IP tunnel, thus minimizing handover delays, missing IP packets and buffering Can be avoided. As a result, the performance of handover related to IP packet flow movement is significantly improved. This is because the IP packet flow determined to move from the service radio network system to the target radio network system is associated with the flow binding registration (associating the IP packet flow with the bidirectional IP tunnel by enabling the use of a plurality of interfaces simultaneously. This is because it is possible to maintain the service wireless network system until the procedure is complete.

  The first wireless communication network system includes desired operational information indicating that the first wireless interface should be active and between the first wireless interface of the mobile node and the local mobility anchor The flow transfer instruction specifying that a part of a plurality of IP packet flows already established via the first radio access technology should be transferred from the first radio access technology to the second radio access technology; When the flow transfer instruction receiving unit of the mobility anchor gateway receives the flow transfer request transmission unit of the first mobility anchor gateway specifies the IP packet flow specified by the flow transfer instruction The flow transfer request is transferred to the second mobility anchor gateway. The first mobility anchor gateway transmits the flow establishment unit of the second mobility anchor gateway identified by the flow transfer request from the first mobility anchor gateway. Even after establishing an IP packet flow between the second radio interface of the mobile node and the local mobility anchor, the first radio interface of the mobile node and the local mobility anchor Other IP packet flows may be maintained among the plurality of IP packet flows already established via the first wireless communication network system. According to the desired operational information from the mobile node, the first mobility anchor gateway is between the first radio interface of the mobile node and the local mobility anchor via the first radio communication network system. An already established IP packet flow can be maintained, and a part of the plurality of IP packet flows can be transferred from the first radio access technology to the second radio access technology.

  The flow transfer instruction including desired operation information indicating that the flow transfer instruction receiving unit of the first mobility anchor gateway should deactivate the first radio interface from the activated state. Is received, the flow transfer request transmission unit of the first mobility anchor gateway transmits the first wireless communication network between the first wireless interface of the mobile node and the local mobility anchor. Sending the flow transfer request specifying that all of the one or more IP packet flows already established through the system should be transferred from the first radio access technology to the second radio access technology; , The flow establishing unit of the second mobility anchor gateway is All of one or more IP packet flows identified by the flow transfer request from one mobility anchor gateway between the second radio interface of the mobile node and the local mobility anchor It may be established. According to the desired operational information from the mobile node, the first mobility anchor gateway sends a plurality of IP packets that the first mobility anchor gateway is processing to the second mobility anchor gateway. It is possible to instruct to process some or all of the flow.

  The first mobility anchor gateway transmits a copy of an IP packet transmitted on the IP packet flow that the mobile node wishes to transfer from the first radio access technology to the second radio access technology. Do not forward to other mobility anchor gateways. This minimizes end-to-end packet delay during IP flow transfer.

  When the flow transfer request received by the flow transfer request reception unit of the second mobility anchor gateway includes the first transmission instruction, the interface activation unit of the second mobility anchor gateway May activate the second radio interface of the mobile node. According to this configuration, the second mobility anchor gateway is based on the first transmission instruction in the flow transfer request transmitted from the first mobility anchor gateway when the second radio interface is to be activated. To activate the second radio interface of the mobile node.

  According to another aspect of the present invention, to operate based on Proxy Mobile Internet Protocol version 6 and communicate with the Internet via a first wireless communication network system using a first wireless access technology. And a second wireless interface for communicating with the Internet via the second wireless communication network system using a second wireless access technology different from the first wireless access technology. A network architecture for communicating with at least one mobile node comprising: the first wireless communication network system in which the mobile node can communicate using the first radio access technology; The second wireless access technology different from the first wireless access technology. Connected to the first wireless communication network system via the Internet, and connected to the second wireless communication network system via the Internet A local mobility anchor capable of communicating with a counterpart node of the mobile node, wherein the mobile node communicates with the counterpart node via the first wireless communication network system and the local mobility anchor A local mobility anchor capable of communicating with the counterparty node via the second wireless communication network system and the local mobility anchor. And the first A communication network system is capable of operating as an access router for the mobile node and is at least one established via the first wireless communication network system between the mobile node and the local mobility anchor. And the second wireless communication network system can operate as an access router of the mobile node, and the mobile node can manage the IP packet flow of the mobile node. A second mobility anchor gateway capable of managing at least one IP packet flow established between the node and the local mobility anchor via the second wireless communication network system; The first wireless communication network The first mobility anchor gateway of the work system is configured such that a plurality of IP packet flows route the first wireless communication network system between the first radio interface of the mobile node and the local mobility anchor. The IP packet flow via the second radio communication network system is not established between the second radio interface of the mobile node and the local mobility anchor. And a flow transfer instruction transmitted from the mobile node when the mobile node wants to transfer at least one of the IP packet flows already established from the first radio access technology to the second radio access technology. And the mobile node A flow transfer instruction receiving unit capable of receiving a flow transfer instruction specifying the second radio interface of the mobile node used for the target IP packet flow; and A flow transfer request transmitting unit capable of transmitting a flow transfer request to the second mobility anchor gateway of the second wireless communication network system when receiving the transfer instruction; The relocation request includes the mobile node, the second radio interface of the mobile node used for the IP packet flow to be relocated, and the second radio access from the first radio access technology by the mobile node. Identifying the IP packet flow to be transferred to the technology and the second wireless communication network The second mobility anchor gateway of the network system can receive the flow transfer request from the proxy care-of address indicating the second mobility anchor gateway and the first mobility anchor gateway When the flow transfer request receiving unit and the flow transfer request receiving unit receive the flow transfer request, a new connection request specifying the mobile node and the proxy care-of address of the second mobility anchor gateway is generated. A new connection request transmitter capable of transmitting to the local mobility anchor, and the local mobility anchor receives the new connection request from the second mobility anchor gateway A new connection request receiver capable of A new home network prefix of the mobile node used for communication via the second wireless communication network system between the second wireless interface of the wireless node and the local mobility anchor When the new connection request is received by the new connection request receiving unit, the new home network prefix of the mobile node and the proxy awareness of the second mobility anchor gateway A new connection request registration unit capable of registering a new binding with the address, a new home network prefix of the mobile node, and the proxy care-of address of the second mobility anchor gateway Based on The mobile node's new home network prefix to facilitate the establishment of a bi-directional IP tunnel between the second mobility anchor gateway and the local mobility anchor. A new home network prefix transmitter for transmitting to the gateway, wherein the second mobility anchor gateway receives the new home network prefix of the mobile node from the local mobility anchor When the new home network prefix receiving unit receives the new home network prefix receiving unit and the new home network prefix receiving unit of the mobile node, the mobile node Activating the second radio interface of the mobile node identified in the flow transfer request to facilitate establishment of a connection between the second radio interface and the second mobility anchor gateway. A possible interface activation unit, a connection confirmation unit capable of confirming connection establishment between the second radio interface of the mobile node and the second mobility anchor gateway, and the connection confirmation unit And confirming the establishment of the connection with the mobile node further comprising: a flow binding update request transmitting unit capable of transmitting a flow binding update request to the local mobility anchor. From the first radio access technology to the first mobility anchor -Identifying the IP packet flow that is to be transferred to the second radio access technology specified in the flow transfer request from the gateway, wherein the local mobility anchor is from the second mobility anchor gateway; A new one of the flow binding update request receiving unit capable of receiving the flow binding update request, the new home network prefix of the mobile node, and the IP packet flow specified by the flow binding update request. A flow binding registration unit capable of registering a binding, and a flow binding completion message indicating that the registration of the new binding in the flow binding registration unit is completed, the second mobility anchor A flow binding completion report transmitting unit capable of transmitting to the gateway, wherein the second mobility anchor gateway receives the flow binding completion message from the local mobility anchor. And a connection between the second radio interface of the mobile node and the second mobility anchor gateway, and the second mobility anchor gateway and the local Using the bidirectional IP tunnel to and from a mobility anchor, the mobile node is identified from the first radio access technology and in the flow transfer request from the first mobility anchor gateway Second radio access technology Said IP packet flow to be transferred, further comprising a, a flow establishing unit that can be established between the second wireless interface and the local mobility anchor of the mobile node, to provide a network architecture.

  According to this configuration, one or more existing IP packet flows established in the mobile node are transferred from the currently used radio access technology (service radio access technology) to another radio access technology (target) according to an instruction from the mobile node. Wireless access technology). When the second mobility anchor gateway receives the flow transfer request from the first mobility anchor gateway, the second mobility anchor gateway sends a new connection request to the local mobility anchor and As a result, the local mobility anchor executes a procedure for a new connection (new connection) of the mobile node to the second wireless communication network system. (I.e., for a new bi-directional IP tunnel, a new home network prefix and a new binding between this new home network prefix and the care-of-address proxy of the second mobility anchor gateway Assign). After verifying the establishment of the connection between the mobile node and the second mobility anchor gateway, the second mobility anchor gateway sends a flow binding update request to the local mobility anchor. Upon receiving the flow binding update request, the local mobility anchor performs the procedure for associating the transferred IP packet flow with a new home network prefix corresponding to the second mobility anchor gateway, and As a result, the IP packet flow is associated with a new bidirectional IP tunnel. The local mobility anchor performs a new connection procedure followed by a procedure for associating the IP packet flow with the bidirectional IP tunnel, thus minimizing handover delays, missing IP packets and buffering Can be avoided. As a result, the performance of handover related to IP packet flow movement is significantly improved. This is because the IP packet flow determined to move from the service radio network system to the target radio network system is associated with the flow binding registration (associating the IP packet flow with the bidirectional IP tunnel by enabling the use of a plurality of interfaces simultaneously. This is because it is possible to maintain the service wireless network system until the procedure is complete.

  According to another aspect of the present invention, to operate based on Proxy Mobile Internet Protocol version 6 and communicate with the Internet via a first wireless communication network system using a first wireless access technology. And a second wireless interface for communicating with the Internet via the second wireless communication network system using a second wireless access technology different from the first wireless access technology. A network architecture for communicating with at least one mobile node comprising: the first wireless communication network system in which the mobile node can communicate using the first radio access technology; The second wireless access technology different from the first wireless access technology. Connected to the first wireless communication network system via the Internet, and connected to the second wireless communication network system via the Internet A local mobility anchor capable of communicating with a counterpart node of the mobile node, wherein the mobile node communicates with the counterpart node via the first wireless communication network system and the local mobility anchor A local mobility anchor capable of communicating with the counterparty node via the second wireless communication network system and the local mobility anchor. And the first A communication network system is capable of operating as an access router for the mobile node and is at least one established via the first wireless communication network system between the mobile node and the local mobility anchor. And the second wireless communication network system can operate as an access router of the mobile node, and the mobile node can manage the IP packet flow of the mobile node. A second mobility anchor gateway capable of managing at least one IP packet flow established between the node and the local mobility anchor via the second wireless communication network system; The first wireless communication network The first mobility anchor gateway of the work system is configured such that at least one IP packet flow is between the first radio interface of the mobile node and the local mobility anchor. While at least one IP packet flow is established between the second radio interface of the mobile node and the local mobility anchor via the second radio communication network system. Transmitted from the mobile node when the mobile node wishes to transfer at least one already established IP packet flow from the first radio access technology to the second radio access technology. A flow transfer instruction, Current state information indicating whether or not the second radio interface is currently activated, and the second radio interface of the mobile node used for the IP packet flow to be transferred A flow transfer instruction receiving unit capable of receiving the flow transfer instruction, and the flow transfer instruction receiving unit receiving the flow transfer instruction, the second mobility anchor anchor of the second wireless communication network system A flow transfer request transmitting unit capable of transmitting a flow transfer request to the gateway, the flow transfer request being transmitted to the mobile node and the mobile node used for the IP packet flow to be transferred The second wireless interface and the mobile node is connected to the first wireless interface. The IP packet flow to be transferred from the access technology to the second radio access technology, and the second mobility anchor gateway of the second radio communication network system includes the second mobility anchor gateway A proxy care-of address indicating a gateway, a flow transfer request receiving unit capable of receiving the flow transfer request from the first mobility anchor gateway, and the flow transfer request receiving unit receiving the flow transfer request Then, a flow binding update request transmitting unit capable of transmitting a flow binding update request to the local mobility anchor, wherein the flow binding update request includes the mobile node, the second mobility anchor, The gateway proxy And the IP packet flow that the mobile node wishes to transfer from the first radio access technology to the second radio access technology specified by the flow transfer request from the first mobility anchor gateway And the local mobility anchor includes a flow binding update request receiving unit capable of receiving the flow binding update request from the second mobility anchor gateway, and an existing mobile node existing A flow binding registration unit capable of registering a binding between a home network prefix and the IP packet flow specified by the flow binding update request, wherein the existing home network prefix of the mobile node is registered. The second mobility anchor gateway and the local mobility anchor for establishing an existing bidirectional IP tunnel between the second mobility anchor gateway and the local mobility anchor. A flow binding registration unit already associated with the proxy care-of address of the second mobility anchor gateway, and a flow binding completion message indicating completion of registration of the binding in the flow binding registration unit. A flow binding completion report transmission unit capable of transmitting to the second mobility anchor gateway, wherein the second mobility anchor gateway includes the local mobility anchor A flow binding completion report receiving unit capable of receiving the flow binding completion message, and after the flow binding completion report receiving unit receives the flow binding completion message, the second radio interface of the mobile node Using the existing connection between the second mobility anchor gateway and the second mobility anchor gateway and the bidirectional IP tunnel between the second mobility anchor gateway and the local mobility anchor. The IP packet flow to be transferred from the first radio access technology to the second radio access technology specified by the flow transfer request from the first mobility anchor gateway. Second wireless device And a flow establishment unit that can be established between the interface and the local mobility anchor.

  According to this configuration, one or more existing IP packet flows established in the mobile node are transferred from the currently used radio access technology (service radio access technology) to another radio access technology (target radio) in accordance with instructions from the mobile node. Access technology). When the second mobility anchor gateway receives the flow movement request from the first mobility anchor gateway, the second mobility anchor gateway sends a flow binding update request to the local mobility anchor. Upon receiving the flow binding update request, the local mobility anchor performs the procedure of associating the transferred IP packet flow with the existing home network prefix corresponding to the second mobility anchor gateway, and As a result, the IP packet flow is associated with the existing bidirectional IP tunnel. When the second mobility anchor gateway receives the flow binding complete message from the local mobility anchor, the transferred IP packet flow is used, thus avoiding missing IP packets and buffering.

  According to another aspect of the present invention, a local mobility anchor in a network architecture for operating with Proxy Mobile Internet Protocol version 6 and communicating with at least one mobile node, comprising: A mobility anchor is connected to the first mobility anchor gateway via the local mobility anchor Internet, is connected to a second mobility anchor gateway via the Internet, and the first mobility anchor The anchor gateway operates as an access router for the mobile node of a first wireless communication network system that uses a first radio access technology to communicate with the mobile node, and the mobile gateway And at least one IP packet flow established via the first wireless communication network system between the mobile node and the local mobility anchor, wherein the second mobility anchor gateway is the mobile node Operating as an access router for the mobile node of a second wireless communication network system that uses a second wireless access technology to communicate with the mobile node and between the mobile node and the local mobility anchor Managing at least one IP packet flow established via two wireless communication network systems, the local mobility anchor being able to communicate with a counterpart node of the mobile node, wherein the mobile node 1 wireless communication network system It is possible to communicate with the counterpart node via the local mobility anchor, and communicate with the counterpart node via the second wireless communication network system and the local mobility anchor. And the local mobility anchor determines, from the second mobility anchor gateway, a new proxy that identifies a proxy care-of address of the mobile node and the second mobility anchor gateway. A new connection request receiving unit capable of receiving a connection request; and used for communication via the second wireless communication network system between a radio interface of the mobile node and the local mobility anchor, New home network for mobile nodes A network prefix can be assigned to the mobile node, and when the new connection request is received by the new connection request receiving unit, the new home network prefix of the mobile node and the second mobility A new connection request registration unit capable of registering a new binding with the proxy care-of address of the anchor gateway, a new home network prefix of the mobile node, and the second mobility anchor gateway Based on the proxy care-of address of the mobile node to facilitate establishment of a bidirectional IP tunnel between the second mobility anchor gateway and the local mobility anchor. A new home network prefix transmission unit for transmitting a packet to the second mobility anchor gateway, from the second mobility anchor gateway, to the mobile node, and to the second mobility anchor gateway The proxy care-of address and the flow binding capable of receiving a flow binding update request specifying at least one IP packet flow that the mobile node wishes to transfer from the first radio access technology to the second radio access technology An update request receiving unit, and a binding between the new home network prefix or the existing home network prefix of the mobile node and the IP packet flow specified by the flow binding update request. The existing home network prefix of the mobile node is between the second mobility anchor gateway and the local mobility anchor. Already associated with the proxy care-of address of the second mobility anchor gateway by the second mobility anchor gateway and the local mobility anchor for establishing an existing bi-directional IP tunnel; A flow binding registration unit and a flow binding completion message indicating that the registration of the binding in the flow binding registration unit is completed can be transmitted to the second mobility anchor gateway. And a local mobility anchor having a low binding completion report transmission unit.

  According to this configuration, one or more existing IP packet flows established in the mobile node are transferred from the currently used radio access technology (service radio access technology) to another radio access technology (target) according to an instruction from the mobile node. Wireless access technology). When the local mobility anchor receives a new connection request from the second mobility anchor gateway, the local mobility anchor receives a new connection (new connection) of the mobile node to the second wireless communication network system. (I.e., for a new bidirectional IP tunnel, a new home network prefix and the new home network prefix and the care-of address proxy of the second mobility anchor gateway) Assign a new binding between). Upon receiving the flow binding update request from the second mobility anchor gateway, the local mobility anchor transmits the transferred IP packet flow to a new home network prefix corresponding to the second mobility anchor gateway or A procedure for associating with an existing home network prefix is performed so that the IP packet flow is associated with a new or existing bi-directional IP tunnel. Since the local mobility anchor performs the procedure for the new connection and then associates the IP packet flow with the bidirectional IP tunnel, handover delay is minimized and IP packet loss and buffering can be avoided. . As a result, the performance of handover related to IP packet flow movement is significantly improved. This is because the IP packet flow determined to move from the service radio network system to the target radio network system is associated with the flow binding registration (associating the IP packet flow with the bidirectional IP tunnel by enabling the use of a plurality of interfaces simultaneously. This is because it is possible to maintain the service wireless network system until the procedure is complete.

  According to another aspect of the present invention, to operate based on Proxy Mobile Internet Protocol version 6 and communicate with the Internet via a first wireless communication network system using a first wireless access technology. And a second wireless interface for communicating with the Internet via the second wireless communication network system using a second wireless access technology different from the first wireless access technology. A mobility anchor gateway for communicating with at least one mobile node having the mobility anchor gateway belongs to the first wireless communication network system and communicates with a counterpart node of the mobile node. Possible local mobility The mobility anchor gateway is capable of operating as an access router for the mobile node, and the second wireless communication between the mobile node and the local mobility anchor It is possible to manage at least one IP packet flow established via a network system, wherein the mobility anchor gateway has at least one IP packet flow that is connected to the first radio interface of the mobile node and the local When established with the mobility anchor via the first radio communication network system and the mobile node transmits at least one already established IP packet flow to the first radio From the second access technology A flow relocation instruction transmitted from the mobile node when it is desired to relocate to an access technology, and identifies the mobile node and the second radio interface of the mobile node used for the IP packet flow to be relocated And a flow transfer instruction receiving unit capable of receiving a flow transfer instruction including current state information indicating whether or not the second radio interface is currently activated, and the flow transfer instruction receiving unit receiving the flow A flow transfer request transmitting unit capable of transmitting a flow transfer request to another mobility anchor gateway of another wireless communication network system using the second radio access technology when receiving the transfer instruction; The flow transfer request includes the mobile node and the I to be transferred. Identifying the second radio interface of the mobile node used for P packet flow and the IP packet flow that the mobile node wishes to transfer from the first radio access technology to the second radio access technology; , If the current state information in the flow transfer indication indicates that the second radio interface is not currently activated, between the other mobility anchor gateway and the local mobility anchor A first transmission instruction for instructing the other mobility anchor gateway to transmit a new connection request to the local mobility anchor in order to prompt establishment of a bidirectional IP tunnel between the first mobility instruction and the second mobility anchor gateway; That the two radio interfaces are currently active When the current state information in the flow transfer instruction indicates, the IP packet flow specified by the flow transfer instruction is transferred between the another mobility anchor gateway and the local mobility anchor. A mobility anchor gateway comprising a second transmission instruction for instructing the second mobility anchor gateway to transmit a flow binding update request to the local mobility anchor for associating with an IP tunnel; provide.

    According to this configuration, one or more existing IP packet flows established in the mobile node are transferred from the currently used radio access technology (service radio access technology) to another radio access technology (target) according to an instruction from the mobile node. Wireless access technology). According to the current state information indicating whether the second radio interface of the mobile node is currently activated, the mobility anchor gateway sends a first transmission indication or a second transmission to another mobility anchor gateway. Send a flow transfer request with instructions. When the other mobility anchor gateway receives the flow transfer request including the first transmission instruction, the another mobility anchor gateway sends a new connection request to the local mobility anchor, and as a result, the local mobility anchor gateway The mobility anchor executes a procedure for a new connection (new connection) of the mobile node to the second wireless communication network system. (I.e., for a new bi-directional IP tunnel, a new home network prefix and a new mobility between the new home network prefix and the care-of-address proxy of the second mobility anchor gateway Assign bindings). After verifying the establishment of the connection between the mobile node and the second mobility anchor gateway, the other mobility anchor gateway sends a flow binding update request to the local mobility anchor. When the other mobility anchor gateway receives the flow movement request including the second transmission instruction, the other mobility anchor gateway transmits the local mobility without transmitting a new connection request to the local mobility anchor. -Send a flow binding update request to the anchor. Upon receipt of the flow binding update request, the local mobility anchor to associate the transferred IP packet flow with a new home network prefix or an existing home network prefix corresponding to another mobility anchor gateway As a result, the IP packet flow is associated with a new or existing bidirectional IP tunnel. In this way, based on the current state of the mobile node's second radio interface, the mobility anchor gateway can use the first transmission instruction or the first transmission instruction to initiate an appropriate procedure for transferring the IP packet flow. A flow transfer request including two transmission instructions can be selectively transmitted. The local mobility anchor performs a new connection procedure followed by a procedure for associating the IP packet flow with the bidirectional IP tunnel, thus minimizing handover delays, missing IP packets and buffering Can be avoided. As a result, the performance of handover related to IP packet flow movement is significantly improved. This is because the IP packet flow determined to move from the service radio network system to the target radio network system is associated with the flow binding registration (associating the IP packet flow with the bidirectional IP tunnel by enabling the use of a plurality of interfaces simultaneously. This is because it is possible to maintain the service wireless network system until the procedure is complete.

According to another aspect of the present invention, to operate based on Proxy Mobile Internet Protocol version 6 and communicate with the Internet via a first wireless communication network system using a first wireless access technology. And a second wireless interface for communicating with the Internet via the second wireless communication network system using a second wireless access technology different from the first wireless access technology. A mobility anchor gateway for communicating with at least one mobile node, the mobility anchor gateway belonging to the second wireless communication network system and capable of communicating with a counterpart node of the mobile node・ Connected to the mobility anchor At least one IP packet flow established between the mobile node and the local mobility anchor via the second wireless communication network system, capable of operating as an access router of the mobile node The mobility anchor gateway includes a proxy care-of address indicating the mobility anchor gateway and another mobility anchor of another wireless communication network system using the first radio access technology. From the gateway, the mobile node, the second radio interface of the mobile node used for the IP packet flow to be transferred, and the mobile node from the first radio access technology to the second radio Access technology A first transmission instruction that specifies the IP packet flow to be transferred and instructs the mobility anchor gateway to transmit a new connection request to the local mobility anchor, or the local mobility A flow transfer request receiving unit capable of receiving a flow transfer request including a second transmission instruction for instructing the mobility anchor gateway to transmit a flow binding update request to the anchor; and receiving the flow transfer request The mobile node in order to prompt establishment of a bidirectional IP tunnel between the mobility anchor gateway and the local mobility anchor when the flow transfer request received by the mobile station includes the first transmission instruction. And the mobility anchor gateway A new connection request transmitting unit capable of transmitting a new connection request specifying the proxy care-of address to the local mobility anchor, the new home network prefix of the mobile node, and the mobility Based on the proxy care-of address of the anchor gateway, the mobile node's new home network network is urged to facilitate the establishment of a bidirectional IP tunnel between the mobility anchor gateway and the local mobility anchor. A new home network prefix receiving unit capable of receiving a prefix from the local mobility anchor, and the new home network prefix receiving unit in the new home network prefix receiving unit Upon receipt of the prefix, the second of the mobile node identified in the flow transfer request is urged to prompt establishment of a connection between the second radio interface of the mobile node and the mobility anchor gateway. An interface activation unit capable of activating a radio interface; and a connection confirmation unit capable of confirming establishment of a connection between the second radio interface of the mobile node and the mobility anchor gateway. When the connection confirmation unit confirms the establishment of the connection, the IP packet flow specified by the flow transfer request is transferred to the bidirectional IP tunnel between the mobility anchor gateway and the local mobility anchor. Flow binding to associate with A new request can be transmitted to the local mobility anchor, and when the flow transfer request including the second transmission instruction is received by the flow transfer request receiving unit, the flow binding update request is transmitted to the local mobility anchor. A flow binding update request transmitting unit capable of transmitting to a mobility anchor, wherein the flow binding update request includes the mobile node, the proxy care-of address of the mobility anchor gateway, and the mobile node A flow binding update request transmission unit for identifying the IP packet flow to be transferred from the first radio access technology to the second radio access technology;
A flow binding completion report receiving unit for receiving a flow binding completion message from the local mobility anchor; a connection between the second radio interface of the mobile node and the mobility anchor gateway; and the mobility anchor anchor The IP packet flow that the mobile node wants to transfer from the first radio access technology to the second radio access technology using the bidirectional IP tunnel between a gateway and the local mobility anchor, The IP packet flow specified by the flow transfer request from the mobility anchor gateway can be established between the second radio interface of the mobile node and the local mobility anchor. A flow establishing unit such, provides a mobility anchor gateway with.

  According to this configuration, one or more existing IP packet flows established in the mobile node are transferred from the currently used radio access technology (service radio access technology) to another radio access technology (target) according to an instruction from the mobile node. Wireless access technology). When the mobility anchor gateway receives the flow transfer request including the first transmission instruction, the mobility anchor gateway sends a new connection request to the local mobility anchor, so that the local mobility anchor The procedure for the new connection (new connection) of the mobile node to the wireless communication network system 2 is executed. (Ie, assign a new home network prefix and a new binding between this new home network prefix and the care-of-address proxy of the mobility anchor gateway for the new bidirectional IP tunnel) . After verifying the establishment of the connection between the mobile node and the mobility anchor gateway, the mobility anchor gateway sends a flow binding update request to the local mobility anchor. When the mobility anchor gateway receives a flow move request that includes a second transmission instruction, the mobility anchor gateway updates the flow binding to the local mobility anchor without sending a new connection request to the local mobility anchor. Send a request. Upon receipt of the flow binding update request, the local mobility anchor associates the transferred IP packet flow with a new home network prefix or an existing home network prefix corresponding to the mobility anchor gateway. As a result, the IP packet flow is associated with a new or existing bidirectional IP tunnel. In this way, the local mobility anchor can selectively perform an appropriate procedure for transferring the IP packet flow. The local mobility anchor performs a new connection procedure followed by a procedure for associating the IP packet flow with the bidirectional IP tunnel, thus minimizing handover delays, missing IP packets and buffering Can be avoided. As a result, the performance of handover related to IP packet flow movement is significantly improved. This is because the IP packet flow determined to move from the service radio network system to the target radio network system is associated with the flow binding registration (associating the IP packet flow with the bidirectional IP tunnel by enabling the use of a plurality of interfaces simultaneously. This is because it is possible to maintain the service wireless network system until the procedure is complete.

Embodiments of the present invention will be described below with reference to the accompanying drawings.
It is a figure which shows the functional hierarchy model by the technique proposed recently. It is a conceptual diagram which shows the network architecture which concerns on embodiment of this invention. FIG. 3 is a block diagram illustrating a structure of each mobile node capable of using the network architecture shown in FIG. 2. It is a figure which shows the binding cache entry (BCE) table used by the local mobility anchor (LMA) which concerns on this embodiment. It is a figure which shows the flow binding cache entry (FCE) table used by LMA which concerns on this embodiment. It is a block diagram which shows the physical structure of LMA. It is a block diagram which shows the functional structure of LMA. It is a block diagram which shows the physical structure of the mobility anchor gateway (MAG) which concerns on this embodiment. It is a block diagram which shows the functional structure of MAG. It is a figure which shows an example of the binding update list table used by MAG. It is a figure which shows an example of the flow binding update list table used by MAG. It is a figure which shows the local policy profile table which can be used in each mobile node (MN) which concerns on this embodiment. It is a figure which shows the format of the HIF (Handover Initiate for Flow mobility) message transmitted between MAG concerning this embodiment. It is a figure which shows the format of the HAF (Handover Acknowledgment for Flow mobility) message transmitted between MAG concerning this embodiment. It is a figure which shows the format of the information of the interface state and operation | movement contained in a HIF message. It is a conceptual diagram which shows the 1st scenario of IP flow transfer which concerns on this embodiment. FIG. 18 is an information flow diagram of the first scenario of IP flow transfer according to the present embodiment. FIG. 17 is an information flow diagram of the first scenario of IP flow transfer according to the present embodiment. It is a conceptual diagram which shows the 2nd scenario of IP flow transfer which concerns on this embodiment. It is an information flow figure of the 2nd scenario of IP flow transfer concerning this embodiment. It is a conceptual diagram which shows the 3rd scenario of IP flow transfer which concerns on this embodiment. FIG. 23 is an information flow diagram of the third scenario of IP flow transfer according to the present embodiment. FIG. 22 is an information flow diagram of the third scenario of IP flow transfer according to the present embodiment. It is a conceptual diagram which shows the 4th scenario of IP flow transfer which concerns on this embodiment. FIG. 26 is an information flow diagram of the fourth scenario of IP flow transfer according to the present embodiment. FIG. 25 is an information flow diagram of the fourth scenario of IP flow transfer according to the present embodiment.

2.1 Network Architecture Overview FIG. 2 illustrates a network architecture arrangement according to the present invention. The network architecture can operate based on PMIPv6. The network architecture is a heterogeneous network architecture including a plurality of wireless communication network systems in which a mobile node (MN) 10 can communicate according to different wireless access technologies. For example, the network architecture includes a 3G (third generation) network system 12 in which 3G wireless access technology is used to communicate with a plurality of MNs 10 and a WiFi network system 18 in which WiFi wireless access technology is used to communicate with a plurality of MNs 10. including.

  FIG. 3 is a block diagram showing the structure of each MN 10 that can use the network architecture shown in FIG. The MN 10 may be a smartphone, a tablet computer, a laptop, a netbook, or the like, and can communicate with the Internet 24. The MN 10 includes multiple radio interfaces for communicating with the Internet 24 according to different radio access technologies. For example, the MN 10 includes a 3G interface 31 for 3G communication by the 3G network system 12 and a WiFi interface 32 for WiFi communication by the WiFi network system 18. The MN 10 includes a processor 33 for controlling the overall operation of the MN 10, a display unit 34 for displaying still images and moving images under the control of the processor 33, and a speaker for emitting sound under the control of the processor 33. 35 and a human interface 36. The human interface 36 may be a microphone or a button for inputting an instruction to the processor 33.

  As shown in FIG. 2, the 3G network system 12 includes a base station 14 to which a plurality of MNs 10 can communicate via radio, and a mobility anchor anchor that these base stations 14 can typically communicate via a cable. Includes a gateway (MAG). The WiFi network system 18 includes a base station (access node) 20 with which a plurality of MNs 10 can communicate via radio, typically via cables, and a plurality of MAGs 22 with which the access nodes can communicate. For ease of understanding, FIG. 2 shows only one MN 10, one base station 14, one MAG 16, one access node 20, and one MAG 22.

  The network architecture also includes a local mobility anchor (LMA) 26 connected to the plurality of wireless communication network systems 12 and 18 via the Internet 24. The LMA 26 communicates with a plurality of correspondent nodes (CN) 28 of a plurality of MNs 10, whereby each MN 10 is connected via the 3G network system 12 and the LMA 26, and via the WiFi network system 18 and the LMA 26. It is possible to communicate with a plurality of CNs 28.

  MAG and LMA are the central functional entities for IP mobility defined in PMIPv6 (described in RFC 5213) and Proxy Mobile IPv6 fast handover (F-PMIPv6: Fast Handovers for Proxy Mobile IPv6 described in RFC 5949). is there. Embodiments of the present invention enable PMIPv6 or F− to enable IP flow mobility initiated by a mobile node (ie, mobile station initiated IP flow mobility) and to provide a more useful network-based mobility management protocol. Compared to PMIPv6, the functions of MAG and LMA are enhanced.

  The LMA 26 performs HA (home agent) activity (that is, acts as a home agent) for maintaining the binding information defined in RFC 5213 for each mobile node 10, and the home network prefix (HNP) of each mobile node 10. : Topological anchor point for home network prefix).

  MAG (each of MAG 16 and MAG 22) has access to manage mobility-related signaling on behalf of each mobile node 10 connected to the wireless communication network system (eg, 3G network system 12 or WiFi network system 18) where the MAG is located. Acts as a router. The MAG is responsible for tracking the movement of the mobile node to and from the wireless communication network system in which the MAG is provided and signaling the LMA 26 of the mobile node.

  More specifically, when initiating communication between the MN 10 and the CN 28 via the Internet 24, the LMA 26 assigns the mobile node's home network prefix (MN-HNP) to the MN 10 and the MN 10's home network A binding is established between the prefix and the MAG proxy care-of address (proxy CoA) in the wireless communication network system to which the MN 10 is connected. The LMA 26 notifies the MAG of the home network prefix of the MN 10, and the MAG notifies the MN 10 itself of the home network prefix of the MN 10. Then, the MN 10 configures the home address (MN-HoA) of the mobile node from the home network prefix. As long as the MN 10 is connected to the wireless communication network system, the MN 10 uses MN-HoA. Further, the LMA 26 and the MAG establish a bidirectional IP tunnel using a binding between the home network prefix of the MN 10 and the proxy care-of address (proxy CoA) of the MAG described in RFC5213. As a result, each binding matches a bidirectional IP tunnel.

  In order to manage each binding between MN 10's home network prefix (HNP) and MAG's proxy care-of address (proxy CoA), LMA 26 uses the binding cache entry (BCE) table shown in FIG. It is stored in the memory device. The BCE tables are respectively MN-ID (mobile node identifier), BID (binding identifier), priority, HNP, proxy CoA, ATT (access technology type) and MN-LL-ID (mobile node link layer identification). ) Etc. are recorded.

  The MN-ID uniquely identifies the MN 10. The BID is used to distinguish a plurality of bindings registered by one MN 10 described in RFC5648. The priority order specifies the priority order of binding priority when one MN 10 registers a plurality of bindings. For example, when MN # 1 indicated by BID1 and 2 in FIG. 4 registers a plurality of bindings, BID1 associated with the 3G network system has the highest priority (first priority), This first priority means that the IP packet flow using the 3G network system should be maintained as much as possible. BID2 associated with the WiFi network system has a second priority (second priority) which means that the IP packet flow using the WiFi network system may be transferred to another network system (eg, 3G network system). Ranking). HNP is a home network prefix assigned to the MN 10. Proxy CoA is the proxy care-of address of the MAG to which MN 10 is connected. The ATT specifies the type of access technology (for example, 3G or WiFi) that the MN 10 currently uses for connection with the MAG. The MN-LL-ID specifies (identifies) the wireless interface (for example, the 3G interface 31 or the WiFi interface 32) of the MN 10 that the MN 10 uses to connect to the MAG.

  As can be seen from FIG. 4, one MN 10 can communicate with one or more CNs 28 through the 3G network system 12 (including the MAG 16) and the LMA 26 using the 3G interface 31. At the same time, one MN 10 can communicate with one or more CNs 28 through the WiFi network system 18 (including the MAG 22) and the LMA 26 using the WiFi interface 32.

  In addition to the requirements defined in RFC 5213 and RFC 5648, LMA 26 manages all IP packet flows between MN 10 and CN 28. An IP flow (ie, IP packet flow) means a series of IP packets. In RFC 6089, an IP flow is defined as a set of IP packets that conform to a traffic selector. An IP flow may be established on the connection via the 3G network system 12 between the 3G interface 31 of the MN 10 and the LMA 26, and on the connection via the WiFi network system 18 between the WiFi interface 32 of the MN 10 and the LMA 26. May be established in Furthermore, the IP flow may be transferred from the currently used radio access technology to another radio access technology (3G to WiFi and WiFi to 3G). The LMA 26 manages the relationship between each IP flow and the binding between the HNP and the proxy CoA. In other words, the LMA 26 manages each flow binding between the IP flow defined in RFC 6089 and the binding identifier (BID).

In order to manage each flow binding between the IP flow and the BID, the LMA 26 stores a flow binding cache entry (FCE) table shown in FIG. 5 in its memory device. The FCE table records a flow binding cache entry (that is, a flow binding entry) each including a flow ID (flow identifier), a priority, a traffic selector, a BID, and a flow type.
The flow ID uniquely identifies the flow binding and is generated by the MN 10. The priority order specifies the priority order of the IP flows when one binding is associated with a plurality of IP flows. A traffic selector is information including one or more parameters (for example, source IP address, destination IP address, source port number, destination port number and transport protocol number) used to classify packets, and identifies an IP flow. To do. The flow type specifies the type of IP flow. Flow type “dynamic” means that the corresponding IP flow can be transferred from the currently used radio access technology to another radio access technology. The flow type “static” means that the corresponding IP flow is not transferable. As can be seen from FIG. 5, one BID may be associated with multiple flows, whereas each flow binding cache entry (ie, flow binding entry) contains a specific BID. .

  According to the embodiment of the present invention, in response to an instruction from the mobile node, one or more existing IP flows established in the MN 10 are dynamically changed from the currently used radio access technology to another radio access technology. Transferable. In other words, one or more existing IP flows can be dynamically transferred from the currently used wireless communication network system to another wireless communication network system. With the change of the radio access technology of the IP flow, the BID in the flow binding cache entry (flow binding entry) corresponding to the IP flow should be changed in the FCE table shown in FIG.

  In the following description, a radio access technology that is currently used for an IP flow (that is, a transfer) target radio access technology may be referred to as a first radio access technology or a service radio access technology. The technology may be referred to as a second radio access technology or a target radio access technology. Similarly, a wireless communication network system currently used for an IP flow to be moved (that is, relocation) may be referred to as a first wireless network system or a service wireless network system, and wireless communication newly used for the IP flow. The network system may be referred to as a second wireless network system or a target wireless network system. Similarly, when a mobility anchor gateway (MAG) currently used for an IP flow to be moved (ie, relocated) is referred to as a first mobility anchor gateway or a service mobility anchor gateway (sMAG) The mobility anchor gateway (MAG) newly used for the IP flow may be referred to as a second mobility anchor gateway or a target mobility anchor gateway (tMAG). Similarly, the radio interface of the MN 10 currently used for the IP flow to be moved (that is, relocation) may be referred to as a first radio interface or a service radio interface, and the radio interface of the MN 10 newly used for the IP flow may be referred to. It may be called a second radio interface or a target radio interface.

  As will be described later, the LMA 26 targets a proxy binding update (PBU) message including at least one FID (flow ID) associated with the IP flow that the MN 10 wishes to transfer from the service radio access technology to the target radio access technology. Upon receipt from the MAG (tMAG), the LMA 26 identifies the binding between the HNP of the MN 10 and the proxy CoA of the sMAG that is currently used for the IP flow, corresponding to the existing FID in the flow binding entry. Update) with another BID corresponding to the target radio interface (identifying the binding between the HNP of the MN 10 and the proxy CoA of the tMAG that will be used in the future for the IP flow).

  As described above, MAG (each of MAG 16 and MAG 22) functions as an access router for each MN 10 and executes an IP flow mobility management procedure on behalf of each MN 10. The MAG has a role of detecting the movement of the MN and detecting a flow mobility indication message (flow transfer instruction) sent from the MN 10. The flow mobility instruction message specifies at least one IP flow that the MN 10 wishes to transfer from the service radio access technology to the target radio access technology. The flow mobility indication message indicates that the service radio interface should be active or inactive after completion of IP flow movement (transfer) and that the target radio interface should be active or inactive after completion of IP flow transfer Desired operation information. The MAG uses the desired operation information to determine the type of IP flow handover (IP flow transfer) for the specified IP flow.

  When the MAG is the target MAG, if the MN 10 is not connected to the target wireless network system, the tMAG causes the LMA 26 to perform preliminary registration. In this preliminary registration, the LMA registers a new binding of the MN 10 for the MN 10 to start a new connection to the target wireless network system. More specifically, in the preliminary registration, a new binding cache entry indicating the MN-ID, the new HNP of the MN, and the proxy CoA of the tMAG is added to the binding cache entry (BCE) table. The preliminary registration is executed by transmitting a pre-proxy binding update (Pre-PBU) message (new connection request) from the tMAG to the LMA 26.

  If the MAG is the target MAG, and if the MN 10 is connected to the target radio network system, the tMAG includes a PBU message including at least one FID associated with the IP flow that the MN 10 wishes to transfer from the service radio access technology to the target radio access technology ( Send flow binding update request). The PBU message causes the LMA 26 to perform flow binding registration. In this flow binding registration, the LMA uses another FID corresponding to the target radio interface (which is used in the future for the IP flow and identifies the binding between the HNP of the MN 10 and the proxy CoA of the tMAG), and the FID. Update the BID (which identifies the binding between the HNP of the MN 10 and the proxy CoA of the sMAG) that is currently in use for the IP flow.

  In this application, a handover initiation flow mobility (HIF) message and a handover acknowledgment flow mobility (HAF) message are provided so that the tMAG can transmit a pre-PBU message and a PBU message to the LMA. Newly proposed. Details of these messages are described in more detail.

  In order to minimize end-to-end packet delay during IP flow transfer, in an embodiment of the present invention, no bi-directional IP tunnel is established between sMAG and tMAG during the period of IP flow transfer. That is, sMAG does not forward a copy of the IP packet to tMAG on the uplink or downlink IP packet flow that MN 10 wishes to transfer from the service radio access technology to the target radio access technology.

  Furthermore, to avoid packet loss on the serving radio network system or buffering on the target radio network system during the IP flow transfer period, the MN 10 has an L2 / L3 (layer 2 and layer 3) connection on the target radio network. Multiple radio interfaces are utilized simultaneously by maintaining both uplink and downlink paths on the serving radio network system until fully established on the system.

2.2 Structure of LMA (Local Mobility Anchor) FIG. 6 shows the physical structure of the LMA 26. The LMA 26 includes a transmission unit circuit 41, a reception unit circuit 42, a processor 43, and a memory 44. The transmitter circuit 41 transmits signals to the CN 28 and the MAG (for example, MAGs 16 and 22) under the control of the processor 43. The receiving unit circuit 42 receives signals from the CN 28 and the MAG (for example, the MAGs 16 and 22) under the control of the processor 43. The receiver circuit 42 controls the overall operation of the LMA 26. The memory 44 stores the BCE table shown in FIG. 4 and the FCE table shown in FIG.

  FIG. 7 shows the functional structure of the LMA 26 that can communicate with each MAG. As shown in FIG. 7, the LMA 26 includes an IP flow receiver 51, an IP flow transmitter 52, a pre-PBU receiver 53, a preliminary registration execution unit 54, a pre-PBA transmitter 55, and a PBU receiver 56. , A flow binding registration execution unit 57, a PBA transmission unit 58, a BRI transmission unit, and a 59 BRA reception unit 60.

  The IP flow receiving unit 51 is considered to be composed of a combination of the receiving unit circuit 42 and the processor 43, and receives the IP flow from the MAGs via the bidirectional IP tunnel. The IP flow transmission unit 52 is considered to be composed of a combination of the transmission unit circuit 41 and the processor 43, and transmits the IP flow to the MAG via the bidirectional IP tunnel.

  The pre-PBU receiving unit 53 (new connection request receiving unit) is regarded as a combination of the receiving unit circuit 42 and the processor 43. The pre-PBU receiving unit 53 receives a pre-PBU message (new connection request) from tMAG. The pre-PBU message indicates at least the MN-ID of the MN 10 to which the IP flow is to be transferred from the service radio access technology to the target radio access technology and the tMAG proxy CoA. The pre-PBU message may indicate MN-ID, MN-LL-ID, new BID, ATT, tMAG proxy CoA, and so on. The MN-LL-ID confirms the target wireless interface (for example, the 3G interface 31 or the WiFi interface 32) of the MN 10 used for transferring the IP flow. The new BID is used to identify a new binding created by the LMA 26. The new binding is a binding between the new HNP of the MN 10 assigned to the LMA 26 and the proxy CoA of the tMAG. ATT specifies the type of target access technology (eg, 3G or WiFi) that MN 10 will use in the future to connect to tMAG.

  The preliminary registration execution unit 54 (new connection registration unit) is regarded as the processor 43. When the pre-PBU reception unit 53 receives the pre-PBU message (new connection request), the preliminary registration execution unit 54 assigns a new HNP of the MN 10 to the MN 10. The MN 10 configures the home address (MN-HoA) of the mobile node used for communication between the target radio interface of the MN 10 and the tMAG from the HNP. The HNP itself is used for communication between tMAG and LMA 26. Thus, the HNP is used for communication between the target radio interface of the MN 10 and the LMA 26 via the target radio communication network system. The preliminary registration execution unit 54 executes preliminary registration. In this preliminary registration, the preliminary registration execution unit 54 registers a new binding between the new HNP and the tMAG proxy CoA. More specifically, in this preliminary registration, the preliminary registration execution unit 54 adds a new BCE (indicating the MN-ID, the new HNP, and the tMAG proxy CoA to the BCE table stored in the memory 44. Binding cache entry).

  The pre-PBA transmission unit 55 (new home network prefix transmission unit) is considered to be composed of a combination of the transmission unit circuit 41 and the processor 43. When the preliminary registration execution unit 54 completes the preliminary registration normally, the pre-PBA transmission unit 55 transmits a new HNP of the MN 10 to the tMAG in order to prompt establishment of a new bidirectional IP tunnel between the tMAG and the LMA 26. To do. More precisely, the pre-PBA transmission unit 55 transmits a pre-PBA (Pre-PBA: Pre-Proxy Binding Acknowledgment) message indicating that the pre-registration is successful and a new HNP of the MN 10.

  The PBU receiving unit 56 (flow binding update request receiving unit) is considered to be composed of a combination of the receiving unit circuit 42 and the processor 43. The PBU receiving unit 56 receives a PBU message (flow binding update request) from tMAG. The PBU message specifies the MN 10 that wants to transfer the IP flow from the service radio access technology to the target radio access technology, the tMAG proxy CoA, and the IP packet flow that the MN 10 wants to transfer from the service radio access technology to the target radio access technology. The PBU message may indicate the MN-ID of the MN 10, the MN-LL-ID that identifies the target radio interface, the BID, the ATT that specifies the type of the target access technology, the tMAG proxy CoA, and the FID. it can. The BID of the PBU message is a BID that identifies the binding between the HNP of the MN 10 and the proxy CoA of the tMAG used for the IP flow to be transferred, and this BID is an existing bidirectional IP between the tMAG and the LMA 26. In the existing BCE for establishing the tunnel, it is already associated with the MN 10. The FID of the PBU message is the FID present in the existing flow binding entry of the FCE table, and is associated with the IP flow that the MN 10 wishes to transfer from the service radio access technology to the target radio access technology. Thus, the FID identifies the IP packet flow to be transferred to tMAG.

  The flow binding registration execution unit 57 (flow binding registration unit) is regarded as the processor 43. The flow binding registration execution unit 57 associates the IP packet flow to be transferred to the tMAG with a new or existing bidirectional IP tunnel between the tMAG and the LMA 26 for the MN 10. The flow binding registration execution unit 57 executes flow binding registration. In this flow binding registration, the flow binding registration execution unit 57 is between the FID that identifies the IP packet flow to be transferred to the tMAG, and the HNP of the MN 10 and the tMAG proxy CoA that are newly used for the IP flow to be transferred. Register the binding with the new BID that identifies the binding. More specifically, the flow binding registration execution unit 57 updates the FCE including the FID in the FCE table stored in the memory 44 so that the previous BID is updated with a new BID. Therefore, the flow binding registration execution unit 57 registers the binding between the new or existing HNP of the MN 10 and the IP packet flow specified by the PBU message (flow binding update request).

  The PBA transmission unit 58 (flow binding completion report transmission unit) is considered to be composed of a combination of the transmission unit circuit 41 and the processor 43. When the flow binding registration execution unit 57 has successfully completed the flow binding registration, the PBA transmission unit 58 sends a PBA (proxy binding confirmation response) message (flow binding confirmation) indicating the completion of the flow binding registration in the flow binding registration execution unit 57. (Completion message) is sent to tMAG.

  The BRI transmitter 59 is considered to be composed of a combination of the transmitter circuit 41 and the processor 43. When the IP flow is successfully transferred from the sMAG to the tMAG, the BRI transmission unit 59 deletes the information related to the transferred IP flow in the sMAG, and the BRI (Binding Revocation Indication) defined in RFC5846 for the sMAG. Send a message. When the BRI is received, the sMAG deletes the information related to the transferred IP flow and returns it to the LMA 26 with a BRA (Binding Revocation Acknowledgment).

  The BRA receiving unit 60 is considered to be composed of a combination of the receiving unit circuit 42 and the processor 43. The BRA receiving unit 60 receives a BRA message.

2.3 Structure of MAG (Mobility Anchor Gateway) FIG. 8 shows the physical structure of each MAG. The MAG includes a transmitter circuit 71, a receiver circuit 72, a processor 73, and a memory 74. The transmitter circuit 71 transmits signals to the LMA 26, the MN 10, and other MAGs under the control of the processor 73. The receiver circuit 72 receives signals from the LMA 26, the MN 10, and other MAGs under the control of the processor 73. The receiver circuit 72 controls the overall activity of the MAG. The memory 74 stores a MAG proxy CoA and an IP flow mobility information list.

  FIG. 9 shows the functional structure of the MAG. As shown in FIG. 9, the MAG communicates with the MN 10 by an IP flow transmission unit 81, an IP flow reception unit 82, a flow mobility instruction reception unit 85, an interface activation unit 86, and a connection confirmation unit 87. RA transmission unit 100, RS reception unit 101, and flow movement completion reporting unit 102 are included. The MAG includes an IP flow receiver 83 for communicating with the LMA 26, an IP flow transmitter 84, a pre-PBU transmitter 93, a pre-PBA receiver 94, a PBU transmitter 95, a PBA receiver 96, and a BRI. A receiving unit 97 and a BRA transmitting unit 98 are included. The MAG includes an HIF transmission unit 89 for communicating with other MAGs, an HIF reception unit 90, an HAF transmission unit 91, and an HAF reception unit 92.

  The MAG also includes an information management unit 99 for managing information necessary for IP flow mobility. The information management unit 99 is regarded as the processor 73 and stores information necessary for IP flow mobility.

  The IP flow transmission unit 81 is considered to be a combination of the transmission unit circuit 71 and the processor 73, and transmits an IP flow to the MN 10. The IP flow receiving unit 82 is regarded as a combination of the receiving unit circuit 72 and the processor 73 and receives an IP flow from the MN 10. The IP flow receiving unit 83 is regarded as a combination of the receiving unit circuit 72 and the processor 73, and receives an IP flow from the LMA 26 via the bidirectional IP tunnel. The IP flow transmission unit 84 is considered to be composed of a combination of the transmission unit circuit 71 and the processor 73 and transmits the IP flow to the LMA 26 via the bidirectional IP tunnel. The IP flow transmitters 81 and 84 and the IP flow receivers 82 and 83 constitute a flow establishment unit. When the MAG is tMAG, the flow establishment unit transfers the IP packet flow that the MN 10 wants to transfer from the service radio access technology to the target radio access technology, the connection between the target radio interface of the MN 10 and the tMAG, and between the tMAG and the LMA 26. Established using a two-way IP tunnel.

  When the MAG is sMAG, the flow mobility instruction reception unit 85, the interface activation unit 86, the HIF transmission unit 89, the HAF reception unit 92, the BRI reception unit 97, and the BRA transmission unit 98 are used. When MAG is tMAG, RA transmission unit 100, RS reception unit 101, flow movement completion report unit 102, HAF transmission unit 91, HIF reception unit 90, pre-PBU transmission unit 93, and pre-PBA reception A unit 94, a connection confirmation unit 87, a PBU transmission unit 95, and a PBA reception unit 96 are used.

  The flow mobility instruction receiving unit 85 (flow transfer instruction receiving unit) is considered to be composed of a combination of the receiving unit circuit 72 and the processor 73. When the MAG is sMAG, the flow mobility instruction receiving unit 85 receives a flow mobility instruction message (Flow Transfer Indication) from the MN 10. In the flow mobility instruction message, at least one IP packet flow is established between the service radio interface of the MN 10 and the LMA 26 via the service radio communication network system, and the MN 10 has at least one already established IP packet. Sent from the MN 10 when it is desired to move (ie, relocate) the flow from the service radio access technology to the target radio access technology.

  The flow mobility indication message is an L2 (layer 2) trigger and identifies the mobile node and at least one IP packet flow that the mobile node wishes to transfer from the service radio access technology to the target radio access technology. The flow mobility instruction message includes current state information indicating whether the target radio interface is currently activated. The flow mobility indication message may also include desired operation information indicating whether the service radio interface should be deactivated from the activated state after completion of IP flow transfer. In short, the flow mobility instruction message may indicate the MN-ID of the MN 10, the address of the tMAG, information on the current state and desired operation of the radio interface, and at least one FID. The flow mobility instruction receiving unit 85 checks information on the current state and desired operation of the radio interface, and based on the information on the current state and desired operation of the radio interface, the IP flow handover of the specified IP flow Determine the type of (IP flow transfer).

  The HIF transmission unit 89 (flow transfer request transmission unit) is regarded as a combination of the transmission unit circuit 71 and the processor 73. When the MAG is sMAG, when the flow mobility instruction receiving unit 85 receives the flow mobility instruction message (flow transfer instruction), the HIF transmission unit 89 transmits the HIF message (flow transfer request) to the tMAG. HIF is an abbreviation for “Handover Initiate for Flow mobility”.

  The HIF message specifies the MN 10 specified by the flow mobility instruction message and the IP packet flow that the MN 10 wishes to transfer from the service radio access technology to the target radio access technology. The HIF message instructs the tMAG to send a pre-PBU message (new connection request) to the LMA 26 when the current state information of the flow mobility indication message indicates that the target radio interface is not currently activated. A first transmission instruction may be included. The HIF message instructs the tMAG to send a PBU message (flow binding update request) to the LMA 26 when the current state information of the flow mobility indication message indicates that the target radio interface is currently activated. Two transmission instructions can be included. In short, the HIF message includes the MN-ID for identifying the MN 10, the MN-LL-ID for identifying the target radio interface, the address (LMAA) of the LMA 26, the FID corresponding to the IP flow to be transferred, and the radio interface. Information on the current state and desired operation of the user and a first transmission instruction or a second transmission instruction. The HIF message can also indicate the traffic selector corresponding to the designated IP flow and the flow type of the IP flow.

  The HIF transmission unit 89 determines that the first transmission instruction or the second transmission instruction should be included in the HIF message based on the type of IP flow handover determined by the flow mobility instruction reception unit 85. More specifically, if the information on the current state and desired operation of the radio interface includes current state information indicating that the target radio interface is not currently activated, the flow mobility instruction receiving unit 85 It is determined that the type of handover involves a new connection (new connection) of the MN 10 to the target wireless network system. In this case, the HIF transmission unit 89 transmits the first transmission instruction. When the information regarding the current state of the radio interface and the desired operation includes the current state information indicating that the target radio interface is currently activated, the flow mobility instruction receiving unit 85 indicates that the type of IP flow handover is The MN 10 decides not to be accompanied by a new connection (new connection) to the target wireless network system. In this case, the HIF transmission unit 89 transmits the second transmission instruction.

  The HIF receiver 90 (flow transfer request receiver) is considered to be composed of a combination of the receiver circuit 72 and the processor 73. When the MAG is tMAG, the HIF receiving unit 90 receives the HIF message (flow transfer request) from the sMAG. Based on the HIF message (particularly, the first or second transmission instruction), the HIF receiving unit 90 determines that the pre-PBU message or the PBU message should be transmitted to the LMA 26.

  The pre-PBU transmission unit 93 (new connection request transmission unit) is regarded as a combination of the transmission unit circuit 71 and the processor 73. When the MAG is tMAG, the pre-PBU transmission unit 93 transmits a pre-PBU message (new connection request) to the LMA 26 when the HIF message received by the HIF reception unit 90 includes the first transmission instruction. As described above, the pre-PBU message includes the MN-ID of the MN 10, the MN-LL-ID that identifies the target radio interface, the new BID for the new binding, the ATT that specifies the type of the target access technology, and the tMAG. Proxy CoA or the like may be indicated.

  The pre-PBA reception unit 94 (new home network prefix reception unit) is considered to be composed of a combination of the reception unit circuit 72 and the processor 73. When the MAG is tMAG, the pre-PBA receiving unit 94 receives the pre-PBA message sent from the LMA 26 in response to the pre-PBU message after completion of the preliminary registration. As described above, the pre-PBA message indicates that the preliminary registration has been successful and the new MN 10 HNP. After exchanging the pre-PBU message and the pre-PBA message between tMAG and LMA, the IP flow reception unit 51 and IP flow transmission unit 52 of LMA 26, and the IP flow reception unit 83 and IP flow transmission unit 84 of tMAG are: Communication can be performed using a bidirectional IP tunnel between tMAG and LMA.

  The HAF transmitter 91 (registration completion report transmitter) is considered to be composed of a combination of the transmitter circuit 71 and the processor 73. HAF is an abbreviation for “Handover Acknowledge for Flow mobility”. When the MAG is tMAG, when the pre-PBA reception unit 94 receives a pre-PBU message from the LMA 26 or the PBA reception unit 96 receives a PBU message from the LMA 26, the HAF transmission unit 91 transmits the HAF message to the sMAG. To do.

  The behavior of the HAF transmission unit 91 depends on the content of the HIF message received by the HIF reception unit 90. When the HIF message indicates the first transmission instruction, the type of IP flow handover involves a new connection (new connection) of the MN 10 to the target wireless network system. In this case, when receiving the pre-PBA message, the HAF transmission unit 91 transmits the HAF message and does not act according to the PBA message. In this case, the HAF message indicates that the new bidirectional IP tunnel for the new connection of the MN 10 to the target wireless network system has been completed, and the target of the MN 10 specified by the MN-LL-ID in the HIF message. It includes an instruction to the MN 10 to activate the wireless interface. In this case, the HAF transmission unit 91 is a new IP tunnel completion report transmission unit. When the pre-PBA reception unit 94 receives a new HNP of the MN 10, the HAF transmission unit 91 establishes a connection between the target radio interface of the MN 10 and the tMAG. It is an interface activation unit on tMAG for activating the target radio interface of MN10.

  The HAF receiving unit 92 (registration completion report receiving unit) is regarded as comprising a combination of the receiving unit circuit 72 and the processor 73. When the MAG is sMAG, the HAF receiving unit 92 receives the HAF message from tMAG.

  The other interface activation unit 86 is regarded as a combination of the transmission unit circuit 71 and the processor 73. When the MAG is an sMAG, when the HAF message indicating the instruction to the sMAG to activate the target radio interface of the MN 10 is received by the HAF receiving unit 92, the interface activation unit 86 sends the target interface action to the service radio interface of the MN 10. (Target Interface Action) Send a message. The target interface action message is an L2 trigger for activating the target radio interface of the MN 10 to prompt the establishment of a tMAG connection with the target radio interface of the MN 10.

  The connection confirmation unit 87 is regarded as a combination of the reception unit circuit 72 and the processor 73. When the MAG is tMAG, the connection confirmation unit 87 confirms the establishment of the L2 connection between the target wireless interface of the MN 10 and the tMAG. Therefore, tMAG confirms the new connection of MN 10 to the target wireless network system.

  The PBU transmission unit 95 (flow binding update request transmission unit) is considered to be composed of a combination of the transmission unit circuit 71 and the processor 73. When the MAG is tMAG, the PBU transmission unit 95 transmits a PBU message (flow binding update request) to the LMA 26 when the connection confirmation unit 87 confirms the establishment of the connection. When the HIF receiving unit 90 receives the HIF message including the second transmission instruction, the PBU transmitting unit 95 also transmits the PBU message to the LMA 26. In any case, the PBU message contains the MN-ID of the MN 10, the MN-LL-ID that identifies the target radio interface, the new BID of the new binding, the ATT that specifies the type of the target access technology, the proxy CoA of the tMAG, the transfer The FID corresponding to the IP flow to be performed can be indicated.

  The PBA receiver 96 (flow binding completion report receiver) is considered to be composed of a combination of the receiver circuit 72 and the processor 73. When the MAG is tMAG, the PBA receiving unit 96 receives from the LMA 26 a PBA message (flow binding completion message) indicating the completion of flow binding registration.

  The RA transmitter 100 is regarded as comprising a combination of a transmitter circuit 71 and a processor 73. When the MAG is tMAG, after receiving the PBA message by the PBA receiving unit 96, the RA transmitting unit 100 notifies the MN 10 of the existence of the tMAG and also uses the RA (Router) to notify the MN 10 of the new HNP of the MN 10. Advertisement) message is sent to the target wireless interface of MN10. The RA transmitter 100 operates only when the IP flow handover type involves a new connection (new connection) of the MN 10 to the target wireless network system. That is, when the information regarding the current state and desired operation of the radio interface in the HIF message includes current state information indicating that the target radio interface is currently activated, or the HIF message indicates the second transmission instruction. In that case, the RA transmission unit 100 transmits an RA message. When receiving the PBA message, the RA transmission unit 100 may periodically transmit the RA message. Alternatively, when a PBA message has already been received, the RA transmission unit 100 may transmit an RA message according to an RS (Router Solicitation) message received by the RS reception unit 101.

  The RS receiving unit 101 is considered to be composed of a combination of the receiving unit circuit 72 and the processor 73. When the MAG is tMAG, the RS receiver 101 may receive an RS message from the MN 10. The RS message is sent from the MN 10 after the establishment of the L2 connection in order to request the message transmission from the RA to the tMAG.

  The flow movement completion report unit 102 is regarded as a combination of the transmission unit circuit 71 and the processor 73. When the MAG is tMAG, after the transmission of the RA message from the RA transmission unit 100, the flow movement completion reporting unit 102 transmits the flow movement completion message to the MN 10. The flow movement completion message is an L2 trigger for notifying the MN 10 of the completion of the flow movement (flow transfer) from the service radio network system to the target radio network system. After receiving the flow movement completion message at the MN 10, the MN 10 can transmit the uplink packet of the designated IP flow to the CN 28 via the target radio network system and the LMA 26, and pass through the target radio network system and the LMA 26. Thus, the downlink packet of the designated IP flow can be received from the CN 28. After sending the flow movement completion message to the MN 10, the flow establishment unit (the IP flow transmission units 81 and 84 and the IP flow reception units 82 and 83) connects the connection between the target radio interface of the MN 10 and the tMAG, and the tMAG and the LMA 26. A specified IP packet flow is established using a bi-directional IP tunnel to and from.

  The BRI receiving unit 97 is considered to be a combination of the receiving unit circuit 72 and the processor 73. When the MAG is sMAG, when the designated IP flow is normally transferred from the service radio network system to the target radio network system, the BRI receiving unit 97 receives a BRI (Binding Revocation Indication) message from the LMA 26. When the BRI message is received by the BRI receiving unit 97, the information management unit 99 deletes the information regarding the transferred IP flow stored in the memory 74.

  The BRA transmission unit 98 is considered to be composed of a combination of the transmission unit circuit 71 and the processor 73. When the MAG is sMAG, when the information management unit 99 deletes information related to the IP flow transferred in response to the BRI message, the BRA transmission unit 98 responds to the LMA 26 with a BRA (Binding Revocation Acknowledgement) message.

  As described above, the behavior of the tMAG HAF transmission unit 91 (registration completion report transmission unit) depends on the content of the HIF message received by the HIF reception unit 90. If the HIF message indicates a second transmission instruction, the type of IP flow handover does not include a new connection (new connection) of the MN 10 to the target wireless network system. In this case, when receiving the PBA message from the LMA 26, the HAF transmission unit 91 transmits the HAF message. In this case, the HAF message indicates completion of the movement (transfer) of the specified IP flow, but does not include an instruction to the MN 10 to activate the target radio interface of the MN 10. This is because the target radio interface has already been activated.

  Further, after transmitting the HAF message without an instruction to activate the target wireless interface of the MN 10, the flow movement completion reporting unit 102 moves the flow from the service wireless network system to the target wireless network system (flow transfer). ) Is transmitted to the MN 10 in order to notify the MN 10 of the completion. After receiving the flow movement completion message at the MN 10, the MN 10 can transmit the uplink packet of the designated IP flow to the CN 28 via the target radio network system and the LMA 26, and pass through the target radio network system and the LMA 26. The downlink packet of the designated IP flow can be received from the CN 28. After transmitting the flow movement completion message to the MN 10, the flow establishment unit (the IP flow transmission units 81 and 84 and the IP flow reception units 82 and 83) establishes the connection between the target radio interface of the MN 10 and the tMAG, and the tMAG and the LMA 26 Establish a designated IP packet flow using a connection between two-way IP tunnels between the two.

  FIG. 10 shows an example of the binding update list table stored in the memory 74 of each MAG in order to manage the movement of the MN 10 to and from the wireless communication network system. The binding update list table includes a plurality of records. Each record includes the MN-ID for identifying the MN 10, the MN-LL-ID for identifying the radio interface of the MN 10, the home network prefix of the MN 10, the address of the LMA 26 (LMAA), and the binding indicated by this record. It includes a BID (binding ID) for identification.

  FIG. 11 shows an example of a flow binding update list table stored in the memory 74 of each MAG in order to manage the movement (transfer) of the IP flow. The flow binding update list includes a plurality of records. Each record includes an MN-ID for identifying the MN 10, an FID (flow ID) corresponding to the IP flow, a traffic selector corresponding to the IP flow, and a flow type of the IP flow.

  According to an embodiment of the present invention, the MN 10 sends a flow mobility indication message identifying at least one IP flow that the MN 10 wishes to transfer from the service radio access technology to the target radio access technology. Whenever the radio environment around the MN 10 changes (eg, when the MN enters or leaves a zone where both WiFi and 3G wireless technologies are available), the user of the MN 10 determines the IP flow to be transferred. May be. Thus, the MN can interact with the user to prompt one or more IP flows to be transferred whenever the wireless environment changes.

  Alternatively, the MN 10 may automatically determine the IP flow to be transferred based on the stored contents stored in the MN 10 reflecting the user policy. FIG. 12 shows a local policy profile table that can be stored in each MN 10. The local policy profile table includes a plurality of records, each of which includes a flow ID of the IP flow, a priority of the IP flow, a traffic selector corresponding to the IP flow, a flow movement policy, and a flow of the IP flow. The type may be included. In the flow transfer policy, “3G to WiFi” means that once the MN 10 enters a zone where both WiFi and 3G wireless technologies are available, the IP flow wireless access technology should be changed from 3G to WiFi. It is possible to set the flow transfer policy of all IP flows from “3G to WiFi”. In the flow movement policy, “depending on network state” means that when the MN 10 enters a zone where both WiFi and 3G radio technologies are available, the radio access technology of the IP flow depends on the strength of the 3G signal and the strength of the WiFi signal. Means to be changed or maintained.

  The user of the MN 10 can set each record in the local policy profile table. Therefore, the MN 10 can automatically determine the IP flow to be transferred according to the user's intention.

2.4 Messages sent between MAGs This embodiment uses a new mobility header message to support mobile-driven flow mobility in a PMIPv6 environment. The new mobility header message is a HIF (Handover Initiate for Flow mobility) message transmitted from sMAG to tMAG and a HAF (Handover Acknowledgment for Flow mobility) message transmitted from tMAG to sMAG. The HIF message indicates the current state of the radio interface of the MN 10 to which the IP flow is to be transferred, and includes interface state and operation information (interface action information) indicating a desired operation of the radio interface of the MN 10. The interface state and operation information is the above-described information regarding the current state and desired operation of the wireless interface. The flow mobility instruction message sent from the MN 10 to the sMAG may also include interface state and operation information, but is not limited thereto.

2.4.1 Mobility header message (1) HIF (Handover Initiate for Flow mobility)
The HIF message is an extended version of the HI (Handover Initiate) message and is defined in RFC 5949 (F-PMIPv6). The HI message defined by RFC5949 is an extended version of the HI message defined by RFC5568. FIG. 13 illustrates the format of the HIF message.

  The IP address (not shown) of the HIF message should indicate the source address (sMAG IP address) and the destination address (tMAG IP address).

  The message data of the HIF message includes a sequence number, “S” flag, “U” flag, “P” flag, “F” flag, “M” flag, “R” flag, reserved field, , And a code field. The sequence number is the same as that of the RFC5568 HI message and should be set in the transmission side (sMAG). The “S” flag is an allocated address configuration flag defined in the HI message in RFC5568, and should be set to zero in this embodiment. The “U” flag is a buffer flag defined in the HI message by RFC5568, and should be set to zero in this embodiment. The “P” flag is a proxy flag defined in the HI message by RFC5949, and should be set to zero in this embodiment. The “F” flag is a transfer flag defined for the HI message in RFC5949, and should be set to zero in this embodiment.

  The “M” flag, the “R” flag, and the code field are improved HIF messages relative to the conventional RFC5568 and RFC5949 HI messages. The “M” flag is a flow mobility support flag, and is used to distinguish the message from the HIF message defined in RFC5568 and RFC5949. Should be set to 1 if the message is used for designated IP flow transfer according to this embodiment.

  The “R” flag is a registration flag. If sMAG requires tMAG to send a pre-PBU message to LMA 26 for pre-registration, this flag should be set to zero in this embodiment. On the other hand, if sMAG requests tMAG to send a PBU message to LMA 26 for flow binding registration, this flag should be set to 1 in this embodiment. In the first transmission instruction, the “R” flag is set to zero, and in the second transmission instruction, the “R” flag is set to 1.

  According to this embodiment, the initial binding registration defined in RFC5213 is for a designated IP flow move (relocation) with two steps, ie, a new connection (new connection) of the MN 10 to the target wireless network system. Can be divided into preliminary registration and flow binding registration. In the designated IP flow movement (transfer) that does not require a new connection (new connection) of the MN 10 to the target wireless network system, only flow binding registration is executed.

  If the MN is not connected to the target wireless network system, sMAG sends a HIF message with an “R” flag set to zero, and tMAG sends a pre-PBU message to the LMA. Then, the LMA 26 performs preliminary registration. In pre-registration, the LMA allocates a new HNP, creates a new binding cache entry for a new binding between the HNP and the tMAG proxy CoA of the target wireless network system with the new BID, tMAG A new connection process of the MN such as establishment of a bidirectional IP tunnel between the LMA and the LMA is executed. A new binding cache entry is added to the BCE table.

  If the MN is already connected to the target radio network system, sMAG sends a HIF message containing an “R” flag set to 1 and tMAG is assigned to the PBU from the service radio network system to the target radio network system In order to move the IP flow, a message including an FID (flow ID) corresponding to the designated IP flow is transmitted to the LMA. Then, the LMA 26 performs flow binding registration. In flow binding registration, the LMA adds an existing flow binding cache entry to the FCE table, or changes the previous BID to a new BID, thereby changing the existing flow of the IP flow corresponding to the FID. Perform a binding cache entry update.

  By separating into two steps in this way, handover delay is minimized, and it is possible to avoid missing IP packets and buffering, thereby significantly improving handover performance when moving IP flows. . This is because a specified IP flow that is determined to move from a service radio network system to a target radio network system can be transferred to a service radio network system by enabling a plurality of interfaces to be used simultaneously until the flow binding registration is completed. It is because it maintains through. In contrast to the present embodiment, when a new connection process and a flow binding registration process are executed at a time by exchanging PBU and PBA, not only packet loss but also handover delay inevitably increases.

  The reserved field is the same as in the RFC5568 HI message and should be set to zero by the sender (sMAG) so that it will be ignored by the receiver (tMAG). In the case of a conventional HI message, RFC 5568 defines the code field and its values “0” and “1” for specific purposes. In addition, RFC 5949 defines code values “2” and “3” for other specific purposes in the HI message. In the present embodiment, when the “M” flag is 1, the code field is set to “4” or “5”.

If the “M” flag is set to 1 (identifies that the message is used for the specified IP flow movement), the code value 4 is set, and the “R” flag is zero (instructed to send a pre-PBU message) ). In this case, upon receiving the HAF message, the tMAG should transmit a pre-PBU message that does not indicate one or more FIDs corresponding to the one or more IP flows to be transferred to the LMA. Accordingly, the code value 4 indicates “no FID” and is used for a new connection of the MN due to the pre-PBU message without the FID.

  If the “M” flag is set to 1 (identifies that the message is used for the specified IP flow movement), the code value 5 is set, and the “R” flag is set to 1 (PBU message transmission). Set to). In this case, when the tMAG receives the HAF message, the tMAG should send a PBU message indicating one or more FIDs corresponding to the one or more IP flows to be transferred to the LMA. Therefore, the code value 5 indicates “with FID” and is used for an instruction to move the designated IP flow caused by the PBU message with FID.

  The mobility option field contains one or more mobility options, the encoding and format of which is specified in RFC3775. The mobility options included in this field of the HIF message and required for the specified IP flow movement in this embodiment are the mobile node identifier (MN-ID) option and the local mobility anchor address (LMAA). ) Option, mobile node link local identifier (MN-LL-ID) option, flow identifier option, traffic selector (TS) option, flow summary option, and interface action (IA) option. The MN-ID option, the LMAA option, and the MN-LL-ID option are defined in RFC5213. The FID option, TS option, and flow summary option are defined in RFC6089. The interface action (IA) option is newly defined in this embodiment as will be described in detail later. The IA option can be referred to as interface state and operation information.

(2) HAF (Handover Acknowledgment for Flow mobility)
The HAF message is an extended version of a HAck (Handover Acknowledge) message, and is defined by RFC5949 (F-PMIPv6). The HAck message defined by RFC5949 is an extended version of the HAck message defined by RFC5568. FIG. 14 illustrates the format of the HAF message.

  The IP field (not shown) of the HAF message should indicate the source address (IP address of tMAG) and the destination address (IP address of sMAG).

  The message data of the HIF message includes a sequence number, “U” flag, “P” flag, “F” flag, “M” flag, “T” flag, reserved field, and code field. . The sequence number is the same as in the case of the RFC5568 HAck message, and should be copied from the corresponding field in the HAF message to which this HIF message is a response. The “U” flag is a buffer flag defined for the HAck message in RFC5949, and should be set to zero in this embodiment. The “P” flag is a proxy flag defined for the HAck message in RFC5949, and should be set to zero in this embodiment. The “F” flag is a transfer flag defined for the HAck message in RFC5949, and should be set to zero in this embodiment.

  The “M” flag, “T” flag, and code field are improved HAF messages relative to the conventional HAck message in RFC5568 and RFC5949. The “M” flag is a flow mobility support flag, and is used to distinguish the message from the HAck message defined by RFC5568 and RFC5949. Should be set to

  The “T” flag is an L2 trigger flag. When the “T” flag is set to 1, the “T” flag is used to send an L2 trigger (target interface action message) to the MN to activate the MN's target radio interface. sMAG). More specifically, when tMAG receives an HIF message (first transmission instruction) in which the “M” flag is set to 1 and the “R” flag is set to zero, tMAG You must reply to sMAG by sending a message. In this case, the “T” flag is set to 1 after completing the pre-registration process by establishing a bi-directional IP tunnel between tMAG and LMA (or upon receiving a pre-PBA from LMA). When the sMAG receives a HAF message with the “T” flag set to 1, the sMAG should send an L2 trigger (target interface action message) to the MN, which causes the MN's target radio interface to be Activate. Therefore, as described above, the tMAG HAF transmitter 91 receives the MN 10 only when the HIF message (flow transfer request) received by the tMAG HIF receiver 90 (flow transfer request receiver) includes the first transmission instruction. Functions as an interface activation unit on the tMAG for activating the target wireless interface.

  On the other hand, if the tMAG receives the HIF message (second transmission instruction) in which the “M” flag is set to 1 and the “R” flag is set to 1, the tMAG transmits the HAF message. Should be sent back to sMAG. In this HAF message, the “T” flag is set to zero after completion of flow binding registration (when a PBA message is received from the LMA). When the sMAG receives a HAF message with the “T” flag set to zero, the sMAG should not send an L2 trigger (target interface action message) to the MN. This is because when the tMAG receives the HIF message (second transmission instruction), the target radio interface has already been activated.

  The reserved field is the same as in the RFC5568 HAck message and should be set to zero by the sender (tMAG) and ignored by the receiver (sMAG).

  For conventional HAck messages, RFC 5568 defines the code field and its value, “0” to “4” and “128” to “130” for specific purposes. Further, for HAck messages, RFC 5949 defines code values “0”, “5”, “6”, and “129” through “132” for specific purposes. Thus, code values “0” to “6” and “128” to “132” are defined in RFC5568 and RFC5949. In the present embodiment, the code field is set to “7”, “8”, “133”, or “134” by setting “1” to the “M” flag.

  A code value of 7 means that the preliminary registration has been completed normally. A code value of 8 means that the flow binding registration has been completed normally (all requested FIDs have been updated or added normally). Code value 133 means that the pre-registration was not accepted. Code value 134 means that the flow binding registration was not accepted.

  The mobility option field includes one or more mobility options. This encoding and format is defined in RFC3775.

2.4.2 Interface action information In this embodiment, the HIF message transmitted from the sMAG to the tMAG indicates the current state of the radio interface of the MN 10 and the interface state and operation indicating the desired operation of the radio interface of the MN 10 Information (IA option). Thus, the interface state and operation information indicates the type of IP flow handover of the MN.
FIG. 15 illustrates the format of interface state and operation information in the HIF message. Interface state and operation information includes an option type field, an option length field, a target interface action (TIA) field, a service interface action (SIA) field, and a target interface field. It includes a status (TIS) field and a service interface status (SIS) field. The option type field indicates that this information is interface state and operation information (IA option). The option length field indicates the length of this information (not including the option type field and the option length field) in octets.

  The Target Interface Action (TIA) field indicates the desired operation of the MN's target radio interface after completion of the IP flow transfer. When this field is zero, the target radio interface should be inactive. (If the target radio interface is active, it should be deactivated. If the target radio interface is inactive, the inactive state should be maintained.) If this field is 1, The target radio interface should be active. (If the target radio interface is inactive, it should be activated. If the target radio interface is active, the active state should be maintained).

  The Service Interface Action (SIA) field indicates the desired operation of the MN's service radio interface after completion of the IP flow transfer. If this field is zero, the service radio interface should be inactive. (If the service radio interface is active, it should be deactivated. If the service radio interface is inactive, it should remain inactive.) If this field is 1 The service radio interface should be active. (If the service radio interface is inactive, it should be activated. If the service radio interface is active, the active state should be maintained).

  The target interface status (TIS) field indicates the current state of the target radio interface. If this field is zero, the target radio interface is currently inactive. If this field is 1, the target radio interface is currently active.

  The service interface status (SIS) field indicates the current state of the service radio interface. If this field is zero, the service radio interface is currently inactive. If this field is 1, the service radio interface is currently active.

2.5 Operation Four scenarios will be described as an example of the operation of the mobile device initiative type IP flow mobility based on PMIPv6 according to the present embodiment.

2.5.1 First scenario (new connection with selected IP flow transfer)
FIG. 16 shows a first scenario. The first scenario involves a new connection of the MN 10 to the target radio network system and transfer of the selected (designated) IP flow from the service radio network system to the target radio network system. In this scenario, the MN is initially connected to the 3G network system 12 and the MN should be newly connected to the WiFi network system 18. Accordingly, the 3G network system 12 is a service wireless network system, and the WiFi network system 18 is a target wireless network system. The MN's 3G interface 31 is a service radio interface, and the MN's WiFi interface 32 is a target radio interface.

  In the first stage, the MN 10 is located in the zone 13 where the 3G technology can be used, and is not located in the zone 19 where the WiFi technology can be used. The MN 10 has already established two or more IP flows (for example, IP flows F1 and F2) toward the LMA 26 via the 3G network system 12. While the WiFi interface 32 (target wireless interface) is inactive, the 3G interface 31 (service wireless interface) is active. All IP flows are communicated via the 3G network system 12.

  Here, the MN moves to the overlapping zone where the 3G zone 13 and the WiFi zone 19 overlap, and the MN processor 33 maintains the IP flow F1 with the 3G technology, while the 3G technology (service radio access technology) to the WiFi. Suppose we decide to transfer IP flow F2 to the technology (target radio access technology). As described above, this determination may be made automatically based on the local policy profile table (FIG. 12), but may also be made based on interaction between the MN 10 and the user of the MN 10. In any case, this decision reflects the user's intention that the IP flow F2 should be transferred to the WiFi technology when the WiFi radio technology is available. In this scenario, the WiFi interface 32 (target radio interface) should be activated from the inactive state (switch switched on) and the 3G interface 31 (service radio interface) should remain active. .

  The MN 10 transmits information on the current state and desired operation of the radio interface and information on the IP flow (IP flow F2) selected as the target to be transferred from the service radio network system to the target radio network system. The network side performs a new connection of the MN 10 to the target wireless network system and transfers the designated IP flow according to the intention of the MN on behalf of the MN.

17 and 18 are information flow diagrams showing a series of events in the first scenario.
The series of events is described in detail below.

  (A) All IP flows between the MN 10 and the CN (partner node) 28 are bidirectional IP tunnels established between the 3G interface 31 of the MN 10, the sMAG 16 in the 3G network system 12, and the sMAG 16 and the LMA 26. And established through.

  (B) The processor 33 of the MN 10 determines that the IP flow F2 should be transferred from the 3G network system 12 (service radio network system) to the WiFi network system 18 (target radio network system). The MN 10 transmits a flow mobility instruction message (flow transfer instruction) to the sMAG 16. The flow mobility instruction message is information that reflects the user's intention such as the MN-ID of the MN 10, the address of the tMAG 22, the current state of the radio interface and the desired operation, and the FID corresponding to the IP flow F2 to be transferred. including. The information regarding the current state and desired operation of the radio interface indicated by the flow mobility instruction message may or may not be the interface state and operation information described above. In this scenario, the information should indicate that the 3G interface 31 (service radio interface) is kept active and the WiFi interface 32 (target radio interface) should be activated from the inactive state.

  (C) When the flow mobility instruction receiving unit 85 of the sMAG 16 receives the L2 trigger, that is, the flow mobility instruction receiving message from the MN 10, the flow mobility instruction receiving unit 85 of the sMAG 16 first determines the type of IP flow handover. Check the information about the current state of the radio interface and the desired operation. In this scenario, since the interface 31 (service radio interface) should be kept active, it is determined that the 3G network system 12 (service radio network system) should continue to be used after the transfer of the selected IP flow. Also, since the WiFi interface 32 (target radio interface) should be activated from an inactive state, a new connection (new connection) of the MN 10 to the target radio network system is set as the IP flow handover type. It is decided to accompany.

  Next, the HIF transmission unit 89 of the sMAG 16 transmits the HIF message to the tMAG 22. This HIF message indicates the first transmission instruction so that the LMA 26 executes the preliminary registration of the MN 10. In the HIF message, the “M” flag is set to 1 indicating that this message is used for the specified IP flow movement, and the “R” flag requests the tMAG 22 to send a pre-PBU message to the LMA 26. Set to zero for. The code value is “4” indicating “no FID” used for a new connection of the MN 10. The HIF message includes an MN-ID that identifies the MN 10, an MN-LL-ID that identifies the WiFi interface 32 (target radio interface), an address of the LMA 26 (LMAA), and an ID corresponding to the selected IP flow to be transferred. And a traffic selector corresponding to the selected IP flow, and interface state and operation information. In order to construct the HIF message, the HIF transmission unit 89 of the sMAG 16 reads the MN-LL-ID and LMAA from the binding update list table (FIG. 10), and reads the traffic selector from the flow binding update list table (FIG. 11). .

  (D) When the HIF receiver 90 of the tMAG 22 receives the HIF message in which the “M” and “R” flags are set to 1 and 0 and the code value is “4”, the pre-PBU transmitter 93 of the tMAG 22 Transmits a pre-PBU message (new connection request) to the LMA 26 so that the MN 10 performs preliminary registration. The pre-PBU message indicates the MN-ID of the MN 10, the MN-LL-ID that identifies the target radio interface, the new BID for the new binding, the ATT that specifies the type of the target access technology, the proxy CoA of the tMAG 22, and the like. Since the preliminary registration in the LMA 26 does not use the FID, the pre-PBU message does not indicate the FID indicated by the HIF message. Instead, the FID is used in flow binding registration to update or register the specified flow.

  At this time, the information management unit 99 of the tMAG 22 adds a new record for new connection to the binding update list table (FIG. 10). However, the HNP of the new record is empty.

  When the pre-PBU receiving unit 53 of the LMA 26 receives the pre-PBU message from the tMAG 22, the pre-registration execution unit 54 of the LMA 26 assigns the new HNP of the MN 10 to the WiFi interface 32 (target radio interface) of the MN 10, and the new HNP and tMAG 22 Add a new binding to the proxy CoA. More specifically, the preliminary registration execution unit 54 adds a new binding cache entry to the BCE table (FIG. 4). The contents of this new binding cache entry are the contents of the new HNP and pre-PBU messages.

  When the preliminary registration of the new connection of the MN is normally completed, the pre-PBA transmission unit 55 of the LMA 26 transmits a pre-PBA message indicating the new HNP of the MN 10 to the tMAG 22. As a result of receiving a new HNP of the MN 10 at tMAG 22, a new bidirectional IP tunnel is established between tMAG 22 and LMA 26. At this time, the information management unit 99 of the tMAG 22 adds the new HNP of the MN 10 to the new record for new connection in the binding update list table (FIG. 10).

  (E) When the pre-PBA reception unit 94 of the tMAG 22 receives the pre-PBA message indicating that the preliminary registration has been normally completed, the HAF transmission unit 91 of the tMAG 22 transmits the HAF message to the sMAG 16. In the HAF message, the code value is set to “7”, which means normal termination of the new connection of the MN 10 to the WiFi network system 18 (target wireless network system). In the HAF message, the “M” flag is set to 1 indicating that this message will be used for the specified IP flow movement, and the “T” flag also causes sMAG 16 to trigger L2 trigger (target interface action message). Set to 1 to activate the target radio interface of the MN by sending to the MN.

  (F) When the HAF receiving unit 92 of the sMAG 16 receives a HAF message indicating an instruction to the sMAG to activate the target wireless interface of the MN 10, the interface activation unit 86 of the sMAG 16 causes the WiFi interface 32 (target wireless interface ) Is activated (switch is turned on), a target interface action message is transmitted to the 3G interface 31 (service radio interface) of the MN 10.

  (G) After switching on the WiFi interface 32 (target wireless interface), the MN 10 establishes a link layer connection with the WiFi network system 18 (target wireless network system) for a new connection of the MN 10.

  (H) When the connection confirmation unit 87 of the tMAG 22 confirms that the L2 connection between the WiFi interface 32 (target wireless interface) of the MN 10 and the tMAG 22 has been successfully established, the PBU transmission unit 95 of the tMAG 22 causes the LMA 26 to register the flow binding. A PBU message is transmitted to the LMA 26 so as to execute. The PBU message indicates the FID corresponding to the selected IP flow to be transferred indicated in the HIF message from sMAG. Further, the information management unit 99 of the tMAG 22 adds a new record including the FID in the flow binding update list table (FIG. 11).

  When the PBU receiving unit 56 of the LMA 26 receives the PBU message indicating the FID from the tMAG 22, the flow binding registration executing unit 57 of the LMA 26 uses the FID in the FCE table (FIG. 5) so that the previous BID is updated with the new BID. Update an existing FCE (Flow Binding Cache Entry) that contains it. In this way, the new HNP of the MN 10 of the new binding cache entry in the BCE table (FIG. 4) is associated with the IP packet flow corresponding to the FID via the BID, so that the IP packet flow becomes the new HNP. Is associated with a new bidirectional IP tunnel corresponding to.

  When the flow binding registration of the transfer of the selected IP flow is normally completed, the PBA transmission unit 58 of the LMA 26 transmits a PBA message to the tMAG 22.

  (I) When the PBA message is received by the PBA receiver 96 of the tMAG 22, the RA transmitter 100 of the tMAG 22 transmits an RA (Router Advertisement) message to the MN 10 in order to notify the MN 10 of the new HNP of the MN 10. The RA transmission unit 100 may periodically transmit the RA message when receiving the PBA message. Alternatively, the RA transmission unit 100 may transmit an RA message in response to an RS (Router Solicitation) message from the WiFi interface 32 (target radio interface) of the MN 10. When the RA message indicating the new HNP is received, the processor 33 of the MN 10 configures the home address of the mobile node for the target radio interface from the new HNP. This address can then be used to newly connect to tMAG 22.

  (J) After transmitting the RA message, the flow movement completion reporting unit 102 of the tMAG 22 transmits a flow movement completion (Flow Movement Completion) message (L2 trigger) to the MN 10, so that the 3G network system 12 (service radio network system) ) Is notified to the MN 10 of completion of the flow movement (flow transfer) from the WiFi network system 18 (target wireless network system).

  (K) After receiving the flow movement completion message at the MN 10, the selected IP flow (IP flow F2) is completely transferred from the serving radio network system to the target radio network system. That is, from this point on, the selected IP flow can communicate using the connection between the WiFi interface 32 (target radio interface) of the MN 10 and the tMAG 22 and the bidirectional IP tunnel between the tMAG 22 and the LMA 26.

  (L) The BRI transmission unit 59 of the LMA 26 transmits a BRI (Binding Revocation Indication) message to the sMAG 16 so that the sMAG 16 deletes information regarding the transferred IP flow. When the BRI message is received by the BRI receiving unit 97 of the sMAG 16, the information management unit 99 of the sMAG 16 deletes the record corresponding to the transferred IP flow in the flow binding update list table (FIG. 11). When the information management unit 99 of the sMAG 16 normally deletes the record to be canceled, the BRA transmission unit 98 of the sMAG 16 responds to the LMA 26 with a BRA (Binding Revocation Acknowledgement) message as the last step of this scenario.

  In the above description of the first scenario, one IP flow F2 is transferred from the service radio technology to the target radio technology, but one IP flow F1 remains in the service radio technology. The number of IP flows to be transferred is not limited to 1, and two or more IP flows may be transferred from the service radio technology to the target radio technology. The number of remaining IP flows is not limited to 1, and two or more IP flows may remain.

  In the above description regarding the first scenario, the MN is initially connected to the 3G network system 12 and the MN should be newly connected to the WiFi network system 18. However, the MN may initially connect to the WiFi network system 18 (eg, the MN can only communicate with the WiFi network system 18), and then connect to the 3G network system 12 again (eg, the MN is in the 3G zone). 13 and WiFi zone 19 may move to the overlapping zone). Scenario 1 is also applicable in this case. In this case, sMAG is the MAG 22 of the WiFi network system 18 (service radio network system), tMAG is the MAG 16 of the 3G network system 12 (target radio network system), the WiFi interface 32 of the MN is the service radio interface, and the MN The 3G interface 31 is a target wireless interface.

2.5.2 Second scenario (selected IP flow transfer without new connection)
FIG. 19 shows a second scenario. The second scenario is to transfer the selected (designated) IP flow from the service radio network system to the target radio network system without a new connection of the MN 10 to the target radio network system. In this scenario, the MN is initially connected to both the 3G network system 12 and the WiFi network system 18. Then, the IP flow F2 is transferred from the 3G network system 12 to the WiFi network system 18. Accordingly, the 3G network system 12 is a service wireless network system, and the WiFi network system 18 is a target wireless network system. The MN's 3G interface 31 is a service radio interface, and the MN's WiFi interface 32 is a target radio interface.

  The MN 10 is in an overlapping zone where the 3G zone 13 and the WiFi zone 19 overlap. Thus, both WiFi and 3G wireless technologies can be used. Initially, the MN 10 has already established two or more IP flows (eg, IP flows F1 and F2) to the LMA 26 via the 3G network system 12, and at least one to the LMA 26 via the WiFi network system 18. IP flow (for example, IP flow F3) has already been established. The 3G interface 31 (service radio interface) is active, and the WiFi interface 32 (target radio interface) is also active.

  The MN remains in the same zone, but the MN's processor 33 maintains the IP flow F1 in the 3G technology and maintains the IP flow F3 in the WiFi technology, while moving the IP flow F2 from the 3G technology (service radio access technology) to the WiFi technology. Suppose we decide to move to (Target Radio Access Technology). As described above, this determination may be made automatically based on the local policy profile table (FIG. 12), or may be made based on interaction between the MN 10 and the user of the MN 10. In any case, the decision represents the user's intention that the IP flow F2 should be transferred depending on the strength of the 3G signal and the WiFi signal. In this scenario, both the WiFi interface 32 (target radio interface) and the 3G interface 31 (service radio interface) should be kept active.

  The MN 10 transmits information on the current state and desired operation of the radio interface, and information on the IP flow (IP flow F2) selected to be transferred from the service radio network system to the target radio network system. The network side executes the transfer of the designated IP flow according to the intention of the MN instead of the MN.

  FIG. 20 is an information flow diagram showing a series of events in the second scenario. Details of the series of events are described below.

  (A) The IP flow F1 and the IP flow F2 are transmitted between the MN 10 and the CN 28 via the 3G interface 31 of the MN 10, the sMAG 16 of the 3G network system 12, and the bidirectional IP tunnel established between the sMAG 16 and the LMA 26. Established between. On the other hand, the IP flow F3 is established between the MN 10 and the CN 28 via the WiFi interface 32 of the MN 10, the tMAG 22 of the WiFi network system 18, and the bidirectional IP tunnel established between the tMAG 22 and the LMA 26. .

  (B) The processor 33 of the MN 10 determines that the IP flow F2 should be transferred from the 3G network system 12 (service radio network system) to the WiFi network system 18 (target radio network system). The MN 10 transmits a flow mobility instruction message (flow transfer instruction) to the sMAG 16. The flow mobility instruction message reflects the user's intention, for example, the MN-ID of the MN 10, the address of the tMAG 22, the current state of the radio interface and the desired operation, and the FID corresponding to the IP flow F2 to be transferred. Contains information. The information regarding the current state and desired operation of the radio interface indicated by the flow mobility instruction message may or may not be the above-described interface state and operation information. In this scenario, this information should indicate that the 3G interface 31 (service radio interface) should remain active and the WiFi interface 32 (target radio interface) should also remain active.

  (C) When the flow mobility instruction receiving unit 85 of the sMAG 16 receives the L2 trigger, that is, the flow mobility instruction message from the MN 10, the flow mobility instruction receiving unit 85 of the sMAG 16 first relates to the current state and desired operation of the 3G radio interface. Check the information to determine the type of IP flow handover. In this scenario, both the interface 31 (service radio interface) and the WiFi interface 32 (target radio interface) should be kept active, so the 3G network system 12 (service radio network system) and the WiFi network system 18 (target Both wireless network systems) are determined to continue to be used after the selected IP flow is transferred, and the type of IP flow handover does not involve a new connection (new connection) of the MN 10.

  Next, the HIF transmission unit 89 of the sMAG 16 transmits the HIF message to the tMAG 22. This HIF message indicates the second transmission instruction so that the LMA 26 performs flow binding registration for the MN 10. Since a new connection of the MN 10 to the target wireless network system is unnecessary, the preliminary registration procedure can be omitted. In the HIF message, the “M” flag is set to 1 indicating that this message will be used for the specified IP flow movement, and the “R” flag requests the tMAG 22 to send a PBU message to the LMA 26. Therefore, the code value is “5” indicating “with FID” used for transferring the specified IP flow. The HIF message includes an MN-ID that identifies the MN 10, an MN-LL-ID that identifies the WiFi interface 32 (target wireless interface), an address (LMAA) of the LMA 26, and an FID corresponding to the IP flow selected as the transfer target. And a traffic selector corresponding to the selected IP flow, interface state and operation information. In order to construct the HIF message, the HIF transmission unit 89 of the sMAG 16 reads the MN-LL-ID and LMAA from the binding update list table (FIG. 10), and reads the traffic selector from the flow binding update list table (FIG. 11). .

  (D) When the HIF receiver 90 of the tMAG 22 receives the HIF message in which the “M” and “R” flags are set to 1 and the code value is “5”, the PBU transmitter 95 of the tMAG 22 A tMAG 22 PBU message (flow binding update request) is transmitted to the LMA 26 so as to execute the flow binding registration. The PBU message indicates the FID corresponding to the IP flow selected as the transfer target indicated in the HIF message from sMAG. Further, the information management unit 99 of tMAG 22 adds a new record including the FID to the flow binding update list table (FIG. 11).

  When the PBU receiving unit 56 of the LMA 26 receives the PBU message indicating the FID from the tMAG 22, the flow binding registration executing unit 57 of the LMA 26 updates the FID in the FCE table (FIG. 5) so that the previous BID is updated with the new BID. Update an existing FCE (Flow Binding Cache Entry) that contains it. In this way, the existing HNP of the MN 10 of the existing binding cache entry in the BCE table (FIG. 4) is associated with the IP packet flow corresponding to the FID via the BID. Associated with an existing bidirectional IP tunnel corresponding to HNP.

  When the flow binding registration of the transfer of the selected IP flow is normally completed, the PBA transmission unit 58 of the LMA 26 transmits a PBA message to the tMAG 22.

  (E) When the PBA receiving unit 96 of the tMAG 22 receives the PBA message indicating that the flow binding registration has been normally completed, the HAF transmitting unit 91 of the tMAG 22 transmits the HAF message to the sMAG 16. In the HAF message, the code value is set to “8” which means the normal end of the movement of the selected IP flow. In the HAF message, the “M” flag is set to 1 indicating that this message is used for the specified IP flow movement, and the “T” flag is set to zero. Thus, the sMAG 16 does not send an L2 trigger (target interface action message) to the MN (since the target radio interface is already active).

  (F) After transmitting the HAF message, the flow movement completion reporting unit 102 of the tMAG 22 performs flow movement (flow transfer) from the 3G network system 12 (service wireless network system) to the WiFi network system 18 (target wireless network system). In order to notify the MN 10 of the completion, a flow movement completion message (L2 trigger) is transmitted to the MN 10.

  (G) When the flow movement completion message is received by the MN 10, the selected IP flow (IP flow F2) is completely transferred from the service radio network system to the target radio network system. That is, from this time, the selected IP flow can be communicated using the connection between the WiFi interface 32 (target wireless interface) of the MN 10 and the tMAG 22 and the bidirectional IP tunnel between the tMAG 22 and the LMA 26. .

  In the above description of the second scenario, one IP flow F2 is transferred from the service radio technology to the target radio technology, and one IP flow F1 remains in the service radio technology. The number of IP flows to be transferred is not limited to 1, and two or more IP flows may be transferred from the service radio technology to the target radio technology. The number of remaining IP flows is not limited to 1, and two or more IP flows may remain.

  In the above description of the second scenario, the MN 10 is located in a zone where both WiFi and 3G wireless technologies are available, and the IP flow F2 is transferred from the 3G network system 12 to the WiFi network system 18. However, one or more IP flows may be transferred from the WiFi network system 18 to the 3G network system 12 (eg, the system used may depend on the strength of the 3G signal and the WiFi signal). The second scenario is also applicable in this case. In this case, sMAG is the MAG 22 of the WiFi network system 18 (service radio network system), tMAG is the MAG 16 of the 3G network system 12 (target radio network system), the WiFi interface 32 of the MN is the service radio interface, and the MN The 3G interface 31 is a target wireless interface.

2.5.3 Third scenario (new connection with vertical handover)
FIG. 21 shows a third scenario. In this scenario, a new connection of the MN 10 to the target radio network system and a vertical handover in which all IP flows are transferred from the service radio technology to the target radio technology are performed. In this scenario, the MN is initially connected to the 3G network system 12 and should be newly connected to the WiFi network system 18. Accordingly, the 3G network system 12 is a service wireless network system, and the WiFi network system 18 is a target wireless network system. The MN's 3G interface 31 is a service radio interface, and the MN's WiFi interface 32 is a target radio interface.

  In the first stage, the MN 10 is located in the zone 13 where the 3G technology can be used, and is not located in the zone 19 where the WiFi technology can be used. The MN 10 has already established two or more IP flows (for example, IP flows F1 and F2) to the LMA 26 via the 3G network system 12. The 3G interface 31 (service radio interface) is active, the WiFi interface 32 (target radio interface) is inactive, and all IP flows are communicated via the 3G network system 12.

  MN moves to WiFi zone 19 and MN processor 33 performs vertical handover to transfer all IP flows F1 and F2 from 3G technology (service radio access technology) to WiFi technology (target radio access technology) Suppose you have decided what to do. As described above, this determination may be made automatically based on the local policy profile table (FIG. 12) or based on the interaction between the MN 10 and the user of the MN 10. In any case, this determination represents the user's intention that the IP flows F1 and F2 should be transferred to the WiFi technology when the WiFi radio technology is available. In this scenario, the WiFi interface 32 (target radio interface) should be activated from the inactive state (switch on state) and the 3G interface 31 (service radio interface) from the active state to inactive (switch off) Off state).

  The MN 10 transmits information regarding the current state of the radio interface and the desired operation. In this scenario, the MN 10 does not need to send information about the IP flows that are transferred from the serving radio network system to the target radio network system. If the network side can recognize that the MN 10 wants to transfer one or more IP flows and that the service radio interface of the MN 10 should be deactivated from the active state, the network side can receive all the flows from the service radio network system. It can be recognized that it should be moved to the target wireless network system. However, the present invention is not limited to this disclosure, and the MN 10 may transmit information regarding the IP flow to be transferred. The network side performs a new connection of the MN 10 to the target wireless network system, and transfers all IP flows according to the intention of the MN on behalf of the MN.

  22 and 23 are information flow diagrams showing a series of events in the third scenario. Details of the series of events are described below.

  (A) All IP flows are established between the MN 10 and the CN 28 via a bidirectional IP tunnel established between the 3G interface 31 of the MN 10, the sMAG 16 of the 3G network system 12, and the sMAG 16 and the LMA 26. Is done.

  (B) The processor 33 of the MN 10 determines that all IP flows should be transferred from the 3G network system 12 (service radio network system) to the WiFi network system 18 (target radio network system). The MN 10 transmits a flow mobility instruction message (flow transfer instruction) to the sMAG 16. The flow mobility instruction message includes, for example, information reflecting the user's intention such as the MN-ID of the MN 10, the address of the tMAG 22, and information regarding the current state and desired operation of the radio interface. It should be noted that the flow mobility instruction message need not include the FID corresponding to the IP flows F1 and F2 to be transferred. The information regarding the current state and desired operation of the radio interface indicated by the flow mobility instruction message may or may not be the above-described interface state and operation information. In this scenario, the information indicates that the 3G interface 31 (service radio interface) should be deactivated from the active state, and the WiFi interface 32 (target radio interface) is activated from the inactive state. Should show.

  (C) When the flow mobility instruction receiving unit 85 of the sMAG 16 receives the L2 trigger, that is, the flow mobility instruction message from the MN 10, the flow mobility instruction receiving unit 85 of the sMAG 16 first determines the current state and desired operation of the radio interface. To determine the type of IP flow handover. In this scenario, since the 3G interface 31 (service radio interface) should be deactivated from the active state, the 3G network system 12 (service radio network system) should disconnect from the MN 10 after the transfer of the IP flow, and all To be transferred from the 3G network system 12 (service radio network system) to the WiFi network system 18 (target radio network system). Furthermore, since the WiFi interface 32 (target radio interface) should be activated from an inactive state, it is determined that the type of IP flow handover involves a new connection (new connection) of the MN 10 to the target radio network system. Is done.

  Next, the HIF transmission unit 89 of the sMAG 16 transmits the HIF message to the tMAG 22. This HIF message indicates the first transmission instruction so that the LMA 26 executes the preliminary registration of the MN 10. In the HIF message, the “M” flag is set to 1 indicating that this message will be used for the specified IP flow movement, and the “R” flag requests tMAG 22 to send a pre-PBU message to LMA 26. The code value is “4” indicating “no FID” used for a new connection of the MN 10. The HIF message includes a MN-ID that identifies the MN 10, a MN-LL-ID that identifies the WiFi interface 32 (target radio interface), an address (LMAA) of the LMA 26, and an FID corresponding to all IP flows to be transferred. And a traffic selector corresponding to the IP flow, interface state and operation information. In order to construct the HIF message, the HIF transmission unit 89 of the sMAG 16 reads the MN-LL-ID and the LMAA from the binding update list table (FIG. 10), and the FID and traffic selector from the flow binding update list table (FIG. 11). Is read. The flow mobility instruction message from the MN 10 does not indicate the FID corresponding to the IP flow to be transferred. However, since the flow mobility instruction message indicates the MN-ID, the HIF transmission unit 89 of the sMAG 16 includes the flow binding update list table. The FID corresponding to the MN can be specified.

  (D) When the HIF receiver 90 of the tMAG 22 receives the HIF message in which the “M” and “R” flags are set to 1 and 0 and the code value is “4”, the pre-PBU transmitter of the tMAG 22 93 transmits a pre-PBU message (new connection request) to the LMA 26 so that the LMA 26 performs the preliminary registration of the MN 10. The pre-PBU message includes the MN-ID of the MN 10, the MN-LL-ID that identifies the target radio interface, the new BID for the new binding, the ATT that specifies the type of the target access technology, and the proxy CoA of the tMAG 22 Etc. Since pre-registration at LMA 26 does not use FID, the pre-PBU message does not indicate the FID indicated by the HIF message. Instead, the FID is used in flow binding registration to update or register a flow.

  At this time, the information management unit 99 of the tMAG 22 adds a new record for new connection to the binding update list table (FIG. 10). However, the HNP of the new record is empty.

  When the pre-PBU receiving unit 53 of the LMA 26 receives the pre-PBU message from the tMAG 22, the pre-registration execution unit 54 of the LMA 26 assigns the new HNP of the MN 10 to the WiFi interface 32 (target radio interface) of the MN 10, and the new HNP and tMAG 22 Add a new binding to the proxy CoA. More specifically, the preliminary registration execution unit 54 adds a new binding cache entry to the BCE table (FIG. 4). In the BCE table, the contents of the new binding cache entry are the contents of the new HNP and pre-PBU messages.

  When the preliminary registration of the new connection of the MN ends normally, the pre-PBA transmission unit 55 of the LMA 26 transmits a pre-PBA message indicating the new HNP of the MN 10 to the tMAG 22. As a result of tMAG 22 receiving the new HNP of MN 10, a new bidirectional IP tunnel is established between tMAG 22 and LMA 26. At this stage, the information management unit 99 of the tMAG 22 adds the new HNP of the MN 10 to the new record of the new connection in the binding update list table (FIG. 10).

  (E) When the pre-PBA receiving unit 94 of the tMAG 22 receives the pre-PBA message indicating that the preliminary registration has been normally completed, the HAF transmitting unit 91 of the tMAG 22 transmits the HAF message to the sMAG 16. In the HAF message, the code value is set to “7”, which means normal termination of the new connection of the MN 10 to the WiFi network system 18 (target wireless network system). In the HAF message, the “M” flag is set to 1 indicating that this message will be used for the specified IP flow movement, and the “T” flag also causes sMAG 16 to trigger L2 trigger (target interface action message). Set to 1 to activate the target radio interface of the MN by transmitting to the MN.

  (F) When the HAF message indicating the instruction to the sMAG to activate the target wireless interface of the MN 10 is received by the HAF receiver 92 of the sMAG 16, the interface activation unit 86 of the sMAG 16 causes the WiFi interface 32 (target wireless interface ) Is activated (switch is turned on), a target interface action message is transmitted to the 3G interface 31 (service radio interface) of the MN 10.

  (G) After the switch of the WiFi interface 32 (target radio interface) is turned on, the MN 10 establishes a link layer connection with the WiFi network system 18 (target radio network system) for a new connection of the MN 10.

  (H) When the connection confirmation unit 87 of the tMAG 22 confirms that the L2 connection between the WiFi interface 32 (target wireless interface) of the MN 10 and the tMAG 22 has been successfully established, the PBU transmission unit 95 of the tMAG 22 causes the LMA 26 to register the flow binding. A PBU message is transmitted to the LMA 26 so as to execute. The PBU message indicates the FID corresponding to all the IP flows to be transferred indicated by the HIF message from the sMAG. Further, the information management unit 99 of tMAG 22 adds a new record including the FID to the flow binding update list table (FIG. 11).

  When the PBU receiving unit 56 of the LMA 26 receives the PBU message indicating the FID from the tMAG 22, the flow binding registration executing unit 57 of the LMA 26 updates the FCE table (FIG. 5) so that the previous BID is updated with the new BID. Update an existing FCE (flow binding cache entry) containing the FID. Thus, the new HNP of the MN 10 in the new binding cache entry of the BCE table (FIG. 4) is associated with the IP packet flow corresponding to the FID via the BID, and thus the IP packet flow is Associated with a new bidirectional IP tunnel corresponding to HNP.

  When the flow binding registration of the IP flow transfer is normally completed, the PBA transmission unit 58 of the LMA 26 transmits a PBA message to the tMAG 22.

  (I) After the PBA message is received by the PBA receiver 96 of the tMAG 22, the RA transmitter 100 of the tMAG 22 transmits an RA (Router Advertisement) message to the MN 10 in order to notify the MN 10 of the new HNP of the MN 10. When receiving the PBA message, the RA transmission unit 100 may periodically transmit the RA message. Alternatively, the RA transmission unit 100 may transmit an RA message in response to an RS (Router Solicitation) message from the WiFi interface 32 (target radio interface) of the MN 10. Upon receipt of the RA message indicating the new HNP, the processor 33 of the MN 10 constructs the mobile node's home address for the target radio interface from the new HNP. This home address is newly used to connect to tMAG22.

  (J) After transmitting the RA message, the flow movement completion reporting unit 102 of the tMAG 22 performs flow movement (flow transfer) from the 3G network system 12 (service radio network system) to the WiFi network system 18 (target radio network system). In order to notify the MN 10 of completion, a flow movement completion message (L2 trigger) is transmitted to the MN 10.

  (K) After receiving the flow movement completion message at the MN 10, all IP flows (IP flows F1 and F2) are completely transferred from the service radio network system to the target radio network system. That is, from this point on, all IP flows can communicate using the connection between the WiFi interface 32 (target radio interface) of the MN 10 and the tMAG 22 and the bidirectional IP tunnel between the tMAG 22 and the LMA 26.

  (L) The BRI transmission unit 59 of the LMA 26 transmits a BRI (Binding Revocation Indication) message to the sMAG 16 so as to execute deregistration for deleting information regarding all the IP flows to which the sMAG 16 has been transferred. When the BRI message is received by the BRI receiving unit 97 of the sMAG 16, the information management unit 99 of the sMAG 16 deletes the records corresponding to all the transferred IP flows in the binding update list table (FIG. 10), and the flow binding update list. Delete records corresponding to all transferred IP flows in the table (FIG. 11). When the information management unit 99 of the sMAG 16 normally deletes the record to be canceled, the BRA transmission unit 98 of the sMAG 16 responds to the LMA 26 with a BRA (Binding Revocation Indication) message.

  (M) The MN 10 and the sMAG 16 release the link layer connection used for the transferred IP flow, and the MN deactivates the 3G interface 31 (service radio interface) as the last step in this scenario (switches off) To do).

  In the above description of the third scenario, the two IP flows F1 and F2 are transferred from the service radio technology to the target radio technology. The number of IP flows to be transferred is not limited to two, and one IP flow or three or more IP flows may be transferred from the service radio technology to the target radio technology.

  In the above description of the third scenario, the MN is initially connected to the 3G network system 12 and then should be newly connected to the WiFi network system 18. However, the MN may initially be connected to the WiFi network system 18 (eg, the MN may only be able to communicate with the WiFi network system 18) or may be newly connected to the 3G network system 12 (eg, The MN may move to an overlapping zone where the 3G zone 13 and the WiFi zone 19 overlap). The third scenario is also applicable in this case. In this case, sMAG is the MAG 22 of the WiFi network system 18 (service radio network system), tMAG is the MAG 16 of the 3G network system 12 (target radio network system), the WiFi interface 32 of the MN is the service radio interface, and the MN The 3G interface 31 is a target wireless interface.

2.5.4 Fourth scenario (partial vertical handover without new connection)
FIG. 24 shows a fourth scenario with partial vertical handover. In this scenario, part of the existing IP flow is transferred from the service radio technology to the target radio technology without a new connection of the MN 10 to the target radio network system (other of the existing IP flows are already targeted Sent via wireless network system). In this scenario, the MN is initially connected to the 3G network system 12 and the WiFi network system 18, and then the IP flow F2 is transferred from the WiFi network system 18 to the 3G network system 12. Accordingly, the WiFi network system 18 is a service wireless network system, and the 3G network system 12 is a target wireless network system. The MN's WiFi interface 32 is a service radio interface, and the MN's 3G interface 31 is a target radio interface.

  In the first stage, since the MN 10 is located in the overlapping zone where the 3G zone 13 and the WiFi zone 19 overlap, both WiFi and 3G wireless technologies can be used. The MN 10 has already established at least one IP flow to the LMA 26 (for example, the IP flow F1) via the 3G network system 12, and at least one IP flow to the LMA 26 via the WiFi network system 18. (For example, IP flow F2) has already been established. The WiFi interface 32 (service radio interface) is active, and the 3G interface 31 (target radio interface) is also active.

  MN leaves WiFi zone 19, and MN processor 33 should transfer IP flow F2 from WiFi technology (service radio access technology) to 3G technology (target radio access technology), and therefore perform partial vertical handover Assume that you have decided. As described above, this determination may be made automatically based on the local policy profile table (FIG. 12), or may be made based on the interaction between the MN 10 and the user of the MN 10. In any case, this determination indicates the user's intention that the IP flow F2 should be transferred to the 3G technology when the WiFi radio technology is not available. In this scenario, the 3G interface 31 (target radio interface) should be kept active, and the WiFi interface 32 (service radio interface) is changed from the active state to the inactive state (switch off state). Should.

  The MN 10 transmits information regarding the current state of the radio interface and the desired operation. In this scenario, the MN 10 does not need to send information about the IP flows that are transferred from the serving radio network system to the target radio network system. If the network side recognizes that the MN 10 wants to transfer one or more IP flows and that the service radio interface of the MN 10 should be changed from an active state to an inactive state, all of one or a plurality of flows are served as a service radio network system. The network side can recognize that it should move to the target wireless network system. However, the present invention is not limited to this disclosure, and the MN 10 may transmit information regarding the IP flow to be transferred. The network side transfers all of one or more IP flows on behalf of the MN according to the intention of the MN.

  25 and 26 are information flow diagrams showing a series of events in the fourth scenario. Details of the series of events are described below.

  (A) The IP flow F1 is established between the MN 10 and the CN 28 via the bidirectional IP tunnel established between the 3G interface 31 of the MN 10, the sMAG 16 of the 3G network system 12, and the sMAG 16 and the LMA 26. The On the other hand, the IP flow F2 is established between the MN 10 and the CN 28 via the WiFi interface 32 of the MN 10, the tMAG 22 of the WiFi network system 18, and the bidirectional IP tunnel established between the tMAG 22 and the LMA 26. .

  (B) The processor 33 of the MN 10 transfers all of one or a plurality of IP flows (for example, the IP flow F2) using the WiFi network system 18 (service wireless network system) to the WiFi network system 18 (service wireless network system). To 3G network system 12 (target wireless network system). The MN 10 transmits a flow mobility instruction message (flow transfer instruction) to the sMAG 22. The flow mobility instruction message includes information reflecting the user's intention such as, for example, the MN-ID of the MN 10, the address of the sMAG 16, the current state of the radio interface, and information regarding a desired operation. It should be noted that the flow mobility instruction message does not need to include the FID corresponding to the IP flow F2 to be transferred. The information regarding the current state and desired operation of the radio interface indicated by the flow mobility instruction message may or may not be the above-described interface state and operation information. In this scenario, the information should indicate that the WiFi interface 32 (service radio interface) is deactivated from the active state and the 3G interface 31 (target radio interface) remains active.

  (C) When the flow mobility instruction receiving unit 85 of the sMAG 22 receives the L2 trigger, that is, the flow mobility instruction message from the MN 10, the flow mobility instruction receiving unit 85 of the sMAG 22 first relates to the current state and desired operation of the radio interface. Check the information to determine the type of IP flow handover. In this scenario, the WiFi interface 32 (service radio interface) should be deactivated from the active state, so the WiFi network system 18 (service radio network system) is disconnected from the MN 10 after transfer of the selected IP flow. It is determined that all of the one or more IP flows should be transferred from the WiFi network system 18 (service radio network system) to the 3G network system 12 (target radio network system). Furthermore, since the 3G interface 31 (target wireless interface) should remain active, the WiFi network system 18 (service wireless network system) should continue to be used after the selected IP flow is transferred. The type of IP flow handover does not involve a new connection (new connection) of the MN 10.

  Next, the HIF transmission unit 89 of the sMAG 22 transmits the HIF message to the tMAG 16. This HIF message indicates a second transmission instruction so that the LMA 26 performs flow binding registration with the MN 10. Since it is not necessary to newly connect the MN 10 to the target wireless network system, the preliminary registration procedure can be omitted. In the HIF message, the “M” flag is set to 1 indicating that this message will be used for the specified IP flow movement, and the “R” flag requests tMAG 16 to send a PBU message to LMA 26. Is set to 1 and the code value is “5” indicating “with FID” used to transfer the specified IP flow. The HIF message includes an MN-ID that identifies the MN 10, an MN-LL-ID that identifies the 3G interface 31 (target radio interface), an address of the LMA 26 (LMAA), and all of one or more IP flows to be transferred. FID, traffic selectors corresponding to these IP flows, and interface status and operation information. In order to construct a HIF message, the HIF transmission unit 89 of the sMAG 22 reads the MN-LL-ID and LMAA from the binding update list table (FIG. 10), and the FID and traffic selector from the flow binding update list table (FIG. 11). Is read. The flow mobility instruction message from the MN 10 does not indicate the FID corresponding to the IP flow to be transferred, but since the flow mobility instruction message indicates the MN-ID, the HIF transmission unit 89 of the sMAG 22 uses the MN in the flow binding update list table. The FID corresponding to can be specified.

  (D) When the HIF receiver 90 of tMAG 16 receives the HIF message in which the “M” and “R” flags are set to 1 and the code value is “5”, the PBU transmitter 95 of tMAG 16 causes the LMA 26 to perform flow binding. A tMAG 16 PBU message (flow binding update request) is transmitted to the LMA 26 so as to execute the registration. The PBU message indicates the FID corresponding to the transferred IP flow indicated in the HIF message from the MAG. Furthermore, the information management unit 99 of tMAG 16 adds a new record including the FID to the flow binding update list table (FIG. 11).

  When the PBU receiving unit 56 of the LMA 26 receives a PBU message indicating the FID from the tMAG 16, the flow binding registration executing unit 57 of the LMA 26 updates the previous BID with a new BID in the FCE table (FIG. 5). Update the existing FCE including the FID. Thus, the existing HNP of the MN 10 in the existing binding cache entry of the BCE table (FIG. 4) is associated with the IP packet flow corresponding to the FID via the BID, and thus the IP packet flow is Associated with an existing bidirectional IP tunnel corresponding to HNP.

  When the flow binding registration is normally completed for the transfer of the selected IP flow, the PBA transmission unit 58 of the LMA 26 transmits a PBA message to the tMAG 16.

  (E) When the PBA receiving unit 96 of the tMAG 16 receives the PBA message indicating that the flow binding registration has been normally completed, the HAF transmitting unit 91 of the tMAG 16 transmits the HAF message to the sMAG 22. In the HAF message, the code value is set to “8”, which means that the transfer of the selected IP flow has been successfully completed. In the HAF message, the “M” flag is set to 1 to indicate that this message is used for the specified IP flow movement, while the “T” flag is set to zero, and sMAG 22 triggers the L2 trigger on the MN. (Target interface action message) is not sent (because the target radio interface is already active).

  (F) After sending the message to the HAF, the flow movement completion report unit 102 of the tMAG 16 moves the flow (flow transfer) from the WiFi network system 18 (service radio network system) to the 3G network system 12 (target radio network system). In order to notify the MN 10 of completion of the flow, a flow movement completion message (L2 trigger) is transmitted to the MN 10.

  (G) After receiving the flow movement completion message at the MN 10, the IP flow (IP flow F2) is completely transferred from the service radio network system to the target radio network system. That is, from this time, the IP flow can communicate using the connection between the 3G interface 31 (target radio interface) of the MN 10 and the tMAG 16 and the bidirectional IP tunnel between the tMAG 16 and the LMA 26.

  (H) The BRI transmission unit 59 of the LMA 26 transmits a BRI (Binding Revocation Indication) message to the sMAG 22 so that the sMAG 22 executes deregistration for deleting information regarding all transferred IP flows. When the BRI message is received by the BRI receiving unit 97 of the sMAG 22, the information management unit 99 of the sMAG 22 deletes records corresponding to all of the one or more transferred IP flows in the binding update list table (FIG. 10), and the flow Delete records corresponding to all of one or more transferred IP flows in the binding update list table (FIG. 11). When the information management unit 99 of the sMAG 16 normally deletes the record to be canceled, the BRA transmission unit 98 of the sMAG 16 responds to the LMA 26 with a BRA (Binding Revocation Acknowledgement) message.

(I) The MN 10 and the sMAG 22 release the link layer connection used for the transferred IP flow, and the MN deactivates the WiFi interface 32 (service radio interface) as the last step in this scenario (switch off state) ).
In the above description of the fourth scenario, one IP flow F2 is transferred from the service radio technology to the target radio technology. The number of transferred IP flows is not limited to 1, and two or more IP flows may be transferred from the service radio technology to the target radio technology.

  In the above description of the fourth scenario, the MN 10 is in a zone where both WiFi and 3G wireless technologies are available, and the IP flow F2 is transferred from the WiFi network system 18 to the 3G network system 12. However, one or more IP flows may be transferred from the 3G network system 12 to the WiFi network system 18 (eg, the MN leaves the 3G zone 13). The fourth scenario is applicable also in this case. In this case, tMAG is the MAG 22 of the WiFi network system 18 (target radio network system), sMAG is the MAG 16 of the 3G network system 12 (service radio network system), and the 3G interface 31 of the MN is a service radio interface. The MN's WiFi interface 32 is the target wireless interface.

2.6 Note The IP flows transferred by this embodiment are not limited to uplink flows or downlink flows. That is, according to the present embodiment, the uplink IP flow and the downlink IP flow may be transferred.

  The above embodiment employs an example in which an IP flow is communicated with WiFi via 3G wireless technology. However, it is not intended to limit the invention to that disclosure. The IP flows can communicate via other wireless technologies (eg, WiMax or other mobile data communication technologies including 4G or more than 4G wireless technologies).

10: MN (mobile node)
12: 3G network system 13: 3G available zone 14: base station 16: MAG (mobility anchor gateway)
18: WiFi network system 19: WiFi available zone 20: Access node 22: MAG
24: Internet 26: LMA (Local Mobility Anchor)
28: CN (partner node)
31: 3G interface 32: WiFi interface 33: processor 34: display unit 35: speaker 36: human interface 41: transmission unit circuit 42: reception unit circuit 43: processor 44: memory 51: IP flow reception unit 52: IP flow transmission unit 53: Pre-PBU receiver (new connection request receiver)
54: Preliminary registration execution unit (new connection registration unit)
55: Pre-PBA transmitter (new home network prefix transmitter)
56: PBU receiver (flow binding update request receiver)
57: Flow binding registration execution part (flow binding registration part)
58: PBA transmitter (flow binding completion report transmitter)
59: BRI transmitting unit 60: BRA receiving unit 71: transmitting unit circuit 72: receiving unit circuit 73: processor 74: memory 81: IP flow transmitting unit 82: IP flow receiving unit 83: IP flow receiving unit 84: IP flow transmitting unit 85: Flow mobility instruction receiving unit (flow transfer instruction receiving unit)
86: Interface activation unit 87: Connection confirmation unit 89: HIF transmission unit (flow transfer request transmission unit)
90: HIF receiver (flow transfer request receiver)
91: HAF transmission unit (registration completion report transmission unit, interface activation unit)
92: HAF receiver (registration completion report receiver)
93: Pre-PBU transmitter (new connection request transmitter)
94: Pre-PBA receiver (new home network prefix receiver)
95: PBU transmission unit (flow binding update request transmission unit)
96: PBA receiver (flow binding completion report receiver)
97: BRI receiving unit 98: BRA transmitting unit 99: Information managing unit 100: RA transmitting unit 101: RS receiving unit 102: Flow movement completion reporting units F1 to F3: IP flow

Claims (15)

A first wireless interface that operates based on Proxy Mobile Internet Protocol Version 6 and communicates with the Internet via a first wireless communication network system using a first wireless access technology; Communicating with at least one mobile node having a second radio interface for communicating with the Internet via a second radio communication network system using a second radio access technology different from the one radio access technology Network architecture,
The first wireless communication network system in which the mobile node can communicate using the first wireless access technology;
The second wireless communication network system in which the mobile node can communicate using the second wireless access technology different from the first wireless access technology;
A local mobility anchor connected to the first wireless communication network system via the Internet and connected to the second wireless communication network system via the Internet and capable of communicating with a counterpart node of the mobile node; The mobile node can communicate with the counterpart node via the first wireless communication network system and the local mobility anchor, and the second wireless communication network. A local mobility anchor that enables communication with the counterparty node via the system and the local mobility anchor;
The first wireless communication network system can operate as an access router of the mobile node, and the first wireless communication network system is interposed between the mobile node and the local mobility anchor. Having a first mobility anchor gateway capable of managing at least one established IP packet flow;
The second wireless communication network system can operate as an access router of the mobile node, and the second wireless communication network system is interposed between the mobile node and the local mobility anchor via the second wireless communication network system. A second mobility anchor gateway capable of managing at least one established IP packet flow;
The first mobility anchor gateway of the first wireless communication network system is:
When at least one IP packet flow is established between the first radio interface of the mobile node and the local mobility anchor via the first radio communication network system; and A flow transfer indication sent from the mobile node when the mobile node wants to transfer at least one already established IP packet flow from the first radio access technology to the second radio access technology, comprising: A current state that identifies the mobile node and the second radio interface of the mobile node used for the IP packet flow to be transferred, and indicates whether the second radio interface is currently activated A flow that can receive a flow transfer instruction that contains information And the transfer instruction receiving unit,
When the flow transfer instruction is received by the flow transfer instruction receiving unit, a flow transfer request capable of transmitting a flow transfer request to the second mobility anchor gateway of the second wireless communication network system A transmission unit,
The flow transfer request includes the mobile node, the second radio interface of the mobile node used for the IP packet flow to be transferred, and the mobile node from the first radio access technology to the second radio interface. Identifying the IP packet flow that is to be transferred to a radio access technology, and if the current status information in the flow transfer indication indicates that the second radio interface is not currently active, Including a first transmission instruction for instructing the second mobility anchor gateway to transmit a new connection request to the mobility anchor, wherein the second radio interface is currently activated When the current state information indicates in the flow transfer instruction, Includes a second transmission instruction instructing the second mobility anchor gateway to send flow binding update request to Karu Mobility Anchor,
The second mobility anchor gateway of the second wireless communication network system is:
A proxy care-of address indicating the second mobility anchor gateway;
A flow transfer request receiving unit capable of receiving the flow transfer request from the first mobility anchor gateway;
If the flow transfer request received by the flow transfer request reception unit includes the first transmission instruction, a new one that specifies the mobile node and the proxy care-of address of the second mobility anchor gateway A new connection request transmitter capable of transmitting a connection request to the local mobility anchor,
The local mobility anchor is
A new connection request receiving unit capable of receiving the new connection request from the second mobility anchor gateway;
A new home network prefix of the mobile node used for communication via the second wireless communication network system between the second radio interface of the mobile node and the local mobility anchor; When the new connection request is received by the new connection request receiver, the new home network prefix of the mobile node and the second mobility anchor gateway of the second mobility anchor gateway are received. A new connection request registration unit capable of registering a new binding with the proxy care-of address;
Based on the new home network prefix of the mobile node and the proxy care-of address of the second mobility anchor gateway, between the second mobility anchor gateway and the local mobility anchor A new home network prefix transmitter for transmitting a new home network prefix of the mobile node to the second mobility anchor gateway to facilitate establishment of a bidirectional IP tunnel;
The second mobility anchor gateway is
A new home network prefix receiving unit capable of receiving a new home network prefix of the mobile node from the local mobility anchor;
When the new home network prefix receiving unit receives the new home network prefix of the mobile node, the connection between the second radio interface of the mobile node and the second mobility anchor gateway An interface activation unit capable of activating the second wireless interface of the mobile node specified by the flow transfer request;
A connection confirmation unit capable of confirming establishment of a connection between the second radio interface of the mobile node and the second mobility anchor gateway;
When the connection confirmation unit confirms the establishment of the connection, a flow binding update request can be transmitted to the local mobility anchor, and the flow transfer request including the second transmission instruction is transmitted to the flow transfer request. A flow binding update request transmission unit capable of transmitting the flow binding update request to the local mobility anchor when received by the reception unit;
The flow binding update request includes the mobile node, the proxy care-of address of the second mobility anchor gateway, and the mobile node from the first radio access technology to the first mobility anchor gateway. Identifying the IP packet flow to be transferred to the second radio access technology specified by the flow transfer request from
The local mobility anchor is
A flow binding update request receiving unit capable of receiving the flow binding update request from the second mobility anchor gateway;
A flow binding registration unit capable of registering a binding between the new home network prefix of the mobile node or an existing home network prefix and the IP packet flow specified by the flow binding update request. And the existing home network prefix of the mobile node is the second for establishing an existing bidirectional IP tunnel between the second mobility anchor gateway and the local mobility anchor. Flow binding registration already associated with the proxy care-of address of the second mobility anchor gateway by the mobility anchor gateway and the local mobility anchor And,
A flow binding completion report transmission unit capable of transmitting a flow binding completion message indicating that the registration of the binding in the flow binding registration unit is completed to the second mobility anchor gateway; ,
The second mobility anchor gateway is
A flow binding completion report receiving unit capable of receiving the flow binding completion message from the local mobility anchor;
Connection between the second radio interface of the mobile node and the second mobility anchor gateway and the bidirectional IP between the second mobility anchor gateway and the local mobility anchor The IP packet that the mobile node wishes to transfer from the first radio access technology to the second radio access technology specified by the flow transfer request from the first mobility anchor gateway using a tunnel A flow establishment unit capable of establishing a flow between the second radio interface of the mobile node and the local mobility anchor;
Network architecture. When the flow transfer request received by the flow transfer request reception unit of the second mobility anchor gateway includes the first transmission instruction, the interface activation unit of the second mobility anchor gateway Activates the second radio interface of the mobile node;
The network architecture according to claim 1 . A first wireless interface that operates based on Proxy Mobile Internet Protocol Version 6 and communicates with the Internet via a first wireless communication network system using a first wireless access technology; Communicating with at least one mobile node having a second radio interface for communicating with the Internet via a second radio communication network system using a second radio access technology different from the one radio access technology Network architecture,
The first wireless communication network system in which the mobile node can communicate using the first wireless access technology;
The second wireless communication network system in which the mobile node can communicate using the second wireless access technology different from the first wireless access technology;
A local mobility anchor connected to the first wireless communication network system via the Internet and connected to the second wireless communication network system via the Internet and capable of communicating with a counterpart node of the mobile node; And enabling the mobile node to communicate with the counterpart node via the first wireless communication network system and the local mobility anchor, and the second wireless communication network. A local mobility anchor that enables communication with the counterparty node via the system and the local mobility anchor;
The first wireless communication network system can operate as an access router of the mobile node, and the first wireless communication network system is interposed between the mobile node and the local mobility anchor. Having a first mobility anchor gateway capable of managing at least one established IP packet flow;
The second wireless communication network system can operate as an access router of the mobile node, and the second wireless communication network system is interposed between the mobile node and the local mobility anchor via the second wireless communication network system. A second mobility anchor gateway capable of managing at least one established IP packet flow;
The first mobility anchor gateway of the first wireless communication network system is:
A plurality of IP packet flows are established between the first radio interface of the mobile node and the local mobility anchor via the first radio communication network system, while the second of the mobile node The IP packet flow through the second wireless communication network system is not established between the wireless interface of the mobile station and the local mobility anchor, and the mobile node has already been established. A flow transfer instruction transmitted from the mobile node when it is desired to transfer at least one of the packet flows from the first radio access technology to the second radio access technology, the mobile node and the IP to be transferred Before the mobile node used for packet flow And flow transfer instruction receiver capable of receiving a flow transfer instruction specifying a second radio interface,
When the flow transfer instruction is received by the flow transfer instruction receiving unit, a flow transfer request capable of transmitting a flow transfer request to the second mobility anchor gateway of the second wireless communication network system A transmission unit,
The flow transfer request includes the mobile node, the second radio interface of the mobile node used for the IP packet flow to be transferred, and the mobile node from the first radio access technology to the second radio interface. Identify the IP packet flow that you want to transfer to the radio access technology,
The second mobility anchor gateway of the second wireless communication network system is:
A proxy care-of address indicating the second mobility anchor gateway;
A flow transfer request receiving unit capable of receiving the flow transfer request from the first mobility anchor gateway;
When the flow transfer request is received by the flow transfer request reception unit, a new connection request for specifying the mobile node and the proxy care-of address of the second mobility anchor gateway is sent to the local mobility anchor. A new connection request transmitter capable of transmitting,
The local mobility anchor is
A new connection request receiving unit capable of receiving the new connection request from the second mobility anchor gateway;
A new home network prefix of the mobile node used for communication via the second wireless communication network system between the second radio interface of the mobile node and the local mobility anchor; When the new connection request is received by the new connection request receiver, the new home network prefix of the mobile node and the second mobility anchor gateway of the second mobility anchor gateway are received. A new connection request registration unit capable of registering a new binding with the proxy care-of address;
Based on the new home network prefix of the mobile node and the proxy care-of address of the second mobility anchor gateway, between the second mobility anchor gateway and the local mobility anchor A new home network prefix transmission unit for transmitting a new home network prefix of the mobile node to the second mobility anchor gateway to facilitate establishment of a bidirectional IP tunnel of
The second mobility anchor gateway is
A new home network prefix receiving unit capable of receiving a new home network prefix of the mobile node from the local mobility anchor;
When the new home network prefix receiving unit receives the new home network prefix of the mobile node, the connection between the second radio interface of the mobile node and the second mobility anchor gateway An interface activation unit capable of activating the second wireless interface of the mobile node specified by the flow transfer request;
A connection confirmation unit capable of confirming establishment of a connection between the second radio interface of the mobile node and the second mobility anchor gateway;
A flow binding update request transmission unit capable of transmitting a flow binding update request to the local mobility anchor when the connection confirmation unit confirms the establishment of the connection;
In the flow binding update request, the mobile node wants to transfer from the first radio access technology to the second radio access technology specified by the flow transfer request from the first mobility anchor gateway. Identify the IP packet flow,
The local mobility anchor is
A flow binding update request receiving unit capable of receiving the flow binding update request from the second mobility anchor gateway;
A flow binding registration unit capable of registering a new binding between the new home network prefix of the mobile node and the IP packet flow specified by the flow binding update request;
A flow binding completion report transmission unit capable of transmitting a flow binding completion message indicating that the registration of the new binding in the flow binding registration unit is completed to the second mobility anchor gateway; and Have
The second mobility anchor gateway is
A flow binding completion report receiving unit capable of receiving the flow binding completion message from the local mobility anchor;
The connection between the second radio interface of the mobile node and the second mobility anchor gateway and the bi-directional between the second mobility anchor gateway and the local mobility anchor The IP that the mobile node wishes to transfer from the first radio access technology to the second radio access technology specified by the flow transfer request from the first mobility anchor gateway using an IP tunnel A flow establishment unit capable of establishing a packet flow between the second radio interface of the mobile node and the local mobility anchor;
Network architecture. A first wireless interface that operates based on Proxy Mobile Internet Protocol Version 6 and communicates with the Internet via a first wireless communication network system using a first wireless access technology; Communicating with at least one mobile node having a second radio interface for communicating with the Internet via a second radio communication network system using a second radio access technology different from the one radio access technology Network architecture,
The first wireless communication network system in which the mobile node can communicate using the first wireless access technology;
The second wireless communication network system in which the mobile node can communicate using the second wireless access technology different from the first wireless access technology;
A local mobility anchor connected to the first wireless communication network system via the Internet and connected to the second wireless communication network system via the Internet and capable of communicating with a counterpart node of the mobile node; The mobile node can communicate with the counterpart node via the first wireless communication network system and the local mobility anchor, and the second wireless communication network. A local mobility anchor that enables communication with the counterparty node via the system and the local mobility anchor;
The first wireless communication network system can operate as an access router of the mobile node, and the first wireless communication network system is interposed between the mobile node and the local mobility anchor. Having a first mobility anchor gateway capable of managing at least one established IP packet flow;
The second wireless communication network system can operate as an access router of the mobile node, and the second wireless communication network system is interposed between the mobile node and the local mobility anchor via the second wireless communication network system. A second mobility anchor gateway capable of managing at least one established IP packet flow;
The first mobility anchor gateway of the first wireless communication network system is:
At least one IP packet flow is established via the first wireless communication network system between the first radio interface of the mobile node and the local mobility anchor, while the first of the mobile node And at least one IP packet flow is established between the second radio interface and the local mobility anchor via the second radio communication network system, and the mobile node is at least one Is a flow transfer instruction transmitted from the mobile node when it is desired to transfer the already established IP packet flow from the first radio access technology to the second radio access technology, the mobile node and the transfer target Used for the IP packet flow of A flow transfer instruction receiving unit that can identify a second wireless interface of a wireless node and receive a flow transfer instruction including current state information indicating whether or not the second wireless interface is currently activated When,
When the flow transfer instruction is received by the flow transfer instruction receiving unit, a flow transfer request capable of transmitting a flow transfer request to the second mobility anchor gateway of the second wireless communication network system A transmission unit,
The flow transfer request includes the mobile node, the second radio interface of the mobile node used for the IP packet flow to be transferred, and the mobile node from the first radio access technology to the second radio interface. Identify the IP packet flow that you want to transfer to the radio access technology,
The second mobility anchor gateway of the second wireless communication network system is:
A proxy care-of address indicating the second mobility anchor gateway;
A flow transfer request receiving unit capable of receiving the flow transfer request from the first mobility anchor gateway;
A flow binding update request transmitter capable of transmitting a flow binding update request to the local mobility anchor when the flow transfer request is received by the flow transfer request receiver;
The flow binding update request includes the mobile node, the proxy care-of address of the second mobility anchor gateway, and the mobile node from the first radio access technology to the first mobility anchor gateway. Identifying the IP packet flow to be transferred to the second radio access technology specified by the flow transfer request from
The local mobility anchor is
A flow binding update request receiving unit capable of receiving the flow binding update request from the second mobility anchor gateway;
A flow binding registration unit capable of registering a binding between an existing home network prefix of the mobile node and the IP packet flow specified by the flow binding update request, wherein the existing binding of the mobile node The home network prefix is the second mobility anchor gateway and the local for establishing an existing bidirectional IP tunnel between the second mobility anchor gateway and the local mobility anchor. A flow binding registration unit already associated with the proxy care-of address of the second mobility anchor gateway by a mobility anchor;
A flow binding completion report transmission unit capable of transmitting a flow binding completion message indicating that registration of the binding in the flow binding registration unit is completed to the second mobility anchor gateway, and
The second mobility anchor gateway is
A flow binding completion report receiving unit capable of receiving the flow binding completion message from the local mobility anchor;
After the flow binding completion report receiving unit receives the flow binding completion message, the existing connection between the second radio interface of the mobile node and the second mobility anchor gateway and the second Using the bi-directional IP tunnel between the mobility anchor gateway and the local mobility anchor, the mobile node is from the first radio access technology and from the first mobility anchor gateway. The IP packet flow to be transferred to the second radio access technology specified by the flow transfer request can be established between the second radio interface of the mobile node and the local mobility anchor And a flow establishment unit
Network architecture. The first wireless communication network system includes desired operational information indicating that the first wireless interface should be active and between the first wireless interface of the mobile node and the local mobility anchor The flow transfer instruction specifying that a part of a plurality of IP packet flows already established via the first radio access technology should be transferred from the first radio access technology to the second radio access technology; When the flow transfer instruction receiving unit of the mobility anchor gateway receives the flow transfer request transmission unit of the first mobility anchor gateway specifies the IP packet flow specified by the flow transfer instruction The flow transfer request is transferred to the second mobility anchor gateway. The first mobility anchor gateway transmits the flow establishment unit of the second mobility anchor gateway identified by the flow transfer request from the first mobility anchor gateway. Even after establishing an IP packet flow between the second radio interface of the mobile node and the local mobility anchor, the first radio interface of the mobile node and the local mobility anchor Maintaining another IP packet flow among the plurality of IP packet flows already established via the first wireless communication network system
The network architecture according to any one of claims 1 to 4 . The flow transfer instruction including desired operation information indicating that the flow transfer instruction receiving unit of the first mobility anchor gateway should deactivate the first radio interface from an activated state. Is received, the flow transfer request transmission unit of the first mobility anchor gateway transmits the first wireless communication network between the first wireless interface of the mobile node and the local mobility anchor. Sending the flow transfer request specifying that all of the one or more IP packet flows already established through the system should be transferred from the first radio access technology to the second radio access technology; The flow establishment unit of the second mobility anchor gateway Establishing all of the one or more IP packet flows identified by the flow transfer request from a first mobility anchor gateway between the second radio interface of the mobile node and the local mobility anchor To
The network architecture according to any one of claims 1 to 5 . The first mobility anchor gateway transmits a copy of an IP packet transmitted on the IP packet flow that the mobile node wishes to transfer from the first radio access technology to the second radio access technology. Do not forward to two mobility anchor gateways,
The network architecture according to any one of claims 1 to 6 . A local mobility anchor in a network architecture that operates according to Proxy Mobile Internet Protocol version 6 and communicates with at least one mobile node, comprising:
The local mobility anchor is connected to a first mobility anchor gateway via the local mobility anchor internet and connected to a second mobility anchor gateway via the internet;
The first mobility anchor gateway operates as an access router for the mobile node of a first wireless communication network system that uses a first radio access technology to communicate with the mobile node and the mobile Managing at least one IP packet flow established between the node and the local mobility anchor via the first wireless communication network system;
The second mobility anchor gateway operates as an access router for the mobile node of a second wireless communication network system that uses a second radio access technology to communicate with the mobile node, and the mobile Managing at least one IP packet flow established between the node and the local mobility anchor via the second wireless communication network system;
The local mobility anchor can communicate with a counterpart node of the mobile node, and the mobile node communicates with the counterpart node via the first wireless communication network system and the local mobility anchor. And capable of communicating with the counterparty node via the second wireless communication network system and the local mobility anchor,
The local mobility anchor is
A new connection request receiving unit capable of receiving from the second mobility anchor gateway a new connection request specifying a proxy care-of address of the mobile node and the second mobility anchor gateway;
Assign the mobile node's new home network prefix to be used for communication between the mobile node's radio interface and the local mobility anchor via the second radio communication network system When the new connection request is received by the new connection request receiving unit, the new home network prefix of the mobile node and the proxy care-of address of the second mobility anchor gateway A new connection request registration unit capable of registering a new binding between
Based on the new home network prefix of the mobile node and the proxy care-of address of the second mobility anchor gateway, between the second mobility anchor gateway and the local mobility anchor A new home network prefix transmitter for transmitting a new home network prefix of the mobile node to the second mobility anchor gateway to facilitate establishment of a bidirectional IP tunnel;
From the second mobility anchor gateway, the mobile node, the proxy care-of address of the second mobility anchor gateway, and the mobile node from the first radio access technology to the second radio access. A flow binding update request receiving unit capable of receiving a flow binding update request specifying at least one IP packet flow to be transferred to the technology;
A flow binding registration unit capable of registering a binding between the new home network prefix of the mobile node or an existing home network prefix and the IP packet flow specified by the flow binding update request. Te, the existing home network prefix of the mobile node, to establish the existing bidirectional IP tunnel between the second and the mobility anchor gateway the local mobility anchor, the second A flow binding registry already associated with the proxy care-of address of the second mobility anchor gateway by the second mobility anchor gateway and the local mobility anchor. And parts,
A flow binding completion report transmission unit capable of transmitting a flow binding completion message indicating that registration of the binding in the flow binding registration unit is completed to the second mobility anchor gateway;
I have a,
The flow binding registration unit
When the IP packet flow through the second wireless communication network system is not established between the mobile node and the local mobility anchor, the new home network prefix of the mobile node and the Register the binding with the IP packet flow specified in the flow binding update request,
The existing home network prefix and the flow when at least one IP packet flow is established between the mobile node and the local mobility anchor via the second wireless communication network system; A local mobility anchor that registers a binding with the IP packet flow specified by the binding update request. A first wireless interface that operates based on Proxy Mobile Internet Protocol Version 6 and communicates with the Internet via a first wireless communication network system using a first wireless access technology; Communicating with at least one mobile node having a second radio interface for communicating with the Internet via a second radio communication network system using a second radio access technology different from the one radio access technology Mobility anchor gateway,
The mobility anchor gateway belongs to the first wireless communication network system and is connected to a local mobility anchor capable of communicating with a counterpart node of the mobile node, and the mobility anchor gateway is At least one IP packet flow established between the mobile node and the local mobility anchor via the second wireless communication network system, operable as an access router of the mobile node It is possible to manage
Mobility anchor gateway
When at least one IP packet flow is established between the first radio interface of the mobile node and the local mobility anchor via the first radio communication network system; and A flow transfer indication sent from the mobile node when the mobile node wants to transfer at least one already established IP packet flow from the first radio access technology to the second radio access technology, comprising: Current state information that identifies a mobile node and the second radio interface of the mobile node used for the IP packet flow to be transferred and indicates whether the second radio interface is currently activated Flow that can receive flow transfer instructions including And the rolling instruction receiving unit,
When the flow transfer instruction receiving unit receives the flow transfer instruction, a flow transfer request may be transmitted to another mobility anchor gateway of another wireless communication network system that uses the second radio access technology. A possible flow transfer request transmitter,
The flow transfer request includes the mobile node, the second radio interface of the mobile node used for the IP packet flow to be transferred, and the mobile node from the first radio access technology to the second radio interface. When the IP packet flow to be transferred to the radio access technology is specified and the current state information in the flow transfer instruction indicates that the second radio interface is not currently activated, Said another mobility anchor to send a new connection request to said local mobility anchor to facilitate establishment of a bidirectional IP tunnel between said mobility anchor gateway and said local mobility anchor -Including the first transmission instruction to instruct the gateway, the previous When the current state information in the flow transfer instruction indicates that the second radio interface is currently activated, the IP packet flow specified in the flow transfer instruction is transferred to the other mobility anchor anchor. Instruct the second mobility anchor gateway to send a flow binding update request to the local mobility anchor to associate with a bidirectional IP tunnel between the gateway and the local mobility anchor Including a second transmission instruction,
Mobility anchor gateway. The flow transfer instruction receiving unit includes desired operation information indicating that the first radio interface should be active, and between the first radio interface of the mobile node and the local mobility anchor The flow transfer specifying that a part of a plurality of IP packet flows already established via the mobility anchor gateway should be transferred from the first radio access technology to the second radio access technology Upon receiving the instruction, the flow transfer request transmission unit transmits the flow transfer request specifying the IP packet flow specified by the flow transfer instruction to the another mobility anchor gateway, and the mobility anchor request Gateway is said another mobility anchor gateway Even after the IP packet flow identified in the flow transfer request from the mobility anchor gateway is established between the second radio interface of the mobile node and the local mobility anchor , Another IP packet flow among the IP packet flows already established via the first wireless communication network system between the first wireless interface of the mobile node and the local mobility anchor. maintain,
The mobility anchor gateway according to claim 9 . When the flow transfer instruction receiving unit receives the flow transfer instruction including desired operation information indicating that the first radio interface should be deactivated from the activated state, the flow transfer request transmitting unit All of one or more IP packet flows already established via the first radio communication network system between the first radio interface of the mobile node and the local mobility anchor, Sending the flow transfer request specifying that the first radio access technology should be transferred to the second radio access technology;
The mobility anchor gateway according to claim 9 . The mobility anchor gateway transmits a copy of an IP packet transmitted on the IP packet flow that the mobile node wishes to transfer from the first radio access technology to the second radio access technology to the other mobility access gateway. Do not forward to anchor gateway,
The mobility anchor gateway according to any one of claims 9 to 11 . A first wireless interface that operates based on Proxy Mobile Internet Protocol Version 6 and communicates with the Internet via a first wireless communication network system using a first wireless access technology; Communicating with at least one mobile node having a second radio interface for communicating with the Internet via a second radio communication network system using a second radio access technology different from the one radio access technology Mobility anchor gateway,
The mobility anchor gateway belongs to the second wireless communication network system, is connected to a local mobility anchor capable of communicating with the counterpart node of the mobile node, and can operate as an access router of the mobile node Is capable of managing at least one IP packet flow established between the mobile node and the local mobility anchor via the second wireless communication network system;
The mobility anchor gateway
A proxy care-of address indicating the mobility anchor gateway, and
From another mobility anchor gateway of another wireless communication network system using the first radio access technology, the mobile node and the second of the mobile node used for the IP packet flow to be transferred Identifying the radio interface and the IP packet flow that the mobile node wishes to transfer from the first radio access technology to the second radio access technology, and issuing a new connection request to the local mobility anchor A first transmission instruction for instructing the mobility anchor gateway to transmit, or a second transmission instruction for instructing the mobility anchor gateway to transmit a flow binding update request to the local mobility anchor Flow transfer including And flow transfer request receiving unit capable of receiving calculated,
When the flow transfer request received by the flow transfer request reception unit includes the first transmission instruction, it prompts establishment of a bidirectional IP tunnel between the mobility anchor gateway and the local mobility anchor. Therefore, a new connection request transmitter capable of transmitting a new connection request specifying the mobile node and the proxy care-of address of the mobility anchor gateway to the local mobility anchor;
A bidirectional IP tunnel between the mobility anchor gateway and the local mobility anchor based on the new home network prefix of the mobile node and the proxy care-of address of the mobility anchor gateway A new home network prefix receiving unit capable of receiving a new home network prefix of the mobile node from the local mobility anchor;
When the new home network prefix receiving unit receives the new home network prefix of the mobile node, establishment of a connection between the second radio interface of the mobile node and the mobility anchor gateway An interface activation unit capable of activating the second radio interface of the mobile node specified by the flow transfer request;
A connection confirmation unit capable of confirming establishment of a connection between the second radio interface of the mobile node and the mobility anchor gateway;
When the connection confirmation unit confirms the establishment of the connection, the IP packet flow specified by the flow transfer request is transferred to the bidirectional IP tunnel between the mobility anchor gateway and the local mobility anchor. When the flow transfer request including the second transmission instruction is received by the flow transfer request receiving unit, it is possible to transmit a flow binding update request to the local mobility anchor for association. A flow binding update request transmitting unit capable of transmitting an update request to the local mobility anchor, wherein the flow binding update request includes the mobile node, the proxy care-of address of the mobility anchor gateway, and Said identifying and said IP packet flow to be mobile node moved from the first radio access technology to the second radio access technology, a flow binding update request transmission unit,
A flow binding completion report receiving unit for receiving a flow binding completion message from the local mobility anchor;
Using the connection between the second radio interface of the mobile node and the mobility anchor gateway and the bidirectional IP tunnel between the mobility anchor gateway and the local mobility anchor, The IP packet flow that the mobile node wants to transfer from the first radio access technology to the second radio access technology, and the IP packet flow specified by the flow transfer request from the mobility anchor gateway A flow establishment unit capable of being established between the second radio interface of the mobile node and the local mobility anchor;
A mobility anchor gateway. The mobility anchor gateway transmits a copy of an IP packet transmitted on the IP packet flow that the mobile node wishes to transfer from the first radio access technology to the second radio access technology to the other mobility access gateway. Do not receive from the anchor gateway,
The mobility anchor gateway according to claim 13 . The interface activation unit activates the second radio interface of the mobile node when the flow transfer request received by the flow transfer request reception unit includes the first transmission instruction;
The mobility anchor gateway according to claim 13 or claim 14 .

Images