KR20090054147A - System, apparatus and method for performing mobile ipv6 handover based on domain name system - Google Patents

Abstract

The present invention relates to a DNS-based mobile IPv6 handover system and method.

The present invention utilizes a Domain Name System (Domain Name System) server using a domain name as a mobility management method of a mobile terminal in order to solve the problems in the conventional IP-based mobility management method. In addition, an embodiment of the present invention is to provide a mobile IPv6 mobility technology through the domain name by changing the address of the mobile terminal consisting of the IP to the Invals domain structure.

The present invention can support the fast update to the domain name system server when the mobile terminal moves frequently, it can be expected to provide an effect of providing a fast handover without causing data loss.

MIPv6, DNS, Domain Name, Invals Domain, Mobility Binding, Mobility Management

Description

System, Apparatus and Method for Performing Mobile IPv6 Handover Based on Domain Name System}

The present invention relates to a mobile IPv6 handover method, and more particularly, to a mobile IPv6 handover system and method based on a domain name system (hereinafter, referred to as 'DNS').

The TCP / IP protocol currently used in the Internet has a disadvantage in that it is difficult to simultaneously support packet routing and handover required in the mobile Internet.

Currently, the Internet uses a receiving node's IP address to send packets to the network to which the receiving node is connected. Therefore, when the mobile station moves from the serving network to another subnetwork, it is required to be assigned an IP address of the subnetwork to receive the packet.

 However, TCP classifies each session into four values: destination IP address, destination port number, source IP address, and source port number. If one value is changed, the session is recognized as changed.

Therefore, if a mobile terminal that maintains a session with a destination node moves to a new network and receives a new IP address and uses it as a receiving address, the session cannot continue because the destination IP address of the TCP changes.

Mobility Management technology is required to provide Internet services to users regardless of their current location, which can be implemented in a link layer, a network layer, and a transport layer.

However, in the wireless environment, since the mobile station may move to another sub network, it is not possible to guarantee continuous connection with the mobile station using the existing IP protocol.

In order to solve this problem, the Internet Engineering Task Force mobile IP working group has proposed a mobile IPv6 (MIPv6) protocol to support mobility of terminals in the IPv6 network layer.

Mobile IPv6 technology works transparently to protocols above the IP layer, and allows for mobility of IPv6 hosts without interruption of active Transmission Control Protocol (TCP) connections and User Datagram Protocol (UDP) port bindings. Technology to provide.

1 is a diagram illustrating a conventional mobile IPv6 handover procedure.

When the mobile terminal 100 moves to a new subnetwork, the mobile terminal 100 performs L2 handover with a new access point (NAP) 30 (S10). Subsequently, the mobile terminal 100 generates a router request message (Router Solicitation) requesting the prefix information of the new access router 32 and transmits it to the new access router 320 (S12), and the new access router 32. Receive a router advertisement message (Router Advertisement) transmitted from (S14).

The mobile terminal 100 may detect the movement by periodically receiving a router advertisement message from the new access router 32 whenever the mobile terminal 100 moves to the new subnetwork.

After receiving the router advertisement message including the prefix information from the new access router 32, the mobile terminal 100 sets a new care of address (hereinafter referred to as 'nCoA') address setting process and checks for address duplication. Address Detection: DAD) is started (S16).

The mobile terminal 100 generates the binding update message to the home agent 400 and transmits the binding update message to the home agent 400 (S18), and receives the binding response message in response to the binding update message from the home agent 400 to bind the binding. Process the update (S20). Subsequently, the home agent 400 performs a buffering process for storing information of the mobile terminal 100. The target node 500 transmits the packet to the mobile terminal 100 via the home agent 400.

In the conventional mobile IPv6 handover procedure, a handover delay occurs during the address duplication check, and the home node continues to receive a binding update signal to the mobile terminal 100 due to an unoptimized routing problem. There is a problem that should receive a packet through the agent (400).

Such conventional mobility management methods have not completely solved problems such as triangle routing and delay time of mobile IP.

In order to solve such a problem, the present invention is to provide a DNS-based mobile IPv6 handover system and method.

In accordance with an aspect of the present invention, a DNS-based mobile IPv6 handover method includes: (a) an update message from a mobility anchor point receiving a routing message indicating a packet for registration of the mobile station; Receiving a home address for the mobile terminal made of IP and a domain name having a care of address in an inverse domain structure; And (b) search for a resource record indicating a resource of the terminal associated with the home address of the mobile station and update if there is a mobility binding of the mobile station included in the resource record. And if it does not exist, creating a new resource record.

