Edge platform management apparatus, method of operating edge platform management apparatus, and edge gateway apparatus

Abstract

The present invention relates to an edge platform management apparatus, a method of operating an edge platform management apparatus, and an edge gateway apparatus, the edge platform management apparatus proposes an efficient linking method between a layer 2 (L2) based switch and a layer 3 (L3) based service processing gateway node in a mobile edge computing (MEC) environment.

Description

Technical Field

[0001] This disclosure relates to an efficient connection between a Layer 2 (L2) based switch and a Layer 3 (L3) based service processing gateway node in a mobile edge computing (MEC) environment.

[0002] This application claims priority to Korean Patent Application No. 10-2021-0099106, filed on July 28, 2021, with the Korean Intellectual Property Office, the full disclosure of which is incorporated herein by reference. Background Technology

[0003] Serverless computing is a service model where all elements except the application are provided by a cloud provider. In serverless computing services, in addition to the application, the physical infrastructure, virtual machines, containers, and integrated management areas are provided by the cloud provider, and users can manage the application.

[0004] Among the components mentioned above, containers are a much lighter virtualization technology than virtual machines (VMs) and can configure and operate all elements related to application execution in a single package.

[0005] Containers can be smaller than virtual machines, which reduces the time developers need to create and distribute containers and has the advantage of being able to restart quickly.

[0006] In mobile edge computing (MEC) environments that need to provide the various IT services and technologies already available in traditional cloud environments at the edge of mobile networks, it is also necessary to support the aforementioned virtual resources, including containers.

[0007] As required, in a mobile edge computing environment, a virtual network is established in the edge platform by connecting virtual machines, including Kubernetes-based containers (PODs), and customer-specific services are provided.

[0008] In this regard, in a mobile edge computing environment, a Layer 3 (L3) based service processing gateway node connects to a Layer 2 (L2) based switch (physical switch) in the edge platform to support Internet service processing for virtual machines.

[0009] However, since internet services are processed by connecting L2-based switches and L3-based service processing gateway nodes in mobile edge computing environments, there is a limitation that existing routing protocols cannot be applied when the routing path of internet services needs to be changed in the edge platform. Summary of the Invention

[0010] Technical issues

[0011] Therefore, this disclosure has been made in view of the above-mentioned problems, and one aspect of this disclosure is to propose an efficient connection between a Layer 2 (L2) based switch and a Layer 3 (L3) based service processing gateway node in a mobile edge computing (MEC) environment.

[0012] Solution to the problem

[0013] Therefore, the edge platform management apparatus according to the embodiments of the present disclosure is configured to include: an identification unit configured to identify an edge gateway device configured to process internet services for virtual machines (VMs) when a routing event occurs in the edge platform for internet service processing of virtual machines (VMs); and a management unit configured to transmit an event message to a switch in the edge platform configured to route internet services based on event messages through the edge gateway device, and update the routing table in the switch for routing operation management.

[0014] Specifically, routing events may include situations where a specific floating IP address is assigned to a first virtual machine to support internet service processing of the first virtual machine in the edge platform, or where a specific floating IP address already assigned to the first virtual machine is reassigned to a second virtual machine that is different from the first virtual machine.

[0015] Specifically, the management unit can be configured to map a specific floating IP address and the MAC address of a first virtual machine in the routing table via event messages, or to update the MAC address mapped to the specific floating IP address from the MAC address of the first virtual machine to the MAC address of the second virtual machine.

[0016] Specifically, routing events may include situations where an edge gateway device configured to handle Internet services for virtual machines changes from a first edge gateway device to a second edge gateway device that is different from the first edge gateway device.

[0017] Specifically, the management unit can be configured to transmit event messages through the second edge gateway device, and the edge gateway device configured to handle Internet services for virtual machines will be updated from the first edge gateway device to the second edge gateway device in the routing table.

[0018] Specifically, event messages may include gratuitous ARP (GARP) messages that can update information recorded in the routing table using the MAC address and IP address in the message fields.

[0019] Therefore, the edge gateway device according to the embodiments of the present disclosure is configured to transmit an event message to the switch based on the routing event received from the edge platform management device when a routing event occurs in Internet service processing of virtual machines (VMs) in the edge platform, and cause the switch to update the routing table for routing operation management based on the event message.

