KR20160114401A - Method for switching between IPv4 service and IPv6 service in Locator ID Separation Protocol network environment and Locator ID Separation Protocol network system - Google Patents

Abstract

The present invention relates to a method to switch between an internet protocol version 4 (IPv4) service and an internet protocol version 6 (IPv6) service in a locator ID separation protocol (LISP) environment through live migration of a virtual machine, and an LISP network system. The method to switch from the IPv4 service to the IPv6 service through live migration of a virtual machine in an LISP network system according to the present invention comprises the following steps: a second hypervisor receives a packet for migration of a source virtual machine included in a first hypervisor and makes the source virtual machine migrate to a target virtual machine; a second router which is in control of the second hypervisor reflects an IPv4 identifier of the source virtual machine and mapping information which is information about a mapped IPv6 identifier allocated to the target virtual machine and updates a map database; the second router transmits the IPv4 identifier of the source virtual machine and the IPv6 identifier of the target virtual machine to a first router that is in control of the first hypervisor; and the first router checks at least one different router that communicates with the source virtual machine, transmit the IPv4 identifier of the source virtual machine and the IPv6 identifier of the target virtual machine to the at least one different router and updates mapping information stored in the at least one different router.

Description

[0001] The present invention relates to an IPv4-IPv6 service switching method and a LISP network system in a LISP network environment,

The present invention relates to an IPv4-IPv6 service switching technology in a LISP (Locator ID Separation Protocol) network environment, and more particularly, to a method of switching an IPv4-IPv6 service through a live migration of a virtual machine in a LISP environment, LISP network system.

With the emergence of various terminals and services for the Internet of Things (IoT), the issue of IPv4 address depletion has become even more serious, and IPv6 addresses that are unique to all terminals will be used in the near future. .

Although an IPv4-IPv6 service can be accessed using an IPv4-IPv6 conversion technique, there is a problem in that a processing overhead occurs in the conversion process and an additional IPv4-IPv6 conversion equipment is purchased. The following patent documents disclose an IPv4 / IPv6 interworking gateway.

Due to such a problem, actual content providers are considering switching a service being provided in the IPv4 format to an IPv6 format and operating the service. However, it is technically difficult to switch from IPv4 to IPv6, and there is a problem that service switching without service interruption is more difficult.

Korean Patent Publication No. 10-2010-0059739

The present invention has been proposed in order to solve such a problem, and it is an object of the present invention to provide an IPv4-IPv6 service switching method and a LISP network system without service interruption through live migration of a virtual machine in a LISP network environment, .

Other objects and advantages of the present invention will become apparent from the following description, and it will be understood by those skilled in the art that the present invention is not limited thereto. It will also be readily apparent that the objects and advantages of the invention may be realized and attained by means of the instrumentalities and combinations particularly pointed out in the appended claims.

According to a first aspect of the present invention, there is provided a method of switching a service from IPv4 to IPv6 through migration of a virtual machine in a Locator ID Separation Protocol (LISP) network system, Migrating the source virtual machine to a target virtual machine by receiving a packet for migration of the source virtual machine included in the one hypervisor; Updating the map database by reflecting, in the map database, the mapping information that the second router managing the second hypervisor maps the IPv4 identifier of the source virtual machine and the IPv6 identifier assigned to the target virtual machine; Transmitting, by the second router, an IPv4 identifier of the source virtual machine and an IPv6 identifier of the target virtual machine to a first router that is in charge of the first hypervisor; And the first router identifies the router as one or more other routers communicating with the source virtual machine and transmits the IPv4 identifier of the source virtual machine and the IPv6 identifier of the target virtual machine to the one or more other routers, And updating the mapping information stored in another router.

According to a second aspect of the present invention, there is provided a LISP network system for switching a service from IPv4 to IPv6 through migration of a virtual machine in a Locator ID Separation Protocol (LISP) network environment, A first hypervisor that includes a source virtual machine to perform; A first router for routing the first hypervisor; A second hypervisor for creating a target virtual machine, receiving a packet for migration of the source virtual machine, and migrating the source virtual machine to the target virtual machine; And updating the map database by mapping the mapping information in which the IPv6 identifier allocated to the target virtual machine and the IPv4 identifier of the source virtual machine are mapped to the map database to manage the routing of the second hypervisor, And a second router for transmitting an IPv6 identifier of the target virtual machine and an IPv4 identifier of the source virtual machine to the first router, wherein the first router identifies the router as one or more other routers communicating with the source virtual machine, And transmits the IPv6 identifier of the target virtual machine and the IPv4 identifier of the source virtual machine to update the mapping information stored in the one or more other routers.

A method for switching a service from IPv4 to IPv6 in a Locator ID Separation Protocol (LISP) network system according to the third aspect of the present invention for achieving the above object is characterized in that a source virtual machine IPv4 identifier before a router is migrated to a destination address Receiving a set packet from a client terminal; The router verifying the IPv6 identifier of the target virtual machine mapped with the IPv4 identifier in the mapping information being stored; The router changing the destination address of the packet from the IPv4 identifier to the IPv6 identifier; And adding the LISP header to the packet whose destination address has been changed by the router and transmitting the LISP header to the destination router.

