KR101368423B1 - Simultaneous binding typed mobility management method based on HMIPv6 standard - Google Patents

Abstract

When a mobile node having a plurality of wireless communication interfaces transmits and receives data with a corresponding node, the connection is disconnected due to handover, and the network interface immediately creates a new connection, thereby concurrently binding at all times. There is provided a mobility management method to maintain. The mobility management method of a mobile node having a first network interface and a second network interface according to the present invention is activated by connecting the mobile node to a first access router through the first network interface, Is activated by being connected to a second access router via the second network interface, and the mobile node is connected to the Hierarchy Mobile IP version 6 (HMIPv6) standard through simultaneous binding using the first network interface and the second network interface. If the strength of the signal received through the first network interface decreases below the disconnection threshold, the mobile node deactivates the first network interface and then reactivates it unconditionally. To restore concurrent bindings .

Description

Simultaneous binding typed mobility management method based on HMIPv6 standard

The present invention relates to a method of concurrent binding mobility management based on the HMIPv6 standard. In more detail, the mobile node 100 having a plurality of wireless communication interfaces transmits and receives data to and from a corresponding node, thereby satisfying a predetermined Quality of Service (QoS). It relates to a mobility management method.

Since adopting IPv6 for Internet access in Vehicle Ad-hoc NETworks (VANET), MIPv6 (Mobile IP version 6), a three-layer mobility support protocol for mobility management of vehicle Internet communications in Vehicle to Infrastructure (V2I) communications. In addition, the use of Fast Handover Mobile IP version 6 (FMIPv6), Hierarchy Mobile IP version 6 (HMIPv6), and NEtwork MObility (NEMO) have been considered. Most MIPv6 and its extended protocols are not suitable for applications in latency sensitive vehicle networks. The reason for this is that in a vehicle that changes the direction of movement frequently or moves at a high speed, packet loss or delay time may be greatly increased during handover.

However, when a patient using the U-health service is in an ambulance and assuming that the ambulance moves at a high speed, the U-health message transmitted by the U-health terminal is transmitted to the U-health server without interruption even in a vehicle moving at high speed. If there is a type of u-health service that requires a certain quality of service (QoS), it is required to provide a mobility management method of not only seamless but also QoS. Therefore, it is essential to provide a QoS-guaranteed mobility management method for the proliferation of u-health services.

The technical problem to be solved by the present invention is that a mobile node having a plurality of wireless communication interfaces transmits and receives data to and from a corresponding node, and thus disconnects due to handover. By creating the above, it is to provide a mobility management method that maintains concurrent binding at all times.

The technical objects of the present invention are not limited to the above-mentioned technical problems, and other technical subjects not mentioned can be clearly understood by those skilled in the art from the following description.

In the mobility management method of a mobile node having a first network interface and a second network interface according to an aspect of the present invention for achieving the technical problem, the mobile node, through the first network interface, a first access router Is activated by being connected to the mobile node and is activated by being connected to a second access router via the second network interface, wherein the mobile node is concurrently bound using the first network interface and the second network interface. Is connected to a Mobility Anchor Point (MAP) according to Hierarchy Mobile IP version 6 (HMIPv6) standard, and when the strength of a signal received through the first network interface decreases below a disconnection threshold, the mobile node is connected to the first network. After deactivating an interface, reactivate without conditions Including those comprising more than restore the simultaneous binding.

According to the present invention as described above, even after the handover to maintain the simultaneous binding to maximize the network interface resources held by the mobile node. That is, the mobility management method according to the present embodiment has the effect of maximizing the probability that QoS can be satisfied by maximizing the network interface resources held by the mobile node.

In addition, by using a plurality of network interfaces provided in the mobile node there is an effect that can support a handover without disconnection and loss of data.

1 is a first block diagram showing a configuration of a mobile node according to a first embodiment of the present invention.
2 is a second block diagram showing a configuration of a mobile node according to the first embodiment of the present invention.
3 is a third block diagram illustrating a configuration of a mobile node according to the first embodiment of the present invention.
4 is a conceptual diagram illustrating a mobility management method of a mobile node according to a second embodiment of the present invention.
5 is a flowchart of a method for managing mobility of a mobile node according to a second embodiment of the present invention.
6 is a conceptual diagram illustrating a method for managing mobility of a mobile node according to a second embodiment of the present invention.
7 is a flowchart of a method for managing mobility of a mobile node according to a second embodiment of the present invention.
8 is a conceptual diagram illustrating a mobility management method of a mobile node according to a third embodiment of the present invention.
9 is a flowchart of a method for managing mobility of a mobile node according to a third embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention and the manner of achieving them will become apparent with reference to the embodiments described in detail below with reference to the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Is provided to fully convey the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

