KR101394605B1 - A handover support method multimode mobile node and mobile node action - Google Patents

Abstract

The present invention relates to a handover support method for a multimode mobile node in a PMIP domain and its mobile node. The present invention sets a first state value for identifying a network connected to a first device when detecting a network connection trigger to a first MAG generated in a first device connected to a new network according to a handover, (PBA) request message according to the handover type to the first MAG, receives the PBA message, and sets the first device to the first MAG. set to the state of the remaining devices, and then deletes the routing information for the mobile node remaining in the second MAG that was previously connected, and transmits the RA message having the lifetime of 0 to the mobile node Lt; RTI ID = 0.0 > uplink < / RTI >

Handover, heterogeneous network, PMIP, mobile node, routing information

Description

[0001] The present invention relates to a handover support method for a multi-mode mobile node in a PMIP domain,

The present invention relates to handover in network-based Localized Mobility Management. In particular, the present invention supports vertical handover and horizontal handover for a multimode mobile node (MN) having a plurality of different network interface devices (hereinafter referred to as devices) in the PMIPv6 (Proxy Mobile IP) domain And a mobile node thereof.

Generally, IPv6 plays a role of a terminal identifier indicating a mobile node and a network identifier indicating a location of a mobile node in a network. Due to the duality of IPv6, handover problems occur. Since the location of the connected network has changed, the network identifier has to be changed. However, when the new address is used, the existing identifier can not be changed because the terminal identifier is changed.

In order to solve this problem, a MIPv6 (Mobile IPv6: MIPv6) technique has been proposed to enable a mobile node to maintain a previously established connection even if the mobile node changes its location. The MIPv6 protocol is a node-based mobility support protocol. In the mobile node itself, the mobile node provides the mobile node with the unique address and the temporary address of the mobile node as binding information. When the mobile node moves, it changes only the temporary address corresponding to the mobile node, .

Meanwhile, a network-based local mobility management scheme that supports the mobility of a mobile node in an access network is proposed and standardized so that the current connection can be maintained even for a mobile node not equipped with the MIPv6 function. Such network-based local mobility management is performed according to PMIPv6 (Proxy MIP), and the communication flow in a general PMIP network is shown in FIG.

1 is a signal flow diagram illustrating a network access control procedure for a mobile node connected to a new network in a general PMIP network.

When the mobile node 10 is connected to the MAG 20, the MAG 20 acquires the identifier and profile of the mobile node 10, generates a terminal connection event trigger , The MAG 20 requests a PBU (Proxy Binding Update) to the LMA (Local Mobility Anchor) 30.

The LMA 30 accepts the PBU request of the MAG 20, allocates the total network prefix of the terminal, sets the routing information (e.g., routing table and rule), sets the BCE (Binding Cache Entry) do. The LMA 30 transmits a Proxy Binding Acknowledge (PBA) to the MAG 20 in response to the PBU.

The MAG 20 accepts the PBA of the LMA 30 to set up a bi-directional tunnel between the LMA 30 and set up the routing information corresponding to the mobile node 10. Thereafter, the mobile node 10 transmits a Router Solicitation to the MAG 20, and the MAG 20 transmits a Router Advertisement (RA) to the mobile node 10 in response to the Router Advertisement send.

However, as shown in FIG. 1, in the PMIP network, when the network connection to the mobile node is applied to the vertical handover, some problems arise unlike in the MIP network.

First, let's look at FIG. 2 is a diagram illustrating a case where one mobile node handover between two different mobile nodes in a single MAG in a PMIP network during communication. 2 is for a case where one mobile node 11 moves from MAG 1 21 to MAG 2 22 while communicating with another mobile node 12.

The LMA 30 is connected to the MAG 1 21 and the MAG 2 22 through a tunnel and the mobile node 11 is connected to the MAG 2 22).

When the mobile node 11 performs handover from the MAG 1 21 to the MAG 2 22, the handover of the mobile node 11 is performed through the process described with reference to FIG. 1, Information (i.e., binding information) is registered in the LMA 30 through the PBU of the MAG 2 22. However, the routing information of the mobile node 11 registered in the MAG 1 (21) remains unchanged.

Therefore, the communication request to the mobile node 11 generated in the mobile node 12 is not transmitted to the mobile node 11 by the routing information (routing table, rule, etc.) still remaining in the MAG 1 21, A problem arises.

