Abstract:
Disclosed is a packet routing method in mobile IPv6 supporting localized mobility management. A method for routing packets between a mobile node and a destination node in a network system including the mobile node, the destination node, a home agent transferring the packets to a current location of the mobile node, and a localized mobility agent performing localized mobility management of the mobile node, includes steps of deciding whether or not to perform a handoff as the mobile node moves, transferring to the destination node a binding update including a regional care of address (RCoA) of an arbitrary address configured by receiving a prefix of a network in which a localized mobility agent (LMA) existing in an area in which the mobile node moves is located, and transferring packets to the localized mobility agent (LMA) through the RCoA by the destination node. Accordingly, the packet routings are optimized in mobile IPv6 supporting localized mobility management having a short handoff time, and a low binding update and tunneling cost.

Description:
BACKGROUND OF THE INVENTION  
         [0001]    1. Field of the Invention  
           [0002]    The present invention relates to a packet routing method, and more particularly to an optimized packet routing method in mobile IPv6 supporting localized mobility management, which has a short handoff time and a low binding update and tunneling cost. The present invention is based on Korean Patent Application No. 2002-48534, which is incorporated herein by reference.  
           [0003]    2. Description of the Prior Art  
           [0004]    Recently, with the performance enhancements of mobile terminals such as portable computers or PDAs and the developments of wireless communications technologies, the majority of internet users hopes to use high-quality internet services even in wireless environments.  
           [0005]    If all the mobile terminals occupy specific identifiers called ‘IP address’, users overloading their services that have been independently served at a link hierarchy as well as global roaming problems can be naturally solved. Therefore, the Internet Engineering Task Force (IETF) mobile IP working group is working on the standardization of appropriate protocols for mobile IP development and improvements thereof. Further, other standardization organizations are also planning to introduce the mobile IP to cellular systems such as UMTS, CDMA2000, GPRS, and so on.  
           [0006]    In the meantime, as the number of wireless internet users increases, the existing internet protocol version 4 (IPv4) address system can not meet the required amount of increasing IP addresses. Therefore, research is actively ongoing for providing mobility by using the internet protocol version 6 (IPv6) as a next generation internet protocol.  
           [0007]    The mobile IPv6 (hereinafter, referred to as MIPv6) technology of the IETF has been recognized as a standard technology for a method supporting the mobility at the time the internet IP protocol will be transferred to the IPv6 in the future.  
           [0008]    The MIPv6 is described with reference to FIG. 1A and FIG. 1B.  
           [0009]    [0009]FIG. 1A is a view for showing paths for sending a binding update to a home agent HA and a correspondent node CN when a mobile node MN moves in the MIPv6, and FIG. 1B is a view for showing paths for a mobile node MN to receive a packet from a correspondent node CN in the MIPv6.  
           [0010]    First, the following are the definitions of the constituents and terms of the MIPv6.  
           [0011]    Mobile node (MN) is a node changing its network connection position.  
           [0012]    Correspondent Node (CN) is a different node communicating with a mobile node (MN).  
           [0013]    Home Network refers to a network communicated with a home address HoA before a mobile node (MN) moves.  
           [0014]    Home Address (HoA) is an address configured through a home prefix before a mobile node (MN) moves to a different subnet.  
           [0015]    Home Agent (HA) is a router, out of routers in a home network, having information on mobile node (MN) registrations and for transferring a packet to a current position of a mobile node (MN) when the mobile node (MN) leaves a home network.  
           [0016]    Care of Address (CoA) is a temporary address configured through a network prefix in which a mobile node (MN) is located at present as an address obtained in an address auto-configuration manner of the IPv6 when the mobile node (MN) moves to an external network.  
           [0017]    Binding is used to relate a temporarily configured care-of-address (CoA) to a home address (HoA) of original address as information for a registration to a home address (HoA) when a mobile node (MN) moves to an external network.  
           [0018]    In the MIPv6, when a mobile node (MN) moves from a subnet  1  marked in a dotted line in FIG. 1A to a subnet  2  marked in a solid line in FIG. 1A, the mobile node (MN) sends a binding update (referred to ‘BU’, hereinafter) informing a home agent (HA) of its location.  
           [0019]    When updating the binding, the mobile node (MN) registers the prefix information of the subnet  2  in which it is located and a temporary address CoA 2  configured through an IP address.  
           [0020]    Thereafter, as shown in FIG. 1B, only a packet transferred at first is routed via the home agent (HA) from a correspondent node (CN) (path {circle over (1)} of FIG. 1B), and most packets are transferred directly via an optimized path from the correspondent node (CN) to the mobile node (MN) (path {circle over (2)} of FIG. 1B).  
           [0021]    As described above, the MIPv6 efficiently manages the macro mobility of mobile nodes (MNs), but does not efficiently manage the micro mobility of the same. As a method for overcoming such a drawback and complementing and enhancing the MIPv6, the localized mobility management in IPv6 (referred to as LMMv6, hereinafter) has been proposed by the IETF. The localized mobility management is a mobility management method in which routing information bound to a correspondent node (CN) and a home agent (HA) does not change when a mobile node (MN) moves to a different network within a locally limited interior.  
           [0022]    [0022]FIG. 2A is a view for showing paths for sending a binding update to a home agent (HA) and a corresponding node when a mobile node (MN) moves in the LMMv6, and FIG. 2B is a view for showing paths for a mobile node (MN) to receive packets from a correspondent node (CN) in the LMMv6.  
           [0023]    First, the definitions of the constituents and terms of the LMMv6 are as follows.  
           [0024]    Localized Mobility Agent (LMA) is used like a home agent in a network to which a mobile node (MN) moves, and is an agent for performing the localized mobility management of a mobile node (MN).  
           [0025]    Localized Mobility Domain is a group of plural networks in which the localized mobility management is performed, wherein one or more localized mobility agents (LMAs) must exist in a corresponding domain and the mobility of a mobile node (MN) must be hidden against foreign home agents (HAs) and correspondent nodes (CNs).  
           [0026]    Regional CoA (RCoA) is a temporary address configured by a mobile node (MN) receiving a prefix of a network in which a localized mobility agent (LMA) is located as soon as the mobile node (MN) arrives at the network to which the MOBILE NODE (MN) moves. An RCoA the mobile node (MN) receives when entering a corresponding domain does not change during moving inside the domain, and the RCoA is included in binding information to be sent to foreign home agents (HAs) and correspondent nodes (CNs).  
           [0027]    On-line Local CoA (LCoA) has the same meaning as the CoA described in the MIPv6, and is referred to as LCoA in order to distinguish it from the RCoA.  
           [0028]    As shown in FIG. 2A, in the LMMv6, a mobile node (MN) does not have to send a binding update informing a home agent (HA) of its location when the mobile node (MN) moves to a new location in the same domain(a→b→c). Simply, the mobile node (MN) updates the binding only to the localized mobility agent (LMA).  
           [0029]    Therefore, the LMMv6 has an advantage of reducing the binding update cost and the handoff delay time compared to the MIPv6.  
           [0030]    Only a packet transferred at first from a correspondent node (CN) is routed through the localized mobility agent (LMA) via a home agent (HA) (path {circle over (1)} of FIG. 2B), and the binding update including a mobile node (MN) is directly transferred to a correspondent node (CN). Thereafter, most packets are transferred via the localized mobility agent (LMA) from the correspondent node (CN) (path {circle over (2)} of FIG. 2B).  
           [0031]    In the LMMv6, all the packets sent from a correspondent node (CN) are transferred to a mobile node (MN) through a tunneling via the localized mobility agent (LMA). Therefore, data packet transfers are more delayed than the MIPv6, and the localized mobility agent (LMA) is overly loaded.  
           [0032]    Accordingly, both the MIPv6 and the LMMv6 have advantages and disadvantages, so that a new optimized packet routing method is demanded which can overcome such disadvantages.  
         SUMMARY OF THE INVENTION  
         [0033]    In order to solve the above problems, it is an object of the present nvention to provide an optimized packet routing method in mobile IPv6 supporting localized mobility managements which has a short handoff time and low binding update and tunneling costs.  
           [0034]    In order to achieve the above object, an optimized packet routing method in mobile IPv6 supporting localized mobility managements wherein packets are routed between a mobile node and a correspondent node to which the mobile node transfers the packets in a network system including the mobile nodes and a localized mobility agent performing localized mobility managements of the mobile node, comprises steps of (A) sending a binding update including an LCoA to the correspondent node by the mobile node when the correspondent node sends a plurality of packets to the mobile node; (B) decides whether or not a handoff is performed when the mobile node moves; (C) transferring to the correspondent node a binding update including an RCoA of an arbitrary address configured by receiving a prefix of a network in which a localized mobility agent (LMA) existing in an area in which the mobile node moves is located in a case that it is decided that the handoff is performed; and (D) sending the packets to the localized mobility agent through the RCoA by the correspondent node.  
           [0035]    Further, preferably, the mobile node directly receives the packets from the correspondent node during communications with the correspondent node as the mobile node does not move, and the mobile node receives the packets through the localized mobility agent while the mobile node performs the handoff.  
           [0036]    Preferably, in a state that the mobile node communicates with the correspondent node, the mobile node sends to the correspondent node a binding update including an LCoA of an address configured through a prefix of a network in which the mobile node is located.  
           [0037]    Preferably, the mobile node records information on a home agent performing a binding update and the correspondent node to form a binding update list adding optimized (O) flags, and decides and sends one of the LCoA and the RCoA upon transferring a binding update to the correspondent node based on the optimized flags.  
           [0038]    Preferably, when the mobile node receives a first packet from the correspondent node, the mobile node decides whether the transferred packets are tunneled from the localized mobility agent, and manages a reception rate of the tunneled packets.  
           [0039]    Preferably, the mobile node verifies a layer  2  connection state and detects the time when the handoff occurs. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0040]    The above object and other features of the present invention will become more apparent by describing in detail a preferred embodiment thereof with reference to the attached drawings, in which:  
         [0041]    [0041]FIG. 1A is a view for showing paths for a mobile node to send a binding update to a home agent and a correspondent node when the mobile node moves in MIPv6;  
         [0042]    [0042]FIG. 1B is a view for showing paths for a mobile node to receive packets from a correspondent node in MIPv6;  
         [0043]    [0043]FIG. 2A is a view for showing paths for a mobile node to send a binding update to a home agent and a correspondent node when the mobile node moves in LMMv6;  
         [0044]    [0044]FIG. 2B is a view for showing paths for a mobile node to receive packets from a correspondent node in LMMv6;  
         [0045]    [0045]FIG. 3 is a view for showing a binding update list provided to a mobile node according to an embodiment of the present invention;  
         [0046]    [0046]FIG. 4 is a view for showing the movement of a mobile node;  
         [0047]    [0047]FIG. 5 is a graph for showing an SNR in state of FIG. 4;  
         [0048]    [0048]FIG. 6 is a flow chart for showing an operation process when a mobile node receives a first packet from a correspondent node and when the mobile node carries out a handoff according to an embodiment of the present invention;  
         [0049]    [0049]FIG. 7 is a view for showing an operation process for a binding update when a mobile node moves in the same domain;  
         [0050]    [0050]FIG. 8 is a view for showing packet flows after a binding update was carried out in FIG. 7 and a mobile node moved to a different location in the same domain;  
         [0051]    [0051]FIG. 9 is a view for showing an operation process for a binding update when a mobile node moves in different domains; and  
         [0052]    [0052]FIG. 10 is a view for showing packet flows after a binding update was carried out in FIG. 9 and a mobile node moved to a location in a new domain. 
     
    
     DESCRIPTION OF THE PREFERRED EMBODIMENT  
       [0053]    Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.  
         [0054]    [0054]FIG. 3 is a view for showing a binding update list provided to a mobile node (MN) according to an embodiment of the present invention.  
         [0055]    A mobile node (MN) is provided with management functions, tunneling packet reception rate management functions, L2 trigger supports, and L2 state trace functions, which are added for correspondent nodes (CNs) existing in a binding update list.  
         [0056]    The binding update list is to record effective times and so on for binding updates with respect to home agents (HAs) and correspondent nodes (CNs) after a mobile node (MN) sent the binding updates to the home agents (HAs) and the correspondent nodes (CNs) in the existing MIPv6 or the LMMv6.  
         [0057]    Further, a mobile node (MN) adds an extra O flag (Optimized flag) for individual entries of the list, sets a 0 for the O flag if a corresponding correspondent node (CN) is receiving the RCoA, and sets a 1 for the O flag if the same is receiving the LCoA.  
         [0058]    Further, a mobile node (MN) performs the L2 trigger support and L2 state trace technology.  
         [0059]    The L2 trigger is a technology detecting in advance and informing the third layer that a handoff is going to occur in the second layer of the network protocol stack of a mobile node (MN) itself. In the prior wireless LAN technology, a wireless LAN card in a mobile node (MN) keeps measuring a signal-to-noise ratio(SNR) in order to check the quality of a current wireless signal.  
         [0060]    [0060]FIG. 4 shows that a mobile node (MN) is moving from an AP1 area to an AP2 area, and FIG. 5 is a graph for showing SNR variations in the situation of FIG. 4.  
         [0061]    As shown in FIG. 5, as a mobile node (MN) moves closer to the AP2 area, the smaller the SNR values measured from the AP1 become, and the larger the SNR values measured from the AP2 become. At this time, the mobile node (MN) should be provided with one of the following parameters and two kinds of functions.  
         [0062]    a handoff decision interval  
         [0063]    with an SNR1 value measured from an AP1 currently connected, an SNR2 value measured from an arbitrary AP of the APs in adjacent other areas, and handoff decision interval values (HANDOFF_DECISION_INTERVAL) which are threshold values designated beforehand, when the following Formula 1 is satisfied, a binding update including the RCoA is sent to correspondent nodes (CNs) set to a 1 for the O flag in the various entries in the binding update list.  
         [0064]    [Formula 1] 
         SNR1−SNR2&lt;HANDOFF_DECISION_INTERVAL 
         [0065]    Also, with an SNR1 value measured from an AP1 currently connected, an SNR2 value measured from an arbitrary AP of the APs in adjacent other areas, and handoff decision interval values (HANDOFF_DECISION_INTERVAL) which are threshold values designated beforehand, when the following Formula 2 is satisfied, it is recognized as the state of [S:Stable], and, otherwise, as the state of [U:Unstable].  
         [0066]    [Formula 2] 
         |SNR1−SNR2|&gt;HANDOFF_DECISION_INTERVAL 
         [0067]    Further, a mobile node (MN) has a particular parameter TUNNELING_PACKET_COUNT for tunneling packet reception rate managements.  
         [0068]    A mobile node (MN) decides whether packets transferred from an arbitrary correspondent node (CN) is tunneled from the localized mobility agent (LMA), and then decides whether such packets more than the TUNNELING_PACKET_COUNT arrive per second.  
         [0069]    If the packets arrive, when an L2 state grasped by the L2 state trace technology of a mobile node itself is the [S], the mobile node (MN) sends to a correspondent node (CN) a binding update in which the LCoA is included, and the mobile node (MN) sets to a 1 for the O flag of an entry corresponding to the correspondent node (CN) in a binding update list of the mobile node (MN).  
         [0070]    The following is a description on mobile node operations according to an embodiment of the present invention.  
         [0071]    The mobile node operations can be split as follows.  
         [0072]    (Case 1) when a mobile node (MN) does not communicate with a correspondent node (CN),  
         [0073]    (Case 2) when a mobile node (MN) receives the first packet from a correspondent node (CN),  
         [0074]    (Case 3) when a mobile node (MN) performs a handoff in the same domain, and  
         [0075]    (Case 4) when a mobile node (MN) performs a handoff between different domains.  
         [0076]    First, as in the Case 1, if a mobile node (MN) does not communicate with a correspondent node (CN), the correspondent node (CN) is not registered in the binding update list of the mobile node (MN) in general, and the binding update is performed in the same way as the LMMv6.  
         [0077]    Further, in the Case 2, when a mobile node (MN) receives the first packet from a correspondent node (CN), the following two kinds of cases can occur.  
         [0078]    The first case is the case that a mobile node (MN) receives packets through a home agent (HA) and the localized mobility agent (LMA) from a correspondent node (CN), actually starting up a communication session.  
         [0079]    The second case is the case that a mobile node (MN) moves to a new area so as to completely finish a handoff and the mobile node (MN) receives packets in the newly moved area for the first time.  
         [0080]    [0080]FIG. 6 is a flow chart for showing an operation process when a mobile node (MN) receives a first packet from a correspondent node (CN) and when the mobile node (MN) carries out a handoff according to an embodiment of the present invention.  
         [0081]    As shown in FIG. 6, when a mobile node (MN) receives the first packet from a correspondent node (CN), the mobile node (MN) decides whether packets are transferred through a tunneling from the localized mobility agent (LMA) and counts the packets transferred through the tunneling (S 602 ).  
         [0082]    Further, the mobile node (MN) checks the L2 state (S 604 ). If the L2 state is stable (S 606 ), and the mobile node (MN) verifies whether the number of counted tunneling packets is more than a predetermined number per second (S 608 ). If the number of counted tunneling packets is not more than the predetermined number per second, the mobile node (MN) returns to its initial state again.  
         [0083]    If the number of counted tunneling packets is more than the predetermined number per second, the mobile node (MN) transfers to a correspondent node (CN) a binding update including the LCoA (S 610 ).  
         [0084]    Thereafter, the correspondent node (CN) directly transfers packets to the mobile node (MN) without the need of tunneling by using the LCoA transferred.  
         [0085]    In the meantime, if the mobile node (MN) performs a handoff (S 614 ), the mobile node (MN) performs the L2 trigger supports and the L2 state trace, and transfers a binding update including the RCoA to all correspondent nodes (CNs) set to a 1 for their O flags (S 616 ).  
         [0086]    Further, the mobile node (MN) sets the O flags in the binding update list to a 0 (S 618 ).  
         [0087]    Next, operation flows when a mobile node (MN) performs a handoff in the same domain are described with reference to FIG. 7 and FIG. 8.  
         [0088]    [0088]FIG. 7 shows a binding update operation flow when a mobile node (MN) moves in the same domain.  
         [0089]    A mobile node (MN) performs a handoff when the mobile node (MN) moves from an arbitrary area to a different area in the domain.  
         [0090]    A mobile node (MN) checks a handoff occurrence by performing the L2 trigger supports and the L2 state trace (S 702 ). The mobile node (MN) transfers a binding update including the RCoA obtained in the domain in which the mobile node (MN) is currently located to all correspondent nodes (CNs) set to a 1 for the O flags presented by the present invention, that is, to the correspondent nodes (CNs) transferring packets through the LCoA (S 704 ). Further, the mobile node (MN) sets to a 0 the O flags set to a 1 (S 706 ).  
         [0091]    [0091]FIG. 8 shows a packet flow after the binding update operation is done in FIG. 7 and the mobile node (MN) moves to a different area in the same domain.  
         [0092]    After a binding update operation is done, and, if a mobile node (MN) moves to a different area and connects to a new L2, the mobile node (MN) receives prefix information from a new router (AR 2 ) of the area (S 802 ) and configures a new address of its own (S 804 ).  
         [0093]    Further, the mobile node (MN) transfers a binding update to the localized mobility agent (LMA) which manages a corresponding domain (S 806 ).  
         [0094]    In the meantime, a correspondent node (CN) directly transfers packets through the existing LCoA, but, after receiving a binding update including the RCoA transferred by the L2 trigger supports of the mobile node (MN), the correspondent node (CN) sends packets to the localized mobility agent (LMA) by using the RCoA (S 808 ).  
         [0095]    The localized mobility agent (LMA) which has received a binding update from the mobile node (MN) tunnels packets to a moved area in use of the new LCoA (S 810 ).  
         [0096]    However, even though not shown for the convenience of descriptions, if the localized mobility agent (LMA) does not receive a binding update that a mobile node (MN) sends after completely finishing a handoff, the localized mobility agent (LMA) tunnels packets to a prior location.  
         [0097]    Hereinafter, the operations when a mobile node (MN) performs a handoff between different domains are described with reference to FIG. 9 and FIG. 10.  
         [0098]    [0098]FIG. 9 is a flow chart for showing binding update operations when a mobile node (MN) moves in different domains.  
         [0099]    A mobile node (MN) performs a handoff between different domains when the mobile node (MN) moves from a currently located domain to a different domain.  
         [0100]    The mobile node (MN) carries out the L2 trigger supports and the L2 state trace to check a handoff occurrence (S 902 ). The mobile node (MN) sends a binding update including the RCoA obtained from a domain in which the mobile node (MN) is currently located to all correspondent nodes (CNs) set to a 1 for the O flags presented by the present invention, that is, to the correspondent nodes (CNs) transferring packets through the LCoA (S 904 ). Further, mobile node (MN) sets the O flags to a 0 (S 906 ).  
         [0101]    [0101]FIG. 10 shows a packet flow after a mobile node (MN) performs a binding update operation in FIG. 9 and the mobile node (MN) moves in an area of a new domain.  
         [0102]    If a mobile node (MN) moves in an area of a new domain for a new L2, the mobile node (MN) receives prefix information from a new router AR 3  of the area and the localized mobility agent (LMA 2 ) (S 1002 ) and configures its own RCoA and LCoA addresses (S 1004 ).  
         [0103]    Further, the mobile node (MN) sends a binding update including the RCoA to a home agent (HA) and correspondent nodes (CNs) in the binding update list, and sends a binding update including the LCoA to the localized mobility agent (LMA 2 ) which manages a new domain (S 1006 ).  
         [0104]    A correspondent node (CN) transfers packets to the localized mobility agent (LMA 2 ) in use of the RCoA after having received the binding update including the RCoA transferred by the L2 trigger supports of the mobile node (MN), rather than transferring packets directly through the existing LCoA (S 1008 ).  
         [0105]    In the meantime, even though not shown, if the correspondent node (CN) does not receive a BU sent after having completely finished a handoff with the mobile node (MN), the correspondent node (CN) sends packets to the prior LMA.  
         [0106]    Further, the localized mobility agent (LMA 2 ) that has received packets tunnels the packets to the moved area in use of the new LCoA (S 1010 ).  
         [0107]    As described so far, the optimized packet routing method in mobile IPv6 supporting localized mobility managements according to the present invention enables the following effects:  
         [0108]    Firstly, data packet transfers are nearly similar in a cost aspect to the MIPv6 having the least data packet transfer cost.  
         [0109]    Secondly, a handoff delay is nearly similar in a time aspect to the LMMv6 having a relatively small handoff delay time.  
         [0110]    Thirdly, overloads can be eliminated which occur to localized mobility agents (LMAs) being important factors of a localized mobility management protocol.  
         [0111]    Although the preferred embodiment of the present invention has been described, it will be understood by those skilled in the art that the present invention should not be limited to the described preferred embodiment, but various changes and modifications can be made within the spirit and scope of the present invention as defined by the appended claims.