Business data migration method and device, electronic equipment and readable storage medium

Abstract

The embodiment of the invention discloses a service data migration method and device, electronic equipment and a medium, relates to the technical field of cloud data networks, and solves the problem of high complexity of service migration. Comprising the steps that a migration management node receives a service migration mode and sends a first event announcement to a subscription management node, the first event announcement indicates execution of an on-demand deletion event, the first event announcement carries to-be-migrated resource information, and the to-be-migrated resource information comprises a VPC identifier or a tenant identifier corresponding to service data of a to-be-migrated service; the migration management node sends a second event announcement to the subscription management node, the second event announcement indicates the execution of the on-demand creation event, and the second event announcement carries the to-be-migrated resource information; the service migration command is used for requesting to migrate the configuration information of the service data of the to-be-migrated service from the first network device to the second network device, the on-demand deletion event is used for deleting the configuration information of the first network device, and the on-demand creation event is used for creating the configuration information in the second network device.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of cloud data networks, and in particular, to a method, device, electronic device, and readable storage medium for migrating service data. Background Art

[0002] With the continuous popularization of public cloud data centers, users will gradually migrate the services of local data centers to public clouds. In mobile public clouds, for projects such as clairvoyance and home security, as the business expands, large-bandwidth SDN (Software Defined Network) firewalls and dedicated NAT (Network Address Translation) gateways are required. It is necessary to support tenants to bind to exclusive large-scale firewalls and dedicated NAT gateways. Therefore, it is necessary for the public cloud to support the migration of tenant existing services without the user having to delete and rebuild the services, while ensuring that the tenant existing services are not affected. Summary of the Invention

[0003] The embodiments of the present application provide a method, device, electronic device, and readable storage medium for migrating service data, which can solve the problems that the migration process of device configuration of services is complex and time-consuming.

[0004] To achieve the above object, the embodiments of the present application adopt the following technical solutions:

[0005] In a first aspect of the embodiments of the present application, a method for migrating service data is provided, including: when receiving a service migration command, a migration management node sends a first event notification to a subscription management node, where the first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries information of resources to be migrated, and the information of resources to be migrated includes a VPC identifier or a tenant identifier corresponding to service data of a service to be migrated on a first network device; and the migration management node sends a second event notification to the subscription management node, where the second event notification is used to indicate the execution of an on-demand creation event, and the second event notification carries the information of resources to be migrated; the service migration command is used to request to migrate the configuration information of the service data of the service to be migrated to a second network device; where the service migration command is used to request to migrate the configuration information of the service data of the service to be migrated from the first network device to the second network device, the above on-demand deletion event is used to delete the configuration information of the service data on the first network device, and the above on-demand creation event is used to create the configuration information of the service data on the second network device.

[0006] The service data migration method provided by the embodiments of this application. When the migration management node receives a service migration command, it sends a first event notification to the subscription management node. This first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries the information of the resources to be migrated. The information of the resources to be migrated includes the VPC identification information corresponding to the service data of the service to be migrated on the first network device. The migration management node can send a second event notification to the subscription management node. This second event notification is used to indicate the execution of an on-demand creation event, and the second event notification carries the information of the resources to be migrated. Among them, the above service migration command is used to request to migrate the configuration information of the service data of the service to be migrated to the second network device. Through this method, when it is necessary to migrate the configuration information of the service data of a tenant, the migration management node can send an event notification to the subscription management node to indicate the execution of an on-demand deletion event or an on-demand creation event, so as to realize the smooth migration of the tenant service through the "on-demand distribution" logic, thereby realizing the migration of the service configuration on the network device, reducing the complexity of the system, and improving the data migration speed.

[0007] In a possible implementation manner in combination with the first aspect, the above first network device is the first firewall device, the information of the resources to be migrated includes the VPC identification corresponding to the service data of the service to be migrated on the first network device, and the VPC identification is used to indicate a VPC.

[0008] The service data migration method provided by the embodiments of this application. The migration management node can send the VPC identification corresponding to the service data of the service to be migrated to the subscription management node, so as to realize the migration of the configuration information of the service data of the VPC indicated by the VPC identification from the first firewall device to other devices, thereby realizing the migration of the configuration information at the VPC granularity.

[0009] In another possible implementation manner in combination with the first aspect and the above possible implementation manner, the first network device is the first NAT gateway device, the information of the resources to be migrated includes the tenant identification corresponding to the service data of the service to be migrated, and the tenant identification is used to indicate the first tenant, and the first tenant corresponds to at least one VPC.

[0010] The service data migration method provided by the embodiments of this application. The migration management node can send the tenant identification corresponding to the service data of the service to be migrated to the subscription management node, so as to realize the migration of the configuration information of the service data of at least one VPC corresponding to the tenant indicated by the tenant identification from the first NAT gateway device to other devices, thereby realizing the migration of the configuration information at the tenant granularity.

[0011] Combined with the first aspect and the above possible implementation manners, in another possible implementation manner, the migration management node establishes and saves the binding relationship between the first VPC and the second network device; wherein, the first VPC is the VPC indicated by the VPC identifier, or the first VPC is at least one VPC corresponding to the first tenant, and the first tenant is the tenant indicated by the tenant identifier.

[0012] For the service data migration method provided by the embodiments of the present application, the migration management node can establish and save the binding relationship between the first VPC and the second network device to which the configuration information needs to be migrated, so that the configuration information can be migrated to the second network device through this binding relationship subsequently, thereby realizing the rapid migration of service configuration information.

[0013] In a second aspect of the embodiments of the present application, a service data migration method is provided, including: the subscription management node receives a first event notification from the migration management node, the first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries the information of the resource to be migrated, and the information of the resource to be migrated includes the VPC identifier or tenant identifier corresponding to the service data of the service to be migrated on the first network device; the subscription management node receives a second event notification from the migration management node, the second event notification is used to indicate the execution of an on-demand creation event, and the second event notification carries the information of the resource to be migrated; wherein, the on-demand deletion event is used to delete the configuration information of the service data on the first network device, and the on-demand creation event is used to create the configuration information of the service data on the second network device.

[0014] For the service data migration method provided by the embodiments of the present application, the subscription management node can receive the event notifications of the on-demand deletion event and the on-demand creation event from the migration management node, and the event notifications carry the VPC identifier or tenant identifier corresponding to the service data of the service to be migrated, so that the service configuration of various services on network devices of different source device types can be migrated based on the event notifications, reducing the complexity of the system and improving the data migration speed.

[0015] In combination with the second aspect, in a possible implementation, before the subscription management node receives the first event notification from the migration management node, the service data migration method further includes: the subscription management node receives a subscription request message from a service component, where the subscription request message is used to request subscriptions for on-demand deletion events and on-demand creation events, and the subscription request message includes first function information of a first event processing function and second function information of a second event processing function. The first function information is used to indicate the first event processing function, the first event processing function is used to execute the on-demand deletion event, the second function information is used to indicate the second event processing function, and the second event processing function is used to execute the on-demand creation event; an association relationship between the on-demand deletion event and the first function information is established, and an association relationship between the on-demand creation event and the second function information is established.

[0016] For the service data migration method provided by the embodiments of the present application, the subscription management node can receive a subscription request message from a service component and establish an association relationship between the function information of the service component and an event based on the function information of the event processing function provided by the service component in the subscription request message, so as to implement subscribing to on-demand deletion events and on-demand creation events for the service component, and thus be able to, after receiving the event notification, call the corresponding function according to the function information associated with the event indicated by the event notification to execute the event, thereby implementing the rapid migration of service configurations of various services on the network device.

[0017] In combination with the second aspect and the above possible implementation, in another possible implementation, before the subscription management node establishes an association relationship between the on-demand deletion event and the first function information and an association relationship between the on-demand creation event and the second function information, the subscription management node creates the on-demand deletion event and the on-demand creation event.

[0018] For the service data migration method provided by the embodiments of the present application, the subscription management node can create unified on-demand creation events and on-demand deletion events, and establish association relationships between the on-demand creation events and the on-demand deletion events and the corresponding functions respectively, so as to implement the rapid migration of tenant services through the "on-demand deletion" and "on-demand creation" logics.

[0019] In combination with the second aspect and the above possible implementation, in another possible implementation, after the subscription management node receives the first event notification from the migration management node, it calls back the first event processing function corresponding to the on-demand deletion event to query the service data of the services to be migrated of the service component, and deletes the configuration information of the service data of the services to be migrated on the first network device.

[0020] In the business data migration method provided by the embodiment of the present application, the subscription management node can call back the event handling function corresponding to the on-demand deletion event notification to query the business data of the business to be migrated of the business component, and delete the configuration information of the business data on the source device, so as to be able to quickly delete the configuration of the business data based on the "on-demand deletion" logic.

[0021] Combined with the second aspect and the above possible implementation manners, in another possible implementation manner, after receiving the second event notification from the migration management node, the subscription management node calls back the second event handling function corresponding to the on-demand creation event to query the business data of the business to be migrated of the business component, and sends the configuration information of the business data of the business to be migrated to the second network device according to the binding relationship between the first VPC and the second network device; wherein, the above first VPC is the VPC indicated by the VPC identifier, or the above first VPC is at least one VPC corresponding to the first tenant, and the above first tenant is the tenant indicated by the tenant identifier.