[0020] Specifically, routing events may include at least one of the following: a specific floating IP address is assigned to a first virtual machine to support Internet service processing of the first virtual machine in the edge platform; a specific floating IP address already assigned to the first virtual machine is reassigned to a second virtual machine different from the first virtual machine; and a device configured to process Internet services of virtual machines is changed from another edge gateway device to the edge gateway device.

[0021] Therefore, the operation method of the edge platform management device according to the embodiments of the present disclosure includes: an identification operation, in which an edge gateway device configured to process the Internet service of a virtual machine (VM) is identified when a routing event occurs in the edge platform regarding the processing of Internet services of a virtual machine (VM); and a management operation, in which the edge gateway device transmits an event message to a switch in the edge platform configured to route Internet services based on the routing event and updates the routing table in the switch for routing operation management based on the event message.

[0022] Specifically, routing events may include situations where a specific floating IP address is assigned to a first virtual machine to support internet service processing of the first virtual machine in the edge platform, or where a specific floating IP address already assigned to the first virtual machine is reassigned to a second virtual machine that is different from the first virtual machine.

[0023] Specifically, in management operations, a specific floating IP address and the MAC address of the first virtual machine are configured to be mapped in the routing table via event messages, or the MAC address mapped to the specific floating IP address is updated from the MAC address of the first virtual machine to the MAC address of the second virtual machine.

[0024] Specifically, routing events may include situations where an edge gateway device configured to handle Internet services for virtual machines changes from a first edge gateway device to a second edge gateway device that is different from the first edge gateway device.

[0025] Specifically, in management operations, event messages can be configured to be transmitted through a second edge gateway device, and the edge gateway device configured to handle the Internet services of virtual machines will be updated from the first edge gateway device to the second edge gateway device in the routing table.

[0026] Specifically, event messages may include gratuitous ARP (GARP) messages that can update information recorded in the routing table using the MAC address and IP address in the message fields.

[0027] Advantages of the present invention

[0028] The edge platform management device, the method of operating the edge platform management device, and the edge gateway device disclosed herein provide a novel approach to connect layer 2 (L2) based switches and layer 3 (L3) based service processing gateway nodes in a mobile edge computing (MEC) environment, and achieve the effect of effectively responding to changes in routing paths related to Internet service processing without applying existing L3-based routing protocols. Attached Figure Description

[0029] Figure 1 This is an example diagram illustrating a mobile edge computing environment according to an embodiment of the present disclosure;

[0030] Figure 2 This is a schematic diagram illustrating an edge platform management device according to an embodiment of the present disclosure;

[0031] Figure 3 This is an example diagram illustrating the structure of an edge platform according to an embodiment of the present disclosure;

[0032] Figures 4 to 6 This is an example diagram illustrating routing event scenarios according to embodiments of the present disclosure; and

[0033] Figure 7 This is a flowchart illustrating an operation method of an edge platform management device according to an embodiment of the present disclosure. Detailed Implementation

[0034] Hereinafter, preferred embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0035] Embodiments of this disclosure illustrate a mobile edge computing technology in which containers, as virtual resources, are installed on virtual machines (VMs) to provide customer-specific services based on them.

[0036] Mobile edge computing technology represents the concept of providing various IT services and technologies to the edge of mobile networks, and requires support as a container of virtual resources, as in existing cloud environments.

[0037] Here, containers are a much lighter virtualization technology than virtual machines (VMs), and all elements related to application execution can be configured and operated in a single package.

[0038] Containers can be smaller than virtual machines, which reduces the time developers need to create and distribute containers and has the advantage of being able to restart quickly.

[0039] In this regard, most current services consist of a Kubernetes-based microservice architecture, which refers to an open-source system for automatically distributing, scaling, and managing containerized applications, and Kubernetes support is also essential in the aforementioned mobile edge computing environments.

[0040] As required, in a mobile edge computing environment, a virtual network is established in the edge platform using an inter-VM connectivity structure including Kubernetes-based containers (PODs), and customer-specific services are provided based on this network.

[0041] Furthermore, in mobile edge computing environments, multiple Layer 3 (L3) based gateway nodes are provided, separate from the Layer 2 (L2) based switches (physical switches) in the edge platform, to process services and support Internet service processing for virtual machines, in conjunction with L2-based switches.