According to an aspect of the present invention, a DNS-based mobile IPv6 handover system receives a home address and a care of address of an IP of a mobile terminal as a domain name formed in an involes domain structure, and the mobile terminal corresponds to the domain name. A plurality of local domain name system servers updating mobility bindings and managing mobility of the mobile terminal using the domain names; And receiving and managing a mobility binding of the mobile terminal from the plurality of local domain name system servers, and receiving an invalence query message requesting an address of the mobile terminal as a domain name from a target node. And a main domain name system server for sending a response message including the address of the mobile terminal to the target node in response.

According to another aspect of the present invention, a DNS-based mobile IPv6 handover system receives a route setting message indicating a packet for registering a mobile station, establishes a route, and updates a mobility binding of the mobile station. A mobility anchor point for generating and transmitting a message including a home address of the mobile terminal composed of IP and a domain name having a care of address formed in an involes domain structure; And a local domain name system server that receives the update message to update the mobility binding of the mobile terminal corresponding to the domain name, and manages the mobility of the mobile terminal using the domain name.

According to the above-described configuration, the present invention can support a quick update to a domain name system server when the mobile terminal frequently moves, and thus can expect an effect of providing a fast handover without causing data loss.

The present invention enables efficient use of wireless / wired network resources by reducing the load on domain name system servers by allowing local mobility to be managed locally.

The present invention solves a triangle routing problem that degrades TCP performance when performing IP-based handover.

 The present invention can be expected to reduce the packet loss caused by performing the IP-based handover and increase the TCP throughput.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when a part is said to "include" a certain component, it means that it can further include other components, without excluding other components unless specifically stated otherwise. In addition, the terms “… unit”, “… unit”, “module”, “block”, etc. described in the specification mean a unit that processes at least one function or operation, which is hardware or software or a combination of hardware and software. It can be implemented as.

An embodiment of the present invention is a mobility management method of a mobile terminal 100 using a domain name system (DNS) server using a domain name in order to solve problems in the conventional IP-based mobility management method. Is to use.

An embodiment of the present invention is to change the address of the mobile terminal 100 made of IP to the Invals domain structure to provide a mobile IPv6 mobility technology through the domain name.

2 is a diagram briefly illustrating a configuration of a DNS-based mobile IPv6 handover system according to an embodiment of the present invention.

The DNS-based mobile IPv6 handover system according to an embodiment of the present invention includes a plurality of access routers 200, mobility anchor points 300, a plurality of local DNS servers 600, and a main DNS server 700. In addition, the mobile terminal 100 transmits a domain name having an IP address of the mobile terminal 100 formed of an involes domain structure, and a target node 500 for transmitting packet data to the mobile terminal 100.

When the mobile terminal 100 moves to a new sub network, the plurality of access routers 200 transmits and receives a router request message and a router advertisement message with the mobile terminal 100 to inform the mobile terminal 100 of the new access router information. The mobile terminal 100 transmits a message for setting a path of packet data received from the mobile terminal 100 and a message for updating the information of the mobile terminal 100 to the mobility anchor point 300.

The mobility anchor point (hereinafter referred to as 'MAP') 300 is an access router that manages a plurality of access routers 200 located in a sub-network, and has information of an access router 200 managed by itself. The packet data received from the target node 500 is analyzed and transmitted to the corresponding mobile terminal 100. In addition, the MAP 300 transmits various information such as a message for updating the information of the mobile terminal 100 received from the mobile terminal 100 to the local DNS server 600.

The plurality of local DNS servers 600 are domains in which the home address and care of address (hereinafter, referred to as 'CoA') of the mobile terminal 100 formed of IPs from the mobile terminal 100 are formed in an involes domain structure. It receives the name, updates the mobility binding of the mobile terminal 100 corresponding to the domain name according to the update signal of the mobile terminal 100, and performs mobile IPv6 mobility management using the domain name.

The main DNS server 700 receives and stores a mobility binding of a DNS resource record representing a terminal resource from a plurality of local DNS servers 600, and stores DNS resources related to the mobile terminal 100 from the plurality of local DNS servers 600. When the record is requested, DNS resource records including the information of the mobile terminal 100 are searched based on the domain name of the mobile terminal 100 and transmitted to the plurality of local DNS servers 600. Here, the mobility binding includes all information related to the mobile terminal 100 such as the home address of the mobile terminal 100, the CoA of the MAP 300, the lifetime, the option, the address of the new access router, the prefix, the gateway, the local address, and the like. do.

The plurality of local DNS servers 600 and the main DNS server 700 described above, when the domain name is converted to an IP address, as opposed to a function of searching for a domain name by layering an Invals domain obtained by converting an IP address into a domain name. Includes the ability to search for addresses.

Next, referring to Figure 3 will be described in detail the DNS-based mobile IPv6 domain name invoicing structure proposed in the embodiment of the present invention.