[0022] In the business data migration method provided by the embodiment of the present application, the subscription management node can call back the event handling function corresponding to the on-demand creation event notification, and send the configuration information of the business data on the first VPC to the second network device according to the binding relationship between the first VPC corresponding to the business to be migrated and the second network device, so as to be able to quickly migrate the configuration of the business data based on the "on-demand creation" logic.

[0023] In the third aspect of the embodiment of the present application, a business data migration method is provided, including: a business component sends a subscription request message to a subscription management node; wherein, the above subscription request message is used to request to subscribe to the on-demand deletion event and the on-demand creation event, and the above subscription request message includes the first function information of the first event handling function and the second function information of the second event handling function; the above first function information is used to indicate the first event handling function, and the first event handling function is used to execute the on-demand deletion event, and the above second function information is used to indicate the second event handling function, and the second event handling function is used to execute the on-demand creation event.

[0024] In the business data migration method provided by the embodiment of the present application, the business component can send a subscription request message to the subscription management node to request to subscribe to the on-demand deletion event and the on-demand creation event. In this way, the business component can subscribe to the on-demand deletion event and the on-demand creation event, and provide the function information of the corresponding event handling function, so as to implement the migration of the business configuration based on the on-demand deletion event and the on-demand creation event, thereby being able to implement the migration of the business configuration on the network device, reduce the complexity of the system, and improve the data migration speed.

[0025] In the fourth aspect of the embodiments of the present application, a service data migration device is provided for executing the service data migration method described in the first aspect. The service data migration device includes: a sending module; the sending module is configured to send a first event notification to a subscription management node when receiving a service migration command. The first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries information about resources to be migrated. The information about resources to be migrated includes a VPC identifier or a tenant identifier corresponding to the service data of the service to be migrated; and, the sending module is further configured to send a second event notification to the subscription management node. The second event notification is used to indicate the execution of an on-demand creation event, and the second event notification carries information about resources to be migrated; wherein, the service migration command is used to request to migrate the configuration information of the service data of the service to be migrated from a first network device to a second network device. The on-demand deletion event is used to delete the configuration information of the service data on the first network device, and the on-demand creation event is used to create the configuration information of the service data on the second network device.

[0026] For the service data migration device provided in the embodiments of the present application, when it is necessary to migrate the configuration information of the service data of a tenant, the service data migration device can send an event notification to the subscription management node to indicate the execution of an on-demand deletion event or an on-demand creation event, and realize the smooth migration of the tenant service through the "on-demand distribution" logic, so as to be able to achieve the rapid migration of the service configuration on the network device, reduce the complexity of the system, and improve the data migration speed.

[0027] In combination with the fourth aspect, in a possible implementation manner, the first network device is a first firewall device, the information about resources to be migrated includes the VPC identifier corresponding to the service data of the service to be migrated on the first network device, and the VPC identifier is used to indicate a VPC.

[0028] In combination with the fourth aspect, in another possible implementation manner, the first network device is a first NAT gateway device, the information about resources to be migrated includes the tenant identifier corresponding to the service data of the service to be migrated, the tenant identifier is used to indicate a first tenant, and the first tenant corresponds to at least one VPC.

[0029] In combination with the fourth aspect, in another possible implementation manner, the device further includes: an execution module; the execution module is configured to establish and save the binding relationship between the first VPC and the second network device; wherein, the first VPC is the VPC indicated by the VPC identifier, or the first VPC is at least one VPC corresponding to the first tenant, and the first tenant is the tenant indicated by the tenant identifier.

[0030] In the fifth aspect of the embodiments of the present application, a service data migration device is provided for performing the service data migration method described in the second aspect. The device includes: a receiving module; the above-mentioned receiving module is used to receive a first event notification from a migration management node, the first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries information about resources to be migrated. The information about resources to be migrated includes a VPC identifier or a tenant identifier corresponding to the service data of the service to be migrated; the receiving module is further used to receive a second event notification from the migration management node, the second event notification is used to indicate the execution of an on-demand creation event, and the second event notification carries the above-mentioned information about resources to be migrated; wherein, the on-demand deletion event is used to delete the configuration information of the service data on the first network device, and the on-demand creation event is used to create the configuration information of the service data on the second network device.

[0031] The service data migration device provided by the embodiments of the present application can receive event notifications of an on-demand deletion event and an on-demand creation event from a migration management node. The event notifications carry a VPC identifier or a tenant identifier corresponding to the service data of the service to be migrated, so that the service configuration of various services on network devices of different source device types can be migrated based on the event notifications, reducing the complexity of the system and improving the data migration speed.

[0032] In combination with the fifth aspect, in a possible implementation manner, before the receiving module is further used to receive a first event notification from the migration management node, it is used to receive a subscription request message from a service component. The subscription request message is used to request subscription to an on-demand deletion event and an on-demand creation event. The subscription request message includes first function information of a first event processing function and second function information of a second event processing function. The first function information is used to indicate the first event processing function, and the first event processing function is used to execute the on-demand deletion event. The second function information is used to indicate the second event processing function, and the second event processing function is used to execute the on-demand creation event; the device further includes: an execution module; the execution module is used to establish an association relationship between the on-demand deletion event and the first function information, and establish an association relationship between the on-demand creation event and the second function information.

[0033] In combination with the fifth aspect and the above possible implementation manner, in another possible implementation manner, before the execution module is further used to establish an association relationship between the on-demand deletion event and the first function information, and establish an association relationship between the on-demand creation event and the second function information, it is used to create the on-demand deletion event and the on-demand creation event.

[0034] Combined with the fifth aspect and the above possible implementation manners, in another possible implementation manner, an execution module is configured to, after receiving a first event notification from a migration management node, call back a first event handling function corresponding to an on-demand deletion event to query service data of a service to be migrated of a service component, and delete configuration information of the service data of the service to be migrated on a first network device.

[0035] Combined with the fifth aspect and the above possible implementation manners, in another possible implementation manner, an execution module is configured to, after receiving a second event notification from the migration management node, call back a second event handling function corresponding to an on-demand creation event to query service data of a service to be migrated of a service component, and send configuration information corresponding to the above service data to a second network device according to a binding relationship between a first VPC and the second network device; wherein, the above first VPC is the VPC indicated by a VPC identifier, or the above first VPC is at least one VPC corresponding to a first tenant, and the above first tenant is the tenant indicated by the above tenant identifier.

[0036] In a sixth aspect of the embodiments of the present application, there is provided a service data migration device for executing the service data migration method described in the third aspect. The above device includes: a sending module, wherein: the above sending module is configured to send a subscription request message to a subscription management node; wherein, the above subscription request message is used to request to subscribe to an on-demand deletion event and an on-demand creation event, and the above subscription request message includes first function information of a first event handling function and second function information of a second event handling function; the above first function information is used to indicate the first event handling function, the first event handling function is used to execute the on-demand deletion event, the above second function information is used to indicate the second event handling function, and the second event handling function is used to execute the on-demand creation event.

[0037] The service data migration device provided in the embodiments of the present application can send a subscription request message to a subscription management node to request to subscribe to an on-demand deletion event and an on-demand creation event. In this way, a service component can subscribe to the on-demand deletion event and the on-demand creation event, and provide corresponding event handling functions, so as to implement the migration of service configurations based on the on-demand deletion event and the on-demand creation event, thereby enabling the migration of service configurations on a network device, reducing the complexity of the system, and improving the data migration speed.

[0038] In the seventh aspect of the embodiments of the present application, a service data migration system is provided. The system includes a migration management node and a subscription management node, where: the migration management node is configured to send an event notification to the subscription management node when receiving a service migration command; the subscription management node is configured to receive the event notification from the migration management node; where the service migration command is used to request to migrate the configuration information of the service data of the service to be migrated from a first network device to a second network device, the event notification carries the resource information to be migrated, the resource information to be migrated includes a VPC identifier or a tenant identifier corresponding to the service data of the service to be migrated, the first event notification is used to indicate the execution of an on-demand deletion event, and the second event notification is used to indicate the execution of an on-demand creation event; the on-demand deletion event is used to delete the configuration information of the service data on the first network device, and the on-demand creation event is used to create the configuration information of the service data on the second network device.

[0039] For the service data migration system provided by the embodiments of the present application, when it is necessary to migrate the configuration information of the service data of a tenant, the migration management node can send an event notification to the subscription management node to indicate the execution of an on-demand deletion event or an on-demand creation event, so as to realize the smooth migration of the tenant service through the "on-demand distribution" logic, thereby enabling the rapid migration of the service configuration on the network device, reducing the complexity of the system, and improving the data migration speed.

[0040] In combination with the seventh aspect, in a possible implementation, the first network device is a first firewall device, the resource information to be migrated includes a VPC identifier corresponding to the service data of the service to be migrated on the first network device, and the VPC identifier is used to indicate a VPC.

