KR101132295B1 - Method for supporting flow mobility in proxy mipv6 and system therefor - Google Patents

Abstract

PURPOSE: A flow mobility support method and a system thereof are provided to determine the mobility of flow within IP layer on a PMIPv6 network. CONSTITUTION: An MN(Mobile Node) transmits a packet of an address, which is allocated to one interface, to an LMA(Local Mobility Anchor) through a MAG(Mobile Access Gateway)(222, 224). The LMA registers the address to a binding cache entry(226). The flow is set to the interface which transmits the packet.

Description

Method for supporting flow mobility in Proxy MIPv6 and System therefor}

The present invention relates to a network access technology of a mobile station in a PMIPv6 environment, and more particularly, to a flow mobility support method for allowing a mobile terminal having a plurality of interfaces to transmit different flows through different interfaces in a PMIPv6 environment; It's about the system.

In the Proxy Mobile IPv6 (hereinafter referred to as PMIPv6) environment defined in S.Gundavelli, K. Leung, V.davarapalli, K. Chowdhurry and B. Patil, "Proxy Mobile IPv6", RFC 5213, AUG 2008, In the case where an attached mobile node (hereinafter referred to as MN) accesses a PMIPv6 network using multiple interfaces, the MN may access the network through only one interface even though multiple interfaces are installed. Was defined to be. However, this is inefficient because the MN equipped with multiple interfaces cannot access the PMIPv6 network using multiple interfaces at the same time.

Accordingly, in the related art, a method of transmitting an MN equipped with several interfaces using different interfaces for each flow has been proposed.

In other words, when the MN equipped with multiple interfaces accesses a PMIPv6 network using multiple interfaces simultaneously, the netext of the IETF supports the flow-based mobility for the MN to transmit different flows through different interfaces. In WG, T. Melia and S. Gundavelli, "Logical Interface Support for multi-mode IP Hosts", draft-ietf-netext-logical-interface-support-01 (work in progress), Oct. We decided to use the logical interface defined in 2010.

And CJ. Bernardos, "Proxy Mobile IPv6 Extensions to Support Flow Mobility", draft-bernardow-netext-pmipv6-flowmob-01 (work in progress), Oct. In 2010, we proposed a flow-based mobility support scheme using the logical interface defined in the PMIIPv6 network. In this technique, when an MN accesses a PMIPv6 network using multiple interfaces and transmits a flow using one of them, the MN determines the interface to transmit the flow in the PMIPv6 network and transmits the flow through the corresponding interface. However, this technique has a disadvantage in that it cannot reflect the user's intention because the MN cannot determine which interface to use to transmit the flow in the network.

And T. Tran, Y. Hong and Y. Han, "Flow mobility support in PMIPv6" draft-trung-netext-flow-mobility-support-01 (work in progress), Oct. In 2010, you define triggering to determine the interface for sending flows. In this document, triggering to initiate the mobility of the flow in the host and triggering to initiate the mobility of the flow in the network are defined.

And when the flow initiates mobility in the host, the MN is T. Narten, E. Nordmark. The use of router solicitation (hereinafter referred to as RS) as defined in W. Simpson, and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6), REC 2461, Sep. 2007 After adding the information, the RS message is transmitted through the interface to transmit the flow, and since then, the MN transmits the flow through the interface, but this technique has a disadvantage in that the format of the existing RS message has to be changed. there was.

An object of the present invention is to provide a flow mobility support method and system that enables a mobile terminal having a plurality of interfaces to transmit different flows through different interfaces in a PMIPv6 environment.

PMIPv6 network system according to the present invention for achieving the above object, MN having a plurality of interfaces; A plurality of gateways corresponding to each of the plurality of interfaces of the MN to perform communication through the plurality of interfaces; An LMA communicating with a plurality of interfaces of the MN through the plurality of gateways, wherein the MN transmits a packet of an address assigned to one of the plurality of interfaces through another interface and a corresponding MAG. Send to the LMA and if the LMA differs from the interface of the address to which the packet is assigned and the interface from which the packet was sent, set the flow to the address to which the packet is assigned to the interface from which the packet was sent and the MAG. Register with a binding cache entry.