The present invention has an advantage of reducing the cost of switching the IPv4-IPv6 service by switching the IPv4-IPv6 service through the live migration of the virtual machine in the LISP network environment.

In addition, according to the present invention, the mapping information generated through the live migration of the virtual machine is immediately transmitted to the router and the mapping system, and the mapping information of the corresponding router and the mapping system is immediately updated, There is an effect that the interruption can be minimized.

In addition, the present invention realizes the switching service between IPv4 and IPv6 through extension of the mapping information stored in the router and the mapping system, which is also excellent in versatility and determinability of service application.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in and form a part of the specification, illustrate exemplary embodiments of the invention and, together with the description, serve to explain the principles of the invention. And shall not be construed as limited to such matters.
1 is a diagram schematically showing an operation state of an SMR message.
2 is a diagram illustrating a LISP network system, in accordance with an embodiment of the present invention.
3 is a diagram illustrating a format of a control message according to an embodiment of the present invention.
4 is a diagram illustrating a process of performing live migration of a virtual machine in a LISP network system according to an embodiment of the present invention.
FIG. 5 is a flowchart illustrating a method for changing a network configuration according to a migration of a virtual machine in a LISP network system according to an embodiment of the present invention.
6 is a flowchart illustrating a method of routing a packet by converting a destination address of a packet from an identifier of a source virtual machine to an identifier of a target virtual machine in a LISP network system in which live migration has been completed according to an embodiment of the present invention .
7 is a flowchart illustrating a method of processing a control message in a router according to an embodiment of the present invention.

The foregoing and other objects, features and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings, in which: There will be. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. Hereinafter, a preferred embodiment of the present invention will be described in detail with reference to the accompanying drawings.

Before describing an embodiment of the present invention, the LISP (Locator ID Separation Protocol) will be described.

An identifier (EID) is identification information allocated to a terminal or a network interface to which the terminal node is connected.

The RLOC (Routing Locator) is an address assigned to a router that exists in the LISP network and is used to route packets in the LISP core network.

The locator and the identifier are concepts used in a LISP network environment.

The LISP is a protocol for reconfiguring the Internet by separating the IP address architecture into two elements, i.e., a location and an identifier. Only the location is registered in the routing system, and an identifier causing an increase in the BGP (Boarder Gateway Protocol) And thus facilitates the scalability of the Internet.

The packet transmitted from the originating host is added to the LISP header in an edge router (ITR). The Edge router sets the source address of the LISP header as its own IP address (i.e., location) It sets the IP address of the Egress Tunnel Router (ETR) where the host is located, encapsulates the packet with the LISP header added, and sends it. In the Internet backbone, routing is performed using only the ITR and ETR IP addresses present in the LISP header, and the ETR decapsulates the received packet to remove the LISP header, and then refers to the identifier to forward it to the called host.

In order to acquire the locator mapped to the identifier, a mapping system for managing the mapping information of the locator and the identifier is constructed in the LISP network. The mapping information stored in each router is managed by the mapping system. The router stores mapping information of a destination terminal and an IP address of a destination router in a map cache and requests mapping information not stored in the map cache to the mapping system to receive the mapping information. However, when the identifier of the host to which the router is controlled changes, the router does not directly transmit the mapping information of the changed identifier and the positioner to the mapping system, but transmits the changed mapping information to the mapping system only when there is a request of the mapping system.

Meanwhile, the router transmits the mapping information changed in the other routers to another router through a SMR (Solicit Map Request) message. The method of synchronizing the changed mapping information through the SMR message is a method in which the changed mapping information is applied to the entire network There is a problem that a certain period of time is required until it is completed.

1 is a diagram schematically showing an operation state of an SMR message.

Referring to FIG. 1, when the first router 11 detects the change in the mapping information recorded in the map DB of the first router 11, the first router 11 notifies the router corresponding to each positioner stored in the map cache of its own SMR Message to notify each router of the change of the mapping information (S11). That is, the first router 11 confirms the other routers 12 that have recently communicated with the first router 11 in the map cache, and transmits the SMR message to the other routers 12.

Then, the other routers 12 receiving the SMR message detect that a change has occurred in the map DB of the first router 11 and, in order to receive new mapping information from the first router 11, And transmits a message (map-request) to the first router 10 (S12). Then, the other routers 12 receive the map response message (map-reply) including the changed mapping information from the first router 11, store the change mapping information in its own map cache, Routes the packet using the mapping information stored in the cache.

However, since the mapping information update method using the SMR is transmitted only to the placeholders (i.e., routers) stored in the cache of the router, routers that are not stored in the cache have a problem of not knowing the change information of the mapping information of the corresponding node. In addition, when the network size increases or the number of identifiers managed by the router increases, the number of routers (i.e., locators) stored in the map cache increases. Therefore, when mapping information changes in a specific router, Traffic for updating information is also increased, resulting in a problem that it takes much time until the changed mapping information is reflected in the entire network.