Unless defined otherwise, all terms (including technical and scientific terms) used herein may be used in a sense commonly understood by one of ordinary skill in the art to which this invention belongs. Also, commonly used predefined terms are not ideally or excessively interpreted unless explicitly defined otherwise.

Duplicate description of the published standard technology HMIPv6 is omitted. In addition, among the HMIPv6 based technologies by the mobile node 100 having a plurality of network interfaces, "A method for managing high-speed mobility using multi-cast tunneling in a vehicle network, Journal of Korean Institute of Communication Sciences '10 -11 Vol.35 No.11, Chun Seung-man E-HMIPv6 technology described in ", Jae Wook, Park Jong-tae" will not be duplicated.

In addition, in the present specification, that the network interface included in the mobile node 100 is "activated", which means that the network interface is connected to an access point or an access router to transmit and receive data, and conversely, "deactivate". This means that there is no connected access point or access router.

The mobile node 100 according to the first embodiment of the present invention will be described with reference to FIGS.

The mobile node 100 according to the present embodiment has two or more network interfaces. The mobile node 100 may include two or more interfaces 133 and 134 for performing wireless communication in the same manner, as shown in FIG. 2, or perform wireless communication in another manner, as shown in FIG. 3. It may be provided with two or more interfaces 135, 136, 137. Since the mobile node 100 illustrated in FIGS. 2 and 3 differs only in an interface provided with the mobile node 100 illustrated in FIG. 1, the mobile node 100 is described with reference to FIG. 1 for convenience of description. Explain.

The mobile node 100 may include a binding cache table storage 110. The binding cache table storage unit 110 stores address information necessary for performing HMIPv6 based mobility management. In more detail, HoA (Home Address), Regional Care-of Address (RCoA), and a plurality of on-link Care-of Address (LCoA) are stored.

The binding cache table storage unit 110 may include a nonvolatile memory device such as flash memory, a volatile memory device such as random access memory (RAM), and a storage medium such as a hard disk drive. At least one may be implemented but is not limited thereto.

The binding cache table storage unit 110 may store the binding cache table described in Table 1.

As shown in FIG. 1, the binding cache table shown in Table 1 included in the mobile node 100 including the two interfaces 131 and 132 includes two interfaces, LCoA1 and LCoA2, respectively. LCoA is connected to MAP, and RCoA assigned to MAP is the same as RCoA1. There are two entries in the binding cache table. When the connection between the interface corresponding to each entry and the access router is lost, the entry is deleted from the binding cache table. When a new connection between the interface and the access router is established, the binding cache table is established. The new entry is inserted. The binding cache table as shown in Table 1 may also be stored in the MAP.

The reason why the plurality of LCoAs are stored in the binding cache table storage unit 110 is because the mobile node 100 includes the plurality of interfaces 131 and 132. That is, the plurality of interfaces 131 and 132 may be connected to different access routers AR using different LCoAs.

For example, interface 1 131 may be connected to a PAR (Previous Access Router) using LCoA1, and interface 2 132 may be connected to a next access router (NAR) using LCoA2. As described in the Journal of E-HMIPv6, the mobile node 100 simultaneously binds through an Extended-Mobility Anchor Point (E-MAP), a first tunnel through a PAR, and a second tunnel through a NAR. By doing so, it is possible to prevent packet loss during micro handover in the E-MAP jurisdiction.

The mobile node 100 may further include a routing controller 120. The routing controller 120 may add or delete each entry stored in the binding cache table storage unit as the connection is established and disconnected. In addition, the routing controller 120 may determine each interface 131 or 132 according to a calculation result of a signal strength (RSSI) received by each interface 131 or 132 and a data rate received by each interface 131 or 132. The establishment or disconnection of the control may be controlled through the interface manager 130.

The interface manager 130 controls connection establishment or disconnection of each interface 131 and 132 under the control of the routing controller 120.

Next, a mobility management method of the mobile node 100 according to the second embodiment of the present invention will be described with reference to FIGS. 4 to 5.

4 illustrates a case where a mobile node 100 having two interfaces IF1 and IF2 is moving in a management area of the MAP 204. The mobile node 100 transmits / receives data with the corresponding node 200, and the HOME AGENT 202 operates as a HOME AGENT on the HMIPv6 standard.