[0041] In combination with the seventh aspect and the possible implementation, in another possible implementation, the first network device is a first NAT gateway device, the resource information to be migrated includes a tenant identifier corresponding to the service data of the service to be migrated, the tenant identifier is used to indicate a first tenant, and the first tenant corresponds to at least one VPC.

[0042] In combination with the seventh aspect and the possible implementation, in another possible implementation, the migration management node is further configured to establish and save a binding relationship between a first VPC and a second network device, where the first VPC is the VPC indicated by the VPC identifier, or the first VPC is at least one VPC corresponding to the first tenant, and the first tenant is the tenant indicated by the tenant identifier.

[0043] Combined with the seventh aspect and possible implementation manners, in another possible implementation manner, the above-mentioned service component is further configured to send a subscription request message to a subscription management node, where the subscription request message is used to request subscriptions for on-demand deletion events and on-demand creation events, and the subscription request message includes first function information of a first event processing function and second function information of a second event processing function; the first function information is used to indicate the first event processing function, the first event processing function is used to execute on-demand deletion events, the second function information is used to indicate the second event processing function, and the second event processing function is used to execute the on-demand creation events; the subscription management node is further configured to receive the subscription request message from the service component; the subscription management node is further configured to establish an association relationship between the on-demand deletion event and the first function information, and establish an association relationship between the on-demand creation event and the second function information.

[0044] In an eighth aspect of the embodiments of the present application, an electronic device is provided, including a processor and a memory, where the memory stores a program or instruction that can run on the processor, and when the program or instruction is executed by the processor, the steps of the service data migration method described in the possible implementation manners of the first aspect, the second aspect, and the third aspect are implemented.

[0045] In a ninth aspect of the embodiments of the present application, a readable storage medium is provided, where a program or instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the service data migration method described in the possible implementation manners of the first aspect, the second aspect, and the third aspect are implemented. Description of the Drawings

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required to be used in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0047] Figure 1 One of the schematic diagrams of the service data migration method provided by the embodiments of the present application;

[0048] Figure 2 A schematic diagram of the deletion and addition of ordinary / large bandwidth firewall configurations and the deletion and addition of configurations on shared / dedicated NAT gateways provided by the embodiments of the present application;

[0049] Figure 3 Another schematic diagram of the service data migration method provided by the embodiments of the present application;

[0050] Figure 4Schematic diagram of creating a callback function for creating / deleting events on demand for the service components provided in the embodiments of this application;

[0051] Figure 5 The third schematic diagram of the service data migration method provided in the embodiments of this application;

[0052] Figure 6 The fourth schematic diagram of the service data migration method provided in the embodiments of this application;

[0053] Figure 7 The fifth schematic diagram of the service data migration method provided in the embodiments of this application;

[0054] Figure 8 The first schematic diagram of the composition of a service data migration device provided in the embodiments of this application;

[0055] Figure 9 The second schematic diagram of the composition of a service data migration device provided in the embodiments of this application;

[0056] Figure 10 The third schematic diagram of the composition of a service data migration device provided in the embodiments of this application. Detailed implementation manners

[0057] Next, the technical solutions in the embodiments of this application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this application without creative efforts shall fall within the protection scope of this application.

[0058] The terms "first", "second", etc. in the specification and claims of this application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of this application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second", etc. are generally of the same category, and the number of objects is not limited. For example, the first object can be one or multiple.

[0059] In addition, the term "and / or" herein is only a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " herein generally represents an "or" relationship between the associated objects before and after.

[0060] The terms "at least one (item)", "at least one of", etc. in the description and claims of this application refer to any one, any two or more combinations of the objects it contains. For example, at least one (item) of a, b, and c can represent: "a", "b", "c", "a and b", "a and c", "b and c", and "a, b, and c", where a, b, and c can be single or multiple. Similarly, "at least two (items)" means two or more, and its meaning is similar to that of "at least one (item)".

[0061] The following explains the concepts, terms, or self - coined words involved in the service data migration method, device, electronic device, and readable storage medium provided by the embodiments of this application.

[0062] 1. Tenant

[0063] A tenant is an identifier for various business resources of a customer in a cloud data center system. Usually, a cloud data center can support multiple tenants, and each tenant typically can contain multiple VPCs.

[0064] Tenants are created and assigned by system administrators. A tenant is the actual owner and manager of a VDC (Virtual Data Center, a collection of resources that an organization can use, including computing, storage, and network resources). Different VDCs correspond to different tenants.

[0065] 2. Virtual Private Cloud (VPC)

[0066] A VPC is a logical network element abstracted from a physical network, and logical network elements are arranged according to services, thus forming a virtual network. Different VPCs are logically isolated but share the physical network, thereby solving the sharing problem after physical network resource pooling.

[0067] 3. Network Address Translation (NAT)

[0068] NAT is the process of converting one or more local private IP addresses into a global public IP address, through which multiple local devices and hosts can access the Internet.

[0069] NAT is widely used in various types of Internet access methods and various types of networks. The reason is that NAT can not only solve the problem of insufficient IP addresses, but also effectively avoid attacks from outside the network and hide and protect the computers inside the network.

[0070] 4. NAT Gateway

[0071] The NAT Gateway is a network address translation service that provides NAT proxy (SNAT and DNAT) capabilities. The NAT Gateway provides proxy and forwarding capabilities for cloud hosts without public IPs in a Virtual Private Cloud (VPC), meeting the service requirements for public network access of cloud hosts without public IPs.

[0072] The NAT Gateway is set at the routing exit position from the private network to the public network, and two-way traffic must pass through the NAT Gateway. The NAT Gateway performs two address conversions or translations in two access directions, replacing source information in the outbound direction and converting destination information in the inbound direction.

[0073] 5. SDN (Software Defined Network)

[0074] Software Defined Network (SDN) is a network architecture with a centralized control plane, separation of control and forwarding, and direct programmability. The aim is to solve problems such as slow (protocol) development, lack of "consistent" policy control, poor scalability, and strong vendor dependence caused by the complexity of existing networks.

[0075] The SDN architecture mainly consists of two components: the SDN controller and network devices.

[0076] The SDN controller is the core component in the SDN network structure. As the control plane of the entire network, it undertakes the control behaviors of the entire network. The SDN controller can control the corresponding network devices to cooperate in implementing specified functions.

[0077] Network service providers convey requirements to the SDN controller, which is uniformly managed by the SDN controller, achieving centralized control. This reduces the difficulty of network maintenance, shortens the network deployment cycle, and saves operation and maintenance costs.

[0078] 6. SDN Firewall

[0079] The SDN firewall refers to the unified planning and implementation of firewall technology through the SDN controller. The northbound interface API of the SDN controller allows applications to configure and modify the firewall rules of switches in the network. Users can customize any firewall rules they want to implement, making it more flexible and intelligent.

[0080] The following combines the accompanying drawings to detail the HAVIP switching system provided by the embodiments of the present application through specific embodiments and their application scenarios.

[0081] Currently, the existing solutions related to business migration methods are implemented as follows:

[0082] Solution ①: Determine the resource pool requirements and host requirements corresponding to the target server to be migrated. Use the filtering method to select the target resource pool that meets the resource pool requirements from multiple resource pools, and select the target host that meets the host requirements from multiple hosts in the target resource pool, and then migrate the target server to the target host. The key point of this solution lies in how to select the target resource pool and target host for migration, and filter out the appropriate target resource pool and target host through certain algorithms, without involving the migration process of specific device configurations after determining the target resource pool and target host.

[0083] Solution ②: The business inventory management module interacts with the user through the business inventory management interface, and is used to provide business inventory synchronization services, business inventory management services, business design services, and business migration services; the migration task management module interacts with the user through the migration task management interface, and is used to provide migration order management services, migration task monitoring services, migration order processing services, and migration process execution services; the business migration management page is used to provide the entry of the business inventory management interface and the migration task management interface. The key point of this solution lies in implementing the order processing process of the business migration system, changing the orders originally processed offline to online processing, but the configuration change of the actual device still requires manual intervention, without involving the migration of specific network device configurations.

[0084] Solution ③: When the application context migration of the first application fails, the first network device determines to send request information to the edge configuration server or the first edge enabling server according to the application context retention requirements of the first application, thereby improving the efficiency of business migration. The key point of this solution lies in realizing the rapid switching of the terminal device at different network edges, thereby improving the migration efficiency of the upper-layer service. The solution focuses on the switching of the terminal device between communication networks, without involving the device configuration migration under the computer network.

[0085] Currently, the migration of tenants' businesses mainly faces the following problems:

[0086] (1) There are many involved businesses, and other businesses may be added in the future;

[0087] (2) The source device types and destination device types involved in the business migration are diverse, and the configurations are diverse;

[0088] Since the above factors need to be comprehensively considered during the specific migration, the current business migration method has high complexity and long business migration time.