[0042] However, in mobile edge computing environments, due to the need for connections between L2-based switches and L3-based service processing gateway nodes, existing routing protocols cannot be applied as is to address the issue when the routing path for internet services in the edge platform changes.

[0043] Of course, existing L3-based routing protocols (such as BGP and OSPF) can be applied to the connection between L2-based switches and L3-based service processing gateway nodes.

[0044] However, due to the nature of gateway nodes running as software on servers, the software must be purchased separately, which may lead to additional issues such as software maintenance and management.

[0045] In this regard, the embodiments of this disclosure present a new method for establishing an efficient connection between an L2-based switch and an L3-based service processing gateway node in a mobile edge computing environment.

[0046] Figure 1 A mobile edge computing environment according to an embodiment of the present disclosure is shown.

[0047] like Figure 1 As shown, in a mobile edge computing environment according to an embodiment of the present disclosure, there may be a configuration including: an edge platform management device 100 configured to manage a virtual network in an edge platform configured to have an inter-VM connectivity structure; and an edge gateway device 200 configured to support Internet service processing related to virtual machines.

[0048] Edge platform management device 100 refers to a device configured to generate and control virtual networks by using an inter-VM connectivity structure including PODs, and may include, for example, a software-defined networking controller (SDN controller).

[0049] Edge gateway device 200 represents an L3-based service processing gateway node provided to deliver Internet services between a virtual network and the Internet when an Internet connection for a VM is required, and may be configured to run in a server-based software-based manner.

[0050] In an edge platform according to an embodiment of the present disclosure, an internal network configured to support communication between virtual machines connected to a virtual LAN can be generated in such a way that virtual machines are connected to each other via a virtual LAN.

[0051] According to embodiments of the present disclosure, the edge platform can be configured to support communication between internal networks connected to a virtual router in a manner that interconnects virtual LANs constituting the internal network via a virtual router.

[0052] Furthermore, the edge platform according to embodiments of this disclosure can be configured to support external network connections to a virtual router via L2-based switch routing, and then extend the virtual machine's communication area for Internet connectivity via the edge gateway device 200 to be supported.

[0053] The above describes a method for establishing an effective connection between an L2-based switch configured as described above and an edge gateway device 200 serving as an L3-based service processing gateway node in a mobile edge computing environment, according to embodiments of the present disclosure. The configuration of the edge platform management device 100 implementing this method will be described in more detail below.

[0054] Figure 2 A schematic configuration of an edge platform management device 100 according to an embodiment of the present disclosure is shown.

[0055] like Figure 2 As shown, the edge platform management device 100 according to an embodiment of the present disclosure may be configured to include: an identification unit 110 configured to identify an edge gateway device 200 configured to process Internet services of virtual machines based on the occurrence of a routing event; and a management unit 120 configured to update the routing table of the switch in the edge platform.

[0056] The entire configuration or part of the configuration of the edge platform management device 100, which is configured to include the identification unit 110 and the management unit 120, can be implemented in a hardware module or a software module, or in the form of a combination of hardware modules and software modules.

[0057] For example, a software module can be interpreted as instructions executed by a processor configured to handle operations within the edge platform management device 100, and the instructions can be configured to have a separate memory installed in the edge platform management device 100.

[0058] The edge platform management device 100 according to an embodiment of the present disclosure can be configured to provide a method for effective connection between an L2-based switch in an edge platform and an edge gateway device 200, which serves as an L3-based service processing gateway, through the above configuration. Hereinafter, a more detailed description of the configuration in the edge platform management device 100 implementing this method will continue.

[0059] The identification unit 110 is configured to perform the function of identifying the edge gateway device 200, which is configured to process Internet services for virtual machines.

[0060] More specifically, when a routing event occurs in the edge platform, the identification unit 110 can be configured to identify the edge gateway device 200 responsible for processing the Internet services of the corresponding virtual machine.

[0061] Since virtual machines are configured to operate as servers, much of the traffic on edge platforms comes from inbound packets accessing virtual machines from outside.

[0062] Therefore, a public IP address within the public IP band included in the external network can be assigned as a floating IP address to a virtual machine on the edge platform.