Next, consider FIG. 3. FIG. 3 is a diagram illustrating a state after one mobile node handover to another network in FIG.

The MAG 1 21 does not know the handover of the mobile node 11 even after the mobile node 11 performs the handover to the MAG 2 22, There is a problem that the RA is continuously transmitted. Unlike the multicast RA message transmitted in ff02 :: 1 here, the unicast RA message continuously transmits a unicast RA message to each UE.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a method for smooth vertical and horizontal handover in a network-based local mobility management and a user terminal (i.e., mobile node) therefor.

According to an aspect of the present invention, there is provided a method for supporting handover in a mobile node in which at least two or more network interface devices are installed in a PMIP domain in which a plurality of heterogeneous networks are mixed. A method for supporting handover in a mobile node includes the steps of: (a) detecting a network connection trigger from a first device to a first MAG; (b) detecting a first status value for identifying a network to which the first device is connected (B) determining a handover type by comparing the first state value and a previously stored previous state value, (d) transmitting a PBU (Proxy Binding Update) request message according to the handover type to the first MAG and receiving a PBA message; (e) putting the first device into a set state and bringing the remaining devices into an unset state; (f) And transmitting a first message for deleting the remaining routing information to the mobile node.

If the handover type is a vertical handover, the first message further includes an instruction identifier for sending an RA message with a lifetime of 0 from the second MAG. Accordingly, And receiving an RA message with a lifetime of 0 from the second MAG. At this time, the first message is transmitted to the second MAG through a second device connected to the second MAG.

The step (g) receives the RA message through the second device, and the second device removes the uplink default routing for the second MAG.

In step (b), ifindex included in the trigger message received in the network connection trigger is set as the status value, and ifindex is different for each device outputting the trigger message, I will. The method of claim 1, wherein the step (b) comprises the steps of: determining whether the first device is connected to the first device by using identification information of the first device or identification information of the connected network, .

Here, if the RA message having a lifetime of 0 is not received during the set time after the step (f), the method transmits the first message requesting the RA message with a lifetime of 0 to the PCoA Proxy CoA) addressed to the first device through the first device (h).

The step (f) is performed when an RA message is received by the unset device after confirming whether or not the RA message is received by the unset device.

According to another aspect of the present invention, there is provided a multi-mode mobile node for vertical and horizontal handover in a PMIP domain in which a plurality of heterogeneous networks are mixed. The mobile node recognizes at least two or more different network connection devices and whether it is a horizontal handover by a first device or a vertical handover by a new second device when a network connection trigger occurs, A network-based handover process is performed by communication with the PMIP domain, and routing information for the first device recorded in the previous MAG is transmitted through communication with a previous MAG of a previously connected network And a handover manager for causing the handover manager to delete the handover manager.

The handover manager receives a network connection trigger message from one of the devices, determines a first state value for the current access network, compares the first state value with a previously stored previous state value, and determines a handover type And a PBA for a response signal to the PBU, the method comprising the steps of: generating a message requesting a PBU according to a handover type determined by the type determination unit; And outputs the first message to delete the routing information to the mobile node remaining in the MAG of the network to which the previously connected device is connected.

The mobile node of the present invention transmits the first message requesting an RA message with a lifetime of 0 to the PCoA of the second MAG remaining in the binding information of the LMA when the lifetime of the RA message is not received during the set time And a message retransmitting unit for retransmitting, through the set device, a Proxy CoA address.

Wherein the unsetting control unit further includes an instruction identifier for transmitting an RA message having a lifetime of 0 from the second MAG to the first message if the handover type is a vertical handover, From the MAG of the network, an RA message with a lifetime of 0 at the device connected to the previous network.

The type determination unit sets the ifindex included in the trigger message received in the network connection trigger as a status value, and the ifindex enables identification of a network that is different for each device outputting the trigger message and for each device . Or the type determination unit sets the status value for identifying the network connected to the first device by using the identification information of the first device or the identification information of the connected network included in the trigger message received at the network connection trigger do.

According to the above-described embodiment, a multi-mode mobile node having a plurality of devices in the PMIPv6 domain merely adds a handover manager daemon to the user space of the mobile node, .

In addition, the present invention deletes unnecessary routing information for a mobile node remaining in a previous MAG by handover, thereby preventing an RA message from being transmitted from a previous MAG, thereby preventing an increase in load on the MAG.