Such an update mechanism using the SMR message may cause a problem when the service quality and the continuity of the service are required, such as a virtual machine migration.

2 is a diagram illustrating a LISP network system, in accordance with an embodiment of the present invention.

2, the LISP network system according to an exemplary embodiment of the present invention includes a plurality of hypervisors 210 and 220, a mapping system 500, and a plurality of routers 310, 320 and 330 .

The routers 310, 320 and 330 divide the mapping information related to the identifiers connected to the routers 310, 320 and 330 by identifiers into map databases (312, 322, and 332) The mapping information obtained from the system 500 is divided into identifiers and stored in the map cache 311, 321, and 331. That is, the routers 310, 320, and 330 store the mapping information related to the identifier included in the subnet of the router 310 in its own map DB 312, 322, and 332, Information from the mapping system 500 and stores the information in the map cache 311, 321, and 331. Among the mapping information stored in the map cache 311, 321, and 331, unused mapping information is deleted for a predetermined time (e.g., one minute).

The mapping information stored in the map cache 311, 321, and 331 and the map DB 312, 322, and 332 includes information for service switching from IPv4 to IPv6, that is, an IPv4 identifier, an IPv6 identifier, Mapping information is recorded. An IPv4 address used by the source virtual machine 211 is recorded in the IPv4 identifier, and an IPv6 address used by the target virtual machine 221 is recorded in the IPv6 identifier. In addition, the positioner records information on whether the IP address of the router is recorded and whether the IPv6 address is used in the V6 flag. Means that the IPv6 address is used when the number '1' is recorded in the V6 flag, and the IPv4 address is used when the number '0' is recorded in the V6 flag.

The source virtual machine 211 to be described later is a virtual machine that provides an IPv4-based service, and the target virtual machine 221 transfers the service of the source virtual machine 211 and proceeds with the service based on the IPv6 It is a virtual machine. That is, when the live migration according to the present invention proceeds, the function of the source virtual machine 211 is transferred to the target virtual machine.

3 is a diagram illustrating a format of a control message according to an embodiment of the present invention.

Referring to FIG. 3, the Type field indicates a message type. Numbers '0' to '4' and a number '8' are reserved in the LISP. An identifier indicating a control message according to the present invention The number '6' is recorded in the type field.

In addition, the control message includes four flag fields, in which one of the numbers '1' and '0' is recorded as a flag bit.

The flag field 'O' indicates whether the entity that transmitted the control message is a source virtual machine and an associated node (that is, the first hypervisor or the first router) providing the IPv4 service or a node associated with the target virtual machine providing the IPv6 service (I.e., the second hypervisor or the second router). The 'O' used to distinguish the play field means 'O', not a zero, but a vowel with an order of fifteenth of the English alphabet.

In the case of a message generated by the first hypervisor 210 including the source virtual machine 211 having the IPv4 address or the first router 310 responsible for routing of the first hypervisor 210, The second hypervisor 220 that loads the target virtual machine 221 to which the IPv6 service is to be provided or the second router 220 that performs routing of the second hypervisor 220 320, the number '0' is recorded in the flag field 'O'.

The flag field 'H' indicates whether the subject sending the control message is a router or a hypervisor. In the case of the control message generated by the hypervisors 210 and 220, the number '1' is recorded in the flag field 'H' and the number '0' is recorded in the flag field 'H'.

In the flag field 'S', information for determining whether the IPv6 address is basically used in the map cache 311, 321, and 331 is recorded. If the number '1' is recorded in the flag field 'S', the IPv6 address is basically used. If the number '0' is recorded, the IPv4 address is basically used.

Update information for the map cache 311, 321, and 331 of the routers 310, 320, and 330 is recorded in the flag field 'C'. When the number '1' is recorded in the flag field 'C', the routers 310, 320, and 330 having received the control message transmit the map caches 311, 321, and 331 based on the old and new identifiers included in the control message. ).

An identifier in the IPv4 format is recorded in the old identifier (Old EID) field, and an identifier in the IPv6 format is recorded in the new identifier (New EID) field.

The routers 310, 320 and 330 check each flag field included in the control message and perform a procedure for migration based on the respective flag fields as described later. The routers 310, 320, and 330 receive the packet, and when confirming the mapping information that the IP flag mapped with the IPv4 identifier, which is the destination address of the packet, is set to '1' After changing to the IPv6 identifier mapped to the IPv4 identifier, the LISP header is added to this packet, and the LISP header is sent to the destination.

The mapping system 500 collects the mapping information stored in the routers 310, 320, and 330 and stores the combined information in an integrated database 600 (hereinafter referred to as an integrated DB). When the mapping system 500 receives mapping information for a specific identifier from the routers 310, 320, and 330, the mapping system 500 extracts the mapping information having the identifier from the integrated DB 600, and transmits the extracted mapping information to the corresponding router (310, 320, 330). When the mapping system 500 receives the changed mapping information from the routers 310, 320, and 330, the mapping system 500 updates the integrated database by reflecting the mapping information in the integrated DB 600.