[0089] The business data migration method provided by the embodiments of the present application realizes the smooth migration of tenant services through the "on-demand distribution" logic in the cloud data center scenario, which can reduce the complexity of the data migration process and improve the data migration speed. This business data migration method not only supports service migration based on VPC without affecting other VPC services of the same tenant, but also supports service migration based on the tenant without affecting the services of other tenants. Since the floating IP remains unchanged before and after the migration, it does not affect the existing services of the tenant. At the same time, this migration method can also support the mutual migration of tenant services between virtual devices and physical devices, and has a wider range of applicable tenants.

[0090] Figure 1 It is a flowchart of a business data migration method provided by the embodiments of the present application. As Figure 1 shown, this business data migration method may include the following steps S201 and S202:

[0091] Step S201: When the migration management node receives a service migration command, it sends a first event notification to the subscription management node.

[0092] Among them, the above-mentioned first event notification is used to indicate the execution of an on-demand deletion event, and the above-mentioned first event notification carries the information of the resources to be migrated. The information of the resources to be migrated includes the VPC identifier or tenant identifier corresponding to the service data of the service to be migrated on the first network device.

[0093] In the embodiments of the present application, the above-mentioned on-demand deletion event is used to delete the configuration information of the service data on the first network device.

[0094] Optionally, in the embodiments of the present application, the above-mentioned migration management node may be a migration management system in the cloud data network architecture, or an interface for processing service migration in the migration management system, that is, a migration interface.

[0095] Optionally, in the embodiments of the present application, the above-mentioned subscription management node may be a subscription management system in the cloud data network architecture.

[0096] Optionally, in the embodiments of the present application, the above-mentioned service component may be a service component corresponding to the service data whose configuration information needs to be migrated on the network device.

[0097] Optionally, in the embodiments of the present application, the above-mentioned service migration command is used to request to migrate the configuration information of the service data of the service to be migrated to the second network device.

[0098] Optionally, the above-mentioned service migration command may be written to carry the ID information of the VPC and the IP information of the second network device.

[0099] Optionally, in the embodiments of the present application, the first network device is a first firewall device, and the second network device is a second firewall device; or, the first network device is a first network address translation (NAT) gateway device, and the second network device is a second NAT gateway device.

[0100] Exemplarily, the first network device may be an SDN firewall inside the VPC, and the second network device may be a high-bandwidth SDN firewall outside the VPC.

[0101] Exemplarily, the first network device may be a shared NAT gateway, and the second network device may be an exclusive NAT gateway.

[0102] Optionally, in the embodiments of the present application, the first network device is a hardware network device or a software virtual device, and the second network device is a hardware device or a software virtual device.

[0103] Exemplarily, in the public cloud solution, the VPC can be bound to a hardware firewall or a software virtual firewall, and the tenant can bind a hardware NAT gateway or a software virtual NAT gateway. In non-migration services of business components, the configuration adaptation of hardware / software virtual devices will be adapted and implemented, including on-demand deletion and on-demand creation logic. Moreover, the migration operation only needs to bind the VPC and the tenant to the IP of the hardware / software virtual device. Therefore, the migration operation can directly support the migration across virtual devices and physical devices.

[0104] Optionally, in the embodiments of the present application, the service to be migrated may be a cloud data center service supported by the current network orchestrator. Exemplarily, the service to be migrated may include at least one of the following: VPC, FWaaS (Firewall as a Service), IPsec (Internet Protocol Security) VPN (Virtual Private Network), SSL (Security Socket Layer) VPN, NAT gateway, QoS (Quality of Service), shared bandwidth, peer connection, Floating IP (FIP), or FIP record filing.

[0105] It should be noted that IPsec VPN refers to a VPN service based on an encrypted channel over the Internet; SSLVPN refers to a VPN service that uses the SSL protocol to achieve remote access; shared broadband refers to a service that allows multiple public IPs to share a single bandwidth; FIP refers to a service that provides customers with static public IP address resources; FIP filing refers to a filing service for Floating IP. After filing, FIP is allowed to provide access services such as http or ssh; peer connection refers to a service for interconnecting business resource networks on the cloud, where data does not pass through the Internet, ensuring more secure data.

[0106] Optionally, in the embodiments of the present application, the above-mentioned service data includes at least one of inventory service data and newly added service data.

[0107] Optionally, in the embodiments of the present application, the above-mentioned first event notification may be a on-demand deletion notification.

[0108] Exemplarily, on-demand deletion refers to listening for the deletion event of the last service host in the VPC. After the event occurs, the configurations of various high-level services are recycled to reduce the device configuration capacity burden.

[0109] Step S202: The migration management node sends a second event notification to the subscription management node.

[0110] Among them, the above-mentioned second event notification is used to indicate the execution of the on-demand creation event, and the above-mentioned second event notification carries the information of the resources to be migrated.

[0111] In the embodiments of the present application, the above-mentioned on-demand creation event is used to create the configuration information of service data on the second network device.

[0112] Optionally, in the embodiments of the present application, the above-mentioned second event notification may be a on-demand creation notification.

[0113] Exemplarily, on-demand creation refers to listening for the new creation event of the first service host in the VPC. After the event occurs, the configurations of various pre-created high-level services are distributed to the devices, ensuring that configurations are generated only when there are service hosts, saving device capacity and operating burden.

[0114] It should be noted that the above-mentioned on-demand deletion and on-demand creation are the "on-demand processing" logics in the network orchestrator architecture. Through the "on-demand processing" logic in the network orchestrator architecture, it is possible to smoothly migrate and delete the configurations on the old devices and generate new configurations to be distributed to the new devices.

[0115] Figure 2It is a schematic diagram provided by an embodiment of the present application, which involves the deletion and addition of ordinary or large-bandwidth firewall configurations, and the deletion and addition of configurations on shared or dedicated NAT gateways. As Figure 2 shown, the SDN gateway is connected to the ordinary firewall, the value-added service (Service-Leaf) is connected to the large-bandwidth protection wall 1 and the large-bandwidth firewall 2, the CMNET router is connected to the shared NAT gateway and the dedicated NAT gateway, the CMNET router exchanges data with the north-south converging switch, and the north-south converging switch exchanges data with the SDN gateway.

[0116] As Figure 2 shown, when migrating the service configuration of the VPC service, the tenant VPC resource migration interface can be called to migrate the inner wall configuration of the large-bandwidth VPC to the large-bandwidth SDN firewall, or the tenant NAT gateway resource migration interface can be called to migrate the outer wall configuration of the tenant's existing services to the dedicated NAT gateway.

[0117] Optionally, the above-mentioned tenant VPC resource migration interface can be the above-mentioned migration management node, or an interface in the above-mentioned migration management node.

[0118] Optionally, in the embodiment of the present application, the migration of the configuration information of the above-mentioned service data can be the service configuration migration at the VPC granularity. Exemplarily, for the migration of the configuration information at the VPC granularity, the configuration of this VPC can be migrated between the ordinary firewall and the large-bandwidth firewall.

[0119] In some embodiments, the above-mentioned first network device is a first firewall device, and the above-mentioned resource information to be migrated may include the VPC identifier corresponding to the service data of the service to be migrated on the first network device, and the VPC identifier is used to indicate a VPC.

[0120] Exemplarily, the VPC identifier corresponding to the service data can be the VPC identifier of the VPC where the service data is located.

[0121] In the embodiment of the present application, for the service data migration method provided by the embodiment of the present application, the migration management node can send the VPC identifier corresponding to the service data of the service to be migrated to the subscription management node, and migrate the configuration information of the service data of any VPC indicated by the VPC identifier to a new firewall device or a NAT gateway device, so as to implement the service configuration migration at the VPC granularity.

[0122] It should be noted that a VPC is a private network space of a certain tenant in a public cloud, which contains elements such as routers, networks, subnets, and hosts, and can provide the above-mentioned service functions to enable users to access the resources of this network space.

[0123] Optionally, in the embodiments of the present application, the migration of the configuration information of the above service data may be a service configuration migration at the tenant granularity. Exemplarily, the migration of the configuration information at the tenant granularity involves the migration of the configuration of the NAT gateway devices of all the VPCs of the tenant.

[0124] In some embodiments, the above first network device is a first NAT gateway device, and the resource information to be migrated includes the tenant identifier corresponding to the service data of the service to be migrated on the first network device. This tenant identifier is used to indicate a first tenant, and the first tenant corresponds to at least one VPC.

[0125] Exemplarily, the tenant identifier corresponding to the service data may be the tenant identifier of the tenant to which the service data belongs.

[0126] Exemplarily, the at least one VPC corresponding to the first tenant may be all the VPCs or some of the VPCs that provide services for the first tenant.

[0127] In the embodiments of the present application, the migration management node may send the tenant identifier corresponding to the service data of the service to be migrated to the subscription management node, and migrate the configuration information of the services of all the VPCs of the tenant (such as the first tenant) indicated by this tenant identifier to a new firewall device or NAT gateway device, so as to implement the service configuration migration at the tenant granularity.

[0128] Optionally, in the embodiments of the present application, the combined service migration method provided by the embodiments of the present application may further include the following step S203:

[0129] Step S203: The migration management node establishes and saves the binding relationship between the above VPC and the second network device.