[0063] Here, when inbound packets are introduced, the edge gateway device 200 can be configured to perform the operation of converting the floating IP address configured as the destination address of the inbound packet into the private IP address of a virtual machine configured to have a mapping relationship with that address and transmitting the private IP address.

[0064] In one embodiment of this disclosure, the routing event scenarios that may be considered relate to the Internet service processing of virtual machines and may be configured to include, for example, assigning or reassigning floating IP addresses for Internet service processing support to virtual machines, or being configured to change the edge gateway device 200 that supports Internet service processing of virtual machines.

[0065] In this regard, such as Figure 3 As shown, in an edge platform according to an embodiment of the present disclosure, a virtual router may be configured to exist to support communication between a first virtual machine VM#1 and a second virtual machine VM#2 and an internal network configured to include the first virtual machine and the second virtual machine, and a first edge gateway device LEG#1 and a second edge gateway device LEG#2 may be configured to exist to support Internet service processing of the first virtual machine VM#1 and the second virtual machine VM#2.

[0066] Here, it can be identified as follows: Figure 4 The specific floating IP address (233.39.6.3) shown is assigned to the first virtual machine VM#1 to support the Internet service processing of the first virtual machine VM#1 in the edge platform, or as... Figure 5 The example shown illustrates a routing event where a specific floating IP address (233.39.6.3) pre-assigned to a first virtual machine VM#1 is reassigned to a second virtual machine VM#2, which is different from the first virtual machine VM#1.

[0067] Here, the first edge gateway device LEG#1 can be configured as an edge gateway device 200 that is identified as being configured to handle Internet services for the first virtual machine VM#1 and the second virtual machine VM#2.

[0068] In addition, such as Figure 6 As shown, the situation where the edge gateway device 200, which is configured to support Internet service processing of the first virtual machine VM#1, changes from the first edge gateway device LEG#1 to the second edge gateway device LEG#2 due to a fault or other reasons can also be identified as a routing event.

[0069] In this scenario, the second edge gateway device LEG#2 can be configured to be identified as an edge gateway device 200 configured to handle Internet services of the first virtual machine VM#1.

[0070] Management Unit 120 is configured to perform the function of updating the routing tables of switches in the edge platform.

[0071] More specifically, when an edge gateway device 200 configured to handle Internet services for virtual machines is identified based on a routing event occurring in the edge platform, the management unit 120 is configured to transmit an event message to the switch in the edge platform based on the identified edge gateway device 200 according to the routing event, and update the routing table L2 table managed by the switch for routing Internet services based on the event message.

[0072] Here, the management unit 120 can be configured to send gratuitous ARP (GARP) messages to switches in the edge platform that update information recorded in the message with MAC address and IP address in the message field, as event messages for updating the routing table L2 table managed by the switch.

[0073] To better understand, the process of updating the routing table L2 based on the type of routing event will be described in detail below.

[0074] As above Figure 4As shown, assume a specific floating IP address (233.39.6.3) is assigned to the first virtual machine VM#1 to support the routing event scenario of Internet service processing of the first virtual machine VM#1 in the edge platform.

[0075] When the first edge gateway device LEG#1 is identified for Internet service processing of the first virtual machine VM#1, by transmitting the corresponding event message to the switch (physical switch) via the first edge gateway device LEG#1, the switch (physical switch) can map a specific IP address (233.39.6.3) and the MAC address of the first virtual machine VM#1 in its managed routing table L2 table.

[0076] In addition, as mentioned above Figure 5 As shown, it can be assumed that a specific floating IP address (233.39.6.3) pre-assigned to a first virtual machine VM#1 in the edge platform is reassigned to a second virtual machine VM#2, which is different from the first virtual machine VM#1, in a routing event scenario.

[0077] When the second edge gateway device LEG#1 is identified for Internet service processing of the second virtual machine VM#2, by transmitting the corresponding event message to the switch (physical switch) via the first edge gateway device LEG#1, the switch (physical switch) can update the MAC address mapped to the specific floating IP address (233.39.6.3) in its managed routing table L2 from the MAC address of the first virtual machine VM#1 to the MAC address of the second virtual machine VM#2.