In addition, the present invention causes the lifetime to be 0 in the previous MAG to the unset device in the vertical handover, so that the uplink default routing information remaining in the unset device is deleted.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the present invention. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification.

Throughout the specification, when an element is referred to as "comprising ", it means that it can include other elements as well, without excluding other elements unless specifically stated otherwise. Also, the terms " part, "" module," and " module ", etc. in the specification mean a unit for processing at least one function or operation and may be implemented by hardware or software or a combination of hardware and software have.

In this specification, a mobile node MT includes a terminal, a mobile node, a subscriber station (SS), a portable subscriber station (PSS), a user equipment (UE) , An access terminal (AT), and the like, and may include all or some of functions of a mobile terminal, a subscriber station, a mobile subscriber station, a user apparatus, and the like.

A mobile node supporting vertical handover between a plurality of network interfaces in a terminal and a vertical handover method thereof in a PMIP network according to an embodiment of the present invention will now be described with reference to the accompanying drawings.

First, a communication environment, that is, a handover type to which the present invention is applied will be described with reference to FIG. 4 is a diagram illustrating a handover situation according to an embodiment of the present invention.

The network shown in FIG. 4 is a PMIPv6 domain in which a plurality of heterogeneous networks are mixed. The PMIPv6 domain refers to a network that manages the movement of a mobile node using PMIPv6.

The MAGs 21 and 22 in the domain are responsible for monitoring the movement of the mobile node 100 on the access link and transmitting the movement related signaling messages of the mobile node 100 in the LMA 30 instead of the mobile node 100 . The LMA 30 serves as a home agent (HA) for the mobile node 100 in the PMIPv6 domain. The LMA 30 is an anchor point on the topology of the home network prefix allocated to the mobile node 100 and is responsible for managing the reachability state of the mobile node 100 in the domain .

In general, the function of the MAG can be implemented in the access router, and the LMA can be located in the gateway of the domain. Between the MAG and the LMA, there is an IP tunnel for transmitting a signaling message and a data packet to be transmitted / received from the mobile node 100.

The handover situation to which the present invention is applied in the PMIP domain is for horizontal and vertical handovers of the multimode mobile node 100 equipped with different devices (e.g., 802.11, 802.21, 802.16e, 3GPP, etc.).

Specifically, the handover situation to which the present invention is applied is for a horizontal handover in which the multimode mobile node moves from the MAG 1 (21) to the MAG 2 (22) via the same device. At this time, MAG 1 (21) and MAG 2 (22) are MAG of the same network.

In addition, the handover situation to which the present invention is applied is that, after the multimode mobile node has connected to the MAG 1 (21) through one device, the mobile node (20) is connected to the MAG 2 (22) It is about. At this time, MAG 1 (21) and MAG 2 (22) are MAGs of different networks.

Here, there are two kinds of vertical handovers to which the present invention is applied. One is the case where the MAG 1 21 and the MAG 2 22 are located in different areas and the first vertical hand 22 when the mobile node 100 enters the area occupied by the MAG 2 22 by the movement, It is over. The other is the case where the MAG 1 21 and the MAG 2 22 are located in the same area and the mobile node 100 is located at the MAG 2 22 in the MAG 1 21, In the second vertical handover. In the case of performing the second vertical handover automatically, it is performed when a communication through the currently connected MAG 1 (21) causes an error or a communication quality deteriorates.

Meanwhile, since the mobile node 100 has a plurality of devices in the mobile node 100, it is possible to perform device control that sets the devices connected to the handover network and disables other devices (unset, idle) And it is necessary to control the operation of deleting the routing information remaining in the PMIP domain, that is, the MAG.

For this reason, the mobile node 100 in the PMIP domain has a separate device for device control and operation control, which will be described with reference to FIG.

5 is a block diagram of a mobile node according to an embodiment of the present invention.

5, a host according to an embodiment of the present invention includes three devices, for example, Dev 0 110, Dev 1 120, Dev 2 130, And a handover manager 140.

Each of the devices Dev 0 110, Dev 1 120 and Dev 2 130 is a network interface for connecting the mobile node 100 to the MAG of the corresponding network. For example, when Dev 0 110 is a network interface for a WiMAX network, Dev 0 110 only connects to a MAG of a WiMAX network. If Dev 1 120 is a network interface for a wireless LAN, The Dev 2 130 only connects to the MAG of the WCDMA if the Dev 2 130 is a network interface for WCDMA.