3 is a view for explaining the DNS-based mobile IPv6 domain name invault structure proposed in the embodiment of the present invention.

In order to apply the embodiment of the present invention, the mobile terminal 100 mostly uses an IP address, and it should be possible to know the current location of the mobile terminal 100 through DNS with only the IP address. This can be solved with the Invals domain. Here, the Invals domain is used to map IP addresses to names.

As shown in FIG. 3, the servers that handle the Invals domain are hierarchical. This means that the netid part of the address must be at a higher level than the subnetid part. Here, the subnetid should be higher than the hostid.

As shown in Figure 3, 128.227.120.42 is read as 42.120.227.128.inaddr.arpa.

The DNS-based mobile IPv6 mobility technology proposes a local mobility management structure to solve a problem of rapid updating due to frequent movement of the mobile terminal 100 or a continuous literal problem of the access router 200.

A local mobility management structure according to an embodiment of the present invention will be described in detail with reference to FIG. 4.

4 is a diagram for explaining a DNS-based mobile IPv6 local mobility management structure according to an embodiment of the present invention.

First, when the mobile terminal 100 moves to a new sub network, the mobile terminal 100 obtains CoA through the new access router.

As shown in FIG. 4, the access router may be hierarchically configured to minimize the load on updating CoA information of the mobile terminal 100 in the DNS resource record.

AR0 becomes the MAP 300 managing one subnetwork.

Second, when the mobile terminal 100 moves to a new sub network, the mobile terminal 100 transmits a packet for registration to the upper layer through the access router 200 in charge of itself.

The packet described above forms one path from the MAP 300 to the access router 200. Such packets are referred to as routing messages for convenience.

The packet arriving at the MAP 300 informs the access router of the layer following the MAP 300 and is destroyed.

The MAP 300 updates the DNS through an update message including its address, a home address of the mobile terminal 100, and a life time.

When the mobile terminal 100 moves on a subnetwork, the mobility binding information of the mobile terminal 100 is stored in the MAP 300 without changing the CoA of the DNS, and the CoA of the DNS is changed only when the mobile terminal 100 moves to a new subnetwork. do.

When the mobile terminal 100 finds a new path by moving to another access router 200 and transmitting a path setting message upward, the access terminal 200 transmits a packet stored in the buffer of the access router 200 to a higher layer. Check whether there is information of the mobile terminal (100). Each access router 200 forwards the packet to the link of the location where the mobile terminal 100 moves when there is information of the mobile terminal 100.

Next, the DNS-based mobile IPv6 handover method will be described in detail with reference to FIG. 5.

5 is a diagram illustrating a DNS-based mobile IPv6 handover method according to an embodiment of the present invention.

When the mobile terminal 100 moves to a new subnetwork, the mobile terminal 100 generates a path setup message for registering the mobile terminal 100 and transmits the generated path setup message to the MAP 300 to set the path (S100). Here, the route setting message is a message for forming one path from the MAP 300 to the access router 200.

The MAP 300 generates a DNS update message using the route setting message and transmits the generated DNS update message to the local DNS server 600 to update the mobile terminal 100 (S102). Here, the DNS update message includes the home address of the mobile terminal 100, the CoA of the MAP 300, and the life time. In addition, the DNS update message functions to update a DNS resource record of the mobile terminal 100 in the local DNS server 600.

The local DNS server 600 retrieves the DNS resource record associated with the home address of the mobile terminal 100 indicated in the DNS update message (S104). That is, the local DNS server 600 determines whether a mobility binding exists in a DNS resource record related to the mobile terminal 100.

In addition, if the DNS resource record associated with the home address of the mobile terminal 100 indicated in the DNS update message is not confirmed, the local DNS server 600 checks the DNS resource record in association with the main DNS server 700.

In addition, the local DNS server 600 generates a new resource record if the mobility binding does not exist in the DNS resource record, and performs an update if it exists (S106).

In addition, the local DNS server 600, when the mobile terminal 100 moves to a network managed by another MAP (300) must update to the CoA and the lifetime of the new MAP (300) and the mobile within one subnet In this case, update by lifetime.

In addition, when updating the resource record of the mobile terminal 100, the local DNS server 600 updates and stores the resource record of the mobile terminal 100 in the database of the main DNS server 700 in the same manner.

In addition, when the local DNS server 600 checks the DNS resource record in the main DNS server 700, the local DNS server 600 receives and stores the updated resource record from the main DNS server 700.

Subsequently, when there is packet data to be transmitted to the mobile terminal 100, the target node 500 generates an invalence query message and transmits it to the main DNS server 700 (S108).

As shown in FIG. 6, the format of the invalence query message is to have the reserved bit 800 have a value of '001' indicating the mobile terminal 100 and set the value of the OpCode 820 to '0011'. Indicates that this is a query.

