KR101598109B1 - Method and system for robust distributed mobility management - Google Patents

Abstract

The present invention relates to a network management technique and, more particularly, to a method and system for managing distributed mobility. The present invention can provide the handover without a termination of servicing communications even if a mobile terminal is connected to a novel mobile anchor since the mobile anchor to which the mobile terminal is being connected stops a service in a distributed mobility management network. The method for managing the distributed mobility in a tactical mobile network consisting of a plurality of mobile anchors comprises the following steps: (a) determining whether a failure occurs in a first mobile anchor of the mobile anchors; (b) performing the handover by a mobile terminal from the first mobile anchor to a second mobile anchor of the mobile anchors when the failure occurs based on a determination result; (c) transmitting, by the second mobile anchor, an update request message for finding an available mobile anchor, to the mobile anchors; (d) transmitting, by a third mobile anchor which is to be the available mobile anchor, a response message for the update request message; and (e) generating traffic tunneling between the second and third mobile anchors.

Description

METHOD AND SYSTEM FOR ROBUST DISTRIBUTED MOBILITY MANAGEMENT [0002]

The present invention relates to a network management technique, and more particularly, to a network management technique, in which a mobile anchor connected to a mobile terminal in a distributed mobility management network provides a handover without interruption in service even when a service is stopped and a new mobile anchor is connected And more particularly to a method and system for managing distributed mobility.

The MIP (Mobile IP) and the PMIP (Proxy Mobile IP), which are standardized to support the mobility of the terminal, are centralized, so they are transmitted to HA (Home Agent) / LMA (Local Mobility Anchor) So bottlenecks can occur. Therefore, it is impossible to select the optimal route due to traffic concentration, and thus the transmission delay may increase. Also, it is impossible to communicate all terminals managed in case of HA / LMA failure.

Recently, DMM (Distributed Mobility Management) Working Group (DMG) has been discussing various DMM techniques that can make mobility management a distributed type. In the previously proposed distributed mobility management schemes, since the mobile anchor 1 acts as a home agent (HA) with respect to the IP (Internet Protocol) address initially allocated by the mobile node, if a failure occurs in the mobile anchor 1, Since handover is not possible, all packets that were being transmitted are discarded. That is, since a handover can not be performed when a mobile anchor fails, performance degradation due to service interruption occurs.

1. Korean Patent Publication No. 10-2010-0064286 2. Korean Registered Patent No. 10-1023063 (March 10, 2011)

1. Kim, Y., et al., "Distributed Mobility Management Techniques for Tactical Networks", The Journal of the Korean Institute of Communication Sciences, Vol. 39C No. 11 (Nov. 2014) - Fusion Technology pp.1078-1087 2. Kim, YH, "Network-based Distributed Mobility Management in Heterogeneous Networks," Korea University, 2014

The present invention has been proposed in order to solve the problem according to the above background art, and it is an object of the present invention to provide a handover method and a handover method for a mobile anchor, And to provide a robust distributed mobility management method and system capable of providing robust distributed mobility management.

In order to achieve the above-mentioned object, in order to achieve the above-mentioned object, it is an object of the present invention to provide a robust and reliable mobile anchor capable of providing handover without interrupting service even when a mobile anchor connected to the mobile terminal in the distributed mobility management network interrupts a service and accesses a new mobile anchor Thereby providing a distributed mobility management method.

The robust distributed mobility management method is a distributed mobility management method in a tactical mobile network comprising a plurality of mobile anchors,

(a) determining whether a failure has occurred in the first moving anchor among the plurality of moving anchors;

(b) if a failure occurs, handing over from the first mobile anchor to the second mobile anchor among the plurality of mobile anchors, if a failure occurs;

(c) sending an update request message to the plurality of mobile anchors to search for an available available moving anchor for use by the second moving anchor;

(d) sending a response message to the update request message by a third mobile anchor serving as the available movement anchor; And

(e) generating traffic tunneling between the second mobile anchor and the third mobile anchor.

The step (c) may further include transmitting the update request message when a timeout occurs in which a response message to the update request message sent from the second mobile anchor to the first mobile anchor is preset, when the handover occurs The method comprising the steps of:

Also, the update request message may be a destination of an IP (Internet Protocol) address of an opposite terminal to which the mobile terminal connects through communication, and the IP address is generated using HNP (Home Network Prefix) information .