The hypervisors 210 and 220 are logical platforms for simultaneously executing a plurality of operating systems in a host computer, and execute a specific service using one or more virtual machines. That is, a plurality of virtual machines that are responsible for the respective services of the hypervisors 210 and 220 are created, and various services are provided using the virtual machines. The hypervisors 210 and 220 may be mounted on a server to perform specific services. In particular, the hypervisors 210 and 220 generate a control message for live migration when an IPv6 transition is required for the source virtual machine 211 serving as an IPv4-based service, and transmit the control message to the destination hypervisor 220 ), Thereby performing live migration for switching the IPv4-IPv6 service of the source virtual machine 211.

Meanwhile, when the live migration is completed, the destination hypervisor 220 in which the live migration is in progress allocates an IPv6 identifier for the target virtual machine 221 that has been migrated. In addition, when the live migration is completed, the source hypervisor 210 that has performed the live migration suspends the operation of the virtual machine that has performed the service based on the IPv4.

4 to 6, when the first hypervisor 210 and the first router 310 are nodes related to the source virtual machine 211 and the source virtual machine 211 is a target virtual machine It is assumed that the nodes related to the first router 221 and the second router 320 are the second hypervisor 220 and the second router 320, respectively.

4 is a diagram illustrating a process of performing live migration of a virtual machine in a LISP network system according to an embodiment of the present invention.

Referring to FIG. 4, when the first hypervisor 210 receives a request from the administrator for IPv6 service switching for the source virtual machine 211 providing the IPv4-based service, the first hypervisor 210 transmits a control message requesting a live migration to the first router (S401). In this case, the first hypervisor 210 sets '0' in the flag field 'O', '1' in the flag field 'H', '1' in the flag field 'S' to indicate that the control message requests live migration '1' in the flag field 'C', and '0' in the flag field 'C', respectively. Also, the first hypervisor 210 records the identifier of the first hypervisor 210 in the spherical identifier field in the control message, and records the identifier of the destination hypervisor (i.e., the second hypervisor) in the new identifier field do.

Then, the first router 310 confirms the information recorded in each flag field of the control message, and determines that the first hypervisor 210 requests live migration according to the confirmed information. Then, the first router 310 confirms the identifier of the destination hypervisor (i.e., the second hypervisor) included in the new identifier field of the control message, and identifies the location of the mapped location (i.e., the address of the second router) In the map cache 311 (S403). In this case, if the location mapped to the identifier of the second hypervisor 220 is not searched in the map cache 311, the first router 310 requests the mapping system 500 to map the mappers with the identifier, do.

Next, the first router 310 receives a dummy value as an IPv4 identifier, an identifier of the second hypervisor 220 as an IPv6 identifier, an IP address of the second router 320 as a location, 'Are stored in the map cache 311, thereby updating the map cache 311 (S405). Then, the first router 310 transmits the dummy value to the first hypervisor 210 (S407).

Then, the first hypervisor 210 acquires a memory dump of the source virtual machine 211 to be migrated (S409), and transmits the packet including the memory dump to the first router 310 (S411) . At this time, the first hypervisor 210 sets the source address of the packet as its own IP address, sets the destination address of the packet as the dummy value, and sends the packet.

Then, the first router 310 confirms the IPv6 identifier (i.e., the IPv6 address of the second hypervisor) mapped to the dummy value in the map cache 311, and updates the destination address of the packet from the dummy value to the confirmed IPv6 To an identifier (S413). Then, the first router 310 adds a LISP header to the memory dump packet and encapsulates it, and transmits the memory dump packet to the second router 320 (S415 and S417). At this time, the first router 310 adds a LISP header to the memory dump packet in which its IP address is recorded as a source address and the IP address of the second router 320 is recorded as a destination address.

Next, the second router 320 removes the LISP header to unencapsulate (i.e., decapsulate) the memory dump packet, refers to the destination address of the encapsulated header, and transmits the memory dump packet to the second To the hypervisor 220 (S419).

The second hypervisor 220 refers to the memory dump packet to create a target virtual machine 221 to be a migration destination and sends the generated target virtual machine 221 to the first hypervisor 210, The migration of the virtual machine is proceeded by transferring the function of the source virtual machine 211 of step S421.

FIG. 5 is a flowchart illustrating a method for changing a network configuration according to a migration of a virtual machine in a LISP network system according to an embodiment of the present invention.

Referring to FIG. 5, when the second hypervisor 220 completes the migration of the virtual machine, the second hypervisor 220 transmits a control message to the second router 320 indicating that the migration is completed (S501). At this time, the second hypervisor 220 sets '1' to the flag field '0', '1' to the flag field 'H', '0' to the flag field 'S', '0' to the flag field 'C' And transmits to the second router 320 the control message in which the identifier of the source virtual machine 211 and the 'NULL' in the new identifier field are recorded in the old identifier field.