[0078] It can be assumed that the routing event for a specific floating IP address (233.39.6.3) previously assigned to the first virtual machine VM#1 in the edge platform is reassigned to a second virtual machine VM#2, which is different from the first virtual machine VM#1, does not send an event message to the switch (physical switch).

[0079] In this scenario, since the MAC address mapped to the specific floating IP address (233.39.6.3) is still considered the MAC address of the first virtual machine VM#1 in the switch (physical switch), it is predictable that packet dropping will occur, and then the Internet service of the second virtual machine VM#2 can only be processed normally after the timer (ARP timer) of the switch (physical switch) itself deletes the existing information in the routing table.

[0080] In addition, as mentioned above Figure 6 As shown, it can also be assumed that the edge gateway device 200, which is configured to support Internet service processing of the first virtual machine VM#1, changes from the first edge gateway device LEG#1 to the second edge gateway device LEG#2 due to a fault or other event.

[0081] Here, by transmitting the corresponding event message to the switch (physical switch) via the second edge gateway device LEG#2, the switch (physical switch) can update the edge gateway device 200, which is configured to support Internet service processing for the first virtual machine VM#1 and the second virtual machine #2 in the routing table L2 it manages, from the first edge gateway device LEG#1 to the second edge gateway device LEG#2.

[0082] As described above, based on the configuration of the edge platform management device 100 according to the embodiments of this disclosure, a new connection method can be proposed to use event messages (GARP messages) to connect between an L2-based switch and an edge gateway device 200 as an L3-based service processing gateway node in a mobile edge computing (MEC) environment. It can be seen that it can effectively respond to changes in routing paths related to Internet service processing without applying existing L3-based routing protocols.

[0083] The following will refer to Figure 7 The operation method of the edge platform management device 100 according to an embodiment of the present disclosure is described.

[0084] First, when a routing event occurs in the edge platform, the identification unit 110 can be configured to identify the edge gateway device 200 (S110-S120) responsible for processing the Internet services of the corresponding virtual machine.

[0085] The identification unit 110 can be configured to identify situations related to Internet service processing of virtual machines (e.g., assigning or reassigning a floating IP address for Internet service processing support to a virtual machine or changing the edge gateway device 200 configured to support Internet service processing of virtual machines) as routing events.

[0086] In this regard, as mentioned above Figure 3 As shown, in an edge platform according to an embodiment of the present disclosure, a virtual router may be configured to exist to support communication between a first virtual machine VM#1 and a second virtual machine VM#2 and an internal network configured to include the first virtual machine and the second virtual machine, and a first edge gateway device LEG#1 and a second edge gateway device LEG#2 may be configured to exist to support Internet service processing of the first virtual machine VM#1 and the second virtual machine VM#2.

[0087] Can be identified as above Figure 4 The specific floating IP address (233.39.6.3) shown is assigned to the first virtual machine VM#1 to support the Internet service processing of the first virtual machine VM#1 in the edge platform, or as above. Figure 5The diagram shows a routing event where a specific floating IP address (233.39.6.3) previously assigned to the first virtual machine VM#1 is reassigned to a second virtual machine VM#2, which is different from the first virtual machine VM#1.

[0088] Here, the first edge gateway device LEG#1 can be configured as an edge gateway device 200 that is identified as being configured to handle Internet services for the first virtual machine VM#1 and the second virtual machine VM#2.

[0089] In addition, as mentioned above Figure 6 As shown, the situation where the edge gateway device 200, which is configured to support Internet service processing of the first virtual machine VM#1, changes from the first edge gateway device LEG#1 to the second edge gateway device LEG#2 due to a fault or other reasons can also be identified as a routing event.

[0090] In this scenario, the second edge gateway device LEG#2 can be configured to be identified as an edge gateway device 200 configured to handle Internet services of the first virtual machine VM#1.

[0091] Subsequently, when an edge gateway device 200 configured to handle Internet services for virtual machines is identified based on a routing event occurring in the edge platform, the management unit 120 is configured to transmit an event message to the switch in the edge platform based on the routing event through the identified edge gateway device 200, and update the routing table L2 table managed by the switch for routing Internet services based on the event message.

[0092] Here, the management unit 120 can be configured to send gratuitous ARP (GARP) messages to switches in the edge platform that update information recorded in the message with MAC address and IP address in the message field, as event messages for updating the routing table L2 table managed by the switch.