In the step (c), the plurality of mobile anchors intercept the update request message and determine whether the mobile anchor is an available mobile anchor closest to the opposite terminal.

The determination whether the available mobile anchor is a direct connection with an opposite terminal or a determination of whether an opposite terminal is out of the mobile management domain is possible if the same is the same as the home network prefix managed by the home network prefix.

Also, if there is a mobile anchor directly connected to the opposite terminal, the corresponding mobile anchor is selected as the available mobile anchor, and the available mobile anchor includes a mobile terminal ID, a home network prefix, and a mobile anchor IP And a source IP is extracted from the update request message and used as a destination IP.

In addition, if a mobile terminal exists outside the mobility management domain, the mobile anchor is selected as the available mobile anchor, and the mobile terminal performs a role of a border router for the opposite mobile terminal.

Also, the second moving anchor may be configured to find the first moving anchor, which is a previous connecting position of the mobile terminal, from a central database of the tactical mobile network stored in advance.

In the step (c), after the handover is completed, the first mobile anchor is recovered from the failure and is normal, and if it is the mobile anchor closest to the opposite mobile terminal, the available mobile anchor is selected .

On the other hand, another embodiment of the present invention is a distributed mobility management system comprising a tactical mobile network composed of a plurality of mobile anchors, a mobile terminal, and a counter terminal, wherein the first mobile anchor The mobile terminal handover from the first mobile anchor to the second mobile anchor among the plurality of mobile anchors when it is determined that the mobile terminal has failed, Message to the plurality of mobile anchors, a third mobile anchor that is the available mobile anchor sends a response message to the update request message, and generates traffic tunneling between the second mobile anchor and the third mobile anchor The present invention can provide a distributed mobility management system.

According to the present invention, it is possible to perform robust distributed mobility management capable of handover without service interruption even in the case of a mobile anchor failure.

FIG. 1 is a conceptual diagram of a distributed mobility management system 100 according to an embodiment of the present invention.
2 is a sequence diagram illustrating a handover procedure when a mobile anchor failure occurs according to an embodiment of the present invention.
FIG. 3 is a flowchart illustrating a process of intercepting a PBU (Proxy Binding Update) message at each mobile anchor in the handover procedure shown in FIG. 2 to determine whether the mobile anchor is an available mobile anchor and performing a binding update procedure.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It is to be understood, however, that the invention is not to be limited to the specific embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

Like reference numerals are used for similar elements in describing each drawing.

The terms first, second, etc. may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.

For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. The term "and / or" includes any combination of a plurality of related listed items or any of a plurality of related listed items.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.

Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are to be interpreted as either ideal or overly formal in the sense of the present application Should not.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a method and system for robust distributed mobility management according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 is a conceptual diagram of a distributed mobility management system 100 according to an embodiment of the present invention. 1, a distributed mobility management system 100 includes a correspondent terminal 110, a mobile terminal 120 communicating with the opposite terminal 100, a communication terminal 120 communicating with the opposite terminal 110, And a tactical mobile network 130 for connecting the mobile terminal 100 and the mobile terminal 100 to each other. The tactical mobile network 130 includes a first moving anchor 131-1, a second moving anchor 131-2, and a third moving anchor 131-3. Of course, in FIG. 1, three moving anchors are shown for clarity of explanation, but three or more moving anchors can be constructed.

Meanwhile, in the previously proposed distributed mobility management schemes, since the first mobile anchor 131-1 acts as a home agent (HA) with respect to the IP address initially allocated by the mobile terminal, the first mobile anchor 131-1, A handover can not be performed for a flow that is being serviced, so that packets that are being transmitted are discarded.

In contrast, in the present invention, when the mobile terminal 120 moves to the second mobile anchor 131-2 due to a failure of the first mobile anchor 131-1 in the tactical mobile network 130, the second mobile anchor 131- 2 searches for an available mobile anchor to perform a handover for the flow being serviced by the corresponding mobile terminal 120. Accordingly, the second mobile anchor 131-2 transmits a PBU (Proxy Binding Update) message, which is an update request message, to find an available mobile anchor.