The above-described present invention proposes a host-based flow mobility support scheme for allowing a user of an MN to determine an interface on which a flow is transmitted. Allows you to determine the mobility of flows within the hierarchy.

In addition, the present invention does not need to further define an additional control message between the MN and MAG, and between the MAG and LMA to support the mobility of the flow, it is also easy to apply to PMIPv6-based network.

In addition, the present invention is that when the MN wants to exchange VoIP traffic with any host on the Internet, some users select a 3GPP based mobile communication network suitable for QoS requirements, and another user is a low-cost high-bandwidth wireless LAN network There is an effect that the user's selection range can be expanded, such as to select.

1 is a structural diagram of a PMIPv6 network in accordance with a preferred embodiment of the present invention.
2 is a flowchart of a method for supporting flow mobility in a PMIPv6 environment according to a preferred embodiment of the present invention.

According to the present invention, when the MN accesses a PMIPv6 network using multiple interfaces in an environment where a logical interface is implemented in the MN, the MN determines an interface for transmitting a flow, and when the flow is transmitted through the determined interface, the PMIPv6 is determined. It supports mobility of flow in network.

<PMIPv6 Network Structure>

1 illustrates a PMIPv6 network structure according to a preferred embodiment of the present invention.

Referring to FIG. 1, the PMIPv6 network includes a plurality of MAGs and a Localized Mobility Anchor 114. Herein, the MAG only shows the first and second MAGs 112 and 114 for the sake of explanation.

The first and second MAGs 110 and 112 operate as default gateways in the first and second access networks to which the MN 100 is connected. These first and second MAGs 110 and 112 communicate with the LMA 114 as well as with the first and second interfaces 102 and 104 of the MN 100 via first and second access networks.

The LMA 114 operates as a home agent for the MN 100 in the PMIPv6 domain, performs communication with the first and second MAGs 110 and 112, and is connected through the Internet, which is an external network. The communication with the terminal 116 is performed.

In particular, the LMA 114 binds information about the MN 100 that transmitted the packet when the source IPv6 address of the packet received from the MN 100 and the interface of the MN 100 that transmitted the packet are different from each other. It registers a cache entry and sends a packet to the source IPv6 address to the interface of the MN 100 that transmitted the packet.

The MN 100 includes first and second interfaces 102 and 104, a logical interface 106, and an IP 108. The MN 100 has N interfaces and can simultaneously access N access networks having N different characteristics in the PMIPv6 network using the N interfaces. Here, the MN 100 is provided with one or more first and second interfaces 102 and 104 to connect to the first and second access networks, respectively.

<How to Support Flow Mobility in PMIPv6 Environment>

The flow mobility support method in the PMIPv6 environment according to the present invention will be described with reference to the flowchart of FIG. 2.

The MN 100 accesses the domain of the PMIPv6 network, accesses the first MAG 110 through the first interface 102 (step 200), and connects the first MN-HNP (MN-Home) to the first interface 102. 1MN-HoA, which is an IPv6 address belonging to a network prefix, is set (steps 202, 204, 206, and 208). That is, the first MAG 110 transmits the PBU to the LMA 114 according to the attachment request of the first interface 102, and accordingly, the LMA 114 sends the PBAck (HNP1) to the first MAG 110. The first MAG 110 returns the RA (HNP1) to the first interface 102 of the MN 100, and the MN 100 receives the RA (HNP1) and receives the first MN-HoA (MN_HoA1). To sign.

The MN 100 accesses the domain of the PMIPv6 network, accesses the second MAG 112 through the second interface 104 (step 210), and connects the second MN-HNP (MN−) to the second interface 104. 2MN-HoA which is an IPv6 address belonging to Home Network Prefix) is set (steps 212, 214, 216, 218). That is, the second MAG 112 transmits the PBU to the LMA 114 according to the ATTACHMENT request of the second interface 104, and accordingly, the LMA 114 sends the PBAck (HNP2) to the second MAG 112. The second MAG 112 returns RA (HNP2) to the second interface 104 of the MN 100, and the MN 100 receives the RA (HNP2) and receives a second MN-HoA (MN_HoA2). ).