Then, the second router 320 checks each flag field included in the control message, and if the data recorded in this flag field is '0 = 1', 'H = 1', 'S = 0' 0 ', and determines that the migration of the virtual machine has been completed. Then, the second router 320 generates a new IPv6 identifier (i.e., IPv6 address) for the migrated virtual machine (S503). At this time, the second router 320 can generate the IPv6 identifier by combining the 32-bit IPv4 address recorded in the 64-bit IPv6 prefix, the 32-bit random number, and the old identifier field.

Then, the second router 320 transmits a control message in which the generated IPv6 identifier is written in the new identifier field to the second hypervisor 220 (S505). In the control message, the identifier of the source virtual machine 211 is recorded in the spherical identifier field, and '1', '0', and '1' are added to each of the flag fields 'O', 'H', 'S' 1 ', and' 0 'are recorded.

Then, the second hypervisor 220 checks each flag field included in the control message, and if the data recorded in the flag field is '0 = 1', 'H = 0', 'S = 1' = 0 ', and determines that the IPv6 of the target virtual machine 221 is allocated according to the combination of the flag fields. The second hypervisor 220 identifies the IPv6 identifier included in the new identifier field of the control message. Then, the second hypervisor 220 creates a new virtual network interface in the target virtual machine 221, and sets the IP address of the virtual network interface as the confirmed IPv6 identifier (S507). That is, the second hypervisor 220 assigns the identifier of the target virtual machine 221, which has been migrated, to the IPv6 identifier generated by the second router 320.

Next, the second router 320 updates the mapping information stored in the map DB 322 by reflecting the IPv6 identifier generated in step S503 (S509). That is, the second router 320 maps the IPv4 identifier of the source virtual machine, the IPv6 identifier of the migrated target virtual machine 221, its own address (i.e., RLOC), and mapping information in which the V6 flag is mapped to '1' DB 322 to update the mapping information.

Then, the second router 320 transmits a control message including the changed mapping information to the first router 310 and the mapping system 500 (S511, S513). At this time, the second router 320 records '1', '0', '1', and '0' in the flag fields 'O', 'H', 'S', and 'C' Also, an IPv4 identifier (i.e., IPv4 address) of the source virtual machine 211 and an IPv6 identifier (i.e., an IPv6 address) of the target virtual machine 221 are recorded in the old identifier field.

Then, the mapping system 500 identifies the IPv6 identifier included in the IPv4 identifier and the new identifier field included in the old identifier field included in the control message received from the second router 320, and transmits the IPv4 identifier, the IPv6 identifier The IP address of the second router and the V6 flag are set to '1' in the integrated DB 600 to update the mapping information of the integrated DB 600 in step S515.

The first router 310 extracts a flag field included in the control message received from the second router 320. If the data recorded in the flag field is' 0 = 1 ',' H = 0 ',' S = 1 ', and' C = 0 ', the process of deleting old mapping data and updating the mapping information of another router is performed. That is, the first router 310 checks the IPv4 identifier in the old identifier field of the control message received from the second router 320, deletes the mapping information having the IPv4 identifier from the map DB 312, The old mapping information of the machine is deleted (S517). Then, the first router 310 checks the other routers that have communicated with the source virtual machine 211 in the map cache 311, and transmits a control message including mapping information changed to each of the other routers 311 (S519). At this time, the first router 310 records '0', '0', '1', '1' in the flag fields 'O', 'H', 'S' and 'C' Also records the IPv4 identifier of the source virtual machine 211 in the globally identifiable field and records the IPv6 identifier of the target virtual machine 221 in the new identifier field. In the description with reference to FIG. 5, it is described that the third router 330 is a node in communication with the source virtual machine 211.

The third router 330 receives the control message including the changed mapping information from the first router 310 and extracts the flag field included in the control message. The third router 330 transmits the control message to the map cache 331 in accordance with the data recorded in the flag field being '0 = 0', 'H = 0', 'S = 1', ' Quot;), < / RTI > Then, the third router 330 checks the IPv6 identifier included in the IPv4 identifier and the new identifier field included in the old identifier field of the control message, and identifies the IPv4 identifier, the IPv6 identifier, The mapping information of the map cache 331 is updated by reflecting the mapping information in which the IP address and the V6 flag '1' are mapped (S521).

When the update of the map cache 331 of the other router 330 is completed, the first router 310 transmits a message to the first hypervisor 210 indicating that the information of the entire network has been updated (S523).

The first hypervisor 210 stops the operation of the source virtual machine 211 and controls the IPv4-based service not to proceed through the source virtual machine 211, And causes the IPv6 based service to proceed through the target virtual machine 221 (S525).

6 is a flowchart illustrating a method of routing a packet by converting a destination address of a packet from an identifier of a source virtual machine to an identifier of a target virtual machine in a LISP network system in which live migration has been completed according to an embodiment of the present invention .

In the description with reference to FIG. 6, it is described that the client terminal 400 requests a service using the IPv4 identifier of the source virtual machine 211.