At this time, the third mobile anchor 131-3 receiving the PBU message recognizes that it is the mobile anchor closest to the opposite mobile terminal 110 and transmits a response message to the second mobile anchor 131-2 PBA (Proxy Binding Acknowledgment). In response to this message exchange, the third mobile anchor 131-3 transmits the packets for the flow through the second mobile anchor 131-2 and the traffic tunneling 133. [

2 is a sequence diagram illustrating a handover procedure when a mobile anchor failure occurs according to an embodiment of the present invention. Referring to FIG. 2, when a failure occurs in a previously connected first mobile anchor 131-1, a second mobile anchor 131-2 and a third mobile anchor 131-3 closest to the opposite terminal 110 And performs handover through traffic tunneling.

In other words, when the mobile terminal 120 handover from the first mobile anchor 131-1 to the second mobile anchor 131-2, the mobile terminal 120 determines whether the second mobile anchor performs a normal function And transmits a router solicitation (RS) message to the second mobile anchor 131-2 (S210). At this time, the second mobile anchor 131-2 transmits the first mobile anchor 131-1, which is the previous connection position of the mobile terminal 120, from the central DB managing the previous mobile anchor 131-1 information of the mobile terminal 120 -1). In general, all the mobile anchors store the mobile anchor information currently connected to the central DB when the mobile terminal newly connects or changes the connection location. In general, the central DB exists in the form of a separate device, and the mobile anchors know information such as an IP address for accessing the central DB in advance.

Thereafter, the second mobile anchor 131-2 transmits a PBU message, which is an update request message, to the first mobile anchor 131-1 (S220). Accordingly, if the second mobile anchor 131-2 fails to receive a PBA message, which is a response message to the update request message, from the first mobile anchor 131-1 during a preset timeout, (Rauter Advertisement) message (RA) to the mobile terminal 120 (S230).

If the response to the update request message (PBU) for 'update binding' sent to the first mobile anchor 131-1 which is the previous mobile anchor of the mobile terminal 120 does not come, The mobile anchor 131-2 regards the previous mobile anchor as having a failure, and finds a usable mobile anchor and performs a binding procedure.

That is, the second mobile anchor 131-2, which is a new mobile anchor, extracts the destination address (IP address of the opposite terminal) from the packet sent by the mobile terminal 120 using the previous IP address, and then transmits the IP address to the destination address And transmits an update request message (PBU) for 'binding update' to the third mobile anchor 131-3 (S240, S250).

The third mobile anchor 131-3 receiving the update request message (PBU) transmits a proxy message Acknowledgment (PBA) for the update request message to the second mobile anchor 131-2 (S260) .

According to this message exchange, traffic tunneling is formed between the second mobile anchor 131-2 and the third mobile anchor 131-3 (S270).

In addition, if the handover progresses normally, it operates in the same manner as existing schemes. When the mobile terminal 120 moves and connects to the second mobile anchor 131-2, which is a new mobile anchor, a new IP address is obtained by using HNP (Home Network Prefix) information included in a Router Advertisement (RA) message .

Meanwhile, the second mobile anchor 131-2, which is a new mobile anchor, obtains the information of the previous mobile anchor 131-1 that the mobile terminal 120 previously connected to from the 'central DB' Exchanges a message for binding update to the previous mobile anchor 131-1 and performs handover through traffic tunneling.

FIG. 3 is a flowchart illustrating a process of intercepting a PBU (Proxy Binding Update) message at each mobile anchor in the handover procedure shown in FIG. 2 to determine whether the mobile anchor is an available mobile anchor and performing a binding update procedure. Available available mobile anchors serve to transfer the flow through traffic tunneling with a new mobile anchor instead of the previous mobile anchor. Since the correspondent terminal 110 transmits an update request message for 'update binding' to the destination in order to find the available mobile anchor, the mobile anchor directly connected to the opposite terminal 110 or the nearest mobile anchor is selected as an available mobile anchor.

It can be an available moving anchor in the following cases. First, if the available mobile anchor (for example, 131-3 in FIG. 1) is directly connected to the opposite terminal (110 in FIG. 1), it has the same home network prefix (steps S310 and S330). In this case, the PBU message information is used to generate a binding cache entry. The binding cache entry may include a mobile terminal ID, a home network prefix, and a mobile anchor IP. Thereafter, the source IP of the PBU is set as the destination IP, and the PBA message is transmitted (step S340).