[0130] Wherein, the above second network device is the target network device to which the configuration information of the service data of the service to be migrated needs to be migrated, the first VPC is the VPC indicated by the VPC identifier, or the first VPC is at least one VPC corresponding to the first tenant, and the first tenant is the tenant indicated by the above tenant identifier.

[0131] Optionally, in the embodiments of the present application, the migration management node may establish the binding relationship between the VPC and the second network device according to the VPC information of the first VPC and the IP information of the second network device.

[0132] Further optionally, after the migration management node establishes the binding relationship between the VPC and the second network device, it may save this binding relationship in the database, so as to use this binding relationship to migrate the configuration information of the service data of the VPC to this second network device later.

[0133] Exemplarily, in the scenario of device configuration migration for services at the VPC granularity, assuming the first VPC is VPC1, the configuration information of the service data of VPC1 can be migrated from the small-bandwidth SDN firewall inside the VPC to the large-bandwidth SDN firewall outside the VPC.

[0134] Exemplarily, in the scenario of device configuration migration for services at the tenant granularity, assuming the first VPC includes VPC2, VPC3, and VPC4 that provide services for tenant A, the configuration information of the service data of VPC2, VPC3, and VPC4 can be migrated from the shared NAT gateway of the tenant to the dedicated NAT gateway of the tenant.

[0135] It should be noted that the above step S203 can be executed before the above step S201, or after the above step S201 and before the above step S202.

[0136] In the embodiments of the present application, the migration management node can establish and save the binding relationship between the first VPC and the second network device to which the configuration information needs to be migrated, so that the configuration information can be migrated to the second network device through the binding relationship subsequently, thereby realizing the rapid migration of service configuration information.

[0137] In the business data migration method provided by the embodiments of the present application, when it is necessary to migrate the configuration information of the business data of a tenant, the migration management node can send an event notification to the subscription management node to indicate the execution of an on-demand deletion event or an on-demand creation event, and realize the smooth migration of the tenant's business through the "on-demand delivery" logic, so as to be able to migrate the business configurations of various services on network devices of different source device types, and support the migration of business configurations at different granularities, thereby reducing the complexity of the system and improving the data migration speed.

[0138] Figure 3 It is a flowchart of a business data migration method provided by the embodiments of the present application, as Figure 3 shown, the business data migration method may include the following steps S301 and step S302:

[0139] Step S301: The subscription management node receives the first event notification of the service component from the migration management node.

[0140] Among them, the above first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries the information of the resources to be migrated. The information of the resources to be migrated includes the VPC identifier or tenant identifier corresponding to the service data of the service to be migrated on the first network device.

[0141] It should be noted that the explanation of this first event notification can be referred to above, and will not be elaborated here.

[0142] Optionally, in the embodiments of the present application, the above-mentioned on-demand deletion event is used to delete the configuration information of service data on the first network device. That is to say, the above-mentioned on-demand deletion event may be an event for deleting the service configuration of the service data to be migrated on the first network device.

[0143] Step S302: The subscription management node receives a second event notification from the migration management node.

[0144] Wherein, the above-mentioned second event notification is used to indicate the execution of the on-demand creation event, and the above-mentioned second event notification carries the information of the resource to be migrated.

[0145] Optionally, in the embodiments of the present application, the above-mentioned on-demand creation event is used to create the configuration information of service data on the second network device. That is to say, the above-mentioned on-demand creation event may be an event for creating the service configuration of the service to be migrated on the second network device.

[0146] For the service data migration method provided by the embodiments of the present application, the subscription management node can receive the event notifications of the on-demand deletion event and the on-demand creation event from the migration management node. The above-mentioned event notifications carry the VPC identifier or tenant identifier corresponding to the service data of the service to be migrated, so that the migration of the service configurations of various services on network devices of different source device types can be realized based on the event notifications, reducing the complexity of the system and improving the data migration speed.

[0147] Optionally, before the above-mentioned step S301 in the embodiments of the present application, the service data migration method provided by the embodiments of the present application may include the following steps A1 and A2:

[0148] Step A1: The subscription management node receives a subscription request message from the service component.

[0149] Wherein, the above-mentioned subscription request message is used to request the subscription of the on-demand deletion event and the on-demand creation event. The subscription request message includes the first function information of the first event processing function and the second function information of the second event processing function.

[0150] Step A2: The subscription management node establishes an association relationship between the on-demand deletion event and the first function information, and establishes an association relationship between the on-demand creation event and the second function information.

[0151] Exemplarily, the above-mentioned first function information may be the function name of the first event processing function, and the above-mentioned second function information may be the function name of the second event processing function.

[0152] Exemplarily, the function name of the first event handling function can indicate the first event handling function, and the function name of the second event handling function can indicate the second event handling function.

[0153] Exemplarily, the above first event handling function and second event handling function are event handling functions created for business components.

[0154] In an embodiment of the present application, the subscription management node can receive a subscription request message of a business component, and based on the function information of the event handling function provided by the business component in the subscription request message, establish an association relationship between the function information of the business component and the event, so as to implement subscribing to the on-demand deletion event and on-demand creation event for the business component, and thus be able to, after receiving an event notification, call the corresponding function according to the function information associated with the event indicated by the event notification to execute the event, and further implement the rapid migration of the service configuration of various services on the network device.

[0155] Optionally, in an embodiment of the present application, before step A2, the service data migration method provided by the embodiment of the present application may include the following step B1:

[0156] Step B1: The subscription management node creates an on-demand deletion event and an on-demand creation event.

[0157] Exemplarily, the subscription management node can create an event identifier corresponding to the on-demand deletion event and an event identifier corresponding to the on-demand creation event, and then associate the event identifier of the on-demand deletion event with the function name of the first event handling function, and associate the event identifier of the on-demand creation event with the function name of the second event handling function, so as to establish an association relationship between the on-demand creation event and the corresponding event handling function.

[0158] In an embodiment of the present application, the subscription management node can create unified on-demand creation events and on-demand deletion events, and respectively establish association relationships between the on-demand creation events and on-demand deletion events and the corresponding functions, so as to implement the rapid migration of tenant services through the "on-demand deletion" and "on-demand creation" logics.

[0159] Optionally, in an embodiment of the present application, after step S301, the service data migration method provided by the embodiment of the present application further includes the following step S303:

[0160] Step S303: The subscription management node calls back the first event handling function corresponding to the on-demand deletion event to query the service data of the service to be migrated, and deletes the configuration information of the service data of the service to be migrated on the first network device.

[0161] It can be understood that the first event handling function corresponding to the on-demand deletion event refers to the event handling function indicated by the first function information associated with the on-demand deletion event.

[0162] Optionally, in the embodiments of the present application, the service component subscribes to the on-demand deletion event in advance and registers a first event handling function for executing the on-demand deletion event. After receiving the first event announcement indicating the execution of the on-demand deletion event, the subscription management node calls back the first event handling function to trigger the service component to perform the on-demand deletion process, that is, to delete the configuration information of the service data of the service to be migrated on the first network device.

[0163] Exemplarily, after receiving the first event announcement from the migration management node, the subscription management node obtains the function information associated with the on-demand deletion event (i.e., the first function information) according to the event indicated by the first event announcement (i.e., the on-demand deletion event), and obtains the event handling function indicated by the function information (i.e., the first event handling function), and then calls the event handling function to execute the on-demand deletion event.

[0164] Further optionally, the subscription management node queries the service data of the service to be migrated by calling back the first event handling function corresponding to the on-demand deletion event, and deletes the configuration information of the service data of the service to be migrated on the first network device. Since only the configuration information of the service data is deleted, the floating IP of the service to be migrated remains unchanged, so that the relationship between the floating IP of each service and the service can be maintained.

[0165] Exemplarily, the service component can only delete the configuration information of the service data on the SDN firewall, so as to maintain the relationship between the floating IP of the service data and the service.

[0166] In the related art, when migrating the service configuration to the target network device, the service is usually deleted from the original VPC, and then the service is rebuilt on the new VPC associated with the target network device. Since the VPC where the service is located changes after the service is rebuilt and a new floating IP is assigned to the service, the floating IP of the service changes before and after the migration. The service data migration method provided by the embodiments of the present application can only delete the service configuration information on the device while maintaining the floating IP of the service before and after the migration. Since the VPC where the service is located does not change before and after the configuration information migration, it does not affect the subsequent use of the service by the user.

[0167] In the embodiments of the present application, the subscription management node can call back the event handling function corresponding to the on-demand deletion event announcement to query the service data of the service to be migrated by the service component, and delete the configuration information of the service data on the source device, so as to quickly delete the configuration of the service data based on the "on-demand deletion" logic.

[0168] Optionally, in the embodiments of the present application, after the above step S302, the service data migration method provided by the embodiments of the present application may include the following step S304:

[0169] Step S204: The subscription management node calls back the second event handling function corresponding to the on-demand creation event to query the service data of the service to be migrated, and sends the configuration information of the service data of the service to be migrated to the second network device according to the binding relationship between the first VPC and the second network device.

[0170] Wherein, the above-mentioned first VPC is the VPC indicated by the VPC identifier, or the first VPC is at least one VPC corresponding to the first tenant, and the first tenant is the tenant indicated by the tenant identifier.