Each of the devices 110, 120, and 130 is assigned a different LLA (Link Local Address) of IPv6, and the LLA of each of the devices 110, 120, and 130 serves as a device identifier for distinguishing the corresponding device. The LLA of each device is used as network connection trigger information. That is, the LLA enables the handover manager to identify which device the network connection trigger has occurred.

Dev 1 110 is a network interface connected to MAG 0 (not shown), Dev 1 120 is a network interface connected to MAG 1 21 and Dev 2 130 is connected to MAG 2 Network interface.

The handover manager 140 determines the network connection type (including vertical and horizontal handover) performed by each of the devices 110, 120, and 130, performs network mobility based on the PMIP, And performs control and routing information management operations.

The handover manager 140 includes a type determination unit 141, a message generation unit 142, an unset adjustment unit 143, and a message retransmission unit 144.

The type determination unit 141 determines the network connection type. The network connection type is a new attachment in which the mobile node 100 newly connects to the network by power-on or the like, a horizontal handover in which the mobile node 100 handover to the MAG of the same network (i.e., Handover), and vertical handover (handover between devices) in which the mobile node 100 handover to the MAG of the new network. Here, since the new connection is normal as described above with reference to FIG. 1, the type determination unit 141 does not perform any other operation. For this reason, the type of network connection determined by the type determination unit 141 is in line with the handover type.

As an example of a method of determining the network connection type, the type determination unit 141 compares the previous network connection state value with the current network connection state value to determine the network connection type. The type determination unit 141 has a status value of 0 if the mobile node 100 is not connected to the network and a status value of positive numbers (1, 2, 3) if the mobile node 100 is connected to the network. At this time, the state value of the positive number is different according to the type of the network to which the mobile node 100 is connected (that is, the type of the currently set device). For example, the state value is 1 when the mobile node 100 is connected to WiMAX, 2 when it is a wireless LAN, and 3 when it is WCDMA.

Therefore, when the mobile node 100 connects to a new network (i.e., MAG), the type determination unit 141 determines the state value change according to the following three cases, .

1) Case 1: Status value change (0 -> positive number) In this case, when the mobile node 100 is connected to any network without accessing the network, the network connection type is a new connection.

2) Case 2: The state value change (positive -> same positive number) In this case, since the mobile node 100 handover to the MAG of the new network, there is no change in the state value, The handover is a horizontal handover.

3) Case 3: Change of state value (positive - > other positive number) In this case, since the mobile node 100 handover to the MAG of the new network and there is a change in the state value, It is a vertical handover that is a handover.

Here, as an example of a method for the type determination unit 141 to grasp the status value, the type determination unit 141 can grasp the trigger message that is normally output from the device upon network connection. The trigger message contains different ifindex for each device type.

Therefore, the type determination unit 141 can identify the type of the network to which the mobile node 100 is connected by looking at the ifindex. Here, the type determination unit 141 may set the status value to ifindex when Ifindex itself represents a positive value, and may set the status value to a separate positive value according to ifindex.

In addition to using the ifindex, the type determination unit 141 can generate the status value using the separate device identification information included in the trigger message. For example, each of the devices 110, 120, and 130 is given a link local address (LLA). When the LLA is included in the trigger message, the LLA can be used as device identification information such as ifindex. Of course, it is possible to allow the type determination unit 141 to recognize the device connected to the network by including the device identification information in addition to the LLA in the trigger message.

Those skilled in the art will also be able to cause the device to output a separate network connection message instead of a trigger message. However, this method will act as an unnecessary message that overlaps with the trigger message if the trigger message is present.

The message generation unit 142 generates a handover message informing the network connection type under the control of the type determination unit 141. [ Specifically, the handover message generated by the message generating unit 142 includes information indicating the LLA of the current device, the LLA of the past device, the message type, and the network connection type. Here, the LLA of the current device is the LLA of the device connected to the network to be handed over, and the LLA of the previous device is the LLA of the device connected to the previous network.

Therefore, an example of the handover message generated by the message generating unit 142 according to the network connection type is as follows.

1) The new attachment is the same as the procedure described in FIG. 1, so that no separate handover message is required. However, if the mobile node 100 is connected to the MAG 1 (21), the handover message of the mobile node is a Dev 1 Link Local Address (LLA of the current device), a Dev 1 Link Local Address ), access_tech (message type), and attach_new (network connection type).