Thereafter, the MN 100 transmits a flow through the first and second interfaces 112 and 110. The flow includes five pieces of information: a source IPv6 address, a destination IPv6 address, a protocol, a source port number, and a destination port number.

The IPv6 packet having the first MN-HoA as the source IPv6 address may be transmitted to the LMA 114 via the first MAG 110 using the first interface 102 of the MN 100. The LMA 114 transmits a packet to a destination IPv6 address of the packet, and when a packet to the source IPv6 address is received, the LMA 114 transmits the packet to the MN 100 through the first MAG 110 and the first interface 102. do.

In addition, the IPv6 packet having the second MN-HoA as the source IPv6 address is transmitted to the LMA 114 via the second MAG 112 using the second interface 104 of the MN 100. The LMA 114 transmits a packet to a destination IPv6 address of the packet, and when a packet to the source IPv6 address is received, the LMA 114 transmits the packet to the MN 100 through the second MAG 112 and the second interface 104. do.

Unlike the above, the MN 100 may transmit an IPv6 packet having the first MN-HoA as the source IPv6 address to the LMA 114 via the second MAG 112 using the second interface 104 according to a user's selection. (Steps 222, 224).

In this case, the LMA 114 checks whether the source IPv6 address information of the received IPv6 packet and the second MAG 114 or the second interface 104 correspond to each other, and checks the source IPv6 address information and the second MAG 114 or the first. If the two interfaces 104 do not correspond to each other and are identified as the address assigned by the first MAG 110 or the first interface 102, the MN 100 determines that it is requesting flow-based mobility and The flow registers the flow movement information indicating that the flow is transmitted through the second MAG 112 in the binding cache entry (step 226). Here, the LMA 114 stores and manages information on the interface and the MAG for the assigned address, and is used when detecting the flow movement as described above.

The LMA 114 then sends the packet to the destination IPv6 address of the packet.

If an IPv6 packet transmitted to the MN 100 is received from the terminal 116 corresponding to the destination IPv6 address, the LMA 114 has flow movement information for the corresponding destination IPv6 address in its binding cache entry. If the flow movement information exists, the packet is transmitted to the MN 100 through the second MAG 112 and the second interface 104 according to the flow movement information.

3 illustrates an example of a binding cache entry in which flow movement information is registered according to a preferred embodiment of the present invention.

The flow movement information registered in the binding cache entry is composed of MUG and interface addresses, proxy core identification information, and the like, participating in the flow for each identification information of the MN.

100: MN
102: first interface
104: second interface
110: first MAG
112: MAG
114: LMA

Claims (4)

A mobile node (MN) having a plurality of interfaces, a plurality of MAGs corresponding to each of the plurality of interfaces of the MN to perform communication through the plurality of interfaces, and the plurality of MNs through the plurality of mobile access gateways (MAGs). In the flow mobility support method in a PMIPv6 environment having a Localized Mobility Anchor (LMA) to communicate over a plurality of interfaces,
The MN transmitting a packet of an address assigned to one of the plurality of interfaces to the LMA through another interface and a corresponding MAG;
If the LMA differs between the interface at which the packet is assigned and the interface at which the packet was sent, register in the binding cache entry to set the flow to the address at which the packet is assigned to the interface at which the packet was sent and the MAG. Making;
Flow mobility support method comprising the. The method of claim 1,
And when the packet for the address registered in the binding cache entry is received, transmitting the LMA to an interface and a MAG registered in the binding cache entry. In the PMIPv6 network system,
An MN having a plurality of interfaces;
A plurality of gateways corresponding to each of the plurality of interfaces of the MN to perform communication through the plurality of interfaces;
An LMA communicating with a plurality of interfaces of the MN through the plurality of gateways;
The MN transmits a packet of an address assigned to one of the plurality of interfaces to the LMA through another interface and a corresponding MAG,
If the LMA differs between the interface at which the packet is assigned and the interface at which the packet was sent, register in the binding cache entry to set the flow to the address at which the packet is assigned to the interface at which the packet was sent and the MAG. PMIPv6 network system characterized in that. The method of claim 3,
When the packet for the address registered in the binding cache entry is received, the LMA transmits to the interface and MAG registered in the binding cache entry, PMIPv6 network system.

Images