KR100942703B1 - Method for managing address to provide host mobility in network - Google Patents

Abstract

The present invention relates to a distributed address management apparatus and a method for managing terminal mobility in a network, and to guarantee terminal mobility capable of speeding address reallocation and location registration in a mobile IPv6 network, The subnet prefix and the home ID are the same according to the address system, and the terminal ID is selected from the address pool in response to an address allocation request of the mobile terminal and an address pool for forming and storing each address so as to sequentially increase or decrease. It is possible to reduce the handover delay time by including an address assignment routine for assigning an address to the mobile terminal.

Subnet, Prefix, IPv6, Address Pool

Description

Distributed address management method to guarantee terminal mobility in network {METHOD FOR MANAGING ADDRESS TO PROVIDE HOST MOBILITY IN NETWORK}

The present invention relates to an address management method for guaranteeing the mobility of a terminal, and more particularly, a network capable of reducing handover time by supporting address management of a mobile terminal moving in a network and performing address reassignment and location registration at high speed. The present invention relates to a distributed address management apparatus and a management method for guaranteeing terminal mobility.

The present invention is derived from the research conducted as part of the IT new growth engine core technology development project of the Ministry of Information and Communication and the Ministry of Information and Communication Research and Development. [Task management number: 2006-S-061-01 Task name: IPv6 based Qos service and terminal R & D on Router Technology for IPv6 based QoS Services and Host Mobility].

There is an increasing demand for wireless data services in a wireless Internet network. In order to meet such demands, wireless LANs have become widespread and portable Internet services have been introduced.

However, this change has been somewhat successful in terms of simply providing a wireless data service, but there are still problems in terms of providing a seamless real-time service for reliable data transmission on the move. In particular, there is a problem in that the quality can not be guaranteed when VoIP or user-generated content (UCC) services are required.

Meanwhile, in order to provide existing wired / wireless voice services while maintaining the quality of services provided during the movement of the terminal, and to provide wireless data services, all-IP (network having a structure in which different networks are integrated in half of IP) is based. Networks have been introduced, and Mobile IPv6 (MIPv6) has emerged to provide reliability by mobility in such an All-IP based network.

MIPv6 has been proposed to provide terminal mobility, and many problems can be solved by standardization of IETF. In order to overcome the delay caused by fast handover between subnets, methods such as Fast Handover and Hierarchical MIPv6 have been proposed, which can lead to some speed improvement. Recently, a faster handover scheme has been studied through optimization with the link layer (L2).

However, MIPv6 is not yet able to provide enough handover schemes to provide seamless services, as well as the need for a router that provides MIPv6 in place and a separate MIPv6 support scheme for all mobile terminals. There is a problem. In addition, the upgrade of all terminals must be made inevitably, and each terminal carries a considerable burden of performing a complicated operation. In particular, when the mobile terminal is miniaturized, low power, and simplified, this problem becomes more serious. The most fundamental part of this problem is the address reallocation during handover.

SUMMARY OF THE INVENTION An object of the present invention for solving the above problems is to provide an efficient address management method for supporting mobility in an IPv6 network, thereby requiring a means for speeding address reassignment and location registration of a mobile IPv6 network.

In the distributed address management apparatus for guaranteeing terminal mobility in the network of the present invention for realizing the above means, the subnet prefix and the home ID are the same by an IPv6 based address system, and the terminal ID is sequentially increased or An address pool for forming and storing each address so as to reduce the address; and an address allocation routine for selecting an address from the address pool and assigning an address to the mobile terminal in response to an address allocation request of the mobile terminal.

On the other hand, the address assigned to the mobile terminal is characterized in that the mobile network prefix (prefix) is 48 bits, the subnet prefix (prefix) 16 bits, the home ID (ID) 16 bits and the terminal ID (ID) is configured 48 bits do.

In order to achieve the object of the present invention as described above, the distributed address management method for ensuring the mobility of the terminal in the network of the present invention is a step 1 receiving an address registration request from the mobile terminal, the subnet prefix in response to the address request And selecting an address from an address pool that stores addresses having the same value of 16 bits and 16 bits of home ID, and assigning the selected address to the mobile terminal through an address assignment routine. .

On the other hand, the step 2 is characterized in that the smallest value of the selectable value of the mobile terminal ID that can be allocated from the address pool, characterized in that the mobile terminal ID is a value of 48 bits.

In addition, the address registration request from the mobile terminal and the address assignment to the mobile terminal is characterized in that made by the DHCP address assignment protocol.