2) If the handover message according to the vertical handover is handover from the MAG 1 (21) to the MAG 2 (22), the Dev 2 Link Local Address (LLA of the current device), Dev 1 Link Local Address (LLA of the past device), access_tech (message type), handover_between_interfaces (network connection type).

3) If the handover message according to the horizontal handover is handover from the MAG 1 (21) to the MAG 3, the mobile node 100 transmits a Dev 1 Link Local Address (LLA of the current device) and a Dev 1 Link Local Address (LLA of the past device), access_tech (message type), and handover_same interface (network connection type).

The handover message generated by the message generator 142 is transmitted to the current MAG through the current device.

The offsets adjusting unit 143 receives the PBA (Proxy Binding Acknowledge) corresponding to the PBU (Proxy Binding Update) from the currently connected MAG and transmits a message to the current device connected to the MAG that has received the PBA according to the PBA, And unset all the remaining devices including the old device.

Then, the unsetting control unit 143 stops the transmission of the RA message to the MAG, which has been connected to the previous device, in order to remove the remaining routing information from the old device in the MAG connected to the previous device among the unset devices It sends a routing management message requesting deletion of the routing information and requesting an RA message with a lifetime of 0 in order to delete the uplink default routing information to the previous device.

On the other hand, if the vertical handover is performed, the link quality of the previous device may be deteriorated. Therefore, the routing management message transmitted through the previous device by the unset adjusting unit 143 may not be properly transmitted to the MAG. In consideration of this point, the message retransmission unit 144 is required. The message retransmission unit 144 transmits the routing management message once again to the PCAA remaining in the binding information of the LMA 30, with the address of the MAG of the previous network. At this time, the routing management message to be retransmitted is directly transmitted from the message retransmission unit 144 without going through the previous device.

Hereinafter, a state change detection (i.e., handover detection) operation in a mobile node according to an embodiment of the present invention will be described with reference to FIG. 6 is a flowchart illustrating a method of detecting a handover in a mobile node according to an embodiment of the present invention.

The Dev 2 130 generates a network connection trigger message in accordance with the connection to the MAG 2 22 in step S601 and the type determination unit 141 of the handoff manager 140 checks ifindex included in the trigger message The current state value is confirmed (S602).

Then, the type determination unit 141 compares the current state value Sn with the pre-stored previous state value So (S603).

If the previous state value So is 0 and the current state value Sn is positive (S604), the current state value Sn and the previous state value So obtained through the comparison step S603 are changed, The mobile station 141 determines that it is an initial network connection as in the first case of handover (S605).

If the previous state value So is not 0, the type determination unit 141 determines whether the previous state value So and the current state value Sn are the same (S606) If the value Sn is the same, the handover is judged to be a horizontal handover as in the second case (S607). If the previous state value So differs from the current state value Sn, (S608).

Then, the type determination unit 141 controls the message generation unit 142 to generate a message corresponding to the determined network connection type when determining the network connection type through the process (one of S605, S607, and S608) The message generator 142 generates a handover message corresponding to the handover and transmits a handover message generated by the MAG2 22 to the second DEV 130 in step S609.

Hereinafter, the operation of the MAG (i.e., MAG 2) that has received the message transmitted from the handover manager with respect to the handover will be described with reference to FIG. 7 is a flowchart illustrating a handover processing method performed in a new MAG according to an embodiment of the present invention.

Upon receipt of the handover message through the second device 130 (S701), the MAG2 22 determines the handover type of the mobile node 100 by determining the network connection type included in the handover message (S702) .

If the handover type is a new network connection, the MAG 2 22 performs the same operation as that shown in FIG. 1 together with the LMA 30.

If the handover type is a horizontal handover or a vertical handover, the MAG 2 22 transmits a PBU message to the LMA 30 (703), and accordingly transmits a PBA message including a Network Access Identifier (NAI) from the LMA 30 (S704).

Upon receiving the PBA message, the MAG 2 22 forwards the handover registration notification message including the NAI to the handover manager 140 of the mobile node 100 (S705).

Here, the NAI is used when the user authentication is used as a unique identifier given to the mobile node 100, the binding endree of the corresponding mobile node stored in the LMA 30 is found or the binding information of the corresponding mobile node stored in the MAG is found .