[0093] To better understand, the process of updating the routing table L2 based on the type of routing event will be described in detail below.

[0094] The routing event scenario above refers to the allocation of a specific floating IP address (233.39.6.3) to the first virtual machine VM#1 to support the Internet service processing of the first virtual machine VM#1 in the edge platform. Figure 4 As shown, it can be assumed that the first edge gateway device LEG#1 is identified for Internet service processing of the first virtual machine VM#1.

[0095] In this scenario, by transmitting the corresponding event message to the switch (physical switch) via the first edge gateway device LEG#1, the switch (physical switch) can map a specific floating IP address (233.39.6.3) and the MAC address of the first virtual machine VM#1 within its managed routing table L2.

[0096] Furthermore, we can assume the above... Figure 5 The example shown illustrates a routing event where a specific floating IP address (233.39.6.3) previously assigned to the first virtual machine VM#1 in the edge platform is reassigned to a second virtual machine VM#2, which is different from the first virtual machine VM#1.

[0097] Here, when the second edge gateway device LEG#1 is identified for Internet service processing of the second virtual machine VM#2, the corresponding event message can be configured to be transmitted to the switch (physical switch) through the first edge gateway device LEG#1, thereby enabling the switch (physical switch) to update the MAC address mapped to the specific floating IP address (233.39.6.3) in the managed routing table L2 from the MAC address of the first virtual machine VM#1 to the MAC address of the second virtual machine VM#2.

[0098] It can be assumed that the routing event for a specific floating IP address (233.39.6.3) previously assigned to the first virtual machine VM#1 in the edge platform is reassigned to a second virtual machine VM#2, which is different from the first virtual machine VM#1, does not send an event message to the switch (physical switch).

[0099] In this scenario, since the MAC address mapped to the specific floating IP address (233.39.6.3) is still considered the MAC address of the first virtual machine VM#1 in the switch (physical switch), it is predictable that packet dropping will occur, and then the Internet service of the second virtual machine VM#2 can only be processed normally after the timer (ARP timer) of the switch (physical switch) itself deletes the existing information in the routing table.

[0100] In addition, as mentioned above Figure 6 As shown, it can also be assumed that the edge gateway device 200, which is configured to support Internet service processing of the first virtual machine VM#1, changes from the first edge gateway device LEG#1 to the second edge gateway device LEG#2 due to a fault or other event.

[0101] Here, by sending a corresponding event message to the switch (physical switch) via the second edge gateway device LEG#2 in response to this situation, the switch (physical switch) can update the edge gateway device 200, which is configured to support Internet service processing for the first virtual machine VM#1 and the second virtual machine VM#2 in the routing table L2 it manages, from the first edge gateway device LEG#1 to the second edge gateway device LEG#2.

[0102] As described above, based on the operation method of the edge platform management device 100 according to the embodiments of the present disclosure, a new connection method can be proposed to use event messages (GARP messages) to connect between an L2-based switch and an edge gateway device 200 as an L3-based service processing gateway node in a mobile edge computing (MEC) environment. It can also be seen that it can effectively respond to changes in routing paths related to Internet service processing without applying existing L3-based routing protocols.

[0103] The operation method of the edge platform management device 100 according to embodiments of the present disclosure can be implemented in the form of program commands, which can be configured to be executed by various computer means and recorded on a computer-readable medium. The computer-readable medium may include program commands, data files, data structures, etc. (alone or in combination). The program commands recorded on the medium may be specifically designed and configured for the present disclosure, or may be known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical media such as CD-ROMs and DVDs; magneto-optical media such as floppy disks; and hardware devices such as ROMs, RAMs, and flash memory specifically configured to store and execute program commands. Examples of program commands include high-level language code executable by a computer using an interpreter and machine language code generated by a compiler. The aforementioned hardware devices may be configured to function as one or more software modules to perform the operations of the present disclosure, and vice versa.

[0104] Although the present disclosure has been described in detail with reference to preferred embodiments, the present disclosure is not limited to the above embodiments. The technical concept of the present disclosure is extended to the extent that various changes or modifications can be made by those skilled in the art to which the present disclosure pertains without departing from the spirit of the present disclosure as claimed in the following claims.

Claims