Referring to FIG. 6, the client terminal 400 transmits a packet in which the IPv4 identifier (i.e., IPv4 address) of the source virtual machine is set as the destination address to the third router 330 (S601).

In step S603, the third router 330 checks the IPv4 identifier, which is the destination address, in the packet, and transmits the mapping information (i.e., the IPv6 identifier, the locator, and the V6 flag) mapped to the IPv4 identifier to the map cache 331 (S605). On the other hand, when the mapping information mapped to the IPv4 identifier is not stored in the map cache 331, the third router 330 can request and receive the corresponding mapping information from the mapping system 500.

Then, the third router 330 determines whether the V6 flag is set to '1' among the above-identified mapping information. If the V6 flag is set to '1', the third router 330 determines that the target virtual machine 221 of the destination is basically using the IPv6 address, and transmits the mapping information of the IPv6 identifier corresponding to the IPv4 identifier And changes the destination address of the packet from the IPv4 identifier to the IPv6 identifier (S607).

Then, the third router 330 adds the LISP header to the packet to encapsulate the packet (S609), and transmits the encapsulated packet to the second router 320 corresponding to the location in the mapping information (S611 ). At this time, the third router 330 encapsulates the packet by adding a LISP header in which the IP address of the second router 320 is recorded as the source address and the IP address of the second router 320 as the destination address.

On the other hand, when the V6 flag is set to '0', the third router 330 determines that the target virtual machine 221 basically uses the IPv4 address, and does not perform the destination address translation, Add a header.

Next, the second router 320 removes the LISP header to decapsulate (i.e., decapsulate) the packet (S613), and updates the destination address of the decapsulated header (i.e., the identifier of the target virtual machine) And transmits the packet to the second hypervisor 220 (S615). Then, the target virtual machine 221 of the second hypervisor 220 confirms the packet and performs an operation according to the packet.

7 is a flowchart illustrating a method of processing a control message in a router according to an embodiment of the present invention.

Referring to FIG. 7, routers 310, 320, and 330 receive control messages from other routers 310, 320, and 330 or hypervisors 210 and 220 (S701). That is, the routers 310, 320, and 330 receive the control message in which the number '6' is recorded in the Type field.

Then, the routers 310, 320, and 330 verify whether the control message is a valid message, and discard the control message if it is not a valid message.

On the other hand, if the control message is a valid message, the routers 310, 320, and 330 extract information recorded in each flag field of the control message (S703).

The routers 310, 320 and 330 check whether the flag field 'H' is '1' and the flag field 'O' is '1' (S705) It is determined that the migration of the virtual machine is completed in the hypervisor including the virtual machine 221. That is, information indicating that the control message has been transmitted from the hypervisor (i.e., '1') is recorded in the flag field 'H', and the control message is sent from the node related to the target virtual machine 221 providing IPv6 service (I.e., '1') is recorded in the flag field 'O', the routers 310, 320, and 330 determine that the migration of the virtual machine is completed in the hypervisor. The routers 310, 320, and 330 generate an IPv6 identifier used in the target virtual machine 221, write the IPv6 identifier into the new identifier field, and transmit the control message to the hypervisor including the target virtual machine (S707 ).

On the other hand, when the routers 310, 320 and 330 write '1' to the flag field 'H', '0' to the flag field '0', and '1' to the flag field 'S' It is determined that the hypervisor that sent the control message tries to migrate the virtual machine live (S709). That is, information indicating that the control message has been sent from the hypervisor (i.e., '1') is recorded in the flag field 'H', and a message is generated at the node associated with the source virtual machine 211 providing the IPv4 service (I.e., '0') is recorded in the flag field 'O' and information (ie, '1') indicating that the IPv6 identifier is used as the base address is recorded in the flag field 'S' 310, 320, and 330) determines that the hypervisor that sent the control message tries to perform a live migration of the virtual machine. Then, the routers 310, 320 and 330 transmit mapping information in which a dummy value is assigned to the IPv4 identifier, an identifier of the destination hypervisor in the IPv6 identifier, an IP address of the destination router in the locator, and '1' Stores it in the map cache, and transmits the dummy value to the hypervisor that has sent the control message (S711).

When the router 310, 320, and 330 have recorded '0' in the flag field 'H', '1' in the flag field S, and '1' in the flag field C ' It is determined that the control message is an instruction to update the caches 311, 321, and 331. That is, the routers 310, 320, and 330 indicate that the information indicating that the control message is not transmitted from the hypervisor (i.e., '0') is recorded in the flag field 'H' If the information (i.e., '1') is recorded in the flag field 'S' and the information meaning map cache update (ie, '1') is recorded in the flag field 'C' As shown in FIG. The routers 310, 320, and 330 check the IPv6 identifier included in the IPv4 identifier and the new identifier field recorded in the old identifier field of the control message, and the IPv4 identifier, IPv6 identifier, The mapping information of the map cache 311, 321, and 331 is updated by reflecting the mapping information set in the map cache 311, 321, and 331 (S715).