The management zone of the MAP 204 may mean a set of coverages of access routers connected to the MAP 204. For convenience of description, in FIG. 4, only two PAR 206 and NAR 208 are described as an access router connected to the MAP 204, but the number of access routers connected to the MAP 204 is illustrated in FIG. 4. The above may be added, and this is the same in FIGS. 6 and 8.

The MAP 204 may be to perform the function of the E-MAP described in the journal about E-HMIPv6, and the mobile node 100 also uses the media gateway (MG) described in the journal on E-HMIPv6. It may be to perform the function of).

According to the HMIPv6 standard and general mobile IP technology, the start time of the handover procedure is when the signal strength (RSSI) from the currently connected access point or access router is below a predetermined limit. However, although there may be a certain relationship between the signal strength and the data rate, even if the signal strength is high, the data rate may drop when there are many connected access points or other mobile nodes 100 connected to the access router. . Therefore, performing handover based only on signal strength may not satisfy the data rate according to a predetermined QoS.

On the other hand, QoS can be defined according to various criteria, the scope of the present invention is not limited to the QoS based on a specific criteria. The QoS may be specified according to the type of application executed in the mobile node 100 or according to the QoS type included in the packet transmitted or received by the mobile node 100. However, for convenience of description, a case of defining QoS based on a data rate will be described.

The mobility management method according to the present embodiment establishes a new connection until the data transmission rate according to a predetermined QoS is satisfied even if the signal strength from the connected access router does not meet the handover initiation threshold.

Hereinafter, the mobility management method according to the present embodiment according to the situation shown in FIG. It is assumed that the minimum data rate required according to QoS is 100KB / S.

IF1 included in the mobile node 100 is connected to the PAR 206, and the mobile node 100 is located in a management domain (Previous Domain) of the PAR 206. At this time, it is assumed that the mobile node 100 has a data rate of 150 KB / S through data transmission and reception using only IF1. In this case, since the data rate exceeds the minimum data rate, even if the IF2 is not connected, no attempt is made to establish a new connection by the IF2.

Next, if the data rate falls to 80 KB / S as the mobile node 100 moves, the mobile node 100 establishes a new connection using IF2 not connected. The establishment of a new connection by the IF2 may be made for the PAR 206 that is already connected to IF1, or for the NAR 208 which is another access router not connected to the IF1. The establishment of the connection between the interface included in the mobile node 100 and the access router, the tunnel establishment between the MAP 204 and the mobile node 100, and the Local Binding Update (LBU) method are described in the Journal of E-HMIPv6. Since it is described, a separate description is omitted.

In FIG. 5, as the mobile node 100 moves, the data rate drops to 80 KB / S. As a result, IF2 is connected to the NAR 208 to increase the data rate to 150 KB / S. In this case, since the data rate exceeds the lowest data rate, no further connection establishment attempt is attempted. However, even if IF2 is connected to the NAR 208, if the data rate is less than the lowest data rate, if there is an interface that is not connected to the mobile node 100, then when a new connection establishment attempt is made, the data rate exceeds the lowest data rate. Can be achieved continuously.

Next, when the signal strength from the PAR 206 falls below the disconnection threshold as the distance between the PARs 206 increases as the mobile node 100 moves to the NAR 208 managed area (New Domain), IF1 of mobile node 100 disconnects from PAR 206. Since the disconnection between the interface included in the mobile node 100 and the access router and a local unbinding update (LUU) method are described in the above-described journal about E-HMIPv6, a separate description thereof will be omitted.

In the mobility management method according to the present embodiment, even if the signal strength from the connected access router does not meet the handover initiation criterion, a new connection is established until the data transmission rate according to the predetermined QoS is satisfied. There is an effect that can satisfy the maximum data transfer rate.

Next, the mobility management method according to the present embodiment will be described with reference to FIG. 5. 5 is a flowchart of a mobility management method according to the present embodiment.

First, the mobile node 100 measures the current total data rate (S500). The total data rate refers to a data rate in which data transmission and reception of the entire interface connected to a current access point or an access router among two or more interfaces included in the mobile node 100 is reflected.

Next, if the total data rate exceeds the data rate required according to QoS (S502), since the current data transmission and reception satisfies the level required by the QoS, no new connection establishment attempt is attempted.