Second, when the mobile anchor is not directly connected to the opposite terminal but the next path of the message is out of the mobility management domain, the mobile anchor performs a role of an Area Border Router for the opposite terminal (Step S320). In this case, the mobile anchor generates a binding cache entry according to the received information, and transmits a response message for 'binding update' to the new mobile anchor to set up the traffic tunneling.

Since the traffic tunneling is performed with the new mobile anchor in the available mobile anchor, the handover is performed irrespective of whether the previous mobile anchor is operated or not. However, if the previous movement anchor is normal and the mobile anchor closest to the opposite terminal is selected in the available mobile anchor selection step, the previous movement anchor is selected as the available movement anchor.

When the previous mobile anchor is recovered from the failure after the handover procedure is completed, the previous mobile anchor recognizes that the mobile terminal has moved to the new mobile anchor through the 'central DB' managing the location of the mobile station.

100: Distributed mobility management system
110:
120: mobile terminal
130: Tactical mobile network
131-1 to 131-3: first moving anchor to third moving anchor

Claims (10)

1. A distributed mobility management method in a tactical mobile network comprising a plurality of mobile anchors,
(a) determining whether a failure has occurred in the first moving anchor among the plurality of moving anchors;
(b) if a failure occurs, handing over from the first mobile anchor to the second mobile anchor among the plurality of mobile anchors, if a failure occurs;
(c) sending an update request message to the plurality of mobile anchors to search for an available available moving anchor for use by the second moving anchor;
(d) sending a response message to the update request message by a third mobile anchor serving as the available movement anchor; And
(e) generating traffic tunneling between the second moving anchor and the third moving anchor,
Wherein the plurality of mobile anchors intercept the update request message and determine whether the mobile anchor is an available mobile anchor closest to the opposite terminal,
Wherein the update request message includes an IP (Internet Protocol) address of a correspondent terminal to which the mobile terminal connects through communication, and the IP address is generated using HNP (Home Network Prefix) information. How to manage.
The method according to claim 1,
Wherein the step (c) comprises: when the handover occurs, transmitting the update request message when a response message to the update request message sent from the second mobile anchor to the first mobile anchor is preset; Wherein the distributed mobility management method comprises:
delete delete The method according to claim 1,
Wherein the determination of whether the mobile anchor is an available mobile anchor is a direct connection to an opposite mobile terminal or a determination of whether an opposite mobile terminal exists outside a mobile management domain if the same is identical to a home network prefix managed by the mobile communication terminal.
6. The method of claim 5,
And if there is a corresponding mobile anchor connected directly to the opposite terminal, the corresponding mobile anchor is selected as the available mobile anchor, and a binding including the mobile terminal ID, the home network prefix, and the mobile anchor IP Generating a cache entry, extracting a source IP from the update request message, and using the source IP as a destination IP.
6. The method of claim 5,
Wherein if a mobile terminal exists outside the mobility management domain, the mobile anchor is selected as the available mobile anchor and performs a role of a border router for the opposite terminal.
3. The method of claim 2,
Wherein the second mobile anchor finds the first mobile anchor which is a previous connection position of the mobile terminal from a central database of the tactical mobile network to be stored in advance.
The method according to claim 1,
Wherein the step (c) comprises: if the first mobile anchor is recovered from the failure and is normal after the handover is completed, if the mobile anchor is closest to the opposing mobile terminal, the available mobile anchor is selected Distributed mobility management method.
1. A distributed mobility management system comprising a tactical mobile network comprising a plurality of mobile anchors, a mobile terminal, and a counter terminal,
Determining whether a failure has occurred in the first mobile anchor among the plurality of mobile anchors, and if a failure occurs, the mobile terminal handover from the first mobile anchor to the second mobile anchor of the plurality of mobile anchors, The second mobile anchor sends an update request message to the available mobile anchors to find available available mobile anchors, the third mobile anchor, which is the available mobile anchor, sends a response message to the update request message, Generates traffic tunneling between the second mobile anchor and the third mobile anchor,
Wherein the plurality of mobile anchors intercept the update request message to determine whether the mobile anchor is an available mobile anchor closest to the opposite terminal,
Wherein the update request message includes an IP (Internet Protocol) address of a correspondent terminal to which the mobile terminal connects through communication, and the IP address is generated using HNP (Home Network Prefix) information. Management system.

Images