If the router 310, 320, or 330 has recorded '0' in the flag field 'H', '1' in the flag field S, and '0' It is determined that the control message is a command for deleting the mapping information associated with the virtual machine 211. In other words, the routers 310, 320, and 330 send information indicating that the control message is not sent from the hypervisor (i.e., '0') is recorded in the flag field 'H' (I.e., '1') is written in the flag field 'S' and information that does not require a map cache update (ie, '0') is written in the flag field 'C', the source virtual machine 211 Is a control message instructing deletion of the mapping information. The routers 310, 320, 330 check the IPv4 identifier in the old identifier field of the control message and check whether the mapping information having the IPv4 identifier is stored in the map DB 312, 322, 332 S719). If not, the corresponding control message is discarded (S727).

On the other hand, if mapping information having an IPv4 identifier is stored in the map DBs 312, 322, and 332, the routers 310, 320, and 330 delete the corresponding mapping information from the map DBs 312, 322, and 332 S721). Subsequently, the routers 310, 320, and 330 check the other routers that have communicated with the source virtual machine 211 in the map caches 311, 321, and 331, and map the changed mapping information to the other routers, (311, 321, 331) (S723). At this time, the routers 310, 320, and 330 write '0', '0', '1', and '1' to the flag fields 'O', 'H', 'S', and 'C' Writes the IPv4 identifier of the source virtual machine 211 into the old identifier field, and records the IPv6 identifier of the target virtual machine 221 in the new identifier field.

On the other hand, if it is determined in step S717 that the router 310, 320, and 330 have not recorded '0' in the 'H', '1' in the flag field S, and '0' It is determined that the flag information combination is recorded in the control message, and the control message is discarded (S727).

As described above, the LISP network system according to the present invention performs IPv4-IPv6 service switching through live migration of a virtual machine without adding additional equipment, thereby reducing the cost of switching the IPv4-IPv6 service do. In the LISP network system according to the present invention, the mapping information generated through the live migration of the virtual machine is immediately transmitted to the router and the mapping system, and the mapping information of the corresponding router and the mapping system is immediately updated, Minimize service interruptions that occur during the switchover.

While the specification contains many features, such features should not be construed as limiting the scope of the invention or the scope of the claims. In addition, the features described in the individual embodiments herein may be combined and implemented in a single embodiment. Conversely, various features described in the singular < Desc / Clms Page number 5 > embodiments herein may be implemented in various embodiments individually or in combination as appropriate.

Although the operations have been described in a particular order in the figures, it should be understood that such operations are performed in a particular order as shown, or that all described operations are performed to obtain a sequence of sequential orders, or a desired result . In certain circumstances, multitasking and parallel processing may be advantageous. It should also be understood that the division of various system components in the above embodiments does not require such distinction in all embodiments. The above-described program components and systems can generally be implemented as a single software product or as a package in multiple software products.

The method of the present invention as described above can be implemented by a program and stored in a computer-readable recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto optical disk, etc.). Such a process can be easily carried out by those skilled in the art and will not be described in detail.

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. The present invention is not limited to the drawings.

210: first hypervisor 211: source virtual machine
220: Second hypervisor 221: Target virtual machine
310: first router 311, 321, 331: map cache
312, 322, 332: map DB 320: second router
330 third router 400 client terminal
500: mapping system 600: integrated DB

Claims (18)