[0171] It can be understood that the second event handling function corresponding to the on-demand creation event refers to the event handling function indicated by the second function information associated with the on-demand creation event.

[0172] Optionally, in the embodiment of the present application, the service component has subscribed to the on-demand creation event in advance and registered the second event handling function for executing the on-demand creation event. After the subscription management node receives the second event notification indicating the execution of the on-demand creation event, it calls back the second event handling function to trigger the service component to perform on-demand creation processing, that is, to create the configuration information of the service data of the service to be migrated on the second network device.

[0173] Exemplarily, after the subscription management node receives the second event notification from the migration management node, according to the event indicated by the second event notification (i.e., the on-demand creation event), it obtains the function information associated with the on-demand creation event (i.e., the second function information), and obtains the event handling function indicated by the function information (i.e., the second event handling function), and then calls back the second event handling function to trigger the execution of the on-demand creation event.

[0174] Furthermore, during the execution of the second event handling function, the service component can query the service data related to the VPC and the configuration information of the service data, query the binding relationship between the VPC where the service to be migrated by the service component is located and the second network device from the database, and then send the configuration information of the service to be migrated to the second network device according to the binding relationship to migrate the configuration information to the second network device.

[0175] In the embodiment of the present application, in the cloud data center scenario, the smooth migration of tenant services is realized through the "on-demand distribution" logic. Not only the service migration based on the VPC does not affect the other VPC services of the same tenant, but also the service migration based on the tenant is supported without affecting the services of other tenants.

[0176] In the embodiment of the present application, the subscription management node can call back the event handling function corresponding to the on-demand creation event, and according to the binding relationship between the first VPC corresponding to the service to be migrated and the second network device, send the configuration information of the service data on the first VPC to the second network device, so as to realize the rapid migration of the configuration of the service data based on the "on-demand creation" logic.

[0177] Figure 4 Schematic diagram of creating a callback function for on-demand creation or on-demand deletion events for the service components provided in the embodiment of the present application. As Figure 4 shown, the above service components include service component A, service component B, and service component C. Among them, the service component A registers a callback function for the on-demand creation event (denoted as fun_a_create_callback) and a callback function for the on-demand deletion event (denoted as fun_a_delete_callback). After initializing the service component A, the service component A subscribes to the event notification, that is, the service component A subscribes to the on-demand creation event / callback function and subscribes to the on-demand deletion event / callback function. The subscription management system generates a registry of on-demand creation event functions and a registry of on-demand deletion event callback functions for the service component A. The process of creating the callback functions of service component B and service component C is the same and will not be elaborated here.

[0178] In the embodiment of the present application, the "on-demand processing" logic mainly utilizes the message subscription mechanism in the network orchestrator Neutron. Each service component subscribes to the "on-demand creation" and "on-demand deletion" events in advance, and each service needs to provide its own callback function when subscribing. When a VPC migration is requested, the migration logic code will first record the binding relationship between the VPC or tenant and the migration target device, and start the "on-demand deletion" event notification process. The message subscription system will sequentially notify each service component of the "on-demand deletion" event, and each service executes the "on-demand deletion" callback function, and deletes the resource configuration from the old device in the callback function. Subsequently, the location of the migration request is converted into a binding record of the VPC / tenant and the new device; finally, the migration logic uses the message subscription system to sequentially notify each service component of the "on-demand creation" event again, and each service executes the "on-demand creation" callback function, and according to the binding relationship between the VPC / tenant and the migration target device, sends the resource configuration to the migration target device.

[0179] In the embodiment of the present application, through the "on-demand processing" business logic, when each new service is added to the system, it is necessary to implement the on-demand creation and on-demand deletion business logics of its own business and complete the subscription of on-demand events. Once the service component implements the on-demand logic and event subscription, this service can support the migration of service configurations, and the migration framework does not require secondary development / modification. Therefore, the migration framework can support the expansion of new services.

[0180] Figure 5 The flowchart of a service data migration method provided by an embodiment of this application is as follows. Figure 5 As shown, the service data migration method may include the following step S401:

[0181] Step S401: The service component sends a subscription request message to the subscription management node.

[0182] Among them, the above subscription request message is used to request to subscribe to the on-demand deletion event and the on-demand creation event. The above subscription request message includes the first function information of the first event processing function and the second function information of the second event processing function; the above first function information is used to indicate the first event processing function, the first event processing function is used to execute the on-demand deletion event, the above second function information is used to indicate the second event processing function, and the second event processing function is used to execute the on-demand creation event.

[0183] Exemplarily, the above first function information may be the function name of the first event processing function, and the above second function information may be the function name of the second event processing function.

[0184] In the embodiment of this application, the service component may send a subscription request message to the subscription management node to request to subscribe to the on-demand deletion event and the on-demand creation event. In this way, the service component can subscribe to the on-demand deletion event and the on-demand creation event, and provide corresponding event processing functions, so as to implement the migration of service configurations based on the on-demand deletion event and the on-demand creation event, thereby enabling the migration of service configurations on network devices, reducing the complexity of the system, and improving the data migration speed.

[0185] An embodiment of this application provides a service data migration system. The tenant service migration system at least includes: a migration management node and a subscription management node.

[0186] Among them, the above migration management node is used to send an event notification to the subscription management node when receiving a service migration command; the above subscription management node is used to receive the event notification from the migration management node. Among them, the above service migration command is used to request to migrate the configuration information of the service data of the service to be migrated to the second network device. The event notification carries the information of the resource to be migrated. The information of the resource to be migrated includes the VPC identifier or tenant identifier corresponding to the service data of the service to be migrated on the first network device. The event notification includes a first event notification and a second event notification. The first event notification is used to indicate the execution of the on-demand deletion event, and the second event notification is used to indicate the execution of the on-demand creation event.

[0187] Optionally, in the embodiments of the present application, the above migration management node is further configured to establish and save the binding relationship between the first VPC and the second network device, where the first VPC is the VPC indicated by the VPC identifier, or the first VPC is at least one VPC corresponding to the first tenant, and the first tenant is the tenant indicated by the tenant identifier.

[0188] Optionally, in the embodiments of the present application, the service data migration system may further include a service component, where the service component is configured to send a subscription request message to the subscription management node. The subscription request message is used to request to subscribe to the on-demand deletion event and the on-demand creation event. The subscription request message includes the first function information of the first event processing function and the second function information of the second event processing function. The first function information is used to indicate the first event processing function, and the first event processing function is used to execute the on-demand deletion event. The second function information is used to indicate the second event processing function, and the second event processing function is used to execute the on-demand creation event. The subscription management node is further configured to receive the subscription request message from the service component. The subscription management node is further configured to establish an association relationship between the on-demand deletion event and the first function information, and establish an association relationship between the on-demand creation event and the second function information.

[0189] It should be noted that the specific explanation of this embodiment can be referred to the above description, and will not be elaborated here.

[0190] The following provides an exemplary illustration of the service data migration method provided by the embodiments of the present application through examples.