Hereinafter, the operation of the mobile node receiving the handover registration notification message will be described with reference to FIG. 8 is a flowchart illustrating a vertical handover processing method performed between a mobile node and a previous MAG after binding up for handover in an LMA according to an embodiment of the present invention.

8, when the handoff manager 140 receives a handover registration notification message from the MAG 2 22, the binding information is transmitted to the LMA 30 It is determined that the registration is completed and the Dev 2 130 being connected to the current network is set and the remaining devices including the previous device Dev 1 120 are unset so that they do not operate in operation S802.

Then, the unsetup controller 140 notifies the Dev 1 120 of the previous device that the MAG 1 (21) does not continuously transmit the RA message and the uplink default routing existing in the Dev 1 (120) And transmits a routing management message including the NAI of the node 100 to the MAG 1 21 via the Dev 1 120 (S803).

In this case, the step S803 may be performed immediately after the completion of the step S802. However, if the RA message is received by the unset device after confirming that the RA message is received to each device after the step S802, Can be performed. Of course, if the RA message is not received by the unset device, the unsetting control unit 143 does not perform the process of step S803. Generally, when vertical handover or horizontal handover occurs, routing information for the previous device remains in the previous MAG, so that an unnecessary RA message is received at the mobile node 100 and there is an uplink default routing of the device connected to the previous MAG So that the message transfer flow to the current device will not be completed.

Upon receipt of the routing management message (S804), the MAG 1 (21) retrieves the routing information (e.g., routing table, rules, etc.) of the Dev 1 120 corresponding to the NAI included in the routing management message among the stored routing information (S805).

Then, the MAG 1 (21) sends out an RA message with a lifetime of 0 to the Dev 1 (120) (S806), and stops sending the RA message to the Dev 1 (120) (S807) .

In RA messages with a lifetime of 0, the receiving device no longer has uplink default routing. Here, an RA message with a lifetime of 0 is required because even if the device is in an unset state, when the corresponding device receives the RA message, it always takes the default route to the device that transmitted the RA message. This is also the reason why multiple devices at the intersection of heterogeneous networks have default routing at the same time.

On the other hand, in the case of the horizontal handover, the unsetting control unit 143 maintains the current device state when receiving the handover registration notification message. Then, in order to prevent the RA message from being continuously transmitted according to the remaining routing information in the previously connected MAG 1 (21), the unsetup control unit 143 transmits a routing management message including the NAI of the mobile node 100 Dev 2 (130) to the MAG 1 (21).

In the case of the horizontal handover, the MAG 1 (21) deletes only the routing information according to the routing management message, but does not transmit the RA message with the lifetime of 0 to the mobile node 100 as in the case of the vertical handover.

On the other hand, in the case of the vertical handover, the routing management message of the handover manager 140 is sent, but the RA message can be continuously transmitted from the previous MAG 1 (21). This is the case where the link management message is not reached to MAG 1 (21) because the link quality is low.

In this case, when the handover manager 140 determines that the RA message with a lifetime of 0 is not received for a certain period of time after the transmission of the routing management message and the RA message is received by the corresponding unset device, And transmits the routing management message to the MAG 1 (21) via the current device, i.e., Dev 2 (130).

At this time, the address information for MAG 1 (21) is identified through the previous PCoA (Proxy Care of Address) included in the LLL option (option) of PBA, and this PCoA is used as the address information of MAG 1 Retransmit the routing management message.

The embodiments of the present invention described above are not only implemented by the apparatus and method but may be implemented through a program for realizing the function corresponding to the configuration of the embodiment of the present invention or a recording medium on which the program is recorded, The embodiments can be easily implemented by those skilled in the art from the description of the embodiments described above.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, It belongs to the scope of right.

1 is a signal flow diagram illustrating a network access control process of a mobile node connected to a new network in a general PMIP network.

2 is a diagram illustrating a case where one mobile node handover between two different mobile nodes in a single MAG in a PMIP network during communication.

FIG. 3 is a diagram illustrating a state after one mobile node handover to another network in FIG.

4 is a diagram illustrating a handover situation according to an embodiment of the present invention.

5 is a block diagram of a mobile node according to an embodiment of the present invention.

6 is a flowchart illustrating a method of detecting a handover in a mobile node according to an embodiment of the present invention.

7 is a flowchart illustrating a handover processing method performed in a new MAG according to an embodiment of the present invention.