Locator ID Separation Protocol (LISP) As a method for switching services from IPv4 to IPv6 through migration of virtual machines in a network system,
Receiving a packet for migration of a source virtual machine included in a first hypervisor and migrating the source virtual machine to a target virtual machine;
Updating the map database by reflecting, in the map database, the mapping information that the second router managing the second hypervisor maps the IPv4 identifier of the source virtual machine and the IPv6 identifier assigned to the target virtual machine;
Transmitting, by the second router, an IPv4 identifier of the source virtual machine and an IPv6 identifier of the target virtual machine to a first router that is in charge of the first hypervisor; And
Wherein the first router identifies the router as one or more other routers communicating with the source virtual machine and transmits the IPv4 identifier of the source virtual machine and the IPv6 identifier of the target virtual machine to the one or more other routers, And updating the mapping information stored in the router. The method according to claim 1,
Wherein the migrating comprises:
The first router receiving a control message requesting migration from the first hypervisor; And
The first router receiving a packet including a memory dump of the source virtual machine from the first hypervisor and transmitting the packet through the second router to the second hypervisor A method for switching an IPv4-IPv6 service. 3. The method of claim 2,
Wherein the migrating comprises:
The first router storing mapping information in which the dummy value is set as the IPv4 identifier and the identifier of the second hypervisor as the IPv6 identifier is set in the map cache;
The first router sending the dummy value to the first hypervisor; And
The first router receives from the first hypervisor a packet including the memory dump and the dummy value set as the destination address, and changes the destination address of the received packet from the dummy value to the identifier of the second hypervisor And converting the IPv4-IPv6 service to the IPv4-IPv6 service. The method according to claim 2 or 3,
Wherein the receiving the control message comprises:
A flag indicating that the control message has been sent from the hypervisor, a flag indicating that the control message is generated at the node related to the source virtual machine providing the IPv4 service, and a flag indicating that the IPv6 identifier is used as the base address, Wherein the first router determines that the control message is a message for requesting migration. The method according to claim 1,
Wherein updating the map database comprises:
The second router receiving a control message indicating completion of migration from the second hypervisor; And
And the second router generates an IPv6 identifier of the target virtual machine and transmits the IPv6 identifier to the second hypervisor to assign the IP address of the target virtual machine to the IPv6 identifier A method for switching an IPv4-IPv6 service. 6. The method of claim 5,
Wherein the receiving the control message comprises:
A flag indicating that a control message has been sent by the hypervisor, and a flag indicating that the message is generated by a node providing IPv6 service, is recorded in the control message, the second router indicates completion of migration of the control message The method comprising the steps of: The method according to claim 1,
After transmitting the IPv6 identifier of the target virtual machine,
Further comprising the step of the first router deleting the old mapping information mapped with the IPv4 identifier of the source virtual machine. 8. The method of claim 7,
Wherein the step of deleting the old mapping information comprises:
A flag indicating that the first router receives the control message from the second router, a flag indicating that the control message is not dispatched from the hypervisor, a flag indicating that the IPv6 identifier is used as the base address, and a flag not requesting the map cache update Wherein the old mapping information mapped with the IPv4 identifier of the source virtual machine is deleted when the control message is recorded in the control message. The method according to claim 1,
Wherein the updating of the mapping information stored in the one or more other routers comprises:
The first router transmits a control message including a flag indicating that the control message is not sent from the hypervisor, a flag indicating that the IPv6 identifier is used as a base address, and a flag requesting a map cache update to the one or more other routers And updates the mapping information stored in the one or more other routers. The method according to claim 1,
After updating the mapping information stored in the one or more other routers,
And stopping the operation of the source virtual machine by the first hypervisor. LISP (Locator ID Separation Protocol) A LISP network system that converts services from IPv4 to IPv6 through migration of virtual machines in a network environment,
A first hypervisor including a source virtual machine performing an IPv4-based service;
A first router for routing the first hypervisor;
A second hypervisor for creating a target virtual machine, receiving a packet for migration of the source virtual machine, and migrating the source virtual machine to the target virtual machine; And
Updating the map database by reflecting the mapping information in which the IPv6 identifier allocated to the target virtual machine and the IPv4 identifier of the source virtual machine are mapped to the map database, And a second router for transmitting an IPv6 identifier of the target virtual machine and an IPv4 identifier of the source virtual machine,
Wherein the first router comprises:
And transmitting the IPv6 identifier of the target virtual machine and the IPv4 identifier of the source virtual machine to the one or more other routers to update the mapping information stored in the one or more other routers The LISP network system comprising: 12. The method of claim 11,
Wherein the first router comprises:
Receives a packet including a memory dump of the source virtual machine from the first hypervisor, and transmits the packet to the second hypervisor through the second router. 13. The method of claim 12,
Wherein the first router comprises:
Storing a mapping information in which a dummy value is set as an IPv4 identifier and an identifier of a second hypervisor as an IPv6 identifier is set in a map cache, and the dummy value is transmitted to the first hypervisor, When receiving a packet having the dummy value set from the first hypervisor, changing the destination address of the received packet from the dummy value to the identifier of the second hypervisor. 14. The method according to any one of claims 11 to 13,
The second router includes:
When the completion of the migration is notified from the second hypervisor, generating an IPv6 identifier of the target virtual machine, transmitting the IPv6 identifier to the second hypervisor, assigning the IP address of the target virtual machine to the IPv6 identifier The LISP network system comprising: 14. The method according to any one of claims 11 to 13,
Wherein the first router comprises:
Upon receipt of the IPv6 identifier of the target virtual machine and the IPv4 identifier of the source virtual machine from the second router, deletes the old mapping information mapped with the IPv4 identifier of the source virtual machine. 14. The method according to any one of claims 11 to 13,
Wherein the first hypervisor comprises:
And stops the operation of the source virtual machine when the updating of the mapping information is completed. A method for switching from IPv4 to IPv6 in a Locator ID Separation Protocol (LISP) network system,
The method comprising the steps of: a router receiving, from a client terminal, a packet in which a source virtual machine IPv4 identifier before migration is set to a destination address;
The router verifying the IPv6 identifier of the target virtual machine mapped with the IPv4 identifier in the mapping information being stored;
The router changing the destination address of the packet from the IPv4 identifier to the IPv6 identifier; And
And adding the LISP header to the packet having the changed destination address and transmitting the LISP header to the destination router. 18. The method of claim 17,
Wherein changing the IPv6 identifier comprises:
The router verifies whether a flag indicating that an IPv6 address is used as a base address is recorded among the mapping information mapped with the IPv4 identifier and if it is recorded, the router updates the destination address of the packet from the IPv4 identifier To the IPv6 identifier.

Images