In order to achieve the object of the present invention as described above, the distributed address management method for ensuring the mobility of the terminal in the network of the present invention is a step 1 to confirm the home ID and subnet prefix from the address of the mobile terminal, the identified home Step 2 of searching for an address management device which has assigned an address to the mobile terminal using an ID and a subnet prefix; and checking whether an address allocated to the mobile terminal has been normally allocated through communication with the found address management device; The mobile terminal may include four steps of communicating with the mobile terminal using the assigned address when the mobile terminal is normally assigned an address.

As described above, according to the present invention, a distributed address management apparatus and management method for guaranteeing terminal mobility in a network according to the present invention improve the structure that imposes an excessive burden on a mobile terminal in an IPv6-based mobile network, and improves mobility management. It is possible to perform necessary address allocation and reallocation at a high speed.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. However, in describing in detail the operating principle of the preferred embodiment of the present invention, if it is determined that the detailed description of the related known functions or configurations may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

In addition, the same reference numerals are used for parts having similar functions and functions throughout the drawings.

1 is a diagram illustrating a MIPv6 based addressing system applied to the present invention.

Referring to FIG. 1, the MIPv6-based address 100 according to the present invention is a mobile network prefix 110 that all nodes and terminals of a mobile network have in common, and a servernet prefix having a specific subnet in the mobile network. 120, a home ID (130) having a common address among mobile terminals assigned in a specific subnet in the mobile network, and a unique terminal ID 140 of the mobile terminal assigned an address in a specific subnet in the mobile network. It is composed.

The IPv6 address is composed of a 128-bit system, and the method of representation is divided into 8 parts of 128 bits divided into 8 parts, and each part is represented by a colon. In the present invention, a mobile network prefix is defined. Reference numeral 110 denotes 48 bits, servernet prefix 120 includes 16 bits, home ID 130 includes 16 bits, and terminal ID 140 includes 48 bits.

Meanwhile, the mobile network prefix 110 is preset in the entire mobile network. Therefore, when the mobile network is not changed, the values of the mobile network prefix 110 are the same.

The ServerNet Prefix 120 and the Home ID 130 have different values for each device assigning an address to the mobile terminal. That is, home IDs do not overlap between address management devices (or "address management devices") of the entire mobile network. In addition, the unique ID 140 of the mobile terminal assigns a unique ID to each terminal to which the terminal assigns and manages the address by a device that assigns an address (or referred to as an "address management apparatus"). Therefore, there is no case in which terminal IDs are duplicated among terminals assigned an address by one address management apparatus. This indicates that the combination of the home ID 130 and the terminal ID 140 assigned to the terminal in one mobile network is unique and no termination occurs.

For example, assume that a mobile terminal initially connects to a mobile communication network having a mobile network prefix of 3fff: 200: 1000/48. A mobile terminal accessing a mobile network is assigned an address from one router. In this case, the router is called a home agent (HA) in a Mobile IPv6 (MIPv6) network. When the home agent HA assigns an address, the subnet prefix 120 becomes 1abc if the prefix of the subnet that the home agent HA is in charge is 3fff: 200: 1000: 1abc / 64. If the subnet prefix 120 does not overlap over the entire mobile network, the home ID 130 may have the same value as the subnet prefix 120. This is because the home ID 130 is also not duplicated and can be easily calculated from the prefix. In an embodiment, since the terminal ID available in one address management device is 48 bits, since the terminal ID is larger than the current IPv4 address, the terminal ID may be sequentially assigned by increasing the address from 0 to one.

In Mobile IPv6, whenever a mobile station moves through a subnet, a new prefix is allocated and a new address must be generated using the prefix. In the new address generation process, duplicate checks are included, which causes a large delay. However, terminals having such duplicate IDs only need to change the prefix in allocating a new address as the entire mobile network moves. In addition, the terminal may change and forward the prefix at the router including the address management device or the address management device without changing the prefix.

2 is a diagram illustrating a configuration of a distributed address management apparatus for providing terminal mobility according to the present invention.

Referring to FIG. 2, the distributed address management apparatus 200 according to the present invention selects an address from an address pool 210 in which an address is formed and stored according to a predetermined principle with respect to a registration request of a mobile terminal, and thus the mobile terminal. It consists of an address assignment routine 220 for assigning an address.