On the contrary, when the total data rate is less than the data rate required according to QoS (S502), by selecting one of the disabled interfaces among the interfaces included in the mobile node 100, a new connection establishment and local by the selected interface A binding update procedure is performed (S504 to S511).

Since new connection establishment and local binding update procedures (S504 to S511) by the selected interface are described in the above journal about E-HMIPv6, they will be briefly described except for duplicate contents.

First, router discovery is performed through the selected interface (S506). The router discovery may be understood as sending a Router Solicitation (RS) message through the selected interface and discovering a router that responds to it. If more than one router responds, the best router is selected according to a predetermined criterion.

The selection criterion of the best router may be at least one of the strength of the RSSI signal value and the number of connected terminals.

The selected router is referred to as NAR (Next Access Router).

Next, the mobile node 100 generates a new LCoA_new using the prefix information on the router to be connected (S508), and requests the NAR for duplicate address detection of the LCoA_new (S510).

If there is no abnormality in the result of the address duplication check of the LCoA_new, the mobile node 100 transmits a local binding update (LBU) message including information on the LCoA_new to the MAP through the NAR (S511).

The local binding update message may contain a flag for notifying identification information of an interface. The local binding update message complies with the [RFC 5380] [RFC 3775] standard, and the single bit flag is defined as A, H, L, K, and M. At this time, for example, if there are two network interfaces IF1 and IF2 in the mobile node 100, A and M flags may be set in the local binding update message by IF1, and in the local binding update message by IF2. The A, M, and O flags can be set. That is, the O flag can be used to distinguish the interface.

The MAP determines which LCoA for which of the interfaces of the mobile node 100 is updated by using the O flag included in the local binding update message. If it is for an interface that is not included in the binding cache table, an entry consisting of the data contained in the received local binding update message will be added to the binding cache table. For example, in a situation where there is a binding cache table entry of LCoA1 for IF1 in the MAP, when a local binding update message of LCoA2 for IF2 is received, the MAP consists of data included in the received local binding update message. Added entries will be added to the binding cache table. In addition, not only a packet having LCoA1 as a sender address but also a packet having LCoA2 as a sender address will be transmitted to the corresponding node 200. In addition, a packet in which the home address (HoA) of the mobile node 100 is designated as a recipient address (Dst Address) is multicasting tunneling through a first tunnel having LCoA1 as a receiver and a second tunnel having LCoA2 as a receiver. Will be transmitted in a distributed manner.

As a result of the establishment of a new connection by the selected interface, the number of ACTIVE interfaces is increased (S512). If the strength (RSSI) of a signal received by a specific interface among the interfaces operating according to the movement of the mobile node 100 falls below the disconnection threshold Tc, the specific interface is disconnected and deactivated (DEACTIVATED). ) State is changed (S513). The disconnection reference value Tc may be, for example, -80 dBm.

As a result of the establishment of a new connection by the selected interface, no action is taken when the total data rate exceeds the data rate required by QoS, but the overall data rate is required by QoS. If the data rate still falls below, the new connection establishment operation may be performed repeatedly. That is, the mobility management method according to the present embodiment establishes a new connection until the data rate according to a predetermined QoS is satisfied. In FIG. 4, the mobile terminal 100 having only two interfaces is illustrated, but as the number of interfaces included in the mobile terminal 100 increases, the probability of satisfying the required transmission rate according to QoS increases.

In the mobility management method according to the present embodiment, when the total data rate is less than the data rate required according to QoS, the data rate may be increased by adding a communication path using the available interface as much as possible. As a result, the data rate according to QoS may be increased. It is effective to guarantee as much as possible.

Next, a mobility management method of the mobile node 100 according to the third embodiment of the present invention will be described with reference to FIGS. 6 to 7.

FIG. 6 also illustrates a case where the mobile node 100 having two interfaces IF1 and IF2 is moving in the management area of the MAP 204 as in FIG. 4.

The mobility management method according to the present embodiment replaces the existing connection until the data transmission rate according to the predetermined QoS is satisfied even if the signal strength from the connected access router does not meet the handover initiation threshold. That is, when two or more interfaces included in the mobile node 100 do not satisfy the predetermined data rate while all of them are connected with the access router, one of the interfaces is selected, and the selected interface is connected to the other access router. To be possible. In this case, the selected interface may be the lowest data rate among the interfaces provided in the mobile node 100.

Hereinafter, the mobility management method according to the present embodiment according to the situation shown in FIG. It is assumed that the minimum data rate required according to QoS is 100KB / S.

