This application claims priority from Korean Patent Application No. 10-2007-0127874, filed on Dec. 10, 2007, and No. 10-2008-0024909, filed on Mar. 18, 2008, the disclosures of which are incorporated herein in its entirety by reference.
1. Field of the Invention
The present invention relates to an Internet Protocol (IP)-based network, and more particularly, to a technology for supporting mobility of a mobile node (MN).
This work was supported by the IT R&D program of Ministry of Information and Communication (MIC)/Institute for Information Technology Advancement (IITA) [2006-S-058-02, Development of Network/Service Control Technology in All-IP based Converged network].
2. Description of the Related Art
Technologies for supporting mobility of a mobile node (MN) on a general IP-based network include a mobile IP (MIP) defined by the Internet Engineering Task Force (IETF). Such IP-based mobility supporting technologies operate on Layer 3 (L3), so they are called L3 mobility technologies. The L3 mobility technologies operate when processing related to movement of a mobile node on a Layer 2 (L2) is complete, and perform processes of registration to a location manager and message transmission through L3 routing for the registration. During the processes, time delay is generated, the mobile node cannot perform communications for the delayed time, and communications may be even interrupted if the delay time is too long. For this reason, fast mobility processing becomes an important technical element in mobility technologies, and accordingly, new approach and improvement on existing L3 mobility technologies are required.
The present invention provides a method for minimizing delay due to processing of mobility of a mobile node.
According to an aspect of the present invention, there is provided a method of supporting mobility of a mobile node, the method performed by a plurality of agents that connect a plurality of access networks to an Internet protocol core network integrating the plurality of access networks, the method including: acquiring address information of a mobile node connected to an access point from the access point; transmitting the address information of the mobile node and layer 3 address information of an agent to a management unit which is located on the Internet protocol core network and manages the plurality of access networks, and registering a location of the mobile node in the management unit; transmitting the layer 3 address information of the agent to the mobile node, in order to allow the mobile node to transmit a data packet to the agent; and receiving and transmitting the data packet between the mobile node and a correspondent node on the basis of the address information of the mobile node and information registered in the management unit.
According to another aspect of the present invention, there is provided a method of supporting mobility of a node located on an Internet protocol core network and wirelessly connected to an access point, the method performed by a management unit capable of communicating with an agent for each access network, the agent managing the node, the method including: acquiring layer 2 address information and permanent address information of the node, and layer 3 address information of the agent for each access network, from the agent for each access network; mapping and managing the layer 2 address information and the permanent address information of the node and the layer 3 address information of the agent; receiving a request message for requesting layer 3 address information of a receiving party agent which manages a correspondent node, from a transmitting party agent which tries to transmit a data packet to the correspondent node; searching for the layer 3 address information of the receiving party agent from the layer 2 address information and the permanent address information of the node and the layer 3 address information of the agent, in response to the request message; and transmitting the layer 3 address information of the receiving party agent to the transmitting party agent.
According to another aspect of the present invention, there is provided a method of supporting mobility of a mobile node, the method performed by an access point communicating with an agent which connects an access network to an Internet protocol core network, the method including: forming a wireless channel with a mobile node; acquiring layer 2 address information of the mobile node when the wireless channel is formed; and transmitting the layer 2 address information of the mobile node to an agent for registering a location of the mobile node, instead of the mobile node.
According to another aspect of the present invention, there is provided an apparatus of supporting mobility of a mobile node for each access network, the apparatus which connects an access network to an Internet protocol core network integrating the plurality of access networks, the apparatus including: a management unit managing information related to a mobile node connected to an access point, and managing information related to a correspondent node connected to an access point of a different access network; and a reception/transmission processor receiving and transmitting a data packet between the mobile node and the correspondent node using the information managed by the management unit.
According to another aspect of the present invention, there is provided a management apparatus for communicating with an agent for each access network, the management apparatus located on an Internet protocol core network, the agent managing a node wirelessly connected to an access point, the management apparatus including: a central management unit managing permanent address information of a plurality of nodes connected to an access point, and layer 3 address information of an agent for managing the plurality of nodes, and managing communication connections between the plurality of nodes; and transmitting permanent address information of a correspondent node managed by the central management unit, and layer 3 address information of an agent managing the correspondent node, in response to a request of an agent which manages a mobile node trying to communicate with the correspondent node, and transmitting permanent address information of the mobile node managed by the central management unit and layer 3 address information of the agent managing the mobile node, to the correspondent node.
Therefore, a high-speed mobility service for a mobile node is provided in an IP network environment. Accordingly, it is possible to reduce delay due to mobility processing through a L2 trigger function and high-speed mobility signaling through a predetermined control channel. Particularly, it is possible to provide a high-speed mobility supporting service which can quickly perform mobility processing through a L2 trigger when a node moves, allow fast message transmission through a pre-set control channel between HCA and MICS, and omit a process of transmitting information separately to a mobile node or to a correspondent node through tunneling supported by each HCA.
Additional aspects of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the invention, and together with the description serve to explain the aspects of the invention.
The invention is described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure is thorough, and will fully convey the scope of the invention to those skilled in the art. In the drawings, the size and relative sizes of layers and regions may be exaggerated for clarity. Like reference numerals in the drawings denote like elements.
An access point (hereinafter, referred to as an “AP”) 200-1, 200-2 or 200-3, which is a wireless access device, can communicate with a network connection equipment for connecting an access network to an Internet Protocol (IP) core network. In this specification, the network connection equipment, which is a mobility supporting apparatus for supporting mobility of a node, is called a Handover Control Agent (HCA) 300-1, 300-2 or 300-3. An AP (for example, AP#1200-1) extracts a L2 address of a mobile node 100 through a Layer 2 (L2) connection with the mobile node 100, and transmits the L2 address of the mobile node 100 to a HCA (for example, HCA#1300-1) which is in a local area.
The HCA#1300-1 is located in an edge area on the IP core network, and maintains and manages information, such as permanent addresses (PAs), L2 addresses, and local addresses (LAs) of nodes that belong to the corresponding area, and information for interfacing with the AP#1200-1 in which the nodes are located, wherein the PAs means IP addresses not changed when the nodes perform handover to another access network area, and the information is managed in the form of a local node address management table (LNAT). Also, the HCA#1300-1 manages permanent addresses of correspondent nodes with which the nodes located in the access network area to which the HCA#1300-1 belongs want to communicate, L3 addresses of HCAs in which the correspondent nodes are located, and addresses of tunnel interfaces to the HCAs in which the correspondent nodes are located. The address information is managed in the form of a correspondent node address management table (CNAT) illustrated in
Meanwhile, a mobility information control server (MICS) 400 located on the IP core network functions to manage the locations of the nodes, and may be installed in a high-performance server, router or switch. The MICS 400 receives information about L2 addresses and local addresses (LAs) of the nodes and L3 addresses of HCA#1300-1, HCA#2300-2, and HCA#3300-3 in which the nodes are located, from the HCA#1300-1, HCA#2300-2, and HCA#3300-3, and maintains and manages the information. The information is managed in the form of a global location management table (GLMT) illustrated in
There is at least one dynamic control channel or at least one pre-set control channel between the MICS 400 and a HCA (for example, HCA#1300-1). The control channel may be used for traffics to process mobility of the nodes. If a multiprotocol label switching (MPLS) technique is applied to the IP core network, a Label Switched Path (LSP) is established between the MICS 400 and HCA#1300-1 and used as a control channel for receiving and transmitting mobility signaling parameters.
Referring to
The HCA#1300-1 records the L2 address of the mobile node 100 included in the location report message in a LNAT illustrated in
Meanwhile, the HCA#1300-1 transmits the L3 address of the HCA#1300-1 to the mobile node 100 using an address information message, and in some cases, transmits a LA that will be used by the mobile node 100 to the mobile node 100 (operation S250). Here, the LA means a temporary L3 address (for example, an IP address) which the mobile node 100 can use in the access network #1. When the HCA#1300-1 cannot check paths of nodes which have to be managed by the HCA#1300-1 since the number of the nodes are too large, the mobile node 100 generates LAs that are to be used in the access network#1 and allocates the LAs to the nodes, thereby allowing the HCA#1300-1 to easily manage the nodes that are connected thereto. Accordingly, in the case of a network environment requiring such management, a process of allowing a HCA to generate and allocate LAs is needed.
The mobile node 100 receives an address information message, and changes its own default gateway address to a L3 address of the HCA#1300-1 included in the address information message. Accordingly, the mobile node 100 can transmit a data packet using the default gateway address. Also, the mobile node 100 transmits an address information response message to the HCA#1300-1 in response to the address information message. At this time, the mobile node 100 adds PA information of the mobile node 100 to the address information response message, thus informing the HCA#300-1 of the PA of the mobile node 100 (operation S260). The HCA#1300-1 receives the address information response message from the mobile node 100, extracts the PA of the mobile node 100 included in the address information response message, and records the PA of the mobile node 100 in the corresponding record. Then, the HCA#1300-1 informs the MICS 400 of the PA of the mobile node 100 using an address update message (operation S270). The MICS 400 receives the address update message from the HCA#1300-1, extracts the PA of the mobile node 100 included in the address update message, and records the PA of the mobile node 100 in the corresponding record of the GLMT. Through the process, the location and address of the mobile node 100 are registered.
A mobile node 100 sends a data packet, like in a conventional packet network, to communicate with a correspondent node (CN) 500, using a default gateway address which is set through the process described above with reference to
The MICS 400 which receives the location information request message from the HCA#1300-1 searches for a L3 address of the HCA#3300-3 from a GLMT stored in the MICS 400 using the PA information of the correspondent node 500, and transmits a location information response message including the PA information of the correspondent node 500 and the L3 address of the HCA#3300-3 to the HCA#1300-1 (operation S340). Then, the MICS 400 maps the PA of the mobile node 100 to the PA of the correspondent node 50 and stores the result of the mapping in order to record communications between the mobile node 100 and the correspondent node 500. Also, the MICS 400 searches for the L3 address of the HCA#1300-1 using the PA information of the mobile node 100, and transmits a location information transfer message including the PA information of the mobile node 100 and the L3 address of the HCA#1300-1 to the HCA#3300-3 (operation S350).
The HCA#1300-1 and HCA#3300-3 that receive the messages add information about the PAs and the L3 addresses of the other party HCAs included in the received messages, to CNATs stored in the respective HCA#1300-1 and HCA#3300-3. Through this process, information about the PAs of the other parties and the L3 addresses of the other party HCAs required for communications between the mobile node 100 and the correspondent node 500 is registered in the CNAT of the HCA#1300-1 and the CNAT of the HCA#3300-3. Through such registration, additional information spaces are allocated to the configuration tables LNAT, CNAT, GLMT, and CNMT, according to a development environment, thereby performing additional functions.
The HCA#1300-1 which has completed the above process tunnels the data packet which the HCA#1300-1 has buffered, and transmits the tunneled data packet to the HCA#1300-1. When the HCA#1300-1 and the HCA#3300-3 are connected to an IP core network, a destination address of the packet header of the data packet is the HCA#3300-3 in which the correspondent node 500 is located, and a source address of the packet header is the HCA#1300-1 in which the mobile node 100 is located. The HCA#1300-1 performs encapsulation and tunneling on the packet data and transmits the encapsulated and tunneled data packet to the HCA#3300-3 (operation S360). The HCA#3300-3 receives the data packet and performs decapsulation on the data packet (operation S370), then searches for the LNAT to find an interface to which an AP#3200-3 in which the correspondent node 500 is located is connected, and transfers the data packet to the correspondent node 500 through the interface.
Also, when the correspondent node 500 transmits the data packet to the mobile node 100, if the correspondent node 500 sets a destination address of the data packet to a PA of the mobile node 100 and a source address of the packet data to a PA of the correspondent node 100, the HCA#3300-3 encapsulates the packet header of the data packet to a packet header whose destination address is the HCA#1300-1 in which the mobile node 100 is located and whose source address is the HCA#3300-3, and transfers the resultant data packet to the HCA#1300-1 (operation S380). The HCA#1300-1 receives the data packet and performs decapsulation on the data packet (operation S390), then searches for the LNAT to find an interface to which an AP#1200-1 in which the mobile node 100 is located is connected, and transfers the data packet to the mobile node 100 through the interface.
When the moving node 100 moves to a new access network area, as illustrated in
Meanwhile, the MICS 400 updates the L2 address of the mobile node 100, the LA, and the L3 address of the HCA#2300-2, which exist in the GLMT, using the location registration message received from the HCA#2300-2. If a record for the mobile node 100 exists in the CNMT, the mobile node 100 transmits to the HCA#2300-2 a location information transfer message including a list of PAs of all correspondent nodes with which the mobile node 100 can communicate and L3 addresses of HCAs of network areas in which the correspondent nodes are located (operation S430). The HCAs which receive the location information transfer message from the MICS 400 update respective CNATs. Thereafter, the HCA#2300-2 and HCA#3300-3 perform tunneling on the basis of the CNAT information updated when a data packet is transferred (operations S445, S450, S455, and S460).
As illustrated in
The transmission/reception processor 320 receives a data packet that is to be transmitted from the mobile node 100 to the correspondent node 500. Also, the transmission/reception processor 320 searches for the CNAT to find a PA matched to a destination address of the correspondent node 500 included in the data packet. Then, the transmission/reception processor 320 transmits the data packet to the HCA#3300-3 through encapsulation and tunneling, using information about a L3 address of the HCA#2300-2 mapped to the searched PA, and information about a tunnel interface to the HCA#3300-3 in which the correspondent node 500 is located. Also, the transmission/reception processor 320 receives the data packet through the AP#3200-3 and HCA#3300-3 from the correspondent node 500, and performs decapsulation on the data packet. Then, the transmission/reception processor 320 searches for the LNAT to find a PA matched to the destination address of the received data packet. Then, the transmission/reception processor 320 extracts information about an interface to the AP#1200-1 mapped to the searched PA, and transfers the data packet to an AP#1200-1 using the extracted interface information.
As illustrated in
Then, if the mobile node moves to another access network area while the mobile node 100 communicates with an access network area, a HCA#2300-2 of another access network area transmits the L2 address and LA of the mobile node and L3 address information of the HCA#2300-2 to a MICS 400. The central management unit 410 of the MICS 400 receives the L2 address and LA of the mobile node and the L3 address information of the HCA#2300-2, thus updating the GLMT. Then, the information providing unit 420 searches for the CNMT to check the correspondent node communicating with the mobile node, and transmits the PA address of the mobile node and the L3 address information of the HCA#2300-2 to the correspondent node. Also, the information providing unit 420 transmits to the HCA#2300-2 the PA of the correspondent node and the L3 address information of the HCA#3300-3 of the network area in which the correspondent node is located.
It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.
Number | Date | Country | Kind |
---|---|---|---|
10-2007-0127874 | Dec 2007 | KR | national |
10-2008-0024909 | Mar 2008 | KR | national |