The address pool 210 stores addresses for allocating to terminals performing network communication in a specific subnet. The address assigned by the present invention is formed so that the addresses provided in specific subnets do not overlap. In particular, when an address is provided, an address is assigned so as not to go through a process of checking whether it is duplicated. Therefore, in the address pool 210 formed based on IPv6, the subnet prefix and the home ID have the same value. The terminal ID is determined according to a certain principle. As described in FIG. 1, the IPv6-based address according to the present invention includes 48 bits of mobile prefix 110, 16 bits of subnet prefix 120, 16 bits of home ID (130), and terminal ID (ID). 140 is configured for 48 bits. Therefore, even when the subnet prefix 120 and the home ID 130 are the same, since the terminal ID 140 has 48 bits, the address is increased in a sequential manner from 0 to 0 or in a manner that decreases to 0. Can be assigned.

The address assignment routine 220 selects an address to be allocated from the address pool with respect to the address request 231 of the mobile terminal 230 and performs a function of executing the address assignment 232 to the mobile terminal 230.

In order to provide a unique home ID and a terminal ID that do not overlap each terminal in the network in the same mobile network prefix, the mobile terminal is assigned an address by the address management apparatus 200 without generating an address by itself, and thus is assigned an address. It is possible to reduce the handover time by eliminating the need to check whether D is redundant.

In addition, the address of the mobile terminal belonging to the same mobile network formed in the address pool 210 of the address management apparatus 200 has the same value as the subnet prefix 120 and the home ID (ID) 130.

In order for the mobile terminal to be assigned an address, a protocol for network connection must exist between the mobile terminal 230 and the address management device 200. The protocol uses an address allocation protocol such as DHCP of an IP network.

3 is a diagram illustrating an embodiment in which address connection information of a mobile terminal is shared between address management apparatuses according to the present invention.

Referring to FIG. 3, the sharing of the address connection information of the mobile terminal between the address management apparatuses is performed after the mobile terminals 311 and 312 are registered with one address management apparatus 310 to move the other address management apparatus 320. Occurs when moving to a jurisdiction.

In detail, the mobile terminal b 312 registers with the address management device 1 310 and receives the address 3ffe: 200: 1000: 1abc: 1abc: 0: 0: 000b and then moves to the address management device 2 320. When moving to a jurisdiction, the original address is used without changing the address. The subnet prefix of the address management device 1 310 is 1abc, the home ID is 1abc, the subnet prefix of the address management device 2 320 is 1234, and the home ID is 1234. Accordingly, when the mobile terminal b 312 moves and wants to receive a service in the jurisdiction of the address management device 2 320, the mobile terminal b 312 is newly updated with the subnet prefix 1234 and the home ID 1234 of the address management device 2 320. You must assign an address.

However, through sharing of the address connection information according to the present invention, the mobile terminals b 312 and 321 can receive a service using the same address regardless of the address management apparatus. In order for the mobile terminals b 312 and 321 to receive a service using the same address, the following procedure is required.

When the mobile terminals b 312 and 321 move and enter the address management apparatus 2 320, the address management apparatus 2 320 uses the home ID 1abc among the addresses of the mobile terminal b 321 and the mobile terminal b 321. It can be seen that is a terminal registered in another address management device 1 (310). In addition, the address of the address management apparatus 1 310 which has assigned an address to the mobile terminal b 321 may be confirmed using the subnet prefix 1abc among the addresses of the mobile terminal b 321.

On the other hand, the address management device 2 (320) is normally assigned an address from the address management device 1 (310) by the mobile terminal b 321 through communication with the address management device 1 (310) registered with the mobile terminal b (321) Check if it is received. If it is confirmed that the mobile terminal b 321 is normally assigned an address from the address management device 1 310, the address management device 2 320 is the original address of the mobile terminal b 321, 3ffe: 200: 1000: Communicate using 1abc: 1abc: 0: 0: 000b.

Routers generally refuse to forward traffic when it has a traffic address that is different from the subnet prefix of its own subnet.

However, in the present invention, despite the movement of the mobile terminal b (321), the address management device 2 (320) confirms that the address of the mobile terminal b (321) is properly assigned from the address management device 1 (310) In this case, even when the mobile terminal b 321 transmits using the original main path as it is, normal communication is performed. In FIG. 3, the prefix 3ffe: 200: 1000: 1abc / 64 of the mobile terminal b 321 is different from the prefix 3ffe: 200: 1000: 1234/64 of the address management device 2 320, but the address management device 2 320 may not be the same. Even when data having a 3ffe: 200: 1000: 1abc / 64 prefix is transmitted from the mobile terminal b 321 to the sender side address, data transfer is normally performed.