IF1 included in the mobile node 100 is connected to the PAR 206, and IF2 is connected to the NAR 208. That is, all interfaces included in the mobile node 100 are in an ACTIVE state. Nevertheless, as shown in FIG. 6, the data rate does not satisfy the data rate according to the QoS specified as 80 KB / S. In this case, the mobile node 100 according to the present embodiment will replace the connection.

First, the mobile node 100 selects an interface to replace the connection. As a criterion for selecting a connection replacement target interface, at least one of RSSI and data transmission rate may be used, and one of the interface replacement target interfaces having the best data transmission performance is selected using the criteria.

In FIG. 6, it is assumed that IF2 is selected as a connection replacement interface, and as a result, the connection access router of IF2 is replaced from NAR 208 to NAR2 209. As shown in FIG. 6, the data transfer rate increased from 80 KB / S to 120 KB / S as a result of the connection replacement operation.

In FIG. 6, although the data rate exceeds the minimum data rate required according to QoS, as a result of the replacement of the access target router of IF2, in some cases, the minimum data rate required according to QoS is required despite the replacement of the access target router. It may not be exceeded. In this case, the selection of the connection target interface and the replacement of the connection target access router of the selected interface may be repeatedly performed.

In the mobility management method according to the present embodiment, even if the signal strength from the connected access router does not meet the handover initiation threshold, the existing connection is replaced with a new connection until the data rate according to the specified QoS is satisfied. There is an effect that can satisfy the maximum data rate according to the specified QoS.

Next, the mobility management method according to the present embodiment will be described with reference to FIG. 7. 7 is a flowchart of a mobility management method according to the present embodiment.

It is assumed that the mobile node 100 includes two or more network interfaces, and the two or more network interfaces are connected to each access router, that is, activated.

First, the mobile node 100 measures the current total data rate (S700). The total data rate refers to a data rate in which data transmission and reception of the entire interface connected to a current access point or an access router among two or more interfaces included in the mobile node 100 is reflected.

Next, if the total data rate exceeds the data rate required according to QoS (S702), the current data transmission and reception satisfies the level required by the QoS, thereby maintaining the current connection state. On the other hand, if the total data rate is less than the minimum data rate required according to the QoS (S702), the interface replacement target interface among the interfaces included in the mobile node 100 is selected (S704).

As described above, at least one of RSSI and data transmission rate may be used as a criterion for selecting a connection replacement target interface, and the one connection replacement target interface having the best data transmission performance is selected using the criteria. .

For the selected interface, the existing connection is disconnected, the new access router is discovered and connected, and local binding update is also performed (S706). That is, the mobile node 100 deactivates the selected interface and then reactivates it. At this time, in order to induce connection to a new access router according to the change of the location of the mobile node, a predetermined time interval may be given between reactivation after the deactivation.

Since the operation of connecting to the new access router has been described with reference to FIG. 5, the description thereof will not be repeated.

Next, a mobility management method of the mobile node 100 according to the fourth embodiment of the present invention will be described with reference to FIGS.

FIG. 8 also shows a case in which the mobile node 100 having two interfaces IF1 and IF2 is moving in the management area of the MAP 204 as in FIG. 4.

In the mobility management method according to the present embodiment, as in the mobility management method according to the third embodiment of the present invention, all interfaces included in the mobile node 100 are always connected to the router to secure the maximum data rate. We aim to do it.

When the strength RSSI of a signal received by a specific interface falls below the disconnection threshold Tc as the mobile node 100 moves, disconnecting the specific interface and changing the signal to a DEACTIVATED state. This is a normal handover process. According to the journal E-HMIPv6, when a mobile node moves from a PAR region to a NAR region, (1) in the PAR region, IF1 is connected to the PAR, and (2) IF2 is NAR in the overlap region of the PAR region and the NAR region. (3) In the NAR region, the strength of the signal received by the IF1 from the PAR falls below the disconnection threshold (Tc), and the connection between the IF1 and the PAR is disconnected. It is described that ends. That is, in the journal of E-HMIPv6, simultaneous binding is performed only in the overlapping region of the first access router region and the second access router region.

On the other hand, in the mobility management method according to the present embodiment, when the strength (RSSI) of the signal received by the specific interface falls below the disconnection threshold Tc as the mobile node 100 moves, Perform a new connection establishment operation. That is, for example, when the second interface included in the mobile node 100 is disconnected, the second interface immediately discovers a connectable access router without a condition and accesses one of the access routers responding thereto. By connecting to a router, it maintains simultaneous binding after handover.