[0191] As Figure 6 shown, taking the migration management node as the migration interface in the migration management system (corresponding to Figure 6 the migration management in Figure 6 ), the subscription management node as the subscription management system (corresponding to Figure 6 the subscription management in

[0192] Step 11: The administrator calls the service migration command interface to request VPC configuration migration.

[0193] Optionally, the service migration command carries the following parameters: VPC id, device ip.

[0194] Exemplarily, before step 11, the system may perform component initialization operations on each service component.

[0195] It should be noted that the above system can be an orchestration system. After the software program of the orchestration system is started, component initialization operations can be performed on each business component.

[0196] Step 12: The migration management calls the subscription management and issues an "on-demand deletion" event notice (i.e., the first event notice), and the "on-demand deletion" event notice carries VPC information.

[0197] Step 13: The subscription management executes the on-demand deletion event callback function (i.e., the first event handling function).

[0198] Step 14: Query the business data managed by the business component.

[0199] It should be noted that the above business component corresponds to Figure 6 the advanced services (1,..., n) and VPC services in

[0200] Step 15: The business component deletes the configuration information on the ordinary firewall device and deletes the associated configuration information of the business on the NAT gateway.

[0201] It should be noted that in the related art, when migrating business configurations to the target network device, the business is usually deleted from the original VPC and then rebuilt on the new VPC associated with the target network device. Since the VPC where the business is located changes after the business is rebuilt and a new floating IP is assigned to the business, the floating IP of the business changes before and after the migration. The business data migration method provided by the embodiments of the present application can only delete the business configuration information on the device while maintaining the floating IP of the business before and after the migration. Since the VPC where the business is located does not change before and after the configuration information migration, it does not affect the subsequent use of the business by users.

[0202] Exemplarily, after all the callback functions are executed, the process returns to the migration management.

[0203] Step 16: The migration management establishes and saves the binding relationship between the VPC indicated by the VPC information (i.e., the first VPC) and the new device.

[0204] Step 17: The migration management calls the subscription management and sends an "on-demand creation" event notice (i.e., the second event notice), and the notice carries VPC information.

[0205] Step 18: The subscription management calls back the business "on-demand creation" event callback function.

[0206] Step 19: The business component queries the business data related to the VPC corresponding to the VPC information.

[0207] Step 20: The business component performs the distribution of the business configuration information on the large bandwidth firewall device.

[0208] Exemplarily, the subscription management triggers the business component to query the business data related to the VPC by calling the "create on demand" event callback function, and distributes the configuration to the corresponding large bandwidth firewall device according to the binding relationship between the VPC and the new device.

[0209] Exemplarily, after all the callback functions are executed, the process returns to the migration interface, and the migration is completed, and the migration success is returned.

[0210] As Figure 7 shown, taking the migration management node as the migration interface (corresponding to the migration management in Figure 7 ), the subscription management node as the subscription management system (corresponding to the subscription management in Figure 7 ), the business component, the first network device as the shared NAT gateway, and the second network device as the dedicated NAT gateway as an example, the above business data migration method may include the following steps:

[0211] Step 31: The user calls the business migration command interface to request tenant configuration migration.

[0212] Exemplarily, the business migration command carries parameters: tenant id, device ip.

[0213] Step 32: The migration management queries the VPC of the tenant corresponding to the tenant id;

[0214] Step 33: The migration management issues a "delete on demand" event notice (i.e., the first event passes) to the subscription management, and the notice carries the tenant id or the VPC id of the tenant.

[0215] Step 34: The subscription management calls back the business "delete on demand" event callback function (i.e., the first event processing function).

[0216] Step 35: The business component queries the business data associated with the VPC.

[0217] It should be noted that the above business component corresponds to Figure 7 the advanced services (1,..., n) and VPC services in

[0218] Step 36: The business component deletes the configuration on the shared NAT gateway.

[0219] Step 37: The migration management saves the binding relationship between the VPC of the tenant and the dedicated NAT gateway.

[0220] Step 38: The migration management sends a "create on demand" event notice (i.e., the second event notice) to the subscription management, and the notice carries the VPC information of at least one VPC that provides services for the tenant.

[0221] Step 39, the subscription management callback callback function of the "create on demand" event (i.e., the second event processing function);

[0222] Step 40: The business component queries the VPC-related business data corresponding to the VPC information through the callback function of the "create on demand" event.

[0223] Step 41: The business component sends the configuration to the corresponding dedicated NAT gateway based on the binding relationship between the VPC and the new device.

[0224] Exemplarily, after all callback functions are executed, the process returns to the migration interface, the migration is completed, and a migration success is returned.

[0225] The embodiment of the present application proposes a method for smooth migration of tenant services in a cloud data center scenario, which implements on-demand operation logic for each service, so that service configuration can be migrated at the VPC or tenant granularity. When the VPC is migrated, other VPC services under the same tenant are not affected; when the tenant is migrated, all services of other tenants are not affected; the external floating IP information of each service will not be changed during the migration operation, so the tenant's existing services will not be affected. The migration implemented by this solution can also directly support migration between software virtual firewalls and physical firewall devices. In addition, when a new service is added, it is only necessary to implement the on-demand processing logic and event subscription of the service itself, and the migration function of the new service can be supported without modifying the migration framework.

[0226] The business data migration method provided in the embodiment of the present application can be executed by a business data migration device. It is understandable that, in order to realize the above functions, the business data migration device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

[0227] The embodiment of the present application can divide the functional modules of the business data migration device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0228] In the case of dividing each functional module according to the corresponding function, Figure 8 Fig. shows a possible schematic composition diagram of the service data migration device involved in the above embodiment. As Figure 8 shown, the service data migration device 51 may include: a sending module 52; the above-mentioned sending module 52 is used to send a first event notification to the subscription management node when receiving a service migration command, the first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries the information of the resources to be migrated. The above-mentioned information of the resources to be migrated includes the VPC identifier or tenant identifier corresponding to the service data of the service to be migrated; and, the above-mentioned sending module 52 is further used to send a second event notification to the subscription management node, the above-mentioned second event notification is used to indicate the execution of an on-demand creation event, and the second event notification carries the above-mentioned information of the resources to be migrated; wherein, the above-mentioned service migration command is used to request to migrate the configuration information of the service data of the service to be migrated from the first network device to the second network device, the above-mentioned on-demand deletion time is used to delete the configuration information of the service data on the first network device, and the above-mentioned on-demand creation event is used to create the configuration information of the service data on the second network device.

[0229] Optionally, in the embodiment of the present application, the above-mentioned first network device is a first firewall device, the above-mentioned information of the resources to be migrated includes the VPC identifier corresponding to the service data of the service to be migrated on the first network device, and the above-mentioned VPC identifier is used to indicate a VPC.

[0230] Optionally, in the embodiment of the present application, the first network device is a first NAT gateway device, the information of the resources to be migrated includes the tenant identifier corresponding to the service data of the service to be migrated, and the above-mentioned tenant identifier is used to indicate a first tenant, and the above-mentioned first tenant corresponds to at least one VPC.

[0231] Optionally, in the embodiment of the present application, the device further includes: an execution module; the above-mentioned execution module is used to establish and save the binding relationship between the first VPC and the second network device; wherein, the above-mentioned first VPC is the VPC indicated by the VPC identifier, or the above-mentioned first VPC is at least one VPC corresponding to the first tenant, and the above-mentioned first tenant is the tenant indicated by the tenant identifier.

[0232] The service data migration device provided by the embodiment of the present application, in the case of needing to migrate the configuration information of the service data of a tenant, the service data migration device can send an event notification to the subscription management node to indicate the execution of an on-demand deletion event or an on-demand creation event, and realize the smooth migration of the tenant service through the "on-demand distribution" logic, so as to be able to realize the rapid migration of the service configuration on the network device, reduce the complexity of the system, and improve the data migration speed.

[0233] Figure 9Shows another possible composition schematic diagram of the service data migration device involved in the above embodiments. As Figure 9 shown, the service data migration device 61 may include a receiving module 62; the above-mentioned receiving module 62 is used to receive a first event notification from a migration management node, the first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries information about resources to be migrated. The information about resources to be migrated includes the VPC identifier or tenant identifier corresponding to the service data of the service to be migrated; the receiving module 62 is further used to receive a second event notification from the migration management node, the second event notification is used to indicate the execution of an on-demand creation event, and the second event notification carries the information about the resources to be migrated; wherein, the on-demand deletion event is used to delete the configuration information of the service data on the first network device, and the on-demand creation event is used to create the configuration information of the service data on the second network device.

[0234] Optionally, in the embodiments of the present application, before the receiving module is further used to receive the first event notification from the migration management node, it receives a subscription request message from a service component. The subscription request message is used to request to subscribe to the on-demand deletion event and the on-demand creation event. The subscription request message includes first function information of a first event processing function and second function information of a second event processing function; the device further includes: an execution module; the execution module is used to establish an association relationship between the on-demand deletion event and the first function information, and establish an association relationship between the on-demand creation event and the second function information.

[0235] Optionally, in the embodiments of the present application, before the execution module is further used to establish an association relationship between the on-demand deletion event and the first function information, and establish an association relationship between the on-demand creation event and the second function information, it creates the on-demand deletion event and the on-demand creation event.

[0236] Optionally, in the embodiments of the present application, after the execution module receives the first event notification from the migration management node, it calls back the first event processing function corresponding to the on-demand deletion event to query the service data of the service to be migrated of the service component, and deletes the configuration information of the service data of the service to be migrated on the first network device.

[0237] Optionally, in the embodiments of the present application, after the execution module receives the second event notification from the migration management node, it calls back the second event processing function corresponding to the on-demand creation event to query the service data of the service to be migrated of the service component, and sends the configuration information corresponding to the service data to the second network device according to the binding relationship between the first VPC and the second network device; wherein, the first VPC is the VPC indicated by the VPC identifier, or the first VPC is at least one VPC corresponding to the first tenant, and the first tenant is the tenant indicated by the tenant identifier.

[0238] The service data migration device provided by the embodiment of the present application can receive event announcements of on-demand deletion events and on-demand creation events from a migration management node. The above event announcements carry the VPC identifier or tenant identifier corresponding to the service data of the service to be migrated, so that the service configuration of various services on network devices of different source device types can be migrated based on the event announcements, reducing the complexity of the system and improving the data migration speed.

[0239] Figure 10 Another possible schematic diagram of the service data migration device involved in the above embodiment is shown. As Figure 10 shown, the device 70 includes: a sending module 71. Among them: the above sending module 71 is used to send a subscription request message to a subscription management node; wherein, the above subscription request message is used to request to subscribe to on-demand deletion events and on-demand creation events, and the above subscription request message includes first function information of a first event processing function and second function information of a second event processing function; the above first function information is used to indicate the first event processing function, and the first event processing function is used to execute on-demand deletion events, and the above second function information is used to indicate the second event processing function, and the second event processing function is used to execute on-demand creation events.