8 is a flowchart illustrating a vertical handover processing method performed between a mobile node and a previous MAG after binding up for handover in an LMA according to an embodiment of the present invention.

Claims (14)

A method for supporting handover in a mobile node in which at least two or more network interface devices are mounted in a PMIP domain in which a plurality of heterogeneous networks are mixed, (a) detecting a network connection trigger from the first device to a first MAG, (b) setting a first status value that identifies the network to which the first device is connected, (c) comparing the first state value with a previously stored previous state value to determine a handover type, (d) transmitting a Proxy Binding Update (PBU) request message according to the handover type to the first MAG and receiving a PBA message, (e) putting the first device into a set state and bringing the remaining devices into an unset state, (f) sending a first message to delete routing information to the mobile node remaining in the second MAG that was previously connected. A method of supporting handover to a multimode mobile node in a PMIP domain. The method according to claim 1, If the handover type is vertical handover, Wherein the first message further includes an instruction identifier for transmitting an RA message having a lifetime of 0 from the second MAG, And (g) receiving an RA message with a lifetime of 0 from the second MAG. 3. The method of claim 2, Wherein the first message is transmitted to the second MAG through a second device connected to the second MAG. The method of claim 3, Wherein the step (g) comprises receiving the RA message through the second device, wherein the second device is maintained in an unset state, and the handover to the multimode mobile node in the PMIP domain is supported. 3. The method according to claim 1 or 2, In step (b), ifindex included in the trigger message received in the network connection trigger is set as the status value, and ifindex is different for each device outputting the trigger message, A method for supporting handover to a multimode mobile node in a PMIP domain. 3. The method according to claim 1 or 2, Wherein the step (b) includes the step of: determining the state value for identifying the network connected to the first device by using the identification information of the first device or the identification information of the connected network included in the trigger message received at the network connection trigger A method for supporting handover to a multimode mobile node in a PMIP domain to be established. 3. The method of claim 2, (h) if the handover type is a vertical handover, if the RA message with a lifetime of 0 after the step (f) is not received during the set time, the first message requesting an RA message with a lifetime of 0 Further comprising the step of retransmitting the first MAC address to the first device using the Proxy CoA (PCoA) of the second MAG as an address. 3. The method according to claim 1 or 2, Wherein the step (f) comprises checking whether an RA message is received from the unset device, and if the RA message is received from the unset device, a handover support method for a multimode mobile node in a PMIP domain. In a multi-mode mobile node for vertical and horizontal handover in a PMIP domain in which a plurality of heterogeneous networks are mixed, At least two or more different network connection devices, When a network connection trigger occurs, it is determined whether the first handover is performed by the first device or the second handover is handled by the second device, and only devices of the currently connected network are set according to the grasp, And a handover manager for causing routing information for the first device recorded in the previous MAG to be deleted by communication with a previous MAG of a previously connected network, Mobile node. 10. The method of claim 9, The handover manager comprises: A type determination unit for determining a handover type by receiving a network connection trigger message from one of the devices and determining a first status value for a current access network and comparing the first status value with a previously stored previous status value, A message generation unit for generating a message for requesting a PBU according to the handover type determined by the type determination unit; Upon receiving the PBA, which is a response signal to the PBU, only the devices corresponding to the currently connected network are set up according to the handover type, the remaining devices are set up, and the remaining devices are connected to the mobile node And outputting a first message for deleting the routing information. 11. The method of claim 10, The unset- If the handover type is a vertical handover, transmitting an RA message having a lifetime of 0 from the MAG of the network that was previously connected to the first message, Accordingly, a mobile node that has received a RA message with a lifetime of 0 from the MAG of the network to which it has previously connected is receiving from a device connected to the network to which it has previously connected. 12. The method of claim 11, If the RA message with the lifetime of 0 is not received for the set time, the first message requesting the RA message with a lifetime of 0 is transmitted to the PCOA of the MAG of the previously connected network remaining in the binding information of the LMA And a message retransmitting unit for retransmitting the message through the set device. 11. The method of claim 10, Wherein the type determining unit sets an ifindex included in a trigger message received at the network connection trigger as a status value, wherein the ifindex is different for each device outputting the trigger message and identifies a network to be accessed for each device Mobile node. 11. The method of claim 10, Wherein the type determination unit determines the first status value for identifying the network connected to the first device by using the identification information of the first device or the identification information of the connected network included in the trigger message received at the network connection trigger The mobile node to set.

Images