On the contrary, even when traffic is delivered to the mobile terminal b 321, the prefix of the sender address is 3ffe: 200: 1000: 1abc / 64. However, the address management apparatus 1 310 determines whether a mobile terminal having a 3ffe: 200: 1000: 1abc / 64 prefix is connected to its own subnet like the mobile terminal a 311 or the mobile terminal b 321. You must know if you moved to a different subnet. In the mobile IPv6 standard, it is possible to know whether the mobile terminal belongs to the subnet of the address management apparatus 1 310 by using a Binding Update.

4 is a diagram illustrating a method of performing communication using an original address when a mobile terminal moves according to the present invention.

Referring to FIG. 4, when the mobile terminal moves out of the jurisdiction of the address management apparatus to which the mobile terminal has assigned an address, and performs communication in the jurisdiction of another address management apparatus, the other address management apparatus may transmit the address of the mobile terminal from the mobile terminal. Receive a communication request using the. As described in FIG. 1, the address of the mobile terminal is composed of 48 bits of mobile prefix, 16 bits of subnet prefix, 16 bits of home ID, and 48 bits of terminal ID.

The subnet prefix of the original address management device to which the mobile terminal is assigned an address and the address management device currently requesting communication are not the same.

Therefore, the address management device receiving the communication request confirms that the subnet prefix of the mobile terminal address is different from its own subnet prefix.

When it is confirmed that the subnet prefix of the mobile terminal and the subnet prefix of the address management device are different, the home ID and the subnet prefix are retrieved from the address of the mobile terminal (S410).

The address management device searches for an address management device that assigns an address to the mobile terminal using the home ID and the subnet prefix identified through the search. (S420) Specifically, the mobile terminal uses the home ID among the addresses of the mobile terminal. It is confirmed that the terminal is registered in another address management apparatus, and the address of the address management apparatus which has assigned an address to the mobile terminal using the subnet prefix is checked.

When the address management device which has assigned an address to the mobile terminal is confirmed in this way, the address management device that has received the communication request communicates with the address management device that has assigned the address to the mobile terminal to determine whether the address allocated to the mobile terminal is normally allocated. Check (S430).

When the mobile terminal is normally assigned an address, the mobile terminal communicates with the mobile terminal using the assigned address.

However, the address management device receiving the communication request rejects the transmission of traffic transmitted from or transmitted to the mobile terminal when the mobile terminal is not normally assigned an address.

The present invention described above is not limited to the above-described embodiments and the accompanying drawings, and it is common in the art that various substitutions, modifications, and changes can be made without departing from the technical spirit of the present invention. It will be apparent to those skilled in the art.

1 is a diagram illustrating a MIPv6 based addressing system applied to the present invention.

2 is a diagram illustrating a configuration of a distributed address management apparatus for providing terminal mobility according to the present invention.

3 is a diagram illustrating an embodiment in which address connection information of a mobile terminal is shared between address management apparatuses according to the present invention.

 4 is a diagram illustrating a method of performing communication using an original address when a mobile terminal moves according to the present invention.

Description of the main parts of the drawing

110: mobile network prefix 120: subnet prefix

130: home ID (ID) 140: terminal ID (ID)

200: address management device 210: address pool

220: address assignment routine

Claims (12)

delete delete delete delete delete delete delete Verifying a home ID and a subnet prefix from an address of the mobile terminal; Searching for an address management device assigned an address to the mobile terminal using the identified home ID and subnet prefix; Checking whether the address allocated to the mobile terminal is normally allocated through communication with the retrieved address management apparatus; And If the mobile terminal is normally assigned an address, a method of address management of a distributed method for guaranteeing terminal mobility in a network comprising the step of communicating with the mobile terminal using the assigned address. The method of claim 8, wherein the first step Receiving a communication request using the address of the mobile terminal, And confirming that the subnet prefix of the mobile terminal address is different from the value of the subnet prefix of the address management device that has received the communication request. The method of claim 8, wherein the address of the mobile terminal is Distributed for ensuring terminal mobility in a network comprising 48 bits of mobile prefix, 16 bits of subnet prefix, 16 bits of home ID, and 48 bits of terminal ID Method of address management. The method of claim 8, wherein the second step Confirming that the mobile terminal is a mobile terminal registered with another address management device by using the home ID; And determining an address of an address management device which has assigned an address to the mobile terminal using the subnet prefix. The method of claim 10, When the mobile terminal is not properly assigned an address, the distributed address management method for guaranteeing terminal mobility in a network, characterized in that the transmission of traffic transmitted from the mobile terminal or to the mobile terminal is rejected. .

Images