Query message types are shown in [Table 1] below.

The main DNS server 700 analyzes the received Invals query message to determine that it is an Invals query and to query the address of the mobile terminal 100.

In addition, the main DNS server 700 must generate a new response message to manage the resource record for the mobile terminal 100 differently.

As shown in FIG. 7, the format of the response message includes the lifetime value and the CoA of the mobile terminal 100 that the target node 500 needs.

The response record has a 0xC00C point value, which specifies the query record instead of repeating the domain name.

The main DNS server 700 generates a response message in response to the invalence query message and transmits the response message to the target node 500 (S110).

The target node 500 may transmit packet data using CoA as a destination address. The target node 500 includes the home address of the mobile terminal 100 in the option field of the IP header to inform exactly who is sending the packet data (S112).

The MAP 300 searches the home address by analyzing the IP header of the packet data received from the target node 500, determines whether the home address exists in the visitor list, and moves through the set-up path. It transmits to the terminal 100 (S114).

In the exemplary embodiment of the present invention, mobile IPv6 mobility management is performed through a domain name in which an IP address of the mobile terminal 100 having an IP address is formed in an involes domain structure.

Conversely, it is possible to manage mobile IPv6 mobility by converting domain names into IP.

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

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

1 is a diagram illustrating a conventional mobile IPv6 handover procedure.

2 is a diagram briefly illustrating a configuration of a DNS-based mobile IPv6 handover system according to an embodiment of the present invention.

3 is a view for explaining the DNS-based mobile IPv6 domain name invoicing structure proposed in the embodiment of the present invention.

4 is a diagram for explaining a DNS-based mobile IPv6 local mobility management structure according to an embodiment of the present invention.

5 is a diagram illustrating a DNS-based mobile IPv6 handover method according to an embodiment of the present invention.

6 is a diagram illustrating a format of an invalence query message according to an embodiment of the present invention.

7 is a diagram illustrating a format of a response message according to an embodiment of the present invention.

Claims (9)

In the mobile IPv6 handover method when the mobile station moves to a new subnetwork, (a) an update message from a mobility anchor point receiving a routing message indicating a packet for registration of the mobile station, wherein the update message includes a home address and a care of address for the mobile station composed of IP; Receiving a domain name formed in an Inverse Domain structure; And (b) search for a resource record indicating a resource of the terminal associated with the home address of the mobile station and update if there is a mobility binding of the mobile station included in the resource record; And create a new resource record if it doesn't exist Handover method comprising a. According to claim 1, In step (b), Searching for and receiving a resource record of the mobile terminal in cooperation with a main domain name system server when there is no mobility binding of the mobile terminal; Handover method further comprising. According to claim 1, In step (b), When the mobile station moves on a sub-network, updating by a life time and updating to a care of address of a new mobility anchor point Handover method comprising a. In the mobile IPv6 handover system when the mobile station moves to a new sub network, Receive the home address and care of address of the mobile terminal made up of IP as a domain name formed in an involes domain structure, update the mobility binding of the mobile terminal corresponding to the domain name, and use the domain name to move the mobile terminal. A plurality of local domain name system server for managing the mobility of the terminal; And Receives and manages the mobility bindings of the mobile terminal from the plurality of local domain name system servers, and receives an invalence query message for requesting the address of the mobile terminal as a domain name from a target node in response to the invalence query. Main domain name system server for transmitting a response message including the address of the mobile terminal to the target node Handover system comprising a. The method of claim 4, wherein The invalence query message includes a wireless query and a wireless invalence query in a query message type. The method of claim 4, wherein The response message includes the lifetime of the mobile terminal and the care of address. In the mobile IPv6 handover system when the mobile station moves to a new sub network, An update message for setting a path by receiving a path setting message indicating a packet for registration of the mobile station, and updating a mobility binding of the mobile station, wherein the update message is a home address and a care-of-address of the mobile station made of IP; A mobility anchor point for generating and transmitting the domain name including the domain name formed in the invoicing domain structure; And A local domain name system server that receives the update message to update the mobility binding of the mobile terminal corresponding to the domain name and manages the mobility of the mobile terminal using the domain name Handover system comprising a. The method of claim 7, wherein The mobility anchor point stores the mobility binding information of the mobile terminal without transmitting the update message to the local domain name system server when the mobile terminal moves on a subnetwork. The method of claim 7, wherein When the mobility anchor point receives packet data including the home address of the mobile station in an IP header from a target node, the mobility anchor point searches for whether the mobile station's home address exists in a pre-stored visitor list and searches for the packet data. Handover system, characterized in that for transmitting to the mobile terminal through.

Images