That is, the mobility management method according to the present embodiment maintains simultaneous binding even after the handover to maximize the network interface resources held by the mobile node 100.

Hereinafter, a mobility management method according to the present embodiment will be described with reference to FIG. 8. IF1 included in the mobile node 100 is connected to the PAR 206, and the mobile node 100 is located in the management area of the PAR 206.

Next, as the mobile node 100 moves to the combined area of the management area of the PAR 206 and the management area of the NAR 208, IF2 included in the mobile node 100 is additionally connected to the NAR 208, The mobile node 100 is connected to the MAP 204 in a concurrent binding state. The establishment of the connection between the interface included in the mobile node 100 and the access router, the tunnel establishment between the MAP 204 and the mobile node 100, and the Local Binding Update (LBU) method are described in the Journal of E-HMIPv6. Since it is described, a separate description is omitted.

Next, if the signal strength from the PAR 206 falls below the disconnection threshold Tc as the distance between the PARs 206 increases as the mobile node 100 moves to the NAR 208 management zone, the move. IF1 of node 100 disconnects from PAR 206. Since the disconnection between the interface included in the mobile node 100 and the access router and a local unbinding update (LUU) method are described in the above-described journal about E-HMIPv6, a separate description thereof will be omitted.

The handover according to the general mobile IP technology does not take any further action after the connection between the IF1 and the PAR 206 is disconnected, but the mobile node 100 according to the present embodiment discovers an access router to which the disconnected IF1 can be immediately connected. In addition, by connecting to an access router of one of the access routers responding to it, the concurrent binding state is continuously maintained even after the handover. As shown in FIG. 8, IF1 may be directly connected to NAR3 210 after disconnection from PAR 206.

The mobility management method according to the present embodiment maintains simultaneous binding even after the handover to maximize the network interface resources held by the mobile node 100. That is, the mobility management method according to the present embodiment can maximize the probability that QoS can be satisfied by maximizing the network interface resources held by the mobile node 100.

A mobility management method according to the present embodiment will be described with reference to FIG. 9. 9 is a flowchart of a mobility management method according to the present embodiment.

When the specific interface included in the mobile node 100 drops the strength of the signal received from the access router (S900), instead of disconnecting the specific interface (S902), a new router is discovered and connected (S902). S904), thereby maintaining the simultaneous binding state.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, You will understand. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive.

Mobile node 100
PAR 206
NAR 208
MAP 204

Claims (5)

In the mobility management method of a mobile node having a first network interface and a second network interface,
The mobile node is activated by being connected to a first access router via the first network interface;
The mobile node is activated by being connected to a second access router via the second network interface;
The mobile node is connected to a Mobility Anchor Point (MAP) in Hierarchy Mobile IP version 6 (HMIPv6) standard through simultaneous binding using the first network interface and the second network interface;
If the strength of the signal received via the first network interface decreases below a disconnection threshold, the mobile node deactivates the first network interface and then reactivates it unconditionally to restore concurrent binding; But
The reactivation is,
Including being activated by being connected to a third access router different from the first access router,
After connecting to the third access router, it is determined whether the total data rate is less than the required data rate according to a predetermined Quality of Service (QoS),
When the total data rate is less than the data rate required according to the predetermined QoS, establishing a new connection until the total data rate is not below the data rate required according to the predetermined QoS. How to manage mobility. The method according to claim 1,
Restoring concurrent binding by reactivating without the above condition,
The mobile node discovers a new router;
The mobile node selects one of the routers that has responded to the discovery;
The mobile node automatically generates a new on-link care-of address (LCoA) using the prefix information of the selected router;
The mobile node requests Duplicate Address Detection of the new LCoA to the selected router;
And the mobile node sends a local binding update (LBU) message to the MAP via the selected router, the local binding update (LBU) message including information about the new LCoA. The method of claim 2,
Selecting one of the routers in response to the discovery,
And selecting one of routers responding to the discovery based on at least one of a strength of an RSSI signal value and a number of connected terminals. The method of claim 2,
Sending the local binding update (LBU) message to the MAP,
And transmitting to the MAP a local binding update message containing a flag for informing the identification information of the selected network interface, the mobility management method of a mobile node having a plurality of network interfaces. 5. The method of claim 4,
And the flag is an O flag of a local binding update message according to the HMIPv6 standard.

Images