[0240] The service data migration device provided by the embodiment of the present application can send a subscription request message to a subscription management node to request to subscribe to on-demand deletion events and on-demand creation events. In this way, service components can subscribe to on-demand deletion events and on-demand creation events and provide corresponding event processing functions to implement the migration of service configurations based on on-demand deletion events and on-demand creation events, so that the migration of service configurations on network devices can be realized, reducing the complexity of the system and improving the data migration speed.

[0241] It should be noted that all relevant contents of the steps involved in the above method embodiment can be cited in the function description of the corresponding function module, and will not be repeated here.

[0242] The embodiment of the present application provides an electronic device, including a processor and a memory. The memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the above Figures 1 to 7 service data migration method are implemented.

[0243] Specifically, the above electronic device includes a processor, a memory, and a communication interface.

[0244] In some embodiments, a communication interface is configured to, upon receiving a service migration command, send a first event notification to a subscription management node. The first event notification is used to indicate the execution of an on-demand deletion event, and the to-be-migrated resource information is carried in the first event notification. The to-be-migrated resource information includes a virtual private cloud (VPC) identifier or a tenant identifier corresponding to the service data of the to-be-migrated service. Further, the communication interface is also configured to send a second event notification to the subscription management node. The second event notification is used to indicate the execution of an on-demand creation event, and the to-be-migrated resource information is carried in the second event notification.

[0245] Wherein, the service migration command is used to request to migrate the configuration information of the service data of the to-be-migrated service from a first network device to a second network device. The on-demand deletion event is used to delete the configuration information of the service data on the first network device, and the on-demand creation event is used to create the configuration information of the service data on the second network device.

[0246] It should be noted that the specific working processes of the functional modules in the electronic device provided in the embodiments of the present application can refer to the specific descriptions of the corresponding processes in the method embodiments on the migration management node side, and the embodiments of the present application will not elaborate herein.

[0247] In other embodiments, a communication interface is configured to receive a first event notification from a migration management node. The first event notification is used to indicate the execution of an on-demand deletion event, and the to-be-migrated resource information is carried in the first event notification. The to-be-migrated resource information includes a VPC identifier or a tenant identifier corresponding to the service data of the to-be-migrated service. The communication interface is also configured to receive a second event notification from the migration management node. The second event notification is used to indicate the execution of an on-demand creation event, and the to-be-migrated resource information is carried in the second event notification. Wherein, the on-demand deletion event is used to delete the configuration information of the service data on the first network device, and the on-demand creation event is used to create the configuration information of the service data on the second network device.

[0248] It should be noted that the specific working processes of the functional modules in the electronic device provided in the embodiments of the present application can refer to the specific descriptions of the corresponding processes in the method embodiments on the subscription management node side, and the embodiments of the present application will not elaborate herein.

[0249] The embodiments of the present application provide a readable storage medium, on which a program or instructions are stored. When the program or instructions are executed by a processor, the steps of the above service data migration method are implemented.

[0250] From the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0251] In the several embodiments provided in the present application, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in electrical, mechanical or other forms.

[0252] The units described as separate components may or may not be physically separated. The components displayed as units may be one physical unit or multiple physical units, that is, they can be located in one place or distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0253] In addition, in each embodiment of the present application, the functional units can be integrated in a processing unit, or each unit exists physically alone, or two or more units can be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0254] If the above integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on such an understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The software product is stored in a storage medium and includes several instructions to enable a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: USB flash drive, mobile hard disk, read-only memory (ROM), random access memory (RAM), non-volatile storage medium, magnetic disk or optical disk and other various media that can store program codes.

[0255] As described above, it is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the said claims.

Claims

1. A method for migrating service data, characterized in that, the method includes: When the migration management node receives a service migration command, it sends a first event notification to the subscription management node. The first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries information about the resources to be migrated. The information about the resources to be migrated includes the virtual private cloud (VPC) identifier or tenant identifier corresponding to the service data of the service to be migrated; and, The migration management node sends a second event notification to the subscription management node. The second event notification is used to indicate the execution of an on-demand creation event, and the second event notification carries the information about the resources to be migrated; wherein, the service migration command is used to request to migrate the configuration information of the service data of the service to be migrated from a first network device to a second network device. The on-demand deletion event is used to delete the configuration information of the service data on the first network device, and the on-demand creation event is used to create the configuration information of the service data on the second network device.

2. The method according to claim 1, characterized in that, the first network device is a first firewall device, and the information about the resources to be migrated includes the VPC identifier corresponding to the service data of the service to be migrated on the first network device. The VPC identifier is used to indicate a VPC.

3. The method according to claim 1, characterized in that, the first network device is a first NAT gateway device, and the information about the resources to be migrated includes the tenant identifier corresponding to the service data of the service to be migrated. The tenant identifier is used to indicate a first tenant, and the first tenant corresponds to at least one VPC.

4. The method according to any one of claims 1 to 3, characterized in that, the method further includes: The migration management node establishes and saves the binding relationship between the first VPC and the second network device; wherein, the first VPC is the VPC indicated by the VPC identifier, or the first VPC is at least one VPC corresponding to a first tenant, and the first tenant is the tenant indicated by the tenant identifier.

5. A method for migrating service data, characterized in that, the method includes: The subscription management node receives a first event notification from the migration management node. The first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries information about the resources to be migrated. The information about the resources to be migrated includes the VPC identifier or tenant identifier corresponding to the service data of the service to be migrated; The subscription management node receives a second event notification from the migration management node. The second event notification is used to indicate the execution of an on-demand creation event, and the second event notification carries the information about the resources to be migrated; wherein, the on-demand deletion event is used to delete the configuration information of the service data on the first network device, and the on-demand creation event is used to create the configuration information of the service data on a second network device.

6. The method according to claim 5, characterized in that, before the subscription management node receives the first event notification from the migration management node, the method further includes: The subscription management node receives a subscription request message from a service component. The subscription request message is used to request subscription to on-demand deletion events and on-demand creation events. The subscription request message includes first function information of a first event processing function and second function information of a second event processing function. The first function information is used to indicate the first event processing function, and the first event processing function is used to execute the on-demand deletion event. The second function information is used to indicate the second event processing function, and the second event processing function is used to execute the on-demand creation event; The subscription management node establishes an association relationship between the on-demand deletion event and the first function information, and establishes an association relationship between the on-demand creation event and the second function information.

7. The method according to claim 6, wherein, Before establishing the association relationship between the on-demand deletion event and the first function information, and establishing the association relationship between the on-demand creation event and the second function information, the method further includes: The subscription management node creates the on-demand deletion event and the on-demand creation event.

8. The method according to any one of claims 5 to 7, wherein, After the subscription management node receives a first event notification from a migration management node, the method further includes: The subscription management node calls back the first event processing function corresponding to the on-demand deletion event to query the service data of the service to be migrated of the service component, and deletes the configuration information of the service data of the service to be migrated on the first network device.

9. The method according to any one of claims 5 to 7, wherein, After the subscription management node receives a second event notification from the migration management node, the method further includes: The subscription management node calls back the second event processing function corresponding to the on-demand creation event to query the service data of the service to be migrated of the service component, and sends the configuration information of the service data of the service to be migrated to the second network device according to the binding relationship between the first VPC and the second network device; wherein, the first VPC is the VPC indicated by the VPC identifier, or the first VPC is at least one VPC corresponding to the first tenant, and the first tenant is the tenant indicated by the tenant identifier.

10. A service data migration device, wherein, The device includes: a sending module; The sending module is configured to, when receiving a service migration command, send a first event notification to a subscription management node. The first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries information about resources to be migrated. The information about resources to be migrated includes a VPC identifier or a tenant identifier corresponding to the service data of the service to be migrated; and, The sending module is further configured to send a second event notification to the subscription management node. The second event notification is used to indicate the execution of an on-demand creation event, and the second event notification carries the information about resources to be migrated; Among them, the service migration command is used to request to migrate the configuration information of the service data of the service to be migrated from a first network device to a second network device. The on-demand deletion time is used to delete the configuration information of the service data on the first network device, and the on-demand creation event is used to create the configuration information of the service data on the second network device.

11. A service data migration device, characterized in that the device includes: a receiving module; the receiving module is configured to receive a first event notification from a migration management node, the first event notification is used to indicate the execution of an on-demand deletion event, and the first event notification carries information about resources to be migrated, and the information about resources to be migrated includes a VPC identifier or a tenant identifier corresponding to the service data of the service to be migrated; the receiving module is further configured to receive a second event notification from the migration management node, the second event notification is used to indicate the execution of an on-demand creation event, and the second event notification carries the information about resources to be migrated; Among them, the on-demand deletion event is used to delete the configuration information of the service data on the first network device, and the on-demand creation event is used to create the configuration information of the service data on a second network device.

12. An electronic device, characterized in that it includes a processor and a memory, the memory stores a program or instructions that can run on the processor, and when the program or instructions are executed by the processor, the steps of the service data migration method according to any one of claims 1 to 9 are implemented.

13. A readable storage medium, characterized in that the readable storage medium stores a program or instructions, and when the program or instructions are executed by a processor, the steps of the service data migration method according to any one of claims 1 to 9 are implemented.

Images