1. An edge platform management device, the edge platform management device comprising: An identification unit is configured to identify an edge gateway device for processing internet services of a virtual machine (VM) when a routing event occurs in the edge platform for internet service processing of the VM. as well as The management unit is configured to transmit event messages via the edge gateway device to the switches in the edge platform used for routing Internet services, thereby updating the routing tables of the switches for routing operations based on the event messages. The switch is a Layer 2 (L2) based switch, and the routing table is an L2 table. The edge gateway device is a Layer 3 (L3) based edge gateway device.

2. The edge platform management device according to claim 1, wherein, The routing events include events where a specific floating IP address is assigned to a first virtual machine to support Internet service processing of the first virtual machine in the edge platform, or events where the specific floating IP address assigned to the first virtual machine is reassigned to a second virtual machine.

3. The edge platform management device according to claim 2, wherein, The management unit is configured to map the specific floating IP address and the MAC address of the first virtual machine in the routing table based on the event message, or to update the MAC address mapped to the specific floating IP address from the MAC address of the first virtual machine to the MAC address of the second virtual machine.

4. The edge platform management device according to claim 1, wherein, The routing events include events where the edge gateway device used to process the Internet services of the virtual machine changes from a first edge gateway device to a second edge gateway device.

5. The edge platform management device according to claim 4, wherein, The management unit is configured to transmit the event message through the second edge gateway device to update the edge gateway device used to process the Internet services of the virtual machine from the first edge gateway device to the second edge gateway device in the routing table.

6. The edge platform management device according to claim 1, wherein, The event messages include gratuitous ARP / GARP messages that update information in the routing table using the MAC address and IP address in the message fields.

7. An edge gateway device configured to, when a routing event occurs in Internet service processing concerning a virtual machine (VM) on an edge platform, transmit an event message to a switch based on the routing event received from an edge platform management device, and cause the switch to update its routing table for routing operation management based on the event message. in, The switch is a Layer 2 (L2) based switch and the routing table is an L2 table. The edge gateway device is a Layer 3 (L3) based edge gateway device.

8. The edge gateway device according to claim 7, wherein, The routing events include at least one of the following: a specific floating IP address is assigned to a first virtual machine to support Internet service processing of the first virtual machine in the edge platform, or the specific floating IP address assigned to the first virtual machine is reassigned to a second virtual machine, and the device for processing the Internet service of the virtual machine is changed from another edge gateway device to the edge gateway device.

9. An operation method for an edge platform management device, the operation method comprising the following steps: When a routing event occurs in the edge platform for Internet service processing of a virtual machine (VM), the edge gateway device used to process the Internet service of the VM is identified. as well as The edge gateway device transmits event messages to the switches in the edge platform used for routing Internet services based on the routing events, thereby updating the routing tables of the switches used for routing operations based on the event messages. The switch is a Layer 2 (L2) based switch, and the routing table is an L2 table. The edge gateway device is a Layer 3 (L3) based edge gateway device.

10. The operating method according to claim 9, wherein, The routing events include events where a specific floating IP address is assigned to a first virtual machine to support Internet service processing of the first virtual machine in the edge platform, or events where the specific floating IP address assigned to the first virtual machine is reassigned to a second virtual machine.

11. The operating method according to claim 10, wherein, In management operations, based on the event message, the specific floating IP address and the MAC address of the first virtual machine are mapped in the routing table, or the MAC address mapped to the specific floating IP address is updated from the MAC address of the first virtual machine to the MAC address of the second virtual machine.

12. The operating method according to claim 9, wherein, The routing events include events in which the edge gateway device used to process the Internet services of the virtual machine changes from a first edge gateway device to a second edge gateway device that is different from the first edge gateway device.

13. The operating method according to claim 12, wherein, The steps for transmitting the event message include the following: The event message is transmitted via the second edge gateway device to update the edge gateway device used to process the Internet services of the virtual machine from the first edge gateway device to the second edge gateway device in the routing table.

14. The operating method according to claim 9, wherein, The event messages include gratuitous ARP / GARP messages that update information in the routing table using the MAC address and IP address in the message fields.

15. A computer-readable storage medium storing program commands that, when executed by a processor, cause the processor to perform the operating method according to any one of claims 9 to 14.

Images